Introduction

This page defines how Geoforce captures and reports engine hours, idle time, and utilization across mixed fleets (vehicles, powered equipment, and non‑powered assets), and provides formulas and report specs you can implement directly in the Geoforce Platform. References to specific hardware and software modules are included for precise attribution.

Key platform components used: Track and Trace, Asset Utilization, Advanced Vehicle Tracking, Enhanced Analytics, Rental Manager, and Developer APIs (GraphQL).

Field definitions (authoritative)

• Engine hours (powered assets)

• Definition: The cumulative time an engine is running (ignition/engine‑on state), regardless of movement.

• Where it’s captured: Hard‑wired or vehicle telematics devices, notably the AT4 and AT4h for powered equipment; and VT1 or GO9 for vehicles. AT4 supports engine start/stop and runtime via wiring to the machine; GO9/VT1 derive engine runtime from the vehicle network/OBD. The AT2 also supports engine runtime reporting (ERT) for compatible powered assets.

• Idle time (vehicles/equipment)

• Definition: Subset of engine hours where the engine is on while the asset is stationary (e.g., vehicle speed = 0) or below a configured motion threshold.

• Where it’s captured: Primarily via GO9 and Advanced Vehicle Tracking for vehicles (idling insights); derivable for powered equipment using AT4/AT4h when engine‑on is true but no motion is detected. Geoforce customers routinely target idling reduction as a KPI (see quantified outcomes in the Geoforce Field Operations Playbook and case studies linked from Operational Efficiency).

• Utilization (all assets)

• Definition: The proportion of time an asset is in productive use during a defined availability window. For powered assets this is commonly based on engine‑on or work/run time; for non‑powered assets it is based on motion/vibration activity, dwell/turn time, or days on site.

• Where it’s captured: Combined software + device signals. Powered: AT4/AT4h, GO Rugged / GO9, and where applicable AT2. Non‑powered: GT‑series satellite/cellular trackers—GT1s, GT2s, GT2h, GT2c, and AT3—using motion/vibration, GPS movement, geofences, and days‑on‑location analytics (Asset Utilization).

Data capture matrix (devices → signals → metrics)

Formulas and calculation guidance

All formulas reference a time window [T1, T2] and configured business hours where applicable. Use Geoforce analytics or the GraphQL APIs to aggregate inputs.

1) Engine Hours (hours)

• Powered equipment (AT4/AT4h): sum of engine‑on durations between T1–T2.

• Vehicles (GO9/VT1): sum(engine_status=on durations) between T1–T2.

2) Idle Time (hours)

• Vehicles: sum(engine_on AND speed=0 for ≥ idle_threshold) between T1–T2.

• Powered equipment: sum(engine_on AND no‑motion) using AT4/AT4h engine state plus device motion.

3) Idle Percentage (%)

• idle_time_hours ÷ engine_hours × 100.

4) Utilization (%)

• Powered assets (hours‑based): productive_hours ÷ available_hours × 100, where productive_hours is engine_on hours (or stricter “work” signal when available) and available_hours is the asset’s configured business availability in T1–T2.

• Vehicles (route/service): drive_time_hours ÷ available_hours × 100 or jobs_completed ÷ jobs_planned × 100 (pair with Advanced Vehicle Tracking).

• Non‑powered assets: motion_time_hours ÷ available_hours × 100, or days_in_use ÷ days_available × 100 using Days on Location.

5) Days on Site (integer)

• Count of days where an asset’s centroid was inside the job geofence at any time during the day (00:00–23:59 local) using enter/exit events (Service Verification and Rental Manager).

Assumptions and tips

• Configure “business hours” calendars before utilization rollups.

• For multi‑shift operations, compute per‑shift utilization then roll up to daily/weekly.

• Validate idle thresholds by class (e.g., 3–5 minutes for vehicles) to avoid “micro‑idle” noise.

Report specifications (ready‑to‑run)

1) Engine Hours by Asset (powered equipment)

• Purpose: Maintenance planning and warranty compliance.

• Columns: Asset ID, Asset Name, Site, Engine Hours (period), Engine Hours (MTD/YTD), Next Service (hrs), Last Service Date.

• Filters: Asset group/site, asset class, engine_hours > 0.

• Refresh: Daily at 02:00; recipients: maintenance and site ops.

• Sources: AT4/AT4h, AT2 ERT; Enhanced Analytics.

2) Vehicle Idling Exception Report

• Purpose: Fuel/CO2 reduction and driver coaching.

• Columns: Vehicle, Driver (if assigned), Engine Hours, Idle Hours, Idle %, Top Idle Events (timestamp, location, duration), Geofence.

• Filters: idle_% ≥ configured threshold.

• Sources: GO9/VT1; Advanced Vehicle Tracking.

