07_Exhibit_A_CDRL_List_(29_Apr_09).docx

GPS Advanced Control Segment (OCX) Contract Data Requirements List (CDRL) and CDRL Instructions Exhibit A for

FA8807-09-R-0003

29 April 2009

1. SCOPE

These instructions supplement the GPS Control Segment (OCX) Exhibit A Contract data Requirements List (CDRL). All delivery instructions are specified on the CDRL forms or its mechanized equivalent.

2. GENERAL

The CDRL is a list of data requirements authorized for this specific procurement and are part of this contract. The CDRLs shall apply to Blocks 1.0, 2.0, and the Capability Insertion program unless otherwise stated. The CDRL form, DD Form 1423, specifies the data required to be delivered to the Government, as well as the frequency and approval requirements. The Data Item Description (DID), listed on the CDRL form, were selected from the Acquisition Streamlining and Standardization Information System (ASSIST) and provide additional direction for data preparation.

3. COMMUNICATIONS

Any correspondence related to requests for data delivery deviations and/or amendments, additions or deletions to the CDRL form shall be addressed to the Procuring Contracting Officer (PCO) with a courtesy copy to the GPS Data Management Officer (DMO).

4. CODES USED IN THE DD FORM 1423

The directions for submittal and approval of data is indicated in Blocks 7, 8, 9, 10, 11, 12, 13, or 16 of the DD Form 1423. Usually, the direction is in the form of a code (explained below). The following abbreviations/codes are either extracted from AFR 310-1 or are common usage within the Space and Missiles Center (SMC).

4.1 Block 7, DD FORM 250 Requirements

Block 7 of the CDRL form indicates whether Procurement Quality Assurance (PQA) inspections and acceptance of deliverable data by DD Form 250 is required. “Draft” copies submitted for advance approval and “Preliminary Draft” copies submitted are exempt from the DD Form 250 requirements. Information copies of DD Form 250 to accompany each letter of transmittal for this category of data.

4.2 Block 8, Approval Code

4.3 Block 10, Frequency of Submittals

* When ASREQ is used in Blocks 10, 11, 12 or 13 and explanation of the requirements must be entered in Block 16.

4.4 Blocks 12 and 13, Dates of Initial and Subsequent Submissions

* When ASREQ is used in Blocks 10, 11, 12 or 13 and explanation of the requirements must be entered in Block 16.

5. SUPPLEMENTAL DATA PREPARATION INSTRUCTIONS

5.1 Data Item Description (DID) Tailoring

The DID is a specification for the preparation of data. DID tailoring is reflected in Block 16 of the CDRL form. “T” entered after the DID number in Block 4, means that the DID has been tailored. Block 4 tailoring is made to either relax preparation instructions or to tailor the DID to be in consonance with the source document tailoring contained in the Statement of Work (SOW).

5.2 Distribution Statement Marking

The designation in Block 9 of the CDRL form indicates that one of the following seven (7) authorized distribution statements from AFR 85-3 (MIL-STD-1806 procedures may be used for distribution statements) shall be annotated on that technical data. Distribution statements will be selected to denote the audience the data is intended for: A distribution statement marking is distinct from and in addition to a security classification marking assigned IAW DoD 5200.1-R. Should Block 9 of the CDRL form and the DID be in conflict, Block 9 of the CDRL form shall take precedence. The following distribution statements are authorized for use in marking technical documents:

Distribution Statement A:

Approved for public release; distribution is unlimited.

Distribution Statement B:

Distribution authorized to U.S. government agencies only (fill in reason) (date of determination). Other requests for this document shall be referred to (insert controlling DoD office).

Distribution Statement C:

Distribution authorized to U.S. government agencies and their contractors (fill in reason) (date of determination). Other requests for this document shall be referred to (insert controlling DoD office).

Distribution Statement D:

Distribution authorized to the DoD and DoD contractors only (fill in reason) (date determination). Other requests for this document shall be referred to (insert controlling DoD office).

Distribution Statement E:

Distribution authorized to DoD components only (fill in reason) (date determination). Other requests for this document shall be referred to (insert controlling DoD office).

Distribution Statement F:

