Receive work request
How receive work request are reshaped as AGI capability advances.
The bottom line
Roughly 85% of the work in Receive work request is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: The process 'Receive work request' lacks seeded child occupations, so the scalar is derived from the process name and its utilities industry context. Receiving, logging, and triaging a work request is an administrative, information-routing task typically handled via software systems or telecommunications. Because the value-producing work of this specific step is data ingestion and orchestration, it sits squarely in the digital band.
grounded in the economy graph · digital scalar 0.85 · digital
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Receive work request sits inside a larger value-flow — 1 parent structure it composes into. The hierarchy is grounding, not the story: it tells you which aggregate exposure Receive work request inherits.
Where Receive work request sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
How the work flows
Trigger: A customer, grid sensor, or internal employee submits a notification requiring intervention on utility infrastructure.
- Capture incoming request details and geographic location
- Verify the associated customer account or physical grid asset
- Classify the work type such as outage repair or routine maintenance
- Determine initial safety hazards and urgency
- Assign priority level based on classification
- Route the request to the appropriate dispatch or engineering queue
Outcome: The work request is logged, categorized, prioritized, and queued for planning or immediate dispatch.