PF2_-_DRFP_-Exhibit_A_CDRLs_(ao_17_Jan_17).pdf

EXHIBIT A

FOR

CONTRACT NO. XXXXXX-XX-XXXX

CONTRACT DATA REQUIREMENTS LIST (CDRL)

FOR

COMSATCOM PATHFINDER #2

DD MONTH YYYY

Contract No: XXXXXX-XX-XXXX Contractor: Name Exhibit: A System Item: COMSATCOM Pathfinder #2 Date: DD MMM YYYY

REVISION HISTORY

ARROVAL

DATE

DESCRIPTION OF CHANGE MODIFICATION

(P000) NO.

DD MMM YYYY Initial Release

1.0 SCOPE

1.1 These instructions establish the requirements for data to be delivered by the Contractor for submittal, inspection, approval, acceptance and distribution requirements of all the Contract Document Requirements List (CDRL (DD Form 1423)) items contained within Exhibit A for COMSATCOM Pathfinder #2 on Contract XXXXXX-XX-XXXX.

2.0 GENERAL

2.1 Data Item Descriptions (DIDs) referenced in Block 4 of the DD Form 1423 line are available in the Acquisition Streamlining and Standardization Information System (ASSIST) (http://quicksearch.dla.mil). Only unique DIDs or attachments shall be included in the exhibit when applicable.

2.2 This document consolidates all contract data items and requirements associated with deliverable data.

2.3 The Contractor shall immediately notify the Procurement Contracting Officer (PCO) of any request for electronic delivery/distribution changes that the Contractor feels increases the contract price, and shall not comply with the request until directed by the PCO.

3.0 DISTRIBUTION STATEMENTS

3.1 The designation of the letter “D” in Block 9 of the DD Form 1423 indicates that distribution statement “D” shall be annotated on each data item in accordance with Department of Defense Directive (DoDD) 5230.24, Distribution Statements on Technical Documents.

3.1.1 Unclassified documents must be marked with the following statements:

UNCLASSIFIED DISTRIBUTION STATEMENT D: Distribution authorized to DoD and US DoD Contractors only, due to the sensitive information (as defined in DoD 5230.25) associated with the COMSATCOM Pathfinder #2 effort. Other requests for this document shall be referred to SMC/PKJ through SMC/MCX.

UNCLASSIFIED DESTRUCTION NOTICE: For this document, destroy by any method that will prevent disclosure of contents or reconstruction of material.

3.1.2 If the program has a Program Security Classification Guide, unclassified data items must be marked with the following statement:

UNCLASSIFIED DISTRIBUTION STATEMENT D: Distribution authorized to DoD and US DoD Contractors only, due to the sensitive information (as defined in DoD 5230.25) associated with COMSATCOM Pathfinder #2, and as determined in the COMSATCOM Pathfinder #2 Security Classification Guide. Other requests for this document shall be referred to SMC/PKJ through SMC/MCX.

UNCLASSIFIED DESTRUCTION NOTICE: For this document, destroy by any method that will prevent disclosure of contents or reconstruction of material.

3.1.3 Classified data items must be marked with the following statements:

http://quicksearch.dla.mil/

CLASSIFIED DISTRIBUTION STATEMENT D: Distribution authorized to DoD and US DoD Contractors only, due to the sensitive information (as defined in DoD 5200.1-R) associated with the COMSATCOM Pathfinder #2 effort. Other requests for this document shall be referred to SMC/PKJ through SMC/MCX.

CLASSIFIED DESTRUCTION NOTICE: Classified material must be destroyed using procedures in Chapter 5, Section 7 and Chapter 6, Section 7 of DoD 5300.1- R, Information Security Program (ISP) and/or DoD 5220.22-M, National Industrial Security program Operating Manual (NIPSOM).

3.1.4 If the program has a Program Security Classification Guide, classified data items must be marked with the following statement:

CLASSIFIED DISTRIBUTION STATEMENT D: Distribution authorized to DoD and US DoD Contractors only, due to the sensitive information (as defined in DoD 5200.1-R) associated with COMSATCOM Pathfinder #2, and as determined in the COMSATCOM PATHFINDER #2 Security Classification Guide. Other requests for this document shall be referred to SMC/PKJ through SMC/MCX.

CLASSIFIED DESTRUCTION NOTICE: Classified material must be destroyed using procedures in Chapter 6, Section 7 of DoD 5300.1-R, Information Security Program (ISP), and/or Chapter 5, Section 7 of DoD 5220.22-M, National Industrial Security Program Operating Manual (NIPSOM).

3.1.5 All data items must be marked with the following export control notice:

WARNING - INFORMATION SUBJECT TO EXPORT CONTROL LAWS: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. 2751 et seq.) or Executive Order 12470. Violators of these export laws are subject to severe criminal penalties. Dissemination of this document is controlled under DoD Directive 5230.24.

4.0 LETTER OF TRANSMITTAL (LT)

4.1 Each data submittal shall be accompanied by a separate Letter of Transmittal. The Letter of Transmittal shall be signed and contain the following information:

Assigned Contractor program unique Letter of Transmittal number.

Contract number.

Contract Line Item Number (CLIN) (if applicable).

CDRL number and sequence number (Example A001-001). Sequence number should consist of three digits following the CDRL number with a hyphen separating the two sets of numbers. Resubmittals should be assigned a new sequence number.

Exact title and subtitle (if applicable) of the document being transmitted.

