Attachment B - InSPA SOW and Payment Milestone Template.docx

Statement of Work Name of Lead Entity In Space Production of [Insert Technology/Product] Principal Investigator:

Period of Performance: Task order issuance thru Month/Day/Year

Note: this Statement of Work (SOW) template is provided to facilitate a full understanding of the work associated with development, integration, delivery, and operations of an InSPA payload on the ISS for Principal Investigators, Payload Developers, and Project Managers with little or no ISS research experience. The proposer is encouraged to review the SOW with their selected Implementation Partner (where applicable) and to tailor the SOW for your specific needs.

1.0 SCOPE

This contract authorizes the contractor to perform one or more phases of the In Space Production Applications (InSPA) program to develop, demonstrate and mature selected in-space production technologies, leading to successful transition to commercial operations on future Commercial LEO Destinations (CLDs) or other LEO platforms. The tasks associated with this contract will mature in-space production concepts that produce high-value items for use on Earth with potential for scalability and capturing sizeable markets, creating new markets, or disrupting existing Earth-based technologies by taking advantage of the unique environment of low-Earth orbit (LEO) through utilization of the International Space Station (ISS).

2.0 OVERVIEW

The work includes design, development and testing of ground and flight unit(s) as well as completion of flight demonstration(s) on the ISS National Lab (NL) or a CLD/platform. The effort includes delivery of all mandatory integration, test, and safety verification data (including ground and flight), and support of real-time operations. The effort also includes delivery of additional data related to system/hardware design, development, test & evaluation to provide NASA with insight into hardware performance and project risk to increase mission success. This includes delivery of post-flight data, project status reports, and briefings documenting lessons learned and the results of product evaluation, including analysis and test by an independent third-party of flight and ground samples.

NASA may offer the support of technical or business experts, aka Space Hardware Experts for Research, Production and Applications (SHERPAs), from within or external to the agency to share lessons learned and accelerate learning. The contractor is not required to accept SHERPA support, but NASA believes it is highly advantageous to mission success and continued government investment.

The effort also includes study of the addressable market to identify customers, mature the business case, and attract non-NASA investment. This includes conducting business development activities to understand customer needs and investor goals, identifying supply chain and CLD partners, and developing a realistic cash flow summary forecast.

This contract does not provide authorization for access to and use of ISS resources. Sponsorship for access to and use of ISS NL resources, where applicable, must be obtained from the operator of the ISS NL through a signed User Agreement or Resource Request Form (RRF). Sponsorship for access to and use of the ISS resources under the NASA allocation, where applicable, is provided via the signed Payload Integration Agreement (PIA).

3.0 OBJECTIVES

The contractor proposes in Phase 1 to [insert summary of proposed technology innovation/product and target markets].

3.1 Mission Objectives (Success Criteria)

Insert the science and/or performance objective(s) for each mission or set of demonstrations on the ISS. Objectives should be measurable and are often set by potential customers or industry standards.

3.2 Phase 1 Objectives (Exit Criteria)

Insert the science and/or performance objective(s) for the entire Phase 1 activity that represents full and complete technology demonstration and sufficient learning to warrant proceeding to the next phase. Objectives should be measurable and are often set by potential customers or industry standards.

4.0 TASK DESCRIPTION

The integration of the payload into the ISS shall be in accordance with:

· SSP 57057 ISS Science, Technology, and Exploration Integration Flow, current revision F

· SSP 51721 ISS Safety Requirements Document, baseline

4.1 Phase 1 - the contractor shall perform the following tasks as part of the Phase 1 award to increase the [technology name] Technology Readiness Level (TRL) to a minimum of level 6 (System prototype Demo in relevant environment). Principal Investigators with little or no experience flying payloads on the ISS should visit NASA center(s) supporting their work to gain familiarity with NASA and ISS processes, tour facilities, and meet personnel. This includes the Marshall Space Flight Center where the Payload Operations & Integration Center (POIC) is located, Johnson Space Center where ISS Program and Mission Control is located, and the Kennedy Space Center and Wallops Flight Facility where limited-life cargo is processed for launch to ISS and following return from ISS.

4.1.1 Conception Phase / Preliminary Project Requirements

a. Conduct a kickoff meeting with NASA and other sponsors/stakeholders to review project implementation and commercialization plans, key personnel, science objectives, schedule, preliminary Concept of Operations (ConOps), and initial assessment of ISS interface and service needs. Additionally, assess needs for government and industry Space Hardware Expertise for Research, Production and Applications (SHERPA) support. Any supporting implementation partners or subcontractors should participate.

Deliverables:

1. Kickoff presentation charts.

4.1.2 Plan and Prepare Phase / Preliminary Project Plan

a. Support development of an Interface Requirements Baseline (IRB) with NASA by providing inputs on environments and hardware interfaces with ISS.

