- Documentation
- /
- Prt 01 Infra
- /
- 00 — Overview
00 — Overview
Demonstration prototype. prt_01_infra is a reference application and part of the Port & Terminal Operations series (catalogue PRT-01). It holds no real port, structure, inspection or engineering data — everything in the demo is fictional and illustrates the data model only.
What the Port Infrastructure & Engineering Restrictions application is
Know what the fixed infrastructure is, how it is inspected, and which engineering restrictions apply — port, terminal, area, fixed assets, inspection plans and inspections, defects, engineering assessments, restrictions, remedial work and independent verification. Owner role: port engineer.
The rules the model is built around
The pack's five requirements (business_rules.yaml, PRT-01-R01 to R05; they bind to hooks that are Phase 2 — not enforced yet). Default verdict on missing or stale safety-critical inputs: deny.
- R01 — Acyclic hierarchy. The asset hierarchy (
InfraAsset.parent) must be acyclic, and every asset belongs to a terminal area. - R02 — Inspection intervals. Intervals are positive; the next due date is calculated from an accepted inspection, never a draft.
- R03 — Versioned restrictions. Restriction activation and release each increment the restriction's
version; releasing one restriction releases only that one. - R04 — Emergency restrictions. An emergency restriction may precede the engineering assessment, but it creates a review obligation.
- R05 — Structural rating. A structural rating needs engineer approval; load capacity is never inferred from a condition grade.
Ownership boundaries: PRT-01 owns the physical berth identity and civil/fixed supporting infrastructure (PRT-04 owns the berth's operational projection and allocation; PRT-02 owns the operating equipment). Other applications' records are canonical strings (dependent_cid and the *_cid / *_ref columns), never foreign keys; every record has a hidden canonical_ref.
The workflow actions (Phase 2 guards)
| Action | Model | From → to | Role | Guards (documented, not enforced yet) |
|---|---|---|---|---|
| approve_assessment | InfraAssessment | draft → approved | port engineer | assessment complete; approver authorised |
| activate_restriction | InfraRestriction | draft → active | port engineer | approved assessment or emergency authority; effective time and review due recorded |
| complete_remedial_work | InfraRemedialWork | in_progress → completed | maintenance supervisor | work evidence recorded |
| release_restriction | InfraRestriction | active → released | port engineer | independent InfraVerification pass; all linked remedial work complete; no other restriction implicitly released |
System transitions (also Phase 2): an inbound authoritative scoped hold may force an asset to held, audited and published; expiry never auto-releases; reopening needs authorised new adverse evidence.
The 15 models by area
| Area | Models |
|---|---|
| Restrictions & Defects | InfraRestriction · InfraDefect · InfraAssessment · InfraRemedialWork · InfraVerification |
| Assets & Inspection | InfraAsset · InfraInspectionPlan · InfraInspection |
| Network Links | InfraDependency · InfraObligationTask · InfraSafetyHold · InfraCaseLink |
| Terminal Structure | InfraArea · InfraTerminal · InfraPort |
Twelve are the pack's models (translated from S001–S012); InfraObligationTask, InfraCaseLink and InfraSafetyHold are OVERLAY models — additions to the pack's models that hold what the consumed events deliver (an assigned obligation, a closed assurance case, a safety hold). Model names are unique across the whole fleet (hence the Infra prefix), because network tests load many applications into one process.
The dashboard
The pack's dashboard tiles are active restrictions, overdue inspections and open defects. In the demo all three are empty or zero by design: the terminal has no active restriction, no overdue inspection and no open defect.
The demo story
Example Bulk Terminal (T01, two berths B01 and B02, a ship loader SL01 and a conveyor CV01) in the state just before step 1 of the reference scenario (2026-11-15 23:30 UTC): five fixed assets with condition grades (B01, B02, SL01-RAIL, CV01-GANTRY, STK-PAD-1) plus a replaced fender panel under B01, five inspection plans (two due within a few weeks, none overdue) with accepted inspections, and no active restriction. The history shows how a restriction runs: in October, IR-26-0001 (Berth 1 fender damage, a speed limit, active 2026-10-01 to 2026-10-15) was based on an approved assessment, cleared by remedial work and released on an independent verification pass (the verifier is not the performer). The overlay tables carry the October case thread: a closed link to assurance case PC-26-0001, a done task for obligation PO-26-0001 and the released safety hold SH-26-0001. InfraDependency says SL01 and CV01 are installed on their supports, the handling route uses B01 and the stockpile pad, and B01 is the berth of both vessel visits. The reference scenario then runs on the other applications; this one is expected to publish infrastructure.restriction_changed only if a restriction is activated (Phase 2).
How to read it
- Start from the first menu group (Restrictions & Defects); it holds the records the port engineer works in.
- Terminal Structure is the master data and Network Links are this application's own copies of what other applications said about it.
- Date-times are stored as UTC and shown in each person's own time zone; the demo terminal's zone is Australia/Brisbane.
- Quantities carry an explicit unit (
limit_unit,design_limitwithlimit_unit); the speed limit in the history is a synthetic number.