80KSC020R0034 Attachment 03 MDDR.pdf

VCLS Demo 2 ATTACHMENT 03 – MDD&R 80KSC020R0034

ATTACHMENT 03

MILESTONE DELIVERABLE DESCRIPTIONS AND REQUIREMENTS

for

Venture Class Launch Service Demonstration 2 (VCLS Demo 2)

VCLS Demo 2 - DRFP ATTACHMENT 03 – MDD&R 80KSC020R0034

Milestone Deliverable Descriptions and Requirements

Government approval is defined as providing authority to proceed and/or formal acceptance of requirements, plans, tests, or success criteria in 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).

Kick-Off Meeting

Presentation packages and hand-out materials provided at the meeting to include:

A. Vehicle Overview B. Proposed Schedule C. Risks to implementation of SOW (Cost, Schedule, Technical) D. Minutes recorded during meeting

Technical / Operational Interchange Meeting

Presentation packages and hand-out materials provided at the meeting to include

a. Launch Vehicle Development/Build Status/Propulsion

b. Integration/ICD Status

c. Ground Operation Overview/Schedule

d. Technical and Schedule Risk and Mitigation

e. Minutes recorded during meeting

Development Engine and Stage Testing

Core stage engines are defined as propulsive engines on stages required for the launch vehicle to achieve orbit. Engines needed for orbit circularization or trim are not considered core stage engines. Tests are not required to be on the actual engines or stages to be used on the VCLS Demo 2 mission.

>90% Thrust Test

The Contractor shall have completed a test of all core stage engines in a flight like configuration demonstrating the engines successfully operating at a minimum of 90% of the thrust needed for the VCLS Demo 2 mission. The test will demonstrate high confidence in the ability to successfully deliver the launch service on schedule. Plots of the engine time vs: thrust, mixture ratio, pressures and temperatures shall be provided. A list describing all configuration changes under consideration prior to the VCLS Demo 2 mission shall be provided.

Full Mission Profile and Duration Test

The Contractor shall have completed a test of all core stage engines in a flight like configuration demonstrating the engines successfully operating through the full mission profile and duration needed for the VCLS Demo 2 mission. The test will demonstrate high confidence in the ability to successfully deliver the launch service on schedule. Plots of the engine time vs: thrust, mixture ratio, pressures and temperatures shall be provided. A list describing all test anomalies encountered during the mission duration shall be provided. A list describing all configuration changes under consideration prior to the VCLS Demo 2 mission shall be provided. The mission profile demonstrated in this test shall become an input for the Performance and Guidance Accuracy Analysis (PGAA) CDRL VCLS 2-4.

Core Stages Propulsion Testing Complete

The Contractor shall have completed propulsion qualification testing of all core stages in a flight like configuration demonstrating the stages successfully achieved Contractor proposed propulsion test objectives. The tests will demonstrate high confidence in the ability to successfully deliver the launch service on schedule. Plots shall be provided addressing each of the contractor’s documented test objectives. A list describing all test anomalies, and associated risks, encountered during the stage testing shall be provided. A list describing all configuration changes under consideration prior to the VCLS Demo 2 mission shall be provided. The test success shall be subject to NASA approval if the Contractor defined success criteria has not been met, the contractor defined criteria has not been demonstrated, or there is other reasonable evidence to suggest the test was unsuccessful. In addition, NASA reserves the right to withhold approval based on the Contractor not having a credible plan to resolve risks and implement planned changes in time for the VCLS Demo 2 mission.

Reviews

The Contractor shall conduct and chair reviews, as described below, that apply to the system, subsystem, component, and software level items of the launch service (payload interface, and any supporting equipment). Where there is not a direct match between a SOW specified design review(s) and the Contractor’s standard review(s), the Contractor’s review process will be acceptable provided it addresses equivalent content. All derived requirements from all system requirements must be identified and addressed in each of these reviews.

Mission Critical Design Review (CDR)

The Contractor shall conduct a Mission CDR before significant fabrication of mission interface hardware begins. The Contractor shall present a final detailed design based on drawings, analyses, and evaluation testing that shows the mission specific design meets final performance and interface specifications, safety requirements, and mission objectives. The Contractor shall identify and describe all planned qualification and acceptance tests to be performed to prove validity. NASA reserves the right to withhold approval of this milestone if the design does not meet performance or schedule requirements and until all action items have been closed. As a minimum, the Contractor shall provide verification and submittal of the following items at the

CDR:

i. All known technical design problems and development anomalies associated with meeting the ICD requirements have been resolved without compromising required system function, performance and safety. If not resolved a credible and detailed resolution plan exists to resolve them prior to qualification testing.

ii. The detailed mission hardware and analytical design will meet performance, functional requirements, and schedule.

iii. Software simulations and prototyping results do not present any potential mission risks.

iv. All key engineering analyses have been performed to support the detailed design.

v. Integrated safety analysis identifying any remaining hazards and proposed resolution.

vi. Launch vehicle/payload compatibility test plans, if any, have been defined.

vii. Approximately 75% of drawings released.

