Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.183 Consolidate operational data
Goal | Achieve elegant and optimal operational data diagrams. |
---|---|
Requirements met by this process step | None. |
Inputs | AMOD-101 Consolidated operational activities & interactions AMOD-105 Operational data objects [O.CDB] AMOD-110 Operational exchange items [O.CDB] |
Outputs | AMOD-025 Abstract concepts (new full scope viewpoint) AMOD-105 Operational data objects [O.CDB] |
Methodology | At this point, operational feature review have been concluded and consolidation of operational activities and interactions is being done (ARCH.121) which includes to optimise flows and this includes to optimise the operational data as well. That is why this process is required. The consolidation should be done only for abstract concepts and operational data and will be the end of the activity started in the process step ARCH.008 Define abstract concepts relevant to the wider system of interest and based on what has been done on each operational capability data elaboration. This process step includes to create a new viewpoint AMOD-025 but focusing on full-scope. This means a consolidation of the AMOD-025 (limited scope) done in previous process steps should be elaborated. The operational data will be consolidated but it will be done on the previous viewpoint (limited scope). Consolidation should aim to achieve:
|
Tools and non-human resources | Team for Capella |
Cardinality | Once per package of operational capabilities |
Completion criteria | The produced view is compliant with its modelling rules. The complete set of operational data is safe enough to try. |
Design review | ARCH.R.2 Operational review - consolidated |
Step done by (Responsible) | Operational concept architect |
Provides input to/assists (Contributes) | System architect Systems engineer Cross-cutting engineer Operations domain expert |
Uses outputs (Informed) | None directly |