Enclosure BB.3- RTO.3 Earth Prox and xCislunar Relay Val.pdf

Enclosure BB.3 – RTO 3

RFP# 80GSFC22R0029

Near Space Network (NSN) Services (NSNS)

Representative Task Order (RTO) Contract Number TBD

Validation Task Order Statement of Work

Note: An Offeror will not be considered for award if the Offeror proposes a price greater than the stated validation RTO Not-To-Exceed validation price.

Task Name: Earth Proximity (EP) and xCislunar Space Relay Capability Validation/(Offeror to Identify the proposed subcategory) Task Period of Performance: See Table 1 Not to Exceed Firm Fixed Price: TBD for each proposed Sub-Category

1. Scope of Work NASA’s Near Space Network (NSN) fulfills the essential needs of user missions, empowering them with mission-critical communication and navigation services and enabling the transmission of science and exploration data to and from space. The goal of the Near Space Network Services (NSNS) is to provide NASA with a single avenue to procure commercial communication and navigation services that are secure, reliable, and affordable, so that all NSN mission users will receive the services required by their mission within their latency, accuracy, and availability requirements.

This Representative Task Order (RTO) focuses on Near Space Relay communications and navigation services for the Earth Proximity (EP) and xCislunar regions, defining the required validation activities for secure Space Relay services for those two subcategories.

During execution of this task order, the Contractor shall validate their ability to provide operational services for Relay communication and navigation services to user missions in the EP and xCislunar Service Regions of Near Space, as defined in the NSNS Statement of Work (SOW).

2. Space Relay Services Validation 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 Orders 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 is consistent with Government’s needs for operational support.

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 lifecycle.

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.2 Capability Validation Milestone-02 – Service Requirements During the Service Requirement phase, the Contractor shall define 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,

2.3 Capability Validation Milestone-03 – Service Design

During the Service Design phase, the Contractor shall define the 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 as well as full compliance with requirements.

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,

2.4 Capability Validation Milestone-04 – Service Integration

During the Service Integration phase, the Contractor shall perform service integration.

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 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,

2.5 Capability Validation Milestone-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.

The contractor shall perform on orbit service testing.

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

The Contractor shall perform Interoperability Check – Flight (IC-F) to demonstrate that integrated capabilities support end-to-end data flow with all necessary flight and ground elements and user missions in the as well as retain compliance with requirements.

The contractor shall complete verification and validation of requirement subset (TBD).

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,

2.6 Capability Validation Milestone-06 – Service Verification During the Service Verification phase, the Contractor shall mature a comprehensive Service Test plan in collaboration with the government, including identification of additional target mission platforms.

The contractor shall perform on orbit service testing.

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

The Contractor shall perform Interoperability Check – Flight (IC-F) to demonstrate that integrated capabilities support end-to-end data flow with all necessary flight and ground elements and user missions in the loop as well as retain compliance with requirements.

The contractor shall complete verification and validation of requirements from servicing testing phase and subset allocated to Service Verification phase (TBD).

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,

2.7 Capability Validation Milestone-07 – Service Validation Complete During the Service Validation phase, the Contractor shall mature a comprehensive Service Test plan in collaboration with the government, including identification of additional target mission platforms.

The contractor shall perform on orbit service testing.

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

The Contractor shall perform Interoperability Check – Flight (IC-F) to demonstrate that integrated capabilities support end-to-end data flow with all necessary flight and ground elements and user missions in the loop as well as retain compliance with requirements.

The contractor shall complete verification and validation of all requirements.

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

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 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.