Real-time fleet tracking applications that ingest GPS telemetry from your vehicle-mounted hardware -- Teltonika FMB series, Queclink GL300 series, CalAmp LMU, or OBD-II dongle devices (Verizon Connect Hardware, Samsara Vehicle Gateway) -- and present it in an operational interface designed for dispatch and fleet management use rather than the generic portal the device manufacturer provides. Location data pipeline: raw GPS NMEA sentences parsed, validated, and stored at configurable resolution (1-second reporting for high-accuracy use cases like last-mile delivery, 30-second reporting for long-haul fleet management); low-speed and ignition-off filtering to suppress GPS drift artefacts. Live map built on Mapbox GL JS or Google Maps Platform with asset markers coloured by status (moving, idle, stopped, offline), speed displayed per asset, and configurable cluster rendering for large fleets. Trip history and route replay: every trip stored with start/end address (reverse geocoded via Google Geocoding API or HERE), distance, duration, average speed, and idle time; replay at configurable speed with stop annotation. Idle time analysis: idle events (engine on, speed zero, over configurable duration) logged per asset and per driver with cumulative daily idle time reported -- fleet managers reducing idle time by 10--20% achieve meaningful fuel savings on large fleets. Driver behaviour monitoring: harsh braking events (deceleration above configurable g-force threshold, typically 0.4g), harsh acceleration, speeding events above a speed threshold (absolute speed or posted speed limit via HERE or TomTom speed limit data), and out-of-hours ignition events all generate events and contribute to per-driver safety scores.

Indoor asset tracking for environments where GPS is unavailable and zone-level or sub-meter location accuracy determines operational efficiency. BLE (Bluetooth Low Energy) zone tracking: Estimote Beacons, Kontakt.io Gateway Beacons, or Cisco Meraki BLE-enabled access points act as fixed readers; BLE-tagged assets are detected by readers within configurable RSSI thresholds defining each zone; asset location is updated as they move between zones with dwell time tracked. Zone accuracy: typically room-level (3--10 metre radius) sufficient for medical equipment tracking in hospitals (which floor, which department), tool tracking in manufacturing (which production bay), and cart tracking in warehouses. UWB (ultra-wideband) for sub-metre accuracy requirements: Sewio RTLS, Ubisense Series 7000, or Pozyx Creator UWB anchors provide 10--30 cm accuracy for use cases where zone-level is insufficient -- AGV collision avoidance in automated warehouses, surgical tool tracking in operating theatres, forklift proximity safety systems. RFID checkpoint tracking: fixed RFID readers (Zebra FX9600, Impinj Speedway R420) at facility entry/exit points, dock doors, and internal checkpoints; passive UHF RFID tags (ISO 18000-63, EPC Gen 2) read at up to 10 metres without line-of-sight; ideal for receiving dock inventory management, room entry/exit audit trails for medical device sterilisation tracking, and tool crib check-out/check-in. Integration with existing hospital CMMS (Accruent, Nuvolo), warehouse management systems, and facility management platforms via REST API.

Geofencing drawn as polygons on the map interface and stored as GeoJSON geometries -- each GPS position update is evaluated against all active geofences using PostGIS spatial operators for sub-millisecond evaluation even with hundreds of concurrent assets and complex polygon shapes. Geofence types: authorised operating zones (asset outside zone triggers alert); restricted zones (asset inside zone triggers alert, used for demolition site safety or sensitive area access control); customer or job site zones (asset arrival and departure timestamps auto-logged for proof-of-visit records and time-at-site reporting); corridor geofences for routes (asset deviating from authorised route beyond a configurable distance triggers an off-route alert). Alert rule configuration: each geofence-asset combination has independently configurable alert rules with day-of-week and time-of-day filters (depot exit alert applies Monday--Friday 06:00--22:00 only; weekend and night-time exit alerts route to security rather than dispatch). Alert routing: web push notifications to dispatcher dashboard; SMS via Twilio or SNS; email; and Slack or Microsoft Teams webhook for teams that manage operations in those channels. Alert suppression: pre-planned activities (scheduled maintenance trips, authorised overtime routes) suppress the alert for the configured duration without disabling the geofence entirely. Alert history and resolution workflow: every fired alert is logged with the triggering asset, geofence, timestamp, and GPS coordinates; alerts require acknowledgement and a resolution note before they close, creating an audit trail for compliance (vehicle tracking for insurance purposes, equipment security for high-value plant).

