exhibit c for contract no. fa8808-17-r-0006 contract … government... · page 1 of 169 exhibit c...

of 169

EXHIBIT C

FOR

CONTRACT NO. FA8808-17-R-0006

CONTRACT DATA REQUIREMENTS LIST (CDRL)

FOR

PROTECTED TACTICAL ENTERPRISE SERVICE (PTES)

CLIN 0003

DD MONTH YYYY

Contract No: FA8808-17-R-0006 Contractor: Name Exhibit: C System Item: PTES CLIN: 0003 Date: DD MMM YYYY ___________________________________________________________________________

of 169

REVISION HISTORY

ARROVAL DATE

DESCRIPTION OF CHANGE MODIFICATION (P000) NO.

DD MMM YYYY Initial Release for CLIN 0003


of 169

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 C for Protected Tactical Enterprise Services (PTES) on Contract FA8808-17-R-0006, Contract Line Item Number (CLIN) 0003.

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.


of 169

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


of 169

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.


of 169

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


of 169

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

Los Angeles Air Force Base Space and Missile Systems Center MILSATCOM Systems Directorate PTES - Attn: MCEC Configuration/Data Management 2350 East El Segundo Blvd. /A8 Lobby El Segundo, CA 90245

8.6 Email the notification of unclassified delivery to: [email protected]

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:


of 169

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

9.3 Hand deliver unclassified data items to:

Los Angeles Air Force Base Space and Missile Systems Center MILSATCOM Systems Directorate PTES - Attn: MCEC Configuration/Data Management 2350 East El Segundo Blvd. /A8 Lobby El Segundo, CA 90245

9.4 Email the notification of unclassified delivery to: [email protected] 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:

Los Angeles Air Force Base Space and Missile Systems Center SMC/MC Security (MCES) PTES - Attn: MCD 483 N. Aviation Blvd. El Segundo, CA 90245

10.8 Hand deliver classified data items to:

Los Angeles Air Force Base Space and Missile Systems Center SMC/MC Security (MCES) PTES - Attn: MCD


of 169

2350 East El Segundo Blvd. El Segundo, CA 90245

10.9 To coordinate a classified delivery by mail/hand, contact: [email protected]

10.10 Email the notification of classified delivery to: [email protected]

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.


of 169

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


of 169

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


of 169

CODE DEFINITION 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 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 Exhibit: C System Item: PTES CLIN: 0003 Date: DD MMM YYYY

of 169

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

C001 DI-SESS-81785A Systems Engineering Management Plan (SEMP)

A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C002 DI-IPSC-81430A/T Operational Concept Description (OCD) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C004 DI-MGMT-81453B/T Data Accession List (DAL) N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C005 DI-MISC-80508B/T Technical Report-Study/Services System Integration and Test Plan (SITP)

BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C006 DI-IPSC-81432A/T System/Subsystem Design Description (SSDD)

SSDD and Solution Architecture Model BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C007 DI-MGMT-81334D/T Contract Work Breakdown Structure (CWBS)


LT w/enclosures LTO

LT w/enclosures LTO

C008 DI-SESS-81757A/T Design Review Information Package (DRIP)


LT w/enclosures LTO

LT w/enclosures LTO

C010 DI-MISC-80508B/T Technical Report-Study/Services PTES Software Development Plan (SDP)


LT w/enclosures LTO

LT w/enclosures LTO

C011 DI-MISC-80508B/T Technical Report-Study/Services Software Architecture Description (SAD)


LT w/enclosures LTO

LT w/enclosures LTO

C012 DI-IPSC-81437A/T Database Design Description (DBDD) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C013 DI-IPSC-81433A/T Software Requirements Specification (SRS)

Software Requirements Specification (SRS) - Joint Hub


LT w/enclosures LTO

LT w/enclosures LTO

C014 DI-IPSC-81438A/T Software Test Plan (STP) N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C015 DI-IPSC-81439A/T Software Test Description (STD) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C016 DI-IPSC-81440A/T Software Test Report (STR) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C017 DI-IPSC-81443A/T Software User Manual (SUM) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C018 DI-IPSC-81441A/T Software Product Specification (SPS) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C019 DI-IPSC-81442A/T Software Version Description (SVD) Mission Management System to Key Management System (MMS - KMS) SVD


LT w/enclosures LTO

LT w/enclosures LTO

C020 DI-MGMT-82035/T Software Resources Data Reporting: Development and Maintenance Reports and Data Dictionary

DD Form 3026-1 (SDR) & DD Form 3026-3 (ERP SDR)

N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO


of 169

CDRL NO.




C021 DI-MISC-80508B/T Technical Report-Study/Services Software and System Measurement Report (SSMR)


LT w/enclosures LTO

LT w/enclosures LTO

C022 DI-IPSC-81448B/T Firmware Support Manual (FSM) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C023 DI-IPSC-81429A/T Software Transition Plan (STrP) A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C024 DI-MISC-80508B/T Technical Report-Study/Services Agile Product Roadmap/Product Backlog


LT w/enclosures LTO

LT w/enclosures LTO

C025 DI-MISC-80508B/T Technical Report-Study/Services Software Licenses and Warranties A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C026 DI-IPSC-81431A/T System/Subsystem Specification (SSS) PTES System Specification BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C027 DI-MISC-80508B/T Technical Report-Study/Services Requirements Traceability Matrix (RTM)


LT w/enclosures LTO

LT w/enclosures LTO

C028 DI-SESS-80643D/T Specification Change Notice (SCN) Specification Change Notice (SCN)/Interface Revision Notice (IRN)


LT w/enclosures LTO

LT w/enclosures LTO

C029 DI-SESS-81248B/T Interface Control Document (ICD) Mission Management System to Key Management System (MMS - KMS) ICD


LT w/enclosures LTO

LT w/enclosures LTO

C030 DI-SESS-81248B/T Interface Control Document (ICD) Mission Management System to Joint Hub (MMS -Joint Hub) ICD


LT w/enclosures LTO

LT w/enclosures LTO

C031 DI-SESS-81248B/T Interface Control Document (ICD) Mission Management System to Key Loading and Initialization Facility (MMS KLIF) ICD


LT w/enclosures LTO

LT w/enclosures LTO

C032 DI-SESS-81248B/T Interface Control Document (ICD) Key Management System to End Cryptographic Unit (KMS-ECU) ICD


LT w/enclosures LTO

LT w/enclosures LTO

C033 DI-SESS-81248B/T Interface Control Document (ICD) Joint Hub to End Cryptographic Unit (Joint Hub ECU) ICD


LT w/enclosures LTO

LT w/enclosures LTO

C034.x DI-SESS-81248B/T Interface Control Document (ICD) Intra-Segment ICDs BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C035 DI-SAFT-81626/T System Safety Program Plan (SSPP) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C036 DI-SAFT-80102C/T Safety Assessment Report (SAR) N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C037 DI-MGMT-81808 Contractor's Risk Management Plan A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C038 DI-MGMT-81809 Risk Management Status Report N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C039 DI-HFAC-81742A/T Human Engineering Program Plan (HEPP)


LT w/enclosures LTO

LT w/enclosures LTO

C040 DI-SESS-80858C/T Supplier's Configuration Management Plan

Contractor's Configuration/Data Management Plan


LT w/enclosures LTO

LT w/enclosures LTO


of 169

CDRL NO.




C041 DI-SESS-80639D/T Engineering Change Proposal (ECP) Engineering Change Proposal (ECP)/Contract Change Proposal (CCP)


LT w/enclosures LTO

LT w/enclosures LTO

C042 DI-SESS-80640D Request for Variance (RFV) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C043 DI-MISC-80508B/T Technical Report-Study/Services Cybersecurity Implementation Plan (CSIP)


LT w/enclosures LTO

LT w/enclosures LTO

C044 DI-MISC-80508B/T Technical Report-Study/Services Cybersecurity Test and Verification Plan (CTVP)


LT w/enclosures LTO

LT w/enclosures LTO

C045 DI-MISC-80508B/T Technical Report-Study/Services Operating System and Software Patching Plan (OSSPP)


LT w/enclosures LTO

LT w/enclosures LTO

C046 DI-ADMN-81306/T Program Protection Implementation Plan (PPIP)


LT w/enclosures LTO

LT w/enclosures LTO

C047 DI-MISC-80508B/T Technical Report-Study/Services Key and Certificate Management Plan (KCMP) KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C048 DI-MISC-80508B/T Technical Report-Study/Services Key and Certificate Management Plan (KCMP) - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C049 DI-MISC-80508B/T Technical Report-Study/Services PTES System Verification Plan (SVP) A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

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

LT w/enclosures LTO

LT w/enclosures LTO

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

LT w/enclosures LTO

LT w/enclosures LTO

C052 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

C053 DI-MGMT-80227/T Contractor's Progress, Status and Management Report

Program Management Review Briefing N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C056 DI-FNCL-81565C/T Cost Data Summary Report (DD Form 1921)

Contractor Cost Data Report (CCDR) N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C057 DI-FNCL-81566C/T Functional Cost-Hour Report (DD Form 1921-1)


LT w/enclosures LTO

LT w/enclosures LTO

C058 DI-FNCL-81765B/T Contractor Business Data Report (DD Form 1921-3)


LT w/enclosures LTO

LT w/enclosures LTO

C059 DI-MISC-80508B/T Technical Report-Study/Services Product Support Plan (PSP) A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C060 DI-SESS-81613A Reliability And Maintainability (R&M) Program Plan


LT w/enclosures LTO

LT w/enclosures LTO

C061 DI-MISC-80508B/T Technical Report-Study/Services Combined Logistics Analyses Report (CLAR)


LT w/enclosures LTO

LT w/enclosures LTO

C062 DI-MISC-80508B/T Technical Report-Study/Services Product Support Analysis A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO


of 169

CDRL NO.




C063 DI-PSSS-81872A Level of Repair Analysis (LORA) Report N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C064 DI-MISC-80508B/T Technical Report-Study/Services Product Drawings/Models and Associated Lists


LT w/enclosures LTO

LT w/enclosures LTO

C065 DI-MGMT-81994 Priced Bill of Materials N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C066 DI-IPSC-81431A/T System/Subsystem Specification (SSS) PTES Segment Specification (MMS) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C067 DI-IPSC-81431A/T System/Subsystem Specification (SSS) PTES Segment Specification (KMS) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C068 DI-IPSC-81431A/T System/Subsystem Specification (SSS) PTES Segment Specification (KLIF) BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C069 DI-MISC-81762/T Security Evaluation Document (SED) Security Evaluation Document (SED) - KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C070 DI-MISC-81762/T Security Evaluation Document (SED) Security Evaluation Document (SED) - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C071 DI-QCIC-81689/T Security Verification Plan and Procedures

Security Verification Plan and Procedures - KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C072 DI-QCIC-81689/T Security Verification Plan and Procedures

Security Verification Plan and Procedures - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C073 DI-QCIC-81690/T Security Verification Report Security Verification Report (SVR) - KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C074 DI-QCIC-81690/T Security Verification Report Security Verification Report (SVR) - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C075 DI-IPSC-81427B/T Software Development Plan (SDP) Software Development Process Description Document - KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C076 DI-IPSC-81427B/T Software Development Plan (SDP) Software Development Process Description Document - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C077 DI-MISC-80508B/T Technical Report-Study/Services Software/Hardware Requirements Specification (SHRS) - KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C078 DI-MISC-80508B/T Technical Report-Study/Services Software/Hardware Requirements Specification (SHRS) - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C079 DI-MISC-80508B/T Technical Report-Study/Services Software/Hardware Design Description (SHDD) - KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C080 DI-MISC-80508B/T Technical Report-Study/Services Software/Hardware Design Description (SHDD) - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C081 DI-MISC-80508B/T Technical Report-Study/Services Software and Programmable Logic Evaluation Report (SPLER)- KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C082 DI-MISC-80508B/T Technical Report-Study/Services Software and Programmable Logic Evaluation Report (SPLER)- Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO


of 169

CDRL NO.




C083 DI-SESS-81646B/T Configuration Audit Plan Physical Configuration Audit Plan (PCAP) - KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C084 DI-SESS-81646B/T Configuration Audit Plan Physical Configuration Audit Plan (PCAP) - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C085 DI-SESS-81022D/T Physical Configuration Audit Report and Certification

Physical Configuration Audit Report (PCAR) - KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C086 DI-SESS-81022D/T Physical Configuration Audit Report and Certification

Physical Configuration Audit Report (PCAR) - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C087 Reserved

C088 Reserved

C089 DI-EMCS-81683/T TEMPEST Test Plan TEMPEST Test Plan - KMS ECU A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C090 DI-EMCS-81683/T TEMPEST Test Plan TEMPEST Test Plan - Joint Hub ECU A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C091 DI-EMCS-81684/T TEMPEST Test Report TEMPEST Test Report - KMS ECU A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C092 DI-EMCS-81684/T TEMPEST Test Report TEMPEST Test Report - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C093 DI-QCIC-81691A/T In-Process Accounting Procedures Plan In-Process Accounting Procedures Plan - KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C094 DI-QCIC-81691A/T In-Process Accounting Procedures Plan In-Process Accounting Procedures Plan -Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C095 DI-QCIC-81722/T Quality Program Plan (QPP) Security Production Assurance (SPA) Description- KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C096 DI-QCIC-81722/T Quality Program Plan (QPP) Security Production Assurance (SPA) Description - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C097 DI-SESS-81000E Product Drawings/Models and Associated Lists

Product Drawings/Models and Associated Lists - KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO

C098 DI-SESS-81000E Product Drawings/Models and Associated Lists

Product Drawings/Models and Associated Lists - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C099 Reserved

C100 Reserved

C101 DI-MGMT-81717D/T Information Systems Security (INFOSEC) Anonymity Plan (IAP)

Information Systems Security (INFOSEC) Anonymity Plan (IAP) - KMS ECU


LT w/enclosures LTO

LT w/enclosures LTO


of 169

CDRL NO.




C102 DI-MGMT-81717D/T Information Systems Security (INFOSEC) Anonymity Plan (IAP)

Information Systems Security (INFOSEC) Anonymity Plan (IAP) - Joint Hub ECU


LT w/enclosures LTO

LT w/enclosures LTO

C103 DI-IPSC-81431A/T System/Subsystem Specification (SSS) Segment Specification - KMS ECU BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C104 DI-IPSC-81431A/T System/Subsystem Specification (SSS) Segment Specification- Joint Hub ECU BLK 16 (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C105 DI-IPSC-81431A/T System/Subsystem Specification (SSS) PTES Segment Specification - Joint Hub


LT w/enclosures LTO

LT w/enclosures LTO

C106 DI-MISC-80508B/T Technical Report-Study/Services System Level Test Readiness Review Briefing


LT w/enclosures LTO

LT w/enclosures LTO

C107 DI-MISC-80508B/T Technical Report-Study/Services Modem Certification Data Package A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C108 DI-ILSS-80739 Depot Maintenance Study N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C109 DI-SESS-81254C Request for Nomenclature (DD Form 61)


LT w/enclosures LTO

LT w/enclosures LTO

C110 DI-MISC-80508B/T Technical Report-Study/Services Installation, Operation, Support, and Maintenance Manuals


LT w/enclosures LTO

LT w/enclosures LTO

C111 DI-TMSS-80527C/T Commercial Off-The-Shelf (COTS) Manual and Associated Supplemental Data


LT w/enclosures LTO

LT w/enclosures LTO

C112 DI-ILSS-80872/T Training Materials A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C113 DI-SESS-81639A Warranty Performance Report N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C114 Reserved

C115 DI-MISC-80508B/T Technical Report-Study/Services IDE Database N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C116 DI-MISC-80508B/T Technical Report-Study/Services Reliability and Maintainability Reports N/A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C117 DI-MISC-80508B/T Technical Report-Study/Services Hardware/Software List A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C118 DI-MISC-80508B/T Technical Report-Study/Services Ports, Protocols and Services (PPS) A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

C119 DI-MISC-80508B/T Technical Report-Study/Services Cybersecurity Architecture Diagram A (E) SMC/MCEC (E) SMC/PKJ

LT w/enclosures LTO

LT w/enclosures LTO

Contract No.: FA8808-17-R-0006 Contractor: Name Exhibit: C System Item: PTES CLIN: 0003 Date: DD MMM YYYY ________________________________________________________________________________

of 169

16.0 CDRL ATTACHMENT LIST

CDRL NO.

ATTACHMENT NO.

ATTACHMENT TITLE DATED

C061 1 Sample Worksheet for Failure Modes Effect Analysis (FMEA) N/A

C061 2 Sample Worksheet for Criticality Analysis (CA) N/A

C056 3 CSDR Plan N/A

Contract No.: FA8808-17-R-0006 Contractor: Name Exhibit: C System Item: PTES CLIN: 0003 Date: DD MMM YYYY ________________________________________________________________________________

of 169

17.0 CDRL ADDRESS LIST

SMC/MCD Los Angeles Air Force Base Space and Missile Systems Center MILSATCOM Systems Directorate Advanced Development Division 483 N. Aviation Blvd. El Segundo, CA 90245-2808

SMC/MCEC Los Angeles Air Force Base Space and Missile Systems Center MILSATCOM Systems Directorate System Engineering Configuration/Data Management 483 N. Aviation Blvd. El Segundo, CA 90245-2808

SMC/MCLA Los Angeles Air Force Base Space and Missile Systems Center MILSATCOM Systems Directorate Sustainment Logistics 483 N. Aviation Blvd. El Segundo, CA 90245-2808

SMC/MCP Los Angeles Air Force Base Space and Missile Systems Center MILSATCOM Systems Directorate Program Control 483 N. Aviation Blvd. El Segundo, CA 90245-2808

SMC/MCPC Los Angeles Air Force Base Space and Missile Systems Center MILSATCOM Systems Directorate Program Control 483 N. Aviation Blvd. El Segundo, CA 90245-2808

SMC/PKJ Los Angeles Air Force Base Space and Missile Systems Center MILSATCOM Systems Directorate Contracting Division 483 N. Aviation Blvd. El Segundo, CA 90245-2808

of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16

5. CONTRACT REFERENCE

DI-SESS-81785A

4. AUTHORITY (Data Acquisition Document No.)

3. SUBTITLE

Systems Engineering Management Plan (SEMP)

2. TITLE OF THE DATA ITEM

C001

1. DATA ITEM NO.

TBD F. CONTRACTOR

FA8808-17-R-0006 E. CONTRACT/PR NO.

PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER SESS

C B. EXHIBIT

A. CONTRACT LINE ITEM NO. CLIN 0003

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)

A 8. APP CODE

LT

7. DD 250 REQ

D

9. DIST STATEMENT REQUIRED

13. DATE OF SUBSEQUENT SUBMISSION

BLK 16

11. AS OF DATE

N/A

BLK 16

12. DATE OF FIRST SUBMISSION

BLK 16

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

1. (BLK 5): 1.1.1.1.a.1; 1.1.1.1.d; 1.1.1.3.b.4; 1.1.1.6.a.6; 1.1.4.3.a; 1.1.4.4.a; 1.1.4.5.a; 1.1.4.9.b; 4.4.1.1.1.e.1 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 update 45 CD prior to the Delta Integrated Baseline Review (IBR). b. Submit final incorporating Government comments at Delta IBR. c. Review annually and 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

Page 1 of 166 Pages PREVIOUS EDITION MAY BE USED. DD FORM 1423-1, FEB 2001

of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-IPSC-81430A/T


3. SUBTITLE

Operational Concept Description (OCD)


C002

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER IPSC

C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Use/relationship. Delete the first two paragraphs entirely and replace with the following: "The Operational Concept Document (OCD) shall describe a proposed system in terms of user needs. It shall fulfill its relationship to existing systems and the ways they shall be used. The OCD shall be used to obtain consensus among the acquirer, Contractor, support and user agencies on the operational concept of a proposed system. The OCD shall focus on communicating the Contractor’s ideas to the Government Program Office and users of the system. The term “system” refers to the Protected Tactical Enterprise Service (PTES) system." b. Requirements. Paragraph 4. Content. Delete the following paragraphs entirely: (1) Paragraphs 3 through 3.5 (2) Paragraphs 4 through 4.5 (3) Paragraphs 7 through 7.3 2. (BLK 5): 1.1.1.1.c; 1.1.1.16.b; 1.3.2.1.2.a; 1.4.1.2.a; Table A-8 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for Build Decision Reviews (BDR) 5 thru8 submittal(s) only. 3. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) prior to Build Design Reviews (BDRs) 5 thru 8. b. Submit update 45 CD after all reviews to incorporate design review action item responses. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCEC

6. REQUIRING OFFICE

BLK 16


DI-MGMT-81453B/T


3. SUBTITLE

Data Accession List (DAL)


C004

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER MGMT

C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) " Contractor shall submit in a format that can be read, searched and sorted electronically by the Government.” (2) " All submissions shall be in electronic format compatible with Microsoft Suite 2010." b. Requirements. Paragraph 3. Content. Delete in its entirety and replace with the following: (1) “The Data Accession List (DAL) shall include but not be limited to a listing of non-CDRL items that make up the product baseline, peer reviews, executive reviews, independent program reviews, assessments, inspections, trade studies, memos, reports, test reports, flow diagrams, computer support software, configuration control list of all non-developmental items (NDI) software used, free and open-source software (FOSS), interim versions of software work products, as-built configuration list, plans, procedures, risk information from the risk database, Security Technical Information Guides (STIG), Original Equipment Manufacturer (OEM) test status, staffing plans, informal meeting minutes, DoD Information Technology Standards Registry (DISR) questionnaire, analysis and simulations, action items, liens, Dynamic Object Orientation Requirements System (DOORS) modules, Problem Reports, discrepancy reports, product backlogs, spring backlogs, configuration records, and all other documents generated to support the program accessible in the contractors Integrated Digital Environment (IDE).” (2) “The DAL shall be a cumulative list.” 2. (BLK 5): 1.1.1.1.b; 1.1.1.1.h; 1.1.1.1.j.1; 1.1.1.1.1.b; 1.1.1.1.1.i; 1.1.1.2.f; 1.1.2.m.3; 1.1.1.2.m.4; 1.1.3.f.1; 1.1.1.3.g; 1.1.1.3.h.2; 1.1.1.3.h.6; 1.1.1.5.c; 1.1.1.7.b; 1.1.1.11.e; 1.1.1.11.e.1; 1.1.1.12.a; 1.1.1.14.k; 1.1.2.1.d; 1.1.3.1.a.1; 1.1.3.4.c.1; 1.1.3.6.h.1; 1.1.4.8.f.1; 1.1.4.8.f.3; 1.1.4.8.f.4; 1.1.4.8.f.5; 1.3.2.1.1.2.b.3; 1.3.2.1.1.3.d; 1.3.2.1.2.c; 1.3.3.1.1.2.b.3; 1.3.3.1.1.3.d; 1.3.3.1.2.c; 1.4.1.1.2.b.3; 1.4.1.1.3.f; 1.4.1.2.c; A.1.2.2.b; A.1.3.1.b.3; A.1.3.2.c.3; A.2.1.c; A.2.1.4.a; A2.1.4.b; A.2.1.4.c; Table A-8; D.1.3.i; 3.1.3.1.b.1; 3.3.2.4.2.b; 3.3.3.4.2.a 3. (BLKs 10, 12, 13): a. Submit initial 60 calendar days (CD) after award of CLIN 0003. b. Subsequent submittals shall be submitted on the 15th of every month. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCD

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

System Integration and Test Plan (SITP)

Technical Report-Study/Services


C005

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER MISC

