Energy / Utilities Pilot Path
A controlled path to an Energy/Utilities pilot
The recommended path is offline review, synthetic reference tenant, or read-only pilot before any production integration. Runtime activation requires customer scope and security approval.
Pilot data classes
Incident historyMeasure event sequence, recurrence, closure signal and decision delay.
Asset telemetry exportCompare weak operational signals with alert timing and approved decisions.
Dispatch recordsQualify field readiness, team availability and travel timing without live dispatch.
Maintenance and change eventsConnect scheduled work, asset state and decision windows without assuming causation.
Customer-impact summaryUse aggregate complaint, call or service impact records where approved.
Financial assumptionsCost exposure stays MODEL or ESTIMATE until finance validates assumptions.
Acceptance checklist
Scope and sponsorScope locked, human decision owner named, no automatic execution accepted.
Data boundaryForbidden classes excluded, retention accepted, deletion rule written.
SecurityNo credential material requested, audit trail ready, read-only path defined.
Success metricsDecision delay, dispatch timing, avoided escalation estimate, report usefulness and decision defense completeness.
Boundary
No live controlRaven prepares decision packets. It does not operate the grid, water system or field crew.
Human approvalThe operator, manager or authorized customer role approves action.
Customer requiredReal source mapping, role model, retention, legal/security review and support scope require the customer.