Every vehicle
registered, fitted,
and reporting.
A vehicle isn't just a dot on the map. Each one carries a tracker and cameras under a single, verified identity — reporting position alongside battery, connection, ignition and tamper status, with maintenance readiness, in one continuous, court-ready record. Mounted, fully accountable — moving coverage over the ground you patrol.
FLEET BACKHAUL
UPLINK LEDGER · LIVE
One plate, one VIN, one verified identity
Each vehicle enters the fleet as its own governed asset — a VIN with checked provenance, a plate validated against South African formats, a recognised platform type, and branding evidence held on the same record. The split is deliberate: a motor-pool platform with no crew stays representable in its own right, never folded into the unit that operates it.
The plate is validated against South African per-province formats; VIN provenance — ownership history and vehicle detail — is checked before the platform goes on patrol
Each platform carries its own NSN identity, the recognised NATO supply number — a classification facet for browsing, a serial identity as the natural key, company part numbers in the same slot
Branding compliance is held as photographic evidence per vehicle — no police-resembling livery, no blue lights, only the permitted white security identification bar
Each platform is tagged Reality, Exercise or Simulation, and that context travels with it everywhere
REGISTERED PLATFORMS
PLATE FORMATS
NSN IDENTITY
BRANDING EVIDENCE
Position fixes that carry vehicle state
Each position fix can carry vehicle state beside lat / lon — battery charge, link type, ignition and jam — all optional, so nothing already in the field has to change. Ignition is the one CAN-adjacent signal carried today; the extended CAN fields — odometer, fuel, coolant, RPM — are on the roadmap, arriving alongside today’s signals once the bus tap lands. Beside the trail the platform surfaces its own vehicle-event subset: ignition and tamper.
Bad readings — out-of-range values, blank sensors, or a position with nothing attached — are rejected rather than trusted
SEE ALSO
Detections are de-duplicated and admitted in OSINT; the full device-event taxonomy and precedence in Force; crew man-down in Wearables.
TELEMETRY CHANNELS
VEHICLE EVENTS
IGNITION STATE
LOW-BATTERY
The link is never assumed
Backhaul spans every link a platform might find — cellular, LoRa mesh, satellite, NB-IoT. When a link degrades, traffic is held and delivered the moment the link returns, in order and exactly once. Every link is authenticated and encrypted end to end. This is the mounted platform's resilient connection to the rest of the picture — the same delivery assurance Sensors, Wearables and Drones ride on.
BACKHAUL MIX
DELIVERY
LINK SECURITY
INTEGRITY
One awaiting part flips the whole platform
Every part on a platform sits in exactly one of three states — installed, spare or awaiting — and a single awaiting line rolls the whole platform to not-mission-capable for supply. Readiness itself is commanded in GSORTS vocabulary — FMC, PMC, NMC — never inferred: fault codes and telemetry propose a state, an operator sets it. Before each shift, a readiness check gates patrol assignment the way credential checks gate officers.
FLEET PLATFORM
Patrol 4x4 — Response Fleet
NMC-S
ROLLED UP FROM PARTS
One awaiting part rolls up to flip the whole platform to not-mission-capable for supply — readiness you can watch propagate, not just a static label.
NSN PARTS · ONE OF THREE STATES
ALTERNATOR ASSY
SPOTLAMP ASSY
HUB REDUCTION
RUN-FLAT INSERT
CASCADE → NMC-S
A dead tracker is a liveness problem, never silently a readiness label — the two axes stay separate.
GATE → PATROL ASSIGNMENT
no pass, no patrol- 01
A part is always in exactly one of three states — installed, spare or awaiting — so the parts column reads as a definite bill of state, never free text.
- 02
One awaiting line drives the platform to not-mission-capable for supply automatically; installed and spare lines carry custody only.
- 03
Readiness is commanded in GSORTS vocabulary — FMC, PMC or NMC; fault codes and telemetry propose a state, never impose one.
- 04
A pre-shift readiness check — diagnostics, fuel, open faults, tracker health — gates patrol assignment the way credential checks gate officers.
FLEET PLATFORMS
PARTS TRACKED
AWAITING-DRIVEN NMC-S
PRE-SHIFT CHECKS
Coverage that moves with the patrol
Vehicles join patrol runs and response duty through the same conflict-checked assignment as officers — one unit, one window, no overlap slipping through — and a pre-shift readiness check gates the run the same way credentials gate the crew. Once the run is moving, the coverage geometry moves with it: mounted cones sweep each patrol leg while fixed rings hold the perimeter the route threads. When an incident opens, dispatch reads the same picture and pulls the nearest capable unit.
SEE ALSO
The camera, ANPR and perimeter modalities and their edge processing are detailed in Sensors; patrol planning, route generation and the run itself are owned by Force — the fleet supplies the moving coverage that carries them.
UNITS ON RUN
READY POOL
ASSIGNMENT CONFLICTS
DISPATCH
Select a platform, preview it live
The fleet console holds one roster and one live map — never two sources of truth. Selecting a platform on the left previews it on the right: posting, readiness and a telemetry read pulled from the same position fix the map already carries.
FLEET OPERATIONS · LIVE CONSOLE
Configure the platform, emit one symbol
Vehicles, parts and crew are fully editable — erasable on request, changeable a field at a time, with protected fields that cannot be silently altered. Operators tailor vehicle-type labels, watchlists and symbol context per platform. From that record the platform emits one thing the field can read: its symbol.
VEHICLE TYPE
SYMBOL CONTEXT
AFFILIATION
ECHELON
This platform emits a single 2525D glyph derived from its own record. The CoT egress that delivers it to the consuming tactical picture lives in Graph; the affiliation and echelon symbology model behind the glyph is owned by Force.
Deleting a vehicle also removes its crew and assignments — a genuine right-to-erasure
Watchlist hex / callsign entries are tunable per platform; the affiliation model they feed lives in Force
SIDC status is planned in Planning and present once Tracking — the symbol matures with the platform
VEHICLE TYPES
WATCHLIST
SYMBOL EGRESS
SIDC STATUS
Mount the platform, authenticate the sensor.
Stream it through any link that survives — see your fleet as the live, audit-traceable picture it already is. Talk to our team about a mounted-sensor-node walkthrough, a CAN and vehicle-health telemetry evaluation over your platforms, or a degraded-link backhaul trial across your motor pool.