Atch 12 - List Instructions for Cod CDRLs ADPs_06 Feb 2012.pdf

CONTRACT DATA REQUIREMENTS LIST (CDRL) and AUTOMATED DATA PRODUCT (ADP)

INSTRUCTIONS

1. General

Where possible all CDRL and ADP items delivered will be updates to documents generated under the Thule Contract. The contractor shall update the applicable UEWR common documents to incorporate Clear specific information into the baseline. These updates are intended to provide one single library of documents representative of the UEWR sensors and associated impedimenta.

Document Security - Security Instructions found in the DD254 for this contract will apply to CDRLs.

Public Release - All information related to the program must be submitted in accordance with Special Contract

Requirement H-4, Public Release of Information.

Internet - Unclassified controlled MDA information must not be posted in unprotected form, on any system network (WEB site) directly accessible from the public internet.

Encryption - The CDRL defines the data that is to be delivered to the Government by the contractor. This data may be in electronic format and unclassified material may be delivered via the Government IDE Integrated Data

Environment (IDE). Classified material will be delivered via appropriate mail delivery or other Government approved methods.

Automated Data Products (ADP) - ADPs are items that would be listed on the data accession list, available to the

Government as electronic data to be provided via IDE.

Formats - CDRLs and ADPs are to be prepared and delivered on plain backgrounds for ease of downloading and word processing (Microsoft office suite) use. CDRLs will be in the format and contain information specified in the DD Form 1423. ADPs will follow the contractor format. These instructions apply to Exhibit A and to all subsequent Exhibits added to this contract.

2. Data Item Description (DID)

Data Item Descriptions entered on the CDRL, were selected from the Acquisition Streamlining and Standardization

Information System (ASSIST) data base available at http://assist .dps.dla.mil.

3. Data Approval Requirements

Selected data requires approval before the submission is considered final. The letter “A” appearing in Block 8 of the

CDRL designates such data. The approving authority shall be the PCO. The absence of an “A” in Block 8 does not forfeit or otherwise affect the Government’s right to comment on the CDRL. Unless otherwise specified, resubmittal of disapproved data, or data approvals which are subject to the incorporation of comments, shall be so identified and delivered by the next CDRL submission or as directed by the PCO. The requirements applicable to the original submittal shall apply to the resubmittal data. Should the Contractor disagree with a resubmittal requirement, the Contractor shall submit comments in writing to the PCO within 15 calendar days of receipt of data disapproval notification.

4. Distribution Statements

The following distribution statement shall be included on the cover page to protect all technical data:

DISTRIBUTION STATEMENT F: Further dissemination only as directed by DoD, Missile Defense Agency, ATTN:

Procuring Contracting Officer, MDA/DACX, Building 5222, Martin Road, Redstone Arsenal, AL 35898, or higher authority.

5. Data Rights

The Contractor shall affix the following data rights legend to all CDRL or ADP documents.

Any document produced under this contract and posted as an ADP or CDRL shall have a legend asserting Government data rights IAW DFAR 252.227-7013, Rights in technical data—Noncommercial items.

Unlimited Government Data Rights

Contract No.____________________

Contractor Name____________________

Contractor Address____________________

Expiration Date____________________

All data shall be delivered with at least Government purpose rights unless approved by the program office in writing.

Add the following Export Control Statement to all documents assigned distribution Statement F:

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. Section 2751 et. seq.) or the Executive order 12470. Violation of these export laws is subject to sever criminal penalties

Data which is not available on IDE, such as classified data, shall be delivered via hardcopy, CD or other Government-approved method to MDA/SNU. Additional copies shall be delivered to the following address:

ESC/HSIGS MDA/SNU AFSPC/A5

Document Control (if Classified) Document Control (if classified) 150 Vandenberg St, Suite 1105

1050 E. Stewart Avenue 11 Barksdale Street,Bldg 1614 Peterson AFB, CO 80914-4580

Peterson, AFB CO 80914-2902 Hanscom AFB, MA 01731-1700

CDRL List Approval OPR OCR

B001 Cost Data Summary Report (CDSR) No MDA/SNU MDA/SNU

B002 Functional Cost Hour No MDA/SNU MDA/SNU

B003 Reserved

B004 Contract Funds Status Report (CFSR) No MDA/SNU MDA/SNU

B005 Contract Performance Report (CPR) No MDA/SNU MDA/SNU

B006 Integrated Master Schedule (IMS)

Yes MDA/SNU

MDA/SNUA

FSPC/A5F/

A3F

ESC/HSIGS

B007 Program Protection Management Plan (PPMP)

Yes MDA/SNU

MDA/SNUA

FSPC/A5F/

A3F/A6S/IP

, 13

SWS/MA

B008 Reserved

B009 Reserved

B010 Engineering Change Proposals (ECPs)

Yes MDA/SNU

MDA/SNUA

FSPC/A5F/

A3F/A4M

ESC/HSIGS

B011 Request for Deviations and Waivers Yes MDA/SNU

MDA/SNUA

FSPC/A5F

B012 Site Security Management Plan (SSMP)

Yes MDA/SNU

MDA/SNUA

FSPC/A5F/

A3F/A6S/IP

, 13

SWS/MA

B013 Specification Change Notices (SCNs)

MDA/SNU

AFSPC/A5F/

A3F/A4M

ESC/HSIGS

B014 DT&E Test Plans and Procedures

Yes MDA/SNU

MDA/SNU

AFSPC/A5F/

A3F

ESC/HSIGS

B015 Software Test Plans and Procedures

Yes MDA/SNU

MDA/SNU

AFSPC/A5F/

A3F

ESC/HSIGS

B016 Data Accession List (DAL) No MDA/SNU

MDA/SNU

AFSPC/A5F

B017 Technical Data Package (TDP) (AutoCad Compatible)

