16 guides. 51 minutes, all of them.

A fitter does about 8 wired installs in a night. Whether they manage that depends almost entirely on the yard, not on them.

1. 1

   Send the vehicle list with plates and parking positions two days before.

   Ten of every fifty-five minutes are already spent finding the vehicle. A list in parking order takes most of that back.

2. 2

   Leave keys in a box the night supervisor controls, labelled by plate.

   Ignition has to be switched on to commission the unit. A missing key is a vehicle skipped until next week.

3. 3

   Light the bays, or tell us which ones are dark.

   We bring lighting. We bring more of it if we know.

4. 4

   Name one person on site with a phone who can move a vehicle.

   The truck blocking three others is always the one without a driver.

5. 5

   Do not fuel Advanced trucks before the visit.

   Probe calibration is a fill from nearly empty. A full tank means a second visit.

A vehicle without a driver attached records trips that belong to nobody, and every score, alert and report built on them is anonymous.

1. 1

   Import vehicles from the sheet you already keep: plate, type, fuel, and the unit serial on the fitter's photo sheet.

2. 2

   Invite drivers by mobile number. The app arrives in Arabic unless they choose otherwise.

3. 3

   Choose how drivers are identified: a fixed assignment, a key fob, or signing in to the app at the start of a shift.

   Shared vehicles need a fob or sign-in. A fixed assignment is wrong the first day someone covers a shift.

4. 4

   Check the unassigned-trips report after the first week, and fix the pattern rather than the trips.

Essential includes 25 geofences. That is enough for a first month if you draw the ones you will act on, and far too many if you draw every customer.

1. 1

   Start with your own yards and workshops.

   They turn raw movement into 'left the depot' and 'arrived for service', which half the alerts depend on.

2. 2

   Draw the boundary around where vehicles park, not the property line.

   A fence around the whole site misses a truck parked on the service road outside it.

3. 3

   Add operating hours to each yard, then turn on after-hours movement alerts for those yards only.

4. 4

   Leave customer sites until dispatch is set up — jobs create their own temporary fences.

Most permission problems are the same one: everyone was made an administrator in week one because it was quicker.

1. 1

   Administrators: two people, named. Billing, users and integrations.

2. 2

   Managers: see and act on their own depots or regions, not the whole fleet.

3. 3

   Dispatchers: plan and message; no access to footage or scores.

4. 4

   Workshop: maintenance, faults and inspections for all vehicles; nothing about drivers.

5. 5

   Footage retrieval is its own permission, and every use of it is logged with a reason.

   Drivers can see that log. A camera programme survives on that.

A replay is a list of fixes drawn as a line. Knowing which fixes arrived late is the difference between reading it and misreading it.

1. 1

   Every point has two times: when it happened on the unit, and when it reached us. They differ after a dead zone.

   An alert at 14:32 about something that happened at 14:10 is a backfill, not a slow system.

2. 2

   Dashed stretches were buffered and backfilled. The route is real; it was just late.

3. 3

   Speed comes from the satellite fix, not the speedometer, so short spikes near tall buildings are filtered before they become events.

4. 4

   Tap the ignition lane to see where the engine was running while stopped. That is where the idling money is.

Most fuel alerts are not theft. The point of an investigation is to find out quickly which ones are, without accusing anyone of the rest.

1. 1

   Open the tank trace around the alert: was the engine off, and was the vehicle stationary?

   A drop while driving is consumption or a sensor. A drop with the engine off and the vehicle still is the one to look at.

2. 2

   Check for a refuel receipt or fuel card transaction within the hour.

3. 3

   Look at where it happened. A depot or a known site is a question for a supervisor; a lay-by at 03:00 is a different conversation.

4. 4

   Compare with the same vehicle's last month. One drop is an event; a weekly pattern is a habit.

5. 5

   Write down what you found, including 'nothing'. The next alert on this vehicle is judged against it.

Every event already has a clip: 12 seconds before and 8 after, from both cameras. Anything else comes off the card in the vehicle, and only while it is still there.

1. 1

   Start from the event in the incident centre, not from the vehicle.

   The clip, the speed trace and the driver's statement are already attached there.

2. 2

   Need more? Request a longer window from the card. State the reason — it is logged.

3. 3

   Do it today. The card overwrites the oldest footage first, and a double-shifted vehicle overwrites faster.

4. 4

   Export the incident file as one document for the insurer rather than sending clips separately.

Essential allows 5 scheduled reports. The limit is a feature: a report nobody acts on is a report teaching people to ignore reports.

1. 1

   Start from a decision, not a dataset: who will do what when this arrives?

2. 2

   Address it to one person. A report sent to a group is read by nobody in particular.

