Exhibit_A_-_CDRLs_1423_13_Mar.pdf

PDF 133 KB Posted Apr 8, 2015

Attached to: ORS-5 (Operationally Responsive Space) SensorSat 5 Launch Services Federal contract opportunity
Solicitation number: FA8818-15-R-0003
Issued by: Department of the Air Force Space Command Space and Missile Systems Center

View the file

Other files for this federal contract opportunity

Other files attached to ORS-5 (Operationally Responsive Space) SensorSat 5 Launch Services, newest first.
File	Type	Posted
A6_DD254_V1.pdf	PDF	Apr 24, 2015
A2_-_ORS-5_TRD_V1.pdf	PDF	Apr 24, 2015
ORS-5_QA_2.pdf	PDF	Apr 24, 2015
A1_-_ORS-5_LV_PWS_11_Mar.pdf	PDF	Apr 15, 2015
ORS_Q A_1.pdf	PDF	Apr 15, 2015
A7_-_Sec_L__ITO_11_Mar.pdf	PDF	Apr 8, 2015
FA8818-15-R-0003_RFP.pdf	PDF	Apr 8, 2015
A4_-_Price_Adjustment_for_GFP_and_Services_3_Mar.pdf	PDF	Apr 8, 2015
A6_-_DD254_draft.pdf	PDF	Apr 8, 2015
A3_-_ORS-5_Payment_Plan_v10.pdf	PDF	Apr 8, 2015
A1_-_ORS-5_LV_PWS_11_Mar.pdf	PDF	Apr 8, 2015
A5_-_Small_Business_Sub-Contracting_Plan_4_Mar.pdf	PDF	Apr 8, 2015
A2_-_ORS-5_TRD_17_Mar.pdf	PDF	Apr 8, 2015
A8_-_Sec_M_Eval_Criteria_11_Mar.pdf	PDF	Apr 8, 2015

Show all 14

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 A

FA8818-15-R-0003

Operationally Responsive Space – 5 (ORS-5)

CONTRACT DOCUMENTATION REQUIREMENTS LIST (CDRLS)

13 March 15

CDRL List

Number DID Title

- A001 N/A Meeting/Review Documentation

- A002 N/A Countdown Documentation

- A003 N/A SV to Launch Service Interface Control Document (ICD)

- A004 N/A ICD Requirements Verification Report (RVR)

- A005 N/A Final Flight Report

- A006 N/A SV – Launch Service Integration Procedures

- A007 N/A Integrated Master Schedule

-A008 N/A Contractor System Safety Program Plan, Risk Management Plan and Range Documents

17. PRICE GROUP

DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 1 of 10

18. ESTIMATED

TOTAL PRICE

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

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 Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP X TM OTHER

D. SYSTEM/ITEM

ORS-5

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

Technical Report - Meeting / Review Documentation

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508A

5. CONTRACT REFERENCE

PWS

6. REQUIRING OFFICE

7. DD 250 REQ 9.DIST STATEMENT

REQUIRED

10. FREQUENCY

ASREQ

12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE

N/A

13. DATE OF SUBSEQUENT

SUBMISSION

Draft

Final

Reg

Repro

16. REMARKS:

Applies to:

Presentation and handout material, minutes, and accompanying action item lists from each formal review.

Blk 4: The DID is tailored as follows:

1) Delete 1 (a) through 1 (d) and replace with: “Contractor format is acceptable for all documents in this CDRL.”

2) The following shall be added to the DID under 2. Content:

(A) Presentation packages and hand-out materials provided at the review for attendees

(i) Reviews as documented in Attachment 1, PWS

(B) Minutes from each formal review

An action item list maintained and updated by the Contractor.

Block 12: The DIID is tailored as follows:

Draft presentation packages are due 15 calendar days prior to the review; final packagaes are due at the review; minutes, attendees list and action items are due 10 caledar days after the review.

Block 14:

The draft and preliminaries shall be submitted in Microsoft Office. The finals shall be submitted in Adobe Acrobat.

SMC/ORS 1 1 1

15. TOTAL

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 2 of 10

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP X TM OTHER