Yes MDA/SNU

MDA/SNU

ESC/HSIGS

AFSPC/A5F/

A3F/A4M

B018 Facility Design Review Yes MDA/SNU

MDA/SNU

ADSPC/A5F

B019 Scientific and Technical Reports

Yes MDA/SNU

MDA/SNU

AFSPC/A5F/

A3F

B020 Technical Publication Plan

Yes MDA/SNU

MDA/SNU

AFSPC/A5F/

A3F/A4M

B021 Software Users Manual (SUM)

Yes MDA/SNU

MDA/SNU

ESC/HSIGS

AFSPC/A5F/

A3F/A4M

B022 Reserved

B023 Information Assurance Administrators Guide (AG)

MDA/SNU

ESC/HSIGS

AFSPC/A5F/

B024 Failure Modes, Effects and Criticality Analysis (FMECA) &

Critical Items List (CIL) Yes MDA/SNU

MDA/SNU

ESC/HSIGS

AFSPC/A5F/

A3F/A4M

B025 Technical Orders (TOs) for UEWR

Yes MDA/SNU

MDA/SNU

ESC/HSIGS

AFSPC/A5F/

A3F/A4M

B026 Software Version Description (SVD) Document and

Software Source Code

Yes MDA/SNU

MDA/SNU

ESC/HSIGS

AFSPC/A5F/

A3F/A4M

DSC

Contractor and HSV

Labs

B027 Reserved

B028 Delta Design Review (DDR)

MDA/SNU

ESC/HSIGS

AFSPC/A5F/

B029 Reserved

B030 Logistics Data Product

MDA/SNU

ESC/HSIGS

AFSPC/A5F/

A3F/A4M

B031 Mission Assurance Implementation Plan

Yes MDA/SNU

MDA/SNU

AFSPC/A5F/

A3F

B032 Safety Assessment Report

Yes MDA/SNU

MDA/SNU

AFSPC/A5F/

A3F

B033 Information Assurance Users Guide

MDA/SNU

ESC/HSIGS

AFSPC/A5F/

A3F/A6S

B034 Information Assurance Implementation Plan

Yes MDA/SNU

MDA/SNU

ESC/HSIGS/

AFSPC /

A5F/A3F/

A6S

B035 Reserved

B036 Risk Management Plan

MDA/SNU/

MDA/DE

B037 Reserved

B038 Small Business Utilization and Participation Data Yes MDA/SB MDA/SB

B039 DIACAP Executive Package

Yes MDA/SNU

MDA/SNU

ESC/HSIGS/

AFSPC /

A5F/A3F/

A6S

B040 Reserved

B041 Reserved

B042 Reserved

B043 Software Design Description (SDD) for MAS, STS, SPS & REX

Yes MDA/SNU

MDA/SNU

ESC/HSIGS

B044 Software Product Specification (SPS) for MAS, STS, SPS & REX

Yes MDA/SNU

MDA/SNU

ESC/HSIGS

B045 Software Requirements Specification (SRS) for MAS, STS, SPS & REX

Yes MDA/SNU

MDA/SNU

ESC/HSIGS

B046 Functional Configuration Audit (FCA) Yes MDA/SNU

MDA/SNU

ESC/HSIGS

B047 Physical Configuration Audit (PCA) Yes MDA/SNU

MDA/SNU

ESC/HSIGS

ADP List

ADP 1 Identification of Required Support Equipment List

ADP 2 Studies & Analysis Reports

ADP 3 System Engineering Management Plan (SEMP)

ADP 4 Program Management Review /Monthly Minutes

ADP 5 Construction Schedule - Cape Cod Only

ADP 6 PMT Charts to include Quality / Manufacturing Metrics

ADP 7 Facility Verification & Cross Reference Matrix - Cape Cod Only

ADP 8 Transportation Plan

ADP 9 UEWR Training Plan

ADP 10 Facility Equipment Warranties – Cape Cod Only

ADP 11 Facility Equipment Operator & Maintenance Manuals – Cape Cod Only

ADP 12 Facility Equipment List of Recommended Spares – Cape Cod Only

ADP 13 Facility Equipment Preventive Maintenance Summary – Cape Cod Only

ADP14 Facility As-Built Drawings

ADP 15 Reserved

ADP 16 Software Development Plan (SDP)

ADP 17 Reserved

ADP 18 Software Test Report

ADP 19 Reserved

ADP 20 DT&E Test Reports

ADP 21 Reserved

ADP 22 Quality Assurance Plan

ADP 23 Reliability, Availability, Maintainability And Testability (RAM&T) Program Plan

ADP 24 Corrective Action Reports (CARs)

ADP 25 Foreign Object Elimination (FOE) Program Plan

ADP 26 Reserved

ADP 27 Facility Cable Run Summary – Cape Cod Only

ADP 28 Human Systems Integration Program Plan

ADP29

ICD UEWR Integrated Tactical Warning / Attack Assessment and Space Surveillance

Network Users

ADP 30 Reliability Design Criteria

ADP 31 Maintainability Design Criteria

ADP 32 Electromagnetic Compatibility (EMC) Control Plan

ADP 33 Dynamic Object Oriented Requirements System (DOORS) database for delivery

ADP 34 Human System Integration Design Assessment Report

ADP 35 Health Hazard Assessment Report

ADP 36 Environmental / Accident Incident Report (As Required)

ADP 37 Product Parts Plan

ADP 38 Failure Reporting, Analysis and Corrective Action System (FRACAS) data summaries

ADP 39 Maintainability Math Models, Allocations and Predictions

ADP 40 Reliability Math Models, Allocations and Predictions

ADP 41 Joint Master Schedule (JMS)

ADP42 Specialty Engineering Management Plan (SpEMP)

ADP43

Interface Design Description (IDD) for Mission Application Software / Simulation & Toll

