J1a_1_-_Pathfinder_Technology_Demonstrator_SOW_(Rev1).pdf

i

STATEMENT OF WORK

A REQUEST FOR PROPOSAL ENTITLED

“PATHFINDER TECHNOLOGY DEMONSTRATOR”

March 14, 2016

NASA Ames Research Center Moffett Field, California

Pathfinder Technology Demonstrator (PTD) Statement Of Work ii

Statement of Work

Approved by:

Date Project Manager Pathfinder Technology Demonstrator Project

Project Systems Engineer Pathfinder Technology Demonstrator Project

Program Manager Small Spacecraft Technology Program iii

PTD PROJECT

DOCUMENT CHANGE LOG

Sheet: 1 of 1

REV

LEVEL

DESCRIPTION OF CHANGE

APPROVED

BY

DATE

APPROVED

Rev - Draft

Rev -1

Baseline for review

SOW updated per RFP Q&A refining CDRL details

February 09, 2016

March 14, iv

TABLE OF CONTENTS

1.0 Introduction:

1.1 Scope of Work:

1.2 Project Authority, Governance Structure, Management structure

1.3 WBS Baseline

1.4 Safety and Mission Assurance

Compliance Documents:

Reference Documents:

2.0 Description of Tasks/Technical Requirements:

2.1 TASK 1: Requirements Phase: ATP – SRR

ATP Kick-Off Meeting

SRR

2.2 TASK 2: Design Phase: Post SRR - PDR/CDR

Design Phase Preliminary Design Review/Critical Design Review (PDR/CDR)

2.3 TASK 3: Implementation Phase: Post PDR/CDR – SIR/PER

Post PDR/CDR System Integration Review (SIR)/Pre-Environmental Review (PER)

2.4 TASK 4: Integration and Test Phase: Post SIR/PER – ORR/PSR Post SIR/PER Operational Readiness Review (ORR)/Pre-Ship Review (PSR)

2.5 TASK 5: Engineering and Operations Support

2.6 Option 1: First Flight Payload Integration Assessment

2.7 Option 2: First Flight Payload Integration Activity

2.8 Option 3: Second Flight Assessment: ATP – ΔSRR

2.9 Option 4: Second Flight Bus Delivery and Support

Option 4: Task 1: Second Flight Bus Delivery Option 4: Task 2: Engineering and Operations Support

2.10 Option 5: Third Flight Assessment: ATP – ΔSRR

2.11 Option 6: Third Flight Bus Delivery and Support

Option 6: Task 1: Third Flight Bus Delivery Option 6: Task 2: Engineering and Operations Support

2.12 Option 7: Fourth Flight Assessment: ATP – ΔSRR

2.13 Option 8: Fourth Flight Bus Delivery and Support

Option 8: Task 1: Fourth Flight Bus Delivery Option 8: Task 2: Engineering and Operations Support

2.14 Option 9: Fifth Flight Assessment: ATP – ΔSRR

2.15 Option 10: Fifth Flight Bus Delivery and Support

Option 10: Task 1: Flight Bus Delivery Option 10: Task 2: Engineering and Operations Support

2.16 OPTION 11: Globalstar Technology Demonstration

3.0 Period Of Performance

4.0 Required Meetings

5.0 Deliverables:

5.1 Recurring Deliverables

5.2 Support to Project Deliverables

5.3 Hardware Deliverables

5.4 Contractor Data Deliverables

v

TABLES

Table 2-1 Task and Option Summary Table 2-2: SRR Entrance and Success Criteria Table 2-3: Combined PDR/CDR Entrance and Success Criteria Table 2-4: SIR/PER Entrance and Success Criteria Table 2-5: ORR/PSR Entrance and Success Criteria Table 3-1: Work Element Period of Performance Table 4-1: Required Meetings Table 5-1: Recurring Contractor Deliverables Table 5-2: Contractor Support for Project Deliverables Table 5-3: Contractor Hardware Deliverables Table 5-4: Contractor Data Deliverables

FIGURES

Figure 2-1: TASK and OPTION FLOW DIAGRAM

1.0 INTRODUCTION:

The purpose of the Pathfinder Technology Demonstrator (PTD) mission is to demonstrate novel satellite technologies in Low Earth Orbit (LEO).

NASA’s Pathfinder Technology Demonstrator project will test the operation of a variety of novel satellite technologies in low Earth orbit, providing significant enhancements to the performance of these small and effective spacecraft. Cubesats are a class of nanosatellites that use a standard size and form factor. The standard cubesat size uses a "one unit" or "1U" measuring 10x10x10 centimeters and is extendable to larger sizes by “stacking” a number of the 1U blocks to form larger spacecraft. Each Pathfinder Technology Demonstrator mission consists of a 6U cubesat weighing approximately 12 kilograms and measuring approximately 30 centimeters x 25 centimeters x 10 centimeters. Each spacecraft will be equipped with solar arrays that provide power while in orbit.

The PTD project—led by NASA’s Ames Research Center at Moffett Field, California, in collaboration with NASA’s Glenn Research Center in Cleveland, Ohio and potentially other NASA centers or partners—will benefit future missions by demonstrating the operation of new subsystem technologies in orbit. These include spacecraft systems that provide the capability to maneuver small science platforms and send small spacecraft to deep space, novel technologies to stabilize spacecraft and a laser communication system that will greatly increase the amount of data that can be transmitted from the spacecraft to the ground. As small spacecraft increase in mobility and capability, by flight qualifying these subsystems, NASA benefits by having access to low cost, highly capable, science and technology platforms that can operate from the near-Earth to the deep space environment.

The PTD mission is funded through NASA’s Small Spacecraft Technology Program (SSTP), which is chartered to develop and mature technologies to enhance and expand the capabilities of small spacecraft with a particular focus on communications, spacecraft, pointing, power, and autonomous operations. The SSTP is one of nine programs within NASA’s Space Technology Mission Directorate (STMD).

