04 - 80KSC020R0034 DRFP Attachment 02 CDRLs.pdf

ATTACHMENT 02

CONTRACT DATA REQUIREMENTS LIST

FOR

VENTURE CLASS LAUNCH SERVICE DEMO 2 (VCLS Demo 2)

This page left intentionally blank.

CONTRACT DATA REQUIREMENTS LIST (CDRL)

The Contract Data Requirements List (CDRL) identifies critical elements of the contracted effort where NASA requires aspects of mission integration insight and approval. The following CDRL defines the scope of documentation required; however, NASA will utilize the Contractor’s existing documentation to the extent practicable. Where there is not a direct match between a CDRL item and the Contractor’s standard documentation, the Contractor’s documentation will be acceptable provided it contains equivalent data requirements. CDRL approval may be assumed unless the Contractor is notified by NASA of disapproval within thirty (30) days. Under certain circumstances, NASA may elect to eliminate certain submittal cycles.

All CDRL data requirements shall be delivered electronically to the Contracting Officer. All electronic formats shall be mutually acceptable to ensure government accessibility.

TABLE: CDRL INDEX

Item Document Approval/ Review/Sub mit

Initial Submittal Date

Subsequent Submittal Date

Documentation

VCLS 2-1 Formal Meeting & Review Documentation Submit

At Each Review

As Required (A/R)

Mission Integration

VCLS 2-2 Interface Control Document (ICD) Approval Preliminary ICD L-12 months

Baseline ICD at CDR and

A/R

VCLS 2-3 Interface Control Document (ICD) Requirements Verification Matrix Approval

CDR

A/R or with each

ICD revision

Analysis

VCLS 2-4 Performance and Guidance Accuracy Analysis (PGAA)

Initial Submittal =

Review, Subsequent Submittals =

Approval

CDR QDR, A/R

VCLS 2-5 Coupled Dynamic Loads Analysis Review CDR A/R

VCLS 2-6 Final Flight Report Review L+ 1 Month A/R

Engineering

VCLS 2-7 Spacecraft to Launch Vehicle Integrated Procedures

Initial

Submittal = Review, Subsequent Submittals =

Approval

Draft 30D Prior to Use

1W Prior to Use

* All CDRL’s are required per mission

CDRL DESCRIPTION Number: VCLS 2-1

FORMAL MEETING & REVIEW DOCUMENTATION

DESCRIPTION/PURPOSE:

To provide presentation and handout material, minutes, and accompanying action item lists from each formal review.

DATA REQUIREMENTS:

Formal review documentation shall include:

(A) Presentation packages for the review for NASA attendees due 3 days prior to the Review. The presentation package for the QDR is due 1 week prior to the QDR or the QDR will be rescheduled.

(i) Reviews as documented in Attachment 03, Milestone Deliverable Descriptions and Requirements

(B) Minutes from each formal review

(C) List of attendees

(D) An action item list maintained and updated by the Contractor. The list shall include:

(i) Due Date

(ii) Subject (iii)Assigned tracking number for each action item

(iv) Person or organization responsible for completing the action

(v) Status of action (i.e., open with key points/details and timeline identified/planned, closed, or deleted)

(vi) Closure rationale

CDRL DESCRIPTION Number: VCLS 2-2

INTERFACE CONTROL DOCUMENT (ICD)

DESCRIPTION/PURPOSE:

The ICD identifies and defines the functional and environmental interfaces, and performance requirements of the payload, and payload GSE with the launch vehicle and associated payload/launch processing facilities, as well as the mission success criteria.

Preliminary ICD is the first CDRL release of the ICD and is expected to have several TBD’s. Baseline ICD is the next release of the CDRL and is expected to have very few TBD’s.

DATA REQUIREMENTS:

The number of interface requirement changes incorporated in each new revision and subsequent release of the ICD shall not exceed ten (10) approved requirements changes.

Where there is not a direct match between the specified ICD data requirements identified below and the Contractor’s standard ICD, the Contractor’s standard ICD will be acceptable provided it addresses equivalent content as appropriate to meet payload requirements. The outline below is meant to assure all potential requirements are addressed regardless of payload complexity or risk posture; however any deemed unnecessary requirements based upon manifested payload requirements (upon mutual Government/Contractor agreement) may be listed as not applicable (NA) in the approved ICD:

1.0 INTRODUCTION

1.1 Purpose

1.2 Scope

1.3 Definitions

1.4 Interface Change Control

1.5 Requirement Traceability

1.6 Requirements Status

2.0 APPLICABLE DOCUMENTS

2.1 Government Documents

2.2 Contractor Documents

2.3 Other Documents

3.0 INTERFACE REQUIREMENTS

3.1 Structural /Mechanical Interfaces

3.2 Electrical Interfaces

CDRL DESCRIPTION Number: VCLS 2-2 (cont)

3.3 Environmental Interfaces

3.4 Flight Design

3.5 Ground Operations

3.6 Safety Requirements

4.0 MISSION SUCCESS CRITERIA

The Contractor’s proposed criteria to be used to determine the success of the mission. These criteria shall be based on applicable flight related ICD requirements.

