Attachment 01_SOW_Comformed_on-ramp 2023.pdf

VADR RFP ATTACHMENT 02 –SOW 80KSC021R0034 Rev A

ATTACHMENT 01

STATEMENT OF WORK

For

Venture-Class Acquisition of Dedicated and Rideshare (VADR) Launch Services

VADR RFP ATTACHMENT 01 –SOW 80KSC021R0034 Rev A

Table of Contents

1.0 STANDARD LAUNCH SERVICES (CLIN 1)

Scope of Standard Launch Services Planning Program Management Technical Oversight

1.4.1 Approval

1.4.2 Insight

Launch Vehicle Design and Analysis Development and Production Mission Integration Payload Separation Systems Payload Processing Support

Launch Operations

1.10.1 Integration and Checkout

1.10.2 Launch Support

Safety and Quality Contract Documentation Requirements List (CDRL) Public Affairs

2.0 STREAMLINED CUBESAT LAUNCH SERVICES (CLIN 2)

2.1 Scope and Requirements

2.2 Streamlined CubeSat Launch Services Ground Rules

2.3 Streamlined CubeSat Launch Services Requirements

2.4 FCC Consulting Services

2.5 Deliverables

3.0 SPECIAL TASK ASSIGNMENTS (CLIN 3)

Statement of Work

This Statement of Work (SOW) and all documents attached or referenced herein define the Government's requirements for the Contractor to provide launch services in support of NASA's Launch Services Program (LSP). Launch services will include dedicated and rideshare launch service capabilities.

This SOW defines the overall launch service requirements for US Government payloads (hereinafter referred to as 'payloads'). The Contractor shall perform all tasks necessary to safely and reliably launch payloads in accordance with Government-defined mission objectives. The loss of payloads will not be considered a “Mishap” under 8621.1 NASA Procedural Requirements (NPR) for Mishap and Close Call Reporting, Investigating, and Recordkeeping, which is consistent with the NASA Policy Directive (NPD) 8610.23, Launch Vehicle Technical Oversight Policy, modified technical oversight approach.

The Contractor shall provide all Contract Data Requirements List (CDRL) items as described in Attachment 03, Contract Data Requirements List (CDRL).

The Contractor shall comply with the following documents:

a. Range Safety Documentation for the selected launch site as determined by the appropriate governing authority (e.g. Federal Aviation Administration (FAA)).

b. Certification Regarding United States Commercial Provider of Space Transportation

Services (Public Law 105-303, Title II, Section 201).

1.0 STANDARD LAUNCH SERVICES (CLIN 1)

Scope of Standard Launch Services

This SOW defines the Venture-Class Acquisition of Dedicated and Rideshare (VADR) launch services. The Contractor shall provide an FAA licensed launch service for payloads with a risk tolerance of Class D per NPR 8705.4, Risk Classification for NASA Payloads, or payloads that do not have defined risk classification. The Contractor shall perform launch vehicle planning, analysis, design, development, production, integration, and testing required to provide the launch service appropriate to transport the payload to the desired orbit.

The standard launch services described in this section are intended to align with standard commercial practices while still retaining an appropriate level of Government oversight commensurate with a Class D mission and an FAA-licensed launch. The actual mission orbital requirements will be identified at the task order level, will be to a variety of orbits, and may include escape trajectories.

Missions will require one of the following launch types: dedicated, primary (aka anchor) payload on rideshare, or traditional rideshare. Some missions will require a specific type of launch and others will have flexibility for the launch service provider to define its approach to meeting the mission’s requirements.

a. Dedicated: The Government is allocated the full performance capacity of the launch vehicle for sole use by the Government’s payload(s).

b. Rideshare: The Government is allocated a portion of the full performance capability of the launch vehicle for use by the Government’s payload(s). The launch vehicle provider is allowed to utilize excess capacity for other payloads.

i. Traditional rideshare missions are defined as follows: the Government has flexibility on some orbit parameters for the task order mission (to be defined at the task order level); does not control the other mission’s(s’) orbits, order of payload deployment, or the launch schedule; and does not have the right to refuse other payloads on the mission.

ii. Primary rideshare missions are defined as follows: The Government will require, or the Contractor’s approach shall state, that the payload be designated as the primary payload that controls both the schedule (launch day and time) and specific orbit parameters of the launch, including the Government’s payload separation sequence. If the primary payload is not ready on schedule, the Contractor shall not launch without it.