D. SYSTEM/ITEM

ORS-5

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A002

2. TITLE OF DATA ITEM

Technical Report - Countdown Documentation

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508A

5. CONTRACT REFERENCE

PWS

6. REQUIRING OFFICE

12. DATE OF FIRST SUBMISSION

L-1 WEEK

14. DISTRIBUTION

AS CHANGED

The documents necessary to launch the vehicle and assist ORS-5 management during the countdown process. Contractor developed documentation, as required and approved by the launch Range, is sufficient to meet this CDRL if Data Requirements as defined in A

– B below are included.

1) Delete 1 (a) through 1 (d) and replace with: “Contractor format is acceptable for all documents in this CDRL.”

Appendices for the documents listed below shall be provided when necessary to present supplemental or incidental information, detailed tabulations or deviations, or graphic representations.

(A) Countdown The Countdown document shall provide:

(i) All necessary steps and built-in holds required to successfully launch the vehicle and the ORS-5 SV during the launch window

(ii) Procedures required to safe the launch vehicle after a launch attempt

(iii) Procedures required to recycle the countdown for another launch attempt

The necessary steps shall be listed as a sequence of events with each entry including a T-time. T-time is defined as the time before launch, not including planned holds, and with T-0 being the time of launch vehicle lift-off from the launch pad.

DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 3 of 10

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP X TM OTHER

D. SYSTEM/ITEM

ORS-5

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A002

2. TITLE OF DATA ITEM

Technical Report - Countdown Documentation

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508A

5. CONTRACT REFERENCE

PWS 2.0

6. REQUIRING OFFICE

L-1 WEEK

T+ time is any event after T-0. Each member of the launch team shall be identified by call sign and communication channel. All mission constraints to launch shall also be identified.

(B) Mission Constraints Document This document is a summary of all the launch vehicle, space vehicle and range mission constraints to launch.

Block 14:

The draft and preliminaries shall be submitted in Microsoft Office.

The finals shall be submitted in Adobe Acrobat.

DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 4 of 10

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP X TM OTHER

D. SYSTEM/ITEM

ORS-5

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A003

2. TITLE OF DATA ITEM

SV to Launch Service Interface Control Document (ICD)

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-CMAN-81248

5. CONTRACT REFERENCE

PWS 2.0, 5.1, TRD 2.2.3

6. REQUIRING OFFICE

@PDR

The ICD identifies and defines the functional, structural/physical, electrical, thermal and environmental interfaces, and performance requirements of the payload, and payload GSE with the launch service and associated payload/launch processing facilities, 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.

1) No changes to DID

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; 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:

DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 5 of 10

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP X TM OTHER

D. SYSTEM/ITEM

ORS-5

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A003

2. TITLE OF DATA ITEM

SV to Launch Service Interface Control Document (ICD)

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-CMAN-81248

5. CONTRACT REFERENCE

PWS 2.0, 5.1, TRD 2.2.3

6. REQUIRING OFFICE

@PDR

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/Thermal Interfaces

3.2 Electrical Interfaces

3.3 Environmental Interfaces

3.4 Flight Design

3.5 Ground Operations

3.6 Safety Requirements

Block 13: Baseline ICD at CDR, updates as required after baseline Block 14:

DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 6 of 10

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP X TM OTHER

D. SYSTEM/ITEM

ORS-5

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A004

2. TITLE OF DATA ITEM

Technical Report – ICD Requirements Verification Report (RVR)

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508A

5. CONTRACT REFERENCE

PWS

6. REQUIRING OFFICE

ICD + 3 MTHS

Applies to:

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.

acceptable for all documents in this CDRL.”

2) The following shall be added to the DID under 2. Content:

The verification matrix shall be released no later than three (3) months after the Preliminary ICD CDRL approval and shall be updated upon release of each ICD revision. The final RVM shall be submitted at the DCR, and shall include all verification artifacts.

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 • Verification Plan

• ICD requirement paragraph number • Verification Source

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

• Responsible Organization • Notes/Comments

• Status Block 14:

DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 7 of 10

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP X TM OTHER

