Enclosure BB.2 - RTO2 GEO-to-Cislunar Relay Validation.pdf

Enclosure BB.2 – RTO 2

RFP# 80GSFC22R0029

forth in Contract Clause H.10 “Subcategory 2.2 Capability Validation Task Orders - Ordering Process and Firm Fixed Prices.”

2. Validation Subtask and Milestones The milestones described below provide the Government with insight into the Contractor’s path forward to successful completion of this Capability Validation Task Order. Upon successful completion and acceptance of all milestones, the Contactor is eligible to compete for Operational Services Task Order and Mission Integration and Special Studies (MI&SS) task orders.

The Contractor shall validate the Contractor’s owned and operated Space Relay and ground systems to ensure that the quality of service meets or exceeds the requirements of the NSNS SOW and this RTO.

The Contractor shall conduct Capability Validation Milestone (CVM) reviews, for the purpose of assessing programmatic and technical progress and contract performance at key decision points and phases in the Performance of this RTO.

Figure 1 Milestone and Subtask Sequence

The Contractor shall complete all seven milestones within the period of performance for the given service in Table 1 of this RTO.

The CVMs have been grouped into five subtasks as shown in Table 1 and Figure 1.

Contractors can satisfy multiple milestones within the same subtask concurrently.

The Government intends to provide incremental milestone payments upon successful completion and acceptance of the milestones in accordance with the payment schedule identified in Table 2 of this RTO.

The Contractor shall provide data items to be reviewed at the various CVMs in the Contractor’s selected format and, unless specified otherwise, may be provided to NASA via access to an online system. If provided via access to an online system, access must be available from the NASA network.

The Contractor shall meet the NSNS requirements for GEO-to-Cislunar service in accordance with the SOW and this RTO.

The Contractor shall meet the detailed requirements for each milestone described in this RTO.

The Contractor shall host Technical Exchange Meetings (TEM) with the Government throughout each sub-task’s performance. In addition to technical discussions and progress reporting, the TEMs will be used to determine what Government Furnished Equipment (GFE) and Government Furnished Information (GFIs) may be offered and to ensure it is equitably available to all contractors. GFE and GFI (simulators, test tools, etc.), subject to Contractor and government requirements, may be made available for validation assurance.

2.1 Subtask 01

2.1.1 Milestone-01 (CMV-01) – Service Concept

During the service concept phase, the Contractor shall provide the operations concept, system architecture, and other support functions required for communications and navigations services that meet the requirements identified in the NSNS SOW and this RTO for the service being offered. The service concept shall also include an approach to complete all CVMs, including interoperability checks, described in the subsequent subtasks.

The Contractor shall hold a CVM-01 Service Concept success review with the government to demonstrate successful completion of all activities related to the Service Concept phase. The Contractor shall work with the government through periodic technical exchanges to determine readiness for the CVM-01 Service Concept success review.

The Contractor shall provide a CVM-01 Service Concept Data Package (DP) comprised of all Service Concept success review briefings and artifacts related to activities in the Service Concept phase no later than 7 days ahead of the review.

Following the review, the Contractor shall provide updated versions of the CVM-01 DP no later than 7 days after the review.

Upon receipt of the final versions of the CVM-01 DP, the Government will respond in writing with acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone within 7 days. For any conditional acceptance or rejection items, the Government will communicate comments against the deliverable.

The Contractor shall submit updates to the CVM-01 DP responding to the Government’s comments for a reassessment of acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone. Government concurrence with completion of the milestone is required.

2.1.2 Milestone-02 (CVM-02) – Services Requirements

During the Service Requirement phase, the Contractor shall define GEO-to-Cislunar service requirements derived in accordance with the NSNS SOW. The derived requirements shall address functional, performance, interface, and interoperability requirements at the minimum.

The contractor shall develop plans for Service Design, Service Integration, Service Testing, Service Verification, and Service Validation milestones.

The Contractor shall identify major risks and define viable mitigation strategies.

The Contractor shall hold a CVM-02 Service Requirements success review with the government to demonstrate successful completion of all activities related to the Service Requirements phase. The Contractor shall work with the government through periodic technical exchanges to determine readiness for the CVM-02 Service Requirements success review.

