The planned scenario
Water Utility separates published information from operational context. Customer accounts, service advisories, water quality reports, and contractor documents form the public surface. Private context includes treatment telemetry, laboratory information, and pump or controller inventory.
The scenario suits an exercise about information boundaries across customer service, contractors, laboratory work, and treatment operations. A quality report or maintenance request provides a recognizable starting point; the private inventory provides a second perspective for assessing what should remain restricted.
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.
| Route | Surface | Context |
|---|---|---|
/ | customer-portal | Customer account, billing, and service request portal. |
/advisories | advisories | Public water advisory and service interruption facade. |
/quality | quality-results | Water quality report and lab result browser. |
/contractors | contractor-upload | Contractor document and field work upload surface. |
Private systems
These service names and segments describe the internal context of Water Utility. They help define exercise boundaries and interpret the generated records.
treatment-telemetryTreatment plant telemetry and process history service. Catalog segment: private application.
lab-limsLaboratory information management system simulation. Catalog segment: private data.
plc-inventoryPump, PLC, and telemetry endpoint inventory. Catalog segment: private data.
Configure your exercise
Choose a question for the assignment and define the evidence participants should collect.
- Which details are appropriate in a public quality report or advisory, and which belong to internal laboratory or treatment context?
- How should a contractor document be scoped against the wider pump station and equipment inventory?
- What evidence distinguishes observed information exposure from an assumption about control of a represented process?
What to hand in
Create a review of customer, contractor, laboratory, and operations information boundaries. Tie each observation to a route or synthetic artifact and identify the audience authorized to access that information.
Records and evidence
Customers, advisories, laboratory results, pump stations, contractor files, and maintenance events make an investigation specific to water services. Compare published information with the records needed for laboratory work, maintenance, and treatment operations.
customersadvisorieslab-resultspump-stationscontractor-filesmaintenance-events
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 →.