Once the quote signs and the design ships — somebody dispatches the crew. Somebody routes the parts. Somebody watches the assets in the field. Active Operations is that layer, reading from the same canonical graph that priced the work.
Active Operations doesn't replace your FSM. It sits on top — reading the work plan from Deployment Design, reading the canonical graph from the platform, and routing decisions back when crews or assets drift.
Crews, trucks, SKUs reconciled against margin-protected schedules. When a job slips, we reshuffle — and tell you which stops are still on margin.
Schedule against real crew availability, real skill match, real travel time — not the dispatcher's whiteboard. Reads HOS, certifications, and historical fix-rate per tech.
Every deployed unit (charger, chiller, sensor, vehicle) feeds telemetry back into the graph. Drift, faults, and utilization flow into margin and renewal scoring.
Hours burned, parts consumed, change orders — captured at the line, the crew, the supplier. Variance attributed before the invoice cuts. Feeds back into Cost Engine.
Work orders ship from Active Operations into your FSM. Your techs see the same screens. Active Ops is the decision layer above.
Real route geometry, traffic-aware ETAs, address resolution all feeding the dispatch board.
Deployed-asset signal arrives via industrial IoT pipelines. Allometry doesn't replace your historian — it reads from it.
Crew SMS, dispatcher escalations, change-order approvals — routed through the channels your team already uses.
Send us a live route from your FSM. We'll plug Active Operations in, score every stop on margin, and show you where the bleed is happening. No replacement of your stack — just the decision layer above it.