The Contractor shall provide a CVM-02 Service Requirements Data Package (DP) comprised of all Service Requirements success review briefings and artifacts related to activities in the Service Requirements phase no later than 7 days ahead of the review.

Following the review, the Contractor shall provide updated versions of the CVM-02 DP no later than 7 days after the review.

Upon receipt of the final versions of the CVM-02 DP, the Government will respond in writing with acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone within 7 days. For any conditional acceptance or rejection items, the Government will communicate comments against the deliverable.

The Contractor shall submit updates to the CVM-02 DP responding to the Government’s comments for a reassessment of acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone. Government concurrence with completion of the milestone is required.

2.1.3 GOVERNMENT ACCEPTANCE SUBTASK 1:

Upon successful completion and acceptance of the Subtask 1 milestones, the Government intends to proceed with issuance of Subtask 2 in accordance with Clause H.10 of the contract.

2.2 Subtask 02

2.2.1 Milestone-03 (CVM-03) – Service Design

During the Service Design phase, the Contractor shall define GEO-to-Cislunar service design that demonstrates compliance with service requirements. The design shall address fulfilment of the functional, performance, interface, and interoperability requirements at the minimum.

The contractor shall mature plans for Service Integration, Service Testing, Service Verification, and Service Validation milestones.

The Contractor shall identify major risks and define viable mitigation strategies.

The Contractor shall perform the Interoperability Check-Design (IC-D) to demonstrate the design supports interoperability in accordance with LN-IS Version 4 and any other proposed commercial standards as well as full compliance with all requirements allocated to IOC (Increment A, Increment B, Increment).

The Contractor shall hold a CVM-03 Service Design success review with the government to demonstrate successful completion of all activities related to the Service Design phase. The Contractor shall work with the government through periodic technical exchanges to determine readiness for the CVM-03 Service Design success review.

The Contractor shall provide a CVM-03 Service Design Data Package (DP) comprised of all Service Design success review briefings and artifacts related to activities in the Service Design phase no later than 7 days ahead of the review.

Following the review, the Contractor shall provide updated versions of the CVM-03 DP no later than 7 days after the review.

Upon receipt of the final versions of the CVM-03 DP, the Government will respond in writing with acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone within 7 days. For any conditional acceptance or rejection items, the Government will communicate comments against the deliverable.

The Contractor shall submit updates to the CVM-03 DP responding to the Government’s comments for a reassessment of acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone. Government concurrence with completion of the milestone is required.

2.2.2 Milestone-04 (CVM-04) – Service Integration

During the Service Integration phase, the Contractor shall perform GEO-to-Cislunar service integration for IOC Increment A at a minimum.

The contractor shall retain compliance with the functional, performance, interface, and interoperability requirements at the minimum during Service Integration.

The contractor shall mature plans for Service Testing, Service Verification, and Service Validation milestones.

The Contractor shall identify major risks and define viable mitigation strategies.

The Contractor shall perform Interoperability Check - Hardware (IC-H) for all applicable operational modes (Communication / Data Services, Navigation Services, etc.) on the ground (Earth). The objective of IC-H is to ensure flight elements, ground elements, and interfaces are at adequate maturity level. The IC-H shall demonstrate that integrated capabilities support end-to-end data flow in accordance with LNIS V4 and proposed commercial standards as well as requirements for IOC Increment A. IC-H checks shall be done with contractor hardware-in-the-loop and government interoperability suite in-the-loop capability.

The Contractor shall hold a CVM-04 Service Integration success review with the government to demonstrate successful completion of all activities related to the Service Integration phase. The Contractor shall work with the government through periodic technical exchanges to determine readiness for the CVM-04 Service Integration success review.

The Contractor shall provide a CVM-04 Service Integration Data Package (DP) comprised of all Service Integration success review briefings and artifacts related to activities in the Service Integration phase no later than 7 days ahead of the review.

Following the review, the Contractor shall provide updated versions of the CVM-04 DP no later than 7 days after the review.

Upon receipt of the final versions of the CVM-04 DP, the Government will respond in writing with acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone within 7 days. For any conditional acceptance or rejection items, the Government will communicate comments against the deliverable.