Further distribution only as directed by (insert controlling DoD office) date of determination) or higher DoD authority.

Distribution Statement X:

Distribution authorized to U.S. government agencies and private individuals or enterprises eligible to obtain export-controlled technical data IAW regulations implementing 10 U.S.C. 140 (date of determination). Other requests for this document shall be referred to (insert controlling DoD office).

The following table lists examples of Distribution Statement usage on Technical Documents follow:

5.3 Destruction Notice

All technical documents marked with Distribution Statements B, C, D, E, F, or X will also be marked with the following notice:

6. SUPPLEMENTAL DATA DELIVERY INSTRUCTIONS

6.1 Due Dates

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

6.2 Late Delivery

Delivery of data is considered late if it does not arrive at its destination by 1530 hours (3:30 PM) Pacific time on the date specified in Blocks 12, 13 or 16 of the CDRL. If the data delivery is post marked three days before the due date, and due to U.S. Postal Service handling, it is not received by the Los Angeles AFB mail room on the due date, the CDRL delivery requirements are still met. U.S. Postal Service “Express Mail” or overnight courier/delivery service is not encouraged.

6.3 Letter of Transmittal (Block 7)

Each data submittal shall be accompanied by a Letter of Transmittal (LT). Transmittal letters shall contain the following information:

6.4. Submittal Procedure

Unclassified CDRLs are submitted to the government via the TopVue tool and in accordance with this instruction. Classified CDRLs, documentation, are submitted in accordance with this instruction and are never to be posted to TopVue.

6.4.1 Unclassified CDRL Submittal Procedure

Global Positioning Systems Wing (GPSW)/ENR 483 North Aviation Boulevard, El Segundo CA 90245-2808 ATTN: GPS OCX Data Manager

6.4.2 Classified CDRL Submittal Procedure

Classified CDRLs or portions of a CDRL, as applicable, shall be forwarded in accordance with (IAW) Appendix B of the DD-254.

For Classified Disks send two (2) copies.

Outer Envelope:

Global Positioning Systems Wing (GPSW)/ENR 483 North Aviation Boulevard El Segundo, CA 90245-2808 ATTN: Security Office/Document Control

Inner Envelope:

Global Positioning Systems Wing (GPSW)/ENR 483 North Aviation Boulevard El Segundo, CA 90245-2808 ATTN: Lonetta Demmings GPSW Technical Library

6.4.2.1 Secret SAP Deliveries & Comments

Attention: GPS Wing Program Security Office (GPSW/PSO) Classified Fax Number: (310) 336-3111, have fax cover sheet identify program contract number and request GPSWPSO personnel contact OCX Government Data Manager regarding delivery.

Note: A sterile P.O. Box exists for Disk delivery or extensive comments to by pass faxing. This type of delivery requires each contractor’s CPSO (Contractor Program Security Officer) to contact the GPSW/PSO personnel at (310) 336-3212 or at (310) 336 3081 for P.O. Box address.

6.5 Distribution

The contractor is not authorized to provide copies of any data to any outside agency other than those listed in Block 14, or Block 16 of the CDRL form without specific approval of the PCO.

All official submittals shall be accompanied with a corresponding transmittal letter. Address transmittal to GPSW/PK.

7. SUPPLEMENTAL DATA REVIEW AND APPROVAL PROCESS

7.1 Approval CDRLs

The letter “A” in Block 8 of the DD Form 1423 indicates that the Government must approve the data item. In addition, Block 16 of the form may contain additional directions.

Written Approval Written approval indicates agreement or concurrence with the contractor furnished data only and shall not be construed as changing any of the terms or conditions of the subject contract. The approval authority shall be the PCO. Approval shall take the form of either a letter signed by the PCO or a Contractual Document Action (CDA) form AFC-1691, signed and dated by the PCO and the Air Force Officer of Primary Responsibility (AF OPR). Data items submitted for approval are NOT automatically approved without government approval.

Approved with Comment or Disapproved The Contractor shall revise data items Approved with Comments or Disapproved in accordance with the specific written comments transmitted with the CDA or PCO letter and resubmit not later than 30 calendar days from receipt of the Approval with Comments or Disapproval, unless otherwise directed. The resubmitted data will require a new approval cycle as indicated in Block 8 of the DD Form 1423.

