Project context is captured.
Project name, utility territory, capacity, technology type, site-control reference, queue or application ID, and milestone context are placed into one operating record.
EnergyOps · Reference workflow
Interconnection packet readiness follows one operating route.
EnergyOps receives project context, normalizes packet evidence, checks readiness, identifies gaps, records exceptions, and returns a delivery package through the same OS rail used for onboarding, trust, quote, run contract, queue, result contract, callback, ledger, and attestation.
Workflow route
From project record to packet readiness package.
The reference workflow is designed for project teams, agents, and operators that need a clear interconnection packet review instead of scattered notes across files, emails, portals, and spreadsheets.
Packet artifacts are checked.
Application records, single-line diagram references, study or milestone records, permits, fee references, correspondence, and missing-item notes are compared against the readiness checklist.
The result package carries the trail.
EnergyOps returns readiness status, evidence checklist, missing items, exceptions, milestone summary, next action, callback state, ledger reference, and attestation.
Machine-readable workflow
Agents can inspect the route before submitting work.
The workflow schema and example show accepted input categories, readiness checks, output fields, callback behavior, ledger references, and attestation records.