[M-01]JOUR 06 · 07 · 08 · 09 · 10

3D SOCIAL MAP

Real-time fleet visualization on a vector-rendered 3D map — with Time Machine replay, community odometer, and SQL-level geofence enforcement.

// OPS_COMPANION FIELD MANUAL

FIRST MONDIALE

The Community Odometer (Jour 07) is a world-first: a continuously aggregated, immutable register of every kilometre driven by every asset in the fleet. Each metre driven is permanently recorded and contributes to the collective fleet odometer — unfalsifiable by construction.

Real-Time Fleet Tracking

Every asset equipped with a telematic module transmits GPS coordinates over the Hexa-SQL injector layer (Jour 03). Coordinates are decoded from raw binary telematic frames — no cloud gateway, no intermediate API. The position data lands directly in the database, triggering a WebSocket event to all connected Dispatcher dashboards within 500 milliseconds.

// PERFORMANCE SPECS

Position update latency< 500ms via WebSocket

GPS frame sourceDirect telematic binary decode — no cloud

Map render engineVector 3D (no raster tiles)

Active assets per viewUnlimited — no viewport cap

Historical data retentionFull history, no TTL

Offline map cacheRegion tiles pre-fetched on startup

3D Vector Map Engine (Jour 06)

The map renders using a vector 3D engine — buildings, roads, and terrain are drawn from vector data, not satellite imagery. This eliminates raster tile bandwidth, enables smooth 60fps rotation and zoom, and keeps the interface clean under low-bandwidth cellular conditions.

DAY MODE

Standard visibility with full building detail and route overlays.

NIGHT MODE

Dark terrain, ambient-lit buildings, neon asset pins — optimized for low-light dispatch.

FIELD MODE

High-contrast simplified render for sunlit outdoor use on mobile devices.

Time Machine — Fleet Rewind (Jour 08)

Any Dispatcher or Administrator can rewind the 3D map to any past date and time. The map reconstitutes the exact position and operational state of every asset at that millisecond — using the immutable GPS event log stored in the database.

Time Machine is not a recording — it is a live query against the raw telemetry tables, rendered in real time. This means it can replay events that were not anticipated when they occurred: retroactive audit of geofence breaches, accident reconstruction, route verification for billing disputes.

-- Reconstruct fleet state at a specific moment

SELECT asset_id, lat, lng, speed_kmh, status

FROM gps_events

WHERE recorded_at <= '2026-05-15 14:32:07.483'

AND recorded_at >= '2026-05-15 14:32:07.483'::timestamptz - interval '30s'

ORDER BY recorded_at DESC;

Dynamic 3D Wear Gradient (Jour 09)

Machine pins on the 3D map are colored according to their mechanical wear state, computed by crossing the maintenance history and usage metrics from the 54-table relational core:

TURQUOISE

Asset in excellent condition — within maintenance window, low hour count

DIJON

Asset approaching service threshold — preventive action recommended

RED

Asset overdue for service or flagged by predictive anomaly detection

Community Odometer (Jour 07)

A continuously updating counter aggregates the cumulative distance driven by every asset across the entire organization. The counter is additive and immutable — each metre logged is sealed into the record and cannot be subtracted or modified. It serves as a collective operational fingerprint of the fleet over its lifetime.

USE CASE

The Community Odometer is used for insurance reporting, maintenance budget forecasting, and client SLA verification. Because it is backed by immutable GPS records, it is auditable to the millimetre.

Geofence Enforcement (Jour 10)

Geofences are polygon zones drawn directly on the 3D map. When an asset's GPS coordinates cross a zone boundary, the breach is detected inside the SQL engine using PostGIS spatial functions — not in the application layer. Enforcement is therefore instantaneous and cannot be bypassed by application bugs.

On breach: the machine's operational status is locked, active work order authorizations are revoked, the Dispatcher receives a real-time WebSocket alert, and an immutable breach record is created. All of this occurs as a single atomic database transaction.

// GEOFENCE ZONE TYPES

RESTRICTED

Entry triggers immediate machine lockout and Dispatcher alert

AUTHORIZED

Exit triggers lockout — machine must stay within zone for task execution

MONITORING

Entry/exit logged and reported — no automatic lockout

CLIENT SITE

Punch-in auto-triggered when asset enters, departure flagged