Energy & Utilities

Field Service Grid Copilot

Designed for Field technician

Equip a field technician at the pole or substation with the right asset record, switching procedure, and outage context to complete the work order safely, with a control-room switching authorization before any energized operation.

Contract ENE-01 · primary aggregate FieldWorkOrder · mode loading

Decision brief

Authorize switching and energization: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Control-room operator

The named role remains accountable for the consequential decision.

Governed evidence

5 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

A technician arrives at a failed pole-mounted recloser during a storm; the copilot shows 312 customers out on the feeder, identifies the upstream isolating device, cites the manufacturer's bypass procedure for the voltage class, and holds the energized steps until the control room issues the switching authorization..

Decision to make

Equip a field technician at the pole or substation with the right asset record, switching procedure, and outage context to complete the work order safely, with a control-room switching authorization before any energized operation.

Outcome to show

Issued switching authorization and permit record gives Control-room operator the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Accept the work order in the field
  2. 2Load asset, connectivity, and outage context
  3. 3Retrieve the applicable procedure
  4. 4Guide the field task with citations
  5. 5Authorize switching and energization

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Control-room operator verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved FieldWorkOrder evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Equip a field technician at the pole or substation with the right asset record, switching procedure, and outage context to complete the work order safely, with a control-room switching authorization before any energized operation.
Primary aggregate
FieldWorkOrder
Primary container
fieldWorkOrders
Hierarchical key
/tenantId + /serviceTerritoryId
Schema version
1

Sample scenario

A technician arrives at a failed pole-mounted recloser during a storm; the copilot shows 312 customers out on the feeder, identifies the upstream isolating device, cites the manufacturer's bypass procedure for the voltage class, and holds the energized steps until the control room issues the switching authorization.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
fieldWorkOrders Primary /tenantId + /serviceTerritoryId FieldWorkOrder, GridAssetRecord, OutageIncident
gridProcedureLibrary Reference /tenantId + /documentId SwitchingProcedure, TechnicalManualChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
FieldWorkOrder fieldWorkOrders /tenantId + /serviceTerritoryId workorder::{serviceTerritoryId}::{workOrderId} None
GridAssetRecord fieldWorkOrders /tenantId + /serviceTerritoryId asset::{serviceTerritoryId}::{assetId} None
SwitchingProcedure gridProcedureLibrary /tenantId + /documentId switching::{documentId}::{stepIndex} stepVector
OutageIncident fieldWorkOrders /tenantId + /serviceTerritoryId outage::{serviceTerritoryId}::{incidentId} None
TechnicalManualChunk gridProcedureLibrary /tenantId + /documentId manual::{documentId}::{chunkIndex} bodyVector

Query patterns