Software (MAS/STS)

ADP 44 Reserved

ADP45 Reserved

ADP 46 Technical Performance Measures (TPM)

ADP 47 Systems Safety Program Plan

ADP 48 Non-Franchise Distributor - Microcircuits Report

ADP 49 Reserved

ADP 50 Reserved

ADP 51 Contractor Furnished Equipment

ADP 52 Ship Readiness Review

ADP 53 Test Readiness Review

ADP 54 Integrated Support Plan

ADP 55 Facilities Requirements Document Inputs – Clear Only

ADP 56 Hazardous Material Management Program (HMMP)

ADP 57 Contractor Quality Control (CQC) Plan

ADP 58 O&M Training

ADP 59 Reserved

ADP 60 Requirements Verification Traceability Matrix

ADP 61 STIG List

ADP 62 Contractor Configuration Management Plan

ADP 63 Parts Management Process (PMP) Plan

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO: 012

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER___X__

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B001

2. TITLE OF DATA ITEM: COST DATA SUMMARY REPORT (DD FORM 1921)

3. SUBTITLE: Contractor Cost Data Report - DD 1921

4. AUTHORITY: (Data Acquisition Document No.): DI-FNCL-81565C/T

5. CONTRACT REFERENCE: SOW Para 5.1.3

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: N

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: Annually

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: See Block 16

13. DATE OF SUBSEQUENT SUBMISSION: See Block 16

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic Copy on IDE

16. REMARKS Applicability: The contents of this CDRL are applicable to all CLINs.

Block 4 Data shall be submitted to OSD Contractor Cost Data Reporting Program Office (CCDR¬PO) via Electronic Data

Interchange (EDI). Electronic Data Transmission shall be in format consistent with Accredited Standards (AS). The contractor will deliver the 1921 report in a format compatible with Microsoft Excel 2007 or greater. 1921 shall include all contract cost (prime and subcontractor) of system elements as specified in your submission of the CWBS CDRL A003.

Blocks 12 and 13 Contractor will submit 1921 report 60 calendar days after the end of the calendar year, beginning with

CY2012 data. A final submission will be submitted at the end of the contract.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER__X___

D. SYSTEM/ITEM: CLEAR UERWR CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B002

2. TITLE OF DATA ITEM: FUNCTIONAL COST HOUR REPORT (DD Form 1921-1)

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-FNCL-81566C/T

5. CONTRACT REFERENCE: SOW Para 5.1.3

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: N

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: See Block 16

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: See Block 16

13. DATE OF SUBSEQUENT SUBMISSION: See Block 16

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic Copy IDE

16. REMARKS: Applicability: The contents of this CDRL are applicable to all CLINs.

Block 4 1921-1 submittals will be reported at the same level as the 1921 reports as defined in Government Cost and

Software Reporting Plan (DD 2794). Submissions will be in a Microsoft Excel 2007 or greater format.

Blocks 10, 12 and 13 Contractor will submit 1921-1 report 60 calendar days after the end of the calendar year beginning with CY2012 data. Following submissions will occur no later than 60 calendar days after the end of the following calendar years. A final submission will be submitted at the end of the contract.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER__X___

D. SYSTEM/ITEM: CLEAR UEWR CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B003

2. TITLE OF DATA ITEM: UEWR CONTRACT WORK BREAKDOWN STRUCTURE (CWBS) AND

DICTIONARY

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-MGMT-81334D/T

5. CONTRACT REFERENCE: SOW Para 5.1.3

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: N

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: 30 calendar days after contract definitization

13. DATE OF SUBSEQUENT SUBMISSION: See Block 16

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: IDE

16. REMARKS:

Block 4 Contractor CWBS format acceptable. Contractor will submit CWBS in a form compatible with Windows Office

2007.

Block 13 Subsequent reports are due within 30 calendar days of program changes requiring a revised CWBS.

Prepare in contractor format using the Data Item Description (DID) as a guide.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER X

D. SYSTEM/ITEM: CLEAR UEWR CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B004

2. TITLE OF DATA ITEM: CONTRACT FUNDS STATUS REPORT (CFSR)

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-MGMT-81468/T

5. CONTRACT REFERENCE: SOW Para 5.1.3

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: N

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: Quarterly

11. AS OF DATE: See Block 16

12. DATE OF FIRST SUBMISSION: See Block 16

13. DATE OF SUBSEQUENT SUBMISSION: See Block 16

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic copy on IDE

16. REMARKS: Applicability: The content of this CDRL is applicable to all CLINs.

Block 4: Include reconciliation with dollar totals in the Contractor Performance Report (CPR) for those months in which the CFSR is submitted. Include summary of all CLINs as well as an individual worksheet for each CLIN.

Projections in blocks 12, 13, and 14 of the CFSR shall be monthly for the next six months, then quarterly for the remainder of the government fiscal year, then by government fiscal year to contract completion.

Block 12 and 13: Initial and subsequent CFSR submissions shall be delivered 20 working days after the end of the contractor’s accounting quarter, beginning with December 2012 data.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER___X__

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO: B005

2. TITLE OF DATA ITEM: CONTRACT PERFORMANCE REPORT (CPR)

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-MGMT-81466A/T

5. CONTRACT REFERENCE: SOW Para 5.1.3

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: N

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: Monthly

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: See Block 16

13. DATE OF SUBSEQUENT SUBMISSION: See Block 16

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic Copy on IDE

16. REMARKS:

a. Electronic copies shall be provided using the United Nations Centre for Trade Facilitation and Electronic Business

(UN/CEFACT) XML standard. In addition, the submission shall include one human readable backup (XLS, DOC, etc.) of

Formats 1-4. Format 5 may be submitted in a human readable form factor. The same human readable file may be used for