For all rideshare missions, the Contractor shall ensure that there are no compatibility issues that impact NASA payload(s). The Contractor shall provide mass simulators for NASA payload(s), if required by the launch vehicle provider.

Some missions will require a Category 1 certified launch vehicle. This requirement will be determined at the task order level. For missions that require Category 1 certification, the Contractor shall comply with NPD 8610.7D, Launch Services Risk Mitigation Policy for NASA-Owned and/or NASA-Sponsored Payloads/Missions and LSP-PLN-324.01, Launch Vehicle Certification Plan. Information about attaining a NASA Category 1 certification should be coordinated through

LSP.

Planning

The Contractor shall furnish all services necessary to accomplish the contract requirements including: program management, mission integration, payload processing, launch site support, ground and flight system safety, and performance assurance necessary to accomplish the safe and successful launch of payloads to the required orbit conditions within required launch period.

The Contractor shall be responsible for initiating and ultimately obtaining the necessary approval/licensing (e.g., FAA, Federal Communications Commission) to successfully deliver the procured launch service. The Contractor shall be responsible for all integration and Range services in order to successfully deliver the launch service. The Contractor shall make all arrangements with the responsible authorities for the required launch Range authorization and support for vehicle processing; integrated payload/vehicle processing, launch; and launch site maintenance and modifications if required.

The Contractor shall provide logistical supplies, services, and hardware support to the post-production, transportation, and launch base operations of the vehicle system. The Contractor shall provide all necessary services and mission specific elements, including launch vehicle test and flight hardware and software, required to integrate the payload to the launch vehicle system. The

Contractor shall provide all necessary services, test hardware, software, and mission specific elements required to integrate the combined payload and separation system to the launch vehicle system. Such support should include but is not limited to: provision of spares; provision of propellants; liquids, and gases for launch and test; packaging and transportation of the vehicle system; and warehousing and storage.

Limited Government program management and technical insight, in accordance with NPD

8610.23 Attachment C, Class D Mission Launch Vehicle Modified Technical Oversight, will be required in order to assess completion of milestones as defined in Attachment 02 and Attachment

03. NASA seeks to enable the use of commercially accepted practices while still understanding the schedule risks of the launch service used for the mission.

Program Management

The Contractor shall perform the program management tasks required to provide the launch service and satisfy the mission requirements. These tasks shall include as a minimum:

a. Conduct launch vehicle program reviews that provide evidence of launch vehicle maturity towards the contracted launch period and provide the Government with appropriate evidence needed to satisfy milestone payments to the Contractor as defined in Attachment 02 and Attachment 03.

b. Develop and maintain a master schedule and sub-tier schedules.

c. Obtain all applicable licenses, permits, and approvals required by federal, state, and local regulatory agencies; and prepare (or, if necessary, support the Government in preparing, for the payload) and submit any environmental impact statements that may be necessary for the provisioning of the launch service. Approvals required by the payload will be the responsibility of the Government. The Contractor and the Government shall cooperate and support to each other in the process of obtaining, maintaining, and renewing permits and licenses as set forth above.

d. Provide resolution of critical problem areas to minimize or eliminate schedule impacts.

e. Manage all subcontracts and monitor subcontractor activities to a sufficient level of detail to ensure timely delivery of acceptable components.

f. Provide the recommended mission success criteria and determination methodology prior to the launch and the Final Flight Report (VADR 1-14) to enable determination of mission success as defined in the Interface Control Document (ICD) (VADR 1-2). NASA will determine whether the mission is a success or failure based on the application of the mission success criteria as defined in the Section 2.9, Mission Success Criteria of the base contract and the approved mission success criteria and determination methodology in the

ICD.

g. Make provision for insurance to cover liability for possible damage to Government property and third parties in accordance with necessary approval/licensing (i.e., FAA).

h. Pay any taxes and transfer costs required for the delivery of the launch service.

Technical Oversight

While the Contractor shall allow NASA oversight, the Contractor shall ensure necessary steps have been taken that result in mission success per clause 2.9, Mission Success Criteria. The Contractor shall comply with all requirements for Class D missions described in NPD 8610.23C Attachment C, Class D Mission Launch Vehicle Modified Technical Oversight.

Government oversight has two elements: approval and insight. Government approval is defined as: the provision of authority to proceed and/or formal acceptance in limited specified areas.

Where Government approval is required, the Contractor shall submit the necessary documentation to the Contracting Officer and copies to the Contracting Officer’s Representative (COR).