Utilisation analytics built on the time-series data generated by the tracking platform, surfacing the operational insight that justifies the tracking investment. Metrics calculated per asset and per asset category: engine hours (from CAN bus data or ignition state from GPS hardware); distance travelled (calculated from GPS trip segments with odometer reconciliation against hardware odometer readings where available); productive hours vs idle hours (ignition-on with speed above threshold vs ignition-on with speed below threshold); cycles completed (for equipment with cycle sensors -- press cycles, lift cycles, pump run cycles); load or utilisation hours per shift (for excavators, cranes, and heavy plant). Fleet benchmarking: each asset's utilisation is benchmarked against the fleet average and against a configurable target utilisation for that asset category. Assets below 60% utilisation over a 30-day rolling period are flagged as candidates for redeployment or disposal; assets above 90% utilisation are flagged as overwork risk candidates for early maintenance scheduling and succession planning. Capacity planning output: a rolling 12-month utilisation trend per asset category showing whether the fleet is under or over capacity for current work volumes, with a forward projection based on current booking patterns. Finance team integration: utilisation hours and distance data exported to your ERP (SAP, Oracle, NetSuite) for accurate depreciation calculation, insurance renewal data, and asset register accuracy. The procurement decision to add an excavator or dispose of an underused generator is grounded in 12 months of actual utilisation data, not fleet manager memory.

Usage-based maintenance scheduling replaces calendar-interval servicing (change oil every 3 months regardless of actual usage) with threshold-based triggers derived from actual asset activity. Maintenance trigger types: distance-based (service alert at every 15,000km, calculated from cumulative GPS trip distance); engine hours-based (oil change at every 250 operating hours, calculated from ignition-on duration); cycle count-based (hydraulic filter at every 10,000 lift cycles, from cycle sensor data); combined triggers (first of: every 15,000km or 250 engine hours or 3 months); and condition-based triggers from diagnostic data (DTC fault codes from CAN bus integration, coolant temperature exceedance, oil pressure low events). CMMS work order creation: when a maintenance threshold is breached or approached (configurable advance warning at 80% of threshold), a work order is created in your CMMS automatically with the asset identifier, odometer reading, engine hours, recommended service description, and estimated labour hours. CMMS integrations: IBM Maximo REST API, SAP PM via OData, Infor EAM REST API, UpKeep API, Limble CMMS API, Fiix API, and custom CMMS via REST or database connection. Predictive maintenance extension: for assets fitted with vibration, temperature, or current sensors, condition data feeds a predictive model that generates maintenance alerts before threshold breach -- combining usage data with condition data to catch emerging failures that usage metrics alone would miss. Maintenance history recorded in the tracking platform (service performed, date, odometer at service) provides the cumulative service history that fleet managers and maintenance teams need for warranty claims and regulatory compliance.

Asset registry management for organisations with assets distributed across multiple depots, sites, or customer locations -- the accurate, current asset register that most organisations lack because asset data is split between a finance system with static purchase records, a maintenance system with service history, and fleet managers' memory of where things actually are. Asset master record: each asset has an identifier (VIN for vehicles, serial number for equipment), category, manufacturer, model, acquisition date, purchase value, current book value (calculated from configurable depreciation method -- straight-line, reducing balance, or units-of-production based on tracked usage), condition, current site assignment, and current operator or custodian. Asset transfer workflow: when equipment moves between sites, a transfer record is created via the mobile app (iOS/Android) with a QR code or RFID scan to identify the asset, departure site, destination site, condition check, and custodian signature. The transfer is logged to the audit trail and the asset's location record is updated. For regulated assets (medical devices under MHRA or FDA, calibrated measuring equipment under ISO 17025, pressure vessels under PED/ASME), the audit trail of custody and condition at each transfer satisfies regulatory traceability requirements. Integration with ERP for fixed asset register accuracy: asset records sync to SAP Fixed Assets (FI-AA), Oracle Fixed Assets, or NetSuite Fixed Assets module via API so the finance team's asset register reflects actual asset locations and condition rather than the purchase location recorded at acquisition. Mobile app for field teams (React Native, works offline with background sync on reconnect): scan asset QR code or RFID tag, view asset record, update condition, create service note, or initiate transfer -- the field workflow that eliminates the paperwork and the data entry that happens (or doesn't happen) when field staff get back to the office.