Formats 1-5 (.pdf files are not acceptable). Submissions shall not include macros, program executables, embedded objects or external links. In addition to the monthly CPR, monthly wInsight XML files and periodic submissions of a wInsight history file that contains CPR reporting level EV data from inception is required. The wInsight equivalent to this is the

WSA backup file. Requiring office shall receive an electronic notification from the contractor that the data is available.

All other addressees, shall only receive an electronic notification that the data is available.

b. Format 1 reporting shall be at Level 4 for all elements except Prime Mission Product elements , These WBS element shall be at Level 6 of the CWBS thereby providing visibility of the major hardware, software and integration/assembly components. Lower level reporting may be required for areas of significant technical, cost and /or schedule risk. The contractor, with Government approval, shall update Format 1 reporting levels requirement at major program transitions

(e.g.,program start, PDR, CDR start of test program).

c. Current month and cumulative cost (CV) and schedule variance (SV) explanations are required. Format 5 shall incorporate problem analyses and narrative explanations (highlighting root cause, impact, corrective action and expected recovery) for Format 1 elements when cost/schedule variances fall within the following categories (report the higher value either dollar amount):

- Current period cost variances exceeding $100K

-Current period schedule variances exceeding $100K

-Cumulative cost variances exceeding $500K

- Cumulative schedule variances exceeding $500K

- Variances at completion exceeding $500K

-Other cost and schedule variances or technical performance issues that are causing or are likely to cause significant schedule delays or cost overruns.

-The contractor with Government approval shall review and update threshold levels as required. As required, lower level detail maybe requested.

d. All Budget at Completion (BAC) changes on Format 1 shall be explained in Format 5. All Management Reserve (MR) transactions, including the work scope to be covered by the MR, and the amount of MR distributed to the applicable WBS element shall be explained on Format 5. Undistributed Budget (UB) transactions shall be explained in a similar manner.

The composition of UB, including Engineering Change Proposal (ECP) number and the associated contract modification dollar values (NTEs etc), shall also be listed in Format 5.

e. Specific corrective actions, forecasted closure date, and impact to the Estimate at Completion (EAC) shall be included in each variance narrative. Schedule variance narratives shall identify significant missed milestones, impact to major milestones, and expected recovery dates. Contractor shall go to lowest CWBS level necessary to completely explain the variances.

f. “Best case,” “Worst case,” and “Most Likely” EACs at the total contract level are required.

g. Format 2 of the CPR shall provide the contractor’s functional breakdown structure (e.g. Engineering, Manufacturing, Program Management, Quality, Test) or other organizational breakdown, e.g., by Integrated Product Teams (IPTs). No formal monthly variance analysis is required for Format 2; however, the contractor should be able to correlate the variances in Format 1 to Format 2.

h. Formats 3 and 4 should report the next 6 months in columns 4-9 and quarterly in columns 10-13. Column 14 will have the balance. Format 4 should be EAC headcount. Any change in the Format 3 total Performance Measurement Baseline

(PMB), and/or any change in the current or forecast periods that exceeds 5% shall be explained in detail in Format 5. Any change in current, forecast period, or total manpower for each Format 4 element, that exceeds 10% shall be explained in

Format 5. Explanation of the changes to the PMB shall include the movement of scope, schedule and budget for all periods.

i. The Government reserves the right to review and modify, through negotiations, the variance analysis requirements and reporting levels for Formats 1, 2, 3, and 4 during the performance of the contract.

j. Initial submission, Formats 1-5 are due 23 calendar days after first full accounting period. Formats 1-5, are due 12 days after end of previous monthly reporting period.

k. Format 1 will be reported by WBS, Formats 2 and 4 will be reported by IPT.

Other Notes:

• Block 9: For Official Use Only, exemption b)4) applies.

• Block 11: Last day of contractor’s monthly accounting period.

• Technical data or computer software that is not properly included on a data rights assertion list incorporated into the contract shall NOT be delivered with any restrictive markings.

• Technical data or computer software that is properly included on the data rights assertion list incorporated into the contract and containing "Limited Rights" or "Restricted Rights" legends as specified in DFARS 252.227-7013 and

252.227-7014 shall NOT be delivered under or in conjunction with this CDRL without prior approval of the Contracting

Officer or the Contracting Officer’s Representative.

• Under no circumstance shall technical data or computer software to be delivered under or in conjunction with this CDRL be marked "Proprietary" (or any similar nonconforming marking).

• "Technical data" is defined at DFARS 252.227-7013(a)(14) and means recorded information, regardless of the form or method of the recording, of a scientific or technical nature (including computer software documentation).

• "Computer software" is defined at DFARS 252.227-7014(a)(4).

B. EXHIBIT: B

C. CATEGORY: TDP TM OTHER X

D. SYSTEM/ITEM: CLEAR UEWR

1. DATA ITEM NO.: B006

2. TITLE OF DATA ITEM: INTEGRATED MASTER SCHEDULE

3. SUBTITLE: INTEGRATED MASTER PLAN

4. AUTHORITY: (Data Acquisition Document No.): DI-MGMT¬81650/T See Block 16

5. CONTRACT REFERENCE: SOW Para 5.1.3.2

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: Monthly

11. AS OF DATE: As Required

12. DATE OF FIRST SUBMISSION: See Block 16

13. DATE OF SUBSEQUENT SUBMISSION: See Block 16

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic copy on IDE

16. REMARKS: Block 4: Prepare IMS data in electronic format IAW current EVM policy ANSI/EIA – 748, for file format, utilize detailed instructions contained in DID DI-MGMT-81650. Utilize DoD All sub-contractor activities, that meet the the reporting threshold, shall be included in the IMS. Submitted schedules shall be compatible with Microsoft

Project 2003, or higher and in its original format.

Blocks 12 and 13: The contractor shall deliver the updated Integrated Master Plan (IMP) 15 days after contract award.