C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 3(c) and (d). Contents. Delete entirely and replace with the following: "The System Integration and Test Plan (SITP) shall include: i) Introduction - subsection shall cover Purpose and Objectives, SITP Document Scope and Overview, Relationship between SITP and other major program documents, System Overview, and System Integration and Test (I&T) Evaluation Approach. ii) Applicable Documents – shall include SITP applicable documents. iii) Roles and Responsibilities - shall cover responsibilities of Program Management Office (PMO), Contractor, External Stakeholders, and Integration and Test (I&T) Event Point of Contact (POC). iv) Integration Analysis - shall cover Architecture, Verification, Certification and Risk analysis to support the development of I&T events. v) System Integration and Test Process - shall cover I&T Processes, I&T Strategy, and I&T Working Groups. vi) System Integration and Test Events - shall cover System I&T Event Management, I&T Roadmap, and SITP Event Integration Plan (EIP) Report Format. vii) Integration and Test Enablers - shall cover Facilities, Support Equipment, Tools and Test Beds, Model, Simulation and Analysis, Common Test and Evaluation (T&E) Database, Government Furnished Equipment/Property/Item, Memorandum of Understanding (MOU)/Memorandum of Agreement (MOA), Anomaly and Deficiency Handling, and Training. viii) Assumptions – shall include assumptions used in the SITP. ix) Appendix - shall cover Event Integration Plans (basis for CDRL C050 System Test Plan Appendix’s Event Test Plan development). Content per Event: I&T Event Description and Objectives, dependency diagrams, test/installation configuration, connection diagrams, integration sequence diagrams, integration/execution roles and responsibilities, certifications or authorizations required and giver/receiver items. 2. (BLK 5): 1.1.1.1.k.1; 1.1.2; 1.1.2.c; 1.1.2.2.c; 1.1.2.4.a; 1.1.2.4.a.1; 1.3.2.1.2.1.b; 1.3.2.1.2.1.j; 1.3.3.1.2.1.b; 1.3.3.1.2.1.j; 1.4.1.2.1.b; A.2.1.5.b.6; Table A-8; D.3.b.i; D.3.f.iii; D.3.f.vii; D.3.j.i; 3.1.2.8.c; 3.1.2.8.d; 5.4.1.2.1.b 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only.

16. REMARKS

See Distro List

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


17. PRICE GROUP


of 169

16. REMARKS (Continued)

4. (BLKs 10, 12, 13):

a. Submit update as required 30 CD prior to Build Decision Reviews (BDR) 5 thru 8.

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

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT



Page 6 of 166 Pages DD FORM 1423-1, FEB 2001

of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-IPSC-81432A/T


3. SUBTITLE

SSDD and Solution Architecture Model

System/Subsystem Design Description (SSDD)


C006

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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.a. General Instructions. Delete in its entirety and replace with the following: "The term “document” shall mean a model to be delivered in HyperText Markup Language (HTML) format." b. Requirements. Paragraph 2.b. General Instructions. Delete in its entirety and replace with the following: "Diagrams, tables, matrices, Microsoft Word files, and other formats/presentation styles shall be acceptable additions to the document when the data required can be made more readable using these styles." c. Requirements. Paragraph 3. Format. Add: (1) "Data shall be delivered on Compact Disk.” (2) “Data shall be delivered in other formats compatible with the Contractor tools (examples include Extensible Markup Language (XML) Metadata Interchange (XMI), native tool file format, etc.) upon request from the Government.” d. Requirements. Paragraph 4. Content. System Architectural Design. Add the following at the end of the first paragraph: "The system architectural design shall include a system/segment level Solution Architecture (SA) product as delineated in the System Engineering Plan (SEP) and Institute of Electrical and Electronics Engineers (IEEE) 15288.1 Section 6.4.4.4 Architecture Definition Process Outputs, using Model Based Systems Engineering (MBSE) methodology and utilizing Commercial Off-The-Shelf (COTS) available Systems Modeling Language (SysML) compliant tools. The model includes SysML models along with architecture description documentation. Note that the descriptions in the SEP and IEEE standard include data and engineering areas not included in this DID, including but not limited to verification, integration, and risk." 2. (BLK 5): 1.1.1.2.b; 1.1.1.2.b.1; 1.1.1.2.b.2; 1.1.1.2.b.3; 1.1.3.5.b; 1.3.2.1.1.3.b; 1.3.3.1.1.3.b; 1.4.1.1.3.b; 1.4.1.1.3.d 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update as required 30 calendar days (CD) prior to Build Decision Reviews (BDR) 5 thru 8. b. Submit final incorporating Government comments 30 CD following BDRs 5 thru 8, as required. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP

of 169

SMC/MCPC

6. REQUIRING OFFICE

BLK 16


DI-MGMT-81334D/T


3. SUBTITLE

Contract Work Breakdown Structure (CWBS)


C007

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Preparation Instructions. Paragraph 1. Add: "The Contract Work Breakdown Structure (CWBS) shall be prepared in accordance with (IAW) Military Standard (MIL-STD)-881C, Appendix F, and the Office of the Secretary of Defense (OSD) Deputy Director, Cost Assessment (DDCA) and OSD Acquisition, Technology and Logistics (AT&L) Performance Assessments and Root Cause Analyses (PARCA) Director-approved contract Cost and Software Data Reporting (CSDR)/Earned Value Management (EVM) Co-Plan (Attachment 3)." b. Preparation Instructions. Add: "Routine reporting shall be at the lowest level of the Government provided Work Breakdown Structure (WBS). More detailed reporting of the CWBS shall be required for lower-level elements such as hardware and software items that address high-risk, high-value, or high-technical-interest areas of a program." 2. (BLK 5):

1.1.3.3.a; 1.1.3.4.d

3. (BLK 8): a. Government approval shall be by contract modification.

b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): a. Submit draft 30 calendar days (CD) after CLIN 0003 award. b. Submit update 30 CD after any revisions to the CWBS.

c. Submit final 30 CD prior to Delta Integrated Baseline Review (IBR). d. Updates as required or by Procurement Contracting Officer (PCO) direction. e. The CWBS Dictionary shall be submitted electronically using the CSDR Submit-Review System. Data submitters shall register through the Defense Cost and Resource Center (DCARC) website (http://cade.osd.mil) and possess a Department of Defense (DoD)-approved External Certification Authority(ECA) digital certificate from a third party vendor to obtain a DCARC Portal account and be authorized to upload CSDR content.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-SESS-81757A/T


3. SUBTITLE

Design Review Information Package (DRIP)


C008

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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.0. Contents. Add: (1) "A Reliability and Maintainability (R&M) Predictions Report shall be included with the System Preliminary Design Review (PDR) and the System Critical Design Review (CDR) Design Review Information Package (DRIP)." (2) "The R&M Predictions Report shall include: i) System configuration identification. ii) Assumptions used in the prediction process. iii) Documentation or cross-reference to the data used in performing R&M predictions, including the following: (a) Hardware parts description, including manufacturer part number and manufacturer Commercial and Government Entity (CAGE) if applicable (b) Software Configuration Items description (c) Failure rate data source and assumed operational loads (d) Failure distributions (e) Constraints (f) Item definition, including assembly indenture (g) Service use profile (h) R&M block diagrams and mathematical models (i) Failure Modes, Effects, and Criticality Analysis (FMECA) (j) Environmental data, including life cycle loads (e.g. engineering mechanical, electrical, and thermal analysis) (k) Environmental and operating Stress data, including physics of failure analyses iv) Description of system Built-In-Test (BIT), maintenance and support concepts. v) Description of data developed to support system age-reliability relationships (particularly for the identification of life limits) for Reliability-Centered Maintenance (RCM) analysis to develop appropriate life limits or maintenance tasks. vi) Description of the R&M prediction procedures used, including methodology, models and tools. vii) Results of the analysis performed for field reliability (mission and logistics), maintainability and BIT performance of similar and analogous items operating in the same expected environment. viii) Applicable failure rates, failure distributions, failure rate adjustment factors, and reliability variables used in the calculation of each configuration item.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) ix) The source(s) of the data and the evaluated validity of data used in the reliability predictions. x) The operating and environmental stress factors and ratios, along with other factors used in determining part failure rates shall be specified in in the report and shall be individually identified as estimated (i.e. documented subject matter expert (SME) engineering opinion), calculated (i.e. reliability analysis from comparable systems), and measured (i.e. historical reliability from predecessor systems and shall include test and field data). xi) How the accumulated operating hours were determined when using field experience data for similar items in a like environment. xii) The reliability prediction for each subdivision of the system breakdown structure for each mission, mode of operation, and periods of non-operation and storage from an items final factory acceptance through its terminal expenditure including removal from inventory. xiii) Maintainability predictions shall be identified for each associated level of maintenance, including both unscheduled and scheduled maintenance, and shall also include repair time source data for the prescribed level of maintenance. xiv) BIT predictions of the overall system level BIT fault detection, and fault isolation for the overall system. xv) Risk assessment and mitigation plans for each configuration items R&M, and BIT value based upon the data source and maturity of design. xvi) Conclusions and recommendations based upon the R&M predictions that coincide with the phase of item development and shall specify any indication of the systems R&M status. All R&M deficiencies identified shall be included and shall also contain the course of action to be taken to resolve each deficiency." b. Requirements. Paragraph 2.9. Section 11 – Functional Configuration Audit (FCA). Add: “Institute of Electrical and Electronics Engineers (IEEE) 15288.2, Section 6.8, shall be referenced for the detailed criteria to be addressed for each review and audit. FCA detailed criteria shall include both hardware configuration items (CIs), software CIs, and Commercial Off-The-Shelf (COTS) environment. IEEE 15288.2,Sections 5.8 and 7.8 shall be used as compliance.” c. Requirements. Paragraph 2.10 Section 12 – Physical Configuration Audit (PCA). Add: “IEEE 15288.2, Section 6.11, shall be referenced for the detailed criteria to be addressed for each review and audit. PCA detailed criteria to include both hardware CIs, software CIs, and COTS environment. IEEE 15288.2, Sections 5.11 and 7.11 shall be used as compliance.” 2. (BLK 5): A.3.1.a.3; 3.1.1.10.b.2; 3.1.1.10.b.3; 3.1.2.5.a.4; 3.3.1.1.3.a.4 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): a. Submit 30 calendar days (CD) prior to Build Decision Reviews (BDR) 5 thru 8. b. Submit 45 CD prior to Functional Configuration Audit (FCA) for each additional Build. c. Submit 45 CD prior to Physical Configuration Audit (PCA) for each additional Build. d. Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE PTES Software Development Plan (SDP)



C010

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace with the following: (1) "Contractor's format is acceptable." (2) "All submissions shall be in electronic format compatible with Microsoft Suite 2010." b. Requirements. Paragraph 3. Contents. Delete in its entirety and replace with the following: (1) “The Contractor shall use data item description (DID) DI-MISC-80508B in lieu of DID DI-IPSC-81427A.” (2) "Appendix H.1 of Space and Missile Systems Center (SMC)-S-012 (Software Development) shall be followed for paragraph number, titles, and content of the Software Development Plan (SDP). Government Statement of Work (SOW), Appendix A, Agile Project Management shall be used to plan and manage the Agile development effort." (3) "The SDP shall describe the Contractor’s plans for conducting a software development effort. The SDP provides insight into, and a tool for monitoring the processes to be followed for software development, the methods to be used, the approach to be followed for each activity, and project schedules, organization, and resources." (4) “The SDP shall describe the contractor’s approach, tools and CM process to support continuous integration and automated testing at unit, segment and system level.” (5) "The SDP shall be a single integrated plan with hyperlinks to the team’s processes to ensure effective work product/component transition across process and tool(s) interfaces and organizational boundaries for the software development activities for all software team members throughout the Protected Tactical Enterprise Service (PTES) development for all software items in the following categories of software (including the software portion of firmware) except KMS ECU and Joint Hub ECU: i) ground operations software (e.g., mission planning, mission support, database software; infrastructure (including cybersecurity platform and services); and ii) other software (e.g., software for training; modeling, simulation, and other analysis tools; database support, automatic test equipment, test facility and environment, and maintenance) to be: (a) delivered to the customer; or (b) used in satisfying, verifying, or validating requirements (c) used in performing or supporting operations; or (d) used in performing or supporting sustainment" 2. (BLK 5): 1.1.1.3.b.4; 1.1.1.3.c.4; 1.1.1.3.e; 1.1.1.3.e.1; 1.1.1.3.f; A2.1.9.b; Table A-8; A.4.2.d.1 2.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for updates and final submittals only. 3. (BLKs 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.3.c.1; Table A-8


DI-MISC-80508B/T


3. SUBTITLE

Software Architecture Description (SAD)



C011

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace with the following: (1) "Contractor's format is acceptable. Contractors format is acceptable for the software architecture model if delivered as an Appendix to the main document." (2) " All submissions shall be in electronic format compatible with Microsoft Word 2010 and contain no embedded file objects." b. Requirements. Paragraph 3. Content. Delete in its entirety and replace with the following: "Appendix H.2 of Space and Missile Systems Center (SMC)-S-012 shall be followed for paragraph number, titles, and content except for the following: i) Delete paragraphs 5h(2), 5h(3), 5h(4), 5i(2), 5i(3), 5i(4), 5l(1) through 5l(6), 5o(5), 5o(6), 6.x h(2), 6.x h(3), 6.x h(4), 6.x l(1) through 6.x l(6), 6.x o(5), and 6.x o(6) entirely. ii) Delete the contents of paragraphs 4.2, 4.4, 5e, 5k, 5m, 5q, 6.x e, 6.x k, and 6.x q entirely and mark as RESERVED. iii) Delete the content of paragraph 6.x.m in its entirety and replace with the following: “Description shall include how the software item architectural design supports automated testing at unit, sub-system and system level.” iii) Paragraph 4.3. Delete the sentence "This paragraph shall describe any changes to software architecture decisions as a result of these evaluations." iv) Paragraphs 5 and 6. Add the following sentence before the last sentence: "In lieu of diagrams in the text, the software architecture model, along with a user guide on how to view information required in this document, shall be delivered electronically in a Contractor-defined, Government-approved format as an Appendix to this document." v) Paragraph 5b. Delete in its entirety and replace with the following: "Description shall include how the software architecture integrates into the system architecture." vi) Paragraphs 5d and 6.x d. Replace the phrase "their impact" with "these requirements' impact." vii) Paragraph 5f. Delete in its entirety and replace with the following: "A description, expressed in a set of use cases, or equivalent, of how the software shall interact with the users, with external systems, and other elements of the system to meet system and software requirements, including use cases, or equivalent, for nominal and off-nominal scenarios." viii) Paragraphs 5g and 6.x g. Delete entirely and replace with the following: "Descriptions of the following software architectural views, including both diagrams and detailed textual descriptions. All diagrams shall be accompanied by descriptions of the functionality and behavior provided by the components. This paragraph shall provide the criteria used to determine consistency among the architectural views. The views shall include the following information:" ix) Paragraphs 5g(1) and 6.x g(1). Add the phrase "to the system" to the first sentence. x) Paragraph 5l. Delete in its entirety and replace with the following: "Description shall include how and where the software architecture supports cybersecurity

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) requirements, including security categorization of data exchanges, allocated security controls and control enhancements, and security accreditation." xi) Paragraph 5n. Delete in its entirety and replace with the following: "Description shall include how and where the software architecture supports system safety and reliability, maintainability, and availability (RMA)." xii) Paragraph 5o. Delete in its entirety and replace with the following: "Description shall include how and where the software architecture supports the human systems interface to account for human capabilities and limitations in the operations, maintenance, and support of the system. This description shall include:" xiii) Paragraphs 5p and 6.x p. Replace the term "system increment" with "software release." xiv) Paragraph 6.x.b. Delete in its entirety and replace with the following: “Description shall include how the software item architecture integrates into the higher level software architecture." xv) Paragraph 6.x f. Delete in its entirety and replace with the following: "A description, expressed in a set of use cases, or equivalent, shall describe how the software item will interact with the users, with external systems, with other software items, and with other elements of the system to meet system and software requirements, including use cases, or equivalent, for nominal and off-nominal scenarios." xvi) Paragraph 6.x n. Delete in its entirety and replace with the following: “Description shall include how and where the software item architecture supports system safety and system reliability, maintainability, and availability (RMA)." xvii) Paragraph 6.x o. Delete in its entirety and replace with the following: "Description shall include how and where the software item architecture supports the human systems interface to account for human capabilities and limitations in the operations, maintenance, and support of the system. This description shall include:" 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. Agile: (1) Submit update 10 CD prior to Build Decision Reviews (BDR) 5 thru 8. (2) Submit final with the release of software for Build 5 thru 8. (3) Submit update 45 CD prior to software operational Release 2. (4) Update as required or by Procurement Contracting Officer (PCO) direction. b. Non-Agile: (1) Submit update 30 CD after Government approval of Class 1 Engineering Change Proposal (ECP)/Contract Change Proposal (CDRL C041). (2) Update as required or by PCO direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.3.c.2; Table A-8


DI-IPSC-81437A/T


3. SUBTITLE

Database Design Description (DBDD)


C012

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Replace all references to "Computer Software Configuration Item (CSCI)" with "Software Item (SI)." b. Requirements. Paragraph 3. Format. Add: "All submissions shall be in electronic format compatible with Microsoft Suite 2010." 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. Agile: (1) Submit update with Builds 5 thru 8. (2) Submit update 45 calendar days (CD) prior to software operational Release 2. (3) Update as required or by Procurement Contracting Officer (PCO) direction. b. Non-Agile: (1) Submit update 30 CD after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CCP)(CDRL C041). (2) Update as required or by PCO direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.3.c.3; 1.4.1.1.2.a.2


DI-IPSC-81433A/T


3. SUBTITLE Software Requirements Specification (SRS) - Joint Hub

Software Requirements Specification (SRS)


C013

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Use, Relationships. Add: "The Software Requirements Specification (SRS) shall be used as the basis for design and requirements testing of a system or subsystem." b. Requirements. Paragraph 4. Content. Subparagraph 1.3. Document overview. Add: "The SRS shall cover all deliverable software items in the Protected Tactical Enterprise Service (PTES) Hub." c. Requirements. Paragraph 4. Content. Subparagraphs 3.3.x.f and 3.3.x.f.4. Project-unique identifier of interface. Add: "Shall include requirements for abnormal conditions, as appropriate.” d. Requirements. Paragraph 4. Content. Subparagraph 3.4. Software Item (SI) internal interface requirements. Add: "Shall include requirements for abnormal conditions, as appropriate.” e. Requirements. Paragraph 4. Content. Subparagraph 3.7. Safety requirements. Add: "Shall include requirements for abnormal conditions, as appropriate.” f. Requirements. Paragraph 4. Content. Subparagraph 3.11. Software quality factors. Add: "Shall include requirements for abnormal conditions, as appropriate. g. Replace all references to "traceability" with "bi-directional traceability." h. Replace all references to “Computer Software Configuration Item (CSCI)” with “Software Item (SI).” i. The term "system" shall be interpreted to mean "subsystem" as applicable. 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. Non-Agile: (1) Submit final 30 CD prior to software operational release for Builds 5 thru 8 and Release 2. (2) Submit update 30 CD after Government approval of Class 1 Engineering Change Proposals (ECPs)/Contract Change Proposal (CCP) (CDRL C041). (3) Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE 1.

5. CONTRACT REFERENCE BLK 16

DI-IPSC-81438A/T


3. SUBTITLE

Software Test Plan (STP)


C014

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 1.1. Identification. Add the following to the end of the paragraph: "The Contractor shall deliver one STP for the overall system and 2 additional Software Test Plan (STP) Appendices, one for each of the following subsystems: i) Mission Management Scheduling (MMS) ii) Key Management System (KMS)" b. Requirements. Paragraph 1.1. Identification. Add the following paragraph: "1.1.1. The STP shall address all applicable types of Developmental Test and Evaluation (DT&E) for the life of the system. Subsystem STP Appendices need not duplicate information in the overall system STP; they shall focus on DT&E planning unique to the respective subsystem. Subsequent references to "system" in the data item description (DID) and DID tailoring refer to either the system or subsystem, as applicable for the STP or Appendix." c. Requirements. Paragraph 1.4. Relationship to other plans. Delete the paragraph in its entirety and replace with the following: "This paragraph shall describe the relationship of the STP to any related project management plans." d. Requirements. Paragraph 3. Software test environment. Add the following to the end of the paragraph: "Since each STP shall address multiple DT&E events, paragraphs in this section shall be written in a generic fashion covering either the overall system or the specific subsystem, as applicable to the particular STP." e. Requirements. Paragraph 4.1.4. Test Progression. Delete entirely. f. Requirements. Paragraph 4.1.5. Data recording, reduction, and analysis. Add the following to the end of the paragraph: "Since the STP shall address multiple DT&E events, paragraphs in this section shall be written in a generic fashion covering either the overall system or the specific subsystem, as applicable to the particular STP or Appendix." g. Requirements. Paragraph 4.2. Planned Tests. Delete this paragraph in its entirety and replace with the following: "This paragraph shall generically describe the scope of planned testing, addressing all types of applicable DT&E. For sustainment testing, this section shall list and describe any applicable reusable regression tests and describe the process by which they are selected for use for evaluation of system modifications." h. Requirements. Paragraph 4.2.x.y. Project-unique identifier of a test. Add: (1) ",or equivalent" after "as specified in the requirements specification." (2) ",or equivalent" after "SI requirements." i. Requirements. Paragraph 5. Test Schedules. Delete "This section shall contain or reference the schedules for conducting the tests identified in this plan" and replace with "This section shall provide generic test schedule and process information covering typical sequence and duration of events related to the DT&E process. The described process and generic schedule information shall include events such as test requests; test procedure development, coordination,

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) and approval; peer reviews; quality assurance (QA) participation; configuration management/control; dry-runs; test event notification to the Government/witness requests; runs for record; test data reduction and analysis; report development, coordination, and approval; etc.; as applicable." j. Requirements. Paragraph 6. Requirements traceability. Add: (1) ", or equivalent" after "all instances of SI requirements." (2) "all" after "The traceability shall cover." b. Replace all references to “Computer Software Configuration Item (CSCI)” with “Software Item (SI).” 2. (BLK 5): 1.1.1.3.c.5; A.1.1.1.c; A.1.1.2.b; 2.1.7.b.2; Table A-8 3. (BLKs 10, 12, 13): a. Agile: (1) Submit initial 30 calendar days (CD) prior to delivery of operational Release 2. (2) Submit updates 7 CD prior to the delivery of Builds 5 thru 8. (3) Submit updates incorporating Government comments as required or by Procurement Contracting Officer (PCO) direction. b. Non-Agile: (1) Submit final with software operational Release 2. (2) Update as required or by PCO direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.3.c.6


DI-IPSC-81439A/T


3. SUBTITLE

Software Test Description (STD)


C015

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Use, Relationships. Add: "Software Test Description (STD) shall describe the test preparations, test cases, test procedures, and test scripts to be used to perform qualification testing of a Software Item (SI) or a software system or subsystem." b. Requirements. Paragraph 2. General Instructions. Add: (1) "There shall be one or more STD for each software event." (2) "A unified STD shall be provided for multiple software items according to the integration and verification strategy in the Software Test Plan (STP)." (3) "STDs shall cover all deliverable software items." c. Requirements. Paragraph 3. Format. Add: "All submissions shall be in an electronic format compatible with Microsoft Word 2010." d. Requirements. Paragraph 4.x.y.6. Test procedure. Add "and test script" after each instance of "test procedure." c. Replace all references to “Computer Software Configuration Item (CSCI)” with “Software Item (SI).”

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. Agile:

(1) Submit final 7 CD prior to the delivery of software Builds 5 thru 8.

(2) Submit update 30 CD prior to delivery of Release 2..

(3) Update as required or by Procurement Contracting Officer (PCO) direction. b. Non-Agile: (1) Submit final with software operational release for Builds 5 thru 8 and Release 2. (2) Update as required or by PCO direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.3.c.7; A.1.c.11; A.4.2.a


DI-IPSC-81440A/T


3. SUBTITLE

Software Test Report (STR)


C016

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Use, Relationships. Add: "The Software Test Report shall be used to analyze and record test results of Software Item requirement testing at the Segment level. The word test shall include all verification methods (i.e., Inspection, Analysis, Demonstration, and Test)." b. Requirements. Paragraph 2. General instructions. Add: "A unified System Test Report shall be provided for multiple software items in accordance with (IAW) the integration and verification strategy." c. Requirements. Paragraph 3. Format. Add: "All submissions shall be in electronic format compatible with Microsoft Word 2010." d. Requirements. Paragraph 4. Content. Add: (1) "System Test Reports shall cover all deliverable software items." (2) “Replace all references to “Computer Software Configuration Item (CSCI)” with “Software Item (SI).” 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. Agile: (1) Submit 5 calendar days (CD) after delivery of Builds 5 thru 8. (2) Update as required or by Procurement Contracting Officer (PCO) direction. b. Non-Agile: (1) Submit 10 CD after each test event. (2) Update as required or by PCO direction. c. Submit final incorporating Government comments 30 CD prior to delivery of software operational Release 2.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.3.c.8


DI-IPSC-81443A/T


3. SUBTITLE

Software User Manual (SUM)


C017

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 instructions. Add: "Electronic deliveries shall be stored in an Integrated Digital Environment (IDE) in a format compatible with Microsoft Office Suite 2010 and converted to Portable Document Format (PDF) so as to be readable by Adobe Acrobat Reader before printing on paper for submission to the Government. The Government shall have complete access to the CMS. The CMS is chosen and licensed by the Contractor." b. Requirements. Paragraph 3. Format. Delete in its entirety and replace with the following: "Contractor's format is acceptable." c. Requirements. Paragraph 4.1.1. Equipment familiarization. Add: "Use of combinations of special keys such as ESC, Alt, Ctrl, Fn with other keys to perform shortcut operations on the system being controlled from a keyboard for emergency purposes (e.g., shutdown and transfer control to manual mode) and general usage." d. Requirements. Paragraph 4.1.3. Installation and setup. Add: "In addition, the Contractor shall include a description of any Commercial Off-The-Shelf (COTS) /Government-Off-The-Shelf (GOTS) software that will be installed along with instructions for use with latest stable release, and contents of configuration files shall be provided." e. Replace all references to "Computer Software Configuration Item (CSCI)" with "Software Item (SI)." 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): Agile and Non-Agile: (1) Submit draft 10 calendar days (CD) prior to delivery of software builds 5 thru 8. (2) Submit update 30 CD prior to delivery of software operational Release 2. (3) Submit final incorporating Government comments with delivery of software operational Release 2. (4) Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.3.c.9


DI-IPSC-81441A/T


3. SUBTITLE

Software Product Specification (SPS)


C018

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 instructions. Add: (1) "All submissions shall be stored in the Integrated Digital Environment (IDE).” (2) “All submissions shall be compatible with International Business Machine (IBM)Rational Dynamic Object Oriented Requirements System (DOORS).” (3) “All submissions shall be compatible with Microsoft Office Suite 2010, and shall be submitted in Portable Document Format (PDF).” (4) "The Contractor shall organize a single Software Product Specification (SPS) to cover a group of software items rather than a separate SPS for each software item." b. Requirements. Paragraph 3.1. Executable Software. Add: The Contractor shall provide the uniform resource locator (URL), and the directory/sub-directory locations of the executable software on virtual machines of Government enterprise computing platforms.” c. Requirements. Paragraph 3.2. Source files. Add: "The Contractor shall provide the URL, and the directory/sub-directory locations of the source files on virtual machines of Government enterprise computing platforms for source files, Commercial Off-The-Shelf (COTS) , Government-Off-The-Shelf (GOTS), and Non-Developmental Items (NDI) files.” d. Requirements. Paragraph 4. Content. Subparagraph 1.3. Document overview. Add: "The SPS shall cover all deliverable software items." e. Requirements. Paragraph 4. Content, Subparagraph 3.2. Source files. Add: "The source code shall be delivered with all comments intact." f. Requirements. Paragraph 4. Content. Subparagraph 5.1. "As built" software design. Replace "Software Design Description (SDD)" with "Software Architecture Description (SAD)" and replace "Interface Design Description (IDD)" with "Interface Control Document (ICD)" and "IDD" with "ICD." g. Requirements. Paragraph 4. Content. Add: "SPS shall contain the executable software, source files, and software support information, including as-built design information and compilation, build, and modification procedures, for a Software Item (SI). The SPS shall be used to order the executable software and source files for a software item and is the primary software support document for the software item." i. Requirements. Paragraph 5.2 Compilation/build procedures. Add "and build scripts" after "the compilation/build process." j. Replace all references to “Computer Software Configuration Item (CSCI)” with “Software Item (SI).”

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) 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. Agile: (1) Submit draft with delivery of Builds 5 thru 8. (2) Submit final with delivery of software operational release for Builds 5 thru 8 and Release 2. (3) Update as required or by Procurement Contracting Officer (PCO) direction. b. Non-Agile: (1) Submit draft with software operational release for Builds 5 thru 8 and Release 2. (2) Submit final incorporating Government comments 10 calendar days (CD) after receiving comments. (3) Update as required or by PCO direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.3.c.10


DI-IPSC-81442A/T


3. SUBTITLE

Mission Management System to Key Management System (MMS - KMS) SVD

Software Version Description (SVD)


C019

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Use, Relationships. Add: "The Software Version Description (SVD) shall identify and describe a software version consisting of one or more Computer Software Configuration Items (CSCIs). It shall be used to release, track, and control software versions." b. Requirements. Paragraph 2. General Instructions. Add: (1) "The term "version" shall be applied to the initial release of the software, to a subsequent release of that software, or to one of multiple forms of the software released at approximately the same time (for example, different sites)." (2) "The SVD shall be used when the Contractor is tasked to identify and record the exact version of software to be delivered to a user, support, or other sites. It shall be used by the acquirer, the software team and the users." c. Requirements. Paragraph 3. Format. Add: "All submissions shall be in an electronic format compatible with Microsoft Word 2010." d. Requirements. Paragraph 4. Content. Subparagraph 3.2. Inventory of Software Contents. Add: "and all computer files including any Build-Scripts and Non-Developmental Items" after "including any Commercial-Off-The Shelf (COTS) Items." e. Replace all references to “Computer Software Configuration Item (CSCI)” with “Software Item (SI).” 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. Agile: (1) Submit draft with delivery of Builds 5 thru 8. (2) Submit update 30 calendar days (CD) prior to software operational release for Builds 5 thru 8 and Release 2. (3) Submit final incorporating Government comments with delivery of each software operational for Builds 5 thru 8 and Release 2. (4) Update as required or by Procurement Contracting Officer (PCO) direction. b. Non-Agile: (1) Submit 30 CD prior to each software operational release. (2) Submit update incorporating Government comments with delivery of software operational Release 2. (3) Submit final 30 CD prior to final transition to sustainment. (4) Update as required or by PCO direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCPC

6. REQUIRING OFFICE

1.1.1.3.c.11; 1.1.3.4.f


DI-MGMT-82035/T


3. SUBTITLE

DD Form 3026-1 (SDR) and DD Form 3026-3 (ERP SDR)

Software Resources Data Reporting: Development and Maintenance Reports and Data Dictionary


C020

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Use/relationship. Paragraph 1.1.2. Delete entirely. b. Requirements. Paragraph 2.5.1. Replace “…SRDR shall be submitted for each release" with “an Software Resources Data Reporting: Development and Maintenance Report and Data Dictionary shall be submitted for each software build.” c. Requirements. Paragraph 2.4.1.1. Add: "The approved Excel formats will be provided by the Government." d. Preparation Instructions. Paragraph 3.1.1. Delete in its entirety and replace with the following: "The Software Resources Data Report (SRDR) shall be prepared in accordance with (IAW) DI-MGMT-82035, as tailored, and the Office of the Secretary of Defense (OSD) Deputy Director, Cost Assessment (DDCA) and OSD Acquisition, Technology and Logistics (AT&L) Performance Assessments and Root Cause Analyses (PARCA) Director-approved contract CSDR/Earned Value Management (EVM) Co-Plan." e. Preparations Instructions. Paragraph 3.3.2.5.7. Add: "Agile development shall also require DD Form 3026-1 along with DD Form 3026-3." f. Preparation Instructions. Paragraph 3.3.2.6.4. Delete in its entirely and replace with the following: "Enterprise Resource Planning (ERP) systems and systems reporting Agile development measures shall be required to use Format 3, the Enterprise Resource Planning Software Development Report." 2. (BLKs 10, 12, 13): a. Submit initial 60 calendar days (CD) after CLIN 0003 award. b. Submit update 60 CD after completion of software Builds 5 thru 8. c. Submit final 60 CD prior to contract end. d. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.3.c.12; 1.1.1.14.h; A.1.4.2.a


DI-MISC-80508B/T


3. SUBTITLE Software and System Measurement Report (SSMR)



C021

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 3(c)(2). Contents. Delete entirely and replace with the following: "Software and System Measurements. Software and System Measurements Report, at a minimum, shall include these measurements by software item, and by build in accordance with (IAW) Statement of Work (SOW) Appendix A, 1.4.2, Measurements. Include additional measures from Systems Engineering Management Plan (SEMP)(CDRL C001)and Software Development Plan (SDP)(CDRL C076) that provide visibility into Contractor’s quality indicators." b. Delete all references to "DTIC." 2.(BLKs 10, 12, 13): a. Agile: (1) Submit initial 10 calendar days (CD) after end of first Sprint. (2) Submit updates 10 CD after each Sprint. (3) Update as required or by Procurement Contracting Officer (PCO) direction. b. Non-Agile: (1) Submit initial 10 CD after end of first month. (2) Submit updates 10 CD after the end of each month. (3) Update as required or by PCO direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCD

6. REQUIRING OFFICE

1.1.1.3.c.13


DI-IPSC-81448B/T


3. SUBTITLE

Firmware Support Manual (FSM)


C022

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Use, Relationship. Replace "other firmware devices" with "Field Programmable Gate Array (FPGA) and other firmware devices" at the end of the first paragraph. b. Requirements. Paragraph 3. Format. Add: "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." 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 final document that includes as-built design 30 calendar days (CD) prior to the delivery of Release 2. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-IPSC-81429A/T


3. SUBTITLE

Software Transition Plan (STrP)


C023

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 3. Format. Add: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." 2. (BLK 5): 1.1.1.3.c.14; 1.3.3.2.c; 1.4.7.1.f; A.4.3.b.1; A.4.3.b.2; 3.1.4.13.c 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Agile: (1) Submit final 30 calendar days (CD) before end of Builds 5 thru 8. (2) Update as required or by Procurement Contracting Officer (PCO) direction b. Non-Agile: (1) Submit draft 60 CD prior to transition to operations. (2) Submit final 30 CD prior to transition to operations. (3) Update as required or by PCO direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.3.c.15; A.1.3.1.a.1


DI-MISC-80508B/T


3. SUBTITLE Agile Product Roadmap/Product Backlog



C024

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

1. (BLK4): a. Delete all references to "DTIC." b. Requirements. Paragraph 2. Format. Delete in its entirety and replace with the following: "Contractor’s format is acceptable." c. Requirements. Paragraph 3(b). Contents. Add the following to the end: "For data in a database or other alternative form, this information shall consist of an internal or external table of contents containing pointers to, or instructions for accessing." d. Requirements. Paragraph 3(2). Contents. Delete in its entirety and replace with the following: "Inventory - This paragraph shall contain the complete product backlog, User Stories yet to be completed, tracking database and associated data used to track capabilities, features, and user stories. Product Roadmap is to include prioritized Features going into each Build mapped to SSS. Product Backlog includes prioritized Features and User Stories mapped to SSS." e. Requirements. Paragraph 3(3). Contents. Delete in its entirety. 2. (BLKs 10, 12, 13): a. Submit 5 calendar days (CD) before end of contract period of performance. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

Software Licenses and Warranties



C025

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace with: (1) "Contractor's format is acceptable." (2) "All submissions shall be in electronic format compatible with Microsoft Suite 2010." b. Requirements. Paragraph 3. Content. Delete in its entirety and replace with the following: "The report shall include a complete and serialized listing of all warranties and licenses applicable to the delivery order. The warranty listing shall identify the specific equipment and period of warranty applicable to the equipment." 2.(BLK 5): 1.1.1.3.j; 1.1.1.3.j.1; 1.1.1.12.c; 3.1.4.16.g.3 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): a. Submit the complete serialized listing of all warranties and licenses and documentation applicable to the delivery 90 calendar days (CD) after Procurement Contracting Officer (PCO) approval to proceed with procurement and installation. b. Submit all warranties, documentation and equipment and software licenses and updated serialized listing, if necessary, 7 CD prior to Government Acceptance Testing. The original equipment warranties and licenses shall be submitted/transferred/provided to the Government PCO. c. Submit all open warranties and documentation applicable to any spares and equipment/software installed during the ICS performance period 7 CD prior to the end of the ICS period of performance (POP). Provide original warranties that remain open at FOC declaration to Government PCO. d. Submit all equipment/software licenses and documentation for equipment/software installed during the ICS period 7 CD after the installation of the applicable equipment/software. Submit/transfer original equipment/software licenses to the Government PCO on the day that the equipment is installed. e. Update as required or by PCO direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-IPSC-81431A/T


3. SUBTITLE

PTES System Specification

System/Subsystem Specification (SSS)


C026

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 Instructions. Add: (1) "Main volume shall be unclassified with reference to a separate classified Appendix." (2) "Classified portions of this data item shall be submitted in accordance with (IAW) Department of Defense form DD-254 and the instructions contained in the CDRL instructions of this document." b. Requirements. Paragraph 3. Format. Add: "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." c. Requirements. Paragraph 4.a. Title page or identifier. Add: "Revision Control Page. The revision control page shall list the following information: i) Each revision letter ii) Date of each revision iii) Pages affected by each revision and a description of the change(s)" 2. (BLK 5): 1.1.1.4.a; 1.1.2.3.c; 1.3.2.1.2.1.f; 1.3.3.1.2.1.f; 3.1.2.4.b; 3.1.2.5.a.1; 3.3.1.1.3 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CDRL C041) and Specification Change Notice (SCN) (CDRL C028) as required. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

Requirements Traceability Matrix (RTM)



C027

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace with the following: (1) "Format shall be compatible with International Business Machine (IBM) Rational Dynamic Object Oriented Requirements System (DOORS)." (2) "Submittal DOORS format shall be consistent with Protected Tactical Enterprise Service (PTES) System Program Office (SPO) schema to be coordinated with Government." b. Requirements: Paragraph 3. Contents. Delete in its entirety and replace with the following: (1) "The PTES Requirements Traceability Matrix (RTM) shall contain all bi-directional traceability information existing between requirements in the following documents: i) PTES System Technical Requirements Document (TRD) ii) Terminal Modem (TM) Line Replaceable Unit (LRU) TRD iii) MMS-Terminal Modem (TM) LRU Interface Control Document (ICD) iv) Protected Tactical Waveform Interface Control Document (ICD) v) Any Contractor developed ICDs and/or specifications" (2) "Each requirement shall be identified by its unique identifier, as established in the document which contains the requirement." 2. (BLK 5): 1.1.1.4.b; 1.1.1.4.b.1; 1.3.2.1.2.1.e; 1.3.2.1.2.1.e.1; 1.3.2.1.2.1.l; 1.3.3.1.2.1.e; 1.3.3.1.2.1.e.1; 1.4.1.2.1.e; A.1.c.12 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update with each Test Report (CDRL C052). b. Submit final 30 CD prior to BDRs 5 thru 8. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCEC

6. REQUIRING OFFICE

1.1.1.10.a.3


DI-SESS-80643D/T


3. SUBTITLE

Specification Change Notice (SCN)/Interface Revision Notice (IRN)

Specification Change Notice (SCN)


C028

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Use/relationship. Add: (1) "This data item shall be used to manage, record, and distribute approved changes the contract baseline specifications and/or interface control documents (ICDs).” (2) “An Interface Revision Notice (IRN) shall be used in lieu of a Specification Change Notice (SCN) for Interface Control Documents (ICDs)." b. Requirements. Paragraph 2. Format. Add:

(1) "Contractor's format is acceptable." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010.”

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. SCNs/IRNs shall be submitted after Government approval of the proposed (Engineering Change Proposal – CDRL C041) changes. b. Submit authenticated document 30 calendar days (CD) after Government approval is received. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-SESS-81248B/T


3. SUBTITLE

Mission Management System to Key Management System (MMS - KMS) ICD

Interface Control Document (ICD)


C029

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 2. Format. Add: (1) "Contractor's format is acceptable." (2) " All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." 2. (BLK 5): 1.1.1.4.e; Table 1-1; 1.3.2.1.1.2.a.2.ii; 1.3.3.1.1.2.a.2.ii 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) prior to Build Decision Reviews (BDR) 5 thru 8. b. Submit update 45 CD after each review, as required to incorporate review action item responses. c. Submit final that includes as-built design 60 CD prior to Release 2. d. Submit update 30 CD after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CCP)(CDRL C041) as required. e. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-SESS-81248B/T


3. SUBTITLE

Mission Management System to Joint Hub (MMS -Joint Hub) ICD



C030

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 2. Format. Add: (1) "Contractor's format is acceptable." (2) " All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." 2. (BLK 5): 1.1.1.4.e; Table 1-1; 1.3.2.1.1.2.a.2.ii; 1.4.1.1.2.3.a.ii 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CCP)(CDRL C041) as required (associated with approved Interface Revision Notices (IRN) (CDRL C028) to include IRNs associated with Builds 5 through 8). b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-SESS-81248B/T


3. SUBTITLE Mission Management System to Key Loading and Initialization Facility (MMS KLIF) ICD



C031

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 2. Format. Add: (1) "Contractor's format is acceptable." (2) " All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." 2. (BLK 5): 1.1.1.4.e; Table 1-1; 1.3.2.1.1.2.a.2.ii; 1.3.3.1.1.2.a.2.ii 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 45 calendar days (CD) after each review, as required to incorporate review action item responses. b. Submit final that includes as-built design 60 CD prior to Release 2. c. Submit update 30 CD after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CCP)(CDRL C041) as required. d. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-SESS-81248B/T


3. SUBTITLE Key Management System to End Cryptographic Unit (KMS-ECU) ICD



C032

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 2. Format. Add: (1) "Contractor's format is acceptable." (2) “All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader.” 2. (BLK 5): 1.1.1.4.e; Table 1-1; 1.3.3.1.1.2.a.2.ii; 1.4.1.1.2.a.3.ii 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CCP) (CDRL C041) as required (associated with approved Interface Revision Notices (IRN) (CDRL C028) to include IRNs associated with Builds 5 through 8). b. Submit updated ICD that includes as-built design 60 CD prior to delivery of Release 2. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-SESS-81248B/T


3. SUBTITLE

Joint Hub to End Cryptographic Unit (Joint Hub ECU) ICD



C033

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 2. Format. Add: (1) "Contractor's format is acceptable." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." 2. (BLK 5): 1.1.1.4.e; Table 1-1; 1.4.1.1.2.a.3.ii 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CCP)(CDRL C041)as required (associated with approved Interface Revision Notices (IRN) (CDRL C028) to include IRNs associated with Builds 5 through 8). b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-SESS-81248B/T


3. SUBTITLE

Intra-Segment ICDs



C034.x

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "Contractor's format is acceptable." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." 2. (BLK 5): 1.1.1.4.g; 1.3.2.1.1.2.a.2.iii; 1.3.3.1.1.2.a.2.iii; 1.4.1.1.2.a.3.iii 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update for each ICD 45 calendar days (CD) after each review for each ICD, as required to incorporate review action item responses. b. Submit final for each ICD that includes as-built design 60 CD prior to Release 2. c. Submit update 30 CD for each ICD after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CCP)(CDRL C041) as required. d. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-SAFT-81626/T


3. SUBTITLE

System Safety Program Plan (SSPP)


C035

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER SAFT

C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 2. Content. Add the following before the first sentence: "The Contractor shall be consistent with the following Military Standard (MIL-STD)-882E, Space and Missile Systems Center (SMC)-T-004 tasks: i) Task 101: Be consistent with Section 3 and Section 4 of MIL-STD-882E, SMC-T-004. ii) Task 102: Be consistent with all." 2. (BLK 5): 1.1.1.5.b.1; 4.4.1.1.1.e.2; 5.4.1.1.1.d.2 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.5.b.2; 1.1.1.5.b.2.i


DI-SAFT-80102C/T


3. SUBTITLE

Safety Assessment Report (SAR)


C036

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER SAFT

C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 1. Reference documents. Add: "The Contractor shall be consistent with the following Military Standard (MIL-STD)-882E, Space and Missile Systems Center (SMC)-T-004 tasks: i) Task 106: Be consistent with all. The Contractor shall maintain a hazard log of all hazards. The hazard log shall be importable to Microsoft Excel [2010] and shall be included as an Appendix to the Safety Assessment Report (SAR). ii) Task 301: Be consistent with all. Results of MIL-STD 882E, Space and Missile Systems Center (SMC)-T-004 Tasks 201, 202, 204, and 208 shall be included in the SAR.” 2. (BLKs 10, 12, 13): a. Submit final 30 calendar days (CD) prior to First Test. b. Submit final 30 CD prior to CLIN 0003 contract end. c. Update as required by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

1.(BLK 5):

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-MGMT-81808


3. SUBTITLE

Contractor's Risk Management Plan


C037

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

1. (BLK 5): 1.1.1.7.a; 1.1.1.7.a.1; 4.4.1.1.1.e.3; 5.4.1.1.1.d.3 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. Update annually or anytime there is an organizational or technical change in the program. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.1.7.a.2


DI-MGMT-81809


3. SUBTITLE

Risk Management Status Report


C038

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

1. (BLKs 10, 12, 13): a. Submit on the 1st day of each month. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-HFAC-81742A/T


3. SUBTITLE

Human Engineering Program Plan (HEPP)


C039

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER HFAC

