Legal information

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

Jira tickets

SM-3494 - Define criteria for review ARCH.R.2 Finished

RCAMT-299 - Update design review critieria/evidence to indicate the 50126 phase where the artefacts are created/updated Finished

SM-5282 - Add batches of artefacts to ARCH process diagram Finished


AREV-2.1 Artefacts list

Scope of complianceArtefactO1O2O3O4Identities of views createdModelling rules compliance (tick)/(error)Notes
FullAMOD-021 Operational capabilities definitionInitialUpdated-Updated


FullAMOD-022 Enterprise & environment definitionInitialUpdated--


FullAMOD-023 Operational entity/actor statesInitialUpdated-Updated


FullAMOD-025 Abstract conceptsInitialUpdated-Updated


FullAMOD-105 Operational data objects [O.CDB]-Initial-Updated


FullAMOD-110 Operational exchange items [O.CDB]-Initial-Updated


FullAMOD-024 Operational activity definition and allocation-Initial-Updated


FullAMOD-128 Safety compliance strategy--Initial/ updated-
(tick) Not applicableOnly created initially if this is the first batch of operational capabilities to be worked on; otherwise, reuse and/or update the existing artefact
FullAMOD-129 Relevant safety legislation/regulations--Initial/ updated-
(tick) Not applicableOnly created initially if this is the first batch of operational capabilities to be worked on; otherwise, reuse and/or update the existing artefact
FullAMOD-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
FullAMOD-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
FullAMOD-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
FullAMOD-145 Security compliance strategy--Initial/ updated-
(tick) Not applicableOnly created initially if this is the first batch of operational capabilities to be worked on; otherwise, reuse and/or update the existing artefact
FullAMOD-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
FullAMOD-135 Consolidated operational deviation analysis report--Initial-


FullAMOD-101 Consolidated operational activities & interactions---Initial


FullARCH.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

CapabilityCapability versionReview pageReview ticket




Activity & viewpoint completion

ID

Prefix AREV-2.2.1.x

EN 50126 phaseActivityTicketsViewpoint output

Scope of compliance

Notes
010O1ARCH.004 Analyse trade space factors
AMOD-010 (Included in AMOD-037)FullThis 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.
020O1ARCH.005 Define set of system of interest lifecycle variants
AMOD-012FullThis 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.
030O1ARCH.144 Define enterprise goals
AMOD-106 (Included in AMOD-037)FullThis 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.
040O1ARCH.009 Define measures of effectiveness
Included in AMOD-037FullThis 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.
050O3ARCH.023 Identify relevant safety legislation and regulation

AMOD-128FullThis 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.
060AMOD-129Full
070O3ARCH.012 Determine measure of effectiveness target values
Included in CONOPSFull
080O3ARCH.018 Identify internal & external issues affecting successful security
AMOD-145Full
090O3ARCH.019 Determine need for information availability, confidentiality, integrity
AMOD-110Full
100O4ARCH.121 Consolidate operational activities and interactions
AMOD-101Full
110O4

ARCH.183 Consolidate operational data




AMOD-025

Full
120AMOD-105Full
130AMOD-110Full
140O4ARCH.121 Consolidate operational activities and interactions
AMOD-024Full

Content criteria

ID

Prefix AREV-2.2.2.x

EN 50126 phase - initialEN 50126 phase - final updateContent criterionEvidence

Achieved 

(tick)/(error)

Required review roleReviewer identityReviewer commentaryBlocking corrective actionNon-blocking corrective action
010O1O1The enterprise goals relevant to this package of capabilities are complete and correct.AMOD-106 included in AMOD-037
Design authority



030O1O1The system lifecycle model is safe enough to try for this package of capabilities.AMOD-012
Design authority



040O1O1The trade space factors relevant to this package of capabilities are complete and correct.included CONOPS
Design authority



060O1O4

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.

AMOD-021

Description of OC


Design authority



080O1O4The measures of effectiveness are safe enough to try for this package of operational capabilitiesincluded CONOPS
Design authority



090O1O4

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)

AMOD-030

AMOD-101

AMOD-135


Design authority



092O1O4The 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)

AMOD-131

AMOD-135

AMOD-101


Design authority



094O1O4The 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)

AMOD-135

AMOD-130

AMOD-101


Design authority



100O2O4The operational activities have been allocated to the correct operational actors or entities, including any duplicate or joint responsibilities.AMOD-024
Design authority



105O2O4

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



107O2O4The 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



110O2O4Exchange item definitions and supporting data types for all operational capabilities in the package are safe enough to try.

AMOD-110

AMOD-105


Design authority



120O2O4

Operational states of operational actors or entities are defined in compliance to one of the following critera:

  • there is a clear and relevant difference in the behaviour of an entity/actor, depending on its state, or
  • the behaviour of the wider system of interest is defined in terms of changing the state/mode of an entity/actor.

and the states that have been defined are safe enough to try.

AMOD-023
Design authority



130-O4The 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