This will enable the Government to approve the IMP in sufficient time to generate the Integrated Master Schedule (IMS).

The first IMS monthly submission will be due 15 days prior to the Integrated Baseline Review. Subsequent submissions for monthly performance status reporting against the baseline plan, are due no later than fifteen (15) working day after the close of the fiscal month. The Government has Thirty (30) days to review and comment.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER___ X __

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B007.

2. TITLE OF DATA ITEM: UEWR PROGRAM PROTECTION MANAGEMENT PLAN (PPMP)

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-MISC-80711A/T See Block 16

5. CONTRACT REFERENCE: SOW Para 5.1.4

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: See Block 16

11. AS OF DATE: See Block 16

12. DATE OF FIRST SUBMISSION: See Block 16

13. DATE OF SUBSEQUENT SUBMISSION: See Block 16

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic Copy on IDE

16. REMARKS: Block 4: Contractor shall update existing UEWR Program Protection Management Plan to address

Clear-unique program protection efforts, utilizing supporting data from the GMD Program Protection Management Plan

(PPMP). The Contractor shall outline how they will assist the Government in protecting the BMDS program; specifically to ensure that the research, development and acquisition (RD&A) of BMDS capabilities, systems and technologies is not hindered, compromised or in any way defeated prior to fielding and, as a result, contribute to the survivability and increased longevity required once fielded. This requires security processes and structures that establish and assure the confidentiality, availability, and integrity of information used in conjunction with BMDS RD&A and supporting contracts.

Contractor security processes include, but are not limited to, identifying: (1) aspects of, or items within, the UEWR program, classified or unclassified, that require protection e.g. Critical Program Information (CPI) systems and/or technology (2) classification management; (3) physical, personnel and operations security; (4) international security, technology transfer and foreign disclosure.

10. Preparation Instructions and Content Requirements - Inputs should conform to the current PPMP format. Contractor format is acceptable but should, as a minimum, contain the following information:

A. System and Program Description, detailing unique UEWR characteristics (e.g. capabilities and structures)

B. Program and related information impacting CPI (e.g. critical information, systems & technologies), and related threats

(e.g. foreign collection threat).

C. Information Assurance Strategy

Blocks 10,11, 12 and 13: Submit PPMP 120 calendar days after contract definitization. Updates annually or as required.

B. EXHIBIT: A

C. CATEGORY: TDP___ TM___ OTHER_X____

D. SYSTEM/ITEM: CLEAR UEWR

1. CONTRACTOR: DATA ITEM NO.: B008

2. TITLE OF DATA ITEM: UEWR LOGISTICS SUPPORT PLAN (LSP) AND SUPPORTABILITY ANALYSIS

PLAN (SAP)

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-ILSS-80095

5. CONTRACT REFERENCE: SOW Para 3.6.3

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: Draft 30 calendar days prior to PDR and Final 30 calendar days prior to CDR

13. DATE OF SUBSEQUENT SUBMISSION: As Required

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic Copy on IDE

16. REMARKS: Use the existing support plans as quides to incorporate CLEAR UEWR. LSP will be updated for any major changes in the program.

Contractor format is acceptable. Prepare in contractor format using the Data Item Description (DID) as a guide. Including the following:

Deliver an Integrated Logistics Support Plan consistent with the DID with emphasis on documenting and delivery of requirements for supply support, training, computer resources, support equipment, technical order and data requirements, consistent with the Air Force’s two level maintenance concept and program office direction. Review system documentation and recommend design documents and formats for release to the Government. Define manpower and personnel requirements for system sustainment and notify the Government of staffing recommendations and shortfalls against the developers staffing recommendations. Plan for and support transition of the system and it’s impedimenta to the Government for sustainment.

Plan for and design to minimize obsolescence and lifecycle costs. As a minimum the contractor shall provide analysis and documentation of the following:

a) Best practices the contractor has identified to minimize system lifecycle and obsolescence costs

b) Actions the contractor is taking to address the UEWR goals of minimizing lifecycle and obsolescence costs.

c) Analysis of the lifecycle cost impacts of hardware and software decisions.

d) Recommendations and timeline for Government action to address open issues. The contractor is expected to bring issues to the Government’s attention while they are actionable.

e) Self assessment of the contractor’s implementation of obsolescence and lifecycle cost reduction strategies.

f) Technology independence and parts obsolescence risk mitigation plans;

g) Recommendations to reduce life cycle costs by modifying the support concept

Contractor format is acceptable. Prepare in contractor format using the Data Item Description (DID) as a guide. Including the following:

Deliver an Integrated Logistics Support Plan consistent with the DID with emphasis on documenting and delivery of requirements for supply support, training, computer resources, support equipment, technical order and data requirements, consistent with the Air Force’s two level maintenance concept and program office direction. Review system documentation and recommend design documents and formats for release to the Government. Define manpower and personnel requirements for system sustainment and notify the Government of staffing recommendations and shortfalls against the developers staffing recommendations. Plan for and support transition of the system and it’s impedimenta to the Government for sustainment.

Plan for and design to minimize obsolescence and lifecycle costs. As a minimum the contractor shall provide analysis and documentation of the following:

a) Best practices the contractor has identified to minimize system lifecycle and obsolescence costs

b) Actions the contractor is taking to address the UEWR goals of minimizing lifecycle and obsolescence costs.

c) Analysis of the lifecycle cost impacts of hardware and software decisions.

d) Recommendations and timeline for Government action to address open issues. The contractor is expected to bring issues to the Government’s attention while they are actionable.

e) Self assessment of the contractor’s implementation of obsolescence and lifecycle cost reduction strategies.

f) Technology independence and parts obsolescence risk mitigation plans;

g) Recommendations to reduce life cycle costs by modifying the support concept