C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Use/relationship. Add: "The Human Engineering Program Plan (HEPP) shall be the single document that shall describe the Contractors entire human engineering (human factors engineering (HFE) or human systems integration (HSI) program, identifies its elements, and explains how the elements shall be managed." b. Requirements. Paragraph 2. Format. Delete in its entirety and replace with the following: "The Contractor's format is acceptable. Unless effective presentation would be degraded, the initially used format arrangement shall be used for all subsequent submissions." c. Requirements. Paragraph 3. Tailoring. Add: "Proposed tailoring shall include rationale for the tailoring." d. Requirements. Paragraph 4.b.ii. Overview. Add: "All information pertinent to the HSI effort shall be included in the HEPP. Reference to other documents can be included, however, all information necessary to understand the scope and interactions shall be provided with the HEPP. The overview shall also describe the overall HFE/HIS objectives for the program, the HSI domains that shall be addressed, and the strategy for addressing HFE/HSI domain objectives individually and in domain trade studies. If any HSI domains shall not be addressed, rationale for their exclusion shall be provided." e. Requirements. Paragraph 4.c.1. Organization. Add: "The Contractor shall include the number of proposed personnel by job type on an annual basis. Describe the approach for assessing and reporting on the quality (relative success and progress) of the overall HSI effort and each HSI domain on the course of the contract. Describe the approach for assessing the following contributors to HSI success: implementation of HSI policy and processes; implementation of a human-centered design process; education and qualifications of HSI personnel; HSI involvement in Subcontractor requirements and selection; availability and use of HSI tools; and HSI participation in verification." f. Requirements. Paragraph 4.d. Human engineering in requirements development. Add: "The Contractor shall describe tailoring of Military Standard (MIL-STD)-1472, American National Standards Institute/Human Factors and Ergonomics Society (ANSI/HFES) 100 (2007) and other requirements documents as applicable. The method for how requirements shall be allocated and decomposed (as required) shall be described. Where applicable, the threshold and goal for specific requirements as it pertains to human performance shall be described. The section shall also describe the methods by which the Contractor shall ensure that operator and maintainer personnel and training requirements are based upon human performance requirements developed form system analysis data. If a style guide is proposed then the process for how the requirements from MIL-STD-1472 are mapped to the style guide shall be described."

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) g. Requirements. Paragraph 4.f. Human Engineering in System Analysis. Add: "Assess how automation decisions shall be addressed as part of system, hardware, and software detailed design. This shall include trade studies, analysis and Commercial-Off-The-Shelf (COTS); on-developmental items; trade studies and analysis; mock-up evaluations and dynamic simulations; usability assessments; tests; detailed drawing reviews; and system and program technical reviews.” h. Requirements. Paragraph 4.g. Human Engineering in equipment detail design. Add: "In addition to human engineering requirements and guidance documents, the human engineering efforts in hardware and software user interface shall ensure the detailed design is compliant with contractual requirements. The process for how human engineering/HFE/HSI is integrated as part of the Contractor peer review process shall be described." i. Requirements. Paragraph 4.h. End-user involvement. Add: "All end user involvement forums or working groups shall be included as part of the Integrated Master Schedule (IMS) and key milestones identified within the HEPP. This shall describe the operator engagement approach consistent with systems engineering, software (Agile), hardware, logistics, training and technical order development efforts." j. Requirements. Paragraph 4.m. Human Engineering in test and evaluation. Add: "Design milestones shall be identified at which human engineering tests are to be performed to assess compatibility among human performance requirements, personnel aptitude and skill requirements, training requirements and equipment design aspects of personnel equipment/software interfaces. Human Performance Measures such as those defined in the American National Standards Institute/American Institute of Aeronautics and Astronautics (ANSI/AIAA) Guide to Human Performance Measures (G-035-1992) shall be identified with corresponding threshold and goal measures included as appropriate. This section shall also include a summary of the human engineering test schedule. The summary test schedule shall depict major project milestones such as design reviews, training, 30/60/90 percent in process reviews, first article demonstration tests, and commencement of procuring agency testing. The human engineering approach shall be consistent with the evaluation/test efforts planned for systems engineering, software (Agile), hardware, logistics, training and technical order development." k. Requirements. Paragraph 4. Add: (1) "q. Intended user. The Contractor shall describe the intended user operations, maintainer, and end-user population. The purpose of this section is to identify user specific factors that shall be integrated as part of the system design. A description of the methods used to ensure that the identified factors shall be addressed as part of the design shall be included. User factors that shall be considered include, but are not limited to user knowledge, skills, limitations, experience, and designated military code." (2) "r. Human Systems Integration Key Performance Parameters and Key System Attributes. Shall describe HFE/HSI Key Performance Parameters (KPPs) and Key System Attributes." 2. (BLK 5): 1.1.1.8.c; 1.1.1.8.c.1; 4.4.1.1.1.e.4; 5.4.1.1.1.d.4 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER HFAC

C B. EXHIBIT




of 169

SMC/MCEC6. REQUIRING OFFICE

BLK 16


DI-SESS-80858C/T


3. SUBTITLE

Contractor's Configuration/Data Management Plan

Supplier's Configuration Management Plan


C040

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Replace “Supplier” with “Contractor.” b. Use, Relationships. Paragraph a. Replace "paragraph 3.1.2 (1) of EIA-649-1” with "EIA-649B-2011, Configuration Management Standard." c. Requirements. Paragraph 2. Format. Delete entirely and replace with the following: (1) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010." (2) "Contractor's format is acceptable." d. Requirements. Paragraph 3. Content. Delete in its entirety and replace with the following: "At a minimum, the Contractor’s Configuration/Data Management Plan shall include: i) Planning and Management ii) Change and Data Management iii) Status Accounting iv) Programmatic and organization interfaces v) Organizations, roles, responsibilities, and resources vi) Data to be managed shall include, but not limited to contractual deliverables, supplier deliverables, specifications, ICDs, drawings, reports, software documentation, software code, reference documents, databases, engineering change, meeting agendas, and minutes. The Data management plan shall include a logical data filing plan. vii) A Configuration Audit Plan that shall include information required for conducting Functional Configuration Audits (FCA) and Physical Configuration Audits (PCA). Military Standard (MIL-STD)-973/T, Section 5.6.2 and (Institute of Electrical and Electronics Engineers) IEEE 15288.2, Sections 5.8 and 7.8, shall be used as reference. IEEE 15288.2, Sections 5.11 and 7.11, shall be used as compliance. The plan shall include location(s) and date(s); team composition that includes contractor representatives and their function in the audit and proposed Government participation and functions in the audit." e. Requirements. Paragraph 3. Content. Subparagraph 3.1. Replace "ISO 10007, Quality management systems – Guidelines for configuration management” with "MIL-HDBK-61A, Configuration Management Guidance and EIA-649B-2011." 2. (BLK 5): 1.1.1.10.a; 1.1.1.11.a; 1.1.1.11.c.2; 4.4.1.1.1.e.5; 5.4.1.1.1.d.5 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): Review annually and update as required, or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCEC

6. REQUIRING OFFICE

1.1.1.10.a.2


DI-SESS-80639D/T


3. SUBTITLE Engineering Change Proposal (ECP)/Contract Change Proposal (CCP)

Engineering Change Proposal (ECP)


C041

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 2. Format. Delete in its entirety and replace with the following: (1) “An Engineering Change Proposal (ECP) shall be used to propose Class I changes to the technical baseline. Only Class I changes shall be submitted to the Government for approval. (2) “An ECP shall include related contract, contract Statement of Work (SOW), and CDRL changes.” (3) “Proposed Specification Change Notices (SCNs) / Interface Revision Notices (IRNs) shall identified with the ECP in redlined/tracked format.”

(4) “In the event changes to both baseline and non-baseline documents are made, all changes shall be included in an ECP.”

(5) "The Contractor’s format is acceptable for ECPs.” (6) “ECPs shall include, where applicable, the following information: i) the change priority, change classification, and change justification ii) complete description of the change to be made and the need for that change iii) complete listing of other configuration items impacted by the proposed change and a description of the impact on those configuration items (CIs) iv) proposed changes to documents controlled by the government v) proposed serial (or lot) number effectivities of units to be produced in, or retrofitted to, the proposed configuration vi) recommendation about the way a retrofit should be accomplished vii) impacts to any logistics support elements (such as software, manuals, spares,tools, and similar) being utilized by government personnel in support of the product viii) impacts to the operational use of the product ix) complete estimated life-cycle cost impact of the proposed change x) milestones relating to the processing and implementation of the engineering change” (7) “A Contract Change Proposal (CCP) shall be used to propose changes to the contract and statement of work (SOW) requirements.” (8) “A CCP shall not be used for making changes to specifications, drawings, or other baseline documentation.” (9) “The Contractor’s format is acceptable for CCPs.” (10) “CCPs shall include the following information: (3) "An ECP shall be used to propose Class I changes to the technical baseline. Only Class I changes shall be submitted to the Protected Tactical Enterprise Service (PTES) Program Office for approval." (4) "An ECP shall include proposed SCN/IRN is/was text." (5) "For NSA ECPs, reference Section 2.18, pg., 31-32 of the NSA Technical Security Requirements Document (TSRD)." (6) "A CCP shall be used to propose changes to the contract and SOW requirements and CDRL changes." (7) "A CCP shall not include technical baseline changes.” i) control number ii) date of preparation iii) title iv) identifies the part or parts of the contract which ae affected by the proposed changes statement of justification and alternatives v) a detailed description of proposed changes vi) schedule updates vii) estimated cost (or estimated savings) expected as a result of implementing the change

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) 2. (BLK 8): a. Government approval shall be by contract modification for proposed changes. b. Government approval shall be required for each submission. 3. (BLKs 10, 12, 13): a. Neither frequency nor submission dates can be reasonably predicted; submission shall occur as the need presents itself. b. Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCEC

6. REQUIRING OFFICE

1.1.1.10.a.4


DI-SESS-80640D/T


3. SUBTITLE

Request for Variance (RFV)


C042

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 2. Format: Delete in its entirety and replace with the following: “The Contractor’s format is acceptable, or the Contractor shall use DD Form 1692.” 2. (BLK 8): a. Government approval shall be by contract modification or letter signed by the Government Procurement Contracting Officer (PCO). b. Government approval shall be required for each submission. 3. (BLKs 10, 12, 13): a. Submission shall be dependent on the occurrence of an event which generates the need to submit the proposed change(s). b. Update as required or by PCO direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCLA

6. REQUIRING OFFICE

1.1.1.14.c; 1.1.1.14.e; 1.1.1.14.j


DI-MISC-80508B/T


3. SUBTITLE

Cybersecurity Implementation Plan (CSIP)



C043

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 3. Contents. Add: "The Cybersecurity Implementation Plan (CSIP) shall show how the Contractor will integrate government identified Risk Management Framework (RMF) controls from Technical Requirements Document(s) (TRDs) into the engineering processes, products, system and components. The CSIP shall demonstrate how the Contractor will deliver a system that is RMF cybersecurity control compliant." 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 update 45 calendar days (CD) prior to Test Readiness Review (TRR). b. Submit updates quarterly thereafter. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCEC

6. REQUIRING OFFICE

1.1.1.14.d; 1.1.1.14.e


DI-MISC-80508B/T


3. SUBTITLE

Cybersecurity Test and Verification Plan (CTVP)



C044

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 3. Contents. Add: (1) "The Cybersecurity Test and Verification Plan (CTVP) shall show how the Contractor will test and validate the cybersecurity identified controls from the Technical Requirements Document (TRD) throughout the system lifecycle." (2) "The CTVP shall be developed for each Information Assurance (IA) enabled device (router, switch, desktop, server, etc.) and from a system perspective." 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 update 45 calendar days (CD) prior to Test Readiness Review (TRR). b. Submit updates quarterly thereafter. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCEC

6. REQUIRING OFFICE

1.1.1.14.l


DI-MISC-80508B/T


3. SUBTITLE Operating System and Software Patching Plan (OSSPP)



C045

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace with the following: "Contractor's format is acceptable." b. Requirements. Paragraph 3. Contents. Add: (1) "Operating System and Software Patching Plan (OSSPP) shall outline how the Contractor shall maintain the operating system and software patching compliance with published Security Technical Information Guides (STIGs) and/or Contractor original equipment manufacturer (OEM) standards." (2) "Plan shall demonstrate how the OSSPP is integrated into the systems engineering policies, plans, and procedures." 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): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCO

6. REQUIRING OFFICE

BLK 16


DI-ADMN-81306/T


3. SUBTITLE

Program Protection Implementation Plan (PPIP)


C046

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER ADMN

C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Block 3. Description/Purpose. Paragraph 3.1. Delete in its entirety and replace with the following: "The Program Protection Implementation Plan (PPIP) shall outline and define the Contractor's implementation of the Government developed Program Protection Plan (PPP). The PPIP is the principle planning and communications means for validation and approval by the Department of Defense (DoD) or Component Program Manager of the specific methods used by the Contractor to: i) identify the means chosen to implement the PPP at Contractor, Subcontractor, vendor controlled locations and ii)provide protection inputs to the system acquisition lifecycle process. The principle purpose is to provide a method to ensure effective and efficient protection of critical program information (CPI), components, and technologies." b. Block 7. Application/Interrelationship: (1) Paragraph 7.1. Delete in its entirety and replace with the following: "This data item description (DID) contains the format and content preparation instructions for the PPIP resulting from the program protection requirements set forth in Department of Defense Instructions (DoDI) 5000.02, Enclosure 3, DoDI 5200.44, and Air Force Pamphlet (AFPAM) 63-113." (2) Paragraph 7.2. Delete in its entirety and replace with the following: "This DID shall be applicable to all DoD acquisition programs regulated by DoDI 5000.02." c. Block 10. Preparation Instructions. Paragraph 10.1. Content requirements. Delete in its entirety and replace with the following: "The PPIP shall contain the following: i) A section(s) detailing the overall approach to the PPIP and the methodologies which shall be applied to the protection requirements indicated in the PPP. Section(s) shall describe the system approach to protecting Critical Functions and explain planned actions through all applicable milestones. Include: ii) Participation in working groups and integrated product teams for identifying Critical Functions and the specific Critical Components (CC) that implement those Critical Functions (hardware, software, and firmware). ii) The approach for protecting critical program information (CPI). iv) Participation in working groups and integrated product teams to conduct threat assessments to CCs. v) Participation in working groups and integrated product teams to conduct performing vulnerability assessments on CCs. vi) Participation in working groups and integrated product teams to conduct software assurance investigations and analysis on software and firmware CCs. vii) Participation in working groups and integrated product teams to assess CC risk and mitigation of identified risks.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) viii) The approach to identify CC suppliers and the supply chain. ix) Participation in working groups and integrated product teams to conduct and implement supply chain risk management. x) Participation in working groups and integrated product teams to utilize the Systems Security Engineering (SSE) approach to identify security requirements and optimize their integration into a single system engineering effort, to include the approach for optimizing life-cycle security costs, while improving overall survivability of the system or component. xi) A section(s) describing fully the results of activities and methodologies that satisfy the PPP requirements. The Contractor shall list the results of each of these activities with tables similar to those identified in the PPP. xii) Suppliers of CCs (at the component level) and the supply chain utilized (including Subcontractors that shall handle or store CCs). xiii) Details of all costs and resource requirements necessary to effectively and efficiently implement the applicable PPP requirements shall be included in the PPIP." 2. (BLK 5): 1.1.1.15.b; 1.1.1.15.c; 1.1.1.15.d; 1.1.1.15.h; 1.1.1.15.i; Table A-8 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLK 10, 12, 13): a. Submit update 60 calendar days (CD) after each Systems Engineering Technical Review (SETR). b. Submit update 60 CD after Operational Test Readiness Review (OTRR). c. Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER ADMN

C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

Key and Certificate Management Plan (KCMP) KMS ECU



C047

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) " All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." b. Requirements. Paragraph 3(c) and (d). Contents. Delete entirely and replace with the following: (1) “Section 2.9, 2.9.2 and 2.9.3, pg. 21 – 26, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as a reference.” (2) “The Key and Certificate Management Plan (KCMP) shall describe the key/certificate product interaction between the NSA Key/Certificate Infrastructure and the Contractor, with a view of the eventual user interaction. The KCMP shall re-address and finalize all areas of the Key and Certificate Management Architecture (KCMA).” (3) “The Protected Tactical Enterprise Service (PTES) KCMP, along with the PTES KCMA will be developed by the Government program office to provide common Key and Certificate Infrastructure for the PTES and will be distributed to each PTES Contractor. The Contractor’s role shall be to provide comments back to the Government on the KCMA and KCMP to ensure compatibility across the End Cryptographic Unit (ECU) platforms for PTES. The Contractor shall return comments using Track Changes in the documents.” (4) “A Key and Certificate Specification (KCS) Annex (only if needed for new key types) for a unique ECU development that is not a common part of the PTES development for key and certificates shall be a deliverable, if required, using Section 2.9.3, pg. 25- 26, of the NSA TSRD.” 2. (BLK 5): 1.1.1.16.a.1; 1.1.1.16.a.2; 1.1.1.16.a.3; 3.4.1.1.1.b.15 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

Key and Certificate Management Plan (KCMP) - Joint Hub ECU



C048

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) " All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." b. Requirements. Paragraph 3. Contents. Delete 3(c) and 3(d) entirely and replace with the following: (1) "Section 2.9, 2.9.2 and 2.9.3, pg. 21 – 26, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD)shall be used as a reference.” (2) "The Key and Certificate Management Plan (KCMP) shall describe the key/certificate product interaction between the NSA Key/Certificate Infrastructure and the Contractor, with a view of the eventual user interaction. The KCMP shall re-address and finalize all areas of the Key and Certificate Management Architecture (KCMA).” (3) "The Protected Tactical Enterprise Service (PTES) KCMP, along with the PTES KCMA will be developed by the Government program office to provide common Key and Certificate Infrastructure for the PTES and will be distributed to each PTES Contractor. The Contractor’s role shall be to provide comments back to the Government on the KCMA and KCMP to ensure compatibility across the End Cryptographic Unit (ECU) platforms for PTES. The Contractor shall return comments using Track Changes in the documents.” (4) "A Key and Certificate Specification (KCS) Annex (only if needed for new key types) for a unique ECU development that is not a common part of the PTES development for key and certificates shall be a deliverable, if required, using Section 2.9.3, pg. 25 - 26, of the NSA TSRD." 2. (BLK 5): 1.1.1.16.a.1; 1.1.1.16.a.2; 1.1.1.16.a.3; 3.4.1.1.1.b.16 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

PTES System Verification Plan (SVP)



C049

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace with the following: (1) "Contractor's format is acceptable." (2) "SVP shall contain the Requirement Verification Plan (RVP), which shall be in an electronic file format that is compatible to the existing (MILSATCOM) MC software or software and hardware MC provided. The electronic file format shall allow for the RVPs to be organized quickly by both system requirement and by verification event. The format shall allow any selected RVP to be exported to a file format compatible with MC and Contractor desktop software that allows for tracking of all RVP changes for coordination.” (3) "After the collection of verification results/artifacts for each RVP, the data shall be kept in the RVP and become an Requirement Verification Report (RVR) as one document." b. Requirements. Paragraph 3(c). Contents. Delete in its entirety and replace with the following: (1) ”The System Verification Plan (SVP) shall be delivered in 7 volumes: i) Volume 1 – System Spec Verification Plan and Reports ii) Volume 2 – Joint Hub Segment Spec Verification Plan and Reports iii) Volume 3 - Joint Hub ECU Subsystem Spec Verification Plan and Reports iv) Volume 4 – KMS ECU Subsystem Spec Verification Plan and Reports v) Volume 5 – MMS Segment Spec Verification Plan and Reports vi) Volume 6 – KMS Segment Spec Verification Plan and Reports vii) Volume 7 – KLIF Segment Spec Verification Plan and Reports (2) “Each volume shall include the following: i) Title Page. ii) Table of Contents. iii) Introduction - subsection shall cover Purpose and Objectives, Document Scope and Overview, Volume document structure, Relationship with Other Major Program Documents, Overview. iv) Applicable Documents v) Roles and Responsibilities - shall cover responsibilities of Program Management Office (PMO), Contractor, External Stakeholders, and Verification Point of Contact (POC). vi) System/Segment/Subsystem Verification Approach - shall cover respective System/Segment/Subsystem verification strategy , Overview of Verification Requirements, Verification Methods and Levels, Verification Planning, Validation and Accreditation (V&A) of Simulations, Emulators and Special Test Equipment. vii) Verification Process - shall cover respective System/Segment/Subsystem verification Processes, Working Groups, production description, execution, manage process/product. viii) Verification Summary – Use Cases, Enabling Systems, respective System/Segment/Subsystem verification Roadmap, Input to IMS, and Verification product Format.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) ix) Appendix – respective System/Segment/Subsystem verification RVPs/RVRs.” c. Requirements. Paragraph 3. Contents. Add: (1) "Each RVP shall contain the following minimum content: i) The System Requirements Identification (REQID) and unclassified or FOUO System Requirement text. ii) The unique verification methods (e.g. Test, Analysis, Demonstration, Inspection, and Similarity), Levels, and events of the RVP. Include RVP coordination and completion status information. iii) Any RVP interpretation needed to describe limitations associated with this verification effort and a list of other segment REQIDs verified or partially verified by this RVP. iv) Verification description to determine scope, number of test cases, and general complexity. Included in the description shall be any unique operational scenario listing special loading conditions needed, operator allocations, simultaneous operations, etc. The RVP shall provide detail for step-by-step test procedures to be written to accomplish the verification effort. v) The specific measurements/results that shall be used to determine if verification succeeded or failed. The pass/fail criteria shall be included separately for each individual requirement within the RVP.” 2. (BLK 5): 1.1.2; 1.1.2.3.b; 1.1.2.3.b.1; 1.1.2.3.e; 1.3.2.1.2.1.a; 1.3.3.1.2.1.a; 1.4.1.2.1.a; 1.4.1.2.1.h; 3.1.2.3.c; 5.4.1.2.1 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): a. For Builds 5 thru 8, submit draft 90 calendar days (CD) prior to the start of each test event where the Contractor shall desire to verify requirements. b. For Builds 5 thru 8, submit final 30 CD prior to the start of each major test event where the Contractor desires to test and verify requirements. c. Submit update 90 CD before start of subsystem testing. d. Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-NDTI-80566A/T


3. SUBTITLE

System Test Plan

Test Plan


C050

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER NDTI

C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 or Procedures for each activity shall be included as attachments and added during updates or as stand-alone documents as required.” (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 Agile 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 C005).” 2. (BLK 5): 1.1.2.4.b; 1.1.2.4.d.1; 1.1.2.8.b; 1.3.2.1.2.1.j; 1.3.3.1.2.1.j; D.3.b.ii; 3.1.2.b; 3.4.1.2.1.b 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. For Builds 5 thru 8, submit draft 90 calendar days (CD) prior to the start of each test event where the Contractor desires to verify requirements. b. For Builds 5 thru 8, submit final 30 CD prior to the start of each major test event where the Contractor desires to test and verify requirements. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-NDTI-80603A/T


3. SUBTITLE

Test Procedure


C051

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER NDTI