b. Develop an Integrated Milestone Schedule (IMS) that links contractor tasks/milestones with those of the implementation partner and NASA integration team to ensure understanding of data/hardware exchanges.

c. Provide input to the draft PIA, including requests of ISS Program services and resources. Review and concur on the final PIA.

d. Develop a preliminary science requirements document listing science and technology goals with traceability to system performance requirements for pre-flight, in-flight, and post-flight phases, differentiating between individual flights or missions, including but not limited to:

i. Science Traceability Matrix (STM)

ii. Appropriate environmental and handling constraints.

iii. Current 1g State of the Art

iv. Individual Flight or Mission success criteria

v. InSPA Phase 1 exit criteria

b. Complete Phase 0 Safety Technical Interchange Meeting (TIM) with ISS Safety Review Panel (ISRP), as necessary. Include discussion of potential hazards from both nominal and off-nominal operations and failure modes, with the expectation of unexpected results from early demonstrations.

e. Conduct a Preliminary or Initial Design Review (PDR or IDR) with participation from Implementation Partners/Subcontractors, NASA, other stakeholders, and industry experts. Deliver to NASA no later than 1 week prior to the review to a level of detail sufficient to meet NASA’s insight needs, including but not limited to the following data products:

i. Team Members: key scientific/technical personnel and their roles in ground and flight activities

ii. Science goals and hardware performance targets, detailing how each flight or mission demonstration will meet those targets

iii. Preliminary System and Subsystem architecture and pertinent analysis of expected systems performance in microgravity

iv. Communications and Control strategy

v. Listing of expected items for launch and return with associated constraints, and how that relates to meeting the science goals and performance targets

vi. Initial ConOps baseline reflecting on-orbit test protocols and environments. Test protocols should include number and strategy for each attempt and success criteria

vii. Risk Summary and Mitigation Plans Note: Although a PDR is listed as an ISS integration milestone in SSP 57057, its primary purpose is to ensure Mission Success. Attendance should include NASA civil servants and integration contractors, as well as approved external advisors. For guidance, reference NASA Procedural Requirements NPR 7120.5F Chapter 2 (Fig 2-5), and NPR 7123.1C Chapter 5 and Appendix G (Table G-6). These documents are provided for reference only; it is not required to conduct a “formal” PDR as defined in NASA procedures.

f. Deliver a summary of PDR/IDR results, including key decisions and action closure plans.

g. Develop a Safety Data Package (SDP) including Phase I Hazard Reports (HRs) and obtain approval from ISRP. Ensure inclusion of potential hazards from both nominal and off-nominal operations and failure modes, with the expectation of unexpected results from early demonstrations. For payloads with a material rated at THL2 or above, or any catastrophic hazard, the Principal Investigator (PI) and/or Payload Developer (PD) shall attend the ISRP review in person and bring any available ground hardware prototype for inspection by ISRP members. Alternatively, the PI/PD may host the ISRP members at their facility.

h. Develop a brief report on the benefits (or lack thereof) of Parabolic/Suborbital flight testing for risk mitigation and development of team expertise.

i. Develop an initial Commercialization Roadmap documenting the business development strategy (e.g. marketing plan, target markets/customers), business maturation goals for Phase 1, and business case (e.g. unit economics, operating expenses, cash flow, breakeven point).

Deliverables:

1. PIA Inputs

2. Integrated Milestone Schedule

3. Preliminary science requirements document

4. ISRP Phase 0 TIM Charts

5. PDR/IDR data package

6. PDR/IDR Summary including key decisions and action items

7. SDP with approved Phase I HRs.

8. Parabolic/Suborbital flight-testing recommendation report

9. Initial Commercialization Roadmap (charts or document)

4.1.3 Design and Analyze Phase / Baseline Project Plan

a. Develop a functional Engineering Development Unit (EDU).

b. Develop a Science Validation Test (SVT) or equivalent ground testing Test Plan with clear test objectives and success criteria traceable to the science requirements document.

c. Conduct Science Validation Test (SVT) or equivalent ground testing of the EDU.

d. Develop a Report detailing test results and expected changes to the final design.

e. Finalize the science requirements document.

f. Conduct a Critical or Final Design Review (CDR or FDR) with participation from NASA, the organization sponsoring your mission, and stakeholder/industry expert. Deliver to NASA no later than 2 weeks prior to the review to a level of detail sufficient to meet NASA’s insight needs, including but not limited to the following data products:

i. Team Members: key scientific/technical personnel and their roles in ground and flight activities

ii. Science goals and hardware performance targets, detailing how each flight demonstration will meet those targets

iii. Baseline System architecture, including mechanical and electrical diagrams, pertinent analysis of expected systems performance in microgravity, and key differences between the EDU and the final design