The Contractor shall submit updates to the CVM-04 DP responding to the Government’s comments for a reassessment of acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone. Government concurrence with completion of the milestone is required.

2.2.3 GOVERNMENT ACCEPTANCE SUBTASK 2:

Upon successful completion and acceptance of the Subtask 2 milestones, the Government intends to proceed with issuance of Subtask 3 in accordance with Clause H.10 of the contract.

2.3 Subtask 03

2.3.1 Milestone-05 (CVM-05) – Service Test

During the Service Test phase, the Contractor shall establish a comprehensive Service Test plan in collaboration with the government, including identification of target mission platforms for IOC Increment A at a minimum.

The contractor shall perform on orbit GEO-to-Cislunar service testing for IOC Increment A at a minimum.

The contractor shall successfully demonstrate end-to-end Service Testing capability with all necessary flight and ground elements in the loop, for IOC Increment A at a minimum.

The Contractor shall perform Interoperability Check – Flight (IC-F) on-orbit to demonstrate that integrated capabilities support end-to-end data flow with all necessary flight and ground elements and user missions in the loop in accordance with LNIS V4 and proposed commercial standards as well as requirements for IOC Increment A.

The contractor shall complete verification and validation of all requirements allocated to IOC Increment A.

The Contractor shall support additional on-orbit testing beyond the IC-F for IOC Increment A to realize any test opportunities identified in Service Test Plan.

The Contractor shall perform GEO-to-Cislunar service integration for IOC Increment B at a minimum.

The Contractor shall perform Interoperability Check - Hardware (IC-H) for all applicable operational modes (Communication / Data Services, Navigation Services, etc.) on the ground (Earth). The objective of IC-H is to ensure flight elements, ground elements, and interfaces are at adequate maturity level. The IC-H shall demonstrate that integrated capabilities support end-to-end data flow in accordance with LNIS V4 and proposed commercial standards as well as requirements for IOC Increments A and B. IC-H checks shall be done with contractor hardware-in-the-loop and government interoperability suite in-the-loop capability.

The contractor shall retain compliance with the functional, performance, interface, and interoperability requirements at the minimum during Service Testing.

The contractor shall mature plans for Service Verification and Service Validation milestones.

The Contractor shall identify major risks and define viable mitigation strategies.

The Contractor shall hold a CVM-05 Service Test success review with the government to demonstrate successful completion of all activities related to the Service Test phase. The Contractor shall work with the government through periodic technical exchanges to determine readiness for the CVM-05 Service Test success review.

The Contractor shall provide a CVM-05 Service Test Data Package (DP) comprised of all Service Test success review briefings and artifacts related to activities in the Service Test phase no later than 7 days ahead of the review.

Following the review, the Contractor shall provide updated versions of the CVM-05 DP no later than 7 days after the review.

Upon receipt of the final versions of the CVM-05 DP, the Government will respond in writing with acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone within 7 days. For any conditional acceptance or rejection items, the Government will communicate comments against the deliverable.

The Contractor shall submit updates to the CVM-05 DP responding to the Government’s comments for a reassessment of acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone. Government concurrence with completion of the milestone is required.

2.3.2 GOVERNMENT ACCEPTANCE SUBTASK 3:

Upon successful completion and acceptance of the Subtask 3 milestone, the Government intends to proceed with issuance of Subtask 4 in accordance with Clause H.10 of the contract.

2.4 Subtask 04

2.4.1 Milestone-06 (CVM-06) – Service Verification

During the Service Verification phase, the Contractor shall establish a comprehensive Service Test plan in collaboration with the government, including identification of target mission platforms for IOC Increment B at a minimum.

The contractor shall perform on orbit GEO-to-Cislunar service testing for IOC Increment B at a minimum.

The contractor shall successfully demonstrate end-to-end Service Testing capability with all necessary flight and ground elements in the loop, for IOC Increment B at a minimum.

The Contractor shall perform Interoperability Check – Flight (IC-F) on-orbit to demonstrate that integrated capabilities support end-to-end data flow with all necessary flight and ground elements and user missions in the loop in accordance with LNIS V4 and proposed commercial standards as well as requirements for IOC Increments A and B.

