02b_Exhibit_B_CDRL_30_Sep_2015.pdf

PDF 521 KB Posted Sep 30, 2015

Attached to: EELV Phase 1A GPS III Launch Services Federal contract opportunity
Solicitation number: 15-102
Issued by: Department of the Air Force Space Command Space and Missile Systems Center

About this file

From the source

02b Exhibit B CDRL

View the file

Other files for this federal contract opportunity

Other files attached to EELV Phase 1A GPS III Launch Services, newest first.
File	Type	Posted
06_Acceptance_Criteria_30_Sep_2015.pdf	PDF	Sep 30, 2015
07_Instructions_to_Offerors_30_Sep_2015.pdf	PDF	Sep 30, 2015
05_Small_Business_Plan_30_Sep_2015.pdf	PDF	Sep 30, 2015
11_Payment_Plan_GPS_III_30_Sep_2015.pdf	PDF	Sep 30, 2015
04_DD254_30_Sep_2015.pdf	PDF	Sep 30, 2015
01_Model_Contract_30_Sep_2015.pdf	PDF	Sep 30, 2015
10_Government_Property_30_Sep_2015.pdf	PDF	Sep 30, 2015
09_Mission_Requirements_Annex_(See_Bidder's_Library).pdf	PDF	Sep 30, 2015
08_Evaluation_Criteria_30_Sep_2015.pdf	PDF	Sep 30, 2015
02a_Exhibit_A_CDRL_30_Sep_2015.pdf	PDF	Sep 30, 2015
03_PWS_30_Sep_2015.pdf	PDF	Sep 30, 2015
02c_Exhibit_C_CDRL_30_Sep_2015.pdf	PDF	Sep 30, 2015
07_Attachment_5_Draft_Instructions_to_Offerors_(updated_15_Jul_15).pdf	PDF	Jul 15, 2015
10_Attachment_8_Government_Property_(updated_15_Jul_15).pdf	PDF	Jul 15, 2015
08_Attachment_6_Draft_Evaluation_Criteria_(updated_15_Jul_15).pdf	PDF	Jul 15, 2015
03_Attachment_1_Draft_PWS_(updated_15_Jul_15).pdf	PDF	Jul 15, 2015
02_Draft_CDRLs_Exhibit_A.pdf	PDF	Jul 15, 2015
09_Attachment_7_Mission_Requirements_Annex_(See_Bidder's_Library).pdf	PDF	Jul 15, 2015
01_Draft_Model_Contract.pdf	PDF	Jul 15, 2015
06_Attachment_4_Draft_Acceptance_Criteria_(updated_15_Jul_15).pdf	PDF	Jul 15, 2015
02_Draft_CDRLs_Exhibit_C_(updated_15_Jul_15).pdf	PDF	Jul 15, 2015
04_Attachment_2_Draft_DD_254_(updated_15_Jul_15).pdf	PDF	Jul 15, 2015
05_Attachment_3_Draft_Small_Business_Plan.pdf	PDF	Jul 15, 2015
02_Draft_CDRLs_Exhibit_B_(updated_15_Jul_15).pdf	PDF	Jul 15, 2015
11_Attachment_9_Draft_Payment_Plan_(updated_15_Jul_15).pdf	PDF	Jul 15, 2015
09_DRAFT_GPS_III_MRA_Version_2015-04-30.pdf	PDF	May 14, 2015
DRAFT_GPS_III_RFP_CRM.XLSX	XLSX spreadsheet	May 14, 2015
07_Draft_Attach_5_Instr_to_Offerors_11_May_(GPSIII).pdf	PDF	May 14, 2015
03_draft_attachmnt_1_pws_11_may_(GPS_III).pdf	PDF	May 14, 2015
05_draft_attachmnt_3_small_business_plan.pdf	PDF	May 14, 2015
02_Draft_CDRLs_20150511_(GPS_III).pdf	PDF	May 14, 2015
01_Draft_1449_Model_Contract_110515.pdf	PDF	May 14, 2015
NDA_Bidders_Library_Access.pdf	PDF	May 14, 2015
11_draft_payment_plan_atch_9_150511_GPS_III.pdf	PDF	May 14, 2015
08_Draft_Attach_6_Eval_Criteria_11_May_GPS_III.pdf	PDF	May 14, 2015
10_government_property_attachmnt_8_(GPS_III).pdf	PDF	May 14, 2015
06_attachmnt_4_acceptance_criteria_150511_(GPS_III).pdf	PDF	May 14, 2015
04_draft_attachmnt_2_dd_254_150511_(GPS_III).pdf	PDF	May 14, 2015

Show all 38

On GovTribe

Work with this file on GovTribe

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

EXHIBIT B

FA8811-15-R-0001

EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV)

PHASE 1A

CONTRACT DATA REQUIREMENTS LIST (CDRLs)

30 September 2015

Department of the Air Force

Space and Missile Systems Center

Launch and Range Systems Directorate

Los Angeles Air Force Base, California

CDRL General Instructions CDRL Address List CDRL Distribution List CDRLs

CDRL GENERAL INSTRUCTIONS

CONTRACT DATA REQUIREMENTS LIST (CDRL)

A list of data requirements authorized for this specific procurement and made a part of this contract. The contractual method is the use of Department of Defense Form (DD Form) 1423s, Contract Data Requirement List (CDRL), which specifies the data which is required to be delivered to the government. For the purpose of this agreement, the “contract” applies for each Launch Vehicle Service order.

DATA ITEM NUMBER

If the Contract is awarded multiple Launch Vehicle (LV) Service orders, the Contractor shall use a sequential double alpha, single numeric number scheme. For example, Order 1 will have CDRLs AA01–AA11, AB01–AB20, and AC01; and Order 2 will have CDRLs BA01–BA11, BB01–BB20, and BC01.

DATA ITEM DESCRIPTIONS (DIDs)

The DID is a specification for the preparation of data. The DIDs listed on the CDRLs were selected from the Department of Defense (DoD) Index of Specifications and Standards (DoDISS) listed on the Acquisition Streamlining and Standardization Information System (ASSIST).

DID TAILORING

DID tailoring is made to either relax format requirements or to tailor the DID to be in consonance with the source document tailoring contained in the Performance Work Statement (PWS). Since contract data requirements are normally a by-product of some contract task, if the requirements of the DID are in conflict with the tailored application of the source document as reflected in the PWS, the latter takes precedence.

DATA DELIVERY DATES

For Soft Copies, delivery of data is to be construed as the date data is available in the contractors’ data management system and electronic notification is sent to addressees.

For Hard Copies, delivery of data is to be construed as “On Dock” dates at destination. Provision of a 3-day postage handling period from postmark at contractor's facility to “On-Dock” delivery at destination meets this requirement, unless otherwise stated in CDRL. The date of government signature at destination, if courier service is used, is to be construed as the “On Dock” date. It shall be the contractor's responsibility to ensure data delivery prior to end of business on the due date if a courier service is used in lieu of the United States (U.S.) Postal Service.

If due date falls on weekend or government holiday, data shall be due on the next scheduled government workday.

DD FORM 250 REQUIREMENTS

Block 7 of the CDRL will indicate whether inspection and acceptance of the data by DD Form 250 is required.

“Draft” copies submitted for advance approval and “Preliminary” h copies submitted are exempt from the DD Form 250 requirements.

ADDITIONS TO DISTRIBUTION

If an addressee is added to distribution, or distribution quantities have been increased to an existing addressee, initial submittal to new addressee shall include the basic document and revisions as appropriate.

COMMUNICATIONS

Any correspondence related to requests for data delivery deviations, amendments, additions, or deletions shall be addressed to the PCO with an information copy to the government Data Management Officer (DMO).

For those data items where “LT” (Letter of Transmittal) is indicated in Block 7 of the CDRL, the Contractor shall utilize a Letter of Transmittal (LOT). Each copy submitted shall have a LOT attached. In addition, the contractor shall furnish one copy of each LOT (without data) to the government DMO. Change pages shall indicate updates by a bar in the margin adjacent to the change and encompassing all changed portions.

CDRL ADDRESS LIST AND DATA DISTRIBUTION LIST

The Address List provides the complete mailing address for each addressee and a mailing code.

The Data Distribution List provides information regarding quantities for shipment (normally in Blocks 14 and 15 of the CDRL) to each mailing code. Quantity of Hard deliverables and Soft deliverables will be indicated to the left and right of the “/,” respectively. See CDRL for possible additional format or delivery instructions.

DATA APPROVALS

While all data are subject to government approval, selected data will require advanced approval. The letter “A” appearing in Block 8 of the CDRL designates such data. Approval will be required on every submittal (e.g., the Preliminary, Draft, Finals that incorporate government comments, and revisions or change pages, if applicable). The approving authority shall be the Procuring Contracting Office (PCO). Delivery of the Final data shall be submitted within 30 CD after receipt of government approval of Draft unless otherwise stated on CDRL.

CODES USED ON THE CDRL

The following codes may be used as described below.

a. Block 7: DD Form 250 requirements

CODE WHEN USED

LT Letter of Transmittal only

b. Block 8: Approval code

CODE WHEN USED

A Approval is required by government on all submittals.

N/A Approval is not required.

c. Block 10: Frequency

CODE (Limit to five characters)

DAILY Daily WEKLY Weekly BI-WE Each 2 weeks MTHLY Monthly BI-MO Each 2 months QRTLY Quarterly ANNLY Annually SEMIA Each 6 months OTIME One time ONE/R One time, and revisions R/ASR Revisions as required *ASREQ As required DFDEL Deferred delivery DFORD Deferred ordering ONE/P 1-time preliminary draft 2TIME Two separate submittals

*When ASREQ is used in items 10, 11, 12 or 13, an explanation of the requirement must be entered in item 16.

d. Blocks 12 and 13: Date of 1st and Subsequent Submissions

SDA = Government APPROVAL CDR = Critical Design Review CA = Contract Award IPR = In Process Review CO = Change Order FCA = Functional Configuration Audit

SA = Supplemental Agreement PCA = Physical Configuration Audit SRR = System Requirements Review FLT = Flight Test Review SDR = System Design Review CD = Calendar Days PDR = Preliminary Design Review WD = Working Days EOC = End of Contract ATP = Authority to Proceed ILC = Initial Launch DACA = Days After Contract Award*

* For this agreement, Contract Award is the same as Launch Vehicle Services Order

ELECTRONIC DISTRIBUTION

CDRLs shall be delivered on the contractors’ data management system(s). The contractor shall enable remote access to these systems by all SPO personnel (AF, Aerospace, SE&I, and SETA) subject to applicable terms on this contract.

An index of addressees to be allowed access to or to be notified of CDRL availability will be provided by government DMO via e-mail notification for contractor’s implementation. Access Lists will be updated, as required, without modification to the contract. The contractor shall use an acceptable electronic format that is compatible with existing government systems, unless a precise format is specified in the CDRL.

CDRL ADDRESS LIST

1. HQ Space & Missile Systems Center (AFSPC) LR

Launch Systems Directorate 483 North Aviation Blvd.

Los Angeles AFB El Segundo, CA 90245-2808 smc.lrdm@us.af.mil

a. LRE, Bldg. 271 B3-405 (Data Management Office, DMO)

b. LRE

c. LRP

d. LRK

e. LRG

f. LRS

NOTE: Submit Hard Copies to 1.a. for distribution, if applicable

2. HQ Space & Missile Systems Center (AFSPC) SAF/SL

Attn: SAF/SL, Bldg. A5 483 North Aviation Blvd.

Los Angeles AFB El Segundo, CA 90245-2808

3. 30th Launch Group 30 LCG

4th Space Launch Squadron Directorate of Engineering Attn: Data Desk 1515 Iceland Ave., Suite 222 Bldg. 8500 Vandenberg AFB, CA 93437-5321

4. 45 LCG/45 LCSS 45 LCG

Attn: Data Library 15270 Samuel C. Phillips Parkway (CCAFS) Building 1645 Patrick AFB, FL 32925-2009

5. Defense Cost and Resource Center (DCARC) DCARC

201 12th Street South Suite 220 Arlington, VA 22202

(703) 601-4850

6. DCMA, TBD DCMA

7. NRO Operations Squadron NOPS

401 Discoverer Ave. Ste 32 Schriever AFB, CO 80912 NOPS_Launch@us.af.mil

NOTE: The contractor shall provide electronic access of CDRLs, and notification via e-mail to select addressees, when requested, in accordance with government provided Access List index. Addressees (for notification purposes only) not listed above may include, for example, Aerospace, DCMA, Patrick AFB, Vandenberg AFB, SE&I, and SETA contractors.

It is not the responsibility of the Contractor to make actual distribution of either electronic or hard copy CDRLs to these unnamed addressees. Draft documents delivered electronically must be marked “draft.” Notifications for Revisions to required CDRL deliveries shall be provided to all POCs.

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503 Please DO NOT RETURN your form to either of these addresses Send completed form to the Government issuing Contracting officer for the Contract/PR No listed in Block E

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A TDP TM OTHER X

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

B001 Technical Report Launch Schedule/Date Recommendation 4 AUTHORITY (Data Acquisition Document No.) 5 CONTRACT REFERENCE 6 REQUIRING OFFICE DI-MISC-80508/T Performance Work Statement, Para 3.1.6.2 SMC/LRG

7 DD 250 REQ 9 DIST STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

LT BLK 16 BLK 16 b COPIES

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

SUBMISSION

a ADDRESSEE

FINAL

N/A BLK 16 BLK 16 Draft Reg Repro

16 REMARKS See Distribution List

1. (BLK 4):

a. Replace 2 with: Contractor Format.

b. Replace 3 with:

i. The Contractor shall provide a Launch Slot Recommendation (LSR) for each launch order identifying the following:

1. A Launch Slot within the previously assigned Launch Period

2. Additional supplemental hardware or capability when required

3. A decision date for Government concurrence. If not specified, need date is fifteen (15) calendar days after Government receipt of LSR.

ii. The Contractor shall provide a Launch Date Recommendation (LDR) for each launch order identifying the following:

1. Specific Launch Date within the previously authorized Launch Slot

2. Assigned launch site

3. Deadline for Government provided payload/spacecraft ready for Launch Vehicle mate

4. Decision date for Government concurrence. If not specified, need date is fifteen (15) calendar days after Government receipt of LDR.

2. (BLKs 10, 11,12,13)

a. The Contractor shall provide the LSR no later than 405 CDs (approximately 13 and a half [13 5] months) prior to the beginning of the Launch Period.

b. The Contractor shall provide the LDR no later than 225 CDs (approximately seven and a half [7.5] months) prior to the beginning of the Launch Slot.

15 TOTAL

G PREPARED BY H DATE I APPROVED BY J DATE

Electronically Generated PAGE 1 OF 1 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A TDP TM OTHER X

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

B002 System Safety Program Plan (SSPP) 4 AUTHORITY (Data Acquisition Document No.) 5 CONTRACT REFERENCE 6 REQUIRING OFFICE DI-SAFT-81626 Performance Work Statement, Para 3.1.7 SMC/LRE

7 DD 250 REQ 9 DIST STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

LT BLK 16 BLK 16 b COPIES

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

A CA Blk16 Draft Reg Repro

16 REMARKS See Distribution List

(BLKs 10, 11,12,13)

a. Draft SSPP shall be submitted 90 DACA.

b. Final SSPP shall be submitted 60 CD after receipt of Government comments to the Draft

SSPP. If there are no Government comments, the Draft shall be considered the final submittal.

c. Updates shall be submitted as significant revision to the System Safety Program are made or by PCO direction.

Electronically Generated PAGE 1 OF 1 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A TDP TM OTHER X

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

B003 Safety Assessment Report (SAR) 4 AUTHORITY (Data Acquisition Document No.) 5 CONTRACT REFERENCE 6 REQUIRING OFFICE DI-SAFT-80102B/T Performance Work Statement, Para 3.1.7 SMC/LRE

7 DD 250 REQ 9 DIST STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

LT R/ASR 60 DACA b COPIES

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

N/A CA R/ASR Draft Reg Repro

16 REMARKS See Distribution List

(BLK 4):

1. Delete 10.2.2.b.

2. Replace 10.2.2.c with “A brief description of the system and its major subsystems and components.

Software and its roles shall be included in this description.”

3. Delete 10.2.3.

4. Replace 10.2.4 with: “10.2.4. This section may be developed by referencing other program documentation and shall include the following:

a. The specific risk matrix used to classify hazards

b. The results of analyses and tests performed to identify hazards, assess risks, and verify/validate effectiveness of mitigation measures

c. Hazard Tracking System (HTHS) data

d. A summary of risks for each identified hazard

e. Any Hazardous Material (HAZMAT) contained within the system or required for the operations and support of the system

f. Test or other event-unique mitigation measures necessary to reduce risks

g. Recommendations applicable to hazards located at the interface of the system with other systems”

5. Delete 10.2.5.

6. Replace 10.2.6 with “10.2.6 Reference. List all pertinent references, including (but not limited to) test and analysis reports, standards and regulations, specifications and requirements documents, operating manuals, and maintenance manuals.”

Electronically Generated PAGE 1 OF 1 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A TDP X TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

B004 Hazardous Materials Management Program (HMMP) Plan 4 AUTHORITY (Data Acquisition Document No.) 5 CONTRACT REFERENCE 6 REQUIRING OFFICE DI-MGMT-81398B Performance Work Statement, Para 3.1.15 SMC/LRE

7 DD 250 REQ 9 DIST STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

LT ASREQ 30 DACA b COPIES

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

N/A N/A BLK 16 Draft Reg Repro

16 REMARKS See Distribution List

(BLK 13): Updates shall be submitted as significant revisions to the plan are made or by PCO direction.

Electronically Generated PAGE 1 OF 1 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A TDP X TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

B005 Contractor’s Standard Operating Procedures Compliance Document Tailoring 4 AUTHORITY (Data Acquisition Document No.) 5 CONTRACT REFERENCE 6 REQUIRING OFFICE DI-MGMT-81580/T Performance Work Statement, Para 3.2. SMC/LRE

7 DD 250 REQ 9 DIST STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

LT BLK 16 90 DACA b COPIES

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

A N/A BLK 16 Draft Reg Repro

16 REMARKS See Distribution List

1. (BLK 4): Replace 3. Content. with :

“3. Content.

a. For the following compliance documents, the contractor shall submit either

1) Tailoring to the standard as a redlined document and a listing of the tailored items and rationale for each change (Word or Excel) or

