MO-002a — Maximum Platform Deployment Duration

Go to MO-002 — Reduced Platform Deployment Timelines

Crucible SHALL complete the selected Platform Deployment within the maximum Deployment Duration specified by the applicable Acceptance Criteria.

This requirement derives from:

• MO-002 — Reduced Platform Deployment Timelines

The Original Requirement states:

Crucible SHALL reduce platform deployment timelines from months to days or hours through automation.[C2]

MO-002a preserves the portion of the Original Requirement that establishes a target duration for completing a Platform Deployment.

The separate requirement derived from MO-002 addresses:

• MO-002b — Platform Deployment Duration Reduction

The Original Requirement uses from months to days or hours without identifying:

• The maximum permitted Deployment Duration
• The applicable Platform Deployment
• The starting event
• The completion event
• The activities included in the measured duration
• The applicable operational context
• The measurement method
• The treatment of failed, incomplete, interrupted, or repeated deployments
• The Acceptance Criteria used to determine whether the measured duration is acceptable

The terms days or hours provide alternative and unbounded target ranges rather than a measurable performance threshold.

MO-002a:

• Replaces days or hours with a maximum Deployment Duration
• Identifies Crucible as the responsible actor
• Identifies the selected Platform Deployment as the measured activity
• Requires the applicable Acceptance Criteria to specify the maximum permitted Deployment Duration
• Separates the maximum-duration obligation from comparison against an approved Deployment Baseline
• Removes through automation because the phrase prescribes an implementation approach rather than the required outcome

Organizations require predictable Platform Deployment timelines to support development, integration, testing, evaluation, release, recovery, and operational planning.

A qualitative or unbounded target such as days or hours does not establish an objectively verifiable performance obligation. A maximum Deployment Duration provides a measurable limit based on defined measurement boundaries.

The applicable Acceptance Criteria establish:

• The selected Platform Deployment
• The operational context
• The activities included in the measured deployment
• The starting event
• The completion event
• The maximum permitted Deployment Duration
• The measurement method
• The required measurement precision
• The treatment of failed, incomplete, interrupted, or repeated deployments

Different Acceptance Criteria can apply to different:

• Platform types
• Deployment scopes
• Infrastructure sizes
• Computing resources
• Network conditions
• Connected Environments
• Disconnected Environments
• Air-Gapped Environments
• Initial deployments
• Repeated deployments
• Recovery deployments

This requirement establishes an absolute maximum Deployment Duration. It does not require the measured duration to improve upon an approved Deployment Baseline. MO-002b establishes the relative duration-reduction requirement.

This requirement applies to:

• Crucible
• Platform Deployments
• Deployment Duration
• Acceptance Criteria
• Controlled Inputs
• Baseline Composition
• Machine Image construction
• Infrastructure Deployment
• Provisioning
• Compliance Assessment
• Deployment Validation
• Connected Environments
• Disconnected Environments
• Air-Gapped Environments
• CI/CD Pipelines
• Evidence
• Provenance
• Traceability

Verification confirms that:

1. The applicable Acceptance Criteria identify the selected Platform Deployment
2. The applicable Acceptance Criteria identify the Platform Deployment activities included in the measurement
3. The applicable Acceptance Criteria identify a defined starting event
4. The applicable Acceptance Criteria identify a defined completion event
5. The applicable Acceptance Criteria specify the maximum permitted Deployment Duration
6. The measured Deployment Duration begins when the defined starting event occurs
7. The measured Deployment Duration ends when the defined completion event occurs
8. The selected Platform Deployment reaches the state required by the defined completion event
9. The measured Deployment Duration does not exceed the maximum permitted Deployment Duration
10. Failed, incomplete, interrupted, and repeated deployments receive the treatment specified by the applicable Acceptance Criteria

Verification includes:

• Acceptance Criteria inspection
• Platform Deployment scope inspection
• Controlled Input inspection
• Deployment-event inspection
• Starting-time capture
• Completion-time capture
• Elapsed-time calculation
• Platform state inspection
• Deployment-result inspection
• Repeated Platform Deployment tests
• Connected Environment tests
• Disconnected Environment tests
• Air-Gapped Environment tests
• End-to-end CI/CD Pipeline tests

The verification record identifies:

1. The applicable Acceptance Criteria
2. The selected Platform Deployment
3. The operational context
4. The Platform Deployment activities included in the measurement
5. The selected Controlled Inputs
6. The defined starting event
7. The defined completion event
8. The recorded starting time
9. The recorded completion time
10. The measured Deployment Duration
11. The maximum permitted Deployment Duration
12. The treatment of any failed, incomplete, interrupted, or repeated deployment
13. The observed result
14. The generated Evidence

This requirement is realized by:

• OR-001 — Operational Roles
• OR-002 — Deployment Environments
• OR-004 — Concurrent Environment Management
• OR-005 — Distributed Environment Management
• FR-CFG-001 through FR-CFG-005
• FR-IMG-001 through FR-IMG-006
• FR-DEP-001 through FR-DEP-007
• FR-COMP-001 through FR-COMP-010
• FR-DSO-001 through FR-DSO-006
• FR-BAS-001 through FR-BAS-004
• PERF-001 through PERF-005
• KVP-001 — Reduce Environment Deployment Timelines

• 5. Descriptions, Composition, and Baselines
• 6. Machine Images and Image Layers
• 7. Infrastructure and Deployment
• 8. Dependencies and Air Gap Operations
• 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 measurement of the current Crucible implementation against the maximum Deployment Duration specified by the applicable Acceptance Criteria.

Draft

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

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

This page is a leaf requirement page and omits a trailing :start from its namespace.

Changes to the Statement SHALL preserve the maximum Platform Deployment duration intent derived from MO-002.

The applicable Acceptance Criteria should identify:

• The selected Platform Deployment
• The operational context
• The activities included in the measurement
• The starting event
• The completion event
• The maximum permitted Deployment Duration
• The measurement method
• The required measurement precision
• The treatment of failed, incomplete, interrupted, and repeated deployments
• The required 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-002:mo-002a#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.