Exhibit_E_-_PTES_CLIN_0005_CDRLs.pdf

P000X

FA8808-17-R-0006

EXHIBIT E

FOR

CONTRACT NO. FA8808-17-R-0006

CONTRACT DATA REQUIREMENTS LIST (CDRL)

FOR

PROTECTED TACTICAL ENTERPRISE SERVICE (PTES)

CLIN 0005

19 MARCH 2018

Contract No: FA8808-17-R-0006 Contractor: Name Exhibit: E System Item: PTES CLIN: 0005 Date: 19 MAR 2018

REVISION HISTORY

APPROVAL

DATE

DESCRIPTION OF CHANGE MODIFICATION

(P000) NO.

DD MMM YYYY Initial release for CLIN 0005. P000X

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) items contained within Exhibit A for Protected Tactical Enterprise Services (PTES) on Contract FA8808-17-R-0006, Contract Line Item Number (CLIN) 0005.

2.0 GENERAL

2.1 Data Item Descriptions (DIDs) referenced in Block 4 of the CDRL line items are listed in the Acquisition Streamlining and Standardization Information System (ASSIST) (http://quicksearch.dla.mil). Only unique DIDs or attachments will 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 will 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 indicates that distribution statement “D” shall be annotated on each data item in accordance with (IAW) 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 Department of Defense (DoD) and US DoD Contractors only, due to the sensitive information (as defined in DoD 5230.25) associated with the Protected Tactical Enterprise Services (PTES) effort. Other requests for this document shall be referred to SMC/PKJ through SMC/MCES.

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 Protected Tactical Enterprise Services (PTES), and as determined in the Program PTES Security Classification Guide. Other requests for this document shall be referred to SMC/PKJ through SMC/MCES.

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

http://quicksearch.dla.mil/

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

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 Protected Tactical Enterprise Services (PTES) effort. Other requests for this document shall be referred to SMC/PKJ through SMC/MCES.

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 Protected Tactical Enterprise Services (PTES), and as determined in the PTES Security Classification Guide. Other requests for this document shall be referred to SMC/PKJ through SMC/MCES.

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.

• 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 CDRL 1423 form).

• 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 CDRL 1423 form.

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 effective contract date (ECD), the contract shall be required to support electronic delivery via TopVue. External addressees will 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 (ECAs) 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.

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

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

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). 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) days 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.

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 https://cloud1.topvue.com/topvue-mc/ 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 -1840C, Automated Interchange of Technical Information. Coordination must be made with the Government Data Manager prior to delivery.

8.4 Mail large unclassified data items to:

Los Angeles Air Force Base Space and Missile Systems Center MILSATCOM Systems Directorate PTES - Attn: MCEC Configuration/Data Management 483 N. Aviation Blvd.

El Segundo, CA 90245

8.5 Hand deliver large unclassified data items to:

MILSATCOM Systems Directorate PTES - Attn: MCEC Configuration/Data Management 2350 East El Segundo Blvd. /A8 Lobby

8.6 Email the notification of unclassified delivery to: SMCMC.ACDCMDM@US.AF.MIL

8.7 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 can be mailed or hand delivered on

CD/DVD. Coordination must be made with the Government Data Manager prior to delivery.

9.2 Mail unclassified data items to:

Space and Missile Systems Center MILSATCOM Systems Directorate PTES - Attn: MCEC Configuration/Data Management mailto:AEHF.CMDM@us.af.mil

9.3 Hand deliver unclassified data items to:

MILSATCOM Systems Directorate PTES - Attn: MCEC Configuration/Data Management 2350 East El Segundo Blvd. /A8 Lobby

9.4 Email the notification of unclassified delivery to: SMCMC.ACDCMDM@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 or hand delivered.

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 Coordination must be made with SMC/MC Security (MCES) and the Government Data Manager prior to delivery by hand or mail.

10.5 The Contractor shall provide a notification of shipment/delivery to the Government Data Manager via 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 Mail classified data items to:

SMC/MC Security (MCES) PTES - Attn: MCD

10.8 Hand deliver classified data items to:

SMC/MC Security (MCES) PTES - Attn: MCD 2350 East El Segundo Blvd.

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

10.10 Email the notification of classified delivery to: SMCMC.ACDCMDM@US.AF.MIL mailto:SMCMC.ACDCMDM@US.AF.MIL mailto:SMC.MC.Security@us.af.mil mailto:AEHF.CMDM@us.af.mil

