Attachment 03 - MDDR TROPICS.pdf

ATTACHMENT 03

MILESTONE DELIVERABLE DESCRIPTIONS AND

REQUIREMENTS

FOR

TROPICS

TROPICS ATTACHMENT 03 – MDD&R 80KSC020R0036-RFP

Milestone Deliverable Descriptions and Requirements

Kick-Off Meeting

A. Vehicle Overview B. Proposed Schedule C. Risks to implementation of SOW (Cost, Schedule, Technical)

Technical / Operational Interchange Meeting

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

a. Launch Vehicle Development/Build Status

b. Integration/ICD Status

c. Ground Operation Overview/Schedule

d. Minutes recorded during meeting

Interface Control Document (ICD)

Delivery of an ICD per CDRL TROPICS-2

ICD Verification Matrix

Delivery of an ICD Verification Matrix per CDRL TROPICS-3

Engine and Stage Propulsion Testing

Core stage engines are defined as propulsive engines on stages required for the launch vehicle to achieve low earth orbit. Qualification Tests are not required to be on the actual engines or stages to be used on the TROPICS launch vehicle(s).

Core Stage Engine(s) Qualification Testing Completed

The Contractor shall have completed all core stage engine qualification tests consistent with the planned qualification tests specifically identified as proposed by the Offeror. The test shall demonstrate that the Contractor has high confidence in the ability to successfully deliver the launch service(s) on schedule. Deviations, anomalies during qualification testing and a list describing all configuration changes under consideration prior to the TROPICS mission shall be documented in the Contractor's risk system and/or technical decision-making system with only a summary provided to the Government. NASA reserves the right to withhold approval based on the Contractor not having a credible plan to resolve risks and/or implement planned changes in time for the TROPICS mission.

The mission profile demonstrated in this test shall become an input for the Performance and Guidance Accuracy Analysis (PGAA) CDRL TROPICS-4.

Core Stages Propulsion Qualification Testing Complete

The Contractor shall have completed propulsion testing of all core stages in a flight like configuration demonstrating the stage(s) successfully achieved Contractor proposed propulsion test objectives. The tests will demonstrate high confidence in the ability to successfully deliver the launch service(s) on schedule. Deviations, anomalies during qualification testing, and a list describing all configuration changes under consideration prior to the TROPICS mission shall be documented in the Contractor's risk system and/or technical decision-making system with only a summary provided to the Government. NASA reserves the right to withhold approval based on the Contractor not having a credible plan to resolve risks and/or implement planned changes in time for the TROPICS 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(s) (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. The Contractor shall present a final detailed design based on drawings, analyses, and evaluation testing that shows the mission design meets final performance and interface specifications, safety requirements, and mission objectives. The Contractor shall identify and describe all planned mission 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 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 or final analysis cycle as appropriate.

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(s)/payloads compatibility test plans, if any, have been defined.

vii. The baseline ICD and Verification Matrix has been signed by the Contractor and submitted to the Government (CDRLs TROPICS-2 and TROPICS-3).

Qualification Data Review (QDR)

The Contractor shall present rational to the Launch Service Program (LSP) showing that the below listed vehicle components and subsystems are “qualified” to the Contractor’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 or 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 rationale will 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 the core stage engines and tanks, flight computer, Inertia 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 and accepted by NASA that the contractor chooses or maintains their own technical standards for design and test and NASA will not approve them. The Contractor’s technical standards for design and test of the vehicle shall be included in the final presentation package. 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.

Post Flight Data Review (PFDR)

The Contractor may choose to provide a PFDR in lieu of a QDR if there has been a successful flight of the launch vehicle using core engines and core stages identified in Table 2.2.9-1, Launch Service Milestone Payment Schedule, Launch Service Milestone Payment #’s 5 (Core Stage Engines Qualification Testing Complete) and 6 (Core Stages Propulsion Qualification Testing Complete).

The Contractor shall present the PFDR with a technical team to a Launch Services Program small, multifunctional technical team that includes a safety and mission assurance representative. The Contractor’s post fight data report, in their own format, shall be provided 1 month prior to the PFDR. Regardless of what is in the post-fight data report, the PFDR shall include identification of actual vehicle and performance parameters in the flight telemetry which exceed three sigma predictions, regardless of Contractor’s mission success determination. The Contractor’s resolution or plans for resolution of the anomalies shall also be presented to NASA.

NASA reserves the right to withhold approval of this milestone if the anomaly resolution plans do not support the TROPICS contract launch date.

Launch Vehicle Readiness Review (LVRR)

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 payload and launch vehicle configuration; integration status;

summary of mission specific waivers; mission specific analyses results; if applicable, status including updates, if any, from the QDR; if applicable, ; description of first flight items and summary of Contractor’s rational for flight acceptance; flight launch vehicle and launch site hardware/software production and testing status, and Contractor’s assessments of any significant manufacturing, test and prior flight anomalies. Open and accepted contractor risks with the acceptance plan or acceptance rational respectively.

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

Flight Readiness Review (FRR)

The Contractor shall conduct an FRR for the mission to ensure the launch vehicle is acceptable for flight to their satisfaction 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.

xi. If required, status of the launch vehicles in support of second and third insertions.

The Contractor shall also discuss:

i. Anomalies from previous missions, if applicable.

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

iii. Open corrective actions/problems reports.

Quick Look Report

The Contractor shall provide a quick look post-flight analysis using preliminary evaluations of vehicle telemetry and insertion performance per CDRL TROPICS-6.

If multiple launches approach is utilized to meet TROPICS requirements, this report shall be provided to the Launch Services Program after each launch as identified in Table 2.2.9-1, Launch Service Milestone Payment Schedule.

The Quick Look Report is submitted approximately thirty (30) days after each insertion, but prior to the next launch (if applicable).

Post-Launch Final Assessment Report

Include verification that:

i. The launch vehicle(s) 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 been had 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 orbits by the launch vehicle(s), and

ii. The launch vehicle(s) causes no damage to the payloads during launch(es) or thereafter from collision or contamination products.

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

i. Are destroyed during launch(es)/flight(s), or

ii. Cannot be separated from the launch vehicle(s) because of exceedances in ICD defined flight environments imposed on the payloads by the launch vehicle(s), or due to an incorrect separation command sent to the dispenser, or because of the launch vehicle(s) state and health at the time of separation prevent the payloads from achieving its mission.