Draft Versions of the CDRL If a DD Form 1423 directs the Contractor to submit a “draft” version of an approval CDRL in advance of the final version, the draft will be considered an information only submission. However, the PCO still retains the right to disapprove a draft data item that does not comply with the contract requirements. Unless otherwise directed by the PCO, the Contractor shall incorporate the Government’s comments in the final submission and shall not resubmit the draft version of the data item.

7.2 Contractual Document Action (CDA)

After the Government receives a data item submission, a CDA number, a unique identifier to that submission, will be assigned. The Government’s review of that data item will result in a CDA, or PCO letter, indicating the data items approval or disapproval. Should the Government have comments on the data item, the CDA will include a Comment Resolution Matrix (CRM). Comments will be assigned one of the following codes:

7.3 Information Only CDRLs

When an “A” is not indicated in Block 8 of the DD Form 1423, the PCO still retains the right to disapprove any data that does not comply with contract requirements. The Contractor shall revise the disapproved data item in accordance with the specific written comments transmitted with the CDA or PCO letter and resubmit not later than 30 calendar days, unless otherwise directed, from receipt of the disapproval. The resubmitted data will require a new approval cycle as indicated in Block 8 of the DD Form 1423.

7.4 DD Form 250 Requirements

Block 7 of the DD Form 1423 indicates whether Procurement Quality Assurance inspections and acceptance of deliverable data by DD Form 250 are required. “Draft” copies submitted for advance approval and “Preliminary Draft” copies submitted are exempt from the DD Form 250 requirements. Information copies of DD Form 250 shall accompany each letter of transmittal for this category.

8. TOPVUE CONTRACTOR PUBLIC KEY INFRASTRUCTURE (PKI) PROCEDURE

Air Force Space Command (AFSPC) requires all web applications, including TopVue, to present a valid DoD Public Key Infrastructure (PKI) certificate before allowing access to the system. DoD contractors working off site will need to acquire PKI certificates from one of the DoD approved External Certification Authorities (ECA) in order to access the TopVue system. ECA information can be found at: http://iase.disa.mil/pki/eca/index.html . Once PKI certificate(s) have been acquired, TopVue users should follow the steps below to register their certificate with the TopVue system: Make sure your PKI certificate is enabled.

9. DATA ACCESSION LIST (DAL)

EXHIBIT A

CONTRACT DATA REQUIREMENT LIST (CDRL) INSTRUCTIONS

Requests from the PCO for data ordered from the Data Accession List (DAL) (with the application of DID DI-MGMT-81453) shall be provided at no increase in contract price. Requests for quantities greater than two each per document shall be honored upon receipt of PCO direction and with Contractor concurrence that such request can be filled at no increase in contract price. Transmittal of any data so ordered shall include information copies to the GPS DMO.

Exhibit A to FA8807-09-R-0003

ATTACHMENT I

DYNAMIC OBJECT-ORIENTED REQUIREMENTS

SYSTEM (DOORS) INSTRUCTIONS

DYNAMIC OBJECT-ORIENTED REQUIREMENTS SYSTEM (DOORS) INSTRUCTIONS

The contractor shall provide CDRL deliverables specified in Table 2 as a DOORS archive module. If the DOORS file contains links to other modules, then the archive file shall be a DOORS project archive (.dpa) file. If there are no links, then the archive shall be a DOORS module archive (.dma) file.

All DOORS module archives shall use the following naming convention:

COMPANYNAME_CDRL NUMBER_PROJECT NAME_ARCHIVEDATE.dma.

All DOORS project archives shall use the following naming convention:

COMPANYNAME_CDRL NUMBER_PROJECT NAME_ARCHIVEDATE.dpa.

The contractor shall coordinate with the GPSW to deliver a project archive that contains the appropriate link schematic. The project archive shall correctly employ the use of link modules and linksets.

The contractor shall submit Microsoft Word files using the following specified DOORS compatible format:

a. For MS WORD submittals the following format applies:

All headers shall be styled as Heading 1, Heading 2, etc. For example:

2 FUNCTIONAL REQUIREMENTS (Heading 1)

2.1 Power (Heading 2)

2.1.1 Battery (Heading 3)

The battery shall be rechargeable (Normal)

b. All requirements shall be written in a form of single sentence. If there are multiple sentences in the paragraph, those shall be the supported statements which do not include the word “shall”.

c. All headings shall be separated from the text using paragraph returns. Text paragraphs shall be styled as Normal and end with a paragraph return. There shall be no blank lines with paragraph returns. Each Paragraph shall contain a single requirement.

d. Figures need to be embedded as Object Link/Embed (OLE) objects. The contractor shall ensure that there are no additional layered figures. In instance where a user shall utilize Word’s draw features to highlight portions of a diagram using arrows and text boxes, when exported to DOORS, these layered figures shall come over as separate objects, and the original picture shall be fragmented. The contractor shall change these layered figures into a single figure contained within an OLE object.

e. Title and signature page shall be extracted into a separate Microsoft Word file and then reinserted into the document file, at the same location, as an OLE object.

f. Tables without embedded requirements shall be extracted into separate word files and then reinserted into the document file, at the same location, as OLE objects.

g. Tables with embedded requirements shall not contain merged cells. The contractor shall repair any tables containing merged cells and also manipulate the tables’ borders such that they do not contain any merged cells. When these tables are brought into DOORS, they shall be automatically parsed into the database module as DOORS tables. Each cell shall have the capability to be separately linked to other documents when parsed in as DOORS tables.

h. The Government requires the minimum number of attributes (additional defined characteristics) of Table 1 be applied to all specifications and ICD’s. The contractor shall supply these specified attributes. If a Microsoft Word file is submitted, then the attributes shall be submitted along with the main body Microsoft Word file as a Microsoft Excel Spreadsheet file showing each paragraph DOORS object ID and the corresponding attributes. Other attributes may optionally be added at the contractor’s discretion.

i. DOORS baseline versions of a DOORS module shall be coordinated with the GPSW prior to incorporation. The contractor shall baseline the last GPSW approved versions into a DOORS baseline set and should include these baselines in their DOORS archive.

Submitting Changes

Submittals for Configuration Control Board (CCB) approval that document changes made to a file submitted to the GPSW as a DOORS file shall include a Microsoft Word formatted export from the DOORS file that include the following: Object Identifier, Object Number, Classification Level, Object Text headings, Object Text, Req. ID, Proposed Requirement, Reason For Change, and Verification Method. The Microsoft Word document shall be submitted and approved by the CCB.

a. When submitting proposed changes, the contractor shall use the Proposed Requirement attribute for proposed wording changes and the Reason for Change attribute to describe the justification for a given object change.

b. When incorporating an approved change, the contractor shall place the new approved wording in the current object, the justification for a given object change in the Reason for Change attribute, and then populate the Authority attribute with the appropriate ECP number.

Table 1 DOORS Attributes

DOORS

ATTRIBUTES

ECPs, IRNs, Deviations, Waivers, etc.

any comments

Multi

Proposed new object wording.

Describes the justification for a given object change.

Optional Attributes

DOORS

ATTRIBUTES

Brief description of origin of the requirement, with references as appropriate

Table 2 DOORS Format CDRL’s

CDRL NO.

DATA ITEM TITLE

SUBTITLE

Exhibit A to FA8807-09-R0003

Exhibit A to FA8807-09-R-0003

EXHIBIT A

CDRL SUMMARY LIST

CDRL NO. TITLE AND SUBTITLE DID NO.

A001 Conference Minutes DI-ADMN-81250A/T

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

A003 Logistics Management Information (LMI) Data Product DI-ALSS-81529/T [Support Equipment, Data Products]

A004 Logistics Management Information (LMI) Summaries DI-ALSS-81530/T [Provisioning Support Equipment Summaries]

A005 Supplemental Data for Provisioning (SDFP) DI-ALSS-81557/T

A006 Engineering Change Proposal (ECP) DI-CMAN-80639C/T