C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace with the following: "Contractor's format is acceptable." b. Requirements. Paragraph 3. Content. Add: "As-run test procedures 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 test activities needed for Agile Builds, and how best to engage the program office, users, Developmental and Operational Testers to achieve approvals and certifications to operation." 2. (BLK 5): 1.1.2.4.b; 1.1.2.8.b; 1.3.2.1.2.1.j; 1.3.3.1.2.1.j; D.3.c.ii; 3.1.2.b; 3.4.1.2.1.b 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (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.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

Test Reports



C052

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): 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. 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 or Build. However test reports are expected for major tests and where the Contractor plans to formally verify requirements.” 2. (BLK 5): 1.3.2.1.2.1.j; 1.3.3.1.2.1.j; D.3.j.ii; 3.1.2.b; 3.1.2.4.c; 3.4.1.2.1.b 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (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.b. Submit final 21 CD after the last Government comment is received. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.3.1.b


DI-MGMT-80227/T


3. SUBTITLE

Program Management Review Briefing

Contractor's Progress, Status and Management Report


C053

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Preparation Instructions. Paragraph 10.2. Format. Delete in its entirety and replace with the following: "All submissions shall be in Microsoft Power Point2010." b. Preparation Instructions. Paragraph 10.3. Content. Delete in its entirety and replace with the following: "Program Management Review (PMR) briefing shall cover the status of the program, including an executive summary and summaries for each Integrated Product Team (IPT). Summary shall include, at a minimum: i) Summary status of development - to include cost, and schedule and performance/technical factors. ii) Risk management and risk status- to include risk identification, analysis and mitigation of the highest risk areas with Risk management and risk status, to include risk identification, analysis (cost, schedule, and technical performance impacts) and mitigation of the highest risk areas. Include opportunity identification and analysis, as applicable. iii) Schedule review - include primary and secondary critical path identification and analyses, schedule margin to key future events, and key internal/external dependencies. iv) Description of the progress made against milestones during the reporting period. v) Metric analysis - to include baseline, actuals, and projected, and corrective action plan (as applicable). vi) Listing of Giver/Receiver status - to include key internal and external Giver/Receivers. Include the status of key Giver/Receivers associated with Government activities or actions such as GFE, tests, certifications, site installations, etc. vii) Issues or problem areas affecting technical, cost or schedule elements with background and any applicable recommendations for solutions. viii) Results, positive or negative, obtained related to previously identified issues or problems areas with conclusions, recommendations and corrective actions, as applicable. ix) Plans for activities during the following reporting period. x) Special Topics, as agreed to by the Contractor and Government program managers. xi) Status of CDRLs.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) xii) Business Management Review (BMR) - to include Earned Value Management Analysis showing baseline, actuals and projected Earned Value Management (EVM) data; historical and current Estimate At Completion (EAC) data; cost curves showing baseline, actuals and projected; time-phased staffing profiles showing baseline, actuals and projected; costs incurred for the reporting period and total contractual expenditures as of the reporting date; material costs; list showing status of contract changes to include proposed, submitted, approved, and recently implemented; contract schedule; and contract funds availability analysis." 2. (BLKs 10, 12, 13): (BLKs 10, 12, 13): a. Submit draft agenda and request for Special Topics 14 calendar days (CD) prior to Program Management Review (PMR). b. Submit final agenda 7 CD prior to PMR. c. Submit final briefing 2 CD prior to PMR. d. Provide at least 4 color hard copies of the agenda and briefing charts at the PMR. e. Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCPC

6. REQUIRING OFFICE

1.1.3.4.f


DI-FNCL-81565C/T


3. SUBTITLE

Contractor Cost Data Report (CCDR)

Cost Data Summary Report (DD Form 1921)


C056

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER FNCL

C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

BLK 16

BLK 16


BLK 16

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): Preparations Instructions. Paragraph 1. Add: "The Contractor shall prepare the Cost Data Summary Report (CDSR) (DD Form 1921) in accordance with (IAW) the Office of the Secretary of Defense (OSD) Deputy Director, Cost Assessment (DDCA) and OSD Acquisition, Technology and Logistics (AT&L) Performance Assessments and Root Cause Analyses (PARCA) Director-approved contract CSDR/Earned Value Management (EVM) Co-Plan." 2. (BLKs 10, 11, 12, 13): a. First submission to Defense Cost and Resource Center (DCARC) shall be IAW the attached contract Cost and Software Data Reporting (CSDR) Plan (Attachment 3). The "As of Date" and "Due Date" are relative to the event on the contract CSDR Plan. b. Subsequent submissions to DCARC shall be IAW the contract CSDR Plan attached. The "As of Date" and "Due Date" are relative to the event on the contract CSDR Plan. c. All 1921 reports shall be submitted electronically using the CSDR Submit-Review System. Data submitters shall register through the DCARC website (http://cade.osd.mil) and possess a Department of Defense-approved External Certification Authority (ECA) digital certificate from a third party vendor to obtain a DCARC Portal account and be authorized to upload CSDR content. d. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP

Page 73 of 166 Pages

of 169

Attachment 3 - CSDR Plan

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

of 169

of 169

SMC/MCPC

6. REQUIRING OFFICE

1.1.3.4.f


DI-FNCL-81566C/T


3. SUBTITLE

Functional Cost-Hour Report (DD Form 1921-1)


C057

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

BLK 16

BLK 16


BLK 16

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): Preparations Instructions. Paragraph 1. Add: " The Contractor shall prepare the Functional Cost-Hour Report (FCHR) (DD Form 1921-1) in accordance with (IAW) the Office of the Secretary of Defense (OSD) Deputy Director, Cost Assessment (DDCA) and OSD Acquisition, Technology and Logistics (AT&L) Performance Assessments and Root Cause Analyses (PARCA) Director-approved contract Cost Data Summary Report (CDSR)/Earned Value Management (EVM) Co-Plan." 2. (BLKs 10, 11, 12, 13): a. First submission to Defense Cost and Resource Center (DCARC) shall be IAW the attached contract CDSR Plan (Attachment 1). The "As of Date" and "Due Date" are relative to the event on the contract CDSR Plan. b. Subsequent submissions to DCARC shall be IAW the attached contract CDSR Plan (Attachment 2). The "As of Date" and "Due Date" are relative to the event on the contract CDSR Plan. c. All 1921-1 reports shall be submitted electronically using the CDSR Submit-Review System. Data submitters shall register through the DCARC website (http://cade.osd.mil) and possess a Department of Defense-approved External Certification Authority (ECA) digital certificate from a third party vendor to obtain a DCARC Portal account and be authorized to upload CDSR content. d. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCPC

6. REQUIRING OFFICE

1.1.3.4.f


DI-FNCL-81765B/T


3. SUBTITLE

Contractor Business Data Report (DD Form 1921-3)


C058

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Preparation instructions. General instructions. Add: (1) "Only one report shall be required to be completed and submitted by each Forward Pricing Rate (FBR) unit (e.g., plant, site, business unit) per year, independent of the number of contracts within the FPR unit which contain this CDRL item." (2) "The Contractor Business Data Report (DD Form 1921-3) shall be prepared by and for the business entity (e.g., plant, site, or business unit) responsible for submitting the Forward Pricing Rate Proposal (FPRP) representing the basis for Forward Pricing Rate Agreement (FPRA) negotiations with the Government." b. In the absence of a FPR requirement, the term FPR unit shall be interpreted for reporting purposes as business unit as defined in the FAR. The Defense Cost and Resource Center (DCARC) is responsible for administration of this requirement. The DCARC website is located at http: //cade.osd.mil. 2. (BLKs 10, 12, 13): a. Submit annually. b. All 1921-3 reports shall be submitted electronically using the 1921-3 and FPR Submit-Review System. . Data submitters shall register through the DCARC website and possess a Department of Defense-approved External Certification Authority (ECA) digital certificate or DoD-issued computer access card (CAC) to obtain a DCARC Portal account and be authorized to upload CSDR content. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

Product Support Plan (PSP)



C059

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Use/relationship. Add: "The Product Support Plan (PSP) shall be used by the Government to evaluate, monitor, and approve the Contractor's planning and performance of the Product Support Program task(s) as specified in the contract." b. Requirements. Paragraph 3. Content. Delete in its entirety and replace with the following: (1) "The Product Support Plan (PSP) shall be organized and include the following six major sections: i) Introduction ii) Summary of System Characteristics iii) Product Support Program Management, Organization, and Execution iv) Product Support Program Tasks v) Milestones Schedule vi) Related Plans applicable to the Product Support Program" (2) "The Product Support Plan (PSP) shall describe the Contractor's plans for the management, control, execution, interface, and integration of all aspects of the Contractor's Product Support Program." (3) "The PSP shall include the Contractor's implementation plan for item unique identifications (IUIDs)." (4)" The PSP shall document the Contractor's management plans for gathering and analyzing data; management, control and execution; integration and interface of the Product Support Program task(s) delineated in the contract. The Contractor's management plans shall demonstrate that the new system or equipment, when fielded, shall satisfy all supportability criteria." (5) "Reference Documents - The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract." 2. (BLK 5): 1.1.4.1.a; 1.1.4.2.a; 1.1.4.8.c; 1.1.4.8.f; 1.1.4.9.c; 3.1.4.9.a; 3.1.4.9.a.3 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCLA

6. REQUIRING OFFICE

1.1.4.3.b; 1.1.4.5.b.4


DI-SESS-81613A


3. SUBTITLE

Reliability and Maintainability (R&M) Program Plan


C060

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

1. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 2. (BLKs 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCLA

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

Combined Logistics Analyses Report (CLAR)



C061

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace with the following: "Contractor's format is acceptable." b. Requirements. Paragraph 3(d). Contents. Delete in its entirety and replace with the following: (1) ”The Combined Logistics Analyses Report (CLAR) shall be developed and delivered in four volumes: i) Volume 1 - Failure Mode Effect and Criticality Analysis Report/Damage Modes Analysis ii) Volume 2 - Failure Analysis and Corrective Action Report (FACAR) iii) Volume 3 - Mission Critical Fault Analysis (MCFA) iv) Volume 4 - Failure Summary and Analysis Report” (2) “Each volume shall include the following: i) Title Page shall identify the report by providing contract number, project name or purchase description title, task number, and reporting period. ii) Table of Contents. iii) Section I shall include the following: (a) Introduction (b) Summary A brief statement of results obtained for the analytic effort (c) Conclusions and their condensed technical substantiations iv) Section II.” (3) “Section II for Volume 1 - Failure Mode Effect and Criticality Analysis Report/Damage Modes Analysis shall contain: i) Identification of the system overview, scope, level of analysis, assumptions, summary of results, documentation of the data sources and techniques used in performing the analysis, and worksheets used during the analysis. The worksheets shall be organized to first display the highest indenture levels of the system. Refer to the attached sample worksheets for Failure Modes Effect Analysis (FMEA) (Attachment 1) and Criticality Analysis (CA) (Attachment 2). ii) Analysis performed for all mission profile(s), under worst-case conditions, which shall document and relate all associated failure modes from the piece part (or lowest indenture level specified) through all indenture levels through the subsystem and system levels, as well as identifying severity levels (categories I through IV) for each indenture level. All single-point failure modes shall be identified, evaluated and design mitigation documented. iii) Identification of those failure modes which are detectable by Built-In-Test (BIT) and to what level they will be isolated. If failures are identified as undetectable but the failure has no effect on the mission, the consequences of a second, separate item failure shall be analyzed. For those cases in which the mission would be jeopardized by the second failure, it shall be determined whether or not a failure indication would now be evident to

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) the operator, maintainer, or detectable by Built-In-Test (BIT). The report shall also identify failure modes that result in an out-of-tolerance condition or loss of functionality rather than a hard failure. The report shall identify the extent to which system monitoring and warning features will provide warning of impending failure, to facilitate corrective action during a preventive maintenance period. iv) Identification of both the preventive maintenance provisions which would minimize the probability of occurrence and the corrective maintenance features which would minimize downtime in the event of occurrence, and a description of the methodology and controls used to ensure the preventive and corrective actions are adequate. v) Identification and description of the hardware and software design provisions for maintenance by modular replacement, indication probable adjustment requirements following repair, and identification of the first point at which the post-repair checkout can be made to verify that the maintenance action is complete. vi) A description of the impact of the FMECA analysis on design, maintenance planning/supportability, and diagnostics. Major problems detected by the analysis shall be detailed, including how the problems were resolved (e.g. design changes, etc.), including impacts on safety, supportability, and diagnostics. Contractor interpretations and comments concerning the analysis and identification of the critical items list and initiated or recommended actions for control of failure risk shall be included. vii) A summary which shall include Contractor conclusions and recommendations based on the analysis results and problem information included in the report.” (4) “Section II for Volume 2 - Failure Analysis and Corrective Action Report (FACAR) shall contain: i) A Preliminary Report that shall contain the following items: (a) Originator of the report (b) Date of the failure/Incident (Technical Information Report (TIR) block 40) (c) Start date of the Contractors Report (d) Contractors name (e) Failure Analysis Report Number (f) Contract number (g) Equipment title, part number, and serial number (h) Assembly title, part number, and serial number (i) Subassembly title, element or module number, part number, and serial number (j) Part name, part number, serial number, date code, and manufacturer (k) Name and specification of test failed (l) Elapse time and phase of test failed (m) Total operation time of unit at time of failure (n) Failure symptoms (o) Failure mode, Developers Analysis of Problem (ref: TIR block 106) (p) Classification failure (independent or dependent) (q) Type of failure from Failure Keyword List (see below) (r) Disposition of failed item (s) Any supplemental information relating to the failure (i.e., any internal Contractor assessments, records, reports, correspondence, etc.) (t) Corrective Action Status (ref: TIR block 100). The content shall include on of: 1) Open (no solution is proposed) 2) Proposed (FACAR Initial of Final submitted by Contractor) 3) Verified (demonstrated at Test Site) 4) Reviewed (Corrective Action Review Team (CART) judges Corrective Action as effective) 5) completed (approved for production implementation) 6) Incomplete (external program influence) 7) Not Required” ii) “A Final Report that contains the items required in the Preliminary Report and the following additional items shall be included: (a)Failure Analysis methods (b) Corrective Action Test Results (ref: TIR block 108) (c) Statement as to whether this is a pattern failure. If it is, the reports of the other failure(s) shall be referenced (d) Corrective action: 1) Description for individual equipment failure (ref: TIR block 107) 2) Implementation Planned/Achieved to prevent other failures (ref: TIR block 109) iii) Failure Keyword list that shall include: (a) Workmanship (b) Handling (c) Process (d) Design (e) Marking (f) Test Equipment (g) Contamination (h) Open Bond Wire (i) Electrical Short (j) Electrical Open (k) Software (l) Mechanical (m) Testing Error (n) Tolerance”

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

16. REMARKS (Continued) (5) “Section II for Volume 3 - Mission Critical Fault Analysis (MCFA) shall be developed in accordance (IAW) TOR-2014-02537-Revision A, The Test Like You Fly Process Guide for Space, Launch, and Ground Systems, dated September 30 2016. For the purpose of the MCFA, a mission-critical failure is defined as a condition that meets one or more of the following criteria: i) Failure leading to inability to meet/achieve mission objectives (e.g., payload, spacecraft bus, or ground element is no longer capable of supporting mission objectives). ii) Inability to meet minimum performance specifications. iii) Degrading condition whose trend indicates a loss of mission before mean mission duration (MMD) or design life. iv) Repetitive transient condition(s) that, if not corrected, would lead to an unacceptable loss of mission performance, data, or services (e.g., satellite with processor susceptibility to single-event upsets in orbit with mean-time-to-upset much less than mean-time-to-recovery-from-upset). V) Inability to correctly generate, process, and/or transmit data to requester (e.g., end user of the mission data). The MCFA shall: i) Include a list of mission objectives divided into two categories: (a) Primary mission success, which is the absolute minimum that the project must accomplish. (b) Full mission success, which defines the baseline mission that the project is attempting to achieve. ii) Trace each mission objective to the relevant: (a) Critical Operational Issues (COIs) (b) Critical Technical Parameters (CTPs) (c) Key Performance Parameters (KPPs) (d) Key System Attributes (KSAs) (e) Mission Threads iii) Include a timeline of mission operations, showing system phases and a list of events and activities which will include for each event and activity: (a) Associated mission objective (b) Mapping to mission timeline (c) The type of event/activity, more than on category may apply, which shall include: 1) Nominal - one that is expected and normal operational for the phase, 2) Critical - success is required for continuation of the mission, 3) Contingency - response to an off-nominal, possibly critical condition, 4) First-time - the first occurrence in a phase 5) Recurring - one that has occurred before (d) Include a list of mission characteristics for each critical event or activity. (e)Include a list of hardware and software items that directly contribute to any of the critical activities/events. These are called critical mission contributors. iv) Include criteria used to define the top-level mission critical failures used as the starting points for the root cause analysis. v) A list of the potential top-level mission critical failures identified and the associated mission objective for each. vi) A list of the top-level mission critical faults analyzed and their fault paths. vii) For each fault path list: (a) contributing factors that affect the likelihood and severity of failure for each fault path. (b) Exoneration plan for each failure path. viii) Include a list of mission-critical events and fault paths not planned to be exonerated and associated data to be used for risk management.”

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

16. REMARKS (Continued) (6) "Section II for Volume 4 - Failure Summary and Analysis Report shall contain: i) A summary of the results of the Contractors Failure Reporting, Analysis, and Corrective Action System (FRACAS) implementation required by the statement of work, and shall include a cumulative tabulation of failure data. Failures which occurred during the latest report period shall be identified by suitable notation. The report shall include the following elements at a minimum: (a) Failure number (b) Failure analysis number c) Failure date (d) Name of engineer responsible for failure analysis (e) Failed part name (f) Failed part number (e.g. national stock number (NSN), logistics control number, work unit code) (g) Manufacturer of failed part (h) Subassembly name and number (i) Major assembly name and number (j) Equipment name and serial number (k) Failed parts accumulated test or field operational life data (l) Test or mission being performed when the failure occurred (m) Test or mission mode of operation and environmental and use conditions when the failure occurred (n) Failure symptoms and description of detection or diagnosis methods (e.g. Built-In-Test) (o) Failure effects (e.g. none, degradation, abort) (p) Repair action (e.g. remove/replace) (q) Failure mode description (r) Description of engineering analysis method employed in failure analysis (s) Failure mechanism/cause of failure (t) Contributing factors, including multiple factor interactions, or secondary effects of the failure (u) Categorization of failure (e.g. equipment design, equipment manufacturing workmanship, part design, part manufacturing workmanship software errors, unverified, intermittent, non-relevant) (v) Information on previous corrective actions for the same part and/or failure mode (w) Corrective action required to mitigate the failure mode, including: 1) Identification of the failure mode 2) The recommended process or process control changes, when the failure cause is due to workmanship defects 3) Proposals for retrofit of all equipment already delivered or assembled, including recommended effectivity, in accordance with the contract 4) Disposition of all defective material and material rendered obsolete because of any necessary redesign, to assure their exclusion from production items 5) Identification of previous functional and environmental qualification tests, if any, invalidated by the corrective action changes and recommendation of those tests that should be repeated, in accordance with the terms of the contract, to demonstrate the corrective actions effectiveness 6) Effect on operational and diagnostic software programs and plan for changes, if necessary (x) Corrective action status (y) The recommended fix effectiveness factor (FEF) to be applied to the failure mode based on the proposed corrective action (z) Rationale for any open failure analyses past the contract-specified closeout time (aa) Severity criticality ranking of the failure modes. The severity classification categories are: 1) Category I - Catastrophic - A failure which may cause death or system loss (i.e., aircraft, tank, missile, ship) 2) Category II - Critical - A failure which may cause severe injury, major property damage, or major system damage resulting in mission loss. 3) Category III - Marginal - A failure which may cause minor injury, minor property damage, or minor system damage which will result in delay or loss of availability or mission degradation. 4) Category IV - Minor - A failure not serious enough to cause injury, property, or system damage, but which results in unscheduled maintenance or repair.” 2. (BLK 5): 1.1.1.5.b.2.ii; 1.1.4.4.b; 1.1.4.4.c; 1.1.4.4.c.1; 1.1.4.5.b; 1.1.4.5.b.2; 1.1.4.6.a; E.(b)(10) 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) after Government approval of Class 1 Engineering Change Proposals (ECPs)/Contract Change Proposal (CCP)(CDRL C041). b. Submit update (FACAR only) 30 CD following completion of testing events. c. Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT



Page 81 of 166 Pages

of 169

Attachment 1 - Sample Worksheet for Failure Modes Effect Analysis (FMEA)

A - A serial number or other reference designation identification number is assigned for traceability purposes. B - The name or nomenclature of the item or system function being analyzed for failure mode and effects. C – The first function shall be numbered 01, the second 02, and so on. D - A concise statement of the function performed by the item including any performance standards. E – The first functional failure shall be numbered A, the second B, and so on. F – Ways an item can either partially (with upper and/or lower performance limits) or totally fail to perform its functions. G - All predictable failure modes along with their most probable causes for each indenture level analyzed shall be identified and described. H - A concise statement of the mission phase and operational mode in which the failure occurs. I - Local effects identify the impact a failure mode has on the operation and function of the item in listed in block A. J - Next higher level effects identify the impact an assumed failure has on the operation and function of the items in the next higher indenture level above the indenture level under consideration. K - End effects evaluate and identify the total effect a failure has on the operation, function, or status of the uppermost system or end item and the surrounding environment. L - A description of the methods by which occurrence of the failure mode is detected by the operator and by the maintainer at the unit level and to what indenture level they will be isolated. Describe the method by which ambiguities are resolved when more than one failure mode causes the same failure indication. Identify to what indenture level failures can be isolated by the use of Built-In-Test (BIT) features and indicate when ancillary test equipment will be required for fault isolation. M - Describe the most direct procedure that allows an operator to isolate the malfunction or failure. N - The compensating provisions, either design provisions or operator actions, which circumvent or mitigate the effect of the failure. O - Severity classification categories (I-IV) assigned to each failure mode, without considering compensating provisions, according to the failure effect at the uppermost system. The severity classification categories are: Category I - Catastrophic - A failure which may cause death or system loss (i.e., aircraft, tank, missile, ship) Category II - Critical - A failure which may cause severe injury, major property damage, or major system damage which will result in mission loss. Category III - Marginal - A failure which may cause minor injury, minor property damage, or minor system damage which will result in delay or loss of availability or mission degradation. Category IV - Minor - A failure not serious enough to cause injury, property, or system damage, but which results in unscheduled maintenance or repair. P - Describe the basic actions taken by the maintainer to correct the failure. Q - Any pertinent remarks pertaining to and clarifying any other columns or recommendations for design improvements.

of 169

Attachment 2 - Sample Worksheet for Criticality Analysis (CA)

Columns A, B, D, G, H, O, & Q on the Criticality Analysis worksheet are copied from the FMEA worksheet. R – Failure probability or Failure rate data source - When failure modes are assessed in terms of probability of occurrence (Levels A-E):

Level A – Frequent: High probability of occurrence that may be defined as a single failure mode probability greater than or equal to 10-1 of the overall probability of failure during the operating time interval. Level B – Reasonably probable: Reasonable probability of occurrence that may be defined as a single failure mode probability of occurrence which is more than 10-2 but less than 10-1 of the overall probability of failure during the item operating time. Level C – Occasional: Occasional probability of occurrence that may be defined as a single failure mode probability of occurrence which is more than 10-3 but less than 10-2 of the overall probability of failure during the item operating time. Level D – Remote: Remote probability of occurrence that may be defined as a single failure mode probability of occurrence which is more than 10-6 but less than 10-3 of the overall probability of failure during the item operating time. Level E – Extremely unlikely: Extremely unlikely may be defined as a single failure mode probability of occurrence which is less than 10-6 of the overall probability of failure during the item operating time. When failure rate data are to be used in the calculation of criticality numbers (column W), the data source of the failure rates used in each calculation shall be listed. When a failure probability is listed, the remaining columns S-V are not required.

S - The conditional probability that the failure effect will result in the identified criticality classification, given that the failure mode occurs. The values represent the analyst's judgment as to the conditional probability the loss will occur and should be quantified in general accordance with the following:

Actual loss 1.0 Probable Loss > 0.10 to <1.0 Possible Loss >0 to = 0.10 No Effect = 0

T - The fraction of the part failure rate related to the particular failure mode under consideration. U - The failure rate from the appropriate reliability prediction. V - The operating time of the item per mission shall be derived from the system definition. W – A relative measure of consequence of a failure mode and its frequency of occurrence. X – A relative measure of consequence of an item failure and its frequency of occurrence.

of 169

SMC/MCLA

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

Product Support Analysis



C062

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



As Needed

11. AS OF DATE

N/A

60 DAC