10.11 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 CDRL form, 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 will 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 will 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 CDRL form, 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 CDRL form, the Contractor is to refer to the approval method(s) outlined in Block 16 of the CDRL form.

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) will 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 BI-WE Each two weeks BLK Block CD Calendar Days CDA Contractual Document Action CDRL Contract Data Requirements List CLIN Contract Line Item Number DAC Days After Contract start DACM Days After Contract Modification ECD Effective Contract Date EOC End of Contract EOM End of Month EOQ End of Quarter EOW End of Week IAW In Accordance With LT Letter of Transmittal MTHLY Monthly N/A Non-Approval NET No Earlier Than NLT No Later Than ONE/P One Time Preliminary Draft ONE/R One Time and Revision

CODE DEFINITION

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 WEKLY Weekly XTIME Multiple Separate Submittals (i.e., 2Time, 3Time)

Contract No.: FA8808-17-R-0006 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

E050 DI-NDTI-80566A/T Test Plan BLK 16 (E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures

LTO

LT w/enclosures

LTO

E051 DI-NDTI-80603A/T Test Procedure A (E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures

LTO

LT w/enclosures

LTO

E052 DI-MISC-80508B/T Technical Report-Study/Services Test Reports BLK 16 (E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures

LTO

LT w/enclosures

LTO

E064 DI-MISC-80508B/T Technical Report-Study/Services Product Drawings/Models and Associated Lists A (E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures

LTO

LT w/enclosures

LTO

E087 RESERVED

E088 RESERVED

E099 RESERVED

E100 RESERVED

E106 DI-MISC-80508B/T Technical Report-Study/Services System Level Test Readiness Review Briefing BLK 16 (E) SMC/MCEC

(E) SMC/PKJ

LT w/enclosures

LTO

LT w/enclosures

LTO

E114 RESERVED

16.0 CDRL ATTACHMENT LIST

CDRL

NO.

ATTACHMENT

NO. ATTACHMENT TITLE DATED

N/A

17.0 CDRL ADDRESS LIST

SMC/MCD Los Angeles Air Force Base

MILSATCOM Systems Directorate Advanced Development Division

El Segundo, CA 90245-2808

SMC/MCEC Los Angeles Air Force Base

MILSATCOM Systems Directorate System Engineering Configuration/Data Management

SMC/MCLA Los Angeles Air Force Base

MILSATCOM Systems Directorate Sustainment Logistics

SMC/MCP Los Angeles Air Force Base

MILSATCOM Systems Directorate Program Control

SMC/MCPC Los Angeles Air Force Base

MILSATCOM Systems Directorate Program Control

SMC/PKJ Los Angeles Air Force Base

MILSATCOM Systems Directorate Contracting Division

SMC/MCDP

6. REQUIRING OFFICE

CLIN 0005 - 1.4.1.2.1.f

5. CONTRACT REFERENCE

DI-NDTI-80566A/T

4. AUTHORITY (Data Acquisition Document No.)

3. SUBTITLE

Test Plan

2. TITLE OF THE DATA ITEM

E050

1. DATA ITEM NO.

TBD

F. CONTRACTOR

E. CONTRACT/PR NO.

PTES

D. SYSTEM/ITEM

TDP

C. CATEGORY

TM OTHER NDTI

E

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 (0704-0188). 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)

BLK 16

8. APP CODE

LT

7. DD 250 REQ

D

9. DIST STATEMENT

REQUIRED

13. DATE OF SUBSEQUENT

SUBMISSION

11. AS OF DATE

12. DATE OF FIRST

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. General. Add:

(1) “Only one System Level Test Plan shall be generated, detailed Event Test Plans for each activity shall be included as attachments and added during updates or as stand-alone documents as required.” The plan shall include 3 additional Appendices, one for each of the following:

i) Joint Hub Segment

ii) Joint Hub Key Management System (ECU) (non Security Verification Plan and Procedures (SVPP))

iii) Key Management System (KMS) ECU (non SVPP)”

(2) “Following the initial System Test Plan delivery, it is envisioned all future deliveries shall be updates, attachments, and/or amendments or such that development and approval process reflects the intent of development.”

(3) “For system Developmental Test (DT) and Operational Test (OT) events, the 46th Test Squadron and Air Force Operational Test and Evaluation Center (AFOTEC) will develop and use their specific test plans.”

b. Requirements. Paragraph 4.7. Schedule. Add: “Shall identify a schedule for test planning, execution and reporting.”

c. Requirements. Paragraph 4.9.6. Test Objectives. Add: “Test objectives shall be consistent with the Protected Tactical Enterprise Service (PTES) System Integration and Test Plan (SITP)(CDRL E005).”

2. (BLK 8):

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

b. Government approval shall be required for final submittal(s) only.

3. (BLKs 10, 12, 13):

