====== MO-006b — Infrastructure Lifecycle Initiation ====== [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start|Go to MO-006 — Infrastructure Lifecycle Management]] ===== Statement ===== [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL designate the initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] as the first stage of its associated [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] revision. ===== Derived From ===== This requirement derives from: * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:start|MO-006 — Infrastructure Lifecycle Management]] The Original Requirement states: > //The system SHALL support infrastructure lifecycle management from initial deployment through retirement.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] MO-006b preserves the lifecycle-initiation boundary expressed by **from initial deployment** in the Original Requirement by identifying the initial Infrastructure Deployment as the first stage of the associated Operational Lifecycle revision. The separate requirements derived from MO-006 address: * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006a|MO-006a — Operational Lifecycle Association]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006c|MO-006c — Infrastructure Lifecycle State Recording]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006d|MO-006d — Infrastructure Lifecycle Transition Execution]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006e|MO-006e — Infrastructure Environment Retirement]] ===== Rationale ===== The initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] first realizes an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]]. Designating the initial Infrastructure Deployment as the first stage of the associated Operational Lifecycle revision establishes the point at which management of the realized Infrastructure Environment begins. The initial Infrastructure Deployment can include: * Selection of the Infrastructure Baseline * Preparation of deployment inputs * Provisioning of infrastructure resources * Configuration of infrastructure components * Application of security controls * Application of compliance controls * Deployment Validation * Evidence generation * Establishment of the initial lifecycle state Lifecycle initiation supports: * Identification of the first lifecycle stage * Association of deployment records with the Operational Lifecycle revision * Determination of subsequent lifecycle states * Controlled execution of lifecycle transitions * Reproducibility of lifecycle actions * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] * Maintenance of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] Pre-deployment planning, design, approval, and preparation may precede the Operational Lifecycle of the realized Infrastructure Environment. A subsequent deployment does not automatically initiate a new Operational Lifecycle. The governing Operational Lifecycle revision determines whether the deployment represents maintenance, restoration, replacement, recreation, or creation of a new Infrastructure Environment. This requirement does not associate the Operational Lifecycle revision with the Infrastructure Environment. MO-006a addresses that association. This requirement does not record the current lifecycle state after initiation. MO-006c addresses lifecycle-state recording. This requirement does not execute lifecycle transitions following initiation. MO-006d addresses transition execution. This requirement does not retire the Infrastructure Environment. MO-006e addresses Retirement. ===== Applies To ===== This requirement applies to: * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] * Initial Infrastructure Deployments * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycles]] * Operational Lifecycle revisions * Operational Lifecycle stages * Lifecycle-initiation records * Infrastructure Baselines * Deployment records * Deployment Platforms * Operational environments * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] ===== Verification ===== Verification confirms that: - The [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] is identified - The associated [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] identifier and revision are identified - The initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] is identified - The identified Infrastructure Deployment first realizes the Infrastructure Environment - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] designates the initial Infrastructure Deployment as the first stage of the associated Operational Lifecycle revision - The lifecycle-initiation relationship remains associated with the Infrastructure Environment - A subsequent deployment does not initiate a new Operational Lifecycle unless the governing Operational Lifecycle revision requires creation of a new Infrastructure Environment - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Infrastructure Environment, initial Infrastructure Deployment, Operational Lifecycle revision, first lifecycle stage, and initiation record ===== Referenced By ===== The following pages reference this requirement: {{backlinks>.#dido:02-crusible}} ===== Delivery Phase ===== Implemented and Verified. ===== Implementation Status ===== Assess whether the current Crucible implementation designates the initial Infrastructure Deployment of an Infrastructure Environment as the first stage of its associated Operational Lifecycle revision. ===== Requirement Status ===== Review and accept MO-006b as a proposed derived requirement created from the evaluation and decomposition of MO-006 in the Crucible System Requirements Specification, Version 1.1 Draft. ---- ===== Issues ===== The following unresolved issues affect this requirement: Define the criteria used to identify the initial Infrastructure Deployment of an Infrastructure Environment. Define the event at which the initial Infrastructure Deployment first realizes the Infrastructure Environment. Define the first stage of each Operational Lifecycle revision that may govern an Infrastructure Environment. Identify the authority or process responsible for designating the initial Infrastructure Deployment as the first lifecycle stage. Define whether pre-deployment planning, approval, and preparation belong to a separate lifecycle or process. Define when a subsequent deployment creates a new Infrastructure Environment and initiates a new Operational Lifecycle. ---- ===== Notes for Editors ===== This requirement page should retain the stable requirement identifier ''MO-006b''. This page is a leaf requirement page and omits a trailing '':start'' from its namespace. The parent MO-006 page is a non-leaf page and retains a trailing '':start'' in its namespace. Changes to the Statement should preserve: * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor * The initial [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] as the lifecycle-initiation event * The [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] as the lifecycle subject * The associated [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] revision as the governing lifecycle model * The first lifecycle stage as the result of initiation The lifecycle-initiation record should identify: * The Infrastructure Environment identifier * The Operational Lifecycle identifier * The Operational Lifecycle revision * The initial Infrastructure Deployment identifier * The first lifecycle stage * The initiation date and time * The authority or process responsible for the designation * The Infrastructure Baseline * The Deployment Platform * The operational environment * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] Material changes should receive review and should update the verification criteria, source records, and Issues section. To reference this requirement Statement from another wiki page, insert: {{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006:mo-006b#Statement&noheader&nofooter&noeditbtn}} Do not rename this page after an external citation unless a redirect or move plan is in place. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.