U-Class_Payload_2017_SOW_without_comments.docx

Attachment 01 Statement Of Work for Integration and Launch of U-Class Payloads March 27, 2017

Purpose:

The National Aeronautics and Space Administration (NASA) Kennedy Space Center (KSC) requires a U-Class Payload Launch Vehicle Contractor (LVC) that is capable of integrating (including a deployer system) and launching U-Class payload(s) in the FY18 – FY21 timeframe (Aug 2018 - Dec 2020) to a Polar Orbit (90° - 102° inclination). A U-Class payload is a type of miniaturized space research satellite that typically uses commercial, off-the-shelf electronic components. The U-Class payloads flown by NASA are primarily developed by a variety of educational and Governmental organizations. The U-Class payload is a form factor of 10cm X 10cm X 10cm. This document defines the work to be performed by the LVC in support of this effort, including ground rules and assumptions, description, deliverables, and schedule.

Definitions Dispenser system – U-Class Payload and Dispenser

LVC – Launch Vehicle Contractor shall be the provider of the launch service for the mission.

U-Class Payload(s) – The CubeSat(s)

Ground Rules & Assumptions:

1. All communications, data requests, and exchanges between the U-Class Payload(s) and the LVC shall include the NASA Launch Services Program (LSP).

2. The LVC shall provide the mass limitations for each of the U-Class Payload.

3. The LVC shall determine the deployment time of the U-Class Payload(s).

4. The LVC shall select the deployment direction of the U-Class Payload(s).

5. The LVC shall install the U-Class Payload(s) into the LVC provided carrier/dispenser.

6. The LVC shall be responsible for integrating the U-Class Payload(s) and dispenser system(s) onto the launch vehicle.

7. The LVC shall provide telemetry confirmation that the dispenser system(s) has deployed the U-Class Payload.

8. The U-Class Payload(s) will not have any go/no-go or “hold” authority during countdown.

9. The U-Class Payload(s) will not require any electrical interface while on the launch vehicle.

10. The U-Class Payload(s) will be qualified to the environment levels defined in the Interface Control Document (ICD).

11. The U-Class Payload(s) will have no special temperature or humidity requirements.

12. The U-Class Payload(s) will meet material outgassing and cleanliness requirements provided in the ICD.

13. Some U-Class Payloads may be powered up by battery and have RF systems on at launch and remain powered through ascent.

14. NASA will not require launch pad modifications.

15. Some U-Class Payloads may have pressure and/or propulsion systems.

16. NASA will develop the Orbital Debris Anlysis Report (ODAR) for the U-Class Payload missions.

17. The U-Class Payload(s) are required to be launched on domestic (United States) launch vehicle(s).

18. The U-Class Payload(s) shall be launched within 12 months of the first launch date received.

Description:

The Launch Vehicle Contractor shall:

1. Launch and release U-Class Payloads to a Polar Orbit (90° - 102° inclination) with an altitude that would allow the U-Class Payloads to meet Orbital Debris Policy NPR 8715.6A.

2. Provide separation signals from the carrier/dispenser system(s).

3. Provide dispenser door sensor status in the flight telemetry to Launch Vehicle control center.

4. Provide mechanical and electrical integration of the dispenser sytems (U-Class Payload(s) and dispenser(s)) onto the launch vehicle.

5. Provide a list of all documents to be completed by the U-Class Payload Customer(s) to verify that the payload(s) meets launch vehicle requirements.

6. Provide schedule for mission integration cycle.

7. Make appropriate revisions to the ICD between Launch Vehicle and U-Class Payloads.

8. Develop and manage the verification matrix for the ICD requirements.

9. Allow NASA LSP and Auxilary Payload Integration Coordinator (APIC) to attend any integration review for the mission.

10. Coordinate/facilitate all communication and data exchanges for the U-Class payload.

11. Develop and provide an approved MSPSP of all the U-Class Payloads.

12. Provide a non-deploying mass simulator should the U-Class Payload not be ready for integration.

13. Ensure all U-Class Payload requirements have been met in accordance with the Launch Vehicle to U-Class Payload ICD.

14. Provide an approved ODAR for the U-Class Payload manifested on the mission.

15. Provide required dispenser(s) for the U-Class Payload(s) mission(s).

Deliverables / Schedule:

1. Kick-off Meeting: ATP +1 week The LVC shall perform a kick-off meeting with the NASA team, which will be held by teleconference. The purpose of this kick-off meeting is to ensure that expectations are clear, and discuss ground rules and assumptions. At this meeting, the LVC should summarize relevant data generated to date. The teleconference shall not exceed 2 hours in duration.

· Launch Vehicle Selection documentation.

1. Monthly teleconferences (max 1 hour each) shall be arranged to status the progress of this effort. Participants of the monthly teleconferences shall include, but may not be limited to, the LVC, NASA, and the U-Class Payload (CubeSat) team(s).

· Schedule from ATP through Launch.

· Place U-Class Payloads in desired orbit.

· List of Sun Sync Orbit missions from ATP to end of POP.

· Final Flight Report*. (See note below)

*Description/Purpose:

After each launch, a final post-flight report shall be provided. This report will support the NASA Contracting Officer’s mission success determination.

DATA REQUIREMENTS:

(A)This report shall include, in its entirety, the LVC’s internal post-flight report produced for each mission.

This report shall also include:

(i) Orbit elements determined from vehicle guidance data

(ii) Vehicle data indicating payload separation

(iii) Pre-flight prediction of expected flight environments (i.e., acoustic/vibration, quasi-static acceleration, thermal, and pressure). Generic vehicle environmental data may be submitted unless mission unique environmental requirements are identified in the ICD

(iv) Post flight determination of actual flight environments

(v) Explanation of significant differences between the predicted and actual flight environments

(vi) Payload tracking and telemetry data that is interleaved in the launch vehicle data stream

(B) This report shall also specifically address each ICD orbital parameter and environmental condition using flight data, ground observations, or other data sources.

All deliverables shall be provided electronically via email in PDF format unless otherwise specified. All deliverables shall be submitted to the NASA technical contact listed below and the Contracting Officer.

Launch Service Milestone Payment Schedule

Milestone/ Payment # Criteria

Estimated Scheduled Date

Percentage (%) of Cumulative Payments Made to Date to be Returned to Government

Note: The Contracting Officer will unilaterally determine the Contractor’s accomplishment and successful completion of each milestone event. The Contracting Officer’s determination of milestone event completion will include, but is not limited to, the accomplishment criteria listed for the major milestone events set forth in the SOW.

* Approval of the final payments (Milestones 5 and 6) will be made in accordance with contract requirements of the SOW and attachment 02, Milestone Deliverable Descriptions and Requirements.

The Contracting Officer will either approve the final payment (Milestone 6) within thirty (30) days after receipt of the Final Flight Report, or withhold the final payment in accordance with the requirements of the Milestone Payment Schedule, “Mission Success Criteria.” The final payments (Milestone 5 and/or 6) shall not be made in the event of a failed mission determination. In the event of a failed mission, the final payments shall be forfeited by the Contractor and is not recoupable.