A007 Request for Deviation (RFD) DI-CMAN-80640C/T

A008 Specification Change Notice (SCN) DI-CMAN-80643C/T

A009 Interface Control Document (ICD) DI-CMAN-81248A/T

A010 Request for Nomenclature (DD Form 61) DI-CMAN-81254A/T

A011 System/Subsystem Specification (SSS) DI-IPSC-81431A/T [Prime Item, Critical Item Development Specification]

A012 Configuration Item Product Specification DI-E-3103A/T [Prime Item, Critical Item Product Specification]

[Life Cycle Cost Report (LCCR)]

A014 Cost Data Summary Report (DD Form 1921) DI-FNCL-81565B/T

A016 Human Engineering Test Plan DI-HFAC-80743B/T

A017 Human Engineering Test Report DI-HFAC-80744B/T

A018 Human Engineering System Analysis Report DI-HFAC-80745B/T

CDRL NO. TITLE AND SUBTITLE DID NO.

A019 Human Engineering Design Approach Document -Operator DI-HFAC-80746B

A020 Human Engineering Design Approach Document-Maintainer DI-HFAC-80747B

A021 Failure Mode Effects, and Criticality Analysis Report DI-ILSS-81495/T

A022 Software Development Plan (SDP) DI-IPSC-81427A/T

A023 Software Transition Plan (STRP) DI-IPSC-81429A/T

A024 Operational Concept Description (OCD) DI-IPSC-81430A/T

A025 System/Subsystem Specification (SSS) DI-IPSC-81431A/T

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

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

A028 Interface Requirements Specification (IRS) DI-IPSC-81434A/T

A029 Database Design Description (DBDD) DI-IPSC-81437A/T

A030 Software Test Plan (STP) DI-IPSC-81438A/T

A031 Software Test Description (STD) DI-IPSC-81439A/T

A032 Software Test Report (STR) DI-IPSC-81440A/T

A033 Software Product Specification (SPS) DI-IPSC-81441A/T

A034 Software Version Description (SVD) DI-IPSC-81442A/T

A037 Systems Engineering Management Plan (SEMP) DI-MGMT-81024/T

A038 Contract Work Breakdown Structure (CWBS) DI-MGMT-81334C/T

A039 Data Accession List (DAL) DI-MGMT-81453A/T

A040 Contract Performance Report (CPR) DI-MGMT-81466A/T

A041 Contract Funds Status Report (CFSR) DI-MGMT-81468/T

CDRL NO. TITLE AND SUBTITLE DID NO.

A042 Integrated Master Schedule (IMS) DI-MGMT-81650/T

A046 Progress Curve Report (DD From 1921-2) DI-FNCL-81567B/T

A047 Technical Report-Study/Services DI-MISC-80508B/T [OCX Spares List]

Integrity and Continuity Assurance Plan (PSICAP)]

Assurance Assessment (ICAA)]

Assessment (FHA)]

Report (SSMR)]

CDRL NO. TITLE AND SUBTITLE DID NO.

A067 Test Plan DI-NDTI-80566A/T

A068 Test Procedure DI-NDTI-80603A/T

A069 Failure Summary and Analysis Report DI-RELI-80255/T

A070 System Safety Program Plan DI-SAFT-80100A/T

Preliminary System Hazard Analysis (SHA) Subsystem Safety Hazard Analysis (SSHA) System Hazard Analysis (SHA) Operating and Support Hazard Analysis (O&SHA) Safety Requirements/Criteria Analysis (SRCA)]

A072 Safety Assessment Report (SAR) DI-SAFT-80102A/T

CDRL NO. TITLE AND SUBTITLE DID NO.

A073 Product Drawings/Models and Associated Lists DI-SESS-81000C/T

A075 Initial SRDR DI-MGMT-81739/T

A076 Technical Manual Contract Requirements TM-86-01M/T

A077 Final SRDR DI-MGMT-81740/T

A078 Cost and Software Data Reporting (CSDR) Plan DoD 5000.4M-1 /T (DD FORM 2794) – Supporting Document SRDR

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

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

A

GPS ADVANCED CONTROL SEGMENT

FA8807-09-R-0003