NASA uses its insight to gain an understanding of the mission integration of the unique Government payload to the launch vehicle, to perform program management for associated launch service schedule risks, and to understand the most significant technical risks of the launch service.

In accordance with NPD 8610.23, the Contractor shall provide NASA with insight into any Contractor-initiated fleet or vehicle changes that may impact the common launch vehicle configuration for VADR missions. The Contractor shall accommodate this insight with no increase in contract price.

1.4.1 Approval

As defined in NPD 8610.23C Attachment C, the following areas require Government approval for the VADR missions:

1. Spacecraft-to-launch vehicle interface control documents (ICD)/drawings and requirement waivers.

2. Decisions/resolutions of action items as determined by joint NASA/Contractor mission integration teams.

3. Spacecraft launch commit criteria. (Note: This does not apply to traditional rideshare missions)

4. Spacecraft handling procedures and deviations.

5. Integrated spacecraft/vehicle mate, test, and closeout procedures and planned or real-time deviations, impacting the spacecraft (e.g., handling, spacecraft power-on, or mission specific requirements).

6. Launch countdown procedures and planned or real-time deviations that affect spacecraft interface in the ICD. (Note: This applies only to procedures involving the spacecraft)

7. Anomaly resolutions that affect the spacecraft interface in the ICD.

8. Spacecraft Launch Readiness Go/No-Go. (Note: This does not apply to traditional rideshare missions. For dedicated and primary rideshare missions as defined in section 1.1, the Government will have Go/No-Go authority on launch day for the spacecraft readiness.).

1.4.2 Insight

As defined in NPD 8610.23C, the following areas require Government insight:

1. Baseline vehicle configuration to confirm the common launch vehicle configuration as defined in Attachment 04, Definitions.

2. Production program reviews, plans, and schedules for the VADR missions.

3. Launch Processing Readiness Reviews (pre-ship reviews) for the VADR missions.

4. Major/critical problems affecting the VADR mission's production or launch schedule and their resolutions.

5. Launch site support work schedules and plans for the VADR missions.

6. Contractor-chaired launch readiness review(s) for the VADR missions.

7. Post flight anomaly, as defined by the launch service provider, investigations/closeouts.

8. VADR mission specific hardware design, analysis, manufacture, and test.

9. VADR mission specific software design, analysis, and test.

10. Contractor's spacecraft-to-launch vehicle ICD verification matrix development and closeout for the VADR missions.

11. Baseline and changes to Contractor's risk management, safety and health, and quality management plan/approach.

Launch Vehicle Design and Analysis

The Contractor shall be responsible for the design of the launch vehicle (e.g. structures, mechanisms, fluids/propulsion, electrical/electronics, guidance/navigation/control, flight termination, and software).

The Contractor shall document the analyses required to validate the launch vehicle design to their standards.

NASA will specify the requirements for each mission at the task order level.

Development and Production

The Contractor shall implement a development and qualification program, using Contractor standards, for any new systems required for the launch vehicle including: existing systems that are modified; launch vehicle components not yet qualified; and ground support equipment. The Contractor shall report risks, as defined by the Contractor's risk plan, to the Government.

The Contractor shall manufacture, assemble, test, and transport the launch vehicle and all mission hardware required to provide the launch service and shall provide all materials and equipment necessary for these tasks.

Mission Integration

The Contractor shall provide the necessary services and hardware to integrate the payload to the separation system, the integrated payload assembly (as applicable), and the launch vehicle. The

Contractor shall coordinate with the Government to develop the ICD (VADR 1-2) during integration. The Contractor shall create and maintain an ICD Verification Matrix (VADR 1-3) that includes a verification plan for each requirement in the ICD based on the appropriate method. The Contractor shall perform verification and provide closure evidence for each ICD requirement based upon the verification plan identified in the ICD Verification Matrix upon completion.

The Contractor shall conduct monthly technical mission integration coordination teleconferences with the Government to address technical integration topics and status action items. Beginning at L-12 months, the Contractor shall conduct technical mission integration coordination teleconferences with the Government every two weeks.

The Contractor shall conduct mission integration working group meeting approximately two times a year from mission ATP to launch.

Payload Separation Systems

Separation system interfaces will be specified at the task order level and may include but are not limited to separation ring interfaces, CubeSat interfaces, or other payload interfaces. Launch vehicle to payload interface requirements will be levied at the interface between the separation system and the payload. The Government may elect to provide the separation system at the task order level. In the event NASA provides the separation system, requirements in a. through f. below do not apply to the Contractor.

The following requirements shall apply to the Contractor for the provided launch service:

a. The Contractor shall provide a qualified payload separation system.

b. The Contractor shall conduct, at a location specified by the Government, a mechanical and electrical fit check between the payload separation system and the payload prior to shipment of the payload to the integration site for launch.

c. The ICD shall include requirements necessary for the successful integration of the payload and the separation system.

d. The Contractor shall provide hardware to the payload provider that accurately simulates the mechanical interfaces and dynamic characteristics of the payload separation system, to be used by the payload project during shock and vibration testing. (Note: if applicable, the requirement for separation testing will be included at the task order level)

e. The payload shall be protected from debris generated by the separation system.

f. The separation system shall function in a manner that prevents any re-contact with the payload, including Contractor-provided attach hardware on the payload, by the upper stage or any element of the separation system once separation has been initiated.

g. The Contractor shall initiate the deployment of the payload

h. For all post-separation maneuvers, including a Collision/Contamination Avoidance Maneuver (CCAM) when applicable, the Contractor shall minimize payload contamination and prevent any chance of re-contact with the separated payload.

i. The launch vehicle shall establish and hold the nominal separation attitude and/or spin rate(s) prior to payload separation.

j. The launch vehicle's attitude control system (ACS) shall be disabled immediately prior to payload separation and remain disabled while the launch vehicle sends redundant separation initiation signals to release the payload.

k. The spacecraft separation will be timed and directed in such a way as to avoid near field re-contact with any other spacecraft deployed from the launch vehicle.

Payload Processing Support

The Contractor shall provide a Payload Processing Facility (PPF) that meets ISO 14644-1 Class 8 or better cleanroom to support payload processing operations, pre-integration operations and payload fairing encapsulation operations. The Contractor shall provide cleaning supplies, cleanroom garments, and related supplies for personnel that require access to the cleanroom. The duration of PPF occupancy and facility specifications (i.e., payload lifting/handling requirements, hazardous material accommodations, fueling support services) will be specified at the task order level.

The Contractor shall maintain the contamination environment in the PPF and within the payload fairing such that it meets ISO 14644-1 Class 8 or better. Additional requirements that apply to Contractor-provided flight hardware (i.e., Payload Fairing and Payload Adapter surfaces) may be specified at the task order level.

The Contractor shall provide notification at the Launch Processing Readiness Review (LPRR) (reference Attachment 02, Meetings and Formal Reviews) to coordinate the payload delivery to the integration site or launch site.

The Contractor shall ensure that Contractor-provided hardware does not contaminate the payload.

For example, any thermal and/or acoustic blankets in the payload fairing will be sealed or filtered such that venting of blanket material debris does not contaminate the payload.

The Contractor shall ensure that the PPF includes a control room with the accommodations necessary to operate payload Ground Support Equipment. These accommodations must include harness routing paths and real-time voice and video communication between the control room and payload processing area. For some missions, connectivity between the PPF and launch pad may be required at the task order level.

Launch Operations

The Contractor shall identify and secure a launch site to meet the requirements of the launch service.

1.10.1 Integration and Checkout

The Contractor shall perform the following:

a. Assemble, transport, maintain, checkout, and launch a vehicle that delivers the payload into the ICD required orbit.

b. Provide and make arrangements for all facilities, supplies, and services required for preparation and launch of the vehicle.

c. Identify launch vehicle ground and flight safety launch constraints. If necessary, integrate the satellite procedures with the launch vehicle checkout effort where appropriate and coordinate launch site and safety approvals. The Government will be responsible for providing all integration site satellite checkout procedures and for obtaining the requisite satellite safety approvals (with the assistance of the Contractor).

d. Integrate the payload onto the launch vehicle, encapsulate, transport, and perform spacecraft to launch vehicle integrated checkout activities necessary to assure launch readiness.

e. Provide and schedule the necessary support services at the launch Range that are required for launch preparation of the launch vehicle, integrated testing with the payload, and launch.

f. Provide access for Government payload personnel at the integration site and provide access to real-time payload telemetry, voice, and video communications to government representatives.

1.10.2 Launch Support

