The Four-Layer Analytics Model
Tobe Twin relies on a 4-layer analytics architecture to transform raw site telemetry into strategic operational intelligence. This model mirrors how teams process site information—moving from raw events to structured activities, performance metrics, and global portfolio optimization.
Layer | Layer Name | Description | Construction Example |
Level 1 | Individual Telemetry Records (Datums) | Atomic, high-frequency raw telemetry packets and onboard detected events. | A GPS coordinate ping, engine ignition status, or a speeding alert. |
Level 2 | Structured Behaviour (Workspans & Trips) | Groups Level 1 datums into meaningful, time-bounded operational activities. | A vehicle trip, continuous equipment workspan, or loader cycle. |
Level 3 | Aggregated Performance | Consolidated performance metrics for a specific asset or worker over a defined shift or timeframe. | Total asset idle time, operating runtime, or crew tool time percentage. |
Level 4 | Aggregated Insights | Strategic insights and optimization opportunities compiled across fleets, workfronts, or multi-project portfolios. | Portfolio-wide plant utilisation, fleet balance ratios, and total material moved. |
Level 1: Individual Data Records (Datums)
A Datum is a discrete telemetry record transmitted by connected IoT hardware (such as wired vehicle trackers, battery sensors, or BLE gateways).
Every datum contains:
Timestamp: Exact localized UTC/local timestamp.
Geographic Position: Precise 3D spatial coordinates (latitude, longitude, and elevation).
Onboard Event Code: Hardware-level events calculated by the device processor.
On the 3D map canvas and device timeline, these datums render as interactive markers (for example, purple icons for harsh braking or orange icons for hard cornering), allowing supervisors to inspect exact event locations.
Common Datum Event Types
IoT devices calculate specific operational events at the hardware level:
Event 1 (Start Trip): Ignition turned on or movement initiated.
Event 2 (End Trip): Ignition turned off or stationary threshold reached.
Event 3 (Elapsed Time): Periodic time-based heartbeat check.
Event 4 (Speed Change): Vehicle speed delta threshold exceeded.
Event 5 (Heading Change): Directional turn or heading shift detected.
Event 6 (Distance Travelled): Distance increment threshold met.
Event 11 (Heartbeat): Routine device status and battery health packet.
Event 12 (Harsh Braking): Deceleration threshold breach detected by accelerometer.
Event 13 (Harsh Acceleration): Rapid acceleration threshold breach detected.
Event 14 (Hard Cornering): Lateral g-force threshold breach detected.
Event 15 (External Power Change): Main power disconnected or restored.
Event 23 (Accident Detected): High-impact collision trigger.
Event 50 (BLE Tag Detection): Proximity detection of nearby BLE driver, worker, or tool tags.
Device Selection
You can select one device via clicking on its label or model in the 3D scene, or via selecting a row of the device timeline, or via its row in the device global menu.
You can also select multiple devices via SHIFT+click.
Deselect all devices by clicking anywhere else on the map within the 3D scene window.
Level 2: Structured Behaviour (Workspans)
Level 2 processing aggregates raw Level 1 datums into continuous, time-bounded periods of operational activity called Workspans.
Workspans are visualised as solid color-coded bars along the bottom Devices Timeline track and detailed within the Selection Inspector.
Automatic Workspan Generation & Zone Splitting
Activity Boundaries: Tobe Twin automatically defines a workspan from the start of activity (Event 1) to the end of activity (Event 2).
Work Area Splitting: When an asset travels across defined site zones, Tobe Twin automatically segments the trip into zone-specific workspans.
Zone Color Coding: Each workspan segment adopts the color assigned to the active work area (for example, magenta for main building zones or teal for laydown yards).
If a journey passes through multiple work areas, Tobe Twin splits the trip into individual workspan segments per area. For example, a mobile crane operating across a laydown area and an SSU area will display a multi-segmented workspan bar matching each area's color code.
Workspan Inspection & Total Journey Summaries
When inspecting workspans:
Selection Inspector: Single-clicking or holding
Ctrl+ Clicking a workspan segment locks the viewer into Workspan Investigation Mode.Total Journey Distance: The Selection Inspector header displays the cumulative journey distance covered across all segments in the active trip window.
Paths and Path Line Styling
Spatial trajectory trails (Paths) render vehicle movement across site terrain and BIM models. Path styling provides visual context regarding time and location:
1. Temporal Path Styling (Past vs. Future)
Solid Path Line: Represents historical movement that occurred in the past (prior to the active timeline playhead time).
Dotted Path Line: Represents the remaining trajectory section projected in the future (following the active playhead time).
2. Location & Zone Color Mapping
Inside Defined Work Area: The path line inherits the specific color assigned to that site work zone.
Transit / Public Roads (Outside Work Areas): Movements outside defined site boundaries (such as public road haulage) render in Tobe Orange Accent (solid orange for past movement, dotted orange for future movement).
3. No Defined Work Span (Blue Dotted Line)
Should Tobe Twin fail to recognize a workspan (typically due to incomplete telemetry data or transmission gaps), the platform visualizes the journey segment using a blue dotted line. This indicates an unassigned workspan segment while telemetry re-synchronizes.