2) Contractor’s command media documentation that meets the intent of the standard and a mapping of the requirements of the standard to the command media (Word or Excel) (no mapping required if command media was previously assessed and mutually agreed upon to be acceptable).

Compliance Documents:

AIAA S-080-1998, Space Systems, Metallic Pressure Vessels, Pressurized Structures, and Pressure Components

AIAA S-081A-2006, Space Systems – Composite Overwrapped Pressure Vessels (COPV)

AIAA S-110-2005, Space Systems – Structures, Structural Components, and Structural Assemblies

AIAA S-113-2005, Criteria for Explosive Systems and Devices Used on Space and Launch Vehicles

AIAA S-114-2005, Moving Mechanical Assemblies for Space and Launch Vehicles

AIAA S-120-2006, Mass Properties Control for Space Systems

CNSSD No. 505, Committee on National Security Systems Directive 505, Supply Chain Risk Management

CNSSI No. 1200, National Information Assurance Instruction for Space Systems Used to Support National Security Missions

CPIA 655, Guidelines for Combustion Stability Specifications and Verification Procedures for Liquid Propellant Rocket Engines (Jan 1997)

DOD-W-83575A, Wiring Harness, Space Vehicle, Design and Testing, General Specification

ISO 17666, Space Systems – Risk Management