Document date.

Contractor’s document number (if applicable).

Revision information (if applicable).

State whether the document is a draft or final submittal (if applicable).

State whether the document is “For Approval" or “Non- Approval” (see Block 8 and Block 16 of the DD Form1423).

If document is a re-submittal, reference any correspondence requesting the re-submittal (i.e., Contractual Documentation Action (CDA)).

For periodic reports, specify the report period delivered.

Information disclosing the total contractual distribution being made per Block 14 or 16 of the DD Form 1423.

5.0 TOPVUE CONTRACT PORTAL SYSTEM

5.1 Data items shall be in electronic format and shall be submitted to the Government via the TopVue Contract Portal System tool. TopVue is Commercial Off-the-Shelf (COTS) software licensed for use by the United States Air Force (USAF) Space and Missile Systems Center / MILSATCOM Systems Directorate (SMC/MC). TopVue implements user authentication through the use of encrypted Public Key Infrastructure (PKI) certificates to validate all user account access to the software and protects against unauthorized access via intrusion detection. Access to the TopVue Contractor Portal utilizes Secure Socket Layer (SSL) protocol.

5.2 Data items submitted via TopVue are protected through strict account management policies that limit authorization (data access) only to those given explicit permission to view such data.

5.3 Within 30 calendar days (CD) after contract award, the contract shall be required to support electronic delivery via TopVue. External addressees shall have access to unclassified deliverable data via a Contractor generated web page.

5.4 Data stored on the TopVue server is backed up daily and weekly. TopVue has built in redundancy for access in the event of a server failure.

6.0 TOPVUE CONTRACTOR PUBLIC KEY INFRASTRUCTURE (PKI) PROCEDURE

6.1 Air Force Space Command (AFSPC) requires all web applications, including TopVue, to present a valid DoD PKI certificate before allowing access to the system. DoD Contractors working off site will need to acquire PKI certificates from one of the DoD approved External Certification Authorities (ECA) in order to access the TopVue system. ECA information can be found at: http://iase.disa.mil/pki/eca/Pages/index.aspx.

6.2 Once PKI certificates have been acquired, TopVue users should follow the steps below to register their certificate with the TopVue system. To enable PKI certificate:

Step 1. Go to URL https://cloud1.topvue.com/topvue-mc/.

Step 2. Enter your user identification (ID) and password.

Step 3. Click on your username at the top of the screen.

Step 4. At the bottom of the screen, there should be a field called "Client Certificate."

If your certificate is valid, you should see a "Request" button.

http://iase.disa.mil/pki/eca/Pages/index.aspx https://cloud1.topvue.com/topvue-mc/

Step 5. Click on the "Request" button to request that your certificate is registered with the system.

Step 6. The TopVue administrator will validate your certificate and you will be able to use your certificate on subsequent visits.

7.0 DATA ITEM DELIVERY DUE DATES/TIME

7.1 Both unclassified and classified data items, regardless of the delivery method, shall be received no later than 1600 hours (4:00 PM) Pacific Time on the specified scheduled due date (see Blocks 12, 13 or 16 of the DD Form 1423). If the due date falls on a weekend or Government holiday, then the delivery date becomes the first Government business day (BD) following the weekend and/or holiday.

7.2 Mailed data items (both unclassified and classified) are considered late/delinquent if it does not arrive at its destination by the specified due date/time. If the data delivery is post marked three (3) CD before the due date, and it is not received by the Los Angeles Air Force Base (LA AFB) mail room on said date due to U.S. Postal Service handling, the CDRL delivery requirements are still met. United States Postal Service “Express Mail” or overnight courier/delivery service is not encouraged.

8.0 UNCLASSIFIED DATA ITEM SUBMITTAL PROCEDURE

8.1 Unclassified data items are submitted to the Government via the TopVue tool and in accordance with this instruction. The unclassified data item submittal procedure for TopVue is as follows:

Step 1. Login to TopVue by entering the URL https://cloud1.topvue.com/topvue-mc/.

Step 2. Click the “Contractor Submittal” link in the file cabinet on the left side of the screen.

Step 3. Select the desired “Program” and “Contract” from the resulting drop down lists.

The “Program” and “Contract” drop down will be displayed based on the permissions granted to each account.

Step 4. Select the “CDRL Number” from the filtered list for which the delivery will be submitted against.

Step 5. Click on the “Insert” button. The “Contractor Submittal Insert Page” is displayed.

Step 6. For scheduled data item submittals, select the correct due date from the “CDRL Due Date Field.” If the delivery is “As Required” or “As Generated,” select the “ASGEN/ASREQ” checkbox. Note that not specifying a CDRL due date or checking the “ASGEN/ASREQ” checkbox may result in the scheduled delivery being identified as late to the government. If the “ASGEN/ASREQ” checkbox is not available, the Contractor must contact the Government Data Manager to request a due date be added.

Step 7. Populate the delivery information portion of the submittal insert.

file:///C:/Users/cindy.vass/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/SL0YCUR7/URL%20https:/cloud1.topvue.com/topvue-mc/

Step 8. Once the delivery information has been populated, scroll down the page to the document information section and populate the document information portion of the submittal insert.

Step 9. To attach a file, click the “Browse” button under “Document Attachment(s)” and locate the file on the local machine. For additional files, click the “Add More” icon directly under the “Browse” file name box. A large number of files may be zipped on the local machine and unzipped by the system on the submittal insert if the “Unzip Attachments” field is selected to “Yes” in the delivery information.

