01 · System Architecture
Field Units → Edge Server → Netsonic ERP
ERP is the single source of truth for master data. Monitor is the source of truth for telemetry, detections, and operational intelligence. Click any block to see what it does, what data flows through it, and who touches it.
Field Units
Edge Server · Monitor
Netsonic ERP
Select a block
Click any component above to see its role, what data flows through it, and which user touches it.
Every planned visit — scheduled or emergency — carries the unit's problem history and current parameter snapshot, so the technician arrives briefed instead of diagnosing from scratch on-site.
Provisioning
New unit created in ERP → synced to Monitor → appears in NOC.
Field Deployment
Geo-fence locks the delivery area, monitoring begins.
Active Monitoring
Full telemetry, billing, and safety checks active.
Servicing Loop
Monitor detects → ERP dispatches → tech confirms → Monitor validates.
Repatriation
ERP marks returned → billing stops → health score frozen as handover record.
Two Levels of Reporting
Asset & Service Reports
Everything about the asset over its lifetime — contracts, job history, inventory, service records. Pulled from Netsonic ERP.
Live Fleet Reports
What's happening right now — breakdowns, utilization, revenue at risk. Generated automatically as events occur.
02 · Use Cases
Where the Platform Pays for Itself
Every use case maps to one of four P&L objectives. Cards marked LIVE are demonstrated in the NOC simulation on Tab 04.
Contractual Over-Usage Billing
Problem — runtime outside the contracted shift window often goes unbilled.
Solution — auto-flagged, synced to Netsonic as a supplementary invoice in one click.
Economic Fleet Utilization %
Problem — no fleet-wide view of billable hours vs. yard idle time.
Solution — live utilization % computed across the active fleet.
Fleet Utilization Heatmap
Problem — hard to see which units are earning vs. sitting idle.
Solution — heatmap ranks units earning, idle, or damaged.
Breakdown-to-Dispatch TAT Reduction
Problem — 4–6 hour average turnaround, much of it spent re-diagnosing the same issue on site.
Solution — a validated breakdown auto-generates a task and pulls the unit's history, so the technician starts from a likely root cause instead of zero.
False-Alarm Validation
Problem — data dropouts trigger costly false dispatches.
Solution — 15-second hold + cross-parameter check before escalation.
Opportunity Cost of Downtime
Problem — revenue lost during breakdown isn't visible in real time.
Solution — live AED-value of revenue at risk per minute of downtime.
Heat-Derating Compensation
Problem — UAE summer heat (45–50°C+) silently derates a generator's usable capacity by 10–15%, and the loss isn't visible until load trips.
Solution — cross-references live coolant/exhaust temp and load % against ambient weather data to predict the derate before it happens, and flags load-shedding or backup dispatch in time.
Volumetric Fuel Theft Detection
Problem — tank-level drops at 0 RPM go unnoticed.
Solution — sudden drop + GPS position auto-flagged as a theft event.
Fuel Burn Consistency Check
Problem — fuel going missing and an engine simply running less efficiently look the same on a fuel log.
Solution — Monitor compares actual burn against what the manufacturer says the engine should use, and tells the two apart.
Auto-Verified Service
Problem — paperwork says the job is done — confirming that in real time shouldn't rest on the technician's word alone.
Solution — Monitor checks the engine's own signals (oil pressure, battery step-change) right after the visit, alongside the technician's sign-off.
Aggregated Lifetime Health Score
Problem — no single number tracks an asset's true condition.
Solution — 0–100 score, resets on confirmed service, frozen at repatriation.
Smarter Service Scheduling
Problem — pure calendar-based servicing wastes visits on healthy units and misses others.
Solution — today's plan already takes the earliest of estimated run hours, the OEM's periodic interval, or next appointment slot — Monitor adds one more input: pulling the date forward automatically if a unit is trending toward a breakdown.
Predictive Parts & Repair Insights
Problem — by the time a part fails, it's already an emergency.
Solution — AI trend analysis on each unit's own history flags likely part replacements or repairs before they become breakdowns.
Idle Hours / Wet-Stacking Risk
Problem — chronic light-loading silently damages engines.
Solution — flagged per unit with a projected damage cost.
Auto-Generated Carbon & Emission Certs
Problem — DEWA/MOCCAE-compliant emissions reporting is manual, error-prone, and falls apart under audit.
Solution — computes CO2/NOx output per run from fuel burn, run hours, and load factor, and generates an audit-ready certificate automatically.
03 · NOC Live Wall
Four Panels, One Command View
25 generators + 3 vehicles publishing to the same server stack. Built for a 22″ operator console, one login per seat. This preview runs on scripted sample data — the production wall streams real telemetry.
Panel A · Geospatial Fleet Core
Panel B · Real-Time Telemetry Stream
Panel C · Fleet KPI Ledger
Panel D · Task Workspace (Kanban view)
Proposed 2
Approved 1
Dispatched 1
In Progress 1
Postponed 1
Cancelled 1
Closed 1
—
04 · Sample Flows
Every Flow We Can Demonstrate
Six flows, fully simulated. Click any one to jump into the NOC Live Wall and run it there, step by step, on the actual panels.
Flow A · Catastrophic Failure
SG-2643 drops to 0 RPM under active load → validated breakdown → operator-approved ERP dispatch → technician routed.
Flow B · Predictive Degradation
SG-3108 oil pressure trends down over 48h → advisory raised → remote reset attempted → low-priority ERP job card → health score reset.
Flow C · Preventive Maintenance
SG-1734 approaches its OEM run-hour interval → service auto-booked → added to technician's existing route → run-hour clock reset on confirmation.
Flow D · Track Service Trip
Trip Kit pushed to technician pre-departure → VEH-02 en route to SG-1610 → geo-fence arrival confirmed → sign-off closes the Kanban task instantly.
Flow E · Fuel Theft Investigation
SG-4021 drops 42L in 6 min at 0 RPM → GPS + timestamp captured → no refuel match found → investigation task raised → site & ops notified.
Flow F · Contract Over-Usage Sync
SG-3355 runs past its contracted shift window (checked continuously, not at a fixed time) → overrun captured in the database → billing manager approves at invoicing time → invoice synced to Netsonic ERP.
05 · Value Dashboard
What the Fleet Is Actually Earning
Personalized to your login — every NOC operator sees their own shift and performance alongside the fleet-wide numbers.
Fleet-Wide
My Shift · Before You Leave
NOC operators dispatch and approve — they don't perform the work. Every number below is something Nandya reviewed, approved, or routed this shift; a field technician executes on-site and signs off in the field app, which is what actually closes the task and syncs back here.
My Performance · This Week