a. Submit draft 120 calendar days (CD) prior to the start of each test event where the Contractor desires to test and/or verify requirements.

b. Submit final 90 CD prior to the start of each major test event where the Contractor desires to test and/or verify requirements.

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

PREVIOUS EDITION MAY BE USED. DD FORM 1423-1, FEB 2001

DI-NDTI-80603A/T

Test Procedure

E051

TM OTHER NDTI

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 (0704-0188). 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

A

a. Requirements. Paragraph 2. Format. Delete in its entirety and replace with the following: "Contractor's format is acceptable."

b. Requirements. Paragraph 3. Content. Add: "As-run test procedures, including those used in the Joint Hub, Joint Hub End Cryptographic Unit (ECU) (non Security Verification Plan and Procedures (SVPP)), Key Management System (KMS) ECU (non SVPP), and ground string verification testing including site acceptance testing (SAT), shall be included in the final delivery."

c. Requirements. Paragraph 3.2.3.3. Test requirements. Add: "Test procedures shall focus on Protected Tactical Enterprise Service (PTES) specific test activities, and how best to engage the program office, users, Developmental and Operational Testers to achieve approvals and certifications to operation."

2.(BLK 8):

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

b. Government approval shall be required for each submission.

3. (BLKs 10, 12, 13):

a. Submit draft 60 calendar days (CD) prior to the start of each test event where the Contractor plans to verify requirements.

b. Submit final 30 CD prior to the start of each major test event where the Contractor desires to test and verify requirements.

c. Submit as-run final test procedures 30 CD following major test events.

d. Submit updates incorporating Government comments 15 CD after notification.

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

DI-MISC-80508B/T

Test Reports

Technical Report-Study/Services

E052

TM OTHER MISC

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 (0704-0188). 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

Requirements. Paragraph 3. Contents. Add:

(1) "The Test Report shall include:

i) An executive summary of overall test results to include key activities executed and completion status with dates. All test data used and collected during the test should be made available by Government request.

ii) A test scorecard table with columns for Test Report Paragraph Number, Test Case/Test Procedure ID, corresponding Technical Requirements Document (TRD)/Interface Control Document (ICD) requirements, Test Objective, and Test pass/fail result.

iii) Status of Deficiency Reports (DRs) and lessons learned.

iv) Discussions on system safety and implementation of Protected Tactical Enterprise Service (PTES) Security Classification Guide (SCG)."

(2) “Test Reports are not expected for every Sprint. However test reports are expected for major tests, such as Joint Hub, Joint Hub End Cryptographic Unit (ECU) (non Security Verification Plan and Procedures (SVPP)), Key Management System (KMS) ECU (non SVPP), and ground string verification testing including site acceptance testing (SAT), and where the Contractor plans to formally verify requirements.”

2. (BLK 8):

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

b. Government approval shall be required for final submittal(s) only.

3. (BLKs 10, 12, 13):

a. Submit draft 21 calendar days (CD) following each test event where the Contractor plans to verify requirements.

b. Submit final 21 CD following receipt of last Government comment.

SMC/MCLA

CLIN 0005 - 1.4.1.1.1.c

Product Drawings/Models and Associated Lists

E064

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 (0704-0188). 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

A with the following:

(1) "Contractor's format is acceptable."

(2) "Product Drawings/Models and Associated Lists shall be in either the Contractor's format or the Government's format as specified on the Technical Data Package (TDP) Option Selection Worksheet incorporated into the contract or purchase order."

b. Requirements. Paragraph 3. Contents. Add: "Product Drawings/Models and Associated Lists and Commercial Drawings/Models and Associated Lists shall meet the requirements of Military Standard (MIL-STD)- 31000."

c. Requirements. Paragraph 3(d). Contents. Delete in its entirety and replace with the following:

(1) "The Commercial Drawings/Models and Associated Lists shall be developed and delivered in two volumes:

i) Volume 1 - Product Drawings/Models and Associated Lists

ii) Volume 2 - Commercial Drawings/Models and Associated Lists"

(2) "Volume 1 - Product Drawings/Models and Associated Lists shall include the following:

i) The design disclosure information necessary to enable a manufacturer of similar products at the same or similar state of the art to produce and maintain quality control of item(s) so that the resulting physical and functional characteristics duplicate those of the specified item. These drawings shall:

(a) Reflect the end product at its current level of design maturity.

(b) Provide the engineering data for Logistics Support products.

(c) Provide the necessary data to permit competitive acquisition of the original item(s)."

ii) "Product Drawings/Models and Associated Lists shall conform to the requirements of American Society of Engineers (ASME) Y14.100, or, if applicable, ASME Y14.100 and Appendices B through E, as required, ASME Y14.34 and ASME Y14.41.

