The planned scenario
An airport publishes flight and baggage information while coordinating a much wider operational picture. Airport Operations gives an exercise those separate perspectives: passenger facing routes, vendor workflows, gate assignments, baggage metadata, and fuel records. The useful question is how much operational context a public surface reveals and which records belong behind a different access boundary.
Start with the information a passenger or supplier would reasonably see. Then use the private inventory to distinguish a public flight status from the operational records that support it. The scenario supplies a vocabulary for that investigation without connecting to a working airport.
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 |
|---|---|---|
/ | passenger-portal | Passenger information and airport services portal. |
/flights | flight-info | Flight status and gate information facade. |
/vendors | vendor-portal | Airport vendor and tenant workflow surface. |
/baggage | baggage-status | Baggage tracking status API simulation. |
Private systems
These service names and segments describe the internal context of Airport Operations. They help define exercise boundaries and interpret the generated records.
ops-controlAirport operations control data representation. Catalog segment: private application.
gate-schedulingGate assignment and turnaround workflow data. Catalog segment: private application.
baggage-sortationBaggage sortation system metadata. Catalog segment: private application.
fuel-inventoryFueling inventory and service records. Catalog segment: private data.
Configure your exercise
Choose a question for the assignment and define the evidence participants should collect.
- Which flight, gate, and baggage details belong in passenger information, and which would reveal internal operational context?
- What should distinguish a vendor view from airport operations access when both refer to the same terminal activity?
- Can an investigator explain a public status observation using the relevant gate, baggage, or operations artifacts without assuming every timestamp describes a live event?
What to hand in
Produce a surface inventory grouped by passenger, vendor, and operations access. Attach the exact route or artifact behind each observation and identify the boundary to examine in the configured exercise.
Records and evidence
Flights and gates establish the public context. Baggage events and vendor records widen the investigation; fuel records and operations logs provide the internal perspective. Organize the evidence around the information each audience needs for its task.
flightsgatesbaggage-eventsvendorsfuel-recordsops-logs
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 →.