1.1 SCOPE OF WORK:

NASA is interested in a spaceflight qualified 6U cubesat spacecraft to be operated by NASA for its Pathfinder Technology Demonstrator Project to accommodate new spacecraft or other technology subsystems, hereafter referred to as the payload. One flight demonstration is planned for a low thrust propulsion system with potential for additional follow on technology demonstrations. Follow-on missions may include payloads such as higher thrust propulsion systems or technology demonstrations of other spacecraft subsystems or payloads such as optical communications or high precision attitude determination and control systems.

NASA seeks a state of the art satellite that would require little, or preferably no new technology development for the bus sub-systems and desires the most rapid delivery possible for the integrated satellite. Mission-to-mission design variations in the delivered cubesat bus are acceptable, but to minimize recurring cost and to simplify operations, follow-on buses should be as close as possible in design to the initial bus.

Mission operations will be led by NASA personnel at NASA Ames Research Center in partnership with satellite and payload vendors. The baseline approach is for NASA to provide a supporting NEN S-band ground data system solution. A notional PTD Operational Concept document is provided for reference. The Contractor is given the option to provide a Ground Data System (GDS) solution that is compatible with their proposed communication system or to utilize the NASA provided GDS solution. If the Contractor chooses to utilize their ground data system solution, in lieu of the NASA solution, then appropriate requirements and documents referenced in this SOW

CDRL table and the Project L2 Requirements-(7.0 Mission Ops (vendor GDS) worksheet) shall be considered in the overall proposal response. The Contractor shall assume engineering operational support during pre-flight performance testing and flight operations. The Contractor shall propose integration and test of a Globalstar duplex radio as a secondary technology demonstration (Option 11).

This Statement of Work outlines the technical content, documentation, meetings, and deliverables normally expected. Proposers should base their proposal response, schedule and cost on these requirements making a best effort to streamline approaches that meet stated requirements with sufficient consideration to cost and schedule. NASA will consider alternative approaches to meeting the requirements for technical content, documentation, meetings, and deliverables if these approaches still meet the intent of our processes and products while improving quality and/or reduce cost or schedule with no significant increase in risk.

1.2 PROJECT AUTHORITY, GOVERNANCE STRUCTURE, MANAGEMENT STRUCTURE

Small Spacecraft Technology Program (SSTP) authority is delegated from the NASA Associate Administrator for Space Technology through the Ames Center Director to the SSTP Manager within the Flight Projects Directorate at ARC. The PTD Project Manager is responsible for the overall success of the mission and is accountable to the SST Program for the technological success and to the ARC Center Director, through the SST Program, for the programmatic success. The SST Program is responsible for the oversight and insight of the PTD project. The SST Program develops the integrated budgetary requirements and recommendations for the PTD project based on NASA budgetary guidelines. The Program Office establishes operational policies and assures appropriate independent review of PTD, monitors the progress of the project, reports project and mission status to ARC and NASA management, recommends necessary corrective and preventative actions, and provides access to ARC and NASA expertise. The NASA project manager has overall responsibility for the technical integrity, safety and success of each PTD spacecraft development and mission.

1.3 WBS BASELINE

The following Work Breakdown Structure (WBS) using the NASA standard WBS format shall be used by the Contractor for schedule and financial reporting. The Contractor shall be responsible for spacecraft development, fabrication, system integration and testing including integration of a Government Furnished Equipment (GFE) payload, test and delivery, launch vehicle integration support, and mission operations support. A flight-qualified spacecraft with integral payload approved for flight readiness shall be delivered. The Contractor shall have the option to propose the ground data system or delegate this effort to NASA.

The Contractor shall address the following WBS elements in the proposed technical and programmatic responses:

5.0 Globalstar Tech Demo (option)

6.0 Spacecraft

6.1 Project Management

6.2 Systems Engineering

6.3 Safety & Mission Assurance

6.4 Structures and Mechanisms

6.5 Thermal Control System

6.6 Electrical Power System

6.7 Guidance, Navigation and Control (GN&C)

6.8 Propulsion

6.9 Communications

6.10 Command and Data Handling (C&DH)

6.11 Flight Software (FSW)

6.12 Spacecraft Integration and Test (I&T)

7.0 Mission Operations and Support

7.1 Subject Matter Expert Pre-Flight Support

7.2 Subject Matter Expert Flight and Post-Flight Support

8.0 Launch Accommodation Support

8.1 Spacecraft Safety Approval Process Support for Launch Vehicle

8.2 Launch Vehicle Integration Support

9.0 Ground Data System (GDS) (*If Contractor chooses to propose their own GDS solution for this effort, WBS 9.0 can be tailored as appropriate by contractor)

9.1 GDS Management

9.2 GDS Systems Engineering

9.3 Mission Operations Center - Support

9.4 Ground Stations

9.5 Network Infrastructure

9.6 GDS Integration and Test (I&T)

10. System Integration and Test

10.1 I&T Management

10.2 System Integration

10.3 System Testing

10.4 Test Facilities

10.5 Shipping

Options for additional flight units should use the same WBS structure with the assumption that efficiencies will be gained from the initial build to accommodate design changes for a payload that will adhere to the Spacecraft-Payload ICD.

1.4 SAFETY AND MISSION ASSURANCE

The Contractor shall adhere to the SSTP Safety and Mission Assurance Plan.

Compliance Documents:

Included below are compliance documents that the Contractor shall follow:

APR8070.2 (as applicable per the APR8070.2 Tailored Compliance Matrices)

PTD Spacecraft-Payload ICD.docx

PTD L1 and L2 Requirements.xlsx

SSTP Safety and Mission Assurance Plan.docx

