====== Operational Lifecycle ====== [[dido:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]] ===== Discussion ===== 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 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]] * An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]] * An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprint]] * A [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] * A deployed service * A software component * A controlled [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] Examples of Operational Lifecycle States include states associated with: * Definition * Creation * Configuration * Validation * Approval * [[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 * Maintenance * Modification * Recovery * Replacement * Retirement * Decommissioning * Archiving 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 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 An Operational Lifecycle contains or references the workflows used to perform its lifecycle activities. ===== Definition ===== //[[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 ===== Dido Solutions, Inc. and Jackrabbit Consulting, Inc. ===== Note ===== 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 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 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 operational subject to pass through the same Operational Lifecycle States or transitions. 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 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. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.