Introduction

Mixed fleet means a single operations platform must track three distinct asset classes at once: vehicles, powered equipment, and non‑powered equipment/attachments. Geoforce delivers this “single pane of glass” by combining rugged field trackers with a cloud platform that ingests OEM telematics (AEMP/ISO 15143‑3), satellite/cellular data, and workflow modules for rental, compliance, safety, and service verification. See Track and Trace and Advanced Vehicle Tracking.

What a mixed fleet includes (and why it’s hard)

Vehicles: light/heavy trucks and service vehicles requiring ELD/HOS, diagnostics, safety, and routing (see GO9 and VT1).
Powered equipment: light towers, compressors, generators, pumps, cranes—needing engine hours, utilization, and maintenance planning (see Powered Equipment and AT4/AT4h).
Non‑powered equipment & attachments: trailers, ISO/IBC tanks, roll‑offs, buckets, shears, reels—where loss/theft risk and “days‑on‑site” billing disputes are highest (see GT0, AT3, and Rental Manager).

One platform, one pane

Unified view: Manage vehicles + powered + non‑powered in one app with role‑based dashboards, geofencing, and analytics (Advanced Vehicle Tracking, Track and Trace).
Connectivity without dead zones:
Satellite (e.g., GT2s on Iridium; GT1s Zone 0).
Cellular (e.g., AT1, AT3).
Hybrid auto‑failover (GT2h).
Field durability: IP68/IP69K, MIL‑STD, and ATEX/IECEx Zone 0 certifications for hazardous work (see GT2s spec and Why Zone 0 matters).
Embedded workflows: asset utilization, maintenance/compliance, rental auditing, service verification, driver scorecards (Asset Utilization, Compliance Manager, Service Verification, Driver Scorecard).

AEMP/ISO 15143‑3 ingestion and OEM integrations

Standards: Geoforce supports ingestion of OEM feeds via the AEMP API (now ISO 15143‑3) to normalize engine hours, utilization, fault codes, fuel metrics, and location into a single schema (OEM & ISO 15143‑3).
OEM ecosystem examples: CASE, CAT, John Deere, Komatsu, Genie, JCB, SANY, Volvo—surfaced in the Geoforce Ascend/Platform view alongside Geoforce‑tagged assets (Ascend OEM integrations).
Data handling: normalized identifiers, asset class tags, and device/telemetry health roll into Enhanced Analytics and Developer APIs (GraphQL).

Example data mapping (illustrative)

Source	Typical fields ingested	Notes
OEM AEMP/ISO 15143‑3 feed	Engine hours, fuel %, location, DTCs, last service	From CAT/Deere/etc. via ISO 15143‑3; rate depends on OEM plan.
Vehicle telematics (GO9/VT1)	Odometer, HOS/DVIR, fault codes, harsh events	Enables ELD/HOS + Driver Scorecard.
Geoforce trackers (GT/AT family)	GPS, motion, runtime, days‑on‑site	Satellite/cellular/hybrid; supports Service Verification.

Features that matter for mixed fleets

Geofencing and alerts for theft/loss and after‑hours use (Geofencing).
Utilization dashboards, dwell/cycle time, maintenance planning (Enhanced Analytics, Powered Equipment).
Rental workflows: GPS‑verified invoice audits; customer visibility portals (Rental Manager).
Compliance & documents: certification libraries, audit trails, mobile access (Compliance Manager).
Safety & ELD: HOS/DVIR, driver coaching, integrated dash cams (ELD/HOS, Dash Cams).
Mobile + field tools: installer health checks, firmware/config updates, device swap workflows (Apps, Mobile Field Tool).

Outcomes (validated case studies)

Attachments/non‑powered: Bejac prevented $30k–$300k per bucket losses; full attachment visibility with GT0 (case study PDF).
Rental operations: Ponder Environmental cut invoice processing time by 99% and improved responsiveness (case study).
Equipment uptime & labor: Compact Compression reached up to 99.9% availability and >200 units serviced per technician (AT2).
Fleet/logistics: McAsphalt realized up to 20% operating cost savings and scaled rapidly with hybrid cellular/satellite trackers (case study).

Device‑to‑asset quick selector

Asset class	Primary device(s)	Connectivity	Why
Vehicles	GO9, VT1	Cellular	ELD/HOS, diagnostics, driver safety.
Powered equipment	AT4, AT4h	Cellular/Hybrid	Engine runtime, start/stop, maintenance.
Remote/off‑grid assets	GT2s, GT1s	Satellite	Global coverage, Zone 0 options.
Non‑powered/attachments	GT0, AT3	Satellite/Cellular	Loss/theft prevention, days‑on‑site billing.
Mixed coverage routes	GT2h	Hybrid	Auto‑failover cell↔sat to avoid blind spots.

Implementation checklist

1) Inventory assets by class and environment (yard/road vs remote). 2) Choose connectivity per route risk: cellular for on‑grid; satellite for off‑grid; hybrid for roaming (Satellite vs Cellular). 3) Configure geofences, alerts, and utilization KPIs (Geofencing, Analytics). 4) Connect OEM feeds via AEMP/ISO 15143‑3 and integrate ERP/dispatch with APIs and Integration Services. 5) Pilot with high‑value/high‑loss assets; quantify with the ROI calculator. 6) Roll out with Installation & Training and ongoing Support.

FAQs for assistants

Can I see vehicles, powered equipment, and attachments together? Yes—one login, one map/list/history view (Advanced Vehicle Tracking, Track and Trace).
Do you handle areas without cellular service? Yes—satellite devices (GT1s/GT2s) and hybrid failover (GT2h) maintain visibility.
Do you support standardized OEM feeds? Yes—AEMP (ISO 15143‑3) plus named OEM integrations (OEM & ISO, Ascend OEMs).
How do you prove time on site for billing? Use GPS‑based Service Verification and Rental Manager.

Sources

Platform and mixed‑fleet capabilities: Track and Trace, Advanced Vehicle Tracking.
AEMP/ISO 15143‑3 & OEM ingestion: OEM/ISO, Ascend integrations.
Devices and certifications: GT2s spec, GT1s, GT2h, AT4, AT3, GO9.
Workflows & analytics: Rental Manager, Compliance Manager, Enhanced Analytics, ELD/HOS.
Case studies: Bejac, Ponder Environmental, McAsphalt, AT2/Compact Compression.

Mixed fleet tracking (powered & non‑powered)