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.080 Model operational activities and interactions

Goal

Visualise all the operational activities and interactions needed for one operational capability

Capture new operational activities and interactions identified during scenario/process analysis

Requirements met by this process stepCSM-SMS Guidance 1.1a)
EN 50126-1 7.2.2 a)
ISO 15288 6.4.2.3 c 1)
Inputs

AMOD-024 Operational activity definition and allocation

Method for definition of operational activities

OutputsAMOD-028 Operational activities and interaction definitions (single operational capability)
Methodology

After an initial set of operational activities had been defined and allocated (as per AMOD-024), per capability a thorough analysis of operational activities (this activity), operational scenarios and operational processes (ARCH.078 and ARCH.079) is done. The recommended workflow is as follows:

  • Define viewpoint instance: Per operational capability define one instance of AMOD-028 and popolate the related operational activities that belong to the scope of that capability.
  • Define operational process: Inside the instance of AMOD-028 define the operational process and continue with the ARCH.079 and ARCH.078.
  • Iterate through these three activities as needed (ARCH.078, ARCH.079, ARCH.080).

Note: During the analysis of operational scenarios and processes, it may be necessary to create new operational activities and/or interactions. These should be created on AMOD-028.

Note: Method for definition of operational activities

Tools and non-human resourcesTeam for Capella
CardinalityOnce per operational capability.
Completion criteria

The output view conforms to its modelling rules.

The set of operational activities and interactions is safe enough to try.

Design review

ARCH.R.1 Operational capability review

ARCH.R.2 Operational review - consolidated

Step done by (Responsible)System architect
Provides input to/assists (Contributes)

System architect

Systems engineer

Cross-cutting engineer

Operations domain expert

Uses outputs (Informed)None directly
Goal

Visualise all the operational activities and interactions needed for one operational capability

Capture new operational activities and interactions identified during scenario/process analysis

Requirements met by this process stepCSM-SMS Guidance 1.1a)
EN 50126-1 7.2.2 a)
ISO 15288 6.4.2.3 c 1)
Inputs

AMOD-024 Operational activity definition and allocation

Method for definition of operational activities

OutputsAMOD-028 Operational activities and interaction definitions (single operational capability)
Methodology

After an initial set of operational activities had been defined and allocated (as per AMOD-024), per capability a thorough analysis of operational activities (this activity), operational scenarios and operational processes (ARCH.078 and ARCH.079) is done. The recommended workflow is as follows:

  • Define viewpoint instance: Per operational capability define one instance of AMOD-028 and popolate the related operational activities that belong to the scope of that capability.
  • Define operational process: Inside the instance of AMOD-028 define the operational process and continue with the ARCH.079 and ARCH.078.
  • Iterate through these three activities as needed (ARCH.078, ARCH.079, ARCH.080).

Note: During the analysis of operational scenarios and processes, it may be necessary to create new operational activities and/or interactions. These should be created on AMOD-028.

Note: Method for definition of operational activities

Tools and non-human resourcesTeam for Capella
CardinalityOnce per operational capability.
Completion criteria

The output view conforms to its modelling rules.

The set of operational activities and interactions is safe enough to try.

Design review

ARCH.R.1 Operational capability 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