CP-2(6) - Contingency Plan | Alternate Processing and Storage Sites
Plan for the transfer of [Selection: all; essential] mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity and sustain that continuity through system restoration to primary processing and/or storage sites.
Conventional "alternate processing sites" are not feasible in orbit. However, spacecraft commonly employ redundant modules or slot in a different satellite from a shared constellation to continue critical functions if the primary asset fails. For example, a vehicle's backup flight computer can control attitude if the primary CPU malfunctions. In a multi-satellite scenario, other nodes in the constellation might temporarily handle data storage or relay tasks. This concept parallels traditional continuity-of-operations, except it is baked into the space architecture from the outset. Ensuring these stand-ins truly mirror the main site's security posture demands rigorous version control for software loads, consistent cryptographic keys, and synchronization procedures to avoid data loss. If the mission design allows for partial re-routing of functionality among multiple platforms, then "alternate sites" can mean the difference between graceful degradation and a complete mission abort.
The [organization] shall plan for the transfer of essential ground-segment functions to alternate processing/storage site(s) (e.g.secondary ground terminal) with minimal or no loss of operational continuity until the primary ground terminal is fully restored (if the architecture supports it).{CP-2(6)}
The [organization] shall plan for the transfer of essential space-segment functions to alternate processing platforms (e.g.proliferated/distributed constellations) with minimal or no loss of operational continuity until the primary node is fully restored (if the architecture supports it).{CP-2(6)}