SAF-Specification icon indicating copy to clipboard operation
SAF-Specification copied to clipboard

Add a Operational Mode VP

Open parkaneric opened this issue 9 months ago • 0 comments

To analyse the SOI from an operational perspective (“system as-operated”) one need to define the modes of operation as stated in ISO29148 (chapter A.2.6.5) for an Operational Concept document. In the moment SAF does not provide appropriate means to address this need. This issue requests the definition and implementation of a dedicated viewpoint as part of the operational domain as per NAF L5 – Logical States. The following SAF VP is proposed: O4_OMOD Operational Mode Viewpoint

Purpose The viewpoint defines modes of operation for the prosed system (such as normal, on-road, degraded, war-time, maintenance, training etc.) which apply not only to the SOI but also to involved personnel. An operational mode defines a potential life-cycle selection for the SOI which has a relevant impact for the SOI’s stakeholder/users w.r.t. to the operations. [tbd]

Applicability The Operational Modes Viewpoint supports the “Business or Mission Analysis Process” activities of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2023 [§ 2.3.5.1] defining Modes at an operational level (e.g., business or mission profile, and operational scenarios). The Operational Modes Viewpoint contributes to Preliminary Life-cycle Concepts and the Business or mission analysis strategy.

Presentation A block definition diagram (BDD) featuring states, and state transitions. Note: References to model elements that are dependent of states, or transitions shall be shown as callout, or compartment notation.

Stakeholder

  • Acquirer
  • Customer
  • Portfolio Manager
  • System Architect

Concerns

  • What operational modes are defined?
  • What operational modes do provide operational capabilities?

Profile Model Reference The following Stereotypes / Model Elements are used in the Viewpoint:

  • StateMachine
  • Operational Mode
  • Transition

Proposed Viewpoint Image

Open Points

  • What relations should be documented from operational modes to processes or capabilities?
  • Should new stereotypes be defined for F3 in order to differentiate between a system state and an operational mode?
  • Concept for triggering / terminating processes from O3_OPRO?

parkaneric avatar Mar 25 '25 10:03 parkaneric