iv. Subsystem architecture for key components

v. Communications and Control strategy

vi. Key results from EDU testing

vii. Pre-flight 1g test plans, including vibration and other environments to ensure mission success

viii. Listing of manifested items for launch and return, and associated constraints

ix. Flight hardware shipping and ground handling plans and constraints

x. ConOps reflecting on-orbit test protocols and environments, including step-by-step description of test method, including nominal case and backup crew actions to be taken if operation is not successful. Test protocols should include number and strategy for each attempt and success criteria

· Real-time communications plan, including expected data and video downlink

· Crew actions and design features to enable their support

· Video/imagery requirements and design cues

· Malfunction procedures

xi. Risk Summary and Mitigation Plans Note: Although a CDR is listed as an ISS integration milestone in SSP 57057, its primary purpose is to ensure Mission Success. Attendance should include NASA civil servants and integration contractors, as well as approved external advisors. For guidance, reference NASA Procedural Requirements NPR 7120.5F Chapter 2 (Fig 2-5), and NPR 7123.1C Chapter 5 and Appendix G (Table G-7). These documents are provided for reference only; it is not required to conduct a “formal” CDR as defined in NASA procedures.

g. Deliver a summary of CDR/FDR results, including key decisions and action closure plans.

h. Update SDP with Phase II HRs and gain approval from ISRP. For payloads with a material rated at THL2 or above, or any catastrophic hazard, the Principal Investigator (PI) and/or Payload Developer (PD) shall attend the ISRP review in person and bring a hi-fidelity EDU or flight equivalent hardware for inspection by ISRP members. Alternatively, the PI/PD may host the ISRP members at their facility.

i. Identify initial command and data handling needs and participate in a coordination meeting with NASA.

j. Finalize the ConOps.

k. Develop a final hardware design definition document.

l. Develop on-orbit operating procedures, including nominal and off-nominal scenarios and cleanup procedures.

m. Conduct a Readiness Review for an Experiment Verification Test (EVT) or equivalent ground test with flight-like hardware

n. Support development of crew onboard training aids as applicable.

Deliverables:

1. SVT Test Plan.

2. SVT Test Report.

3. Final science requirements document.

4. CDR/FDR Data Package.

5. CDR/FDR Summary Report.

6. SDP with approved Phase II HRs.

7. Submit final C&DH inputs into the Payload Data Library.

8. Final ConOps document.

9. Final hardware design definition document.

10. Procedure inputs to the MSFC operations team by the template date (e.g. 4 weeks prior to Interface Verification Test (IVT) for MSG).

11. EVT Readiness Review Data Package delivered 1 week prior to the review.

4.1.4 Verify Phase / Test and Verification

a. Manufacture and assemble the Flight Unit(s) and flight-like ground unit(s).

b. Conduct all required EVT / Flight Unit hardware/software integrated testing, human systems interface verification testing, and safety testing. EVT shall be completed no later than L-16 weeks to support sponsor confidence assessment on assigned flight.

c. Develop and submit all required data to close safety and interface verifications.

d. Update SDP with Phase III HRs and gain approval from ISRP.

e. Verify part-level manifest data (for launch and return).

Deliverables:

1. EVT or equivalent Test Report(s)

2. Safety and Interface verification data.

3. SDP with approved Phase III HRs.

4.1.5 Deliver Phase / Preparation for Launch and Mission Operations

a. Support development of flight products, as required.

b. Participate in operations console training.

c. Define Time-critical Ground Handling Requirements and finalize science-driven mission constraints.

d. Prepare the science and flight experiment hardware for launch and turnover to the appropriate cargo processing contractor with sufficient samples to support 3 back-to-back-to-back launch attempts.

e. Develop a test plan for the 1g control samples and flight samples.

f. Conduct 1g testing for production of control samples using flight-like ground unit, with real-time video presentation to NASA and SHERPAs.

g. Coordinate with NASA on delivery of flight samples to an independent third-party for testing (including chain-of-custody from LEO platform to delivery).

h. Conduct a Mission Readiness Review (MRR) summarizing readiness of flight hardware, ops products, and technical team with participation by NASA and SHERPAs.

Note: The MRR is not an ISS integration or safety review. Attendance can be limited to NASA civil servants and approved external advisors. For guidance, reference NASA Procedural Requirements NPR 7120.5F Chapter 2 (Fig 2-5), and NPR 7123.1C Chapter 5 and Appendix G (Table G-13). These documents are provided for reference only; it is not required to conduct a “formal” MRR as defined in NASA procedures.

Deliverables:

1. Time-critical Ground Handling Requirements and science-driven mission constraints.

2. Shipping document for cargo turnover.

3. 1g Test Plan

4. 1g Test Report

5. MRR Charts delivered 1 week prior to review