D. SYSTEM/ITEM

ORS-5

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A005

2. TITLE OF DATA ITEM

Technical Report – Final Flight Report

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508A

5. CONTRACT REFERENCE

PWS 2.0

6. REQUIRING OFFICE

L+60 DAYS

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

acceptable for all documents in this CDRL.”

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

This report shall also include:

(i) A summary of the pre-launch operations and countdown events

(ii) A summary of the recorded flight events

(iii) Orbit elements determined from launch vehicle guidance data

(iv) LV data indicating payload separation

(v) Pre-flight prediction of expected flight environments (i.e., acoustic/vibration, quasi-static acceleration, thermal, and pressure).

Generic vehicle environmental data may be submitted unless specific environmental requirements are identified in the ICD

(vi) Post flight determination of actual flight environments (if available)

(vii) Explanation of significant differences between the predicted and actual flight environments (if available)

(viii) Vehicle sequence and attitudes data (if available)

DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 8 of 10

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP X TM OTHER

D. SYSTEM/ITEM

ORS-5

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A005

2. TITLE OF DATA ITEM

Technical Report – Final Flight Report

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508A

5. CONTRACT REFERENCE

PWS

6. REQUIRING OFFICE

L+30 DAYS

Block 14:

The finals shall be submitted in Adobe Acrobat.

SMC/ORS

DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 9 of 10

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP X TM OTHER

D. SYSTEM/ITEM

ORS-5

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A006

2. TITLE OF DATA ITEM

SV - Launch Service Integration Procedures

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508A

5. CONTRACT REFERENCE

PWS 2.0

6. REQUIRING OFFICE

SV–LS INT -60D

Applies to:

Site procedures for various operations that involve the launch service / space vehicle interfaces.

Blk 4: The DID is tailored as follows:

1) Delete 1 (a) through 1 (d) and replace with: “Contractor format is acceptable for all documents in this CDRL.”

2) The following shall be added to the DID under 2. Content.:

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

(A) space vehicle/ launch service electrical interface verification test

(B) space vehicle integration

(D) Launch service electrical readiness/flight simulation

(E) Fairing installation

(F) Combined system test/final readiness test

Also provide a list of all Contractor-specific procedures used for integrated processing with a brief description of their purpose.

Block 14:

DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 10 of 10

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER X

D. SYSTEM/ITEM

ORS-5

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A007

2. TITLE OF DATA ITEM

Integrated Master Schedule (IMS)

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81650

5. CONTRACT REFERENCE

PWS, 2.0.e, 2.1.b

6. REQUIRING OFFICE

SMC/ORS

MONTHLY

ATP + 30D

MTH END

15TH OF EA. MTH

ORS-5 Launch Service Integrated

Master Schedule.

Blk 4: The DID is tailored as follows:

1. Level of effort tasks are not required in the IMS

2. Hard constraints, if used must be supported with an explanation in the Notes field. Deadlines are recommended to be used in lieu of hard constraints.

3. Baseline changes must be explained in the monthly status report.

4. A calendar with holidays and plant closures shall be used to ensure non-work days are not planned in the baseline. Execution may require customization to accommodate critical work-arounds if the delivery date is in jeopardy.

Block 14:

The IMS shall be submitted in Microsoft Project 2007 or 2010, Primavera P6, Open Plan or other professional project scheduling tool but must be able to provide XML file if not MS Project.

DD Form 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 10 of 10

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER X

D. SYSTEM/ITEM

ORS-5

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A008

2. TITLE OF DATA ITEM

Technical Report – System Safety Program Plan, Risk Management Plan and range documentation

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508A

5. CONTRACT REFERENCE

PWS

6. REQUIRING OFFICE

SMC/ORS

Launch Service Contractor command media

Blk 4: The DID is tailored as follows: Contractor format is acceptable

Block 12: System Safety Program Plan and Risk Management Plan are due at ATP + 30 days

Range Documentation, including the Launch Service UDS documents and Launch Service Safety submittals, are due concurrent with final Range Submittal.

Block 14:

Contractor format is acceptable

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