LSA_OTA_Draft_RFP_Annex_A_-_Statement_of_Objectives.pdf

DRAFT

Solicitation No.: FA8811-17-X-XXXX

ANNEX A

STATEMENT OF OBJECTIVES

1.0 Purpose

This Statement of Objectives (SOO) shall be used by the Offeror in preparing the Launch Service

Agreement (LSA) proposal and Statement of Work (SOW). The Offeror shall propose EELV

Certification Plan(s) and a SOW that together accomplish all objectives identified in this SOO to include the programmatic activities in Section 3.0. The majority of the objectives below will be covered by the Certification Plan(s), which will be included as Annex A to the SOW. See the instructions for the SOW in Request for Proposals (RFP) paragraph 3.1.6.2.

2.0 Objectives

The Government’s objectives are to:

A. Develop Payload Category A, B, and C launch system prototypes, through shared investment with industry partners that will lead to EELV certified launch systems capable of providing launch services for all EELV-class National Security Space (NSS) missions.

For the purpose of this agreement, a prototype is defined as a fully developed EELV-certified launch system, including the validation of non-recurring engineering (NRE) work.

B. Complete rocket propulsion system (RPS) development begun under the current RPS investments, if required for the development of a launch system prototype.

C. Create a positive partnership with the Offeror for this development effort in order to achieve insight and understanding of the Offeror’s launch system and related efforts. This shall include:

a. Develop an automated pedigree process by which pedigree data can be viewed electronically as part of the Contractor and Government mission assurance.

b. Provide facilities for an in-plant Air Force representative during development and production

D. Gain mutual insight and understanding of the Offeror’s launch system design and development and launch service processes through execution of an EELV-approved

Certification Plan or multiple EELV-approved Certification Plans, as required, to meet the full range of EELV mass-to-orbit requirements in compliance with the documents listed in

Attachment 4, Compliance Documents.

E. Gain insight and understanding of the Offeror’s development schedule.

F. Implement a system safety program that meets the requirements of MIL-STD-882E, tailored as specified in Attachment 5, Reference Documents, to identify and track system safety hazards, identify hazard mitigation options, and identify and report residual mishap risk levels to the EELV Program Office. The EELV Program Office will provide feedback on residual risk levels during design discussions. The EELV Program Office will need to perform risk reporting and risk acceptance in accordance with AFI 91-202 for all residual risks.

G. Identify Critical Program Information (CPI), if any, and mission critical functions and critical components, as defined by SMC-S-013, to support supply chain risk management.

3.0 Programmatics

The following activities shall be conducted to allow the Government to gain insight and understanding of the development effort:

A. Program reviews on a regular basis (not less than quarterly). These reviews will be conducted with Government participation at an agreed upon location or by teleconference.

These reviews shall include, at a minimum, the following:

1) Status of launch system development, including development of a launch vehicle that can launch Payload Category C payloads and the status of East and West coast launch pads,

2) Progress against the certification plan(s) and schedule,

3) Business case analysis or updates to previously submitted business case analysis,

4) Status of system safety program, and

5) Cost summary reporting. The cost summary reporting shall identify total development funding expended to date for this launch system development effort to include a breakout of funding from Government sources and from non-

Government sources.

B. Technical reviews will be planned and conducted with Government participation at an agreed upon location. Reference IEEE 15288.2-10-Dec 2014 _ Technical Reviews and

Audits on Defense Programs and TOR 2007(8583)6414-30-Sept 2009 _ Space System

Supplement, to derive entrance and exit criteria.

C. Regular communication (not less than weekly) between the EELV program office and the

Offeror to discuss launch system development progress. This communication will be conducted with Government participation at an agreed upon location or by teleconference.

D. Reporting during the performance of this development effort:

1) Performance Reporting. The Offeror shall include performance reporting in the final report to address technical progress achieved from this launch system development effort. The Offeror shall complete a Standard Form 298 (SF 298) to be included in the final report.

2) Cost Summary Reporting. The Offeror shall include a cost summary report in the final report. The cost summary report shall identify total development funding expended for this launch system development effort to include a breakout of funding from Government sources and from non-Government sources.

3) Payable Milestones Reporting. In accordance with the Milestone Payment Plan

(Annex C Attachment 2), the Offeror shall submit documentation describing the extent of accomplishment of Milestones. This documentation shall be as required by Annex C Article VI.

4) Patent Reporting. The Offeror shall submit invention disclosure reports in accordance with Annex C Article XI, and in accordance with the SOW. Invention reports shall be accomplished using DD Form 882.

4.0 Definitions

Development – For the purposes of this Agreement, development is defined as all activities from initial concept up to, but not including, production. This could include full development of a new launch system or modifications to an existing launch system, including launch infrastructure.

Development includes all efforts leading up to and including EELV certification (and the validation of all NRE work) to meet the full range of EELV mass-to-orbit requirements and all requirements in the EELV SIS and SPRD.

EELV Launch System – The EELV Launch Vehicle Segment and EELV Ground Segment along with associated operation and support services and personnel that provide the capability to perform all EELV Missions.

EELV Launch Vehicle Certification – Formal verification of the non-recurring portion of the

Launch Vehicle Mission Assurance process (ref. New Entrant Certification Guide (NECG)).

Launch vehicle certification consists of validation of a launch vehicle design and qualification along with verification of the company’s engineering, manufacturing, and integration processes.

The SMC Commander is responsible for launch vehicle certification. This certification means that the launch system is considered qualified to launch operational national security spacecraft, and that the company, from a technical perspective, is regarded as a prospective contractor for future EELV missions.

EELV Program – The EELV program is a funded U.S. Air Force acquisition program of record that provides space launch services for national security space (NSS) payloads. The EELV program is in the portfolio of the Program Executive Officer (PEO) for Space at the Space and

Missile Systems Center (SMC). Program requirements for the EELV program, including reliability, accuracy, and standard interface, are specified in the EELV Capability Production

Document (CPD), validated by the Joint Requirements Oversight Council (JROC) in 2016.

Production - The action of making or manufacturing from components or raw materials, or the process of being so manufactured.

Prototype – Per the DoD Other Transaction (OT) Guide for Prototype Projects, a prototype can generally be described as a physical or virtual model used to evaluate the technical or manufacturing feasibility or military utility of a particular technology or process, concept, end item, or system. For the purpose of this agreement, a prototype is defined as a fully developed

EELV-certified launch system, including the validation of all NRE work.

ATTACHMENTS

Attachment 1 – Classified Statement of Objectives (Posted on ARC Site)