The Contractor shall provide a facility at the launch site or remote launch control center capable of supporting up to 3 government representatives during launch countdown. Support for additional government representatives may be required at the task order level. Support should be consistent with the Contractor's commercial practices for integrated spacecraft to launch vehicle operations and on the day of launch using commercial practices with available information, which may include access to real-time telemetry (RF and hardwire), voice communication channels with listen capabilities, video, and telephones. The Contractor shall provide access to real-time payload telemetry to government representatives during the launch terminal countdown. The Contractor shall communicate real time launch and payload separation status. The Contractor shall verify payload separation by launch vehicle telemetry with redundant separation indications. The Contractor shall provide all recorded payload telemetry to NASA with the Final Flight Report (VADR 1-14). Real time delivery of communication and telemetry to NASA is desirable but not required. As determined by the ICD (VADR 1-2), the Contractor shall notify the Government of the achieved orbit characteristics.

The Contractor shall poll NASA during the launch terminal countdown for the payload status for Dedicated and Primary Rideshare missions as defined in section 1.1 Scope of Standard Launch

Services and 1.4.1 Approval. The Contractor shall not launch until NASA states the payload is ready.

Safety and Quality

The Contractor shall establish, implement, and maintain risk management, safety, reliability, and quality assurance programs with AS9100, Aerospace Quality Management System (QMS), or equivalent as a guideline. For task orders that require Category 1 Certification, a QMS compliant to ISO 9001 or AS9100 is required.

The Contractor shall provide any updates to the Occupational Safety and Health Plan that implements safety and health requirements consistent with federal, state, and local government regulations and applicable launch processing site Safety and Health requirements.

NASA will not retain control of the launch due to its modified technical oversight approach, as described in NPR 8610.23. VADR launch services are for high risk tolerant payloads and the Contractor will be responsible for all mission assurance activities. FAA, as the licensing agency, will conduct all mission anomaly and/or failure investigations.

In the event that NASA personnel or property are affected by an anomaly or failure, the Contractor shall provide sufficient information for NASA to perform its own mishap investigation per NPR 8621.1.

Contract Documentation Requirements List (CDRL)

The Contract Documentation Requirements List (CDRL) in Attachment 03 identifies critical elements of the Contractor's efforts. The Contractor shall produce and make the appropriate distribution of all items on the CDRL that require review or approval by the Government.

Public Affairs

The Contractor shall coordinate with NASA Public Affairs Office (PAO) all press releases concerning launches under this contract. The contractor shall provide video footage and photos of vehicle build-up, payload integration, launch countdown, spacecraft integration and encapsulation.

The Contractor may, consistent with Federal law and this Contract, release general information regarding its activities conducted within the scope of the Contract. Any Public Affairs material that refers to NASA or uses the NASA logo requires approval by NASA prior to public release.

Any Public Affairs material that does not refer to NASA, NASA missions, or the Government does not require NASA approval.

2.0 STREAMLINED CUBESAT LAUNCH SERVICES (CLIN 2)

2.1 Scope and Requirements

The scope of the Streamlined CubeSat Launch Services includes launch services capable of delivering a CubeSat to a variety of orbits, including escape trajectories. The integration timeline from ATP to on-orbit deployment will be specified at the task order level. For each task order, the Government will define the particular CubeSat interface specifications, required orbital parameters, and schedule.

The Contractor shall furnish all services to meet the requirements defined for Streamlined CubeSat Launch Services.

Objectives The objectives of the launch service are to:

a. Provide affordable, accurate, and on-time delivery of Government and/or Government-sponsored payloads to space.

b. Ensure the safety of the public, as well as all personnel, hardware, and property associated with the launch service.

2.2 Streamlined CubeSat Launch Services Ground Rules

The following ground rules apply, but may be tailored at the task order level:

1. NASA will not have spacecraft readiness go/no-go or "hold" authority during countdown.

2. The CubeSat typically will not require any electrical interface with the Launch Vehicle

(LV) and will be powered off from closeout of the CubeSat Dispenser through on-orbit deployment.

3. The CubeSat typically will not contain any hazardous materials (except batteries), pressure vessels, pyrotechnic devices, nor radioactive material. This ground rule may be tailored by the government at the task order level.

4. The CubeSat typically will not contain a propulsion system. Propulsion systems may be allowed at the task order level.

5. The CubeSat project will provide all documentation/data necessary to demonstrate compliance with all applicable mission specific technical/safety requirements.

6. The CubeSat project will be responsible for obtaining all spacecraft Radio Frequency and remote sensing regulatory licensing required by the US Government. Note: FCC consultant services may be required as specified at the task order level.

7. The CubeSat will be delivered to the Contractor for integration to the dispenser on the date and the location specified by the Contractor.

2.3 Streamlined CubeSat Launch Services Requirements

The Contractor shall:

1. Provide the CubeSat dispenser that is qualified to the predicted launch environments and meets the detailed interface requirements that will be identified at the task order level.