One/R

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. Delete in its entirety and replace with the following: “All submissions shall be in electronic format compatible with Microsoft Suite 2010.” b. Requirements. Paragraph 3. Content. Delete in its entirety and replace with the following: ”The Product Support Analysis shall be developed and delivered in 14 volumes: i) Volume 1 – Product Support Strategy. Results of Activity 1.1, 1.2, and 1.3 shall be delivered in accordance with (IAW) TA-STD-0017. Applicable to CLIN 1 and 2. ii) Volume 2 – Product Support Analysis Planning. Results of Activity 2.1 and 2.2 shall be delivered IAW TA-STD-0017. Applicable to CLIN 1 and 2. iii) Volume 3 – Program and Design Review. Results of Activity 3.1, 3.2, 3.3 and 3.4 shall be delivered IAW TA-STD-0017. Applicable to CLIN 1 and 2. iv) Volume 4 – Application Assessment. Results of Activity 4.1, 4.2, 4.3 and 4.4 shall be delivered IAW TA-STD-0017. Applicable to CLIN 1 and 2. v) Volume 5 – Support System Standardization. Results of Activity 5.1, 5.2, 5.3 and 5.4 shall be delivered IAW TA-STD-0017. Applicable to CLIN 1, 2 and 3. vi) Volume 6 – Technological Opportunities. Results of Activity 7.1, 7.2 and 7.3 shall be delivered IAW TA-STD-0017. Applicable to CLIN 1 and 2. vii) Volume 7 – Supportability and Supportability Related Design Factors. Results of Activity 8.1, 8.2, 8.3, 8.4, 8.5, 8.6 and 8.7 shall be delivered IAW TA-STD-0017. Applicable to CLIN 1 and 2. viii) Volume 8 – Functional Analysis. Results of Activity 9.1, 9.2, 9.3, 9.4, 9.5, 9.6, 9.7, 9.8, 9.9 and 9.10 shall be delivered IAW TA-STD-0017. Applicable to CLIN 1, 2 and 3. ix) Volume 9 – Evaluation of Alternatives and Tradeoff Analysis. Results of Activity 11.1, 11.2, 11.3, 11.4, 11.5, 11.7, 11.8, 11.10, 11.11, 11.12 and 11.13 shall be delivered IAW TA-STD-0017. Applicable to CLIN 1, 2 and 3.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) x) Volume 10 – Task Analysis. Results of Activity 12.1, 12.2, 12.3, 12.4, 12.5, 12.6, 12.7, 12.8, 12.9, 12.10, and 12.11 shall be delivered IAW TA-STD-0017. Applicable to CLIN 1, 2 and 3. xi) Volume 11 – Early Distribution Analysis. Results of Activity 13.1, 13.2, 13.3, 13.4 and 13.5 shall be delivered IAW TA-STD-0017. Applicable to CLIN 2 and 3. xii) Volume 12 – Diminishing Manufacturing Sources and Material Shortages Management (DMSMS) Obsolescence Analysis. Results of Activity 14.1 shall be delivered IAW TA-STD-0017. Applicable to CLIN 1, 2 and 3. xiii) Volume 13 – Disposal Analysis. Results of Activity 16.1 and 16.2 shall be delivered IAW TA-STD-0017. Applicable to CLIN 2 and 3. xiv) Volume 14 – Operational Suitability Test, Evaluation, Verification and Validation. Results of Activity 17.1, 17.2, 17.3, 17.4 and 17.5 shall be delivered IAW TA-STD-0017. Applicable to CLIN 2 and 3.” 2. (BLK 5): 1.1.4.2.a.4; 1.1.4.7.c; 1.1.4.7.c.4; 3.1.4.9.b; 3.1.4.12.a; 3.1.4.15.a 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLK 13): Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT



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

of 169

SMC/MCD

6. REQUIRING OFFICE

BLK 16


DI-PSSS-81872A


3. SUBTITLE

Level of Repair Analysis (LORA) Report


C063

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER PSSS

C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

1. (BLK 5): 1.1.4.7.c.2; 3.3.2.4.2.e; 3.3.3.4.2.d

2. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) after Government approval of Class 1 Engineering Change Proposals (ECPs)/Contract Change Proposal (CCP)(CDRL C041). b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCLA

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

Product Drawings/Models and Associated Lists



C064

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace 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.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

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 5): 1.1.4.7.d; 1.4.1.1.3.e; 3.1.4.16.e; 3.1.4.16.f 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): a. Submit update of Vol. 1 and 2 90 calendar days (CD) before installations. b. Submit final of Vol. 1 and 2 60 CD prior to Physical Configuration Audit (PCA). c. Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

1.1.4.9.d


DI-MGMT-81994/T


3. SUBTITLE

Priced Bill of Materials


C065

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 2. Contents. Add: “The Contractor shall provide a tailored version of the Bill of Materials (BOM) for each site installation.” 2. (BLKs 10, 12, 13): a. Submit update 90 calendar days (CD) prior to Joint Hub installation. b. Submit update 90 CD prior to End Cryptographic Unit (ECU) installation. c. Submit update 90 CD prior to Key Loading Initialization Facility (KLIF) installation. d. Submit final system BOM 90 CD prior to Physical Configuration Audit (PCA). e. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-IPSC-81431A/T


3. SUBTITLE

PTES Segment Specification (MMS)



C066

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 Instructions. Add: (1) "Main volume shall be unclassified with reference to a separate classified Appendix." (2) "Classified portions of this data item shall be submitted in accordance with (IAW) Department of Defense form DD-254 and instructions contained in the CDRL instructions of this document." b. Requirements. Paragraph 3. Format. Add: "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." c. Requirements. Paragraph 4.a. Title page or identifier. Add: "Revision Control Page. The revision control page shall list the following information: i) Each revision letter ii) Date of each revision iii) Pages affected by each revision and a description of the change(s)" 2. (BLK 5): 1.3.1.1.1.b; 1.3.2.1.1.2.a.1; 1.3.2.1.2.d; 1.3.2.1.2.1.e.1; 1.3.2.1.2.1.f; 1.3.2.1.2.1.f.1; 1.3.2.1.2.1.l 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) prior to Build Decision Reviews (BDR) 5 thru 8. b. Submit update 45 CD after each review, as required, to incorporate design review action item responses. c. Submit final document that includes as-built design 60 CD prior to Release 2. d. Submit update 30 CD after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CCP) (CDRL C041) as required. e. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-IPSC-81431A/T


3. SUBTITLE PTES Segment Specification (Key Management System (KMS))



C067

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 Instructions. Add: (1) "Main volume shall be unclassified with reference to a separate classified Appendix." (2) "Classified portions of this data item shall be submitted in accordance with (IAW) Department of Defense form DD-254 and instructions contained in the CDRL instructions of this document." b. Requirements. Paragraph 3. Format. Add: "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." c. Requirements. Paragraph 4.a. Title page or identifier. Add: "Revision Control Page. The revision control page shall list the following information: i) Each revision letter ii) Date of each revision iii) Pages affected by each revision and a description of the change(s)" 2.(BLK 5): 1.3.1.1.1.b; 1.3.3.1.1.2.a.1; 1.3.3.1.2.1.e.1; 1.3.3.1.2.1.f; 1.3.3.1.2.1.f.1 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) prior to Build Decision Reviews (BDR) 5 thru 8. b. Submit update 45 CD after each review, as required, to incorporate design review action item responses. c. Submit final document that includes as-built design 60 CD prior to Release 2. d. Submit update 30 CD after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CCP) (CDRL C041) as required. e. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-IPSC-81431A/T


3. SUBTITLE

PTES Segment Specification (Key Loading Initialization Facility (KLIF))



C068

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 Instructions. Add: (1) "Main volume to be unclassified with reference to a separate classified Appendix." (2) "Classified portions of this data item shall be submitted in accordance with (IAW) Department of Defense form DD-254 and instructions contained in the CDRL instructions of this document." b. Requirements. Paragraph 3. Format. Add: “All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." c. Requirements. Paragraph 4.a. Title page or identifier. Add: "Revision Control Page. The revision control page shall list the following information: i) Each revision letter ii) Date of each revision iii) Pages affected by each revision and a description of the change(s)" 2. (BLK 5): 1.3.1.1.1.b; 1.3.3.1.1.2.a.1; 1.3.3.1.2.1.e.1; 1.3.3.1.2.1.f; 1.3.3.1.2.1.f.1 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) prior to Build Decision Reviews (BDR) 5 thru 8. b. Submit update 45 CD after each review, as required, to incorporate design review action item responses. c. Submit final document that includes as-built design 60 CD prior to Release 2. d. Submit update 30 CD after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CCP) (CDRL C041) as required. e. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.1


DI-MISC-81762/T


3. SUBTITLE

Security Evaluation Document (SED) - KMS ECU

Security Evaluation Document (SED)


C069

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3. Contents. Add: (1) " Section 2.2, pg. 9 – 11, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as a reference." (2) "The initial delivery for the System Preliminary Design Review (PDR) shall address the Contractor's security theoretical design and operation. The randomizer design shall be discussed and a determination shall be made for the need of a randomizer test (and test report)." (3) "Updates for System Critical Design Review (CDR) shall include Fail Safe Design Analysis (FSDA) data (if traditional FSDA is chosen), Covert Channel Analysis (CCA), and Theory of Compliance (TOC) data. The Contractor and NSA shall agree on QUADRANT design approach." c. Requirements. Paragraph 3.4.1. General info. Add: "The Contractor shall update the Security Evaluation Document (SED) for final delivery before the Test Readiness Review (TRR) to describe final design data." 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 additional deliveries, if required, based on design, per Section 2.2.1 (pg. 10) of the NSA TSRD. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.2


DI-MISC-81762/T


3. SUBTITLE

Security Evaluation Document (SED) - Joint Hub ECU

Security Evaluation Document (SED)


C070

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3. Contents. Add: (1) "Section 2.2, pg. 9 – 11, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as a reference." (2) "The initial delivery for the System Preliminary Design Review (PDR) shall address the Contractor's security theoretical design and operation. The randomizer design shall be discussed and a determination shall be made for the need of a randomizer test (and test report)." (3) "Updates for System Critical Design Review (CDR) shall include Fail Safe Design Analysis (FSDA) data (if traditional FSDA is chosen), Covert Channel Analysis (CCA), and Theory of Compliance (TOC) data. The Contractor and NSA shall agree on QUADRANT design approach." c. Requirements. Paragraph 3.4.1. General info. Add: "The Contractor shall update the Security Evaluation Document (SED) for final delivery before the Test Readiness Review (TRR) to describe final design data." 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 additional deliveries, if required, based on design, per Section 2.2.1 (pg. 10) of the NSA TSRD. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.3


DI-QCIC-81689/T


3. SUBTITLE

Security Verification Plan and Procedures - KMS ECU

Security Verification Plan and Procedures


C071

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER QCIC

C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information. (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3. Contents. Add: (1) "Section 2.3, pg. 11, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as a reference." (2) "When delivering the procedures, an accompanying Software/Hardware Requirements Specification (SHRS) Requirement Traceability Matrix (RTM) with requirements traced to the specific test procedures shall be delivered with it." 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): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.4


DI-QCIC-81689/T


3. SUBTITLE

Security Verification Plan and Procedures - Joint Hub ECU

Security Verification Plan and Procedures


C072

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information.” (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3. Contents. Add: (1) "Section 2.3, pg. 11, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as a reference." (2) "When delivering the procedures, an accompanying SHRS Requirement Traceability Matrix (RTM) with requirements traced to the specific test procedures shall be delivered with it." 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): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

1.4.1.1.1.b.5


DI-QCIC-81690/T


3. SUBTITLE

Security Verification Report (SVR) - KMS ECU

Security Verification Report


C073

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information. (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3. Contents. Add: (1) "Section 2.3, pg. 11, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance." (2) "When delivering the report, an accompanying Software/Hardware Requirements Specification (SHRS) Requirement Traceability Matrix (RTM) with requirements traced to the specific test procedures shall be delivered with it." 2. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 3. (BLK 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.6


DI-QCIC-81690/T


3. SUBTITLE

Security Verification Report (SVR) - Joint Hub ECU

Security Verification Report


C074

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information. (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3. Contents. Add: (1) "Section 2.3 ,pg. 11, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance." (2) "When delivering the report, an accompanying SHRS Requirement Traceability Matrix (RTM) with requirements traced to the specific test procedures shall be delivered with it." 2. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 3. (BLK 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.7


DI-IPSC-81427B/T


3. SUBTITLE

Software Development Process Description Document - KMS ECU

Software Development Plan (SDP)


C075

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3. Contents. Add: (1) "Section 2.5, pg. 13, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as a reference. (2) “The Contractor shall document the development, modification, and management of SW/PL processes, standards, and practices (such as Capability Maturity Model Integration (CMMI), Maturity Level 3, or equivalent).” (3) “Include a description that shall contain the following: i) Organizational Structure to include software/programmable logic configuration management and software/programmable logic quality assurance. ii) Identification of Contractor software and programmable logic development processes for configuration management, quality assurance, and audits; while making the process documents available for review, if requested. iii) Identification of tools to be used, or currently in use, to develop and maintain the software and/or programmable logics. iv) A list of planned hardware, software, and programmable logic documents to be prepared for the development. List includes CDRL deliverables as well as internal process documents. v) A description of the peer review process and products. vi) The methods used to acquire or auto-generate code; such as reuse, Commercial-Off-The-Shelf (COTS), Open Source, Government-Off-the-Shelf (GOTS), etc. vii) A description of the testing process (all levels from desk checking to Security Verification (SV) execution). viii) Provide ‘Coding Standards’ and ‘Naming Conventions’ employed." 2. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) 3. (BLKs 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


A B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.8


DI-IPSC-81427B/T


3. SUBTITLE

Software Development Process Description Document - Joint Hub ECU

Software Development Plan (SDP)


C076

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information.” (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3. Contents. Add: (1) "Section 2.5, pg. 13, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as a reference. (2) “The Contractor shall document the development, modification, and management of SW/PL processes, standards, and practices (such as Capability Maturity Model Integration (CMMI), Maturity Level 3, or equivalent).” (3) “Include a description that shall contain the following: i) Organizational Structure to include software/programmable logic configuration management and software/programmable logic quality assurance. ii) Identification of Contractor software and programmable logic development processes for configuration management, quality assurance, and audits; while making the process documents available for review, if requested. iii) Identification of tools to be used, or currently in use, to develop and maintain the software and/or programmable logics. iv) List of planned hardware, software, and programmable logic documents to be prepared for the development. List includes CDRL deliverables as well as internal process documents. v) Description of the peer review process and products. vi) The methods used to acquire or auto-generate code; such as reuse, Commercial-Off-The-Shelf (COTS), Open Source, Government-Off-the-Shelf (GOTS), etc. vii) Describe the testing process (all levels from desk checking to Security Verification (SV) execution). viii) Provide "Coding Standards" and "Naming Conventions" employed.” 2. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) 3. (BLKs 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.9


DI-MISC-80508B/T


3. SUBTITLE

Software/Hardware Requirements Specification (SHRS) - KMS ECU



C077

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "Contractor shall submit in a format that can be read, searched and sorted electronically by the Government." (2) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information.” (3) "Electronic deliveries shall be submitted in accordance with (IAW) Section 2.6.2 of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD)." (4) “All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader. Format shall be consistent with the format for other NSA required CDRLs.” b. Requirements. Paragraph 3. Contents. Delete entirely and replace with the following: (1) "The Software/Hardware Requirements Specification (SHRS) is intended to be a combined requirements and traceability deliverable. The document shall include traceability up to the Government End Cryptographic Unit (ECU) TRD(s) from the System/Subsystem Specification (SSS) and from the lower level implementation Software, Programmable Logic and Hardware requirements. The SHRS shall include traceability from the test plans/procedures." (2) "Data item descriptions (DIDs) DI-IPSC-81433A and DI-IPSC-81431A shall be used as guidance for the content." (3) "Section 2.6, pg. 13 - 14, of the NSA TSRD shall be used as a reference." (4) "The SHRS shall include attributes for each of the following system level requirements: i) Requirement Type with Identifier (a) Government Security (b) Vendor Derived (c) Government Performance (d) Vendor Performance (e) Vendor value added capability ii) Requirement Description (a) Allocation 1) Hardware 2) Programmable Logic 3) Software (b) Sub Allocation 1) Field Programmable Gate Array (FPGA) 2) Computer Programmable Logic Device (CPLD) 3) Application Specific Integrated Circuit (ASIC) 4) Software Item (SI) with assigned Unit (aka Class, package, function) 5) Processor; such as Memory Management Unit (MMU) 6) Memory Assignment, such as Volatile/Non-Volatile

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) iii) Test Method (a) Security Verification Test (SVT) (b) Software Testing iv) Verification Method (a) Test (b) Inspection (c) Analysis (d) Demonstration v) Vendor Software Test Plan" 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): Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.10


DI-MISC-80508B/T


3. SUBTITLE

Software/Hardware Requirements Specification (SHRS) - Joint Hub ECU



C078

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "Contractor shall submit in a format that can be read, searched and sorted electronically by the Government." (2) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information.” (3) "Electronic deliveries shall be submitted in accordance with (IAW) Section 2.6.2 of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD)." (4) “All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader. Format shall be consistent with the format for other NSA required CDRLs.” b. Requirements. Paragraph 3. Contents. Delete entirely and replace with the following: (1) "The Software/Hardware Requirements Specification (SHRS) is intended to be a combined requirements and traceability deliverable. The document shall include traceability up to the Government End Cryptographic Unit (ECU) TRD(s) from the System/Subsystem Specification (SSS) and from the lower level implementation Software, Programmable Logic and Hardware requirements. The SHRS shall include traceability from the test plans/procedures." (2) "Data item descriptions (DIDs) DI-IPSC-81433A and DI-IPSC-81431A shall be used as guidance for the content." (3) "Section 2.6, pg. 13 -14, of the NSA TSRD shall be used as a reference." (4) "The SHRS shall include attributes for each of the following system level requirements: i) Requirement Type with Identifier (a) Government Security (b) Vendor Derived (c) Government Performance (d) Vendor Performance (e) Vendor value added capability ii) Requirement Description (a) Allocation 1) Hardware 2) Programmable Logic 3) Software (b) Sub Allocation 1) Field Programmable Gate Array (FPGA) 2) Computer Programmable Logic Device (CPLD) 3) Application Specific Integrated Circuit (ASIC) 4) Software Item (SI) with assigned Unit (aka Class, package, function) 5) Processor; such as Memory Management Unit (MMU) 6) Memory Assignment, such as Volatile/Non-Volatile

16. REMARKS

See Distro List



17. PRICE GROUP

Page 101 of 166 PREVIOUS EDITION MAY BE USED. DD FORM 1423-1, FEB 2001

of 169

16. REMARKS (Continued) iii) Test Method (a) Security Verification Test (SVT) (b) Software Testing iv) Verification Method (a) Test (b) Inspection (c) Analysis (d) Demonstration v) Vendor Software Test Plan" 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): Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.11


DI-MISC-80508B/T


3. SUBTITLE

Software/Hardware Design Description (SHDD) - KMS ECU



C079

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3. Contents. Delete entirely and replace with the following: "Data item descriptions (DIDs) DI-IPSC-81432A and DI-IPSC-81435A shall be used as guidance for the content needed for this deliverable and not for format." c. Requirements. Paragraph 3. Contents. Add: (1) "Using DIDs DI-IPSC-81432A and DI-IPSC-81435A as guidelines, combine and replace the information with: "Specific content and format for this CDRL shall be as follows (ref: Section 2.7, pg. 15 - 18) of the National Security Agency ‘s (NSAs) Technical Security Requirements Document (TSRD). (2) "The Software/Hardware Requirements Specification (SHRS) is intended to be a combined requirements and traceability deliverable." (3) "The Software/Hardware Design Description (SHDD) shall include attributes for each of the following systems level requirements: i) Functional Diagram Information - Functional block diagram depicting processors, Information Security (INFOSEC) boundary, cryptographic boundary, Red Input/Output (I/O), Black I/O, fill any other functional block that is contained within the boundary. Identify implementation of each functional block (Hardware/Software/platform)(HW/SW/PL))." ii) Data Flow Information shall include: (a) Diagram identifying each data flow (User data, Bypass, Control) through functional blocks. (b) Diagram reflecting format of data entering/leaving each functional block. (c) Identify the checks done within each functional block. (d) Identify what initiates transfer of data between functional blocks. iii) Processor Information shall include: (a) Processors used in the design. (b) Interrupts (Priority and Masking including internal processor interrupts (Memory Management Unit (MMU) failure, memory Parity failure, etc.). If interrupt is Masked, the conditions that set the mask. (c) Polled Register (Register Name, Polling (periodic/aperiodic), Frequency (sample rate, if periodic; Algorithm/Event, if aperiodic). (d) Address Maps. iv) Parts List - Identify any in-built mechanisms in commercial parts used as part of security architecture (i.e., memory parities, processor diagnostics, etc.).

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) v) Memories - Type (EEPROM, FLASH, SRAM, DRAM, etc.) (Scratchpad, Permanent) shall include: (a) Volatile/Non-Volatile. (b) Red/Black. (c) Zeroization Summary (Passive/Active/None) (Note: if Active, cite overwrite pattern with number of times of overwrite). (d) Zeroization Initiation (Tamper, Panic, OV, UV, etc.). (e) Memory Contents (Data, Data Structure). (f) Memory Access Controls (MMU, Hamming Distance, Read/Write, Red/Black, etc.). vi) Alarms/Checks shall include: (a) Real Time/Periodic Diagnostics. (b) HW/SW Implementation. (c) Narrative description of each Alarm/Check. (d) Functional diagram of HW inhibits. vii) Management Interfaces and Control shall include: (a) Summary of Front Panel controls. (b) Summary of Local Management controls. (c) Summary of Remote Management controls. viii) Summary of External and Internal Message Handling shall include: (a) Protocol Messages/Fields bypassed. (b) Protocol regeneration. (c) Protocol proxies. (d) Responses to protocol prompts. (e) Command/Control/Status messages exchanged internally between Red and Black sides, but not leaving the End Cryptographic Unit (ECU). (f) Contractor shall provide their internal bypass rule set, either as a copy of an existing vendor technical analysis or as part of a SED description. ix) Software Items (SI) (include all OSs used) (note: SI is defined as a major module/function): (a) What SIs reside on each processor? (b) What is the source (Contractor developed, Contractor reuse from other Type 1 efforts, Commercial Off-The-Shelf (COTS) , etc.) of each of the SIs? (c) What are the version numbers of each of the COTS SIs? (d) Is the source code available for the COTS SIs? (e) What is the source of the COTS SW? (f) What checks are done on the COTS SW before integration into the design (include pertinent internet/company-supplied information on known/reported bugs/vulnerabilities)? (g) What changes/modifications are made to the COTS code before integration into the design? (h) Provide a list of all Units (e.g., functions, packages, and cases) contained within the SI and a description of each unit in the initial release by System Preliminary Design Review (PDR). (i) During the detailed design phase, provide/add the detailed design in the SHDD by System Critical Design Review (CDR). x) SW Security Mechanisms: (a) Provide description of HW/SW, and PL Configuration tools/controls/processes. (b) Provide a short description of each of the HW (MMU, Watchdog timers, etc.), SW (Entry-Exit flags, etc.), and Programmable Logic security mechanisms that monitor proper operation of SW. (c) Clarify the mechanisms that preclude the "untrusted" SW from defeating the inherent security services of the box. (d) Provide a detailed memory usage map showing separation and access controls between processes/data/types of memory. (e) Include Processor modes (Supervisor, User, etc.) under which each SI are executed. Memory types shall be broken into Red Code (Untrusted Code), Black Code (Trusted Code), Red Data (Classified Data), and Black Data (Unclassified Data) with any associated restrictions (Read Only, Read/Write). xi) Test/Debug Interfaces: (a) Describe the HW, SW, and PL test interfaces (mechanical, digital, and logical) and the mechanisms used to enable/disable. (b) Describe whether the test interfaces are available within fielded units. 1) JTAG connectors present in the fielded product? 2) Is there debug code embedded in the source code? 3) Is there debug code embedded in the operational, signed code? xii) Image wrapping external to the equipment: (a) Describe the design of the wrap, including source of wrapping key/certificate. (b) Describe the process employed to ensure that proper code is wrapped. xiii) Implementation Assumptions: (a) Document assumptions made when requirements were subject to interpretation. (b) Provide rationale for approach recommended by the Contractor for implementation. (c) Include Government approval status of the implementation approach."

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