NASA General Environmental Verification Standard (GEVS), GSFC-STD-7000 (https://standards.nasa.gov/documents/detail/3315858)

FISMA Federal Information Security Management Act (FISMA) Implementation Project (http://csrc.nist.gov/publications/PubsSPs.html)

NASA-STD-6016 Standard Materials and Processes Requirements for Spacecraft

Reference Documents:

Included below are reference documents that the Contractor should follow or use equivalent procedures:

PTD Thrust Measurement Approach.pdf

PTD Operational Concept.pptx

NEN User’s Guide (http://esc.gsfc.nasa.gov/assets/files/453-UG-002905%282%29.pdf) https://standards.nasa.gov/documents/detail/3315858 http://csrc.nist.gov/publications/PubsSPs.html http://esc.gsfc.nasa.gov/assets/files/453-UG-002905%282%29.pdf

CCSDS Bluebooks reference guides (www.ccsds.org)

NPD 8730.5, NASA Quality Assurance Program

NPR 8735.2, Management of Government Quality Assurance Functions for NASA Contracts

NPD 8730.1, Metrology and Calibration

NPR 1441.1, NASA Records Management Program

NPR 4100.1, NASA Materials Inventory Management Manual

NPR 7120.5, NASA Space Flight Program and Project Management Requirements

APR 6410.1, Material Control, Handling, Preservation and Protection

APR 5100.1, Purchasing

SAE Aerospace Standard (AS) 9100, Quality Management Systems – Aerospace Requirements http://www.ccsds.org/ http://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPD&c=8730&s=5B http://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=8735&s=2B http://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPD&c=8730&s=1C http://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=1441&s=1E http://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=4100&s=1D http://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPR&c=7120&s=5E https://cdms.nasa.gov/assets/docs/centers/ARC/Dirs/APR/APR6410.1.html https://cdms.nasa.gov/assets/docs/centers/ARC/Dirs/APR/APR5100.1.html

2.0 DESCRIPTION OF TASKS/TECHNICAL REQUIREMENTS:

The following tasks are proposed for the project as summarized in Table 2-1.

Table 2-1 Task and Option Summary

TASK# DESCRIPTION SECTION

TASK 1 Requirements Phase: ATP – SRR 2.1

TASK 2 Design Phase: Post SRR - PDR/CDR 2.2

TASK 3 Implementation Phase: Post PDR/CDR – SIR/PER 2.3

TASK 4 Integration and Test Phase: Post SIR/PER – ORR/PSR 2.4

TASK 5 Engineering and Operations Support 2.5

OPTION 1 First Flight Payload Integration Assessment 2.6

OPTION 2 First Flight Payload Integration Activity 2.7

OPTION 3 Second Flight Assessment: ATP – ΔSRR 2.8

OPTION 4 Second Flight Bus Delivery and Support 2.9

OPTION 5 Third Flight Assessment: ATP – ΔSRR 2.10

OPTION 6 Third Flight Bus Delivery and Support 2.11

OPTION 7 Fourth Flight Assessment: ATP – ΔSRR 2.12

OPTION 8 Fourth Flight Bus Delivery and Support 2.13

OPTION 9 Fifth Flight Assessment: ATP – ΔSRR 2.14

OPTION 10 Fifth Flight Bus Delivery and Support 2.15

OPTION 11 Globalstar Technology Demonstration 2.16

Figure 2-1: TASK and OPTION FLOW DIAGRAM

2.1 TASK 1: REQUIREMENTS PHASE: ATP – SRR

ATP Kick-Off Meeting

An Authority to Proceed (ATP) kick-off meeting shall be held at the Contractor facility following contract award. The NASA PTD project manager and systems engineer shall present a project overview, level 1 and level 2 requirements and project milestones. The Contractor shall present an overview of their design approach, processes and systems in place for Safety and Mission Assurance, Configuration Management and Risk Management to ensure that the processes that the Contractor has in place meet the intent of NASA policies and procedures. The Contractor shall provide a facility tour.

SRR

NASA assumes that the Contractor will present a relatively mature spacecraft bus design. At the Systems Requirements Review (SRR), the Contractor shall assess the adequacy of system requirements definition and projected compliance with the PTD Level 2 requirements and the APR8070.2 requirements. Alternative solutions that meet the intent of the requirement will be considered. Particular attention should be given to areas requiring new development or modification and risks associated with the allocated requirements. A summary of the systems engineering process that generated the allocated technical requirements and the systems engineering planning for the next phase will be included. Analyses or trade studies associated with meeting the project requirements should be presented.

The SRR will be a control gate for Key Decision Point B (KDP-B).

Table 2-2: SRR Entrance and Success Criteria

System Requirements Review for Projects and Single-project Programs

Entrance Criteria Success Criteria

1. Project requirements (L2) and applicable APR8070.2 requirements translated into system-specific functional and performance requirements (L3/L4) for each applicable Work Breakdown Structure (WBS).

2. APR8070.2 and L2 Requirements compliance matrix completed with applicable non-compliance justification and approval by NASA.

3. TBD and TBR items are clearly identified with acceptable plans and schedule for their disposition.

4. Inputs to the project level Project Plan, SEMP, Safety and Mission Assurance Plan (SMAP), WBS, Integrated Master Schedule (IMS), Configuration Management Plan (CMP), ODAR and Concept of Operations.

5. Technology development, maturity and assessment plans with Technology Readiness Levels (TRL) identified.

6. Safety issues and risks are identified, characterized with mitigation defined. A Preliminary Risk “watch list” developed.

7. System architecture (HW/FSW) complete, highlighting new development or modifications.

8. Preliminary Technical Performance Measures (TPM) items identified with margins.

9. Preliminary interfaces that will become formal ICD’s are listed.

10. Resource and Acquisition plans with long lead items identified.

11. Updated financial reports

12. System Requirements Review presentation package

1. Definition of a producible system is complete, and fully satisfies all project objectives.

2. System requirements have been logically and fully allocated to each applicable system element, and in turn to their respective subsystem level or below.

3. All allocated requirements (L3/L4) are verifiable and traceable to their corresponding system level requirement (L2).

4. Preliminary verification approaches and acceptance criteria are defined

5. Requisite level of detail and resources are available to support the acquisition and development plan within existing constraints.

6. A mutual understanding of risks and acceptance between the ST Program Office and the project.

7. Approval to proceed with long lead procurement plan.

8. Preliminary engineering development assessment and technical plans to achieve what needs to be accomplished in the next phase.

9. ATP issues/actions closed

Items are to be completed/delivered one week prior to review

2.2 TASK 2: DESIGN PHASE: POST SRR - PDR/CDR

Design Phase

Upon approval of Key Decision Point B (KDP-B), the Contract shall proceed to the design phase (Phase B). A long lead procurement status shall be provided as well as a flight hardware delivery receipt and acceptance process. The Contractor shall refine the mission concept of operations, refine requirements and the corresponding verification matrix, resolve any TBDs, close out any SRR actions, refine the design, demonstrate a solution that meets mission needs with acceptable margins, and demonstrate that any technology development is complete.

Preliminary Design Review/Critical Design Review (PDR/CDR)

The combined spacecraft and mission PDR/CDR demonstrates that the design is clearly beyond PDR maturity level and is sufficiently mature to support proceeding with full-scale fabrication, assembly, integration, flight software coding, and testing. At this review, the Contractor shall establish that it is on track to complete flight and (optional) ground system development; that the payload meets interfaces requirements; and that NASA will adequately perform mission operations to meet mission performance requirements within identified cost and schedule constraints. It is anticipated that the detailed designs will be complete at this review.

The design review process is not considered complete until the SST Program Office provides formal written acknowledgment indicating approval or contingent approval pending satisfactory completion and evaluation of resultant action items (RFA’s) of each review. The PDR/CDR will be a control gate for Key Decision Point C (KDP-C).

Table 2-3: Combined PDR/CDR Entrance and Success Criteria

Preliminary Design Review / Critical Design Review

Entrance Criteria Success Criteria

1. Successful completion of the SRR and responses made to all SRR RFAs. Advisories to be taken under consideration. A timely closure plan exists for open RFAs.

2. A preliminary review agenda and success criteria have been agreed upon.

3. Technical topics shall be addressed at the review:

a. Subsystem design (HW/SW) presented with

PTD mission specific changes.

b. TPM status report with current and projected margins

c. Hardware and flight software fabrication, assembly, integration, test plans and procedures.

d. Technical data information (e.g. schematics, ICDs, and analyses performed to meet PTD requirements).

e. Operational limits and constraints

f. Command and Telemetry list

g. Engineering drawing tree/status

h. Plans for contamination control

i. FSW architecture, release plan and status

(open issues/bugs)

j. Spacecraft-Payload ICD signed, Spacecraft to Ground ICD signed, RF ICD signed.

k. Updated requirements verification matrix/validation plans

l. Updated risk assessment and mitigation

m. Updated Limited Life Items List (LLIL)

n. Inputs to launch safety and ODAR provided.

1. The detailed design is expected to meet the requirements with adequate margins at an acceptable level of risk.

2. The flow down of verifiable requirements is complete and requirements are traceable to mission goals and objectives.

3. Interface control documents are sufficiently matured to proceed with fabrication, assembly, integration, and test, and plans are in place to manage any open items.

4. High confidence exists in the product baseline, and adequate documentation exists or will exist in a timely manner to allow proceeding with fabrication, assembly, integration, and test.

5. The product verification and product validation requirements and plans are complete.

6. The testing approach is comprehensive, and the planning for system assembly, integration, test, and launch site and mission operations is sufficient to progress into the next phase.

7. Adequate technical and programmatic margins and resources exist to complete the development within budget, schedule, and risk constraints.

8. The operational concept is technically sound and includes the flow down of requirements for execution.

9. Risks to mission success are understood and credibly assessed, and plans and resources exist to effectively manage them.

o. Disposal Plan (including decommissioning or termination)

10. Safety issues and mission assurance have been adequately addressed in system and operation designs.

Activities and items are to be completed/delivered one week prior and reviewed at the PDR/CDR

2.3 TASK 3: IMPLEMENTATION PHASE: POST PDR/CDR – SIR/PER

Post PDR/CDR

Upon approval of Key Decision Point C (KDP-C), the Contractor shall proceed to the implementation phase (Phase C). The Contractor shall begin fabrication of test and flight article components, assemblies and subsystems, close out any PDR/CDR actions and finalize test plans and procedures. A NASA flight controller shall be embedded at the Contractor facility for implementation and test support to develop familiarity with spacecraft operations.

System Integration Review (SIR)/Pre-Environmental Review (PER)

At the combined SIR/PER, the Contractor shall ensure that subsystems are ready to be fully integrated as a flight system with an initial comprehensive systems test performed and that the test article (hardware/software), test facility, support personnel, and procedures are ready for testing.

All procurements, GFE and GFI should be received with GSE and facilities ready for use.

Engineering Development Unit (EDU) and qualification testing should be complete. Through a complete and comprehensive evaluation of the project status, the SIR/PER establishes readiness to proceed with environmental testing of the integrated flight system and to demonstrate that the project is on track to complete flight and ground system development and to perform mission operations within identified cost and schedule resources.

Table 2-4: SIR/PER Entrance and Success Criteria

System Integration/Pre-Environmental Review

1. The objectives of the testing have been clearly defined and documented, and all of the test plans, procedures, environment, and configuration of the test item(s) support those objectives. The integration and test plans shall be signed.

2. Configuration of the system under test has been defined and agreed to. All interfaces have been placed under configuration management or have been defined in accordance with an agreed to plan.

3. Applicable functional, unit-level, subsystem, system, and qualification testing has been conducted successfully.

4. SIR/PER-specific materials, such as test plans, test cases and procedures, have been made available to all test participants prior to conducting the review.

5. Mechanical and electrical interfaces for hardware necessary to start system integration have been verified against the interface control documentation and plans for verification of remaining hardware exist.

6. System discrepancies have been identified and disposed in accordance with an agreed-upon plan.

7. Risks have been identified with mitigation plans in place. Accepted risks are documented and reported.

1. The objectives of the testing have been clearly defined and documented, and test plans are completed and approved. Procedures, environment, and configuration of the test item, provide a reasonable expectation that the objectives will be met.

2. Adequate identification and coordination of required test resources are completed.

3. Previous component, subsystem, and system test results form a satisfactory basis for proceeding into planned tests.

4. Risk level is identified and accepted by program/competency leadership as required.

5. Test personnel have received appropriate training in test operation and safety procedures.

8. PDR/CDR actions and key issues have been closed, with advisories taken under consideration.

9. All required test resources such as people (including a designated test director), facilities, test articles, test instrumentation, and other test enabling products have been identified and are available to support required tests.

10. Roles and responsibilities of all test participants are defined and agreed to.

11. Handling and safety requirements have been documented

Activities and items are to be completed/delivered one week prior and reviewed at the SIR/PER

2.4 TASK 4: INTEGRATION AND TEST PHASE: POST SIR/PER – ORR/PSR

Post SIR/PER

Upon approval of Key Decision Point D (KDP-D), the Contractor shall proceed to the system assembly/integration and test phase (Phase D). In this phase, the detailed design of system products shall be implemented with products fabricated, assembled, integrated, and tested. The flight-qualified system shall be delivered in place for storage at the Contractor facility for up to 30 days. NASA will be responsible for shipment of the flight system to the launch services provider.

Operational Readiness Review (ORR)/Pre-Ship Review (PSR)

The ORR examines the actual system characteristics and procedures used in the operation of the end product. It also determines if all operational supporting facilities, equipment, documents, and updated data bases necessary for the normal and contingency operations have been tested, delivered, and installed at the sites to support flight activities. It ensures that all system and support (flight and ground) hardware, software, personnel, procedures, and user documentation accurately reflect the deployed state of the system. NASA shall be responsible for the ORR presentation package and applicable documents, with the Contractor providing inputs, applicable documents and any required approvals.

The PSR verifies the completeness of the specific end products in relation to their expected maturity level and assesses compliance to stakeholder expectations. The Contractor shall establish that all flight and applicable ground system verification activities have been successfully completed. The PSR examines the system, its end products, documentation, test data and support verification. It also ensures that the system has sufficient flight readiness to authorize its shipment to the designated storage facility or launch site. The PSR is conducted after successful completion of all verification activities, including environmental and functional performance testing as well as ground system and network compatibility testing.

Table 2-5: ORR/PSR Entrance and Success Criteria

Operational Readiness Review/Pre-Ship Review

1. A preliminary agenda has been coordinated prior to the ORR/PSR.

2. The following technical topics shall be addressed at the review:

1. Required tests and analyses are complete and indicate that the system will perform properly in the expected operational environment.

2. Risks are known and manageable.

3. System meets the established acceptance criteria.

a. Product verification results;

b. Product validation results;

c. Documentation that the delivered system complies with the established acceptance criteria;

d. Documentation that the system will perform properly in the expected operational environment;

e. Technical data package updated to include all test results;

f. Certification package (NASA owned CoFR);

g. Updated risk assessment, outstanding mitigations and accepted risks;

h. Successfully completed previous milestone reviews.

i. Remaining liens or unclosed actions and plans for closure.

j. Shipping and delivery plans

k. Waivers and approvals (e.g. frequency license)

3. Operational Readiness Review (NASA owned)

a. All validation testing has been completed.

b. Test failures and anomalies from validation testing have been resolved and the results incorporated into all supporting and enabling operational products.

c. All operational supporting and enabling products (e.g., facilities, equipment, documents, updated databases) that are necessary for the nominal and contingency operations have been tested and delivered/installed at the site(s) necessary to support operations. Operations handbook has been approved.

d. Training has been provided to the users and operators on the correct operational procedures for the system.

e. Operational contingency planning has been accomplished, and all personnel have been trained.

f. g. Staffing plans

4. Required safe shipping, handling, checkout, and operational plans and procedures are complete and ready for use.

5. Technical data package is complete and reflects the delivered system.

6. The system, including any enabling products, is determined to be ready to be placed in an operational status.

7. All waivers and anomalies have been closed.

8. Systems hardware, software, personnel, and procedures are in place to support operations.

9. Stage 4 frequency license approval expected by

LRR (as applicable).

2.5 TASK 5: ENGINEERING AND OPERATIONS SUPPORT

The Contractor shall provide 320 hours of engineering and operations support as approved by the NASA Contracting Officer and assigned by the NASA Project Manager. Examples of subject matter expert support can include mission unique trade studies, engineering and operational readiness test support, mission simulations, on-console support, on-orbit calibration and checkout support and anomaly resolution.

The Contractor shall budget travel costs for four (4) 1-week trips to NASA Ames by subject matter experts for engineering and operations support.

2.6 OPTION 1: FIRST FLIGHT PAYLOAD INTEGRATION ASSESSMENT

The Contractor shall perform a technical assessment of bus modifications required (if any) to accommodate a payload that will be NASA GFE. The Contractor shall also provide cost and schedule estimates to perform the tasks. Results to be presented to NASA.

2.7 OPTION 2: FIRST FLIGHT PAYLOAD INTEGRATION ACTIVITY

The Contractor shall integrate a payload that will adhere to the Spacecraft-Payload ICD. Assume the payload to be drop-shipped as GFE to the Contractor integration facility, with on-site payload vendor technician support for handling, installation and checkout support of the payload.

2.8 OPTION 3: SECOND FLIGHT ASSESSMENT: ATP – ΔSRR

The Contractor shall perform a technical assessment of changes required to accommodate a payload that will adhere to the Spacecraft-Payload ICD. The Contractor shall also provide cost and schedule estimates to perform the tasks. Results to be presented at a ΔSRR. A KDP-B decision will determine whether Option 4 will be exercised.

2.9 OPTION 4: SECOND FLIGHT BUS DELIVERY AND SUPPORT

Option 4: Task 1: Second Flight Bus Delivery

The Contractor shall deliver a qualified flight bus, without the payload, identical to the original bus delivered in Task 4 of the base contract. The flight-qualified system shall be delivered in place for storage at the Contractor facility for up to 30 days.

Option 4: Task 2: Engineering and Operations Support

The Contractor shall provide 320 hours of engineering and operations support as approved by the NASA Contracting Officer and assigned by the NASA Project Manager. Examples of subject matter expert support can include mission unique trade studies, engineering and operational readiness test support, mission simulations, on-console support, on-orbit calibration and checkout support and anomaly resolution.

The Contractor shall budget travel costs for four (4) 1-week trips to NASA Ames by subject matter experts for engineering and operations support.

2.10 OPTION 5: THIRD FLIGHT ASSESSMENT: ATP – ΔSRR

The Contractor shall perform a technical assessment of bus changes required to accommodate a payload that will adhere to the Spacecraft-Payload ICD. The Contractor shall also provide cost and schedule estimates to perform the tasks. Results to be presented at a ΔSRR. A KDP-B decision will determine whether Option 6 will be exercised.

2.11 OPTION 6: THIRD FLIGHT BUS DELIVERY AND SUPPORT

Option 6: Task 1: Third Flight Bus Delivery

The Contractor shall deliver a qualified flight bus, without the payload, identical to the original bus delivered in Task 4 of the base contract. The flight-qualified system shall be delivered in place for storage at the Contractor facility for up to 30 days.

Option 6: Task 2: Engineering and Operations Support

The Contractor shall provide 320 hours of engineering and operations support as approved by the NASA Contracting Officer and assigned by the NASA Project Manager. Examples of subject matter expert support can include mission unique trade studies, engineering and operational readiness test support, mission simulations, on-console support, on-orbit calibration and checkout support and anomaly resolution.

The Contractor shall budget travel costs for (4) 1-week trips to NASA Ames by subject matter experts for engineering and operations support.

2.12 OPTION 7: FOURTH FLIGHT ASSESSMENT: ATP – ΔSRR

The Contractor shall perform a technical assessment of bus changes required to accommodate a payload that will adhere to the Spacecraft-Payload ICD. The Contractor shall also provide cost and schedule estimates to perform the tasks. Results to be presented at a ΔSRR. A KDP-B decision will determine whether Option 8 will be exercised.

2.13 OPTION 8: FOURTH FLIGHT BUS DELIVERY AND SUPPORT

Option 8: Task 1: Fourth Flight Bus Delivery

The Contractor shall deliver a qualified flight bus, without the payload, identical to the original bus delivered in TASK 4. The flight-qualified system shall be delivered in place for storage at the Contractor facility for up to 30 days.

Option 8: Task 2: Engineering and Operations Support

The Contractor shall provide 320 hours of engineering and operations support as approved by the NASA Contracting Officer and assigned by the NASA Project Manager. Examples of subject matter expert support can include mission unique trade studies, engineering and operational readiness test support, mission simulations, on-console support, on-orbit calibration and checkout support and anomaly resolution.

The Contractor shall budget travel costs for four (4) 1-week trips to NASA Ames by subject matter experts for engineering and operations support.

2.14 OPTION 9: FIFTH FLIGHT ASSESSMENT: ATP – ΔSRR

The Contractor shall perform a technical assessment of bus changes required to accommodate a payload that will adhere to the Spacecraft-Payload ICD. The Contractor shall also provide cost and schedule estimates to perform the tasks. Results to be presented at a ΔSRR. A KDP-B decision will determine whether Option 10 will be exercised.

2.15 OPTION 10: FIFTH FLIGHT BUS DELIVERY AND SUPPORT

Option 10: Task 1: Flight Bus Delivery

The Contractor shall deliver a qualified flight bus, without the payload, identical to the original bus delivered in TASK 4. The flight-qualified system shall be delivered in place for storage at the Contractor facility for up to 30 days.

Option 10: Task 2: Engineering and Operations Support

The Contractor shall provide 320 hours of engineering and operations support as approved by the NASA Contracting Officer and assigned by the NASA Project Manager. Examples of subject matter expert support can include mission unique trade studies, engineering and operational readiness test support, mission simulations, on-console support, on-orbit calibration and checkout support and anomaly resolution.

The Contractor shall budget travel costs for four (4) 1-week trips to NASA Ames by subject matter experts for engineering and operations support.

2.16 OPTION 11: GLOBALSTAR TECHNOLOGY DEMONSTRATION

The Contractor shall procure and integrate a Globalstar duplex modem (GSP-1720), supporting RF and interface hardware and flight software as a secondary communication system for technology demonstration. Software for ground and flight testing shall be developed. The Contractor shall also provide test ground equipment for end to end testing with the Globalstar network. NASA will provide the ground data system and the interface between the NASA mission operations center and the Globalstar terrestrial network for operations. NASA will assume costs associate with Globalstar licensing subscriptions. The Contractor shall provide a technical implementation and test approach that adheres to the relevant PTD level 2 “Globalstar Tech Demo” requirements.

NASA shall choose whether or not to exercise this option at project award. If exercised, the integral design shall be presented at SRR in the baseline design for the flight and spare spacecraft bus.

The Contractor shall provide associated risks, cost and schedule estimates to perform this task.

3.0 PERIOD OF PERFORMANCE

The period of performance for the following tasks are defined in Table 3.1. Task durations are to be supplied by the vendor with a total TASK 1-4 duration not to exceed 18 months. Shorter durations without cost impacts are desirable.

Table 3-1: Work Element Period of Performance

WORK ELEMENT COMPLETION

CRITERIA

PERIOD OF

PERFORMANCE

TASK 1: Requirements Phase:

ATP - SRR

KDP-B Approval ATP + 2 months

TASK 2: Design Phase:

Post SRR - PDR/CDR

KDP-C Approval End TASK 1 + TBS⃰ months

TASK 3: Implementation Phase:

Post PDR/CDR – SIR/PER

KDP-D Approval End TASK 2 + TBS ⃰ months

TASK 4: Integration and Test Phase:

Post SIR/PER – ORR/PSR

KDP-E Approval End TASK 3 + TBS ⃰ months

TASK 5: Engineering and one month Operations Support: SIR/PER-EOM

EOM End TASK 3 + TBS ⃰ months

⃰Contractor to determine and supply the task duration.

4.0 REQUIRED MEETINGS

The following required meetings/milestones are defined:

Table 4-1: Required Meetings

MEETING FREQUENCY/DATE DURATION LOCATION*

Kick-Off Discussion Once, ATP + 1 week 1 Hour Contractor

Monthly Status Telecon Monthly 1 Hour Via Telecon

SRR Once, ATP + TBS⃰⃰⃰⃰⃰⃰ ⃰ months 1 day Contractor

PDR/CDR Once, ATP + TBS⃰⃰⃰⃰⃰⃰ ⃰ months 2 days Contractor

SIR/PER Once, ATP + TBS⃰⃰⃰⃰⃰⃰ ⃰ months 1 day Contractor

ORR/PSR Once, ATP + TBS⃰⃰⃰⃰⃰⃰ ⃰ months 1 day NASA Ames

*Location is the same for Options Milestones **Contractor to determine/supply the duration

5.0 DELIVERABLES:

The Contractor shall deliver the following data items associated with the work performed in this project (unless otherwise noted, document and presentation deliverables may be provided in contractor layout, electronically in MS Office or Adobe PDF format).

5.1 RECURRING DELIVERABLES

The Contractor is responsible for delivering the items listed in Table 5-1 on a periodic basis for the life of the contract and any options exercised.

Table 5-1: Recurring Contractor Deliverables

CDRL

RECURRING

DELIVERABLES

RECURRING

PERIOD

IMPLEMENTATION PLAN

01 Schedule Monthly

• Integrated Master Schedule updates

• Schedule critical path updates

• Schedule variance report for (10 milestones of choice) w/ explanations

01 Costs Monthly • Cost variance report by WBS

01 Risks Monthly

• Technical/Cost/Schedule Risk updates/mitigations (Red/Yellow and any status changed to Green, or Accepted)

01 Technical Report Monthly • Technical progress reports

01 Margins and TPMs Monthly • First delivery at SRR. Monthly updates.

02 Status Weekly

• Weekly quad chart status report/telecom showing Work Accomplished, Work forward, Concerns/Issues, Support Needs

03 LCCE Each KDP

• Life-Cycle Cost Estimate, first submit at ATP, updated at each KDP

5.2 SUPPORT TO PROJECT DELIVERABLES

The Contractor will provide inputs and technical support for administrative, technical, and developmental activities within their scope of responsibility in support of Project-Level deliverables.

Project deliverables requiring contractor support are listed in Table 5-2.

Table 5-2: Contractor Support for Project Deliverables

PROJECT INPUTS IMPLEMENTATION PLAN

Project Plan

Draft due at SRR, signed at PDR/CDR. The Contractor shall provide inputs to the following sections: S&MA, CM, Procurement, Technology Development Plan, IMS milestones and I&T sections.

SEMP

Systems Engineering Management Plan, Section in Project Plan.

NPR 7123.1A describes NASA Systems Engineering Processes documentation. The Contractor shall provide input to these sections appropriate for their organization.

Concept of Operations Plan

Stand-alone summary. Draft at SRR. Signed at CDR. The Contractor shall provide inputs to the ConOps document providing the directed operation of the bus, limitations , constraints, capabilities, etc.

CoFR

ARC Certification of Flight Readiness (CoFR), per NASA Ames Chief Engineer approval. Due at FRR. The Contractor shall provide a status of the bus, open issues, mitigations, waivers, V&V status.

ODAR

Orbital Debris Assessment Report, Draft due at SRR. Final due at PDR/CDR. The Contractor shall provide information on materials and construction of the bus.

Requirements Matrices

Flowed to level 3 or 4 as applicable. Verified at Level 2. V&V (I,D,A,T) specified. Signed at SRR. Updated at PDR/CDR and signed.

V&V Test Plan

Verification and Validation Test Plan to sell off Level 2 requirements. Draft at SRR, Final at SIR/PER.

Spacecraft-Payload ICD

Draft due at SRR, signed by PDR/CDR (Payload Contractor and NASA involvement). The Contractor shall provide any change requests to the ICD and impact assessments.

LV/Spacecraft Safety Package

Draft due LRD – 6 months (TBR by LV provider) Final due LRD – 3 months (TBR by LV provider) The Contractor shall provide inputs for any bus-specific safety related items, such as remove before flight plugs, etc.

ORR presentation package

Operational Readiness Review slides and supporting data, Due at ORR/PSR. The Contractor shall provide inputs providing bus status, open issues, waivers, limitations, constraints, flight rules, etc.

FRR presentation package

Flight Readiness Review slides and supporting data, Due at FRR. The Contractor shall provide inputs providing bus status, open issues, waivers, etc.

5.3 HARDWARE DELIVERABLES

The Contractor shall deliver the items listed in Table 5-3 on or before the dates referenced.

Table 5-3: Contractor Hardware Deliverables

DELIVERABLE DELIVERY DATE AND DESCRIPTION

Spacecraft Systems w/o Payload

1 spacecraft interface simulator for mission operations with updates provided for follow-on bus deliveries. – due CDR + 1month.

1 payload interface simulator (mechanical/electrical) form/fit/function test for each bus delivered– due at CDR + 2 months.

1 flight spare due at PSR of initial bus delivery only.

Spacecraft Systems with Payload

1 qualified flight system (delivery in place) at PSR

Spacecraft System Shipping Container

Due at PSR for each bus delivered.

DELIVERABLE DELIVERY DATE AND DESCRIPTION

Spacecraft System GSE required for LV integration

Due at PSR for each bus delivered.

Full Scale Spacecraft Models

3 Full-scale spacecraft models for project reviews, operations and outreach. Due at CDR of initial bus delivery only.

5.4 CONTRACTOR DATA DELIVERABLES

The Contractor shall deliver the items listed in Table 5-4 on or before the dates referenced.

Table 5-4: Contractor Data Deliverables

CDRL DELIVERABLE DESCRIPTION

SRR,

PDR/CDR,

SIR/PER, PSR

Presentation Package

Presentation packages delivered 1 week prior to review dates as specified in Table 4-1: Required Meetings

Spacecraft System EIDP

End Item Data Package Draft due at SRR, Final due at PSR.

• Spacecraft System Specifications

• Spacecraft System Drawings (MICD/EICD)

• Spacecraft Handling Procedures

• Spacecraft System Limits/Constraints

• Spacecraft System Test Plan/Data/Reports and Scripts

• Spacecraft Requirement Verification Results

• Spacecraft System CMD/TLM Database (due at

PDR/CDR)

Systems Integration and Test Plan

Draft due at SRR, Final due at SIR/PER. Includes spacecraft I&T approach.

Fault Management Document

Draft delivery at PDR/CDR. Final at SIR/PER. Can be in spreadsheet format.

Operator’s Handbook

Spacecraft Operator’s Handbook or equivalent documentation, providing information needed to operate the spacecraft. Draft due at PDR/CDR. Final due at SIR/PER.

12 PTD HW DD250

Form documenting official delivery of the hardware deliverables. Due after HW delivery to launch services provider.

Public Drawings and Illustrations

The Contractor shall provide publically-releasable drawings and illustrations of the spacecraft design (ITAR and proprietary safe).

Patent Rights or New Technology Report

The Contractor shall submit either (1) Patent Rights—Ownership by the Contractor or (2) New Technology Reports in accordance the applicable clauses listed below. A final report shall be submitted listing all reportable items (or certifying that there were no such reportable items), and listing all subcontracts at any tier containing a patent rights clause (or certifying that there were no such subcontracts).

CDRL DELIVERABLE DESCRIPTION

Space to Ground RF ICD

If Contractor is providing the GDS solution, then this document will be their full responsibility. For the default NASA-provided NEN-GDS, NASA will be responsible for this document and Contractor will supply inputs on the radio solution.

Space to Ground Data

ICD

If Contractor is providing the GDS solution, then this document will be their full responsibility. For the default NASA-provided NEN-GDS, NASA will be responsible for this document and Contractor will supply inputs on Consultative Committee for Space Data Systems (CCSDS) Implementation.

GDS to MOC

ICD

If Contractor is providing the GDS solution, then this document will be developed jointly by the contractor and NASA. For the default NASA-provided NEN-GDS, NASA will be responsible for this document.

Spectrum Application

If Contractor is providing the GDS solution, then Spectrum Approval processing will be their responsibility, with NASA support for Concept of Operations areas. For the default NASA-provided NEN-GDS, NASA will be responsible for this document and Contractor will supply inputs on CCSDS Implementation.

FISMA

Compliance Documentation

If Contractor is providing the GDS Solution, they will need to get Federal Information Security Management Act certified for FIPS 199 Moderate level security compliance in order to connect Contractor Supplied GDS to NASA MOC facilities.

Globalstar to Ground ICD

For Option 11, a spacecraft Globalstar to Ground ICD shall be delivered that specifies data formats flowed between the spacecraft Globalstar modem and the NASA operations center. Any extensions to the Command and Telemetry database should be included.

1. ITEM NO. 2. TITLE

01 Monthly Report

3. DESCRIPTION

The Contractor shall provide and present a monthly report to PTD project management including updates for schedule, costs, risks, technical progress, margins and TPMs.

4. DISTRIBUTION

a. QTY / UNIT — 1 electronic copy shall be delivered to each of the recipients identified in the CDRL distribution list.

b. RECIPIENTS c. SHIPPING ADDRESS d. FREQUENCY /

DELIVERY DATE

CO: As noted in the contract. Charts via secure email prior to presentation or posted on MINX.

First delivery at SRR for initial bus and follow-on bus deliveries.

Recurring Monthly.

Second Wednesdays.

COR and CSE: As noted in the delegation letter.

Charts via secure email prior to presentation or posted on MINX.

5. ADDITIONAL INFORMATION / INSTRUCTIONS

Schedule • Integrated Master Schedule updates

• Schedule critical path updates

• Schedule variance report for (10 milestones of choice) w/ explanations Costs • Cost variance report by WBS Risks • Technical/Cost/Schedule Risk updates/mitigations (Red/Yellow and any status changed to Green, or Accepted) Technical Report • Technical progress reports Margins/TPMs • Technical Performance Measures (mass, power, etc)

02 Weekly Status Report

3. DESCRIPTION

The Contractor shall provide and present a weekly report to PTD project management in a Powerpoint Quad format.

4. DISTRIBUTION

a. QTY / UNIT — 1 electronic copy shall be delivered to each of the recipients identified in the CDRL distribution list.

b. RECIPIENTS c. SHIPPING ADDRESS d. FREQUENCY /

DELIVERY DATE

CO: As noted in the contract. Charts via secure email prior to presentation or posted on MINX.

Recurring weekly on Wednesdays, with exception of monthly reporting date for life of the contract.

COR: As noted in the delegation letter.

Charts via secure email prior to presentation or posted on MINX.

5. ADDITIONAL INFORMATION / INSTRUCTIONS

Weekly quad chart status report/telecom showing Work Accomplished, Work forward,…