Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.R.2 Operational review - consolidated
AREV-2.1 Artefacts list
Scope of compliance | Artefact | O1 | O2 | O3 | O4 | Identities of views created | Modelling rules compliance ![]() ![]() | Notes |
---|---|---|---|---|---|---|---|---|
Full | AMOD-021 Operational capabilities definition | Initial | Updated | - | Updated | |||
Full | AMOD-022 Enterprise & environment definition | Initial | Updated | - | - | |||
Full | AMOD-023 Operational entity/actor states | Initial | Updated | - | Updated | |||
Full | AMOD-025 Abstract concepts | Initial | Updated | - | Updated | |||
Full | AMOD-105 Operational data objects [O.CDB] | - | Initial | - | Updated | |||
Full | AMOD-110 Operational exchange items [O.CDB] | - | Initial | - | Updated | |||
Full | AMOD-024 Operational activity definition and allocation | - | Initial | - | Updated | |||
Full | AMOD-128 Safety compliance strategy | - | - | Initial/ updated | - | ![]() | Only created initially if this is the first batch of operational capabilities to be worked on; otherwise, reuse and/or update the existing artefact | |
Full | AMOD-129 Relevant safety legislation/regulations | - | - | Initial/ updated | - | ![]() | Only created initially if this is the first batch of operational capabilities to be worked on; otherwise, reuse and/or update the existing artefact | |
Full | AMOD-030 Accident and hazard state model | - | - | Initial/ updated | - | Only created initially if this accident has not been addressed by previous risk analysis - otherwise, reuse and update existing view | ||
Full | AMOD-031 Unified risk model (to be discussed) | - | - | Initial/ updated | - | Only created initially if this is the first batch of operational capabilities to be worked on; otherwise, reuse and/or update the existing artefact | ||
Full | AMOD-130 Business loss and risk state model | - | - | Initial/ updated | - | Only created initially if this loss has not been addressed by previous risk analysis - otherwise, reuse and update existing view | ||
Full | AMOD-145 Security compliance strategy | - | - | Initial/ updated | - | ![]() | Only created initially if this is the first batch of operational capabilities to be worked on; otherwise, reuse and/or update the existing artefact | |
Full | AMOD-131 Security loss and threat state model | - | - | Initial/ updated | - | Only created initially if this loss has not been addressed by previous risk analysis - otherwise, reuse and update existing view | ||
Full | AMOD-135 Consolidated operational deviation analysis report | - | - | Initial | - | |||
Full | AMOD-101 Consolidated operational activities & interactions | - | - | - | Initial | |||
Full | ARCH.R.1 Operational capability review | - | - | - | Initial | For each operational capability in the current package, ARCH.R.1 must have been passed before ARCH.R.2 can pass. |
AREV-2.2 Review criteria
Completion of single-capability reviews
Capability | Capability version | Review page | Review ticket |
---|---|---|---|
Activity & viewpoint completion
ID Prefix AREV-2.2.1.x | EN 50126 phase | Activity | Tickets | Viewpoint output | Scope of compliance | Notes |
---|---|---|---|---|---|---|
010 | O1 | ARCH.004 Analyse trade space factors | AMOD-010 (Included in AMOD-037) | Full | This activity does not necessarily need to be done once per package of capabilities; however, in this review, it should be checked that the outputs are still up to date. | |
020 | O1 | ARCH.005 Define set of system of interest lifecycle variants | AMOD-012 | Full | This activity does not necessarily need to be done once per package of capabilities; however, in this review, it should be checked that the outputs are still up to date. | |
030 | O1 | ARCH.144 Define enterprise goals | AMOD-106 (Included in AMOD-037) | Full | This activity does not necessarily need to be done once per package of capabilities; however, in this review, it should be checked that the outputs are still up to date. | |
040 | O1 | ARCH.009 Define measures of effectiveness | Included in AMOD-037 | Full | This activity does not necessarily need to be done once per package of capabilities; however, in this review, it should be checked that the outputs are still up to date. | |
050 | O3 | ARCH.023 Identify relevant safety legislation and regulation | AMOD-128 | Full | This activity does not necessarily need to be done once per package of capabilities; however, in this review, it should be checked that the outputs are still up to date. | |
060 | AMOD-129 | Full | ||||
070 | O3 | ARCH.012 Determine measure of effectiveness target values | Included in CONOPS | Full | ||
080 | O3 | ARCH.018 Identify internal & external issues affecting successful security | AMOD-145 | Full | ||
090 | O3 | ARCH.019 Determine need for information availability, confidentiality, integrity | AMOD-110 | Full | ||
100 | O4 | ARCH.121 Consolidate operational activities and interactions | AMOD-101 | Full | ||
110 | O4 | ARCH.183 Consolidate operational data | Full | |||
120 | AMOD-105 | Full | ||||
130 | AMOD-110 | Full | ||||
140 | O4 | ARCH.121 Consolidate operational activities and interactions | AMOD-024 | Full |
Content criteria
ID Prefix AREV-2.2.2.x | EN 50126 phase - initial | EN 50126 phase - final update | Content criterion | Evidence | Achieved
| Required review role | Reviewer identity | Reviewer commentary | Blocking corrective action | Non-blocking corrective action |
---|---|---|---|---|---|---|---|---|---|---|
010 | O1 | O1 | The enterprise goals relevant to this package of capabilities are complete and correct. | AMOD-106 included in AMOD-037 | Design authority | |||||
030 | O1 | O1 | The system lifecycle model is safe enough to try for this package of capabilities. | AMOD-012 | Design authority | |||||
040 | O1 | O1 | The trade space factors relevant to this package of capabilities are complete and correct. | included CONOPS | Design authority | |||||
060 | O1 | O4 | The operational capabilities defined for this package of capabilities are a safe enough to try representation of all the stakeholder needs that are to be addressed in this package. | Description of OC | Design authority | |||||
080 | O1 | O4 | The measures of effectiveness are safe enough to try for this package of operational capabilities | included CONOPS | Design authority | |||||
090 | O1 | O4 | The operational safety risks associated with this package of capabilities have been identified, assessed, and mitigated to a non-qualifiable level (safe enough to try only) | Design authority | ||||||
092 | O1 | O4 | The operational security risks associated with this package of capabilities have been identified, assessed, and mitigated to a non-qualifiable level (safe enough to try only) | Design authority | ||||||
094 | O1 | O4 | The operational business risks associated with this package of capabilities have been identified, assessed, and mitigated to a non-qualifiable level (safe enough to try only) | Design authority | ||||||
100 | O2 | O4 | The operational activities have been allocated to the correct operational actors or entities, including any duplicate or joint responsibilities. | AMOD-024 | Design authority | |||||
105 | O2 | O4 | The operational activities have been consolidated (to a safe enough to try level) across the set of operational capabilities in this milestone, so that duplicates and gaps have been eliminated. | AMOD-101 | Design authority | |||||
107 | O2 | O4 | The consolidated set of operational activities is sufficient (to a safe enough to try level) to realise all the operational capabilities in this milestone. | AMOD-101 | Design authority | |||||
110 | O2 | O4 | Exchange item definitions and supporting data types for all operational capabilities in the package are safe enough to try. | Design authority | ||||||
120 | O2 | O4 | Operational states of operational actors or entities are defined in compliance to one of the following critera:
and the states that have been defined are safe enough to try. | AMOD-023 | Design authority | |||||
130 | - | O4 | The content in the scope of this review is safe enough to try system needs analysis for the whole package of operational capabilities. | All submitted content | Lead system architect |