Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle [2026/07/16 09:23] – created nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle [2026/07/23 11:10] (current) – nick_dido
@@ Line 5: / Line 5: @@
 ===== Discussion =====
-An Operational Lifecycle describes the progression of an operational subject through the states and activities that govern its use over time.
+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 operational subject may include:
+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.
+Examples of operational subjects include:
   * An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]]
@@ Line 17: / Line 19: @@
   * A controlled [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]]
-An Operational Lifecycle may include activities such as:
+Examples of Operational Lifecycle States include states associated with:
-  * Planning
   * Definition
   * Creation
@@ Line 25: / Line 26: @@
   * Validation
   * Approval
-  * Provisioning
+  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]]
   * Activation
   * Operation
-  * Monitoring
   * Maintenance
   * Modification
@@ Line 38: / Line 38: @@
   * Archiving
-The applicable lifecycle does not need to contain every listed activity. The governed subject and applicable requirements determine the lifecycle activities and states.
+Events cause or request transitions between Operational Lifecycle States. Applicable controls and transition conditions determine whether a transition occurs.
-An Operational Lifecycle differs from an execution workflow:
+An Operational Lifecycle differs from a workflow:
-  * An Operational Lifecycle describes the states and governing activities associated with a 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 a particular sequence of tasks performed to achieve a bounded result
+  * A workflow coordinates activities performed to achieve a bounded result
-An Operational Lifecycle may contain multiple workflows, events, decisions, and state transitions.
+An Operational Lifecycle contains or references the workflows used to perform its lifecycle activities.
 ===== Definition =====
-//lifecycle comprising the states and governing activities 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 =====
@@ Line 57: / Line 57: @@
 ===== Note =====
-The beginning and end of an Operational Lifecycle depend on the subject being governed.
+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 its definition and continue through provisioning, deployment, operation, maintenance, 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 its creation and continue through revision, approval, 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 prescribe a particular process model, workflow engine, deployment method, platform, or implementation technology.
+An Operational Lifecycle does not require every operational subject to pass through the same Operational Lifecycle States or transitions.
-Lifecycle activities may be automated, manually performed, or divided between automated and manual controls.
+The applicable architecture, policies, and requirements determine:
+  * Permitted [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle_state|Operational Lifecycle States]]
+  * Applicable events
+  * Permitted transitions
+  * Transition conditions
+  * Responsible actors
+  * Required records
+The term does not prescribe a particular process model, workflow engine, deployment method, platform, or implementation technology.
 ===== Example =====
-The Operational Lifecycle of an Infrastructure Environment includes defining its desired state, provisioning its resources, deploying required components, validating the resulting environment, operating and monitoring it, applying controlled changes, and decommissioning it when it is no longer required.
+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.
 ----