Attachment 03_CDRLS.pdf

VADR-RFP Attachment 03 - CDRL 80KSC021R0034 Rev A

ATTACHMENT 03

CONTRACT DATA REQUIREMENTS LIST (CDRL)

FOR

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

VADR - RFP Attachment 03 - CDRL 80KSC022R0034 Rev A

This page left intentionally blank.

CONTRACT DATA REQUIREMENTS LIST (CDRL)

The Contract Data Requirements Lists (CDRL) for CLIN 1 and CLIN 2 identify critical elements of the contracted effort where NASA requires aspects of mission integration insight and approval. The following CDRLs define 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 KSC ELV Library and the Contracting Officer. The Contractor shall notify the Contracting Officer in writing of CDRL delivery. All electronic formats shall be mutually acceptable to ensure government accessibility.

The requirements for CLIN 1 CDRLs begin with Table A3-1: CDRL Index for CLIN 1 and the requirements for CLIN 2 CDRLs begin with Table A3-2: CDRL Index for CLIN 2.

Note: Data required in response to this factor that is maintained by a subcontractor may be delivered by either the Offeror, or subcontractor, directly to the Contracting Officer.

Table A3-1: CDRL Index for CLIN 1

Item Document Approval/ Review/Submit

Initial Submittal Date

Subsequent Submittal Date

Documentation

VADR 1-1 Formal Meeting & Review Documentation

