Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.007 Create set of initial operational activities
Goal | Capture existing content that could be candidate operational activities, to avoid unnecessary effort inventing new ones, and maintain consistency with business processes where appropriate |
---|---|
Requirements met by this process step | CSM-SMS Guidance 1.1 a), f) |
Inputs | AMOD-015 Example CONOPS from other railway AMOD-018 Organisation future process framework DB Netz future E2E process map Knowledge of contributors |
Outputs | AMOD-024 Operational activity definition and allocation |
Methodology | Brainstorming using any practical method to identify candidates, then rationalise by agreeing a reasonable level and size of item. Allocate the activities to the operational entity or actor that is believed to carry them out. This activity should be a follow-up to ARCH.002, to sift out candidates from that activity that fit better as operational activities, but have been initially defined as capability. The intention is not to spend a great deal of effort on an exhaustive analysis - we have further opportunities to capture operational activities - but rather to collect together any obvious candidate operational activities that we are already aware of, in one form or other, so that we are not forced to invent new items where we already had something. |
Tools and non-human resources | Basic brainstorming materials Team for Capella |
Cardinality | One-off (no revisions needed) |
Completion criteria | Output view conforms to its modelling rules. The obvious sources of candidate operational activities have been examined and a reasonable set of candidates captured. |
Step done by (Responsible) | Operational concept architect |
Design review | |
Provides input to/assists (Contributes) | Circle/Cluster lead Lead system architect System architect Systems engineer Operations domain expert |
Uses outputs (Informed) | None directly |