JANNAF, Test and Evaluation Guidelines for Liquid Rocket Engines

MIL-STD-461F, Electromagnetic, Emissions, and Susceptibility, Requirements for the Control of Electromagnetic Interference

Electronically Generated PAGE 1 OF 2 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A TDP X TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

16 REMARKS See Distribution List

MIL-STD-1528A, Production Management

MIL-STD-1542B, EMC Grounding Requirements for Space System Facilities

NASA-STD-5012, Strength and Life Assessment Requirements for Liquid Fueled Space Propulsion System Engines

SMC-S-001, Systems Engineering Requirements and Products to include SMC-T-005, Tailoring OF Risk Management Requirements in SMC-S-001

SMC-S-002, Configuration Management

SMC-S-003, Quality Assurance for Space and Launch Vehicle

SMC-S-005, Space Systems – Flight Pressurized Systems

SMC-S-006, Solid Rocket Motor Case Design and Test Requirements

SMC-S-008, Electromagnetic Compatibility Requirements for Space Equipment and Systems

SMC-S-011, Part, Materials and Processes Control Program for Expendable Launch Vehicles

SMC-S-013, Reliability Program for Space Systems

SMC-S-016, Test Requirements For Launch, Upper-Stage, and Space Vehicles

SMC-S-018, Lithium Ion Battery for Launch Vehicle Application