The contractor shall complete verification and validation of all requirements allocated to IOC Increment A and Increment B.

The Contractor shall support additional on-orbit testing beyond the IC-F for IOC Increment B to realize any test opportunities identified in Service Test Plan.

The Contractor shall perform GEO-to-Cislunar service integration for IOC Increment C.

The Contractor shall perform Interoperability Check - Hardware (IC-H) for all applicable operational modes (Communication / Data Services, Navigation Services, etc.) on the ground (Earth). The objective of IC-H is to ensure flight elements, ground elements, and interfaces are at adequate maturity level. The IC-H shall demonstrate that integrated capabilities support end-to-end data flow in accordance with LNIS V4 and proposed commercial standards as well as requirements for all IOC Increments A, B and C. IC-H checks shall be done with contractor hardware-in-the-loop and government interoperability suite in-the-loop capability.

The contractor shall retain compliance with the functional, performance, interface, and interoperability requirements at the minimum during Service Verification.

The contractor shall mature plans for Service Validation milestone.

The Contractor shall identify major risks and define viable mitigation strategies.

The Contractor shall hold a CVM-06 Service Verification success review with the government to demonstrate successful completion of all activities related to the Service Verification phase. The Contractor shall work with the government through periodic technical exchanges to determine readiness for the CVM-06 Service Verification success review.

The Contractor shall provide a CVM-06 Service Verification Data Package (DP) comprised of all Service Verification success review briefings and artifacts related to activities in the Service Verification phase no later than 7 days ahead of the review.

Following the review, the Contractor shall provide updated versions of the CVM-06 DP no later than 7 days after the review.

Upon receipt of the final versions of the CVM-06 DP, the Government will respond in writing with acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone within 7 days. For any conditional acceptance or rejection items, the Government will communicate comments against the deliverable.

The Contractor shall submit updates to the CVM-06 DP responding to the Government’s comments for a reassessment of acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional concurrence, or non-concurrence with completion of the milestone. Government concurrence with completion of the milestone is required

2.4.2 GOVERNMENT ACCEPTANCE SUBTASK 4:

Upon successful completion and acceptance of the Subtask 4 milestone, the Government intends to proceed with issuance of Subtask 5 in accordance with Clause H.10 of the contract.

2.5 Subtask 05

2.5.1 Milestone-07 (CVM-07) – Service Validation Complete

During the Service Validation phase, the Contractor shall establish a comprehensive Service Test plan in collaboration with the government, including identification of target mission platforms for IOC Increment C.

The contractor shall perform on orbit GEO-to-Cislunar service testing for IOC Increment C.

The contractor shall successfully demonstrate end-to-end Service Testing capability with all necessary flight and ground elements in the loop, for IOC Increment C.

The Contractor shall perform Interoperability Check – Flight (IC-F) on-orbit to demonstrate that integrated capabilities support end-to-end data flow with all necessary flight and ground elements and user missions in the loop in accordance with LNIS V4 and proposed commercial standards as well as requirements for all IOC Increments A, B and C.

The contractor shall complete verification and validation of all requirements allocated to IOC (Increment A, Increment B, Increment C)

The Contractor shall support additional on-orbit testing beyond the IC-F for IOC Increment C to realize any test opportunities identified in Service Test Plan.

The contractor shall retain compliance with the functional, performance, interface, and interoperability requirements at the minimum during Service Validation.

The Contractor shall identify major risks and define viable mitigation strategies.

The Contractor shall hold a CVM-07 Service Validation success review with the government to demonstrate successful completion of all activities related to the Service Validation phase. The Contractor shall work with the government through periodic technical exchanges to determine readiness for the CVM-07 Service Validation success review.

The Contractor shall provide a CVM-07 Service Validation Data Package (DP) comprised of all Service Validation success review briefings and artifacts related to activities in the Service Validation phase no later than 7 days ahead of the review.

Following the review, the Contractor shall provide updated versions of the CVM-07 DP no later than 7 days after the review.

Upon receipt of the final versions of the CVM-07 DP, the Government will respond in writing with acceptance, conditional acceptance, or rejection of the DP as well as concurrence, conditional