The planned scenario
Manufacturing OT provides both a business entry surface and an industrial operations vocabulary. Suppliers, product support, quality documents, and remote maintenance requests sit alongside a private manufacturing execution model, historian data, controller inventory, and engineering workstation artifacts.
Investigate the information boundary between a supplier or maintenance request and the production context behind it. A team can review what an external party should know about a work order, then explain how that differs from access to line telemetry, controller inventory, or engineering artifacts.
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 |
|---|---|---|
/ | supplier-portal | Supplier collaboration and purchase order facade. |
/support | product-support | Product support and case workflow. |
/quality | quality-docs | Quality document and nonconformance browser. |
/maintenance | remote-maintenance | Remote maintenance request facade. |
Private systems
These service names and segments describe the internal context of Manufacturing OT. They help define exercise boundaries and interpret the generated records.
mes-apiManufacturing execution system API representation. Catalog segment: private application.
historian-dataProcess historian and production telemetry store. Catalog segment: private data.
plc-inventoryPLC, HMI, and line controller inventory. Catalog segment: private data.
engineering-workstationEngineering workstation artifact simulation. Catalog segment: private application.
Configure your exercise
Choose a question for the assignment and define the evidence participants should collect.
- Which production details should a supplier or maintenance request reveal, and which belong to internal engineering context?
- Can quality records be related to work orders without assuming that a visible record grants control over a production line?
- What boundary should separate controller inventory and engineering artifacts from public product support?
What to hand in
Write a boundary review organized around suppliers, quality, maintenance, and engineering. Include the source artifact for each observation and identify whether a proposed control applies to a scenario surface, an access boundary or a represented OT system.
Records and evidence
Suppliers, work orders, quality records, line telemetry, PLC inventory, and maintenance tickets provide the exercise context. Use them to compare the information an external supplier needs with the records reserved for production and engineering teams.
supplierswork-ordersquality-recordsline-telemetryplc-inventorymaintenance-tickets
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 →.