Geoforce helps teams understand where assets are, whether they’re being used, and how consistently they’re available—across mixed fleets that include powered equipment, vehicles, trailers, containers, tools, and other non-powered assets.

This page explains the practical building blocks behind utilization measurement in the Geoforce ecosystem (rugged GPS tracking hardware with cellular, satellite, or hybrid connectivity plus the Track and Trace platform), and how operations teams turn utilization data into day-to-day decisions.

What “utilization” means in mixed fleets

“Utilization” is not a single universal metric. In practice, teams track multiple utilization KPIs that answer different questions:

• Time-in-use: How much time (or how many engine hours) the asset is actively working.

• Time-on-site: How much time the asset is present at a jobsite, yard, or other operational location.

• Availability: How much time the asset is ready to be dispatched (not down for maintenance, not lost, not otherwise out of service).

Geoforce supports these concepts by combining location history with events (motion, geofence enter/exit) and, where available, telematics such as engine hours and idle time.

Core data sources used to measure utilization

Utilization measurements are typically derived from a combination of the following signals (the exact mix depends on the asset type, tracker model, configuration, and connectivity):

1) GPS location pings

Trackers periodically send position updates (“pings”). From those points, the platform can derive:

• Dwell time at a location

• Trips / movement segments

• Time inside/outside a geofence

2) Motion detection

For many non-powered assets (and some powered use cases), motion is a practical proxy for “in use.” Motion signals can be used to calculate:

• Motion minutes/hours per day

• Days moved vs. days idle

• Last moved time (useful for locating “stranded” or forgotten assets)

3) Geofences (job sites, yards, depots, customer locations)

Geofences convert raw location into operational context:

• Time-on-site (asset is within a defined area)

• Turnaround time (how long assets stay at a customer site)

• Utilization by site (which jobs are consuming capacity)

4) Engine hours and idle time (where available)

For vehicles and powered equipment, utilization can be tied to operating signals such as:

• Engine hours (run time)

• Idle time (engine on, not moving/working—definition depends on configuration)

These signals are often used for maintenance planning and for distinguishing “present at the site” from “actually operating.”

How utilization is measured for powered vs. non-powered assets

Different asset categories often require different measurement methods.

Powered assets (vehicles and powered equipment)

Common utilization approaches for powered assets include:

• Engine-hours-based utilization

• Best for: equipment where run time closely tracks productive work.

• Example KPI: Engine hours per shift / per day / per week.

• Motion/trip-based utilization

• Best for: fleets where movement is a proxy for work (service vehicles, transport equipment).

• Example KPI: Moving time, number of trips, or distance.

• Geofence-based time-on-site

• Best for: tracking how long an asset is allocated to a jobsite regardless of whether it is running.

Because idle time can represent cost without output, some teams track productive ratio using a combination of signals:

• Example: Productive % \= (Engine hours − Idle hours) / Engine hours

Non-powered assets (trailers, containers, tools, bins, generators when not wired for engine data)

Non-powered assets typically do not provide engine data. Utilization commonly uses:

• Motion as “in use” (movement indicates handling, repositioning, active deployment)

• Geofence presence as “on site” (asset is staged at the job)

• Last-seen / last-moved recency (to identify underused or missing assets)

A practical pattern is to define “utilized” as any motion during a reporting window and then track:

• Utilized days / total days

• Average days between moves

• Time in customer geofences (allocation / dwell)

Defining utilization KPIs (and keeping them comparable)

A consistent KPI definition matters more than the exact formula. Many teams create three layers of KPIs:

1) Availability (supply)

Goal: Understand how much capacity you truly have.

Common definition:

• Available time \= total time − planned downtime (maintenance) − out-of-service time

Availability often requires an operational status process (e.g., “In Service,” “Down for Maintenance,” “Retired,” “On Rent,” “On Hold”). Geoforce data can support the workflow, but teams usually define availability rules to match internal policies.

2) Time-on-site (allocation)

Goal: Understand where capacity is committed.

Common definition:

• Time-on-site \= time within a jobsite geofence during the reporting window

This KPI is especially useful for:

• identifying assets “stuck” at a location

• measuring customer/site cycle time

• separating allocated assets from free assets

3) Time-in-use (demand / productive work)

Goal: Understand actual usage.

Typical definitions by asset type:

• Powered assets: engine hours (and optionally motion/idle breakdown)

• Non-powered assets: motion time or “moved at least once” within the window

Putting it together: utilization rate

A commonly used roll-up is a utilization percentage that normalizes usage by availability:

• Utilization % \= (Time-in-use) / (Available time) × 100

If your organization cares about allocation efficiency, a second roll-up is:

