The planned scenario
A port coordinates information across terminals, vessels, trucking, and customs. Port Authority represents those public workflows while keeping terminal operations, crane telemetry, cargo manifests, and yard inventory in the private model. The scenario examines which party needs which part of a shared logistics picture.
Begin with a vessel schedule, truck appointment, or document exchange. Use the private inventory to ask how that context relates to container movements and cargo metadata. Map ownership and information access across several participants in the same operation.
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 |
|---|---|---|
/ | terminal-portal | Terminal operator and stakeholder portal. |
/vessels | vessel-schedule | Vessel schedule and berth planning facade. |
/trucks | truck-appointments | Truck appointment and gate workflow API. |
/customs | customs-docs | Customs document exchange facade. |
Private systems
These service names and segments describe the internal context of Port Authority. They help define exercise boundaries and interpret the generated records.
terminal-osTerminal operating system representation. Catalog segment: private application.
crane-telemetryCrane telemetry and maintenance data. Catalog segment: private application.
manifest-storeCargo manifest and bill of lading data store. Catalog segment: private data.
yard-inventoryContainer yard inventory and movement data. Catalog segment: private data.
Configure your exercise
Choose a question for the assignment and define the evidence participants should collect.
- What should a truck appointment reveal about a container or terminal without exposing a wider cargo inventory?
- How should vessel scheduling and customs documents be separated from internal yard and manifest records?
- Which artifact supports an observation about a logistics relationship, and which details remain assumptions?
What to hand in
Produce a participant and data map covering terminal users, vessel information, truck appointments, customs documents, and private operations. Support exposure claims with a route, record or observed system response.
Records and evidence
Vessels and berths describe the maritime context. Containers and truck appointments add landside movement context. Customs documents and crane events provide investigation artifacts. Compare the information needed by terminal users, carriers, trucking operators, and internal operations.
vesselsberthscontainerstruck-appointmentscustoms-docscrane-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 →.