They shall document directly or by reference the following, as applicable:

(a) Details of unique processes, i.e., not published or generally available to industry, when essential to design and manufacture.

(b) Performance ratings.

(c) Dimensional and tolerance data.

(d) Critical manufacturing processes and assembly sequences.

(e) Tolerance input and output characteristics.

(f) Diagrams.

(g) Mechanical and electrical connections.

(h) Physical characteristics, including form, finishes, and protective coatings.

(i) Details of material identification, including material condition, and mandatory treatments and coatings.

(j) Inspection, test and evaluation criteria.

0 0 0 15. TOTAL See continuation sheet...

16. REMARKS (Continued)

(k) Quality assurance requirements.

(l) Hardware marking requirements.

(m) Requirements for reliability, maintainability, environmental conditioning, shock and vibration testing and other operational or functional tests.

(n) Vendor substantiation data when required by the contract or purchase order.

(o) Requirements for programming software into devices or assemblies including a description of the input media and the procedures for validating that the software has been installed correctly.

(p) Special consideration items and processes.

(q) Equipment calibration requirements.

iii) All parameters required to define each unit, assembly, subassembly, part or material shall be presented on the applicable drawing/model. This includes data such as:

(a) All necessary mechanical dimensions to fully define fabrication, acceptance, interface or installation of the item depicted.

(b) All necessary electrical parameters to fully define fabrication, acceptance, interface or installation of the item depicted.

(c) All other necessary physical parameters to fully define fabrication, acceptance, interface or installation of the item depicted, i.e., weight, pressure, viscosity, etc.

(d) All necessary environmental conditions which units, assemblies, subassemblies, parts and materials must meet to perform effectively in the end item, such that the end item will meet its specification requirements."

(3) "Product Drawings/Models and Associated Lists shall be identified with the Contractor's Commercial and Government Entity (CAGE) code and Contractor document numbers or with a Government CAGE code and document numbers as specified in the TDP Option Selection Worksheet incorporated in the contract or purchase order."

(4) "Selection of drawings. The types of drawings required will vary according to the complexity of the contract end item. The TDP Option Selection Worksheet incorporated in the contract or purchase order shall specify whether the Contractor or the Government is responsible for selecting the types of drawings/models and Associated Lists."

(5) "Vendor Item Control Drawings. Vendor Item Control Drawings shall be used to specify the requirements for purchased items when such items have been approved for use in the design and are used without alteration, selection or source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements)."

(6) "Source Control Drawings. Source Control Drawings shall be used to specify the requirements for purchased items only when such items have been approved for use in the design and:

i) the item is for a critical application; and

ii) the requirements can be met by an item from one or more sources; and

iii) the application required source qualification (testing of an item prior to procurement action to ensure that it satisfies the specified requirements"

(7) "Standard Microcircuit Drawings. Standard Microcircuit Drawings (MIL-HDBK-780) shall be used to specify the requirements of microcircuits."

(8) "Volume 2 - Commercial Drawings/Models and Associated Lists) shall include information to permit Government maintenance, modification, and engineering analysis of commercial items."

2. (BLK 8):

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

b. Government approval shall be required for final submittal(s) only.

3. (BLKs 10, 12, 13):

a. Submit update of Vol. 1 and 2 90 CD before installations.

b. Submit final of Vol. 1 and 2 60 CD prior to Physical Configuration Audit (PCA).

DD FORM 1423-1, FEB 2001

RESERVED

E087

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 (0704-0188). 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

E088

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 (0704-0188). 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

E099

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 (0704-0188). 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

0 0 0 15. TOTAL See continuation sheet...

E100

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 (0704-0188). 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

CLIN 0005 - 1.4.1.2.1.g

System Level Test Readiness Review Briefing

E106

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 (0704-0188). 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 with: "Contractor's format is acceptable."

b. Requirements. Paragraph 3. Contents. Add: "The scope of the System Level Test Readiness Review (TRR) package content shall be in accordance with Institute of Electrical and Electronics Engineers (IEEE) 15288.2 and Space and Missile Systems Center (SMC)-S-021 Appendix F, paragraph 60.3 and shall be written to be compliant with the PTES System Engineering Plan (SEP).

2. (BLK 8):

a. Government approval shall be by Contractual Document Action (CDA) for final deliveries only.

b. Government approval shall be required for final submittal(s) only.

3. (BLKs 10, 12, 13):

a. For test events where the Contractor plans to formally verify requirements:

(1) Submit draft 21 calendar days (CD) prior to the TRR.

(2) Submit final incorporating Government comments 7 CD prior to the TRR.

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

E114

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 (0704-0188). 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