2. Perform launch vehicle planning, analysis, design, development, production, integration, and testing required to provide the launch service appropriate to transport the payload(s) to the required orbit.

3. Provide a test fixture that replicates all dispenser to CubeSat interfaces and clearances for use by CubeSat providers during fit check and CubeSat environmental testing.

4. Include NASA LSP on all communications, data requests, and exchanges with the CubeSat project.

5. Conduct a kick-off meeting with NASA LSP and the CubeSat project.

6. Conduct coordination teleconferences with the CubeSat project and NASA LSP at least every two weeks and transmit a post-conference memo documenting the meeting minutes and any actions taken by the CubeSat project and NASA LSP within 5 working days of each meeting.

7. Provide at kick-off and whenever updates are required, a mission specific schedule that identifies all integration/launch campaign milestones and deliverables due from the CubeSat project, NASA LSP, and the Contractor.

8. Provide at kick-off and whenever updates are required, a listing and description of all documentation/data submittals required by the CubeSat project to demonstrate compliance with all applicable technical and safety requirements required by the Contractor, the LV provider, the launch range, and the local/state/federal Government.

9. Produce a baseline CubeSat to dispenser assembly Interface Control Document (ICD) no later than ATP + 2 months and produce updates, as required. The Contractor shall ensure that the ICD includes the anticipated environments at the CubeSat dispenser to LV interface and all technical requirements that must be met by the CubeSat project. In cases where the dispenser includes internal isolation, the Contractor shall ensure that the ICD also includes anticipated environments at the CubeSat to dispenser interface.

10. Provide a baseline ICD requirement verification matrix no later than ATP + 2 months and produce updates, as required.

11. Perform integration of the CubeSat into the dispenser at a location in the contiguous United States, transport the integrated dispenser assembly as necessary, and perform integration of the integrated dispenser assembly onto the LV.

12. Provide telemetry confirmation of CubeSat deployment.

13. Provide NASA LSP ICD documentation/verification evidence within two weeks of requirement completion.

14. Provide and maintain a non-deploying contingency mass simulator for the CubeSat integrated dispenser assembly if required by the LV provider.

15. Conduct a Mission Readiness Review (MRR) at a mutually agreeable time/date with the

CubeSat project, NASA LSP, and the LV provider (if applicable) approximately one month prior to CubeSat to dispenser integration to verify that the CubeSat and the dispenser have met all technical/safety/regulatory requirements for the mission, that plans for dispenser and LV integration are in place and ready to execute, and that the LV remains on schedule to support the mission.

16. Generate a list of any actions and/or constraints resulting from the MRR within one week of the review and track them to closure. The Contractor shall close all actions and constraints prior to LV integration.

2.4 FCC Consulting Services

Some missions may require that the Contractor shall provide consulting services to the CubeSat project for obtaining a Federal Communications Commission (FCC) license for each spacecraft transmitter and associated ground station, in advance of final delivery of the CubeSat for integration into the dispenser. The Contractor shall assist the CubeSat project in obtaining the required information to fill out the FCC application. The Contractor shall submit the application, on behalf the CubeSat project, to the FCC and assist with any questions with the goal of obtaining the license no later than one month prior to integration to the dispenser. All required licenses (e.g.

FCC licenses) or permits must be acquired by the agreed integration date of the CubeSat into the dispenser, and copies of these shall be provided at the time of integration. Launch of the CubeSats will be subject to NASA approval should licenses/permits not be obtained by dispenser integration.

For missions that need FCC consulting services, the requirement will be specified at the task order level.

2.5 Deliverables

The Contractor shall provide all deliverables electronically via email in PDF format unless otherwise specified. The Contractor shall submit all deliverables to the appropriate NASA Contracting Officer, Contract Specialist, Contracting Officer’s Representative (COR), and Mission Manager assigned to the mission. The Contractor shall deliver all CDRLs in accordance with Attachment 03, CDRLs. The task order will include contact information for the recipients.

3.0 SPECIAL TASK ASSIGNMENTS (CLIN 3)

The Contractor shall perform special studies and analyses in support of this contract, as required.

Each task will be initiated by written direction from the NASA Contracting Officer. These tasks include advance planning and feasibility studies in support of future contemplated missions;

analyses in support of potential change requirements to authorized missions; and development, fabrication, and test of hardware/software to support planning studies or special tests and mission specific studies.

3.0 SPECIAL TASK ASSIGNMENTS (CLIN 3)