SMC-S-020, Technical Requirements for Wiring Harness, Space Vehicles

SMC-S-021, Volume 1: Technical Reviews and Audits for Systems, Equipment, and Computer Software

b. For AFSPCMAN 91-710 (Vol 1-7), Range Safety User Requirements and RCC 319-10, Range Commander’s Council (RCC) Flight Termination Systems Commonality Standard, the contract shall submit the Range-approved tailoring.”

2. (BLKs 10, 11, 12, and 13)

a. Submit initial draft 90 DACA for Government review and comment. No Government approval is required.

b. Submit final tailoring/command media for Government approval 30 CD after receipt of

Government comments to be formalized by bi-lateral contract modification.

c. If Contractor makes changes to command media elements that are mapped to standard requirements, then the Contractor shall submit an update within 30 CD of change. Changes will be formalized by bi-lateral contract modification.

Electronically Generated PAGE 2 OF 2 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A TDP X TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

B006 Test/Inspection Report Post Flight Assessment Report 4 AUTHORITY (Data Acquisition Document No.) 5 CONTRACT REFERENCE 6 REQUIRING OFFICE DI-NDTI-80809B/T Performance Work Statement, Para 3.2.7.2 SMC/LRE

7 DD 250 REQ 9 DIST STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

LT ASREQ BLK 16 b COPIES

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Replace 10.2 with the following:

i. The Post Flight Assessment Report shall include but not be limited to:

1. Assessment of achieved orbital parameters

2. Identification of known ICD violations

3. Identification of significant anomalies

4. Assessment of system and sub-system performance to include flight performance, guidance and navigation analysis and flight control for core vehicle and upper stage hardware (solid rocket motors, liquid engines, propulsion, structures, and mechanical systems), payload accommodations (payload adapter fitting and payload fairing), avionics (guidance and navigation control systems, electrical, telemetry and instrumentation, and flight termination system), flight software, ordnance and separation systems, and launch support systems (ground systems, debris analysis and visual data products)

5. Assessment of the spacecraft flight environment to include loads and dynamics, vibration acoustics and shock, and aero and thermal environments

6. Separation assessment

7. Corrective action plans for all anomalies and anomaly resolution

8. Identification of out-of-family observations

9. Any other observation

ii. Data reduction and the post flight assessment shall address all data obtained from the launch for standard flight instrumentations, special flight instrumentation (if such instrumentation is installed), and ground system data.

b. Replace 10.3 with the following: Document content shall be clearly written and describe accomplishments and other facts adequately with no technical errors.

2. (BLKs 10, 12, and 13):

a. Initial Post Flight Assessment Report (covering Items i1-i3 above) shall be submitted within ten

(10) calendar days following Contractor’s receipt of Launch Vehicle (LV) telemetry data.

b. Final Post Flight Assessment Report shall be submitted within 45 calendar days following Contractor’s receipt of LV telemetry data.

Electronically Generated PAGE 1 OF 1 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A TDP X TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

B007 Design Data and Calculations Performance Capabilities Guide 4 AUTHORITY (Data Acquisition Document No.) 5 CONTRACT REFERENCE 6 REQUIRING OFFICE DI-GDRQ-80650/T Performance Work Statement, Para 3.2.9 SMC/LRE

7 DD 250 REQ 9 DIST STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

LT SEMIA BLK 16 b COPIES

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

N/A N/A SEMIA Draft Reg Repro

16 REMARKS See Distribution List

1. (BLK 4):

a. Contractor format is acceptable

b. Delete 10.2, Replace with the following:

i. For each reference orbit mission listed in the Systems Performance Requirements Document (SPRD) and for representative Contractor’s United States Government certified/approved launch vehicle configurations, a report will be submitted describing the launch vehicles’ performance capability and compliance with the associated SPRD mass-to-orbit performance, performance margin, and flight performance reserve requirements.

ii. All performance threats, liens and ground rules and assumptions used for these calculations will be included.

c. Delete 10.3

2. (BLKs 10 and 12): Submission shall occur twice per year, end of March and end of September;

second semiannual submission not required if capabilities remain unchanged.

Electronically Generated PAGE 1 OF 1 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A X TDP TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

B008 Work Management Plan Mission Integration Management Plan

4 AUTHORITY (Data Acquisition Document No.) 5 CONTRACT REFERENCE 6 REQUIRING OFFICE DI-MGMT-81911/T Performance Work Statement, Para 3.4.2 SMC/LRG

7 DD 250 REQ 9 DIST STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

LT ASREQ BLK 16 b COPIES

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Replace 1 with “1. Format. The plan shall be in the contractor’s format. The plan shall be printable on standard size paper, e.g., 8 ½ x 11 or A4.”

b. Replace 3 with “The Mission Integration management Plan describes the contractor’s mission integration services and process flow. The Plan shall contain the following sections:

1.0 Introduction

2.0 Integration Management

2 1 Standard Mission Integration Plan. Provide an overview of the mission integration processes/tasks, citing applicable Performance Work Statement (PWS) paragraphs for reference.

2 2 Integration Schedules. Provide the Mission Integration Schedule and associated schedules used in the Mission Integration process.

2 3 Action Items: Provide an overview of the contractor’s process and tracking system used to ensure action item closure.

