The planned scenario

An energy provider publishes service information while keeping operational details controlled. Energy Grid Operator gives that distinction a concrete shape through outage reporting, restoration information, contractor work orders, and a market data facade. Private context covers a SCADA gateway representation, meter data, crew dispatch, and an asset registry.

Examine how customer information, contractor work, and operational records are separated. An investigation can start with the public outage picture and build an evidence map around substations, feeders, meter reads, and work orders without interacting with a real electricity network.

Public surfaces

These reference routes describe possible entry points in the scenario model. They are not live customer services or a guarantee of the routes in a particular product release. Use your configured exercise inventory as the authoritative scope.

Public routes declared in the Energy Grid Operator catalog
RouteSurfaceContext
/outage-portalCustomer outage reporting and service status portal.
/outagesoutage-mapPublic outage map and restoration estimate facade.
/contractorscontractor-portalField contractor access and work order exchange.
/marketmarket-apiMarket data and demand response API facade.

Private systems

These service names and segments describe the internal context of Energy Grid Operator. They help define exercise boundaries and interpret the generated records.

scada-gateway

Private SCADA gateway representation in app subnets. Catalog segment: private application.

meter-data

Smart meter telemetry and interval data store. Catalog segment: private data.

field-dispatch

Crew dispatch workflow and outage triage service. Catalog segment: private application.

asset-registry

Substation, feeder, and device inventory data. Catalog segment: private application.

Configure your exercise

Choose a question for the assignment and define the evidence participants should collect.

  • Which outage details are appropriate for public reporting, and which reveal an internal asset or dispatch relationship?
  • How should a contractor work order be scoped against the wider substation and feeder inventory?
  • What evidence would connect an observed public response with the relevant work order or meter data category?

What to hand in

Build an exposure map separating customer status, contractor work, and internal operations. For each finding, record its source and whether it concerns a scenario surface, an access boundary or a represented operational dataset.

Records and evidence

Substations and feeders establish the asset context. Work orders and vendor tickets add the contractor perspective. Smart meter reads and outage reports provide customer and telemetry context. Compare the categories to review how information is separated between customers, contractors, and operations.

  • substations
  • feeders
  • work-orders
  • smart-meter-reads
  • vendor-tickets
  • outage-reports

Preserve the scenario and product version, the record or observation, and its source with each finding. Distinguish what a participant observed from what the reviewer inferred. Use synthetic data and your defined evidence-retention rules.

Public self-service at launch

Managed Verse is planned for 1 January 2027. Users will create an account, choose a scenario and configure their own authorized exercise boundaries. Vulnverse will host and operate the platform and cloud; users will not need to provision or maintain an exercise cloud.

Managed Verse is planned to replace all previous services. All new inquiries are paused during the transition. Read Managed Verse →.