ADD CONTRACTOR'S NAME

A001

CONFERENCE MINUTES

N/R

DI-ADMN-81250A/T

SOW 3.1.1; 3.1.2.1; 3.1.3; 4.4; 4.5

GPAS

LT

N/R

BLK 16

b. COPIES

FINAL

A

D

N/R

BLK 16

This CDRL contains technical data only.

BLK 4: Contractor format acceptable. Add to 10.2 Content ”g. Applicable to all OCX program meetings, reviews, audits, and conferences. This data item shall also contain Conference

Minutes from space segment design reviews in which the OCX contractor participated. Space segment design reviews Conference Minutes shall describe the system integration issues that may arise in the OCX design as a result of the space segment contractor’s design and an evaluation of the progress and completeness of the space contractor’s design review. The

PCO shall provide notification if minutes are not required.”

BLK 8: Government approval/disapproval/comments 45 CD after receipt.

BLKs 12, 13: Submit 10 CD after each event. Updates as required or by PCO notification.

15. TOTAL

ELECTRONICALLY GENERATED PAGE_1_ OF _1_PAGES

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

A

GPS ADVANCED CONTROL SEGMENT

FA8807-09-R-0003

ADD CONTRACTOR'S NAME

A002

PROGRAM PROTECTION IMPLEMENTATION PLAN (PPIP)

N/R

DI-ADMN-81306/T

SOW 4.10.10; 4.10.12

ENS

LT

N/R

BLK 16

b. COPIES

FINAL

A

D

N/R

BLK 16

BLK 4: Contractor format acceptable.

1. Replace 7.1 with: “This DID contains the format and content preparation instructions for the

PPIP resulting from the Program Protection requirements set forth in DoDI 5000.02, Table

E4.T3 (Regulatory Information Requirements), DoDD 5200.39, paragraph 4.4, DoD 5200.1-M, C3.3 and the Defense Acquisition Guidebook, paragraph 8.4.9.3.”

2. Replace 7.2. with: “This DID is applicable to all DoD Acquisition Program regulated by

DoD 5200.1-M, DoDD 5000.1.”

3. Add to Paragraph 10.1.a 1) System Description: “Describe the capabilities and limitations of the system, including support equipment and simulators. Include: a) The specific characteristics that distinguish it from existing systems or other systems under development. b)

The function, operational characteristics, and technical parameters of any components, program, product, technology demonstrator, or other acquisition system that is an integral part of the system.”

4. Add to Paragraph 10.1.a 2) Program Information: “Include the program’s decision authority and specify location, points of contact, and telephone numbers at the following: a)

Government-owned sites that shall handle Critical Program Information (CPI) and Critical

System Resources (CSR) material. b) Government-owned test and evaluation centers where

CPI and CSR material shall be tested. c) Contractors (subcontractors/vendors) who shall handle CPI and CSR materials. d) Contractor-owned facilities where CPI and CSR materials shall be designed, developed, tested, stored, produced, supported, and managed.”

5. Add to Paragraph 10.1.b 1) List CPI and CSR: “Identify the technology, hardware, process, and information that are CPI and CSR.”

6. Add to Paragraph 10.1.b 2) Threats to CPI and CSR: “Identify threats against CPI and

ELECTRONICALLY GENERATED PAGE_1_ OF _3_PAGES

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

A

GPS ADVANCED CONTROL SEGMENT

FA8807-09-R-0003

ADD CONTRACTOR'S NAME

A002

PROGRAM PROTECTION IMPLEMENTATION PLAN (PPIP)

N/R

DI-ADMN-81306/T

SOW 4.10.10; 4.10.12

ENS

LT

N/R

BLK 16

b. COPIES

FINAL

A

D

N/R

BLK 16

7. Add to Paragraph 10.1.b 3) Vulnerabilities of CPI and CSR: “Identify and prioritize

Mitigation): Identify, evaluate, and eliminate or contain known or potential system security vulnerabilities.”

8. Add to Paragraph 10.1.b 5) Countermeasures: “Identify countermeasures to eliminate vulnerabilities associated with an identified threat to the CPI and CSR based upon threat analysis.”

