Attachment 02_Meetings and Formal Reviews.pdf

RFP VADR ATTACHMENT 02 MEETINGS AND FORMAL REVIEWS 80KSC021R0034 Rev A

ATTACHMENT 02

Meetings and Formal Reviews For

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

RFP VADR ATTACHMENT 02–MEETINGS AND FORMAL REVIEWS 80KSC021R0034 Rev A

Meetings and 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 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. The meetings and reviews in this attachment can be conducted virtually, or in-person at the Contractor’s facility upon NASA request.

CLIN 1 Standard Launch Services Meetings and Reviews

Kick-Off Meeting

Kick-off meeting shall be held within two weeks of task order award. 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

Mission Specific Design Review (MSDR)

The Contractor shall conduct a MSDR. Typically, the MSDR occurs 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 rationale for the following items at the MSDR:

• All known technical design problems and development anomalies associated with meeting the ICD requirements, showing that the required system function, performance and safety have not been compromised. If not resolved, provide a credible and detailed plan to resolve them prior to qualification testing or final analysis cycle as appropriate.

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

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

• Key engineering analyses that have been performed to support the detailed design.

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

• Launch vehicle/payload compatibility test plans, if any, that have been defined. Identified any payload compatibility issues and steps for ensuring compatibility of payloads.

• Released drawings (submission to the Government not required) that support the mission qualification, analysis and production milestones in the detailed schedule.

• Review the following submittals: the baseline Interface Control Document (ICD) (VADR 1-2), ICD Requirements Verification Matrix (VADR 1-3), initial submittal of Performance and Guidance Accuracy Analysis (PGAA) (VADR 1-5), and the Coupled Dynamic Loads Analysis (VADR 1-10)

• Status of critical flight hardware qualification (core stage engines and tanks, flight computer and Inertial Navigation Unit (INU), engine actuators, main batteries, separation systems, and payload fairing) and any test anomalies that could affect the NASA mission’s production or launch schedule and their resolutions. This shall include insight into fleet-wide problems, anomalies, corrective actions, deviations or waivers that may impact mission schedule.

• List of first flight items

• Methodology and results of analyses

• Status of licensing or applicable certification efforts.

Mission Integration Readiness Review (MIRR)

The Contractor shall conduct a MIRR to provide NASA with the current mission integration status.

The contractor shall present the design, fabrication, qualification testing, analysis status, and shall incorporate any flight data available. The Contractor shall address all mission specific items for the payload and mission requirements to verify qualification, compliance, and systems-level compatibility. 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 rationale of the following items at the

MIRR:

a. Design changes that occurred subsequent to MSDR or changes as a result of new flight data

b. Summary of applicable major mission specific component tests (test setups, test cases, results and significant anomalies), analyses, margins, or similarity assessments.

Included in the summary is component qualification status and rationale (similarity, test, analysis) for all affected components that are new, changed or subject to new environments or functional requirements

c. Changes or updates to methodology and results of analyses

d. Status of licensing or applicable certification efforts.

Launch Processing Readiness Review (LPRR)

The Contractor shall conduct a Launch Processing Readiness Review to demonstrate that the launch site and launch vehicle are ready to proceed with launch vehicle processing activities at the launch site including regulatory approvals leading to an on-schedule launch. This review will serve as an input to the Government decision to ship the payload by demonstrating the launch vehicle is ready to accept spacecraft hardware at the Payload Processing Facility and the launch site.

The Contractor shall present as a minimum:

a. Mission description including SC and launch vehicle configuration; integration status;

summary of waivers; mission specific analyses results, including updates, if any, from the MIRR; flight launch vehicle and launch site hardware/software production and testing status (including core stage engines and tanks, flight computer and Inertial Navigation Unit (INU), engine actuators, main batteries, separation systems, and payload fairing), and Contractor’s assessments of any significant manufacturing and test anomalies. Open and accepted contractor risks with the acceptance plan or acceptance rationale respectively.

b. A detailed schedule showing all activities (ground and flight with relationship to any other manifested missions) remaining to achieve a successful, on-time launch. Include a status of licensing or applicable certification efforts.

c. A draft outline of the spacecraft to integrated procedures listed in (VADR 1-14), including key inputs received and key inputs still needed from the Government

d. Provide status of flight anomaly resolutions across the fleet, that require Contractor resolution prior to launch of the next mission, including open and closed investigations required for FAA launch license.

e. Discuss readiness of the launch site to support the mission, including any required assets and the Payload Processing Facility

f. Contractor documented risks applicable to the mission

g. Description of first flight items, Contractor’s acceptance rationale or planned date for

Contractor’s acceptance if not yet completed

Launch Readiness Review (LRR)

The Contractor shall conduct a LRR for the mission to demonstrate the launch vehicle is acceptable, to the contractor’s satisfaction, for flight and all Range and other mission requirements have been met, or will be satisfied prior to launch. The LRR will be held approximately TBP days before launch.

As a minimum, the Contractor shall provide verification and specific rationale that:

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

b. Status of licensing or applicable certification efforts.

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

d. All previously recorded action items have been closed or are reflected on the schedule with the planned closure path

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

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

g. Tracking and data support resources are committed to launch

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

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

j. Mission risks are known and documented

k. Launch commit criteria for the payload and launch vehicle are approved and released

The Contractor shall also discuss:

a. Status of flight anomaly resolutions across the fleet that require Contractor resolution prior to launch of the next mission, including, open or closed investigations required for FAA launch license. Hardware/software failures of the launch vehicle during launch site integration and testing

b. Open corrective actions/problems reports

c. Launch vehicle first flight items

d. Mission specific items

If there are still open items at the time of this review, the contractor shall conduct a follow on review to ensure the specific launch vehicle is acceptable for flight and all Range and other mission requirements have been met, or will be satisfied prior to launch. As a minimum, the Contractor shall provide verification that any open items and deviations have been satisfied.

CLIN 2 Streamlined CubeSat Launch Services Meetings and Reviews

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

Mission Readiness Review (MRR)

The Contractor shall conduct a MRR resulting in verification of the following:

a. The CubeSat and the dispenser have met all technical/safety/regulatory requirements for the mission

b. Plans for dispenser and LV integration are in place and ready to execute

c. The LV remains on schedule to support the mission