MO-006a — Operational Lifecycle Association

Go to MO-006 — Infrastructure Lifecycle Management

Statement

Crucible SHALL associate each Infrastructure Environment with an identified revision of an Operational Lifecycle.

Derived From

This requirement derives from:

The Original Requirement states:

The system SHALL support infrastructure lifecycle management from initial deployment through retirement.[C1]

MO-006a preserves the lifecycle-management intent of the Original Requirement by requiring each Infrastructure Environment to have an identified Operational Lifecycle revision.

The separate requirements derived from MO-006 address:

Rationale

An identified revision of an Operational Lifecycle defines the lifecycle framework governing an Infrastructure Environment.

The Operational Lifecycle revision provides the basis for determining:

The lifecycle states that apply to the Infrastructure EnvironmentThe permitted transitions between lifecycle statesThe conditions governing each transitionThe activities allocated to CrucibleThe activities allocated to external actors or systemsThe initial lifecycle stateThe terminal lifecycle stateThe approval and control pointsThe records required for lifecycle activitiesDifferent Infrastructure Environments may require different Operational Lifecycle revisions because of differences in:

Mission purposeOperational environmentSecurity classificationCompliance obligationsDeployment PlatformInfrastructure BaselineOrganizational policyOperational authorityMaintenance modelRetirement and disposition requirementsIdentifying the Operational Lifecycle revision supports:

Consistent lifecycle executionDetermination of the current lifecycle stateControlled lifecycle transitionsLifecycle-specific verificationReproducibility of lifecycle actionsPreservation of ProvenanceMaintenance of TraceabilityThis requirement establishes the association between an Infrastructure Environment and an Operational Lifecycle revision.

This requirement does not initiate the associated Operational Lifecycle. MO-006b addresses lifecycle initiation.

This requirement does not record the current lifecycle state. MO-006c addresses lifecycle-state recording.

This requirement does not execute lifecycle transitions. MO-006d addresses transition execution.

This requirement does not retire the Infrastructure Environment. MO-006e addresses Retirement.

Applies To

This requirement applies to:

Operational Lifecycle identifiersOperational Lifecycle revisionsLifecycle-association recordsLifecycle statesLifecycle transitionsTransition conditionsOperational environmentsDeployment PlatformsInfrastructure BaselinesSecurity profilesCompliance profilesOrganizational policiesOperational authoritiesEvidenceProvenanceTraceability

Verification

Verification confirms that:

Each Infrastructure Environment is identifiedAn Operational Lifecycle is associated with each Infrastructure EnvironmentThe associated Operational Lifecycle has an identifierThe associated Operational Lifecycle revision is identifiedThe lifecycle association applies to the identified Infrastructure EnvironmentThe lifecycle association distinguishes the governing Operational Lifecycle revision from other available revisionsThe verification record preserves Traceability among the Infrastructure Environment, Operational Lifecycle identifier, Operational Lifecycle revision, association authority, and association record

Referenced By

The following pages reference this requirement:

Delivery Phase

Implementation Status

Requirement Status

Issues

The following unresolved issues affect this requirement:

Notes for Editors

This requirement page should retain the stable requirement identifier MO-006a.

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:

as the responsible actorEach Infrastructure Environment as the lifecycle subjectAn identified Operational Lifecycle revision as the governing lifecycle modelThe association between the Infrastructure Environment and the Operational Lifecycle revisionThe lifecycle-association record should identify:

The Infrastructure Environment identifierThe Operational Lifecycle identifierThe Operational Lifecycle revisionThe effective association conditionThe association date and timeThe authority or process responsible for the associationThe operational environmentThe Deployment PlatformThe security and compliance constraintsThe associated ProvenanceThe associated TraceabilityMaterial 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-006a#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.