FleetOps

The dashboard opens mid-pilot: Manali Bulk Terminal, pilot, Day 12 of 30, 2 contractors. When a driver's fatigue signal crosses a threshold, a red alert card leads the page, showing the exact band read that triggered it, heart rate, HRV, SpO2, skin temperature, a predicted fatigue state, and one clear recommended action, assign a relief driver or enforce a rest period, with a live response countdown. Below it sit the key indicators for the day, PTW clearance, open red alerts, signal completeness, band-worn compliance, SLA acknowledgment, a 7-day fleet fatigue trend, route hotspots colored by risk, and a live activity feed of escalations, overrides, and clearances. From there the operator moves into full working surfaces: Trips, Vehicles, Drivers and bands, Fitness checks, Messages, PTW audit trail, and Safety report, each with real search, filter, and record-level detail, not static screenshots standing in for a product.

FleetOps, shipped under the product name Armortrix FleetOps, is a B2B safety dashboard designed for Indian Oil Corporation's tanker fleet, built around a wearable driver-fatigue band. Drivers wear a band that reads heart rate, HRV, SpO2, and skin temperature; on-device inference estimates a fatigue state; that reading gates whether a driver clears the Permit to Work process before a trip. This dashboard is where a fleet operator watches that safety layer in real time and acts on it.

The work happened in two passes. The first shipped eight full surfaces, overview, contractor compliance, PTW audit trail, network safety report, route risk index, terminals, reports and exports, and settings, in a Linear-inspired dark system chosen deliberately over a dense ops-dashboard look: for a safety-critical, DGM-facing product, restraint reads as premium and trustworthy where a wall of charts reads as noise. A PRD review then surfaced a real gap, the written spec and the prototype described two different products: the PRD wanted a trip-lifecycle CRUD spine, the prototype was compliance-and-audit only. The second pass added the missing operational core as real, clickable screens: Trips with a full status lifecycle and conflict-guarded crew assignment, Vehicles, and Fitness Checks, including a governed safety override that requires written justification and a safety-officer sign-off before a fatigue-based hold can be cleared, logged immutably. The build closed with an eight-agent interaction audit and a six-agent Nielsen heuristic pass across every clickable element, which surfaced and led to fixes for both hard accessibility failures found, keyboard operability and color contrast, along with a list of real interaction bugs: a search input that did nothing, table filters that did not filter, and a view-all control that under-expanded a driver list.

A wearable fatigue signal only matters if the workflow around it turns a number into a decision fast enough to act on. The design problem was making a biometric reading resolve into one clear, low-friction safety call for an operator running dozens of trips at once, without burying it under charts. The single-accent, function-only color system exists for exactly that reason: the one alert that actually needs attention is the only thing on the page that reads as urgent.