Block 8, 10 and 12: Government review and approval (or disapproval) and comments will be provided within 30 days of the review of each document or CDRL submittal unless otherwise specified.

Blocks 10, 12, & 13: Align the CDRL delivery for delivery prior to Critical Design Review.

Block 14: Post to an accessible data base to distribute in electronic copy

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER___X__

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B010

2. TITLE OF DATA ITEM: ENGINEERING CHANGE PROPOSALS (ECPs)

3. SUBTITLE: ECPs and Advance Change/Study Notices (ACSNs)

4. AUTHORITY: (Data Acquisition Document No.): DI-CMAN-80639C, DI-CMAN-80642C, DI-CMAN-80643C, DI-SAFT-80104 & DI-SAFT-80103

5. CONTRACT REFERENCE: SOW Para 5.2.2

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: As Required

13. DATE OF SUBSEQUENT SUBMISSION: As Required

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic Copy on IDE

16. REMARKS: This CDRL applies to Specification Change Notices. Interface Change Notices, Notices of Revision, and Advance Change/Study Notices.

Block 4: 10.2 Revise to read as follows: The Engineering Change Proposal shall be in contractor format using ANSI/EIA-

649A as a guide.

Block 16: Contractor approves all Class II ECPs. An ECP is tentatively classified by the contractor. The ACO reviews all

Class II ECPs. If the ACO non-concurs with the tentative Class II determination the ECP becomes a Class I ECP.

This Data Item Description contains the requirements for preparation of Engineering Change Proposals (ECPs) for changes to the baseline system. An ECP is a change proposal resulting from the work task described by paragraph 5.3 of

ANSI/EIA-649A National Consensus Standard for Configuration Management dated August 1998 and approved by DOD on February 1. 1999. ECP submissions shall be one of three types: Specification Change Notice for a proposed change to the Level I System Baseline (ref: DID-CMAN-80639C & DID DI-CMAN-80643C). Interface Change Notice for a proposed change to an External Interface Control Document (ref: GMD Configuration Control Plan and GMD Interface

Control Plan), or Equipment Change accompanied by a Notice of Revision for a proposed change affecting system design, performance, production or support, ref: DI-CMAN-80642C.

The contractor shall prepare process and submit Advance Change Study Notices (ACSNs) to request a Request for

Proposal, or to suggest a change to the Government- controlled system baseline. The Government and Contractor will agree upon the time period for processing submissions under this CDRL. See additional instructions below.

All ECP paperwork and all blocks on the ACSN form must be completed before submittal, including the technical data

(description of change and identification of Statement of Work that govern the change), and the estimated cost for the effort. An ACSN number (#) may be obtained by calling by the Government Change Management Office, TBD. The

Government Procuring Contracting Officer (PCO) will examine letters of transmittal submitted for any ECP/ACSN delivered to the Government. Said letters shall identify:

1. The Technical Office of Primary Responsibility (OPR) person(s) (by name and organization), including a telephone number;

2. The suggested Government subject matter Office of OPR person(s) (by name and organization);

3. A suggested OPR (by name);

4. The ECP/ACSN number;

5. A brief technical description of change and associated primary Statement of Work paragraph; and

6. The estimated price.

The lack of any of the above will be cause for the Government PCO to reject the submitted package. Incomplete information will also be a basis for Government rejection of ECPs and ACSNs. Incomplete documents will be returned to the Originator for correction and resubmittal.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER___X__

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B011

2. TITLE OF DATA ITEM: REQUEST FOR DEVIATIONS AND WAIVERS

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-SAFT-80103, DI-SAFT-80104, DI-CMAN-80640C, DI-

SESS-81732

5. CONTRACT REFERENCE: SOW Para 5.2.2

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: As Required

13. DATE OF SUBSEQUENT SUBMISSION: As Required

14. DISTRIBUTION: See Appendix A

16. REMARKS: The Request for Waiver (RFW) shall be prepared in contractor format.

The Request for Deviation shall be prepared in contractor format. The RFD content shall use ANSI/EIA-649A as a guide.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER____X

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B012

2. TITLE OF DATA ITEM: SITE SECURITY MANAGEMENT PLAN (SSMP)

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-CMAN-80643B

5. CONTRACT REFERENCE: SOW Para 5.1.4

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: See Block 16

13. DATE OF SUBSEQUENT SUBMISSION: As Required

14. DISTRIBUTION: See Exhibit A

16. REMARKS: Prepare item in Data Item Description (DID) format.

Due 60 calendar days prior to start of on-site hardware installation.

This document prescribes requirements, restrictions, processes and procedures that are necessary to safeguard classified and sensitive program data from unauthorized disclosure at Clear AFS, Alaska and applies to MDA/BMDS Program

Personnel and contractors involved with the UEWR Radar program at Clear. This document does not supersede National

Security Policy. The MDA/SNU Program Office is responsible for the management of this document for the period of development/upgrade. The Site Security Management Plan is to be treated as a “living” document and will be reviewed and updated annually or as required.

Document content shall include guidance related to, incident reporting, security clearances, training (initial and refresher), debriefings, classification and marking/material controls/safeguarding, visit procedures, emergency procedures, camera policy; and any special security requirements, to include COMSEC and TEMPEST.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER_X____

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR.

F. CONTRACTOR:

1. DATA ITEM NO.: B013

2. TITLE OF DATA ITEM: SPECIFICATION CHANGE NOTICE (SCN)

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-CMAN-80643C

5. CONTRACT REFERENCE: SOW Para 52.2

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: As Required

12. DATE OF FIRST SUBMISSION: As Required

13. DATE OF SUBSEQUENT SUBMISSION: As Required

14. DISTRIBUTION: See Exhibit A

16. REMARKS: Prepare item in Data Item Description (DID) format.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER__X___

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B014

2. TITLE OF DATA ITEM: DT&E TEST PLANS AND PROCEDURES

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-QCIC-80553A

5. CONTRACT REFERENCE: SOW Para 5.4.2

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: DT&E Test Plans due 120 calendar days prior to formal test events. DT&E

Test Procedures due 75 calendar days prior to formal test event. Test Readiness Review (TRR) slides are due 7 working days prior to TRR. The Initial TRR is 90 days prior to Test start.

13. DATE OF SUBSEQUENT SUBMISSION: Subsequent TRRs are to be conducted 60/30/5 days prior to Test.

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic Copy on IDE

16. REMARKS: Contractor format acceptable. Test Plans should include Requirements Description, Verification

Strategy, Reference Documents, Test Setup and Descriptions, Acceptance Criteria, and Verification Prerequisites. The detailed test procedure to be used by the Contractor during testing delineates the manner, method, and sequence of tests to be performed IAW test plan. The Test Procedures, as a minimum, shall contain the following information: a) requirement(s) being tested, b) test setup, c) detailed operations to be performed by the test operator d) Test Verification