• Allocation efficiency % \= (Time-in-use) / (Time-on-site) × 100

How teams operationalize utilization in Geoforce-driven workflows

Utilization data becomes valuable when it triggers decisions and closes loops.

Right-sizing (reduce surplus, prevent shortages)

Teams use utilization distributions (not just averages) to identify:

• chronically underused assets (candidates to reassign, sell, or avoid replacing)

• overused assets (risk of unplanned downtime; may indicate a need for additional units)

Operational pattern:

1. Segment utilization by asset class and region.

2. Identify the bottom and top utilization quartiles.

3. Validate with site context (geofences) and status (availability rules).

4. Adjust fleet plan (transfer, procurement, retirement).

Redeployments (move capacity to demand)

When an asset is idle in one yard but needed at another site, teams can use:

• last moved time

• time-on-site by geofence

• proximity to the next job

to prioritize redeployment moves and reduce “search time” for equipment.

Maintenance scheduling (use-based rather than calendar-based)

For powered assets, engine hours are often the backbone of maintenance intervals.

Typical process:

• Track engine hours accumulation per asset.

• Apply service thresholds (e.g., every N engine hours).

• Use utilization trends to forecast when each unit will reach the next threshold.

For non-powered assets, motion and time-on-site can still inform maintenance planning:

• assets that move frequently may need more frequent inspections

• assets that sit for long periods may need condition checks before redeployment

Rental invoice audits (verify billed days, location, and usage assumptions)

For rented or leased assets, teams commonly reconcile invoices against operational reality:

• Was the asset on the billed site during the billed period? (time-on-site)

• Did the asset move or show signs of use? (motion)

• For powered equipment, did run hours align with expectations? (engine hours/idle where available)

This approach supports conversations about standby charges, minimum-use clauses, and off-rent timing—without assuming that “on site” always equals “in use.”

Reporting and continuous improvement

Many organizations adopt a simple cadence:

• Daily/weekly: exception lists (never moved, long dwell, missing from site)

• Monthly: utilization by class/site/region; right-sizing recommendations

• Quarterly: policy updates (availability definitions, geofence standards, KPI targets)

Practical configuration tips (so the KPIs stay trusted)

• Standardize geofences: consistent naming, boundaries, and ownership (who maintains them).

• Document KPI definitions: write down the exact rules for time-in-use, time-on-site, and availability so different teams don’t compare mismatched numbers.

• Separate “allocation” from “work”: jobsite presence is not the same as productive use—track both.

• Validate against reality: spot-check a sample of assets with supervisors to ensure motion/engine-hour rules match field operations.

• Use segments: compare like-for-like assets (same class, same region, similar duty cycles).

FAQ

Does Geoforce measure utilization the same way for every asset?

No. Powered assets can often use engine hours and idle time (where available), while non-powered assets typically rely on GPS location history, motion events, and geofence-based time-on-site.

What is the difference between time-on-site and time-in-use?

• Time-on-site measures how long the asset is inside a defined location (like a jobsite geofence).

• Time-in-use measures evidence of work—commonly engine hours for powered assets or motion for non-powered assets.

Can I define utilization by shift, day, week, or billing period?

Yes. Utilization is typically calculated over a reporting window. Teams commonly track daily and weekly operational KPIs and then roll up to monthly or invoice periods.

How does GPS ping frequency affect utilization calculations?

Ping frequency influences the granularity of time-on-site and movement timelines. Higher frequency can produce finer detail, while lower frequency may be sufficient for long-dwell or wide-area monitoring. Teams usually choose settings based on operational needs, power budget, and connectivity.

What if an asset is in a low-coverage area?

Depending on the device and configuration (cellular, satellite, or hybrid connectivity), updates may be delayed or sent less frequently. Utilization reporting should account for gaps—many teams use geofences and longer reporting windows to reduce noise.

Can idle time be excluded from utilization?

Often yes, if idle time is available for the asset and your KPI definition treats idle as non-productive. A common approach is to report both engine hours and idle hours, and optionally a “productive” metric that subtracts idle from engine run time.

How do we handle assets that are shared across multiple sites?

Use geofences to attribute time-on-site by location, then report utilization by asset and by site. Some organizations also add operational status fields (e.g., assigned project) so utilization can be grouped by accountability.

Can utilization data help reduce rental costs?

It can support rental audits by showing whether an asset was on the billed site during the billed period and whether it showed signs of use (motion/engine hours where available). Final conclusions depend on your contract terms and how your organization defines “use.”

Can we export utilization data for BI tools?

Many teams operationalize utilization through reporting and analytics workflows, often exporting data to spreadsheets or BI tools for deeper cost and capacity analysis. The exact export and integration options depend on your Geoforce configuration.