Introduction:
The Tabular Report is the table view of your Load Cycle Analysis (LCA) data. It breaks each load cycle into rows and shows how long each asset spent at the source, traveling, and at the destination.
This article explains:
What the Tabular Report shows
How the key metrics are calculated
How overlapping or “messy” cycles are handled
What customers should expect (and not expect) when reviewing it
1. Where you’ll see the Tabular Report
You may encounter the Tabular Report in two main places:
Completed Shift LCA (standard LCA)
Shows cycles for a completed shift.
Includes shift information (Shift Name, Shift ID), cycle metrics, and tonnage (if scale data is integrated).
Can be exported as CSV or PDF.
Manual LCA
After running a Manual LCA for a chosen date range and geozones, you can open a Tabular Report of that result set.
The structure is the same as the standard Tabular Report, but:
It uses your manual time window instead of shift times.
Shift Name and Shift ID will be blank in CSV for Manual LCA, by design.
In both cases, the Tabular Report is your detailed, row‑by‑row explanation of what you see in the LCA graph.
2. What each row represents
Each row in the Tabular Report represents a cycle (or “stop”) for a specific asset. Cycles are generally defined as:
Source → Destination
For example, leaving a plant (source), traveling, then arriving at a job site (destination).
You’ll see one row per cycle, with columns that describe:
Which asset the row is for
Which geozones were involved
How long the asset spent at each part of the cycle
Additional indicators (e.g., stop‑moving icons, tonnage)
There are also scenarios where you may see “half cycles” (e.g., source to destination only, without a clear return to source), depending on how the shift is configured and how many geozone hits occurred. This is described in more detail in the cycle math section below.
3. Key columns and how the math works
Exact column sets can vary by configuration, but the core LCA Tabular Report typically includes:
3.1 Source Geozone
The Source Geozone is the origin point for the cycle.
It is usually the plant, pit, or yard where the truck starts the load cycle.
Technically:
The system looks at when the asset enters the source geozone.
That entry time is used as part of the cycle timing (see “Time in Source” and “Time to Destination” below).
For some CMMS shifts, special logic ensures that the first source entry is counted even when the truck starts the shift already inside the source geozone
3.2 Destination Geozone
The Destination Geozone is typically the job site or delivery location.
Your tickets show destination inference logic, especially for CMMS shifts:
If an asset does not clearly hit a destination geozone, the system uses inference rules to choose the best candidate.
3.3 Time in Source
What it means:
The amount of time the asset spent in the Source Geozone for that cycle.
How it’s calculated (conceptually):
Start = time the asset enters the source geozone for that cycle.
End = time the asset leaves the source geozone on that cycle.
Time in Source = End - Start (in minutes or hours, depending on display).
Special handling:
If a shift is converted to CMMS and the truck starts inside the source geozone, logic ensures that first in‑source period is counted correctly in the Tabular Report
When geozone “bounces” occur (asset briefly leaving and re‑entering), there is coalescing logic to prevent tiny out‑of‑zone windows from being treated as totally separate visits.
3.4 Time in Destination
What it means:
The amount of time the asset spent in the Destination Geozone.
How it’s calculated (conceptually):
Start = time the asset enters the destination geozone for that cycle.
End = time the asset leaves the destination geozone.
Time in Destination = End - Start.
As with Time in Source, coalescing logic can combine small in/out bounces to better reflect real “on‑job” time.
3.5 Time to Destination
What it means:
The time it takes the asset to travel from Source to Destination for that cycle.
Customers often think of this as the “haul” or “delivery” time.
How it’s calculated:
Start = the end of Time in Source (when the truck leaves the source geozone).
End = the entry time into the destination geozone.
Time to Destination = Destination Entry Time - Source Exit Time.
Asset is at Source from 8:36–8:41 AM.
Asset is at Destination from 8:40–8:42 AM (there is a 1‑minute overlap).
Naive math would treat the cycle like:
Source Exit: 8:41
Destination Entry: 8:40
8:40 − 8:41 = −1 minute (negative time)
Important behavior:
The Tabular Report will never show a negative Time to Destination.
If the timestamps overlap or otherwise result in a negative calculation, the system displays 0 instead.
This guards against confusing negative numbers when Source and Destination intervals overlap on the LCA graph.
4. How “messy” GPS and overlapping geozones are handled
Real‑world GPS data is noisy. Trucks may:
“Bounce” in and out of a geozone by a few seconds or meters.
See source and destination geozones overlap.
Start a shift already inside a geozone.
Your Tabular Report has several behaviors to keep the output usable and intuitive.
4.1 Coalescing geozone “bounces”
Problem: If a truck keeps dipping just outside a geozone boundary and back in, the system could think each dip is a new “travel” segment or a new cycle, cluttering the report.
Intention: Treat those short interruptions as part of a single stop.
So the Tabular Report:
Coalesces multiple short in/out movements into one continuous visit to that geozone when appropriate.
Uses geozone radius logic so that:
Slight GPS drift doesn’t look like the truck has truly left.
What customers should expect:
If a truck “wiggles” near the edge of a geozone, you should still see one row representing the full stop there, instead of many tiny stops.
4.2 Overlapping source and destination times
Source and Destination intervals can overlap when geozones overlap physically or when GPS transitions are imprecise.
In that case, the underlying math might produce a negative “Time to Destination.”
Tabular Report behavior:
If Destination Entry Time < Source Exit Time due to overlap:
Time to Destination is shown as 0.
Time in Source and Time in Destination are still shown based on their own entry/exit windows.
4.3 Starting the shift inside the source
When an asset starts the shift already inside the source:
That initial in‑source time is treated as the start of the first cycle, and is included in Time in Source / cycle calculations.
5. Stop‑moving indicator and stop maps
Some rows in the Tabular Report show a stop‑sign icon:
Clicking the stop sign opens a Stop Map with a breadcrumb trail for that stop.
What the stop‑moving time means:
The stop‑moving time is intended to represent time when the truck was not moving but the engine was on.
This can be longer than Time in Destination if:
The truck was stopped with engine on near the destination but not technically inside the destination geozone.
Or if there’s additional stopped time before entering / after leaving the geozone.
From the customer’s perspective:
They expected the stop‑moving time to be within the destination time.
However, the system may attribute stopped time based on engine/telemetry state and GPS, not strictly by geozone boundaries.
What customers should expect:
Stop‑moving time is not always bounded by Time in Destination.
If you see a larger stop‑moving value than Time in Dest, it likely includes stopped time just outside the geozone.
6. Shift name, CSV/PDF exports, and CMMS specifics
6.1 Shift information
For standard (MMS) and CMMS shifts, the Tabular Report exports now include:
Shift Name
Shift ID (where applicable)
This applies to:
On‑screen Tabular Report.
CSV export.
PDF export.
For Manual LCA:
Shift Name / ID in Tabular CSV are intentionally blank (FW-33498), because Manual LCA is not tied to a single formal shift.
6.2 CMS/CMMS shifts and destination inference
Converting a shift to CMMS (or CMS) triggers additional inference logic:
The system chooses a destination geozone even when the pattern is complex.
7. Tonnage and totals
The Tabular Report can show total tonnage for the shift when scale data is integrated.
Expected behavior:
Each row may show per‑cycle tonnage.
The report also includes total tonnage and load counts for the shift.
What customers should expect:
If your account has scale integration:
The Tabular Report helps reconcile the number of loads, tons per load, and total tons per shift.
If you don’t see tonnage in your Tabular Report, it usually means:
Scale data is not integrated for that shift/asset.
8. How cycles are defined (and why sometimes they look like “half cycles”)
The system calculates cycle start and end as:
Start: Entry into Source Geozone
End: Entry into Destination Geozone
This represents the delivery leg (source → destination), not necessarily:
Destination → back to source.
As noted:
“The cycle start and end times are calculated as the Start Time being the entry at the source geozone and the end time is the entry to the destination geozone. … this is only calculating half the cycle in the cycle details KPI.”
What customers should expect:
In many setups, a “cycle” in the Tabular Report is source → destination, not necessarily a full round trip back to source.
This means:
A KPI labeled “Cycle Time” (built off these same definitions) may show delivery time, not a complete round trip.
For full round‑trip analysis, you may need to:
Look at pairs of cycles, or
Use additional KPIs/reports configured for that purpose.
9. Summary: What customers should look for when reviewing the Tabular Report
When your customers look at the Tabular Report, here’s what they should expect:
Each row = one source → destination cycle
Asset, source geozone, destination geozone, and times per phase.
Time in Source / Time in Destination
Based on entry/exit timestamps.
Short GPS bounces in/out are usually merged into a single visit.
Time to Destination
Travel time between leaving source and entering destination.
Never negative; overlapping intervals are shown as 0.
Stop‑moving icons
Indicate time stopped with engine on.
Can extend beyond the formal destination time if the truck was stopped just outside the geozone.
Shift and tonnage info
Shift Name & ID included for standard/CMMS shifts in CSV/PDF.
Tonnage and load totals present when scale integration is enabled.
“Half‑cycle” appearance
By design, cycles are typically source arrival to destination arrival, not a full round trip.