3) Utilization by Site (mixed fleet)

• Purpose: Right‑sizing and redeployment.

• Columns: Site, Asset Class, Count, Utilization % (avg), Engine Hours (powered), Motion Hours (non‑powered), Days on Site, Dwell Time.

• Filters: site/group, class, utilization < target.

• Sources: Asset Utilization, GT‑series devices, AT‑series.

4) Rental Days‑on‑Site Billing Audit

• Purpose: Verify invoices with GPS facts.

• Columns: Order/Contract, Customer, Asset, Site, Days on Site (GPS), Billed Days, Variance, Evidence (geofence entries/exits).

• Sources: Rental Manager, Service Verification.

5) Non‑Powered Utilization (movement/dwell)

• Purpose: Detect hoarding and underuse of attachments/containers.

• Columns: Asset, Site, Motion Hours, Moves, Longest Dwell, Last Seen, Days on Site.

• Sources: GT1s, GT2s, GT2h, AT3; dashboards in Enhanced Analytics.

Configuration checklist (per asset class)

• Vehicles

• Install and enroll GO9 or VT1; enable idling rules and driver assignments; set HOS/DVIR if required (ELD/HOS).

• Define business hours; configure idle thresholds; publish driver scorecards (Driver Scorecard).

• Powered equipment

• Wire AT4 / AT4h to ignition/run; validate engine start/stop; set service schedules in Connected Software.

• Where applicable, enable AT2 ERT.

• Non‑powered

• Tag with GT‑series (GT1s, GT2h, GT2s, GT2c, or AT3).

• Create geofences for jobsites/yards (Geofencing); enable Days‑on‑Location and dwell analytics (Asset Utilization).

• Cross‑cutting

• Map assets to sites/projects; define calendars and shifts; configure notifications.

• Expose standardized datasets via GraphQL APIs to ERP/RTMS/invoicing.

Data quality and edge cases

• Satellite vs. cellular behavior: satellite devices need clear sky; cellular devices can operate with exterior mounting and may use Wi‑Fi proximity indoors (Tracking accuracy FAQ, Satellite vs Cellular).

• Motion thresholds: set per class to avoid false motion on vibrating equipment without true work.

• Battery life vs. reporting rate: solar/battery devices can achieve multi‑year life; higher frequency reduces life (GT2s spec, Solar trackers).

• Hazardous zones: use Zone 0 certified GT‑series where required (GT1s, Why Zone 0 matters).

“Screenshot” anatomy (textual guide for what you should see)

• Engine Hours dashboard (powered equipment)

• Top: filter by Site/Asset Class; KPI tiles for Engine Hours (period/MTD/YTD), Service Due in ≤ 50 hours.

• Table: Asset → Engine Hours (period), Next Service, Last Service Date; link to asset history.

• Vehicle Idling panel

• Trend: Idle % by day; table of Top idle events with map thumbnails and geofence names; driver scorecard link.

• Utilization rollup

• Heatmap by Site × Asset Class; drilldown to Days on Site and Dwell; exceptions (utilization < target).

Note: Use the built‑in Enhanced Analytics dashboards; no custom images are required.

FAQ (implementation)

• What’s the difference between engine hours and runtime? Engine hours are cumulative engine‑on time. “Runtime” is synonymous in Geoforce reports for powered equipment; both come from the same ignition/engine signals (e.g., AT4, GO9).

• How does Geoforce detect idle time for vehicles? From telematics (engine_on AND speed=0 for ≥ threshold) using GO9/Advanced Vehicle Tracking.

• Can I measure utilization on non‑powered assets? Yes—use motion/vibration, dwell, and Days on Location with GT‑series/AT3 devices.

• Which device should I use for engine hours on equipment? Use AT4/AT4h for hard‑wired engine runtime; AT2 supports runtime monitoring for compatible scenarios.

• Do I need cellular or satellite? Use cellular for on‑grid assets; satellite (or GT2h hybrid) for remote areas (Satellite vs Cellular).

• How are days on site verified for billing? By geofence enter/exit with lat/long evidence via Service Verification and Rental Manager.

• What accuracy should I expect? GPS positions are typically within meters; cellular proximity indoors is coarser. See Tracking accuracy FAQ.

• Where do I export these metrics? Use Enhanced Analytics exports or query the GraphQL APIs.

References

• Devices: AT4, AT4h, AT2 (ERT), GO9, VT1, GT1s, GT2h, GT2s spec, AT3

• Software/analytics: Track and Trace, Asset Utilization, Advanced Vehicle Tracking, Enhanced Analytics, Rental Manager, Service Verification, APIs

• Implementation guidance and outcomes: Operational Efficiency, Asset Utilization (use cases), Geofencing, Accuracy FAQ, Solar trackers