MO-006b — Operational Lifecycle Initiation

Go to MO-006 — Infrastructure Lifecycle Management

Crucible SHALL designate the initial Infrastructure Deployment as the first stage of the assigned Operational Lifecycle.

This requirement derives from:

• MO-006 — Infrastructure Lifecycle Management

The Original Requirement states:

The system SHALL support infrastructure lifecycle management from initial deployment through retirement.[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 assigned Operational Lifecycle.

The separate requirements derived from MO-006 address:

• MO-006a — Operational Lifecycle Assignment
• MO-006c — Current Lifecycle State Determination
• MO-006d — Lifecycle Transition Execution
• MO-006e — Infrastructure Environment Retirement

The Original Requirement identifies initial deployment as the beginning of infrastructure lifecycle management but does not define the lifecycle-initiation relationship.

Without an explicit initiation boundary, an evaluator cannot reliably determine:

• When the assigned Operational Lifecycle begins
• Whether lifecycle management begins before, during, or after the initial Infrastructure Deployment
• Which Infrastructure Deployment constitutes the initial deployment
• Which Infrastructure Environment the initial deployment creates
• Which Operational Lifecycle applies when deployment begins
• Whether pre-deployment planning belongs to the Operational Lifecycle
• Whether a redeployment creates a new Operational Lifecycle
• The Evidence required to demonstrate lifecycle initiation

The phrase from initial deployment embeds a separate lifecycle-initiation obligation within the broader lifecycle-management requirement.

MO-006b:

• Identifies Crucible as the responsible actor
• Identifies the initial Infrastructure Deployment as the lifecycle-initiation stage
• Identifies the assigned Operational Lifecycle as the lifecycle being initiated
• Avoids ambiguity between deployment start and deployment completion by treating the initial Infrastructure Deployment as a lifecycle stage
• Separates lifecycle initiation from lifecycle assignment, current-state determination, transition execution, and Retirement

The initial Infrastructure Deployment begins the realized lifecycle of an Infrastructure Environment.

Designating the initial Infrastructure Deployment as the first stage of the assigned Operational Lifecycle establishes a clear lifecycle boundary without requiring the lifecycle to begin at an ambiguous deployment event.

The initial Infrastructure Deployment can include:

• Selection of the applicable 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 operational state

Lifecycle initiation supports:

• Consistent treatment of the initial Infrastructure Deployment
• Identification of the first lifecycle stage
• Association of deployment Evidence with the Operational Lifecycle
• Determination of subsequent lifecycle states
• Controlled execution of lifecycle transitions
• Reproducibility of lifecycle actions
• Preservation of Provenance
• Maintenance of Traceability
• Generation of auditable Evidence

Pre-deployment planning, design, approval, and preparation can precede the Operational Lifecycle of the realized Infrastructure Environment. Those activities remain governed by their applicable processes and requirements.

A subsequent deployment of the same Infrastructure Environment does not automatically create a new Operational Lifecycle. The applicable lifecycle model determines whether the deployment represents maintenance, restoration, replacement, recreation, or initiation of a new Infrastructure Environment.

This requirement does not assign the Operational Lifecycle. MO-006a establishes lifecycle assignment.

This requirement does not determine the current lifecycle state after initiation. MO-006c establishes current lifecycle state determination.

This requirement does not execute transitions following the initial stage. MO-006d establishes lifecycle transition execution.

This requirement does not establish Retirement. MO-006e establishes Infrastructure Environment Retirement.

This requirement applies to:

• Crucible
• Infrastructure Environments
• Infrastructure Deployments
• Initial Infrastructure Deployments
• Operational Lifecycles
• Operational Lifecycle assignments
• Operational Lifecycle stages
• Lifecycle-initiation records
• Infrastructure Baselines
• Deployment records
• Deployment Platforms
• Operational environments
• Security profiles
• Compliance profiles
• Evidence
• Provenance
• Traceability

Verification confirms that:

1. The Infrastructure Environment is identified
2. The assigned Operational Lifecycle is identified
3. The initial Infrastructure Deployment is identified
4. The identified Infrastructure Deployment creates or first realizes the Infrastructure Environment
5. The initial Infrastructure Deployment is designated as the first stage of the assigned Operational Lifecycle
6. The lifecycle-initiation relationship remains associated with the Infrastructure Environment
7. The initiation record preserves the required Evidence, Provenance, and Traceability

Verification includes:

• Infrastructure Environment inspection
• Operational Lifecycle assignment inspection
• Initial Infrastructure Deployment inspection
• Deployment-record inspection
• Lifecycle-stage inspection
• Lifecycle-initiation record inspection
• Infrastructure Environment identity inspection
• Subsequent-deployment comparison
• Evidence inspection
• Provenance inspection
• Traceability inspection

The verification record identifies:

1. The Infrastructure Environment
2. The assigned Operational Lifecycle
3. The Operational Lifecycle identifier
4. The Operational Lifecycle revision
5. The initial Infrastructure Deployment
6. The Infrastructure Deployment identifier
7. The lifecycle-initiation stage
8. The initiation date and time
9. The lifecycle-initiation record
10. The authority or process responsible for the designation
11. Each conflicting or missing initiation relationship
12. Each identified failure or exception
13. The observed result
14. The generated Evidence

This requirement is realized by:

• OR-001 — Operational Roles
• OR-002 — Deployment Environments
• OR-005 — Distributed Environment Management
• FR-CFG-001 through FR-CFG-005
• FR-DEP-001 through FR-DEP-007
• FR-MC-001 through FR-MC-005
• FR-BAS-001 through FR-BAS-004

• 5. Descriptions, Composition, and Baselines
• 7. Infrastructure and Deployment
• 9. Compliance and Security
• 10. Reproducibility, Provenance, and Traceability

The following pages reference this requirement:

Phase 1 and subsequent phases

Not Assessed

Implementation status requires verification that the current Crucible implementation designates the initial Infrastructure Deployment as the first stage of the assigned Operational Lifecycle.

Draft

This requirement derives from MO-006 in the Crucible System Requirements Specification, Version 1.1 Draft.

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.

Changes to the Statement should preserve the relationship between the initial Infrastructure Deployment and the first stage of the assigned Operational Lifecycle.

The lifecycle-initiation record should identify:

• The Infrastructure Environment identifier
• The Operational Lifecycle identifier
• The Operational Lifecycle revision
• The initial Infrastructure Deployment identifier
• The lifecycle-initiation stage
• The initiation date and time
• The authority or process responsible for the designation
• The applicable Infrastructure Baseline
• The applicable Deployment Platform
• The applicable operational environment
• The associated Provenance
• The associated Traceability
• The supporting Evidence

Material changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.

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.