Step 10. To insert the CDRL submittal, click “Submit” at the top of the screen.

8.2 The Contractor shall provide notification of delivery to the Government Data Manager via email at the time of the data item delivery.

8.3 Any unclassified delivery exceeding 100 MB (in part or total) must be placed on electronic media such as Compact Disc (CD) or Digital Video Disk (DVD) and delivered by hand or sent by mail in accordance with MIL-STD-1840C, Automated Interchange of Technical Information. Coordination must be made with the Government Data Manager prior to delivery.

8.4 Send/hand deliver large unclassified data items to:

Los Angeles Air Force Base Space and Missile Systems Center

SMC/MCES/COMSATCOM PATHFINDER #2

Attn: Name 483 N. Aviation Blvd.

El Segundo, CA 90245-2808

8.5 Email the notification of unclassified delivery to: TBD@us.af.mil

8.6 All unclassified data items, regardless of the delivery method, shall be received on the specified scheduled due date. Reference Section 7.0.

9.0 ALTERNATIVE UNCLASSIFIED DATA ITEM DELIVERY METHODS

9.1 In the event that TopVue is unavailable, a copy of the data item shall be emailed to the

Government Data Manager. Emails containing encrypted files and/or embedded macro may experience conflict with Government Outlook security protocol. Email deliveries shall not exceed 5 MB (in part or total).

9.1.1 Email unclassified deliveries to: TBD@us.af.mil

9.2 A copy of the data item can also be mailed or hand delivered on CD/DVD. Coordination must be made with the Government Data Manager prior to delivery.

9.3 Mail/hand deliver unclassified data items to:

mailto:TBD@us.af.mil

SMC/MCES/COMSATCOM PATHFINDER #2

Attn: Name

El Segundo, CA 90245-2808

9.4 Email the notification of unclassified delivery to: TBD@us.af.mil

10.0 CLASSIFIED DATA ITEM SUBMITTAL PROCEDURE

10.1 Classified data items shall never be posted to TopVue.

10.2 Classified data can be mailed, hand delivered, or electronically transferred via a US

Government authorized electronic transfer system (i.e., Secret Internet Protocol Router Network (SIPRNET)).

10.3 Classified data shall be provided on a CD/DVD using a Mutually Agreeable Commercial

Software (MACS) format, except when being electronically transferred.

10.4 Both mailed/hand deliveries must be coordinated with SMC/MC Security (MCES) and the

Government Data Manager prior to delivery.

10.5 The Contractor shall provide notification of shipment to the Government Data Manager via unclassified email.

10.6 Each classified data item submittal shall be accompanied by a separate unclassified Letter of Transmittal that is to be submitted via TopVue.

10.7 Deliver SIPRNET deliveries to: TBD@mail.smil.mil

10.8 Mail classified electronic media to:

SMC/MCES/COMSATCOM PATHFINDER #2

Attn: Name

El Segundo, CA 90245

10.9 Hand deliver classified electronic media to:

SMC/MCES/COMSATCOM PATHFINDER #2

Attn: Name 2350 East El Segundo Blvd., Bldg. A8 El Segundo, CA 90245-4691

10.10 To coordinate a classified delivery by mail/hand, contact: SMC.MC.Security@us.af.mil

10.11 Email the notification of classified hand delivery to: TBD@us.af.mil mailto:TBD@us.af.mil mailto:SMC.MC.Security@us.af.mil

10.12 All classified data items, regardless of the delivery method, shall be received on the specified scheduled due date. Reference Section 7.0.

11.0 DATA ITEM APPROVAL INFORMATION

11.1 Data Items That Require Formal Government Approval

11.1.1 When an “A” is indicated in Block 8 of the DD Form 1423, formal Government approval is required.

11.1.2 Approval indicates agreement or concurrence with the Contractor’s furnished data only and shall not be construed as changing any of the terms or conditions of the subject contract.

11.1.3 Unless otherwise indicated in the specific CDRL, the Government approval cycle will not be more than 30 CD. The Contractor shall be notified should the Government require additional time.

11.1.4 A CDA form, a contract modification, or a PCO Letter can be used to document the

Government’s decision in regard to the disposition status of the Contractor submitted data item.

11.1.5 The CDA form shall be emailed to the Contractor by the Government Data Manager.

Approval status can only be established once the Government has disposition the data item.

11.1.6 PCO Letters and contract modifications are emailed to the Contractor by the PCO.

Approval status can only be established once the Government has disposition the data item.

11.1.7 Non-response by the Government to a Contractor’s request for approval of a data item is not to be construed as tacit approval of said item(s).

11.1.8 If the data item is “Approved,” no further action is necessary. The document identified with effective date of approval becomes part of the historical CDRL data.

11.1.9 If the data item is “Approved with Comments”, the Contractor shall revise the data item within 30 CD, or in accordance with specific comments provided by the Government PCO, and resubmit the document for approval unless otherwise specified.

11.1.10 If the data item is “Disapproved,” the Contractor shall revise the data item within 30 CD, or in accordance with specific comments provided by the Government/PCO, and resubmit the document for approval unless otherwise specified.

11.2 Data Items That Do Not Require Formal Government Approval

11.2.1 When “N/A” is indicated in Block 8 of the DD Form 1423, no formal Government/PCO approval is required.