Matrix mapping test requirements to specified paragraphs e) exact method of verifications, f) conditions to be maintained,

g) success criteria, h) data formats, i) analysis methods, or acceptance criteria. Test Procedures include Test Information

Sheets.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER___X__

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B015

2. TITLE OF DATA ITEM: SOFTWARE TEST PLANS AND PROCEDURES

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-IPSC-81438A

5. CONTRACT REFERENCE: SOW Para 5.3.1

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: 30 calendar days prior to FQT Test Readiness Review (TRR)

13. DATE OF SUBSEQUENT SUBMISSION: As Required

14. DISTRIBUTION: See Exhibit A

Submit updates as required. Prepare in contractor format using the Data Item Description (DID) as a guide.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER___X__

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR: DATA ITEM NO.: B016

1. TITLE OF DATA ITEM: DATA ACCESSION LIST (DAL)

2. SUBTITLE:

3. AUTHORITY: (Data Acquisition Document No.): DI-MISC-80711A/T, DI-MGMT-81453A

4. CONTRACT REFERENCE: SOW Para 5.2.5.3

5. REQUIRING OFFICE: MDA/SN

6. DD250 REQ: LT

7. APP CODE: N

8. DISTRIBUTION STATEMENT REQUIRED: F

9. FREQUENCY: Monthly

10. AS OF DATE: N/A

11. DATE OF FIRST SUBMISSION: 60 calendar days after contract award

12. DATE OF SUBSEQUENT SUBMISSION: 20th calendar day of each month

13. DISTRIBUTION: See Exhibit A

14. TOTAL COPIES: Electronic Copy on IDE

15. REMARKS:

16. DAL items shall be submitted or placed on IDE. When electronic media is not available, one hard copy shall be provided to the requester. At a minimum, the DAL shall include the following documents.

DAL items - Internal data encompasses Automated Data Products (ADPs) produced under the contract Statement of Work that is not specifically a CDRL requirement. DAL is to include update of technical documents to reflect the CLEAR

UEWR configuration.

17.

B. EXHIBIT: B

C. CATEGORY: TDP__X_ TM___ OTHER__ ___

D. SYSTEM/ITEM: CLEAR UEWR

1. DATA ITEM NO.: B017

2. TITLE OF DATA ITEM: TECHNICAL DATA PACKAGE (TDP)

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): MIL-STD-31000, DI-SESS-81000D

5. CONTRACT REFERENCE: SOW Para: 5.3.2

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: N

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: 30 calendar days prior to Prime Mission Equipment (PME) Ship Readiness Review

(SRR)

13. DATE OF SUBSEQUENT SUBMISSION: Final due 90 calendar days prior to formal UEWR transfer (i.e. DD 250)

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic Copy on IDE

16. REMARKS: Submit updates as required to document system configuration. Prepare in contractor format using the

Data Item Description (DID) as a guide.

The purpose of the TDP is to specify the types of drawings required to substantiate and define the configurations (SEIs) delivered under the governing subcontract/purchase order. Since the governing subcontract/purchase order covers development, production, deployment, and sustaining phases; the primary types of drawings required will be as defined in

MIL-DTL-31000, Paragraphs 3.6.1, 3.6.2, and 3.6.3. An As-Designed Parts, Materials, and Processes List (ADPMPL) shall be included as part of the Associated Lists. The ADPMPL shall comply with basic requirements of DI-MISC-81276, as modified/tailored in accordance with the tailoring specified herein. This PDRD is also intended to cover Seller Class II

Engineering Orders EO(s)/Change Requests CR(s) used to convey Seller dispositioned changes to engineering drawings ands associated lists. All TDP documents, including hardware drawings, will be placed on CD ROMs in AutoCad compatible format.

A. Drawing Requirements and Tailoring for DI-DRPR-81000

Conceptual Drawings: Per Paragraph 3.6.1 of MIL-DTL-31000, in accordance with Seller Best Practices for Format and

Content. Developmental Drawings: Per Paragraph 3.6.2 of MIL-DTL-31000, in accordance with Seller Best Practices for Format and Content. Production Drawings: Per Paragraph 3.6.3 of MIL-DTL-31000, in accordance with the applicable SOW requirements, and paragraphs 3.2.3.1 and 3.2.3.2 of D743-11965-1. Seller format and content is acceptable providing it is commensurate with/satisfies the requirements specified herein and DI-DRPR-81000 tailoring as specified below. DI-DRPR-81000 Tailoring as follows:

Block 3. DESCRIPTION/PURPOSE

3.1 For purposes of this contract, Product Drawings and Associated Lists provide the engineering data to support the delivery requirements of the Seller's End Item, Assembly, and/or Component Part Configurations. These drawings represent the highest level of design disclosure commensurate with the fidelity and usage requirements for the deliverable

