Attachment 2: Meetings and Formal Reviews

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 B

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.
b.
c.
d.

Vehicle Overview
Proposed Schedule
Risks to implementation of SOW (Cost, Schedule, Technical) 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,