11.2.2 Unless otherwise stated in the specific CDRL, the review cycle for the Government for all non-approval submittals shall be 30 CD.

11.2.3 The Government reserves the right to submit comments and/or “Reject” any data submittal.

11.3 Data Items with Various Approval Conditions

11.3.1 When “BLK 16” is indicated in Block 8 of the DD Form 1423, the Contractor is to refer to the approval method(s) outlined in Block 16 of the DD Form 1423.

12.0 MATERIAL INSPECTION AND RECEIVING REPORT (DD FORM 250)

12.1 All data items delivered with a Letter of Transmittal shall be collectively accounted for under the Material Inspection and Receiving Report (DD Form 250). The period of performance shall be 01 January through 30 June and 01 July through 31 December of each year. The DD Form 250 shall be prepared and submitted by the Contractor to the Government Data Manager 30 CD after each respective period of performance unless otherwise stated in the contract.

12.2 The DD Form 250 shall list all data items that have been “Approved,” “Approved/Accepted with

Comments,” or “Accepted” by the Government during the contractual period of performance. Data items that require Government approval shall not be listed until receipt of Government/PCO approval has been received by the Contractor. Data items that were submitted during the contractual period of performance but not “Approved”/”Accepted” until the following period of performance cycle shall be included in the report for the latter cycle.

12.3 A Contractor’s computerized printout may be used in lieu of a DD Form 250 continuation sheets.

The printout must be delivered in an editable format such as Microsoft Word or Microsoft Excel.

12.4 The DD Form 250/computerized printout shall contain the following information:

CDRL number and sequence number.

Document title.

Contractor’s document number (if applicable).

Contractor’s unique Letter of Transmittal number.

Date of submittal/delivery.

State whether the document was “For Approval" or “Non-Approval” (see Block 8 and Block 16.

Government’s disposition for each data item (i.e., “Approved,” “Approved/Accepted with Comments,” or “Accepted”).

12.5 The DD Form 250/computerized printout shall not include:

Data items that have been “Withdrawn.”

Data items that have been “Rejected.”

Data items that have been “Disapproved.”

Data items that are still pending Government disposition.

13.0 SUPPLEMENTAL REQUIREMENTS

13.1 Due dates for delivery of data items are to be construed as receipt at destination.

13.2 The Contractor may not construe acceptance of a data item by the Government as relief from contractual requirements should the data item not meet those requirements. The Government does not assume responsibility for errors contained in Contractor submitted data items.

13.3 Unless directed otherwise, the Contractor’s format is acceptable provided it is useable by the Government. The intent of the DID Instruction(s) shall be met when Contractor’s format is used.

13.4 Changes to data items may be a complete reissue of the data item in its entirety. Change pages shall have the revised information identified and shall be accompanied by a remove and replace listing of the affected pages. Updates to data items shall be a complete reissue of the data item in its entirety.

13.5 The Contractor may at any time submit a request to the Government PCO for data closeout when no further submittal of a specific data requirement is beneficial to the program.

14.0 DEFINITIONS

14.1 The following codes are used when preparing the CDRL DD Form 1423:

CODE DEFINITION

A Approval

AFSPC Air Force Space Command

ANNLY Annually

ASGEN As Generated

ASREQ As Required

ATP Authority to Proceed

BD Business Days

BI-MO Each 2 months

BLK Block

CD Calendar Days

CDA Contractual Document Action

CDRL Contract Data Requirements List

CED Contract Effective Date

CLIN Contract Line Item Number

DAC Days After Contract start

DACM Days After Contract Modification

EOC End of Contract

EOM End of Month

EOQ End of Quarter

EOW End of Week

LT Letter of Transmittal

MTHLY Monthly

N/A Non-Approval

NET No Earlier Than

CODE DEFINITION

NLT No Later Than

ONE/P One Time Preliminary Draft

ONE/R One Time and Revision

OTIME One Time

PCO Procurement Contracting Officer

QTRLY Quarterly

R/ASR Revisions as required

SEMIA Every 6 months

SMC Space and Missile Systems Center

SOW Statement of Work

/T Denotes tailoring to DID (see Block 16)

WD Working Days

XTIME Multiple Separate Submittals (i.e., 2Time, 3Time)

Contract No.: XXXXXX-XX-XXXX Contractor: Name

15.0 CDRL INDEX/DISTRIBUTION LIST

CDRL

NO.

DID NO. CDRL TITLE CDRL SUBTITLE APPROVAL OFFICE

DRAFT FINAL

(E) Electronic copy (LT) Letter of Transmittal

(LTO) Letter of Transmittal Only

A001 DI-MISC-80508B/T Technical Report-Study/Services Satellite Performance N/A

(E) SMC/MCX