viii. Submittal of the following: the baseline Interface Control Document (ICD) (CDRL VCLS 2-2), ICD Requirements Verification Matrix (CDRL VCLS 2-3), initial submittal of Performance and Guidance Accuracy Analysis (PGAA) (CDRL VCLS 2- 4), and the Coupled Dynamic Loads Analysis (CDRL VCLS 2-5)

Qualification Data Review (QDR)

LSC shall provide a two-day Qualification Data Review (QDR) to provide NASA confidence in the LSC’s ability to successfully deliver the launch service. Prior to the QDR, the following major items shall have completed qualification: core stage engines and tanks, flight computer and Inertia Navigation Unit (INU), engine actuators, main batteries. Presentation materials for the QDR are to be sent electronically to NASA no later than one week prior to QDR. The subsequent submittal of the Performance and Guidance Accuracy Analysis (PGAA) (CDRL VCLS 2-4) is due at QDR.

The LSC shall present rationale to LSP showing that the key vehicle components and subsystems are “qualified” to the LSC’s satisfaction (i.e. meets internal standards, documented deviation/waiver processes, and risk management practices). The QDR will include a high-level description of the as-built and qualified implementation/fabrication, the component or assembly part number, and details on any differences in between the qualification and flight configurations. Sufficient information shall be presented for LSP to understand what component acceptance, component qualification, and system level qualification/compatibility testing has been performed and if and how all elements of the hardware’s entire life cycle have been accounted for in the qualification determination. Qualification rationale shall include the qualification and acceptance test and/or analysis levels, the environments derivation methodology and examples. The contractor rationale shall be clear on the use of analysis, test and/or similarity. All anomalies and deviations from the qualification test plans/procedures, with associated resolutions and rationale will be identified.

The QDR presentation shall address at a minimum the core stage engines and tanks, flight computer, Inertial Navigation Unit (INU), engine actuators, main batteries, separation systems, and flight software processes/test status. It shall also address analysis methods, assumptions, results and margins for launch vehicle loads, trajectory, controls and thermal.

It is recognized that the launch service Contractor chooses or maintain their own technical standards for design and test; therefore, the LSC’s technical standards for design and test of the vehicle shall be provided to LSP 1 month prior to the QDR to aid in understanding of the qualification status. The final presentation package shall be provided 1 week prior to the QDR or the QDR will be rescheduled.

NASA reserves the right to withhold approval of this milestone if the design of the listed items is not qualified to the Contractor’s standard(s) and until all action items related to the payload interface have been closed.

Launch Vehicle Readiness Review

The Contractor shall conduct a Launch Vehicle Readiness Review to demonstrate that the launch site and launch vehicle are ready to proceed with launch vehicle processing activities at the launch site. The Contractor shall present as a minimum:

i. Mission description including S/C and launch vehicle configuration; integration status;

summary of waivers; analyses results and status including updates, if any, from the QDR and analyses not related to qualification; flight launch vehicle and launch site hardware/software production and testing status, and Contractor’s assessments of any significant manufacturing and test anomalies

ii. A detailed schedule showing all activities (ground and flight with relationship to any other manifested missions) remaining to achieve a successful, on-time VCLS Demo 2 launch

iii. A draft outline of the Spacecraft to Launch Vehicle Integrated Procedures (CDRL VCLS 2-7)

Flight Readiness Review (FRR)

The Contractor shall conduct a FRR for the mission to ensure the launch vehicle is acceptable for flight and all Range and other mission requirements have been met, or will be satisfied prior to launch. The FRR shall include participation from any appropriate Range approving officials.

The FRR is held approximately five (5) to ten (10) days before launch. As a minimum, the Contractor shall provide verification that:

i. All critical items required to proceed into final launch countdown are ready

ii. Vehicle configuration is defined and all vehicle systems have been verified IAW launch site test plans

iii. All previously recorded action items have been closed or are reflected on the schedule

iv. All previously held Contractor’s readiness review actions have been closed or resolved

v. Launch site/Range support organizations have committed to launch

vi. Tracking and data support resources are committed to launch

vii. Any open work is identified and closeout plans and schedules are in place and supportable

viii. Any constraints to launch are identified and resolution plans developed

ix. Mission risks are known and documented

x. Launch commit criteria for payload and launch vehicle is approved and released

The Contractor shall also discuss:

i. Anomalies from previous missions, if applicable

ii. Hardware/software failures of the VCLS Demo 2 vehicle during launch site integration and testing

iii. Open corrective actions/problems reports

Post-Launch Assessment Report

The Post-Launch Assessment Report shall include submission of CDRL VCLS 2-6 and shall include verification that:

i. The launch vehicle orbit insertions at payload separation agrees with prediction, or if not, it is adequately understood so that future behavior can be predicted with confidence.

ii. All anomalies have been adequately documented, and their impact on future Contractor operations is assessed. Further, anomalies related to the payload to launch vehicle interface have at least one credible cause identified to aid in the Contractors future resolution.

Mission Success Criteria

A. A mission will be determined a Mission Success, if:

i. The payloads are placed into the ICD required insertion orbit(s) by the launch vehicle, and

ii. The launch vehicle causes no damage to the payload during launch or thereafter from collision or contamination products.

B. A mission will be determined a Failed Mission when the payload:

i. Is destroyed during launch/flight, or

ii. Because of the launch vehicle state and health at the time of separation prevent the payload from achieving its mission.