| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle [2026/07/16 09:25] – nick_dido | dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle [2026/07/23 11:10] (current) – nick_dido |
|---|
| An Operational Lifecycle is a specialization of [[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|Lifecycle]] that applies to an operational subject. | An Operational Lifecycle is a specialization of [[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|Lifecycle]] that applies to an operational subject. |
| |
| The Lifecycle identifies the states, events, transitions, and transition conditions through which the operational subject progresses over time. | The Operational Lifecycle identifies the [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle_state|Operational Lifecycle States]], events, transitions, and transition conditions through which the operational subject progresses over time. |
| |
| The operational subject may include: | Examples of operational subjects include: |
| |
| * An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] | * An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] |
| * A controlled [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] | * A controlled [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] |
| |
| An Operational Lifecycle may include states associated with: | Examples of Operational Lifecycle States include states associated with: |
| |
| * Definition | * Definition |
| * Archiving | * Archiving |
| |
| Events cause or request transitions between lifecycle states. Applicable controls and transition conditions determine whether a transition may occur. | Events cause or request transitions between Operational Lifecycle States. Applicable controls and transition conditions determine whether a transition occurs. |
| |
| An Operational Lifecycle differs from a workflow: | An Operational Lifecycle differs from a workflow: |
| |
| * An Operational Lifecycle describes the states, events, transitions, and transition conditions associated with an operational subject over time | * An Operational Lifecycle describes the Operational Lifecycle States, events, transitions, and transition conditions associated with an operational subject over time |
| * A workflow coordinates activities performed to achieve a bounded result | * A workflow coordinates activities performed to achieve a bounded result |
| |
| An Operational Lifecycle may contain or reference multiple workflows. | An Operational Lifecycle contains or references the workflows used to perform its lifecycle activities. |
| |
| ===== Definition ===== | ===== Definition ===== |
| |
| //[[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|lifecycle]] through which an operational subject progresses from introduction through retirement or decommissioning// | //[[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|lifecycle]] through which an operational subject progresses among defined [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle_state|Operational Lifecycle States]] from introduction through retirement or decommissioning// |
| |
| ===== Source ===== | ===== Source ===== |
| ===== Note ===== | ===== Note ===== |
| |
| The beginning and end of an Operational Lifecycle depend on the operational subject. | The beginning and end of an Operational Lifecycle depend on the operational subject and its governing lifecycle definition. |
| |
| For an Infrastructure Environment, the Operational Lifecycle may begin with definition of the desired state and continue through provisioning, deployment, operation, modification, and decommissioning. | For an Infrastructure Environment, the Operational Lifecycle begins with the state identified by its governing lifecycle definition and continues through the states and transitions defined for that environment. |
| |
| For an Artifact, the Operational Lifecycle may begin with creation and continue through revision, use, preservation, retirement, and archival disposition. | For an Artifact, the Operational Lifecycle begins with the state identified by its governing lifecycle definition and continues through the states and transitions defined for that Artifact. |
| |
| An Operational Lifecycle does not require every subject to pass through the same states or transitions. | An Operational Lifecycle does not require every operational subject to pass through the same Operational Lifecycle States or transitions. |
| |
| The applicable architecture, policies, and requirements determine: | The applicable architecture, policies, and requirements determine: |
| |
| * Permitted lifecycle states | * Permitted [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle_state|Operational Lifecycle States]] |
| * Applicable events | * Applicable events |
| * Permitted transitions | * Permitted transitions |
| ===== Example ===== | ===== Example ===== |
| |
| The Operational Lifecycle of an Infrastructure Environment progresses from definition to provisioning, deployment, operation, modification, and decommissioning. A deployment event initiates the transition from a prepared state to a deployed state when the applicable transition conditions are satisfied. | The Operational Lifecycle of an Infrastructure Environment progresses from definition through provisioning, deployment, operation, modification, and decommissioning. |
| | |
| | A deployment event initiates a transition from a prepared [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle_state|Operational Lifecycle State]] to a deployed Operational Lifecycle State when the applicable transition conditions are satisfied. |
| |
| ---- | ---- |