The Contractor’s proposed methods, including required vehicle telemetry measurements, ground observation, and analysis/reconstruction techniques, for verifying that each proposed mission success criterion is satisfied. Allowances for sensor measurement accuracy shall be explicitly identified and justified.

CDRL DESCRIPTION Number: VCLS 2-3

INTERFACE CONTROL DOCUMENT (ICD) REQUIREMENTS VERIFICATION MATRIX

DESCRIPTION/PURPOSE:

A verification matrix will document and track all ICD requirements and methods by which they will be verified and responsible organization. The verification matrix shall list the final documentation of the verification approved by the cognizant Contractor engineer. NASA does not intend to conduct its own verification of the interface requirements.

DATA REQUIREMENTS:

The verification matrix shall be released no later than CDR.

Where there is not a direct match between the specified ICD Verification Matrix data requirements identified below and the Contractor’s standard ICD Verification Matrix, the Contractor’s standard ICD Verification Matrix will be acceptable provided it addresses equivalent content:

• ICD requirement language

• ICD requirement paragraph number

• Verification Method (Test, Inspection, Analysis, Demonstration)

• Responsible Organization

• Verification Plan

• Verification Source

• Notes/Comments

• Status

CDRL DESCRIPTION Number: VCLS 2-4

PERFORMANCE AND GUIDANCE ACCURACY ANALYSIS (PGAA)

DESCRIPTION/PURPOSE:

This analysis is prepared using the provider-defined trajectory requirements to help provide confidence in meeting the VCLS requirement.

The analysis shall include, as a minimum:

(A) The nominal and 3-sigma limits for orbit elements and associated covariance matrix

(B) Performance impacts as a function of launch date and time

Performance capability, margins and reserves, including description of how performance reserve is calculated.

(C) Sequence of events and tracking coverage

(D) Time history of trajectory from launch to targeted condition and extending until the launch vehicle propellant and gases are expended.

(E) Separation trajectory and contact probability prediction

(F) Launch vehicle summary weight statement

(G) Sources and magnitude for all dispersions used. If statistical dispersions are used, then the distribution method (e.g., normal, gaussian) shall be specified for each parameter

(H) Definition of all coordinate systems used

(I) Reference to the source(s) for all payload and launch vehicle inputs to this analysis (e.g., requirements, mass properties)

(J) Evaluation of compliance with applicable ICD requirements and constraints.

(L) Launch windows determined by analysis

(M) Input file

(N) An itemized list of all modeling changes made since the previous CDRL VCLS 2-4 release (including launch vehicle propulsion, mass properties, aerodynamics, and mission design ground rules), along with an assessment of the performance effect of each change

CDRL DESCRIPTION Number: VCLS 2-5

COUPLED DYNAMIC LOADS ANALYSIS

DESCRIPTION/PURPOSE:

This analysis defines flight loads to payload structure. This analysis also supports pre-flight verification of compliance with mission requirements.

(A) Describe the models, methodology and forcing functions used.

(B) The flight events and conditions that cause the greatest loads on the payload shall be identified and included in the analysis.

(C) Output from each flight event shall include maximum/minimum tables of interface accelerations and interface loads as well as interface shock response spectra.

(D) Two load cycles will be required per mission: A preliminary loads cycle and a verification loads cycle.

CDRL DESCRIPTION Number: VCLS 2-6

FINAL FLIGHT REPORT

DESCRIPTION/PURPOSE:

After launch, a final post-flight report shall be provided. This report will support the NASA Contracting Officer’s mission success determination.

DATA REQUIREMENTS:

This report shall include, in its entirety, the Contractor’s internal post-flight report produced for the mission.

This report shall also include an assessment of each ICD orbital parameter and environmental condition using flight data, ground observations, or other data sources in accordance with the determination methods proposed by the Contractor under CDRL VCLS 2-3:

i. Pre-flight prediction of expected flight environments (i.e., acoustic/vibration, quasi-static acceleration, thermal, shock and pressure) imposed on the spacecraft assembly by the launch.

ii. Post flight determination of actual flight environments imposed on the spacecraft assembly by the launch. If analysis is required to transform launch vehicle measured data to a spacecraft assembly requirement, that analysis should also be included in the report or provided to in a separate document.

iii. Vehicle data verifying the actual separation command sent to the dispenser and vehicle data indicating the launch vehicle state and health just prior to and after the separation command was sent.

iv. Explanation of significant differences between the predicted and actual flight environments.

CDRL DESCRIPTION Number: VCLS 2-7

SPACECRAFT INTEGRATED PROCEDURES

DESCRIPTION/PURPOSE:

Site procedures for various operations that involve the payload and/or the launch vehicle/payload interfaces.

Provide as a minimum, the following integrated procedures (If applicable):

(A) Payload/ launch vehicle electrical interface verification test

(B) If applicable, payload encapsulation and transport from or within the payload processing facility to the launch vehicle integration facility/location.

(C) Payload/launch vehicle mate (includes CubeSat to dispenser integration, and adapter and vehicle mates, if separate)

(D) Fairing installation

(E) Any transport of the payload