3.0 Organizational Responsibilities. For the following organizations describe the organization responsibilities in the Contractor’s Mission Integration process. Provide a graphical representation of the corresponding connections and Points of Contacts between the different organizations.

3 1 Government Organizations

3.1.1 Launch Vehicle Program Office (SMC/LR)

3.1.2 Space Vehicle Program Office (For USAF Missions)

3.1.3 NRO/OSL (For NRO Missions)

3.1.1 USAF Space Wing(s)

3 2 Contractor Organizations

3.2.1 Launch Vehicle Contractor (LVC)

3.2.2 Satellite Vehicle Contractor (SVC) (For USAF Missions)

3.2.3 LSIC (For NRO Missions)

Electronically Generated PAGE 1 OF 2 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A X TDP TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

16 REMARKS

4.0 Key Integration Meetings. Provide the detail description purpose/objectives and composition of the following Contractor meetings:

4 1 Mission Integration Kick-off meeting (Four-party meeting to introduce the mission and integration plan) 4 2 Mission Design Review (MDR) (Preliminary design review for mission integration)

4.3 Mission Verification Review (MVDR) (Critical design review for mission integration)

4.4 Ground Operations Readiness Review (GORR) (For USAF missions) (Launch site readiness for ground operations to integrate spacecraft onto the launch vehicle)

4.5 Pre-Vehicle Ship Review (Verify readiness to ship flight hardware to the launch site)

4.6 Component and Subsystem Readiness Review (CSRR) (Assessment of mission and launch vehicle design and analysis)

4.7 Integrated Operation Readiness Review (IORR) (Review and demonstrate launch site and launch vehicle readiness for integrated ops)

4.8 Space Flight Worthiness Certification Review (SCR) (Establishes readiness of launch system to proceed into countdown operations) 4 9 Launch Readiness Review (LRR) (Final Contractor’s readiness review for launch)

4.10 Other Contractor Mission Readiness Reviews (Any other readiness reviews necessary due to the nature of the mission) 4 11 Launch System Program Level Reviews (Contractual or hardware reviews which the integration team should support)

5.0 Customer Reviews and Rehearsals. Provide description and summarization of level of support to be provided for the following meetings:

5.1 Mission Rehearsals (including academics)

5.2 Spacecraft Mission Readiness Review (MRR)

5.3 Flight Readiness Review (FRR)

5.4 Ground Operations Readiness Review (GORR) (For NRO missions) (Launch site readiness for ground operation to integrate spacecraft onto the launch vehicle)

6.0 Integration Working Groups. Provide a description of the nature and composition of the working groups below.

6 1 Management Working Group (MWG)

6.2 Ground Operations Working Group (GOWG)

6.3 Day-of-Launch Working Group (DOLWG)

6.4 Ascent Operations Working Group (AOWG)

6.5 Rehearsal Working Group (RWG)

6.6 Other Contractor Mission related working group (Any other working group necessary due to the nature of the mission)

7.0 Integration Tasks and Responsibilities

7.1 Space Vehicle Information. Provide a chronological tabular listing of data required from the Space Vehicle Contractor by the Launch Vehicle Contractor;

examples include Space Vehicle (SV) interface requirements, SV CAD/loads models, analyses results required for input to integrated analyses.

7.2 Launch Vehicle (LV) Information. Provide a chronological tabular listing of the information/reports developed during the mission integration process.

(Key products including analyses, reports, requests, schedule, and other documentation or data. May require two Couple Loads Analyses at different times.)

7.3 Mission Integration Control Documents. Provide the list of mission integration control documents the contractor is responsible for preparation, distribution, and maintenance of. Provide the process/plan for maintaining configuration control of these documents.

7.4 Interface Control Document (ICD) and Verification Process. Provide a description of the ICD, the Contractor’s process for development, and verification of the ICD.

Appendix A: Entry/Exit Criteria for Key Integration Meetings Appendices as needed for Definitions, Terms, Abbreviations and Acronyms”

c. Delete 5. Media Requirements.

2. (BLKs 12 and 13)

a. Submit draft 45 DACA for Government review and comment

b. Submit final 30 CD after receipt of Government comments

c. Submit updates to incorporate changes to the document process or upon PCO direction

Electronically Generated PAGE 2 OF 2 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A TDP X TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

B009 System/Segment Interface Control Specification Mission Interface Control Document (ICD) 4 AUTHORITY (Data Acquisition Document No.) 5 CONTRACT REFERENCE 6 REQUIRING OFFICE DI-SESS-81314A/T Performance Work Statement, Para 3.4.4.1 SMC/LRG

7 DD 250 REQ 9 DIST STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

LT BLK 16 BLK 16 b COPIES

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

A N/A BLK 16 Draft Reg Repro

16 REMARKS See Distribution List

1. (BLK 4):

a. 2. Format, Replace first two sentences with “The interface specification shall be prepared in an electronic format and printable on 8 ½ x 11” paper (metric size A4). It may be a multi-part electronic document.”

b. Replace 2.1.1 with “2.1.1 Document number. The document number shall appear on the title page.”

c. Replace 2.1.2 with “2.1.2 Date. The document issue data (Baseline/Revision Number and Issue Date) shall appear on the title page.”

d. Replace 2.1.3 with “2.1.3 Title. The document title shall appear on the title page stating the nomenclature of the interfacing items.”