Approval (B & D (vi);

Review all other

(A) as specified in the CDRL

(B, C, D) at Review plus 1W

As Required (A/R)

Mission Integration

VADR 1-2 Interface Control Document (ICD) Approval

Preliminary ICD at

ATP + 3M

Baseline ICD at MSDR and A/R

VADR 1-3

Interface Control Document (ICD) Requirements Verification Matrix

Approval

MSDR

A/R or with each ICD revision

VADR 1-4 Launch Vehicle Schedules Review ATP + 3M L-6M, A/R

Analysis

VADR 1-5 Performance and Guidance Accuracy Analysis (PGAA)

Initial Submittal = Review, Subsequent Submittals =

Approval

ATP+TBP L-9M, A/R

VADR 1-6 Final Mission Analysis

(FMA)

Approval Receipt of P/L Data + TBP

A/R

VADR 1-7 Payload/Expended Stage Separation Analysis

Approval ATP+TBP L-TBP

VADR 1-8 Payload Fairing Venting Analysis

Review Receipt of P/L Data + TBP

A/R

VADR 1-9 Payload Fairing Clearance Analysis

Review Receipt of P/L Model + TBP

L-TBP

VADR 1-10 Coupled Dynamic Loads Analysis

Approval Receipt of P/L Model + 3M

L-6M, A/R

Review/Submit

Initial Submittal Date

Subsequent Submittal Date

Documentation

VADR 1-11 Payload/Launch Vehicle EMC Compatibility Analysis

Review (A & C) ATP+3M

(B) L-12M

(A & C) A/R in CDRL

(B) L-3M

VADR 1-12 Quick Look Flight Report Review TBP A/R

VADR 1-13 Final Flight Report Review Separation + 2M A/R

Engineering

VADR 1-14 Integrated Procedures Initial Submittal = Review, Subsequent Submittals =

Approval

Draft 30D Prior to Use

1W Prior to Use

CDRL DESCRIPTION Number: VADR 1-1

FORMAL MEETING & REVIEW DOCUMENTATION

DESCRIPTION/PURPOSE:

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

DATA REQUIREMENTS:

Formal review documentation shall include:

(A) Presentation packages for the review for NASA attendees due 3 days prior to the Review

(i) Review requirements are documented in Attachment 02, Meetings and Formal Reviews

(B) Minutes from each formal review and archival updates to original presentation packages, as required, within two weeks of the meeting or 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: VADR 1-2

INTERFACE CONTROL DOCUMENT (ICD)

DESCRIPTION/PURPOSE:

The ICD shall identify and define 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. The final revision to the ICD, including all approved changes and waivers, will be used for the mission success determination. The Contractor shall comply with the latest approved revision of the ICD, to include all approved changes and waivers.

Preliminary ICD is the first CDRL release of the ICD and is allowed 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.1.1 Structural Interfaces

3.1.1.1 Static Payload Envelope

3.1.1.2 PLF Clearance Requirements

3.1.1.3 SC Clearance Requirements

3.1.1.4 Separation System Characteristics

3.1.1.5 SC Access Requirements

3.1.2 Structural Loads and Strength

3.1.2.1 SC Stiffness

3.1.2.2 SC Interface Loads

3.1.2.3 Strength

3.1.2.4 SC Load Factors

3.1.3 Mass Properties

3.1.3.1 SC Mass Properties

3.1.3.2 SC Propellant Data

3.2 Electrical Interfaces

3.2.1 Airborne Interfaces

3.2.1.1 Standard Electrical Interfaces

3.2.1.2 Separation Indication

3.2.1.3 Interface Electrical Constraints

3.2.1.4 Separation System Electrical Interface

3.2.2 SC Umbilical Interface

3.2.2.1 T-0 Umbilical Interface

3.2.2.2 EGSE Interface Electrical Constraints

3.2.3 EGSE Telemetry/Command/Data Link

3.2.4 Electrical Grounding

3.2.4.1 Spacecraft Grounding

3.2.4.2 Support Equipment Grounding

3.2.4.3 Personnel Grounding

3.2.4.4 Ground Continuity

3.3 Environmental Interfaces

3.3.1 Thermal

3.3.1.1 SC Thermal Environments

3.3.2 Contamination

3.3.2.1 Payload Fairing Purge

3.3.2.1.1 Spacecraft Transport to the Launch Complex

3.3.2.1.2 Spacecraft at Launch Complex

3.3.2.2 GHe Concentration

3.3.2.3 Payload Compartment Cleanliness

3.3.2.4 Spacecraft Contaminant Deposition Limits

3.3.2.4.1 Particulate

3.3.2.4.2 Molecular

3.3.2.5 Spacecraft Instrument GN2 Purge

3.3.3 Ascent Pressure

3.3.4 Dynamics

3.3.4.1 Sine Vibration

3.3.4.2 Acoustics

3.3.4.3 Shock

3.3.5 Electromagnetic Compatibility

3.3.5.1 EMI Safety Margin

3.3.5.2 Radiated Emissions

3.3.5.2.1 Spacecraft Maximum Allowable Radiated Emissions

3.3.5.2.2 Launch Vehicle Maximum Allowable Radiated Emissions

3.3.5.2.3 SC RF Susceptibility

3.3.5.2.4 Launch Site RF Environment

3.3.5.2.5 Portable Sources Radiated Emissions

3.3.5.3 PLF Electrostatic Discharge

3.3.5.4 Thermal Blanket Electrostatic Discharge

3.3.5.5 RF Transmitter/Receiver Systems EMC

3.3.5.6 Lightning

3.3.5.7 SC/LV Interface Electrical Bonding

3.4 Flight Design

3.4.1 Mission Orbit Specification

3.4.2 Launch Window

3.4.3 SC Separation

3.4.4 Sun Angle Constraint

3.4.5 Thermal Roll

3.4.6 LV Telemetry Data

3.4.6.1 SC Separation State Vector

3.4.6.2 SC Provided Post Separation Data

3.5 Ground Operations

3.5.1 Spacecraft Contractor Supplied Ground Support Equipment

3.5.2 Payload Processing Facility

3.5.2.1 Facility Dimensions

3.5.2.2 Power/Electrical

3.5.2.3 Environment

3.5.2.4 Equipment

3.5.2.5 Furnishings

3.5.2.6 Commodities

3.5.2.7 Consumables & Garments

3.5.2.8 Safety/Security

3.5.2.9 Communications and Telemetry

3.5.3 Launch Complex Ground Operations

3.5.3.1 GSE

3.5.3.2 Ground Operations Communications

3.5.4 SC Transport

3.5.4.1 Processing Facility to Launch Complex Transport

3.5.4.2 SC Hoist and Mate Loads

3.5.5 PLF Environmental Control System

3.5.6 Fluids And Gases Requirements

3.6 Safety Requirements

4.0 MISSION SUCCESS CRITERIA & DETERMINATION METHODOLOGY

The Contractor’s shall provide a list of proposed criteria 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. The criteria and methodology, which will be determined throughout development and execution of the ICD, will be used to support the Contracting Officer’s determination of mission success.

CDRL DESCRIPTION Number: VADR 1-3

INTERFACE CONTROL DOCUMENT (ICD) REQUIREMENTS VERIFICATION MATRIX

DESCRIPTION/PURPOSE:

A verification matrix shall document and track all ICD requirements and methods by which they will be verified by the responsible organization. The verification matrix shall list the final documentation that will be provided of the verification approved by the cognizant Contractor engineer.

ICD verification matrix shall include the following:

• 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: VADR 1-4

LAUNCH VEHICLE SCHEDULE

DESCRIPTION/PURPOSE:

NASA mission launch vehicle production schedule with status and interdependencies of other launch vehicle production. Mission integration schedule and status for the NASA launch service.

DATA REQUIREMENTS:

1. The contractor shall provide a detailed launch vehicle production and mission integration schedule for the launch service on task order.

Schedule shall include at a minimum:

• Production and major sub-contractor delivery milestones

• Qualification schedule of major subsystems including but not limited to: core stage tanks, flight computer, Inertia Navigation Unit (INU), engine actuators, main batteries, PLF, PLA, separation systems, and flight software processes/test status (Not applicable for NASA certified launch vehicles)

• Major test milestones

• Key analysis inputs and deliverables

• Critical path identification

2. Include a high-level schedule including the production interdependencies with other missions in queue and with other product lines.

CDRL DESCRIPTION Number: VADR 1-5

PERFORMANCE AND GUIDANCE ACCURACY ANALYSIS (PGAA)

DESCRIPTION/PURPOSE:

This analysis is prepared using the best available mission requirements (payload mass properties, insertion state vector requirements, tracking requirements, etc.) to identify any potential problems inherent in accomplishing the mission objectives. This analysis shall include parametric trade studies.

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

(C) Performance capability, margins and reserves, including description of how performance reserve is calculated

(D) Sequence of events and tracking coverage

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

(F) Separation trajectories and post separation contact probability prediction (s)

(G) Launch vehicle summary weight statement

(H) 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

(I) Definition of all coordinate systems used

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

(K) 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 VADR 1-5 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: VADR 1-6

FINAL MISSION ANALYSIS (FMA)

DESCRIPTION/PURPOSE:

This analysis is prepared based on payload requirements resulting from NASA review of the PGAA and contains information similar to that in the PGAA. This analysis supports pre-flight verification of compliance with mission requirements.

DATA REQUIREMENTS:

The FMA shall include, as a minimum:

(A) The nominal 5 or 6 Degree of Freedom (DOF) trajectory simulation for each targeted insertion condition utilizing actual weights and propulsion models (electronic format is preferred).

(B) All Data Requirements identified in PGAA Data Requirement Description.

CDRL DESCRIPTION Number: VADR 1-7

PAYLOAD/EXPENDED STAGE SEPARATION ANALYSIS

DESCRIPTION/PURPOSE:

The Payload/Expended Stage Separation Analysis is required to demonstrate that adequate separation distance exists between the payload and the upper stage during the relative motion predicted following payload deployment. The analysis is also required to demonstrate that payload tip-off rates satisfy requirements. This analysis supports pre-flight verification of compliance with mission requirements.

DATA REQUIREMENTS:

(A) Provide nominal, 3-sigma, or worst-case payload tip-off rates and cone angles (cone angles if deployed while spinning) at deployment.

(B) The analysis shall include the effects of residual thrust, vehicle and payload mass properties uncertainties, and separation mechanism uncertainties. Additionally, include any methods utilized to ensure contamination upon separation is prevented.

(C) The report documenting this analysis shall list and describe all dispersion sources used for the analysis, mass properties data sources, and all coordinate systems used.

(D) Expended stage/payload relative motion analysis following payload deployment

CDRL DESCRIPTION Number: VADR 1-8

PAYLOAD FAIRING VENTING ANALYSIS

DESCRIPTION/PURPOSE:

This analysis shall evaluate and verify that the payload depressurization rate requirements are satisfied.

DATA REQUIREMENTS:

The Payload Fairing Venting Analysis shall be based on the mission trajectory, payload geometry, and ventable and non-ventable volume.

CDRL DESCRIPTION Number: VADR 1-9

PAYLOAD FAIRING CLEARANCE ANALYSIS

DESCRIPTION/PURPOSE:

This analysis documents/demonstrates that sufficient clearance exists under dynamic conditions is available to prevent payload damage from lift-off through payload fairing jettison.

DATA REQUIREMENTS:

The Payload Fairing Clearance Analysis shall cover the dynamic response throughout flight prior to p The Payload Fairing Clearance Analysis shall include, as a minimum, the effects of:

(A) Disconnect forces

(B) Actuator forces

(C) Dynamic response

(D) Manufacturing tolerances

CDRL DESCRIPTION Number: VADR 1-10

COUPLED DYNAMIC LOADS ANALYSIS

DESCRIPTION/PURPOSE:

This analysis defines flight loads and deflections for the 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. The flight events and conditions that cause the greatest deflections in the fairing and payload (including instances of minimum clearance) shall be identified and included in the analysis.

(C) Output from each flight event shall include maximum/minimum tables of payload selected

Acceleration Transformation Matrices (ATM), interface forces, and internal Load Transformation Matrices (LTM).

(D) Worst-case payload fairing dynamic relative deflections shall be identified and included.

CDRL DESCRIPTION Number: VADR 1-11

PAYLOAD/LAUNCH VEHICLE EMC COMPATIBILITY ANALYSIS

DESCRIPTION/PURPOSE:

This Electromagnetic Compatibility (EMC) analysis demonstrates that requirements in the ICD are satisfied and ensures that S/C ordnance sub-systems will not be unintentionally triggered by electromagnetic disturbances generated by the launch vehicle, Range or other external sources. This is to ensure that the payload electromagnetic (EM) energy exposure requirements will not be exceeded.

At a minimum, the following data items shall be delivered in approved electronic formats:

(A) An EMC Control Plan including EMC management processes, design guidelines, test requirements and standards used by the launch service provider. Subsequent submittal required with any change from the initial submittal.

(B) A Spacecraft/Launch Vehicle Electromagnetic Compatibility Analysis which includes:

(i) Identification of test levels for S/C and launch vehicle susceptibility, intentional and unintentional emissions.

(ii) Field strengths expected from known ground and external emitters.

(iii) Calculation of EMI safety margins between S/C hardware susceptibility levels and launch vehicle and external emissions sources.

(C) A lightning plan including design and/or operational considerations regarding the presence or effects of lightning. Subsequent submittal required with any change from the initial submittal.

CDRL DESCRIPTION Number: VADR 1-12

QUICK LOOK FLIGHT REPORT

DESCRIPTION/PURPOSE:

After each launch, a quick look post-flight analysis shall be performed using evaluations of all available vehicle telemetry and insertion performance. A briefing may satisfy the intent of this report.

The data report shall include:

(A) Trajectory and performance data

(B) Orbital accuracy estimates

(C) Preliminary vehicle subsystem system performance

(D) Preliminary evaluation

CDRL DESCRIPTION Number: VADR 1-13

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 VADR 1-2.

This report shall also include:

i. Orbit elements determined from vehicle guidance data

ii. 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.

iii. 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.

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

v. Vehicle data indicating payload separation.

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

vii. As flown vehicle sequence data

viii. All recorded payload telemetry to NASA, if applicable

CDRL DESCRIPTION Number: VADR 1-14

INTEGRATED PROCEDURES

DESCRIPTION/PURPOSE:

Site procedures for various operations that involve the payload and/or the launch vehicle/payload interfaces to evaluate any potential impacts to the payload and/or NASA resources.

Provide the following integrated procedures (if applicable):

(A) Payload/ launch vehicle mechanical and electrical integration including fit check

(B) Payload encapsulation

(C) Payload/launch vehicle mate, test and closeout procedures (if applicable this includes CubeSat to dispenser integration, and payload adapter and vehicle mates)

(D) Combined system test/final readiness test if payload is powered on

(E) Any transport or handling of the payload

(F) Launch countdown procedures and planned or real-time deviations that affect spacecraft interface as defined in the ICD.

Table A3-2: CDRL Index for CLIN 2

Review/ Submit

Initial Submittal Date

Subsequent Submittal Date

Documentation

VADR 2-1 Formal Meeting & Review Documentation

Approval (B & D (vi));

Review all other

(A) as specified in the CDRL

(B, C, D) at Review plus 1W

As Required (A/R)

Mission Integration

VADR 2-2 Interface Control Document (ICD) Approval Baseline ICD at

ATP + 2M

A/R

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

ATP + 2M

A/R or with each

ICD revision

Engineering

CDRL DESCRIPTION Number: VADR 2-1

FORMAL MEETING & REVIEW DOCUMENTATION

DESCRIPTION/PURPOSE:

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

Formal review documentation shall include:

(A) Presentation packages for the review for NASA attendees due 3 days prior to the Review.

(i) Reviews as documented in Attachment 02, Meetings and Formal Reviews

(B) Minutes from each formal review and archival updates to original presentation packages as required

(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: VADR 2-2

INTERFACE CONTROL DOCUMENT (ICD)

DESCRIPTION/PURPOSE:

The ICD shall identify and define 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. The final revision to the ICD, including all approved changes and waivers, will be incorporated by reference into the contract via contract modification prior to the mission success determination. The Contractor shall comply with the latest approved revision of the ICD, to include all approved changes and waivers.

Preliminary ICD is the first CDRL release of the ICD and is allowed 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.

CDRL DESCRIPTION Number: VADR 2-3

INTERFACE CONTROL DOCUMENT (ICD) REQUIREMENTS VERIFICATION MATRIX

DESCRIPTION/PURPOSE:

A verification matrix shall document and track all ICD requirements and methods by which they will be verified by the responsible organization. The verification matrix shall list the final documentation that will be provided of the verification approved by the cognizant Contractor engineer.

ICD verification matrix shall include the following:

• ICD requirement language

• ICD requirement paragraph number

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

• Responsible Organization

• Verification Plan

• Verification Source

• Notes/Comments

• Status