16. REMARKS (Continued) 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): Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.12


DI-MISC-80508B/T


3. SUBTITLE

Software/Hardware Design Description (SHDD) - Joint Hub ECU



C080

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3. Contents. Delete in its entirety and replace with the following: "Data item descriptions (DIDs) DI-IPSC-81432A and DI-IPSC-81435A shall be used as guidance for the content needed for this deliverable and not for format." c. Requirements. Paragraph 3. Contents. Add: (1) "Using the above DIDs as guidelines, combine and replace the information with: "Specific content and format for this CDRL is as follows (ref: Section 2.7, pg. 15 - 18) of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD)." (2) "The Software/Hardware Requirements Specification (SHRS) is intended to be a combined requirements and traceability deliverable." (3) "The Software/Hardware Design Description (SHDD) shall include attributes for each of the following system level requirements: i) Functional Diagram Information - Functional block diagram depicting processors, Information Security (INFOSEC) boundary, cryptographic boundary, Red Input/Output (I/O), Black I/O, fill any other functional block that is contained within the boundary. Identify implementation of each functional block (Hardware/Software/Platform (HW/SW/PL)). ii) Data Flow Information shall include: (a) Diagram identifying each data flow (User data, Bypass, Control) through functional blocks. (b) Diagram reflecting format of data entering/leaving each functional block. (c) Identify the checks done within each functional block. (d) Identify what initiates transfer of data between functional blocks. iii) Processor Information shall include: (a) Processors used in the design. (b) Interrupts (Priority and Masking including internal processor interrupts Memory Management Unit (MMU) failure, memory Parity failure, etc.). If interrupt is Masked, the conditions that set the mask. (c) Polled Register (Register Name, Polling (periodic/aperiodic), Frequency (sample rate, if periodic; Algorithm/Event, if aperiodic). (d) Address Maps. iv) Parts List - Identify any in-built mechanisms in commercial parts used as part of security architecture (i.e., memory parities, processor diagnostics, etc.).

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) v) Memories - Type (EEPROM, FLASH, SRAM, DRAM, etc.) (Scratchpad, Permanent) shall include: (a) Volatile/Non-Volatile. (b) Red/Black. (c) Zeroization Summary (Passive/Active/None) (Note: if Active, cite overwrite pattern with number of times of overwrite). (d) Zeroization Initiation (Tamper, Panic, OV, UV, etc.). (e) Memory Contents (Data, Data Structure). (f) Memory Access Controls (MMU, Hamming Distance, Read/Write, Red/Black, etc.). vi) Alarms/Checks shall include: (a) Real Time/Periodic Diagnostics. (b) HW/SW Implementation. (c) Narrative description of each Alarm/Check. (d) Functional diagram of HW inhibits. vii) Management Interfaces and Control shall include: (a) Summary of Front Panel controls. (b) Summary of Local Management controls. (c) Summary of Remote Management controls. viii) Summary of External and Internal Message Handling shall include: (a) Protocol Messages/Fields bypassed. (b) Protocol regeneration. (c) Protocol proxies. (d) Responses to protocol prompts. (e) Command/Control/Status messages exchanged internally between Red and Black sides, but not leaving the End Cryptographic Unit (ECU). (f) Contractor shall provide their internal bypass rule set, either as a copy of an existing vendor technical analysis or as part of a SED description. ix) Software Items (SI) (include all OSs used) (note: SI is defined as a major module/function): (a) What SIs reside on each processor? (b) What is the source (Contractor developed, Contractor reuse from other Type 1 efforts, Commercial Off-The-Shelf (COTS) , etc.) of each of the SIs? (c) What are the version numbers of each of the COTS SIs? (d) Is the source code available for the COTS SIs? (e) What is the source of the COTS SW? (f) What checks are done on the COTS SW before integration into the design (include pertinent internet/company-supplied information on known/reported bugs/vulnerabilities)? (g) What changes/modifications are made to the COTS code before integration into the design? (h) Provide a list of all Units (e.g., functions, packages, and cases) contained within the SI and a description of each unit in the initial release by System Preliminary Design Review (PDR). (i) During the detailed design phase, provide/add the detailed design in the SHDD by System Critical Design Review (CDR). x) SW Security Mechanisms: (a) Provide description of HW/SW, and PL Configuration tools/controls/processes. (b) Provide a short description of each of the HW (Memory Management Unit (MMU), Watchdog timers, etc.), SW (Entry-Exit flags, etc.), and Programmable Logic security mechanisms that monitor proper operation of SW. (c) Clarify the mechanisms that preclude the "untrusted" SW from defeating the inherent security services of the box. (d) Provide a detailed memory usage map showing separation and access controls between processes/data/types of memory. (e) Include Processor modes (Supervisor, User, etc.) under which each SI are executed. Memory types shall be broken into Red Code (Untrusted Code), Black Code (Trusted Code), Red Data (Classified Data), and Black Data (Unclassified Data) with any associated restrictions (Read Only, Read/Write). xi) Test/Debug Interfaces: (a) Describe the HW, SW, and PL test interfaces (mechanical, digital, and logical) and the mechanisms used to enable/disable. (b) Describe whether the test interfaces are available within fielded units. i. JTAG connectors present in the fielded product? ii. Is there debug code embedded in the source code? iii. Is there debug code embedded in the operational, signed code? xii) Image wrapping external to the equipment: (a) Describe the design of the wrap, including source of wrapping key/certificate. (b) Describe the process employed to ensure that proper code is wrapped. xiii) Implementation Assumptions: (a) Document assumptions made when requirements were subject to interpretation. (b) Provide rationale for approach recommended by the Contractor for implementation. (c) Include Government approval status of the implementation approach.”

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169


TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.13


DI-MISC-80508B/T


3. SUBTITLE

Software and Programmable Logic Evaluation Report (SPLER)- KMS ECU



C081

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3(c) and 3 (d). Contents. Delete entirely and replace with the following: (1) "Section 2.8, pg. 18 – 21, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as a reference for specific content and format requirements for this CDRL.” (2) “The monthly report shall provide results in the following areas as they become available: i) Units of code under development shall be analyzed with static analysis tools; errors/warnings shall be addressed and documented. ii) Integrated modules of code shall be analyzed with static analysis tools; errors/warnings shall be addressed and documented. iii) Compiled/linked code shall be analyzed with analysis tools; errors/warnings shall be addressed and documented. (iv) Reused code shall be analyzed with static analysis tools. See Software Analysis and Assessment Process Document (SAAPD) for further guidance." (3) “The Initial Software and Programmable Logic Evaluation Report (SPLER) shall include the most current results and the date of the last run of static analysis tool, and shall include at a minimum the following information: i) Type of product evaluated, such as software or programmable logics. ii) Version/Build description. iii) List of tools or analysis used. iv) For each tool or analysis, provide a final analysis of the software (S/W) issues cited in Section 2.4.1 of the NSAs TSRD. v) All identified security critical defects shall be mitigated. In addition, the report shall identify security related code units and associated defects. All identified security related defects shall be mitigated. When it is not possible to mitigate security related defects, a justification is needed for each unmitigated defect.” (4) “The second SPLER Report is required at the completion of the software/programmable logic integration phase where the software and programmable logics are integrated with the host hardware. The report shall include the most current results and the date of the last run of static analysis tool, and shall include at a minimum the following information: i) Type of product evaluated, such as software or programmable logics. ii) Version/Build description. iii) List of tools or analysis used. iv) For each tool or analysis, provide a final analysis of the S/W Issues

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) cited in Section 2.4.1 of the NSAs TSRD and a statement of how the Contractor plans to fix the issues. v) All software related Information Assurance System Requirements Document (IASRD) requirement not fully met shall be addressed in the report to include plans to correct the code or identify mitigations. When it is not possible to mitigate defects, a justification is needed for each unmitigated defect. It is at this point that the Program Management Office (PMO) shall assist in the mitigation of defects or consult with the Adjudicator in order to assess risk. vi) Software/firmware test report. vii) Provide a copy of the Source and Executable Software Code with instructions where the data represents the code." 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 update 30 calendar days (CD) before Test Readiness Review (TRR). b. Submit update after integration test. c. Submit final 30 CD after Physical Configuration Audit (PCA). This delivery shall include the as-built Source and Executable Software Code with instructions that represent the final signed-software. d. Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.14


DI-MISC-80508B/T


3. SUBTITLE Software and Programmable Logic Evaluation Report (SPLER) - Joint Hub ECU



C082

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements. Paragraph 3(c) and 3(d). Contents. Delete entirely and replace with the following: "Section 2.8, pg. 18 – 21, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as a reference for specific content and format requirements for this CDRL.” (1) “The monthly report shall provide results in the following areas as they become available: i) Units of code under development shall be analyzed with static analysis tools; errors/warnings shall be addressed and documented. ii) Integrated modules of code shall be analyzed with static analysis tools; errors/warnings shall be addressed and documented. iii) Compiled/linked code shall be analyzed with analysis tools; errors/warnings shall be addressed and documented. iv) Reused code shall be analyzed with static analysis tools. See Software Analysis and Assessment Process Document (SAAPD)for further guidance.” (2) “The Initial Software and Programmable Logic Evaluation Report (SPLER) shall include the most current results and the date of the last run of static analysis tool, and shall include at a minimum the following information: i) Type of product evaluated, such as software or programmable logics. ii) Version/Build description. iii) List of tools or analysis used. iv) For each tool or analysis, provide a final analysis of the software (S/W) issues cited in Section 2.4.1 of the NSAs TSRD v) All identified security critical defects shall be mitigated. In addition, the report shall identify security related code units and associated defects. All identified security related defects shall be mitigated. When it is not possible to mitigate security related defects, a justification is needed for each unmitigated defect.” (3) “The second SPLER Report shall be required at the completion of the software/programmable logic integration phase where the software and programmable logics are integrated with the host hardware. The report shall include the most current results and the date of the last run of static analysis tool, and shall include at a minimum the following information: i) Type of product evaluated, such as software or programmable logics. ii) Version/Build description. iii) List of tools or analysis used.

16. REMARKS



17. PRICE GROUP


of 169

16. REMARKS (Continued) iv) For each tool or analysis, provide a final analysis of the S/W Issues cited in Section 2.4.1 of the NSAs TSRD and a statement of how the Contractor plans to fix the issues. v) All software related Information Assurance Systems Requirements Document (IASRD) requirement not fully met shall be addressed in the report to include plans to correct the code or identify mitigations. When it is not possible to mitigate defects, a justification is needed for each unmitigated defect. It is at this point that the Program Management Office (PMO) shall assist in the mitigation pf defects or consult with the Adjudicator in order to assess risk. vi) Software/firmware test report. vii) Provide a copy of the Source and Executable Software Code with instructions where the data represents the code." 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 update 30 calendar days (CD) before Test Readiness Review (TRR). b. Submit update after integration test. c. Submit final 30 CD after Physical Configuration Audit (PCA). This delivery shall include the as-built Source and Executable Software Code with instructions that represent the final signed-software. d. Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCEC6. REQUIRING OFFICE

3.4.1.1.1.b.17


DI-SESS-81646B/T


3. SUBTITLE

Physical Configuration Audit Plan (PCAP) - KMS ECU

Configuration Audit Plan


C083

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information.” (2) “All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." b. Requirements. Paragraph 3. Content. Add: "Section 2.10, pg. 26 – 27, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance." 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 60 calendar days (CD) prior to Physical Configuration Audit (PCA). b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCEC

6. REQUIRING OFFICE

3.4.1.1.1.b.18


DI-SESS-81646B/T


3. SUBTITLE

Physical Configuration Audit Plan (PCAP) - Joint Hub ECU

Configuration Audit Plan


C084

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Replace all references to “Computer Software Configuration Item (CSCI)” with “Software Item.” b. Requirements. Paragraph 2. Format. Add: (1) “All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information.” (2) “All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader.” (3) “All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats.” b. Requirements. Paragraph 3. Content. Add: “Section 2.10, pg. 26 - 27, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as a guidance.” 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 60 calendar days (CD) prior to Physical Configuration Audit (PCA). b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCEC

6. REQUIRING OFFICE

3.4.1.1.1.b.19


DI-SESS-81022D/T


3. SUBTITLE

Physical Configuration Audit Report (PCAR) - KMS ECU

Physical Configuration Audit Report and Certification


C085

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Add: "Upon completion of each Physical Configuration Audit (PCA), the Contractor shall provide the National Security Agency (NSA) with a Physical Configuration Audit Report containing: i) Audit identification including the name and nomenclature of the system. ii) Sub-system, equipment, parts; name of the Vendor, and date the PCA was conducted. iii) List of all documentation subjected to the PCA, along with agreed-upon revision levels, assembly description, SW/FW/HDL identification numbers and serial numbers. iv) List of discrepancies found during the PCA and a description of how the discrepancy shall be specifically resolved including actual or projected completion date. v) List of all unincorporated changes in drawing/software (SW)/Firmware (FW)/HDL number order." b. Requirements. Paragraph 2. Format. Add: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." c. Requirements. Paragraph 3. Contents. Add: "Section 2.10, pg. 26 – 27, of the NSA TSRD shall be used as guidance." 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 15 calendar days (CD) after Physical Configuration Audit (PCA). b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

SMC/MCEC

6. REQUIRING OFFICE

3.4.1.1.1.b.20 5. CONTRACT REFERENCE

DI-SESS-81022D/T


3. SUBTITLE

Physical Configuration Audit Report (PCAR) - Joint Hub ECU

Physical Configuration Audit Report and Certification


C086

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Add: "Upon completion of each Physical Configuration Audit (PCA), the Contractor shall provide the National Security Agency (NSA) with a Physical Configuration Audit Report containing: i) Audit identification including the name and nomenclature of the system ii) Sub-system, equipment, parts; name of the Vendor, and date the PCA was conducted iii) List of all documentation subjected to the PCA, along with agreed-upon revision levels, assembly description, SW/FW/HDL identification numbers and serial numbers iv) List of discrepancies found during the PCA and a description of how the discrepancy shall be specifically resolved including actual or projected completion date v) List of all unincorporated changes in drawing/software (SW)/Firmware (FW)/HDL number order" b. Requirements. Paragraph 2. Format. Add: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." c. Requirements. Paragraph 3. Contents. Add: "Section 2.10, pg. 26 – 27, of NSAs TSRD shall be used as guidance." 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 15 calendar days (CD) after Physical Configuration Audit (PCA). b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

6. REQUIRING OFFICE



3. SUBTITLE

RESERVED


C087

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER

C B. EXHIBIT






8. APP CODE

7. DD 250 REQ



11. AS OF DATE


10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

16. REMARKS

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

6. REQUIRING OFFICE



3. SUBTITLE

RESERVED


C088

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






8. APP CODE

7. DD 250 REQ



11. AS OF DATE


10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

16. REMARKS

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.21


DI-EMCS-81683/T


3. SUBTITLE

TEMPEST Test Plan - KMS ECU

TEMPEST Test Plan


C089

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER EMCS

C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information. (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." b. Requirements. Paragraph 3. Content. Add: " Section 2.11.2, pg. 28, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance." c. Requirements. Paragraph 3(c) and 3(d). Content. Delete in its entirely and replace with the following: "North Atlantic Treaty Organization (NATO) Standard SDIP-27 Level B." 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 60 calendar days (CD) prior to the first day of Telecommunications Electronics Material Protected from Emanating Spurious Testing (TEMPEST). b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.22


DI-EMCS-81683/T


3. SUBTITLE

TEMPEST Test Plan - Joint Hub ECU

TEMPEST Test Plan


C090

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information.” (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." b. Requirements. Paragraph 3. Content. Add: "Section 2.11.2, pg. 28, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance." c. Requirements. Paragraph 3(c) and 3(d). Content. Delete in its entirely and replace with the following: "North Atlantic Treaty Organization (NATO) Standard SDIP-27 Level B." 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 60 calendar days (CD) prior to the first day of Telecommunications Electronics Material Protected from Emanating Spurious Testing (TEMPEST). b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.23


DI-EMCS-81684/T


3. SUBTITLE

TEMPEST Test Report - KMS ECU

TEMPEST Test Report


C091

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." b. Requirements. Paragraph 3. Content. Add: "Section 2.11.3, pg. 28, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance." c. Requirements. Paragraph 3(c) and 3(d). Content. Delete entirely and replace with the following: "North Atlantic Treaty Organization (NATO) Standard SDIP-27 Level B." 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 15 calendar days (CD) after the last day of Telecommunications Electronics Material Protected from Emanating Spurious Testing (TEMPEST). b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.24


DI-EMCS-81684/T


3. SUBTITLE

TEMPEST Test Report - Joint Hub ECU

TEMPEST Test Report


C092

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." b. Requirements. Paragraph 3. Content. Add: " Section 2.11.3, pg. 28, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance.” c. Requirements. Paragraph 3(c) and 3(d). Content. Delete entirely and replace with the following: "North Atlantic Treaty Organization (NATO) Standard SDIP-27 Level B." 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 15 calendar days (CD) after the last day of Telecommunications Electronics Material Protected from Emanating Spurious Testing (TEMPEST). b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.25


DI-QCIC-81691A/T


3. SUBTITLE

In-Process Accounting Procedures Plan - KMS ECU

In-Process Accounting Procedures Plan


C093

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 3. Contents. Add: "Section 2.12.1, pg. 28 – 29, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance." b. Requirements. Paragraph 2. Format. Add: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." 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 60 calendar days (CD) prior to the manufacturing of development and/or production hardware. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.26


DI-QCIC-81691A/T


3. SUBTITLE

In-Process Accounting Procedures Plan -Joint Hub ECU

In-Process Accounting Procedures Plan


C094

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 3. Contents. Add: " Section 2.12.1, pg. 28 – 29, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance." b. Requirements. Paragraph 2. Format. Add: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." 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 60 calendar days (CD) prior to the manufacturing of development and/or production hardware. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.27


DI-QCIC-81722/T


3. SUBTITLE

Security Production Assurance (SPA) Description- KMS ECU

Quality Program Plan (QPP)


C095

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." b. Requirements. Paragraph 3. Contents. Add: (1) "The SPA shall address the following: i) Both the Physical Configuration and the Functional Performance of the product/system. ii) The complete manufacturing process, including sub-contracted portions, if any, and identify the essential hardware (HW)/software (SW)/platform (PL) security checkpoints, making reference to the Contractor's documents that provide the criteria of inspection and test which validate and protect the security integrity of the product/system." (2) "The Security Production Assurance (SPA) Description shall contain (at a minimum) the following: i) Organizational Structure Block Diagram including key personnel/key elements in order to identify and facilitate points of contact in accordance with (IAW) paragraph 3.5 of the data item description (DID) DI-QCIC-81722. ii) Product/System Flow Diagram that identifies the HW/SW security inspection/test checkpoints, and references applicable Contractor documents that specify inspection and test criteria/procedures used throughout the manufacturing process IAW paragraph 3.6 of data item description (DID) DI-QCIC-81722. The flow diagram, as a minimum, shall include the following: (a) A list of the types of inspection and testing that the Contractor plans to perform during the manufacture and assembly of the product/system (b) A list of the security features that shall be tested and a description stating how the Contractor plans to implement the test(s). (Note: do not include a detailed description of the test setup, test equipment, and/or procedures followed)" iii) The product Acceptance Test Specification (ATS) drawing or document that shall describe the Production Acceptance Test Plans." (3) "The Contractor shall ensure the document is maintained and in a current status." (4) "Section 2.13, pg. 29, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance."

16. REMARKS

See Distro List



17. PRICE GROUP


of 169


TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.28


DI-QCIC-81722/T


3. SUBTITLE Security Production Assurance (SPA) Description - Joint Hub ECU

Quality Program Plan (QPP)


C096

1. DATA ITEM NO.

F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (2) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." (3) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." b. Requirements. Paragraph 3. Contents. Add: (1) "The Security Production Assurance (SPA) Description shall address the following: i) Both the Physical Configuration and the Functional Performance of the product/system. ii) The complete manufacturing process, including sub-contracted portions, if any, and identify the essential hardware (HW)/software (SW)/platform (PL) security checkpoints, making reference to the Contractor's documents that provide the criteria of inspection and test which validate and protect the security integrity of the product/system." (2) "The SPA Description shall contain, at a minimum, the following: i) Organizational Structure Block Diagram including key personnel/key elements in order to identify and facilitate points of contact in accordance with (IAW) paragraph 3.5 of the data item description (DID) DI-QCIC-81722. ii) Product/System Flow Diagram that identifies the HW/SW security inspection/test checkpoints, and references applicable Contractor documents that specify inspection and test criteria/procedures used throughout the manufacturing process IAW paragraph 3.6 of DID DI-QCIC-81722. The flow diagram, as a minimum, shall include the following: (a) A list of the types of inspection and testing that the Contractor plans to perform during the manufacture and assembly of the product/system (b) A list of the security features that shall be tested and a description stating how the Contractor plans to implement the test(s). (Note: do not include a detailed description of the test setup, test equipment, and/or procedures followed)" iii) The product Acceptance Test Specification (ATS) drawing or document that shall describe the Production Acceptance Test Plans." (3) "The Contractor shall ensure the document is maintained and in a current status." (4) "Section 2.13, pg. 29, of the National Security

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance." 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): Update as required or by Procurement Contracting Officer (PCO) direction.

F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

SMC/MCLA

6. REQUIRING OFFICE

3.4.1.1.1.b.29


DI-SESS-81000E


3. SUBTITLE

Product Drawings/Models and Associated Lists - KMS ECU



C097

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY


16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCLA

6. REQUIRING OFFICE

3.4.1.1.1.b.30


DI-SESS-81000E


3. SUBTITLE

Product Drawings/Models and Associated Lists - Joint Hub ECU



C098

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY


16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

6. REQUIRING OFFICE



3. SUBTITLE

RESERVED


C099

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






8. APP CODE

7. DD 250 REQ



11. AS OF DATE


10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

16. REMARKS



17. PRICE GROUP


of 169

6. REQUIRING OFFICE



3. SUBTITLE

RESERVED


C100

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






8. APP CODE

7. DD 250 REQ



11. AS OF DATE


10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

16. REMARKS

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.31


DI-MGMT-81717D/T


3. SUBTITLE Information Systems Security (INFOSEC) Anonymity Plan (IAP) - KMS ECU

Information Systems Security (INFOSEC) Anonymity Plan (IAP)


C101

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." (2) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (3) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements: Paragraph 3. Content. Add: "Section 2.16, pg. 30, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance." 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 final 6 calendar days (0 )CD prior to procurement from sources outside the United States. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.4.1.1.1.b.32