e. Delete 2.1.4.

f. Delete 2.2.1.

g. Replace 2.4 with:

“Section 3.0, Requirements. This section provides the detailed description of the interface requirements. Each interface shall be separately covered in its own subsection, and include:

a. Space Vehicle Configuration (For USAF Missions)

b. Mission Parameters

c. Launch Vehicle Configuration

d. Space Vehicle/Launch Vehicle Interface Requirements

e. Space Vehicle Handing and Processing Requirements

Include mission-specific payload systems weight capability for the mission and PLF selected and specific mission design constraints.”

h. Replace 2.5 with:

“Section 4.0, Quality assurance. This section shall identify and define the following:

a. Philosophy of Verification

b. Verification Methods

c. Verification Matrix”

Electronically Generated PAGE 1 OF 2 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A TDP X TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

16 REMARKS

i. Replace 2.6 with: “Section 5.0, Notes. This section shall include Definitions, Abbreviations, Acronyms and Symbols.”

j. Delete Figure 1 Replace 3. With “Appendix A – This appendix shall include the Electrical Interfaces. Appendix B – This appendix shall include the Mechanical Interfaces. Appendix C – This appendix shall include the Requirements Traceability.”

k. Delete 3.1 – 3.3

2. (BLK 8): Signatures by 4-Party Technical Team

a. For USAF Missions: LV Contractor, LV Government Program Office, SV Contractor/LSIC, and SV Customer Program Office, at a minimum, constitutes Government approval of the Mission ICD.

b. For NRO Missions: LV Contractor, OSL MM, OSL COTR and LSIC constitutes Government approval of the Mission ICD

3. (BLKs 10, 12, and 13):

a. Submit first draft of the Baseline Mission ICD NLT Launch – 21 months. No Government approval required.

b. Submit second draft NLT Launch – 12 months for Government approval.

c. Submit Final 30 CD after 4-Party technical Team signature to be formalized by bi-lateral contract modification.

d. Submit revision as necessary taking into account the number of approved changes to be formalized by bi-lateral contract modification.

Electronically Generated PAGE 2 OF 2 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

9002 A TDP X TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

EELV FA8811-15-R-0001

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

B010 Design Data and Calculations Mission Assurance Independent Assessment Data

4 AUTHORITY (Data Acquisition Document No.) 5 CONTRACT REFERENCE 6 REQUIRING OFFICE

DI-GDRQ-80650/T Performance Work Statement, Para 3.4.5 SMC/LRG

7 DD 250 REQ 9 DIST STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

LT BLK 16 BLK 16 b COPIES

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Replace 10.1 with the following: “10.1 Format. The Mission Assurance Independent Assessment Data shall be in contractor’s format unless specified otherwise in 10.2. Electronic access on a Government accessible database satisfies the requirements of delivery as long as all parts of the document are accessible.”

b. Replace 10.2 with Attachment 1.

c. Delete 10.3.

2. (BLK 7) The contractor shall document (electronic Interoffice Memorandum acceptable) and notify the Requiring Office when delivery occurs. Copies of this notification shall be maintained on the Government accessible database.

3. (BLKs 10, 12 and 13)

a. Data explicitly identified with a specific LNLT-/+ date are required for each mission

b. Contractor shall provide and maintain a roadmap/burndown schedule NLT 60 DACA of all deliverables to meet the required deadlines

c. Contractor shall identify any anticipated risk of not being able to provide certain data by the required deadline along with the mitigation steps NLT 60 DACA

d. Contractor shall start coordinating with USG Team on all deliverables NLT 60 days prior to each deadline at the appropriate working group meetings

e. For other data:

i. Initial submission is or has been satisfied by launch system certification

ii. Subsequent submission is required to reflect the latest USG certified/approved launch system configuration and upon implementation of any changes in these data/products

Electronically Generated PAGE 1 OF 1 PAGE

ATTACHMENT 1 to CDRL B010 – Mission Assurance Independent Assessment Data

10.2 Format. Data requested in this CDRL shall be provided in a detailed report format, or accompanied by a detailed report. The term “report” shall be defined as a detailed narrative document in Microsoft Word or equivalent format. The report shall discuss methodology (including equations and numerical methods used, as appropriate), input data, tools/simulations, truth sources, assumptions, results, limitations, publication date, references to related analyses/reports, launch vehicle configuration as applicable, and point of contact; and list all of the technical disciplines and how they have contributed to the detailed report. Also to be included is a discussion of any discrepancies or issues associated with meeting mission requirements and how they were resolved, where applicable. The report shall also include clear instructions (i.e., file path or links) to get access to applicable data that are stored on electronic systems. Data must be approved/released engineering products.

The report shall contain reviewer signatures from the contractor’s Integrated Team of Approvers to include leads or technical authority from avionics, propulsion, structures, GN&C, dynamics/loads, thermal, flight software, etc. USG reserves the right to request copies of referenced materials. A hyperlink to the electronic data is not acceptable without an accompanied report. If the data requested is available in an existing analysis report, then it shall be accompanied with a narrative summary document to identify the specific page containing the items requested in the detailed report.

10.2 Content. The content of this CDRL is data required to support the Government’s Independent Mission Assurance process.

I. Flight Mechanics, Guidance and Navigation

A. Flight Mechanics - Mission Design

1. Published trajectory outputs for:

a. Preliminary Unguided 3DOF [NLT L-12 months]

b. Intermediate Unguided 3DOF [NLT L-6 months]

c. Final Unguided 3DOF [NLT L-75 CD if target spec delivered at NLT L-120 CD, otherwise NLT L-60 CD]

d. For items a. – c., outputs will include:

i. All associated memos

ii. An output file from the contractor’s trajectory simulation code

iii. A file of high frequency trajectory variables (to be specified by government) output at a minimum of every second during stage main engine propulsive flight and at a minimum of every 4 seconds during coast phases

iv. Optimization output that includes a listing of final variable, constraint and objective function values

2. Trajectory inputs and ground rules for:

a. Preliminary Unguided 3DOF [NLT L-12 months]

b. Intermediate Unguided 3DOF [NLT L-6 months]

c. Final Unguided 3DOF [NLT L-75 CD if target spec delivered at NLT L-120 CD, otherwise NLT L-60 CD]

d. For items a. – c., inputs will include:

i. All associated memos with references to data sources

ii. Event sequence/phase criteria and inputs

iii. A listing of optimization variables, with bounds, constraints and objective function

iv. Propellant reserve/performance formulations

v. Mission-specific inputs/assumptions for: mass properties (mass, CG, MOI, and POI), steering, atmosphere, telemetry tracking, aerodynamics, propulsion, attitude control, planet data, etc.

vi. Mission-specific launch vehicle configuration summary that describes all differences between the baseline launch vehicle configuration and the mission-specific vehicle configuration

vii. Summary descriptions of trajectory input and ground rule changes since the prior submittal

3. Simulation data book [As necessary to reflect all modeling changes, up to Quarterly]

a. This document will describe the generic vehicle, its properties, and how these are included in the trajectory simulation with ground rules and modeling assumptions.

b. This data will provide modeling information for, but not be limited to, the following areas: stage properties, propulsion characteristics, aerodynamics, winds, vehicle heating models, steering assumptions, post spacecraft injection maneuvers, general vehicle trajectory constraints, atmospheric and geographical assumptions, etc.

4. Mass properties, aerodynamics, and propulsion updates

a. Notification and description of updates to these areas will be delivered as soon as published by the affected discipline and will include an effectivity.

b. Delivery may coincide with items in [I.A.2], as appropriate.

5. CCAM/Disposal

a. Description of post spacecraft injection sequence and evidence/memo of precluding spacecraft contact [NLT L-6 months]

b. Trajectory data will be included with delivery of trajectories identified in [I.A.1] and [I.B.1] : Inputs and modeling (as described in I.A.2-I.A.4) for CCAM, disposal (including disposal burns) and propellant safing [NLT L-12 months, NLT L-6 months, NLT L-60 CD, respectively]

6. Launch window analysis/memo [NLT L-30 CD]

7. Re-entry data package, if applicable [NLT L-60 CD]; Data package to include impact points, impact ellipse boundaries, and casualty expectation

B. Flight Mechanics – Performance and Guidance and Navigation

1. Published trajectory outputs for the closed-loop guided trajectory

a. Preliminary Guided 6DOF [NLT L-90 CD]

b. Intermediate Guided 6DOF [NLT L-75 CD if Target spec delivered at NLT L-120 CD, otherwise NLT L-60 CD]

c. Final Pre-Launch Guided 6DOF [NLT L-30 CD]

d. Updated Final Prelaunch Trajectory 6DOF [NLT L-10 CD]

e. For items a. – c., outputs will include:

i. All associated memos

ii. Window open, middle, and close trajectory data for time-varying trajectories

iii. An output file from the contractor’s trajectory simulation code

iv. A file of trajectory variables output at a minimum of every second

2. Trajectory inputs and ground rules

a. Preliminary Guided 6DOF [NLT L-90 CD]

b. Intermediate Guided 6DOF [NLT L-75 CD if target spec delivered at NLT L-120 CD, otherwise NLT L-60 CD]

c. Final Pre-Launch Guided 6DOF [NLT L-30 CD]

d. Updated Final Prelaunch Trajectory [NLT L-10 CD]

e. For items a. – c., inputs will include:

i. All associated memos with references to data sources

ii. Event sequence/phase criteria and inputs

iii. Propellant reserve/performance formulations

iv. Mission-specific inputs/assumptions for mass properties (mass, CG, MOI, and POI), steering, atmosphere, telemetry tracking, aerodynamics, winds, propulsion, attitude control, planet data, etc.

3. Simulation Book [As necessary to reflect all modeling changes, up to Quarterly]

a. This document will describe the generic vehicle, its properties, and how these are included in the trajectory simulation with ground rules and modeling assumptions.

b. This data will provide modeling information for, but not be limited to, the following areas: stage properties, propulsion characteristics, aerodynamics, vehicle heating models, steering assumptions, post spacecraft injection maneuvers, general vehicle trajectory constraints, atmospheric and geographical assumptions, etc.

4. Mass properties, aerodynamics, and propulsion updates

a. Notification and description of updates to these areas will be delivered as soon as published by the affected discipline and will include an effectivity.

b. Delivery may coincide with items in [I.B.2] as appropriate.

5. Propellant Utilization (PU)

a. System(s) descriptive documentation (if applicable) [updates in quarterly Simulation Book]: Venting and Pressurization models and…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated Nov 14, 2017.