What this group does
This group covers the four screens that field supervisors and dispatch coordinators use every shift. A work order is created (planned maintenance, a subscriber connect/disconnect, or an outage report), it gets a technician assigned via crew routing, the crew executes it in the field, and the meter/outage systems record the operational and billing consequences. The chain is not strictly linear — Outage Management can spawn Field Work Orders, and Crew Routing schedules across all of them — but data flows one direction: field execution status feeds back up into the source record.
Field Work Orders
→
Crew Routing
→
Outage Management
→
Meter Operations
Each screen is backed by its own server-persisted store (fieldWorkOrderService.ts, crewRoutingService.ts, outageManagementService.ts, meterOperationsService.ts), all scoped under energy-setup/ in the tenant's data folder. Records reference each other by id (linkedWorkOrderId, gridNodeId, serviceZoneId) rather than embedding duplicated data.
1. Field Work Orders
Purpose: Track periodic or ad-hoc work assigned to field crews — repairs, installations, inspections, disconnections and emergency responses — against a grid node, energy asset or service zone.
Key features
- Work order type & priority —
repair, installation, inspection, disconnection, emergency_response, each with a low–critical priority badge.
- Cross-reference to Grid Nodes and Energy Assets — a work order can be scoped to a specific substation/distribution node and, optionally, to one physical asset (transformer, switchgear) on that node.
- Assigned crew tracking — each order carries an
assignedCrewId/assignedCrewName, kept in sync with whatever Crew Routing has scheduled.
- Status lifecycle —
open → assigned → in_progress → completed (or cancelled), with a scheduled date and a completion timestamp once closed.
Integration triggers
| Action | What it does |
|---|
| Created from Outage Management | When an outage event needs a physical repair, Outage Management can spawn a linked Field Work Order, pre-filled with the zone/node and an emergency_response or repair type. |
| Created from SCADA Dashboard | A critical breaker trip lockout in the SCADA Dashboard (Grid Monitoring & Control) automatically opens an outage record, which in turn may generate a Field Work Order once the outage is triaged. |
2. Crew Routing
Purpose: Plan and optimize field crew routes across open work orders by geography and workload, so dispatch can see who is where and what they're carrying before assigning the next job.
Key features
- Route planning — groups a crew's assigned work orders into a route, ordered by proximity and priority, mirroring the pattern used in the platform's Route Optimization Engine.
- Crew workload visibility — open work order count and estimated travel time per crew, so a dispatcher can spot an overloaded team before double-booking it.
- Service zone alignment — routes are built within a crew's assigned Service Zone(s), keeping coverage areas consistent with how Grid Nodes and Outage Management report zone-level metrics.
Integration triggers
| Action | What it does |
|---|
| Assign crew to work order | Writes assignedCrewId/assignedCrewName back onto the target FieldWorkOrderItem and moves it to assigned status. |
3. Outage Management
Purpose: Log, triage and track planned or unplanned electricity/water/gas outages from first report through restoration, with severity, affected-subscriber counts and an estimated restoration time.
Key features
- Outage classification —
planned, unplanned, or emergency_tripping (the type used when a SCADA breaker trip auto-generates the event), each with a minor/major/critical severity.
- Lifecycle tracking —
reported → investigating → crew_dispatched → restoring → resolved, with both an estimated and an actual restoration timestamp.
- Affected subscriber count — surfaced per event so dispatch and communications can prioritize by customer impact, not just technical severity.
Integration triggers
| Action | What it does |
|---|
| Auto-created from SCADA | Automatically opens a critical/emergency_tripping outage record when a breaker enters trip lockout on the SCADA Dashboard (see Grid Monitoring & Control). |
| Dispatch crew | Sets status to crew_dispatched and can create a linked Field Work Order for the physical repair. |
AI Assistant
A collapsible AI Assistant panel lives on the right edge of the screen — click the tab (Sparkles icon) to open it, select one or more outage rows to focus its answers, and use the New Chat and Fullscreen controls in its header as needed. Ask it to flag unresolved critical outages, find events with an overdue restoration time, summarize outages by zone or severity, or point out records missing a linked work order. Every answer can be saved as a report via Save as Report, and the panel can ground its replies in your My Knowledge library through Attach Knowledge.
4. Meter Operations
Purpose: Manage smart-meter and analog-meter field tasks — periodic readings, service connect/disconnect, seal audits and meter replacements — and record the subscriber and tariff context each task ties back to.
Key features
- Task type & meter type —
periodic_reading, connect_service, disconnect_service, seal_audit, meter_replacement, against electricity_smart, electricity_analog, water_smart or gas_smart meters.
- Reading capture — last reading and new reading values recorded on each periodic-reading task, forming the raw input for consumption billing.
- Subscriber & tariff linkage — each task carries a subscriber name and an optional
tariffContractId, connecting field execution to the billing side of Operational Setup.
Integration triggers
| Action | What it does |
|---|
| Sync completed readings | Completed periodic-reading tasks with a recorded new value are used by Asset Health Score and Consumption Analytics (see Grid Monitoring & Control) to refresh telemetry without re-keying data. |
AI Assistant
An AI Assistant panel is available from the right-edge tab on this screen too. Select one or more meter tasks to give it scope, then ask it to surface scheduled tasks with no technician assigned, tasks that are overdue against their scheduled date, a breakdown by task type or meter type, or readings whose consumption jump (new minus last reading) looks unusual. Replies can be saved as a report, and the panel can pull extra context from your My Knowledge library when you attach it.
End-to-end data flow
| Source screen | Action | Target screen / record |
|---|
| SCADA Dashboard | Breaker enters trip lockout | → new record in Outage Management |
| Outage Management | Dispatch crew for physical repair | Linked Field Work Order created/updated → Field Work Orders |
| Field Work Orders | Assign to crew | Route added to crew's schedule → Crew Routing |
| Meter Operations | Complete periodic reading | → Asset Health Score / Consumption Analytics telemetry refresh |
