====== MO-002b — Platform Deployment Duration Reduction ====== [[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]] in less time than the approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] under equivalent measurement conditions. ===== 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-002b preserves the portion of the Original Requirement that requires a reduction in Platform Deployment duration. The separate requirement derived from MO-002 addresses: * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:mo-002a|MO-002a — Maximum Platform Deployment Duration]] ===== Rationale ===== A claim that Crucible reduces Platform Deployment duration requires an approved and measurable comparison point. The approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] records the Platform Deployment process and Deployment Duration used for comparison. Equivalent measurement conditions prevent differences in deployment scope, inputs, resources, environment, or measurement method from producing a misleading comparison. Equivalent measurement conditions can include: * Platform Deployment scope * [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]] * Starting event * Completion event * Included activities * Operational context * Computing resources * Network conditions * Measurement method * Measurement precision * Treatment of failed, incomplete, interrupted, and repeated Platform Deployments This requirement establishes a relative improvement over an approved Deployment Baseline. It does not establish the maximum permitted Deployment Duration. MO-002a addresses the absolute duration limit. ===== 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:d:deployment_baseline|Deployment Baselines]] * Equivalent measurement conditions * [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]] * Platform Deployment scope * Platform Deployment starting events * Platform Deployment completion events * Platform Deployment measurement methods * Failed Platform Deployments * Incomplete Platform Deployments * Interrupted Platform Deployments * Repeated Platform Deployments * [[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 approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] is uniquely identified - The Deployment Baseline identifies the baseline Platform Deployment - The Deployment Baseline records the baseline [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_duration|Deployment Duration]] - The selected [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_deployment|Platform Deployment]] is identified - The baseline and selected Platform Deployments use equivalent measurement conditions - The baseline and selected Platform Deployments use equivalent deployment scopes - The baseline and selected Platform Deployments use equivalent [[dido:99_annexes:annex-b-terms-and-definitions:c:controlled_input|Controlled Inputs]] - The baseline and selected Platform Deployments use equivalent starting and completion events - The baseline and selected Platform Deployments include equivalent measured activities - The baseline and selected Platform Deployments use equivalent measurement methods - The measured Deployment Duration is less than the Deployment Duration recorded by the approved Deployment Baseline - Failed, incomplete, interrupted, and repeated Platform Deployments receive equivalent treatment in the baseline and measured results - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the approved Deployment Baseline, the selected Platform Deployment, the measured Deployment Duration, and the comparison result ===== Referenced By ===== The following pages reference this requirement: {{backlinks>.#dido:02-crusible}} ===== Delivery Phase ===== Implemented and Verified ===== Implementation Status ===== Compare the current Crucible Platform Deployment Duration with the approved Deployment Baseline under equivalent measurement conditions. ===== Requirement Status ===== Review and accept MO-002b 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 approved Deployment Baseline and its controlling source. Define the baseline Platform Deployment process, scope, Controlled Inputs, starting event, completion event, included activities, and Deployment Duration. Define the measurement conditions that must remain equivalent between the baseline and selected Platform Deployments. Define the required amount of Platform Deployment Duration reduction. Define how failed, incomplete, interrupted, and repeated Platform Deployments affect the baseline and measured results. ---- ===== Notes for Editors ===== This requirement page should retain the stable requirement identifier ''MO-002b''. 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 approved [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_baseline|Deployment Baseline]] as the comparison point * Equivalent measurement conditions for the baseline and selected Platform Deployments * A measured Deployment Duration below the baseline Deployment Duration as the required outcome The approved Deployment Baseline should identify: * The Deployment Baseline identifier and revision * The baseline Platform Deployment process * The baseline Platform Deployment scope * The baseline Controlled Inputs * The baseline operational context * The baseline starting event * The baseline completion event * The activities included in the baseline measurement * The baseline measurement method * The baseline measurement precision * The baseline Deployment Duration * 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-002b#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.