====== MO-002a — Maximum Platform Deployment Duration ====== [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:start|Go to MO-002 — Reduced Platform Deployment Timelines]] ===== Statement ===== [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL complete the selected [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] within the maximum [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] established by the [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]. ===== Derived From ===== This requirement derives from: * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:start|MO-002 — Reduced Platform Deployment Timelines]] The Original Requirement states: > //Crucible SHALL reduce platform deployment timelines from months to days or hours through automation.//[[dido:02-crusible:99-annexes:annex-b:cr-002|[C2]]] MO-002a preserves the portion of the Original Requirement that establishes a maximum duration for completing a Platform Deployment. The separate requirement derived from MO-002 addresses: * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:mo-002b|MO-002b — Platform Deployment Timeline Reduction]] ===== Rationale ===== Organizations require predictable Platform Deployment timelines to support development, integration, testing, evaluation, release, recovery, and operational planning. The phrase **days or hours** does not establish an objectively verifiable performance obligation. A maximum [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] provides a measurable limit based on defined measurement boundaries. The [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] establish: * The selected [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] * The activities included in the measurement * The starting event * The completion event * The maximum permitted Deployment Duration * The measurement conditions * The treatment of failed, incomplete, interrupted, or repeated deployments Separating the maximum duration requirement from the relative duration-reduction requirement permits Crucible to satisfy one requirement while independently passing or failing the other. This requirement does not require the measured Deployment Duration to improve upon an approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]]. MO-002b addresses that outcome. ===== 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:p:platform_deployment|Platform Deployments]] * Selected Platform Deployments * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] * [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] * Platform Deployment activities included in the measurement * Platform Deployment starting events * Platform Deployment completion events * Failed Platform Deployments * Incomplete Platform Deployments * Interrupted Platform Deployments * Repeated Platform Deployments * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped 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 selected [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] is identified - The [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] identify the Platform Deployment activities included in the measurement - The Acceptance Criteria identify the starting event - The Acceptance Criteria identify the completion event - The Acceptance Criteria establish the maximum permitted [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] - Measurement begins when the defined starting event occurs - Measurement ends when the defined completion event occurs - The selected Platform Deployment reaches the state required by the completion event - The measured Deployment Duration does not exceed the maximum Deployment Duration established by the Acceptance Criteria - Failed, incomplete, interrupted, and repeated Platform Deployments receive the treatment established by the Acceptance Criteria - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Acceptance Criteria, the selected Platform Deployment, the measured Deployment Duration, and the verification result ===== Referenced By ===== The following pages reference this requirement: {{backlinks>.#dido:02-crusible}} ===== Delivery Phase ===== Implemented and Verified ===== Implementation Status ===== Measure the current Crucible implementation against the maximum Platform Deployment Duration established by the Acceptance Criteria. ===== Requirement Status ===== Review and accept MO-002a as a proposed derived requirement created from the evaluation and decomposition of MO-002 in the Crucible System Requirements Specification, Version 1.1 Draft. ---- ===== Issues ===== The following unresolved issues affect this requirement: Identify the Platform Deployment activities included in the Deployment Duration measurement. Define the starting event and completion event used to calculate Platform Deployment Duration. Define the maximum permitted Platform Deployment Duration and identify the controlling Acceptance Criteria. Define the measurement conditions, precision, exclusions, and tolerances used to evaluate Platform Deployment Duration. Define how failed, incomplete, interrupted, and repeated Platform Deployments affect the measured Deployment Duration. ---- ===== Notes for Editors ===== 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. The parent MO-002 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 selected [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] as the measured activity * The maximum [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] as the performance constraint * The [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]] as the source of the duration constraint The Acceptance Criteria should identify: * The selected Platform Deployment * The activities included in the measurement * The starting event * The completion event * The maximum permitted Deployment Duration * The measurement conditions * The required measurement precision * Any permitted exclusions or tolerances * The treatment of failed, incomplete, interrupted, and repeated Platform Deployments 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-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. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.