DI-MGMT-81717D/T


3. SUBTITLE

Information Systems Security (INFOSEC) Anonymity Plan (IAP) - Joint Hub ECU

Information Systems Security (INFOSEC) Anonymity Plan (IAP)


C102

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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: (1) "All pictures and diagrams shall be converted to Joint Photographic Experts Group (JPG) or similar formats." (2) "All electronic deliveries shall be without restrictions that would prevent the Government from reproducing or editing the information." (3) "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." b. Requirements: Paragraph 3. Content. Add: "Section 2.16, pg. 30, of the National Security Agency’s (NSAs) Technical Security Requirements Document (TSRD) shall be used as guidance." 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 final 60 calendar days (CD) prior to procurement from sources outside the United States. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-IPSC-81431A/T


3. SUBTITLE

Segment Specification - KMS ECU



C103

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 Instructions. Add: (1) "Main volume shall be unclassified with reference to a separate classified Appendix." (2) "Classified portions of this data item shall be submitted in accordance with (IAW) Department of Defense form DD-254 and instructions contained in the CDRL instructions of this document." b. Requirements. Paragraph 3. Format. Add: "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." c. Requirements. Paragraph 4.a. Title page or identifier. Add: "Revision Control Page. The revision control page shall list the following information: (1) Each revision letter. (2) Date of each revision. (3) Pages affected by each revision and a description of the change(s)." 2. (BLK 5): 1.3.2.1.2.1.f; 1.3.3.1.2.1.f; 1.3.3.2.c; 1.4.1.1.2.a.1; 1.4.1.2.d; 1.4.1.2.1.g; 1.4.7.1.c; 1.4.8.1.b; 3.1.2.5.a.1; 5.4.1.2.1.d 3.(BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CDRL C041) and Specification Change Notice (SCN) (CDRL C028) as required. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-IPSC-81431A/T


3. SUBTITLE

Segment Specification- Joint Hub ECU



C104

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 Instructions. Add: (1) "Main volume shall be unclassified with reference to a separate classified Appendix." (2) "Classified portions of this data item shall be submitted in accordance with (IAW) Department of Defense form DD-254 and instructions contained in the CDRL instructions of this document." b. Requirements. Paragraph 4.a. Title page or identifier. Add: "Revision Control Page. The revision control page shall list the following information: (1) Each revision letter. (2) Date of each revision. (3) Pages affected by each revision and a description of the change(s)." 2. (BLK 5): 1.3.2.1.2.1.f; 1.3.3.1.2.1.f; 1.3.3.2.c; 1.4.1.1.2.a.1; 1.4.1.2.d; 1.4.1.2.1.g; 1.4.7.1.c; 1.4.8.1.b; 3.1.2.5.a.1; 4.4.1.2.2.a.1; 5.4.1.2.1.d 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CDRL C041) and Specification Change Notice (SCN) (CDRL C028) as required. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-IPSC-81431A/T


3. SUBTITLE

PTES Segment Specification - Joint Hub



C105

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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 Instructions. Add: (1) "Main volume shall be unclassified with reference to a separate classified Appendix." (2) "Classified portions of this data item shall be submitted in accordance with (IAW) Department of Defense form DD-254 and instructions contained in the CDRL instructions of this document." b. Requirements. Paragraph 3. Format. Add: "All submissions shall be in electronic format compatible with Microsoft Office Suite 2010, Microsoft Project 2010, and Adobe Acrobat Reader." c. Requirements. Paragraph 4.a. Title page or identifier. Add: "Revision Control Page. The revision control page shall list the following information: i) Each revision letter ii) Date of each revision iii) Pages affected by each revision and a description of the change(s)" 2. (BLK 5): 1.3.2.1.2.1.f; 1.3.3.1.2.1.f; 1.3.3.2.c; 1.4.1.1.2.a.1; 1.4.1.2.d; 1.4.1.2.1.g; 1.4.7.1.c; 1.4.8.1.b; 3.1.2.5.a.1; 4.4.1.2.2.a.1; 5.4.1.2.1.d 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for final submittal(s) only. 4. (BLKs 10, 12, 13): a. Submit update 30 calendar days (CD) after Government approval of Engineering Change Proposal (ECP)/Contract Change Proposal (CDRL C041) and Specification Change Notice (SCN) (CDRL C028) as required. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

System Level Test Readiness Review Briefing



C106

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






BLK 16 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace 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 (IAW) the 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 focus on Protected Tactical Enterprise Service (PTES) development using Agile Software Development, and shall be written to be compliant with the PTES System Engineering Plan (SEP). 2. (BLK 5): 1.1.2.1.e; 3.1.2.4.b; 3.1.2.4.g.3; 3.1.2.4.g.4; 3.4.1.2.1.c 3. (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. 4. (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.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.1.2.4.d


DI-MISC-80508B/T


3. SUBTITLE

Modem Certification Data Package



C107

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Requirements. Paragraph 3. Contents. Delete in its entirety and replace with the following: "The Modem Certification Data Package shall be submitted in accordance with (IAW) U.S. Army Space and Missile Defense Command/Army Forces Strategic Command (USASMDC/ARSTRAT) Multi-Frequency Time Division Multiple Access (MF-TDMA) Certification Welcome Package or its replacement." 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 60 calendar days (CD) prior to a test event requiring USASMDC/ARSTRAT approval and certification. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCLA

6. REQUIRING OFFICE

3.1.4.13.a


DI-ILSS-80739


3. SUBTITLE

Depot Maintenance Study


C108

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER ILSS

C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

1. (BLKs 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCLA

6. REQUIRING OFFICE

3.1.4.16.c


DI-SESS-81254C


3. SUBTITLE

Request for Nomenclature (DD Form 61)


C109

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

1. (BLKs 10, 12, 13): Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCLA

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

Installation, Operation, Support, and Maintenance Manuals



C110

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace with the following: “Contractor’s format is acceptable.” b. Superseded if optional Training contract line item number (CLIN) is exercised. 2. (BLK 5): 3.1.4.9.c; 3.1.4.16.d; 3.3.2.4.2.e; 3.3.3.4.2.d; E.9b)(11)(vi) 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): a. Submit initial 90 calendar days (CD) prior to Milestone (MS)-C. b. Submit update 90 CD prior to system delivery for Operational testing. c. Submit updates as required for Hardware (HW) upgrades and Operational releases for Builds 5 thru 8 and Release 2. d. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCLA

6. REQUIRING OFFICE

BLK 16


DI-TMSS-80527C/T


3. SUBTITLE

Commercial Off-The-Shelf (COTS) Manual and Associated Supplemental Data


C111

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER TMSS

C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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): Superseded if optional Training contract line item number (CLIN) is exercised. 2. (BLK 5): 3.1.4.9.d; 3.1.4.16.d 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): a. Submit initial 90 calendar days (CD) prior to Milestone (MS)-C. b. Submit update 90 CD prior to system delivery for Operational testing. c. Submit updates as required for Hardware (HW) upgrades and operational releases for Builds 5 thru 8 and Release 2. d. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCLA

6. REQUIRING OFFICE

BLK 16


DI-ILSS-80872/T


3. SUBTITLE

Training Materials


C112

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER ILSS

C B. EXHIBIT






A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Superseded if optional Training contract line item number (CLIN) is exercised. b. BLK 10. Preparation Instructions. Paragraph 10.2.1.2. Clinical Application. Delete in its entirety. 2. (BLK 5): 3.1.4.9.e.1; 3.1.4.16.d; 3.3.2.4.2.e; 3.3.3.4.2.d 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): a. Submit initial 90 calendar days (CD) prior to start of training for Multi-service Operational Test and Evaluations (MOT&E). b. Submit update 90 CD prior to start of training for Multi-service Operational Test and Evaluations 2 (MOT&E-2). c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCLA

6. REQUIRING OFFICE

3.1.4.14.a; 3.1.4.16.g.2


DI-SESS-81639A


3. SUBTITLE

Warranty Performance Report


C113

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

1. (BLKs 10, 12, 13): a. Submit initial 30 calendar days (CD) after warranty return for repair. b. Subsequent submittals shall be made quarterly starting 30 CD after initial delivery. c. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

6. REQUIRING OFFICE



3. SUBTITLE

RESERVED


C114

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






8. APP CODE

7. DD 250 REQ



11. AS OF DATE


10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE

I. APPROVED BY

H. DATE

G. PREPARED BY

16. REMARKS

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

3.1.1.11.b


DI-MISC-80508B/T


3. SUBTITLE

IDE Database



C115

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace with the following: "Data shall be delivered on Compact Disk, Digital Versatile Disc (DVD), or external hard drive. Blue-Ray disks may not be used.” b. Requirements. Paragraph 3. Contents. Delete in its entirety and replace with the following: (1) "All data developed on the program that is stored in the Integrated Digital Environment (IDE) shall be delivered to the Government as a DAL (CDRL C004) item." (2) "At a minimum, the IDE database shall contain documentation that makes up products that are non-CDRL items that make up the product baseline, peer reviews, executive reviews, independent program reviews, assessments, inspections, trade studies, memos, reports, test reports, flow diagrams, computer support software, configuration control list of all NDI software used, free and open-source software (FOSS), interim versions of software work products, as-built configuration list, plans, procedures, risk information from the risk database, Security Technical Information Guides (STIG), Original Equipment Manufacturer (OEM) test status, staffing plans, informal meeting minutes, DoD Information Technology Standards Registry (DISR) questionnaire, analysis and simulations, action items, liens, Dynamic Object Orientation Requirements System (DOORS) modules, Problem Reports, discrepancy reports, product backlogs, spring backlogs, configuration records, and all other documents generated to support the program.” 2. (BLKs 10, 12, 13): a. Submit 30 calendar days (CD) prior to the end of the contract period of performance. b. Update as required or by Procurement Contracting Officer (PCO) direction.

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


of 169

SMC/MCDP

6. REQUIRING OFFICE

BLK 16


DI-MISC-80508B/T


3. SUBTITLE

Reliability and Maintainability Reports



C116

1. DATA ITEM NO.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT






N/A 8. APP CODE

LT

7. DD 250 REQ

D



BLK 16

11. AS OF DATE

N/A

BLK 16


BLK 16

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. Delete in its entirety and replace with the following: "Contractor's format is acceptable." b. Requirements. Paragraph 3(d). Contents. Delete in its entirety and replace with the following: (1) "The Reliability and Maintainability Reports shall be delivered in three volumes: i) Vol 1 - Reliability and Maintainability (R&M) Block Diagrams and Mathematical Models Report ii) Vol 2 - Reliability Test Report iii) Vol 3 - Maintainability and Built in Test Demonstration Report" (2) "Volume 1 (Reliability and Maintainability (R&M) Block Diagrams and Mathematical Models Report) shall include the following: i) R&M block diagrams and mathematical models and supplementary information suitable for allocation, prediction, assessment, and Failure Mode, Effects, and Criticality Analysis (FMECA) analysis related to the configuration items (including software configuration items) of the systems work breakdown structure. The R&M block diagrams and math models shall be developed to the level required and contain the detail required to support these analyses, in order to avoid duplication of effort across analyses. ii) The type of reliability model (mission or logistics) and the modeling method. iii) The type of functional level maintainability block diagram depicting the levels at which the repair can be made. iv) Reference designation list when warranted by system complexity. The list shall be provided when block diagrams include elements which require correlation between block diagram reference numbers, work breakdown structure identification, or location of specific elements on a diagram set or diagram sheet. The list shall be a composite cross-reference and item element locator (both by name and designation). v) An excluded equipment list which describes system elements not shown on the block diagram. Rationale for each exclusion shall be provided. vi) Identification of the technical assumptions used, including: (a) Service use profile, mission profile, environmental profile (b) Operational and maintenance concepts and requirements (c) Levels to which fault detection and fault isolation is to be extended (d) Redundancy, alternate modes of degraded operation (e) Tradeoff considerations (f) Human interface and software vii) R&M block diagrams that: (a) Represent the system specification and are segmented to represent variables such as: mission type, mission phase, functional mode(s) of operation, duty cycle, maintenance concept, or other factors. When information is limited in the early phase of item development, functional level block diagrams shall be constructed. Diagrams constructed at this level shall contain blocks representing the lowest identifiable function consistent with item element

16. REMARKS

See Distro List



17. PRICE GROUP


of 169

16. REMARKS (Continued) definition (name and designation). (b) Include and identify blocks representing Government Furnished Equipment (GFE), Non-Developmental Items (NDI), and Commercial-Off-The-Shelf (COTS) items. Information shall be included to reflect the use of designated GFE, NDI, and COTS into the design. (c) Are partitioned to agree with the work breakdown structure. Partitioning shall provide diagrams for each configuration item subdivision which reflect and emphasize interfaces with the next lower level of the breakdown structure. In this manner, the block diagram consists of a series of models which are logically derived and capable of being combined to any level of complexity. (d) Indicate interfaces both external to the physical boundary of the item and internal to the item. Particular attention should be paid to interfaces of functional significance including GFE, NDI, and COTS. Interfaces shall be consistent with end item specification, intended purpose, mission use, or higher order functions when the item is used in conjunction with other items. (e) Identify critical items in the system design. (f) Identify in maintainability diagrams which elements are to be designed as repairable or replaceable items for maintainability enhancement. In addition, Built-In-Test (BIT) design expectations (e.g. fault detection, fault isolation), along with test equipment needs for on-line and off-line testing, shall be indicated. viii) Configurations identified during redundancy studies, allocations, or tradeoff studies related to item reliability improvement. Reliability problems leading to the inclusion of redundant elements shall be identified. Additional information describing redundancy considerations not obvious from the block diagrams shall be included. Typical redundancy considerations include: (a) Level (e.g., subsystem, part) (b) Type (e.g., active, standby, M out of N) (c) Element monitoring (e.g., continuous, interval monitored) (d) Rationale (e.g., repair without downtime, prolong operating life) (e) Alternatives with/without redundancy (f) Elements which can be checked (g) Elements which can be inspected (h) Elements whose failure stresses alternate path elements (i) Elements whose failure degrades performance ix) Mathematical models that: (a) Include technical assumptions necessary for model interpretation, model completeness, and model clarity. Assumptions shall be consistent with the phase of item definition, such as frequency distributions (failure rate, time to repair), mathematical approximations, statistical techniques, single mode/multimodal failure, wear out factors/characteristics, failure independency, and operating time. (b) Represent the system specification the level of details, and be organized consistent with the R&M block diagrams. Charts, tables, or other methods may be used to indicate which equation, model, or sets of models apply to specific mission(s) or other variables. The method used shall be the same used for block diagrams, and may include provisions for both the diagram and mathematical model. (c) Supplementary information necessary for proper understanding and use of the model shall be included when specific method(s) of mathematics employed extend beyond the basic rules, practices, and procedures of reliability mathematics (e.g., rules of Boolean algebra, classical laws of reliability, etc.). x) Conclusions and recommendations based upon the data developed. Interpretation and comments concerning diagrams, models, and courses of action to resolve R&M problems shall be included. Consideration should be given to data deficiencies, Government Furnished Equipment (GFE) problems, tradeoffs, assumptions, risks, interpretations affecting R&M planning, qualitative or quantitative information affecting the program, and other pertinent factors related to the diagrams or models." (3) "Volume 2 (Reliability Test Report) shall include the following: i) The results of each test or other action taken to demonstrate the level of reliability achieved in the contract end item and its constituent elements required by the contract. The reports shall specifically contain the following: (a) Test article identification and full description of test specimens utilized, including any deviations for the configuration specified in the applicable test plan. (b) Date and location of test or evaluation. (c) Statement of test/evaluation objectives, including type, unit of measure and Quantitative goals/requirements to be demonstrated. (d) Statistical confidence calculations, if applicable. (e) Discussion of methods and conditions of the demonstration, including test plan used, environmental levels, test profile, methods of evaluating the data obtained and comparison of the conditions with those anticipated in ultimate deployment and use of contract item. (f) Results obtained, including specific identification and discussion of objectives demonstrated satisfactorily and those not demonstrated satisfactorily. (g) Corrective action anticipated, if applicable. (h) Contractors conclusion and recommendations based on evaluation of the test/ demonstration results. (i) Requirements for and results of retest in cases where a reject decision was reached. ii) Summary Reports. Periodic Test Summary Reports shall consist of summaries of the progress or status of various reliability tests underway during the reporting period. All periodic summaries shall include the following:

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT




of 169

16. REMARKS (Continued) (a) Type and number of units on test and the type of test. (b) Total elapsed unit hours of test time during the period covered in the report. (c) Total number of equipment failures for each operational mode specified in the duty cycle. (d) Description of each failure problem area, related failure analysis, and correction action. (e) Test conditions and analysis of any variation from specified conditions. (f) Present accept/reject status. (g) A chart showing a plot of the observed Mean Time between Failures (MTBF) from start of test through the report period and the predicted value of MTBF for comparison. (h) The status and/or disposition of each corrective action." iii) Final Report. The Final Reliability Test Report shall include the information required by the Summary Report, item a. through h., and the results of the completed reliability tests or other action performed or evaluated to demonstrate reliability. The Final Report shall be divided into two parts: Part 1, covering Reliability Acceptance Tests and Part 2, covering Production reliability Tests. Test reports shall include a failure summary and analysis and a general reliability analysis. iv) It is intended that the text of these reports be limited to brief, concise statements of significant progress and present status." (4) "Volume 3 (Maintainability and Built in Test Demonstration Report) shall include the following: i) The results of each demonstration or test to demonstrate the maintainability/BIT achieved. The report shall contain the following: (a) Description of demonstration or test performed. (b) Statement of test objectives, including type, unit of measure and quantitative goals or requirements to be demonstrated, including specific references to the applicable Sections of the specification. (c) A list of all units that were placed on test during the demonstration, including any deviations from the configuration specified in the applicable test plan, and the detailed reason for each deviation. (d) Date and location of demonstration or test. (e) Discussion of methods and conditions of the demonstration or test, including test plan and procedure used, source of inserted faults (i.e., revision and date of fault catalog), environmental and use conditions, operational and performance profiles, measurements, methods of evaluating the data obtained and comparison of the conditions with those anticipated in ultimate deployment and use of the contract item. (f) Results obtained, including specific identification and discussion of objectives demonstrated satisfactorily and those not demonstrated satisfactorily. (g) Factors which influenced the results (i.e., inserted fault sample size deviation from plan). (h) Statistical confidence calculations, if applicable. (i) Assessment of the technical manuals, personnel, tools and test equipment, support equipment, maintenance concept and provisioning for their effect on quantitative and qualitative demonstrated maintainability and Built-In-Test (BIT) parameters. (j) Test incident reports, deficiencies, or failure reports generated and corrective action anticipated, if applicable. (k) Contractors conclusion and recommendations based on evaluation of the results. (l) Requirements for retest in cases where a reject decision was reached. (m) Results of retest, if applicable. (n) Analysis and supporting data. (o) Data sheets." 2. (BLK 5): 1.1.4.3.c; 3.1.4.10.c; 3.1.4.11.b; 3.3.2.4.2.e; 3.3.3.4.2.d 3. (BLK 8): a. Government approval shall be by Contractual Document Action (CDA). b. Government approval shall be required for each submission. 4. (BLKs 10, 12, 13): a. Submit consolidated report 30 calendar days (CD) after the start of each Government test event. b. Update as required or by Procurement Contracting Officer (PCO) direction.

TBD F. CONTRACTOR


PTES D. SYSTEM/ITEM

TDP


C B. EXHIBIT



of 169


SMC/MCLA 6. REQUIRING OFFICE 1.1.1.14.g; 1.1.1.14.p

5. CONTRACT REFERENCE DI-MISC-80508B/T 4. AUTHORITY (Data Acquisition Document No.)

3. SUBTITLE

Hardware/Software List Technical Report-Study/Services 2. TITLE OF THE DATA ITEM C117

1. DATA ITEM NO.

TBD F. CONTRACTOR FA8808-17-R-0006

E. CONTRACT/PR NO. PTES D. SYSTEM/ITEM

TDP

C. CATEGORY TM OTHER MISC C

B. EXHIBIT A. CONTRACT LINE ITEM NO. CLIN 0003



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

(1 Data Item)

A 8. APP CODE

LT 7. DD 250 REQ

D


13 DATE OF SUBSEQUENT SUBMISSION

BLK 16 11. AS OF DATE

N/A

BLK 16

12 DATE OF FIRST SUBMISSION BLK 16

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): Requirements. Paragraph 3. Contents. Add: (1) "The Hardware/Software List shall include: i) complete information of each product (not limited to make, model, serial number, revision, firmware, etc.). ii) information on how the contractor will integrate hardware and software used to meet requirements from Technical Requirements Document(s) (TRDs) into the engineering processes, products, system and components.

iii) information on how the contractor evaluated and the results of the software (COTS / Freeware / OSS) and shareware to ensure they do NOT pose a component or system risk.” (2) “The Hardware/Software List shall demonstrate how the contractor will deliver a system that is Risk Management Framework (RMF) cybersecurity control compliant and supply chain control."

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 update 45 CD prior to Test Readiness Review (TRR).

b. Submit update 45 calendar days (CD) prior to Contractor Program Management

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

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP

of 169


SMC/MCLA 6. REQUIRING OFFICE 1.1.1.14.q


3. SUBTITLE

Ports, Protocols and Services (PPS) Technical Report-Study/Services 2. TITLE OF THE DATA ITEM C118

1. DATA ITEM NO.



TDP

C. CATEGORY TM OTHER MISC C

B. EXHIBIT A. CONTRACT LINE ITEM NO. CLIN 0003




(1 Data Item)

A 8. APP CODE

LT 7. DD 250 REQ

D




N/A

BLK 16


10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE


1. (BLK 4): Requirements. Paragraph 3. Contents. Add: (1) "The Ports, Protocols and Services (PPS) shall include a list of all ports, protocols and services the contractor will use and the status of each to meet government identified Risk Management Framework (RMF) controls from Technical Requirements Document(s) (TRDs) into the engineering processes, products, system and components.” (2) “The PPS shall demonstrate how the contractor will deliver a system that is RMF cybersecurity control compliant." 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 update 45 calendar days (CD) prior to Test Readiness Review (TRR). b. Submit updates quarterly thereafter.

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

16. REMARKS

See Distro List



17. PRICE GROUP

of 169


SMC/MCDP 6. REQUIRING OFFICE 1.1.1.14.m


3. SUBTITLE

Cybersecurity Architecture Diagram Technical Report-Study/Services 2. TITLE OF THE DATA ITEM C119

1. DATA ITEM NO.



TDP


C B. EXHIBIT A. CONTRACT LINE ITEM NO.

CLIN 0003


(1 Data Item)

A 8. APP CODE

LT 7. DD 250 REQ

D




N/A

BLK 16


10. FREQUENCY

Repro Reg

Final

Draft

b. COPIES

a. ADDRESSEE

14. DISTRIBUTION

J. DATE


1. (BLK 4):

Requirements. Paragraph 3. Contents. Add: (1) "The Cybersecurity Architecture Diagram shall show how the contractor will interconnect all hardware with associated software and open ports, protocols and services to comply with government identified RMF controls from Technical Requirements Document(s) (TRDs) into the engineering processes, products, system and components.” (2) “The Cybersecurity Architecture Diagram shall demonstrate how the contractor will deliver a system that is RMF cybersecurity control compliant."

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 update 45 calendar days (CD) prior to Test Readiness Review (TRR).

b. Submit updates quarterly thereafter.

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

16. REMARKS

See Distro List

0 0 0 15. TOTAL


17. PRICE GROUP