3. 3

   Report exceptions — the six vehicles that idled over an hour — not the hundred that did not.

4. 4

   Set it to skip sending when there is nothing to report, so an empty inbox means good news.

Registration links each vehicle and its unit to your operator record. We submit it during onboarding; this is what has to be true for it to go through, and to stay valid for its 12 months.

1. 1

   Confirm every vehicle's operating card is current before fitting.

   An expired card fails registration even when every other field is right — it is the most common rejection we see.

2. 2

   Check plates and chassis numbers on the list match the vehicle registration exactly, including spacing.

3. 3

   Once units are fitted, we submit and confirm each link is active before handing the account over.

4. 4

   Link each driver as well. The driver associated with the operator. A new hire driving before this is done is a common and avoidable gap.

5. 5

   Watch for silent units. A unit that stops transmitting is a registration quietly lapsing.

Regulator exports are on Professional and Command, not Essential. The export is formatted for what is asked for; the work is making sure the underlying records are complete first.

1. 1

   Run the completeness check for the period: vehicles with no trips, trips with no driver, units silent for more than a day.

2. 2

   Resolve or annotate each gap. An explained gap is a note; an unexplained one is a question you will be asked.

3. 3

   Generate the export for the exact period requested, and keep the file we produce rather than an edited copy.

What we keep, for how long, and how you get it back.

1. 1

   Live: Positions on the map within seconds of arriving.

2. 2

   90 days: Full-resolution replay, every fix, instant to load.

3. 3

   6 years: Complete trip history retained, no thinning.

4. 4

   Any time: Export the lot as CSV or Parquet to your own bucket.

5. 5

   Deletion on request removes a driver's personal data and leaves anonymised trips, so your mileage history still adds up.

Vehicles added during a year are pro-rated to your renewal date, and if they push you into a lower band the new rate applies to the whole fleet from that renewal. We do not wait for you to notice and ask.

1. 1

   Add the vehicle and book its fitting in the same step; the subscription starts when the unit first reports, not when the vehicle is added.

2. 2

   If it needs registering, the compliance register opens a task for it automatically.

3. 3

   Assign a driver before its first trip, for the reason the adding-vehicles guide explains.

The API is read-only on Essential and Professional and full on Command. Keys are per integration, not per person.

1. 1

   Create a key under Integrations, name it after the system that will use it, and choose read or write.

2. 2

   Send it as a bearer token to https://api.nml.sa/fleet/v1. Keys never go in a URL.

3. 3

   Stay inside 600 requests a minute per key. Page with the cursor, 1,000 rows at a time, rather than asking per vehicle.

4. 4

   Rotate by creating a second key, switching over, then revoking the first. There is no downtime in that order.

Every delivery is signed with your endpoint's secret. Checking it takes a dozen lines and stops anyone posting fake events at you.

1. 1

   Read the raw body before any JSON parsing. The signature is over the exact bytes.

2. 2

   Reject timestamps more than five minutes old, so a captured request cannot be replayed later.

3. 3

   Compute HMAC-SHA256 of the timestamp and body, and compare in constant time.

4. 4

   Store event ids and ignore repeats. Deliveries are at least once, and replayable for 72 hours.

A night's data as files in storage you own, on Command. The cheapest way to feed a warehouse, and the only one that cannot fall behind.

1. 1

   Create a bucket and a write-only credential scoped to one prefix. We never need to read or delete.

2. 2

   Choose CSV or Parquet. Parquet is a fraction of the size and keeps types.

3. 3

   Files land by date. A failed night is re-sent the next night alongside the new one, never merged into it.

4. 4

   Load by recorded time, not arrival, so backfilled positions fall into the right day.

Most fleets move over months, not a weekend. What carries over from the units you already have is uneven, so plan per signal, not per vehicle.

1. 1

   Position — usually. Every protocol we read carries a fix, a time and a speed. This part simply works.

2. 2

   Ignition — usually. If the previous fitter wired it. Some inferred it from movement instead, which shows in the first day of data.

3. 3

   Driver identity — usually. Comes from the driver app, not the box, so the old unit does not matter.

4. 4

   Accelerometer — sometimes. Most old units report harsh events, at their own thresholds. Their scores are kept in a separate league, not ranked against ours.

5. 5

   Engine bus — sometimes. Only if the old unit decoded it and forwards it. Fault codes survive more often than fuel level.

6. 6

   Temperature — sometimes. Readings come through. Which probe sits in which compartment has to be rebuilt by hand.

7. 7

   Fuel probe — rarely. The probe survives. Its calibration table usually does not, so budget a fill.

8. 8

   Camera — never. Video formats are closed, and we will not claim to read another maker's footage.

9. 9

   Export your old provider's history before the contract ends. We can import it, but only if you still have it.