9. Add to Paragraph 10.1.b.6) Modification Management: “Describe relevant aspects of

Program Protection Implementation Planning to safeguard CPI and CSR.”

10. Add to Paragraph 10.1.b 7) C4I Certification and Accreditation: “Describe the security support that is required for the C4I infrastructure. Identify the information security classification level(s) required and capabilities employed. For example, if data is encrypted, describe the types of encryption planned. Address Information Assurance (IA), giving special consideration to vulnerabilities resulting from reliance on other Government or civil sector infrastructures and the risk of their loss, damage, or destruction.”

11. Add to Paragraph 10.1.b 8) Systems Security Engineering (SSE) Approach: “Identify SSE approach to a) Identifying security requirements optimizing their integration into a single system engineering approach. b) Tailoring individual security disciplines to program development. c) Identifying threats (e.g., physical, electronic, and intelligence) that can be neutralized or minimized through security engineering design and countermeasures.

d) Identifying necessary actions to minimize or contain system or component vulnerabilities.

e) Optimizing life-cycle security costs, while improving overall survivability of the system or component.”

15. TOTAL

ELECTRONICALLY GENERATED PAGE_2_ OF _3_PAGES

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

A

GPS ADVANCED CONTROL SEGMENT

FA8807-09-R-0003

ADD CONTRACTOR'S NAME

A002

PROGRAM PROTECTION IMPLEMENTATION PLAN (PPIP)

N/R

DI-ADMN-81306/T

SOW 4.10.10; 4.10.12

ENS

LT

N/R

BLK 16

b. COPIES

FINAL

A

D

N/R

BLK 16

12. Add paragraph 10.1.e: “Provide SECURITY TARGET (ST) as an appendix that conforms to the PRONAV Protection Profile (PP) and 1) provides PP conformance claims document conventions, terminology, and an overview of the Target of Evaluation (TOE), 2) provides a description of the TOE including the physical and logical boundaries for the TOE, 3) provides a description of the threats, organizational security policies, and assumptions pertaining to the TOE and the TOE environment, 4) identifies the security objectives for the

TOE and its supporting environment as well as a rationale that objectives are sufficient to counter the threats identified for the TOE, 5) includes the completed Security Functional

Requirements(SFRs) with all selections and assignments filled in, Security Assurance

Requirements(SARs), as well as the rationale for security requirements, security requirements

Dependencies, and 6) identifies and describes the assurance measures.

BLK 8: Government approval/disapproval/comments 45 CD after receipt.

BLKs 12, 13: PPIP: Submit draft 30 CD after contract award. Submit final 30 CD prior to

PDR. ST: Submit draft 45 CD after contract award. Submit 30 CD prior to PDR. Submit 30

CD prior to CDR for Block 1 and Block 2. Submit 30 CD prior to Delta SDR for Block 3 and Block 4. Submit 30 CD prior to Delta PDR for Block 3 and Block 4. Update as required or by PCO notification.

15. TOTAL

ELECTRONICALLY GENERATED PAGE_3 OF _3_PAGES

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

A

GPS ADVANCED CONTROL SEGMENT

FA8807-09-R-0003

ADD CONTRACTOR'S NAME

A003

LOGISTICS MANAGEMENT INFORMATION (LMI) DATA PRODUCT

SUPPORT EQUIPMENT, DATA PRODUCTS

DI-ALSS-81529/T

SOW 3.11; 4.10.1

OS

LT

N/R

BLK 16

b. COPIES

FINAL

A

D

N/R

N/R

PPA

BLK 4: Add to paragraph 10.3 “This data item shall contain:

a. Depot Support Equipment Requirements Documents (SERDs) shall be required for items selected for depot repair.

b. LMI Data Product Worksheet for Summaries for Provisioning and Support Equipment (see

Provisioning Technical Documentation (PTD) Data Selection Sheet on the next page).”

BLK 8: Government approval/disapproval/comments 75 CD days after receipt.

BLK 12: Submit final 45 CD after provisioning conference.

BLK 14: The Prime Provisioning Activity (PPA) for this activity is Ogden AFB, UT. Mailing address for the PPA is:

USAF/AFMC (Attn: OCX Item Manager), 418 SCMS/GULAAC, , 6038

Aspen Ave., Bldg 1289 SW, Hill AFB, UT 84056-5809.

Deliver both sets of SDFP to the PPA in hard copy.

15. TOTAL

ELECTRONICALLY GENERATED PAGE_1_ OF _3_PAGES

ELECTRONICALLY GENERATED PAGE 2 OF 3 PAGES

ELECTRONICALLY GENERATED PAGE 3 OF 3 PAGES

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

A

GPS ADVANCED CONTROL SEGMENT

FA8807-09-R-0003

ADD CONTRACTOR'S NAME

A004

LOGISTICS MANAGEMENT INFORMATION (LMI) SUMMARIES

PROVISIONING SUPPORT EQUIPMENT SUMMARIES

N/R

DI-ALSS-81530/T

SOW 3.11; 4.10.1

OS

LT

N/R

BLK 16

b. COPIES

FINAL

A

D

N/R

BLK 16

This CDRL contains technical data only.

BLK 4: Add 10.3.1 to BLK 10 of DID:

“a. Results of the screening shall be incorporated into the Provisioning Parts List (PPL).

b. The following data elements obtained as a result of valid National Stock Numbers (NSN) matches through DLIS screening shall be inserted into the Provisioning Technical

Documentation (PTD) for review by Government personnel at each In Process Review (IPR).

c. CD shall be labeled.

d. Submissions shall be IAW DoD 4100.38-M, Provisioning and Other Pre- Procurement

Screening Manual.

e. Include current data and apply to the PDT. The data elements must be extracted for each

Provisioning List Item Sequence Number (PLISN) line matched to an NSN and inserted in the applicable PTD Parts List for Government review at each IPR.

f. Screening data shall conform to Chapter II and IV of DoD 4100.38-M, Department of

Defense Provisioning and Other Pre-procurement Screening Manual.

g. Supply Support Summaries for Support Equipment recommendation: Use “Air Force Initial

Provisioning Performance Specification (IPPS)” document, “LMI Data Product Selection

Sheet”, and ” LMI Summary Worksheet”,DI-ALSS-81530/T” contained in the following pages.

h. Contractor sample letter of transmittal.

TO: COMMANDER

Defense Logistics Information Service

Item Identification & Management Data Branch

ATTN: DLIS-KPD (Provisioning Screening)

15. TOTAL

ELECTRONICALLY GENERATED PAGE_1_ OF _18_PAGES

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

A

GPS ADVANCED CONTROL SEGMENT

FA8807-09-R-0003

ADD CONTRACTOR'S NAME

A004

LOGISTICS MANAGEMENT INFORMATION (LMI) SUMMARIES

PROVISIONING SUPPORT EQUIPMENT SUMMARIES

DI-ALSS-81530/T

SOW 3.11; 4.10.1

OS

LT

N/R

BLK 16

b. COPIES

FINAL

A

D

N/R

BLK 16

BLK 16 CONTINUED:

Battle Creek, MI 49017-3084

Subject: Request for Provisioning Screening

Reference: Contract Number: ______________________

Enclosure: CD Submittals; specify

Enclosure: CD; Single output/multiple output code 1 “Mandatory”

Number of Records “Mandatory”

Enclosure: CD; Single output/multiple output code 1 “Mandatory”

Number of Records “Mandatory”

Contractor Name and Address

Signature: _____________________________

CDRL Item # ___________________

i. Design Change Notice (DCN) shall include the following:

a. Changes to equipment or parts supplied by the contractor during this contract for any change that affects the part number or assembly that is listed in the Provisioning Parts List

(PPL).

b. The data shall be in the same format as the Provisioning Parts List.

c. Option for Government Organic or Partnering Candidates shall require a Provisioning Parts

List (PPL) top down breakdown.

d. The Prime Provisioning Activity (PPA) for this effort is USAF/AFMC, 418 SCMS/GULAAC, Ogden AFB.”

15. TOTAL

ELECTRONICALLY GENERATED PAGE_2_ OF _18_PAGES

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information, Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204,…