(E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures LT w/enclosures LT w/enclosures

LT w/enclosures LT w/enclosures LT w/enclosures

A002 DI-MISC-80508B/T Technical Report-Study/Services Cyber Compliance Matrix N/A

(E) SMC/MCX

(E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures LT w/enclosures LT w/enclosures

LT w/enclosures LT w/enclosures LT w/enclosures

A003 DI-MISC-80508B/T Technical Report-Study/Services CNSSP-12 Compliance BLK 16

(E) SMC/MCX

(E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures LT w/enclosures LT w/enclosures

LT w/enclosures LT w/enclosures LT w/enclosures

A004 Reserved

A005 DI-MISC-80508B/T Technical Report-Study/Services Pathfinder EMI/RFI Summary of Action Report

N/A

(E) SMC/MCX

(E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures LT w/enclosures LT w/enclosures

LT w/enclosures LT w/enclosures LT w/enclosures

A006 DI-MISC-80508B/T Technical Report-Study/Services Satellite Operator Transmission Plan N/A

(E) SMC/MCX

(E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures LT w/enclosures LT w/enclosures

LT w/enclosures LT w/enclosures LT w/enclosures

A007 DI-MISC-80508B/T Technical Report-Study/Services Overdrive Protection Data BLK 16

(E) SMC/MCX

(E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures LT w/enclosures LT w/enclosures

LT w/enclosures LT w/enclosures LT w/enclosures

A008 DI-MISC-80508B/T Technical Report-Study/Services Milestone Events A

(E) SMC/MCX

(E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures LT w/enclosures LT w/enclosures

LT w/enclosures LT w/enclosures LT w/enclosures

A009 DI-MISC-80508B/T Technical Report-Study/Services Quarterly Program Review (QPR) Package

BLK 16

(E) SMC/MCX

(E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures LT w/enclosures LT w/enclosures

LT w/enclosures LT w/enclosures LT w/enclosures

A010 DI-MISC-80508B/T Technical Report-Study/Services System Safety Program Plan (SSPP) N/A

(E) SMC/MCX

(E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures LT w/enclosures LT w/enclosures

LT w/enclosures LT w/enclosures LT w/enclosures

A011 DI-MISC-80508B/T Technical Report-Study/Services Mishap Cause Report N/A

(E) SMC/MCX

(E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures LT w/enclosures LT w/enclosures

LT w/enclosures LT w/enclosures LT w/enclosures

16.0 CDRL ATTACHMENT LIST

CDRL NO. ATTACHMENT TITLE DATED

A005 Pathfinder EMI/RFI Summary of Action Report Template N/A

17.0 CDRL ADDRESS LIST

SMC/MCEC Space and Missile System Center/Systems Directorate (SMC/MC) System Engineering Division Configuration/Data Management 483 N. Aviation Blvd El Segundo, CA 90245-2808 Attn: SMC/MCEC

Email Address: TBD@us.af.mil

SMC/PKJ Space and Missile System Center/Systems Directorate (SMC/MC) Contracting Division 483 N. Aviation Blvd El Segundo, CA 90245-2808 Attn: SMC/PKJ

Email Address: TBD@us.af.mil

DD FORM 1423-1, FEB 2001

SMC/MCX

6. REQUIRING OFFICE

SOW-01

5. CONTRACT REFERENCE

DI-MISC-80508B/T

4. AUTHORITY (Data Acquisition Document No.)

3. SUBTITLE

Satellite Performance

Technical Report-Study/Services

2. TITLE OF THE DATA ITEM

A001

1. DATA ITEM NO.

TBD

F. CONTRACTOR

TBD

E. CONTRACT/PR NO.

COMSATCOM Pathfinder #2

D. SYSTEM/ITEM

TDP

C. CATEGORY

TM OTHER MISC

A

B. EXHIBIT A. CONTRACT LINE ITEM NO.

The 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 the Department of Defense, Executive Services and Communications Directorate (07040188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

Form Approved OMB No. 0704-0188 CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

N/A

8. APP CODE

LT

7. DD 250 REQ

D

9. DIST STATEMENT

REQUIRED

DATE OF SUBSEQUENT

SUBMISSION

BLK 16

11. AS OF DATE

BLK 16

DATE OF FIRST

SUBMISSION

QTRLY

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE G. PREPARED BY

1. (BLK 4):

a. Requirements. Paragraph 2. Format. Add: "Contractor's format is acceptable."

b. Requirements. Paragraph 2. Format. Delete Paragraphs 2(b) and 2(c) entirely.

c. Requirements. Paragraph 3. Content. Delete Paragraph 3(b) in its entirety.

d. Requirements. Paragraph 3. Content. Delete Paragraph 3(c) and replace with the following: “The report shall contain the following items for the

United States Government (USG) Transponders, and in a format approved by the

USG:

1) Satellite ID#

2) Satellite Location

3) Coverage Area Patterns

4) Saturated Flux Density (SFD) contours

5) Point by Point Cross-Polarization (XPD) contours

6) Frequency Plans

7) Equivalent Isotropically Radiated Power (EIRP) and Gaint/Temperature

(G/T) contours

8) In-Band Performance, amplitude and phase.”

2. (BLKs 12 & 13):

a. Submit initial 5 business days (BD) before the first Quarterly Program

Review (QPR).

b. Subsequent submissions are due the day of each QPR and shall include updates from any analysis and testing since the previous QPR.

c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL

18. ESTIMATED

TOTAL PRICE

17. PRICE GROUP

SOW-02, SOW-03, SOW-04

Cybersecurity Compliance Matrix

A002

TBD

E. CONTRACT/PR NO.

The 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 the Department of Defense, Executive Services and Communications Directorate (07040188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

REQUIRED

DATE OF SUBSEQUENT

SUBMISSION

BLK 16

DATE OF FIRST

SUBMISSION

a. Requirements. Paragraph 2. Format. Add the following: “(e) The

Cybersecurity Compliance Matrix shall be formatted in accordance with the

Microsoft Excel file template provided via electronic means by the

Government.”

b. Requirements. Paragraph 2. Format. Delete Paragraph 2(a) and replace with: “The report and all attachments shall be typewritten and delivered electronically.”

c. Requirements. Paragraph 3. Content. Delete Paragraph 3(b) in it its entirety.

d. Requirements. Paragraph 3. Content. Delete Paragraph 3(c) in it its

e. Requirements. Paragraph 3. Content. Delete Paragraph 3(d) in it its

2. (BLK 10, 12 & 13):

b. Submit updates 5 BD prior to the System Preliminary Design Review, System

Critical Design Review, Integration Readiness Review, and the Spacecraft Pre-

Ship Review.

c. Submit final 20 BD following the Information Assurance (IA) certification.

d. Update as required or by Procurement Contracting Officer (PCO) direction.

SOW-05

CNSSP-12 Compliance

A003

TBD

E. CONTRACT/PR NO.

The 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 the Department of Defense, Executive Services and Communications Directorate (07040188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

REQUIRED

DATE OF SUBSEQUENT

SUBMISSION

BLK 16

DATE OF FIRST

SUBMISSION

with the following: “The report and all attachments shall be typewritten and delivered electronically.”

c. Requirements. Paragraph 2. Format. Delete Paragraphs 2(b) and 2(c)

d. Requirements. Paragraph 3. Content. Delete Paragraph 3(b) in its entirety.

e. Requirements. Paragraph 3. Content. Delete Paragraph 3(c) and replace it with the following: “For the implementation of CNSSP 12, documentation attesting to what is being implemented and progress thereof needs to be provided. For the final submission, the Contractor shall provide a copy of the NSA-issued and signed CNSSP-12 compliance letter.”

f. Requirements. Paragraph 3. Content. Delete Paragraph 3(d).

2. (BLK 8):

a. Only the NSA-issued and signed CNSSP-12 compliance letter delivery will be for approval.

b. Government approval shall be by Contractual Document Action (CDA).

3. (BLKs 12 & 13):

b. Provide subsequent submissions 5 BD prior to each QPR meeting.

c. Submit final 5 BD before the Spacecraft Pre-Ship Review. Submission shall include the NSA-issued and signed CNSSP-12 compliance letter.

RESERVED

A004

TBD

E. CONTRACT/PR NO.

TM OTHER

The 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 the Department of Defense, Executive Services and Communications Directorate (07040188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

REQUIRED

DATE OF SUBSEQUENT

SUBMISSION

DATE OF FIRST

SUBMISSION

SOW-24

Pathfinder EMI/RFI Summary of Action Report

A005

TBD

E. CONTRACT/PR NO.

The 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 the Department of Defense, Executive Services and Communications Directorate (07040188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

REQUIRED

DATE OF SUBSEQUENT

SUBMISSION

BLK 16

DATE OF FIRST

SUBMISSION

a. Requirements. Paragraph 2. Format. Add the following: “(e) The Pathfinder

Electro-Magnetic Interference/Radio-Frequency Interference (EMI/RFI) Summary of Action Report shall be formatted in accordance with the attached

Pathfinder EMI/RFI Summary of Action Report template.

with: “The report and all attachments shall be typewritten and delivered electronically.”

c. Requirements. Paragraph 3. Content. Delete Paragraph 3(b) in it its

d. Requirements. Paragraph 3. Content. Delete paragraph 3(c) in it its

e. Requirements. Paragraph 3. Content. Delete paragraph 3(d) in it its

2. (BLKs 10, 12 & 13):

a. Submit 5 calendar days (CD) after incident resolution.

b. Update as required or by Procurement Contracting Officer (PCO) direction.

Pathfinder EMI/RFI Summary of Action Report

REPORT NUMBER: AR_ _#543-241255ZMAR2011 (20)

REPORT TYPE

IMPACT: Major/Minor

Major

INCIDENT

DATE/TIME

(1)

INITIAL (3) Place an X in appropriate box TCF REP

DATE/TIME:

(2)

UPDATE (3) DATE/TIM

E:

(4) TCF TECH

INITIALS:

(2)

CLOSE (3) Date/Time NOC sent report

INCIDENT

TYPE

EST TIME RESTORE: TBD (5)

OUTAGE (8) NOC

TECH:

Name:

(11)

TIME RESTORED: TBD (6)

HAZCON (8) Place an X in appropriate box TOTAL TIME

OUTAGE:

TBD (7)

OTHER (8)

INFO (9) RFO: (10)

TASK ORDER NUMBER (12)

CIRCUITS/COMPONENTS

AFFECTED (BY CCSD)

(13)

DESCRIPTION OF

PROBLEM

(14)

FINAL RESOLUTION

(15)

CONTAINMENT/RESTOR

AL ACTIONS

(16)

FOLLOW-UP/OTHER (17)

ESCALATION PROCEDURES

IMPLEMENTED? Y/N

(18)

ATTACHMENTS

(19)

Company-NOC Incident Report – Instructions

This document provides instructions for completing the GSSC Incident Report. Reference the Incident Report

Form and match the instructions by number to ensure that the blocks are completed accurately.

(1) INCIDENT DATE/TIME

The actual date/time that the incident started goes in this block, NOT the date/time that the Incident Report was opened. If not known, ask the end user for the known or best estimate for this data. Once entered, this information never changes for this report.

(2) TCF DATE/TIME & TCF TECH INITIALS

The same information that is in (1) above goes in this block, along with the Tech’s name or initials. Once entered, this information never changes for this report. (Note: Reason for duplication of item (1) is not known, so continue as instructed until further notice.)

(3) INITIAL/UPDATE/CLOSE

Place an ‘X’ in the initial block when the report is opened. For the first update and every consecutive update, move the ‘X’ to the ‘Update’ block. Upon closure of the ticket, the ‘X’ moves to the ‘CLOSE’ block.

(4) Item (3) DATE/TIME

Change this date/time to be the actual date/time of the report update you are creating and preparing to send.

(5) EST TIME RESTORE

(6) TIME RESTORED

Enter the date/time that the incident was fixed, not when the ticket was closed. When the ticket is closed, the date/time of closure will be at the top of the last entry in the ‘DESCRIPTION OF PROBLEM’ and/or the

‘FINAL RESOLUTION’ blocks, and the ‘OUTAGE’ block in (3) will be marked.

(7) TOTAL TIME OUTAGE

This is the span of time between items (6) and (1) in hours.

(8) INCIDENT TYPE

Place an ‘X’ in the appropriate block labeled ‘OUTAGE’, ‘HAZCON’ or ‘OTHER’. Use ‘OUTAGE’ if the service was knocked out or is hard down. ‘HAZCON’ is not used often, but could represent severe weather conditions. Use ‘OTHER’ when service is degraded due to interfere, etc.

(9) INFO

Enter a brief description of the incident type in item (8).

(10) RFO

The information in this block needs to be specific sufficiently detailed describing the outage.

(11) NOC TECH

Place the name of NOC Tech providing the latest update.

(12) TASK ORDER NUMBER

This block is for the Task Order where the incident is occurring.

(13) CIRCUITS/COMPONENTS AFFECTED (BY CCSD)

Identify, as accurately as possible, the area (i.e., BW, carrier, network, etc.) being affected.

(14) DESCRIPTION OF PROBLEM

Place all update entries in this block with the latest entry at the top and the history in descending order. Include the date/time and Tech initials at the top of each entry. Example:

112145ZFEB2011_KV

T17, T18, and T19 are currently up and stable since 02/07, but the line card is still receiving intermittent

CRC errors. Plot on E9, transponders 7 & 8 has not indicated interference that was previously affecting sites. Will continue to monitor in ensure no further x-pol from TO253.

022053ZFEB2011_NR

Contacted CACI/Ray who advised the end user suspected of causing the interference in Fort Gordon, GA (CTC 115) was notified yesterday via email. Received call directly from Ft Gordon/Don Huber who advised he is unable to detect any interference via the Specan. Interference on transponder 7 has cleared. Will monitor transponder for further interference.

(15) FINAL RESOLUTION

Cut and pasted the final entry from item (14) above.

(16) CONTAINMENT / RESTORAL ACTIONS

Explain in sufficient detail what was done to correct the problem.

(17) FOLLOW-UP / OTHER

IGNORE this block for now.

(18) ESCALATION PROCEDURES IMPLEMENTED? Y/N

Select either ‘Yes’ or ‘No’ if the problem has been escalated.

(19) ATTACHMENTS

IGNORE this block for now. Usually, this block is for inserting emails or plots. In lieu of this block, it is preferred to add any additional information (i.e., emails, plots, etc.) to the current entry in item (14) so that the additional information is placed with the text entry that it is related to.

(20) REPORT NUMBER: AR#

Report numbers must always be in the following format:

CTC 115-241255ZMAR2011-001-xx

O = Open (for the first report) / U1, U2, - Ux for updates/ C = Closed).

This reference is the only one portion of the number that changes for each ticket update.

001 for the first ticket on CTC 115 on the date created. 002, if a second ticket is opened on CTC 115 on the same date, etc. This shows the total number of tickets opened on CTC 115 on the date shown and is used by

GSSC for statistical information.

Date/time (ZULU)/month/year

Task Order number (i.e., CTC 115, TO 643, etc.)

Note: The report number in the ‘Subject’ line of every outgoing email should match the report number as updated on the ticket.

SOW-28, SOW-29

Satellite Operator Transmission Plan

A006

TBD

E. CONTRACT/PR NO.

The 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 the Department of Defense, Executive Services and Communications Directorate (07040188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

REQUIRED

DATE OF SUBSEQUENT

SUBMISSION

BLK 16

DATE OF FIRST

SUBMISSION

Delete all paragraphs and replace with the following: “The Satellite Operator

Transmission Plan shall be formatted in accordance with the Microsoft Excel file provided via electronic means by the Government.”

2. (BLK 10, 12 & 13):

b. Subsequent submissions are due 5 BD after a change is made to the

Transmission Plan.

SOW-32

Overdrive Protection Data

A007

TBD

E. CONTRACT/PR NO.

The 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 the Department of Defense, Executive Services and Communications Directorate (07040188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

REQUIRED

DATE OF SUBSEQUENT

SUBMISSION

BLK 16

DATE OF FIRST

SUBMISSION

a. Requirements. Paragraph 2. Format. Add: “Contractor’s format is acceptable.”

d. Requirements. Paragraph 3. Content. Replace Paragraph 3(c) with the following: Transponder protection test and evaluation report shall be generated to verify that the transponder protection capability has been implemented on a spacecraft that has not yet been launched. The report shall include at least the following information:

1) Methodology used to achieve transponder protection capability.

2) Unit level test results for the receivers of the USG Transponders against an input power corresponding to the threat specified in the Technical

Requirements Document (TRD).

3) Analysis of the end-to-end transponder performance under simulated attack that demonstrates that the transponder shall withstand a continuous 24 hour period of illumination from the uplink carrier without damage or degradation in transponder performance.

a. Only the final submission is for approval.

3. (BLKs 12 & 13):

b. Subsequent submissions are due 5 BD before each QPR until the completion of spacecraft In Orbit Test.

c. Final submission is due 10 BD prior to the Pre-Ship Review.

SOW-034, SOW-35, SOW-36, SOW-37, SOW-38

Milestone Events

A008

TBD

E. CONTRACT/PR NO.

The 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 the Department of Defense, Executive Services and Communications Directorate (07040188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

REQUIRED

DATE OF SUBSEQUENT

SUBMISSION

BLK 16

DATE OF FIRST

SUBMISSION

a. Requirements. Paragraph 2. Format. Add: “Contractor's format is

b. Requirements. Paragraph 2. Format. Delete Paragraphs 2(b) & 2(c) entirely.

c. Requirements. Paragraph 3. Content. Delete Paragraph 3(b) in its

d. Requirements. Paragraph 3. Content. Replace Paragraph 3(c) with the following: “For the spacecraft on which the USG Transponders reside, the

Contractor shall provide the following:

1) A letter stating successful completion of the Spacecraft Preliminary

Design Review, with a copy of the review presentation itself.

2) A letter stating successful completion of the Spacecraft Critical Design

Review, with a copy of the review presentation itself.

3) A letter stating successful completion of the Spacecraft Thermal Vacuum

Testing and a copy of the test data.

4) A letter stating successful completion of Spacecraft Separation and

Acquisition of Spacecraft Telemetry which includes a description of any issues or anomalies that occurred related to the event.

5) A letter stating successful completion of spacecraft in-orbit test (IOT) and a copy of the test data for the USG Transponder(s).”

2. (BLKs 10, 12 &13):

a. For Section d, items 1 and 2; submit 5 business days (BD) prior to the meeting.

b. For Section d, items 3-5; submit 10 BD after completion of the event.

SOW-39, SOW-40

Quarterly Program Review (QPR) Package

A009

TBD

E. CONTRACT/PR NO.

The 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 the Department of Defense, Executive Services and Communications Directorate (07040188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

REQUIRED

DATE OF SUBSEQUENT

SUBMISSION

BLK 16

DATE OF FIRST

SUBMISSION

a. Requirements. Paragraph 2. Format. Add: “Contractor’s format is

d. Requirements. Paragraph 3. Content. Delete Paragraph 3(c) and replace with the following: “The contractor shall hold Quarterly Program Reviews

(QPRs) which shall cover at a minimum:

1) Program schedules

2) Program status and progress