End Item, Assembly, and/or Component Part configuration.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER__X___

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B018

2. TITLE OF DATA ITEM: DESIGN REVIEWS

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.):

5. CONTRACT REFERENCE: SOW Para 5.6.1

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: As Required

13. DATE OF SUBSEQUENT SUBMISSION: As Required

14. DISTRIBUTION: See Exhibit B

16. REMARKS: Prepare in contractor format using the Data Item Description (DID) as a guide.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER__X___

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B019

2. TITLE OF DATA ITEM: SCIENTIFIC AND TECHNICAL REPORTS

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-MISC-80711/T

5. CONTRACT REFERENCE: SOW Para 5.2

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: As Required

13. DATE OF SUBSEQUENT SUBMISSION: As Required

14. DISTRIBUTION: See Exhibit A

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER_X____

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B020

2. TITLE OF DATA ITEM: TECHNICAL PUBLICATIONS PLAN

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-MISC-80711/T

5. CONTRACT REFERENCE: SOW Para 5.7.1

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE:A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: 120 days after contract definitization

13. DATE OF SUBSEQUENT SUBMISSION: As Required

14. DISTRIBUTION: See Exhibit A

16. REMARKS: Prepare in contractor format using the Data Item Description (DID) as a guide

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER_X___

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B021

2. TITLE OF DATA ITEM: SOFTWARE USERS MANUAL (SUM)

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-IPSC-81443A

5. CONTRACT REFERENCE: SOW Para 5.3.1

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: As Required

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: 30 calendar days prior to first formal on-site training (e.g. Analyst Training)

13. DATE OF SUBSEQUENT SUBMISSION: As Required

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic Copy on IDE

16. REMARKS: Submit updates as required to incorporate Clear in the UEWR documentation. Prepare in contractor format using the Data Item Description (DID) as a guide in accordance with best commercial practices. Data Item includes data reduction user’s manual, special reports and Software Users Manual for all 13 Jobdecks (LOOKALL, POSNEG, FASTSAT, RCS, LRID94p, LRID92i, ALERTS, NONO, SDTL, TASKL/STARRPT, SATMISS, MWOC1A and

OPRACTN)

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER_X____

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B023

2. TITLE OF DATA ITEM: IA ADMINISTRATORS GUIDE (AG)

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DODI-8500.2 Information Assurance Implementation, dated

February 2003; examples of the specific controls/requirements include controls numbers 96 PESP-1 and 102 PRRB-1

5. CONTRACT REFERENCE: SOW Para 5.2.6

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: See Block 16

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: 180 calendar days prior to start of on-site hardware installation

13. DATE OF SUBSEQUENT SUBMISSION: As Required

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic Copy on IDE

16. REMARKS: The Contractor shall provide a one full revision update every year to the IA Admin Guide. In addition, minor revision updates are required no more than quarterly as a result of changes in threats or vulnerabilities.

Special Note: The IA Administrator Guides (AGs) document the administrative procedures, roles, functions, privileges and processes that are necessary to ensure secure system configuration, administration, and operation throughout the system’s life-cycle. As such, preparation and periodic update to the AGs shall be coordinated with system owner, developer, operator/user, and sustainment organizations/teams.

The Administrator Guide (AG) will contain the following:

Component Security Architecture

Component Security Overview

Threats and Security Philosophy

Baseline Security Configuration and Network Security Configuration

Security and Accountability Countermeasures Description

Security Education Procedures

IA Roles & Responsibilities

Information Assurance Officer (IAO)

System Administrator (SA) attributes

Network Administrator/Manager (NA) attributes

Resident Engineer

Maintenance Personnel

Mission Operators

Configuration Management Process

Root Access Procedures

User Accounts Procedures

Auditing Procedures

System Backup Procedures

Monitoring Procedures

Anti-Virus (AV) Management Process

Disaster Recovery and Contingency Planning Process

Incident Response and Reporting Process (IRRP) Planning

The submission will be in Microsoft Word Format and submitted electronically. Contractor format is acceptable.

B. EXHIBIT: B

C. CATEGORY: TDP___ TM___ OTHER___X__

D. SYSTEM/ITEM: CLEAR UEWR

E. CONTRACT/PR. NO:

F. CONTRACTOR:

1. DATA ITEM NO.: B024

2. TITLE OF DATA ITEM: FAILURE MODES, EFFECTS AND CRITICALITY ANALYSIS (FMECA) &

CRITICAL ITEMS LIST (CIL)

3. SUBTITLE:

4. AUTHORITY: (Data Acquisition Document No.): DI-ILSS-81495

5. CONTRACT REFERENCE: Sow Para: 5.2.1

6. REQUIRING OFFICE: MDA/SN

7. DD250 REQ: LT

8. APP CODE: A

9. DISTRIBUTION STATEMENT REQUIRED: F

10. FREQUENCY: See Block 16

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: See Block 16

13. DATE OF SUBSEQUENT SUBMISSION: See Block 16

14. DISTRIBUTION: See Exhibit A

15. TOTAL COPIES: Electronic Copy on IDE

16. REMARKS: Submit initial document which incorporates Clear configuration in the UEWR documentation. Post to an accessible data library. Prepare in contractor format using the Data Item Description (DID) as a guide in accordance with best commercial practices.

10, 12, 13 SUBMITTAL SCHEDULE The initial submittal of the FMECA, including Criticality Analysis (CA), is due 90 calendar days after REX 1 is delivered to the Clear Deployable String. Subsequent submittals will occur annually.

DESCRIPTION / PURPOSE The Failure Modes, Effects and Criticality Analysis (FMECA) report determines by failure mode analysis, the effect of each functional failure on system operation and identifies single failure points, i.e., those failures critical to mission success or personnel safety.