Operations Management
Plan, schedule & dispatch field work
Operations management is Nexma turned toward execution — taking an approved design and getting it built. You plan and schedule the work, dispatch crews, guide them in the field, and reconcile what was actually installed against what was designed. It closes the loop that most platforms leave open: design on one side, the field on the other, and no path between them. Here, the design and the as-built live in the same world model.
It is the same operating system — DataStore, Ontology, Jax, and the engines — surfaced for the people who run the job.
What you can do
- Decompose a design into work. An approved design becomes sequenced work orders with material lists, route maps, and installation steps — no manual re-entry.
- Schedule optimally. The MathEngine builds schedules that respect crew availability, equipment logistics, skill requirements, and dependency chains.
- Dispatch and route crews. Daily assignments are optimized for travel time and capacity; field teams receive mobile work orders with turn-by-turn navigation.
- Guide field execution. The mobile app walks each task with photo-verification checkpoints, measurements, and GPS, online or offline.
- Reconcile as-built. Installed infrastructure is compared against the approved design; deviations are flagged automatically with severity and a remediation recommendation.
Core concepts
Operations in Nexma is not a separate scheduling tool bolted onto a CAD export. Work orders, crews, schedules, and as-built captures are typed entities in the same DataStore as the design they came from — so the loop from design to build to verified-as-built never leaves the world model.
- Work is derived, not transcribed. Jax decomposes a design into work orders directly. Nobody re-keys the bill of materials into a scheduling system.
- The as-built closes the loop. A photo and a GPS fix from the field write back to the same entity the design created, so the model reflects what is actually in the ground.
- Deviations are data, not anecdotes. When installed differs from designed, the gap is a typed, severity-scored entity — surfaced as an alert, not lost in a daily report.
Design and operate are two reads of one model. The crew in the field and the engineer at the desk are looking at the same entities — which is why as-built reconciliation is automatic instead of a reconciliation project.
How it works
An approved design flows into work, the work is scheduled and dispatched, the field executes, and the as-built reconciles — all against the same entities.
1Input: an approved design in the DataStore
2 1. Decompose Jax → sequenced work orders + material lists + route maps
3 2. Schedule MathEngine → crew + equipment + dependency-aware plan
4 3. Dispatch optimized daily routes pushed to the mobile app
5 4. Execute field captures photos, measurements, GPS per checkpoint
6 5. Reconcile compare as-built to design → flag + score every deviationEach as-built capture writes back to the design entity it came from, so the world model converges on ground truth as the job progresses.
The design-to-operate loop
| Stage | What you get |
|---|---|
| Plan | Work orders decomposed from the design, with materials, routes, and installation sequences |
| Schedule | Crew-, equipment-, and dependency-aware schedules with weather windows respected |
| Dispatch | Optimized daily crew routing; mobile work orders with navigation |
| Execute | Guided field tasks with photo verification, measurement validation, and GPS tracking |
| Reconcile | Automatic as-built comparison; deviations flagged with severity and remediation |
Example
A contractor has an approved fiber design for a neighborhood and needs to build it across two weeks.
- Jax decomposes the design into per-pole and per-closure work orders, each with its material list and the splice steps for that location.
- The MathEngine schedules the work across three crews, respecting splicer skill, aerial-lift availability, and a forecast rain window.
- Optimized daily routes push to the crews' mobile app; each crew works its list with navigation and photo checkpoints.
- At a closure, the splicer captures a tray photo and confirms port assignments; the capture writes back to the design entity.
- Reconciliation flags one closure where the installed splitter ratio differs from the design, scores it, and routes a fix — before the area is marked complete.
Swap the Ontology to water or electric and the same decompose-schedule-dispatch-reconcile loop runs a main installation or a feeder build. The operations mechanics are generic; the meaning comes from the world model.
Where to go next
- Autonomous Engineering — produce the approved design operations executes.
- Nexma MathEngine — the scheduling and routing optimization behind dispatch.
- Mobile — the field app crews use to execute and capture as-built.
- Real-Time Digital Twin — watch operations update the world model live.
- Nexma AgentEngine — automate dispatch and reconciliation triggers.