3) All CDRL progress, updates, and status

4) Relevant satellite anomalies across the Contractor’s fleet

5) Technical issues and operational issues

6) Status of all payments and remaining payments

e. Only the first delivery of the QPR package shall be known as the Program

Management Plan (PMP).

a. Only the PMP will be for approval.

2. (BLKs 12 & 13):

a. The first submittal of the QPR package (PMP) is due 5 business days (BD) before each QPR.

b. Subsequent submittals of the QPR package are due 5 BD before each QPR.

SOW-42

System Safety Program Plan (SSPP)

A010

TBD

E. CONTRACT/PR NO.

The 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 the Department of Defense, Executive Services and Communications Directorate (07040188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

REQUIRED

DATE OF SUBSEQUENT

SUBMISSION

BLK 16

DATE OF FIRST

SUBMISSION

a. Use DID number DI-MISC-80508B in leui of DID number DI-SAFT-81626.

b. Requirements. Paragraph 2. Format. Add: "Contractor's format is

c. Requirements. Paragraph 2. Format. Delete Paragraph 2(a) and replace delivered in electronically.”

d. Requirements. Paragraph 2. Format. Delete Paragraphs 2(b) and 2(c)

e. Requirements. Paragraph 3. Content. Delete Paragraph 3(b) in its entirety.

f. Requirements. Paragraph 3. Content. Delete Paragraph 3(c) and replace with the following: “The Contractor shall provide a copy of the system safety program that satisfies its commercial requirements for all work, accommodations, and new components provided under this contract.”

a. Submit initial 5 business days (BD) prior to Spacecraft Preliminary Design

Review.

b. Submit updates 5 BD prior to the following milestones:

1) Spacecraft Critical Design Review

2) Pre-Ship Review

SOW-44

Mishap Cause Report

A011

E. CONTRACT/PR NO.

The 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 the Department of Defense, Executive Services and Communications Directorate (07040188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

REQUIRED

DATE OF SUBSEQUENT

SUBMISSION

BLK 16

DATE OF FIRST

SUBMISSION

1. (BLKs 4):

delivered in electronically.”

c. Requirements. Paragraph 2. Format. Delete Paragraphs 2(b) and 2(c)

d. Requirements. Paragraph 3. Content. Delete Paragraph 3(b) in its entirety.

e. Requirements. Paragraph 3. Content. Delete Paragraph 3(c) in its entirety and replace it with the following: “The Contractor shall provide the

Mishap Cause Report.”

a. Submit within 30 calendar days (CD) of mishap cause determination.

b. Update as required or by Procurement Contracting Officer…