Betriebskonzept (ConOps)

GENERATED from docs/graph/graphcodedemo.graph.json (SSOT). OpsCon nach ISO/IEC/IEEE 29148 §5.2.4, projiziert aus dem Graphen: 4 ACTOR, 7 UC, 0 operationale REQ. Deterministisch generiert.

1 System overview

SYS-people-mover — Driverless cabin transit system for inner-city passenger transport on a dedicated guideway. Eight stations, cabins run fully automatically at block separation, one control center supervises the fleet and intervenes only when something goes wrong.

2 Operational policies & constraints

Constraint	Aussage	status
— keine system-/actor-gebundene REQ kind=non-functional im Graph	—	—

Systemweit bindende non-functional REQ (am SYS-Anker oder an einem ACTOR). Eine REQ, die nur an einem FUNC/MOD haengt, ist Design und steht hier nicht.

3 User classes & involved personnel (4)

• ACTOR-control-center — Control Center Operator — triggert UC-evacuate-cabin · UC-handle-fault · UC-supervise-operation
• ACTOR-emergency-services — Emergency Services — triggert UC-evacuate-cabin
• ACTOR-maintenance-technician — Maintenance Technician — triggert UC-service-cabin
• ACTOR-passenger — Passenger — triggert UC-board-and-alight · UC-evacuate-cabin · UC-request-trip · UC-run-the-line

4 Operational scenarios (7 UC)

UC-board-and-alight — Boarding and alighting at the platform

The stopped cabin releases boarding and alighting by opening cabin door and platform screen door only in synchrony and only while the cabin stands still.

Ausgeloest von: ACTOR-passenger

• FCHAIN-door-cycle — Door cycle at the platform: FUNC-detect-obstruction → FUNC-determine-position → FUNC-operate-cabin-door → FUNC-operate-platform-door → FUNC-prove-door-locking → FUNC-synchronize-door-pair

UC-evacuate-cabin — Evacuate cabin

Passengers leave a cabin stranded on the open guideway only after an explicit release by the control center and escorted by the emergency responders.

Ausgeloest von: ACTOR-control-center · ACTOR-emergency-services · ACTOR-passenger

• FCHAIN-evacuation — Release to cleared cabin: FUNC-announce-situation → FUNC-grant-evacuation-release → FUNC-operate-cabin-door → FUNC-prove-isolation

UC-handle-fault — Handle fault

When a fault is detected, the affected cabin takes itself into the safe state and the control center decides how to proceed.

Ausgeloest von: ACTOR-control-center

• FCHAIN-fault-handling — Fault detection to acknowledgement: FUNC-detect-guideway-obstacle → FUNC-display-alarm → FUNC-record-acknowledgement → FUNC-trigger-emergency-brake

UC-request-trip — Request a trip

The passenger selects a destination station at the terminal or in the app and is assigned a cabin together with a binding waiting time.

Ausgeloest von: ACTOR-passenger

• FCHAIN-trip-request — Trip request to cabin assignment: FUNC-capture-destination → FUNC-check-service-readiness → FUNC-dispatch-trip-order → FUNC-show-waiting-time

UC-run-the-line — Cabin runs the line

The cabin runs an issued trip order driverless and keeps the block separation prescribed by the fleet control system from the cabin ahead at all times.

Ausgeloest von: ACTOR-passenger

• FCHAIN-line-run — Trip order to stop at the destination station: FUNC-compute-speed-profile → FUNC-determine-position → FUNC-grant-block-clearance → FUNC-report-block-occupancy → FUNC-trigger-emergency-brake

UC-service-cabin — Service cabin

The maintenance technician takes a cabin out of service as scheduled, works through it and releases it again only after a passed function test.

Ausgeloest von: ACTOR-maintenance-technician

• FCHAIN-maintenance-window — Withdrawal from service to re-release: FUNC-lock-out-cabin → FUNC-prove-isolation → FUNC-report-cabin-state

UC-supervise-operation — Supervise operation

The control center sees the state of every cabin, station and block section in one picture and spots deviations without having to ask for them.

Ausgeloest von: ACTOR-control-center

• FCHAIN-operational-picture — Status report to operational picture: FUNC-aggregate-fleet-state → FUNC-present-operational-picture → FUNC-report-block-occupancy → FUNC-report-cabin-state

5 Modes of operation

— Lücke, bewusst offen. 29148 zählt Betriebsmodi (normal / degraded / maintenance / recovery) zum ConOps-Kern. Die SE-Ontologie hat keinen MODE-Elementtyp; heute reist ein Modus als REQ mit. Ein neuer ElementType ist Familie-Review + contracts-Bump (Drift-Lock L1/L2), kein lokaler View-Fix — die Lücke steht deshalb hier, statt verschwiegen zu werden. —

6 Nature of changes & summary of impacts

CR	status	Änderung	Betroffene Elemente
— kein CR mit relation auf UC/REQ/FUNC/MOD im Graph	—	—	—

Jeder CR buendelt, was er erzeugt/veraendert hat — nicht immer ein neuer Use Case, oft nur eine Funktion oder ein Requirement. Reine Milestone-Zuordnungen (CR relation MS) sind Planung und stehen im Changelog-View, nicht hier.