4.1.6 Operate and Post-Ops Phase

a. Support payload on-orbit installation activities.

b. Conduct on-orbit demonstrations to meet performance goals as specified in the approved science requirements document. Note: The contractor shall brief the ISRP on any requested changes to on-orbit procedures or payload configuration that alter the documented hazard controls scheme in the hazard reports or instigate new controls to unforeseen hazards. Consultation with the POI Safety representative may obviate the need for full ISRP participation.

c. Retrieve the flight sample post-landing and conduct testing and evaluation, including comparison with ground samples produced pre-flight.

d. Develop a post-mission evaluation report within 30 days of sample return detailing mission operations, hardware performance, and early conclusions on science results and sample inspection.

e. Develop a final written report including but not limited to a summary of the work performed, description of the payload, all testing and analysis results, lessons learned, and results of business development activities.

Deliverables:

1. Post-mission evaluation report.

2. Flight Samples for third-party testing with chain-of-custody from LEO platform to delivery.

3. Final Report.

4.2 Phase 2 - the contractor shall perform the following tasks as part of the Phase 2 award to increase the Technology Readiness Level (TRL) to level 8.

Pending future submission and selection of a Phase 2 proposal to the NASA Research Announcement NNJ13ZBG001N RESEARCH OPPORTUNITIES FOR ISS UTILIZATION.

4.3 Phase 3 – the contractor shall perform the following tasks as part of the Phase 3 award to increase the Technology Readiness Level (TRL) to level 9.

Pending future submission and selection of a Phase 2 proposal to the NASA Research Announcement NNJ13ZBG001N RESEARCH OPPORTUNITIES FOR ISS UTILIZATION.

5.0 ASSUMPTIONS

a. All activities will be performed at contractor facilities with the exception of specific qualification testing that requires NASA unique facilities (i.e. Acoustic, EMI/EMC, and toxicity, as needed) at Johnson Space Center or Marshall Space Flight Center laboratories. These activities are funded by NASA outside of the value in this task order.

b. [LIST COMPANY ASSUMPTIONS]

6.0 PERFORMANCE STATUS, SCHEDULE, AND REPORTING

6.1 The schedule shown below reflects the contractor’s estimate at time of award based on the defined duration of each task after contract start and subject to flight availability. The actual completion of milestones shall be as defined in the Integrated Milestone Schedule (IMS). The contractor shall obtain COR concurrence with any material changes to the payment milestones in the IMS not driven by changes in the NASA Flight Program.

Tailor to your proposal, including modified grouping of tasks and/or showing multiple instances of repeated milestones where two or more missions or demonstrations are proposed

* Note - Operational schedule delays may occur resulting from schedule changes associated with launches to and from, and operations on-board, the ISS. The contractor shall inform NASA of impacts caused by such operational schedule delays. Such delays alone shall not result in the contractor being declared non-performing under this contract.

6.2 The contractor shall provide monthly progress reports addressing completed and remaining work, including but not limited to business development, science/technology development, on-orbit resource needs, test plans, results of test and analysis, status of ISS verifications and safety products, open issues, and project risks/mitigation plans. These progress reports shall also include any major changes to previous reports, including but not limited to, changes in required ISS resources, safety risks, mission success risks, experiment definition/goals, and schedule. The contractor shall present these monthly progress reports in monthly meetings with the Contracting Officer Representative (COR), Research Portfolio Manager (RPM), and Technical Monitor for the purposes of reviewing contract and/or task status.

6.3 The contractor shall maintain an Integrated Milestone Schedule and participate in regular Payload Integration Manager (PIM) tagups (bi-weekly and then weekly as launch date approaches).

6.4 The contractor shall provide quarterly and end-of-project briefings (face-to-face or virtual) with NASA and other sponsors/stakeholders to provide current status on all aspects of the project.

6.5 The contractor shall participate in the annual ISS Research and Development Conference (RDC) and brief any results and lessons learned that can be publicly shared with the InSPA community.

6.6 The contractor shall provide written payload and technology descriptions to NASA for inclusion in the Space Station Explorer web catalog.

6.7 The contractor shall provide contextualized data to be transmitted to the NASA Enterprise Data Management (EDM) System. Specify public vs. controlled (i.e. proprietary) data access requirements.

6.8 The contractor shall develop a final Commercialization Roadmap report documenting the business development strategy (e.g. marketing plan, target markets/customers) and business case (e.g. unit economics, cash flow, breakeven point).

6.9 The contractor shall ensure all proprietary data is properly marked in all deliverables to NASA.

7.0 PAYMENT MILESTONE SCHEDULE

The project milestones, deliverables and payments shall be as follows:

Expand as appropriate for multiple missions or demonstrations

ISS RDC charts

$ OFI

The total firm fixed price of this contract is $[OFI].