Atch 02 - Scope of Work

Clear-Cod UEWR SOW- 6 Feb 2012

Contract #: HQ0147-11-R-0002

Upgraded Early Warning Radar (UEWR)

(Clear and Cape Cod)

Statement of Work

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 Export Administration

Act of 1979, as amended (50

U.S.C Appendix 2401 et. Seq.).

Violation of these export laws is subject to sever criminal penalties. Disseminate in accordance with provisions of

DOD Directive 5230.25 and

AFI 61-204.

DISTRIBUTION STATEMENT D

Distribution authorized to U.S.

Government agencies and their contractors. Other requests for this document shall be referred to:

MISSILE DEFENSE AGENCY (MDA)

SENSORS DIRECTORATE (SN)

HUNTSVILLE, ALABAMA

35897-3801

FOR OFFICIAL USE ONLY

STATEMENT

This document contains information exempt from mandatory disclosure under the

FOIA. Exemption (3) applies

(10 USC 130, Authority to

Withhold Unclassified

Technical Data with Space or

Military Application).

Clear-Cod UEWR SOW- 6 Feb 2012

TABLE OF CONTENTS 1

1. Introduction _________________________________________________________________ 1

1.1 Introduction ________________________________________________________________ 1

1.2 Background ________________________________________________________________ 2

1.3 Government Actions _________________________________________________________ 2

2. Applicable Documents _________________________________________________________ 3

2.1 Reference Documents ________________________________________________________ 3

2.2 Common Compliance Documents ______________________________________________ 4

2.2.1 UEWR Technical Documents ________________________________________________ 9

2.2.2 UEWR Interface Control Documents (ICD)/Interface Design Documents (IDD) ________ 9

3.0 Requirements ________________________________________________________________ 9

3.1 Program Management _______________________________________________________ 10

3.1.1 Integrated Product and Process Development (IPPD) ____________________________ 10

3.1.1.1 Technical Interchange Meeting (TIM)_______________________________________________________________ 11

3.1.2 Program Management Reviews _____________________________________________ 11

3.1.3 Business Operations ______________________________________________________ 11

3.1.3.1 Integrated Baseline Reviews (IBR) __________________________________________________________________ 12

3.1.3.2 Integrated Master Schedule (IMS) ___________________________________________________________________ 12

3.1.3.3 Joint Master Schedule (JMS) ________________________________________________________________________ 12

3.1.4 Security ________________________________________________________________ 13

3.1.4.1 Information Security _________________________________________________________________________________ 13

3.1.4.2 Program Protection __________________________________________________________________________________ 13

3.1.4.3 Supply Chain Risk Management _____________________________________________________________________ 14

3.1.5 Small Business __________________________________________________________ 14

3.2 Systems Engineering ________________________________________________________ 14

3.2.1 Specialty Engineering _____________________________________________________ 15

3.2.2 MDA Sensors System Requirements Allocation/Management _____________________ 16

3.2.2.1 Interface Definition for UEWR ______________________________________________________________________ 16 ii

3.2.3 Risk Management ________________________________________________________ 16

3.2.4 Safety, Quality, and Mission Assurance (SQMA) _______________________________ 16

3.2.4.1 Safety _________________________________________________________________________________________________ 17

3.2.4.2 Quality Assurance (QA) _____________________________________________________________________________ 17

3.2.5 Configuration Management (CM)/Data Management ____________________________ 19

3.2.5.1 Configuration Management (CM) __________________________________________________________________ 19

3.2.5.2 Configuration Reviews, Verification, and Audits____________________________________________________ 19

3.2.5.3 Data Management ___________________________________________________________________________________ 19

3.2.6 Information Assurance (IA) ________________________________________________ 20

3.3 Radar Software/Hardware Development ________________________________________ 21

3.3.1 Radar Software __________________________________________________________ 22

3.3.1.1 Signal Processor /Data Processor (SP/DP) Rehost Effort __________________________________________ 23

3.3.1.2 Clear UEWR software upgrade______________________________________________________________________ 23

3.3.1.3 Version Content Notice (VCN) Synchronization Update ____________________________________________ 23

3.3.2 Radar Hardware _________________________________________________________ 23

3.3.2.1 Obsolescence Redesign ______________________________________________________________________________ 24

3.3.2.2 Signal Processor/Data Processor (SP/DP) _________________________________________________________ 25

3.3.2.3 Prime Mission Equipment (PME), PME Site Spares and PME Replenishment Spares ____________ 25

3.3.2.4 Interim Equipment ___________________________________________________________________________________ 26

3.3.2.5 Peculiar & Common Support Equipment ___________________________________________________________ 26

3.3.2.6 PME Development String ____________________________________________________________________________ 26

3.3.2.7 Huntsville Laboratory _______________________________________________________________________________ 26

3.4 Test _____________________________________________________________________ 27

3.4.1 Baseline Testing and Interim Operational Acceptance ____________________________ 27

3.4.2 Development Testing (DT) _________________________________________________ 27

3.4.3 Test / Shipment Readiness Reviews (TRR/SRR) ________________________________ 27

3.4.4 Support to Operational Test (Support to Force Development Evaluation (FDE) and Trial

Period _________________________________________________________________ 28

3.5 Studies and Analyses Option (Level of Effort) ____________________________________ 28

3.6 Facility Design & Construction/Sustainment _____________________________________ 28

3.6.1 Facilities Design ____________________________________________________________ 28

3.6.1.1 Beale Facilities Design and Construction ___________________________________________________________ 28

3.6.1.2 Clear Facilities Design ______________________________________________________________________________ 28

3.6.1.3 Clear Site Construction ______________________________________________________________________________ 29

3.6.2 Post Operational Activities _________________________________________________ 30 iii

3.6.3 Integrated Logistic Support (ILS) ____________________________________________ 30

3.6.3.1 Technical Publications ______________________________________________________________________________ 30

3.6.3.2 Training ______________________________________________________________________________________________ 30

3.6.3.3 Government Property and Item Unique Identification (IUID) _____________________________________ 31

3.6.3.4 Logistics Data Product (LDP) _______________________________________________________________________ 32

3.6.3.5 Provisioning/Supply Support Planning ______________________________________________________________ 32

3.6.3.6 Packaging, Handling, Storage and Transportation (PHS&T) ______________________________________ 32

3.6.4 Contractor Logistics Support _______________________________________________ 32

4. Cape Cod Long Lead Option __________________________________________________ 33

5. Cape Cod Option ____________________________________________________________ 33

5.1 Program Management _______________________________________________________ 33

5.1.1 Integrated Product and Process Development (IPPD) ____________________________ 33

5.1.1.1 Technical Interchange Meeting (TIM)_______________________________________________________________ 34

5.1.2 Program Management Reviews _____________________________________________ 34

5.1.3 Business Operations ______________________________________________________ 34

5.1.3.1 Integrated Baseline Reviews (IBR) __________________________________________________________________ 35

5.1.3.2 Integrated Master Schedule (IMS) ___________________________________________________________________ 35

5.1.3.3 Joint Master Schedule (JMS) ________________________________________________________________________ 35

5.1.4 Security ________________________________________________________________ 35

5.1.4.1 Information Security _________________________________________________________________________________ 36

5.1.4.2 Program Protection __________________________________________________________________________________ 36

5.1.4.3 Supply Chain Risk Management _____________________________________________________________________ 37

5.1.5 Small Business __________________________________________________________ 37

5.2 Systems Engineering ________________________________________________________ 37

5.2.1 Specialty Engineering _____________________________________________________ 38

5.2.2 MDA Sensors System Requirements Allocation/Management _____________________ 39

5.2.2.1 Interface Definition for UEWR ______________________________________________________________________ 39

5.2.3 Risk Management ________________________________________________________ 39

5.2.4 Safety, Quality, and Mission Assurance (SQMA) _______________________________ 39

5.2.4.1 Safety _________________________________________________________________________________________________ 40

5.2.4.2 Quality Assurance (QA) _____________________________________________________________________________ 40

5.2.5 Configuration Management (CM)/Data Management (DM) _______________________ 42

5.2.5.1 Configuration Management _________________________________________________________________________ 42

5.2.5.2 Configuration Reviews, Verification, and Audits____________________________________________________ 42

5.2.5.3 Data Management ___________________________________________________________________________________ 42 iv

5.2.6 Information Assurance (IA) ________________________________________________ 43

5.3 Radar Software/Hardware Development ________________________________________ 44

5.3.1 Radar Software __________________________________________________________ 44

5.3.2 Radar Hardware _________________________________________________________ 45

5.3.2.1 Prime Mission Equipment (PME), PME Site Spares and PME Replenishment Spares ____________ 46

5.3.2. 2 Interim Equipment ___________________________________________________________________________________ 46

5.3.2.3 Peculiar & Common Support Equipment ___________________________________________________________ 46

5.3.2.4 PME Development String ____________________________________________________________________________ 47

5.3.2.5 Huntsville Laboratory _______________________________________________________________________________ 47

5.4 Test _____________________________________________________________________ 47

5.4.1 Baseline Testing and Interim Operational Acceptance ____________________________ 47

5.4.2 Development Testing (DT) _________________________________________________ 47

5.4.3 Test / Shipping Readiness Reviews (TRR/SRR) ________________________________ 48

5.4.4 Support to Operational Test (Support to Force Development Evaluation (FDE) and Trial

Period _________________________________________________________________ 48

5.5 Studies and Analyses Option _________________________________________________ 48

5.6 Cape Cod Facilities _________________________________________________________ 49

5.6.1 Facilities Design _________________________________________________________ 49

5.6.2 Cape Cod Site Construction ________________________________________________ 49

5.6.3 Post Operational Activities_________________________________________________ 50

5.7 Integrated Logistic Support (ILS) ______________________________________________ 51

5.7.1 Technical Publications ____________________________________________________ 51

5.7.2 Training ________________________________________________________________ 51

5.7.3 Government Property and Item Unique Identification (IUID) ______________________ 52

5.7.4 Logistics Data Products (LDP) ______________________________________________ 52

5.7.5 Provisioning/Supply Support Planning ________________________________________ 52

5.7.6 Packaging, Handling, Storage and Transportation (PHS&T) _______________________ 53

5.8 Contractor Logistics Support _________________________________________________ 53

5.8.1 Transfer of Development String _____________________________________________ 53 v

THIS PAGE INTENTIONALLY LEFT BLANK

STATEMENT OF WORK (SOW) 1

Sensors UEWR 2

1. Introduction 4

1.1 Introduction 6

This contract shall upgrade the Early Warning Radar (EWR) at Clear Air Force Station (AFS), Alaska, 7 with an option for Cape Cod AFS, Massachusetts (herein referred to as the Clear Upgrade and Cape Cod 8

Upgrade respectively). Under this contract the Signal Processors (SP) and Data Processors (DP) at Beale 9

Air Force Base (AFB), California shall be rehosted yielding a clean and stable baseline for the Clear 10 upgrade (and the Cape Cod upgrade if contract option is exercised). The primary purpose of the Clear 11 and Cape Cod upgrades is to add a missile defense capability to the existing missile warning and space 12 surveillance missions, while maintaining the on-going operational mission. The contractor shall be 13 responsible for working with the Missile Defense Agency (MDA) Ballistic Missile Defense System 14

(BMDS) integration/communication contractors to establish connectivity from the radar to the Ground-15

Based Midcourse Defense (GMD) Fire Control and Communication (GFCC). The Clear Upgrade shall 16 be designed based on Revision G of the Prime Item Development Specification (PIDS) and this SOW. 17

Although not required under the provisions of this contract to fully implement the requirements of PIDS 18

Rev H and the BMD System Specification (SS), the design shall be modular, scalable, flexible, and robust 19 enough to be able to address these additional and future emerging requirements without significant 20 architecture modifications. The contractor shall develop and maintain an open architecture that is: 21 reconfigurable, portable, maintainable, capable of technology insertion, vendor- independent, 22 reusable, scalable, interoperable, upgradeable, and long-term supportable. The contractor 23 modular design and integration shall maximize the use of COTS component/ interface standards, 24 technologies, products, or architectures while ensuring logistical supportability throughout the 25 life cycle. 26

The Clear Upgrade is envisioned to consist of a team of multiple contractors: UEWR contractor; United 28

States Army Corps of Engineers (USACE) site construction contractor; all Command, Control, Battle 29

Management, and Communication (C2BMC) GFCC agencies and contractors; and the Single Stimulation 30

Framework (SSF) contractor. The scope of work defined in this Request for Proposal (RFP) is limited to 31 the radar upgrade. Additionally, there will be several concurrent efforts at Clear which will require 32 careful scheduling coordination and de-confliction throughout this upgrade. 33

The Cape Cod Upgrade will be an option to the base contract. Should the Cape Cod option be exercised, 35 the contractor shall implement the Clear Upgrade design, install, and test this capability into the Cape Cod 36 system. The contractor shall support all UEWR integration efforts into the BMDS. 37

1.2 Background 42

The initial Upgraded Early Warning Radar (UEWR) effort was part of the April 1998 contract for the 43

Lead System Integrator for the Ground-Based, Midcourse Defense (GMD) segment of the Ballistic 44

Missile Defense System (BMDS). A second GMD contract in 2001 deployed both Beale and Fylingdales 45

UEWRs. A Thule UEWR Contract followed in 2006 with the BMDS integration completed under the 46

GMD Core Completion (BMDS Integration) Contract in 2008. This EWR upgrade contract documents 47 the requirements for upgrading the EWR at Clear AFS, Alaska, with a follow-up option to also upgrade 48 the EWR at Cape Cod AFS, Massachusetts. 49

1.3 Government Actions 50

The Government is expected to take the following actions in support of the UEWR contractor for the 51 course of the period of performance: 52

Co-chair the UEWR contractor Integrated Product Teams (IPT) as an approving member in 53 addressing the issues relevant to each IPT. Assignments to the various IPTs may vary based 54 on the direction of the UEWR Government Program Manager. 55

Provide sponsorship and funding to the U.S. Army Corps of Engineers for the 56 implementation of the Clear UEWR facility and site requirements in accordance with the 57 information provided to and incorporated into the MDA Facility Requirements Document 58

(FRD) for Clear. 59

Provide sponsorship and coordination to facilitate direct interface between the UEWR 60 contractor and other contractors and Government organizations (e.g., Air Force Space 61

Command (AFSPC), US Strategic Command (USSTRATCOM), US Northern Command, 62

MDA, Electronic Systems Center Missile Warning, Defense, and Wideband Sensors Branch 63

Sustainment Office (ESC/HSIGS), the USAF Sustainment contractor; Operational Test 64

Agency (OTA); other Government programs (e.g., Single Stimulation Framework (SSF), and 65 all communications for C2BMC and GMD to connect UEWR to GMD Fire Control System 66 support agencies and contractors in support of Ballistic Missile Defense Systems)). Upon 67

BMDS integration and upgrade completion, Clear and Cape Cod will be certified and added 68 to the BMDS architecture. 69

Facility changes required at the Centralized Integration Support Facility (CISF) shall be the 70 responsibility of the Government. 71

Develop and process Software Change Forms (SCF) and 1067s (Modification Proposal) for 72

SP/DP design at Beale. 73

Obtaining system accreditation and authorization to operate for all missions is the 74 responsibility of the Government. 75

2. Applicable Documents 82

All documents listed in this SOW shall apply to the base and option. 83

2.1 Reference Documents 84

The following documents are provided for guidance. 85

Document Name Date

UEWR PIDS H293101

UEWR Prime Item Development

Specification (Revision H) 2 Mar 11

BMD SS

Draft BMD System Specification

Requirements (UEWR Portion)

Document No.S-247-5.1

18 Jul 11

MIL-HDBK-61A Configuration Management Guidance 7 Feb 01

MIL-HDBK 502 Acquisition Logistics 20 Jan 05

J-STD-016-1995

Trial-Use Standard for Information

Technology Software Life Cycle

Processes - Software Development

30 Sep 95

ANSI/AIAA R-100-1996

Recommended Practice for Parts

Management 20 Aug 97

ANSI/GEIA EIA-649A

National Consensus Standard for

Configuration Management 1 Apr 04

NOAA Data

National Oceanic and Atmospheric

Administration Global Summary of the

Day www7.ncdc.n oaa.gov

International Solar Cycle

NASA/TP-2004-212020, An Improved

Solar Cycle Statistical Model for the

Projection of Near Future Sunspots (08

Nov 96)-- Solar Cycle 23 Project:

Summary of Panel Findings

Sep 04

ITU-R P.676-5

International Telecommunications

Union Method: Attenuation by

Atmospheric Gasses

Feb 01

POAM

UEWR Information Assurance (IA)

Plan of Action and Milestones

Updated

Quarterly

ITU-R P.837-4

International Telecommunications

Union Method: Effects of Refraction on

Radio Wave Propagation Patterns

Feb 01

GAO-09-3SP

GAO Cost Estimating and Assessment

Guide Mar 09

DOD Risk Mgt Guidebook DOD Risk Management Guidebook 6 th edition Version 1 14 Aug 06

IMP and IMS DOD Version 0.9 Integrated Master Plan and the

Integrated Master Schedule Preparation: 21 Oct 05

MDA 3058.01-INS Risk Management 15 Apr 11

MDA 5010.24-INS

Performing an Engineering

Manufacturing Readiness Level

Assessment, MDA 5010.24-INS 12 Jul 10

12207-2008 ISO/IEC/IEEE

Standard for Systems and Software

Engineering Software Life Cycle

Processes

31 Jan 08

2.2 Common Compliance Documents 88

The following documents, of the exact issue specified, form a part of this UEWR Statement of Work 89 which shall be executed in accordance with (IAW) the documents specified herein. Where no date is 90 specified, the revision of the document current as of the date of this Statement of Work applies. In the 91 event of a conflict between any of the following documents and this Statement of Work, this Statement of 92

Work shall have precedence. 93

Document Name Date

GOVERNMENT

DOCUMENTS

UEWR PIDS UEWR Prime Item Development

Specification (Revision G) Doc

No. H293101

1 Jul 10

NOTE: When PIDS is invoked in this contract, it includes the following updated

UEWR PIDS documents.

DOD 5200.1-R Information Security Program

Regulation

Oct 08

DOD 5200.8-R Department of Defense Physical

Security Program

Mar 08

DODI 6055.11 Protecting Personnel From

Electromagnetic Fields

19 Aug 09

ESD/SCT-00001A Performance Specification for the

Phased Array Warning System, PAVE PAWS, AN-FPS-123(V)1, V2, V3, V4, Rev E

Jul 10

MIL-HDBK-454 General Guidelines for Electronic

Equipment

15 Apr 07

MIL-HDBK-1791 Designing for Internal Aerial

Delivery in Fixed Wing Aircraft

14 Feb 97

MIL-STD-461 F Requirements for the Control of

Electromagnetic Interface

Characteristics of Subsystems and

10 Dec 07

Equipment

MIL-STD-464C Department of Defense Interface

Standard: Electromagnetic

Environmental Effects

Requirements for Systems

1 Dec 10

MIL-STD-810G Department of Defense Test

Method Standard for

Environmental Engineering

Considerations and Laboratory

Tests

31 Oct 08

MIL-STD-882D Standard Practice for System

Safety

10 Feb 00

MIL-STD-1366E Interface Standard

Transportability Criteria

31 Oct 06

MIL-STD-1472F Department of Defense Design

Criteria Standard: Human

Engineering

5 Dec 03

National Security

Telecommunications and

Information Systems

Security Advisory

Memorandum

(NSTISSAM)

Tempest/2-95 Red/Black

Installation Guidance 12 Dec 95

AR 70-38 Research, Development, Test and

Evaluation of Material for

Extreme Climate Conditions

16 Jan 06

49 CFR 100-185 Code of Federal Regulations, Title 49, Parts 100-185, "Transportation"

1 Oct 08

DOD JTA Ver. 6.0 DOD Joint Technical

Architecture, 3 Oct 03

End of UEWR PIDS Documents

UEWR S-T PIDS UEWR Simulator Tester

Doc No. H310673; Revision F

1 Jul 10

AFI 33-201 Communications Security 1 May 05

BMDS 5004.01-INS BMDS IBR Instruction 5004.01-

INS

Dec 10

29 CFR 1910.147 Code of Federal Regulations, Title 29, Labor Part 1910, Occupational Safety and Health

Standards, Control of Hazardous

Energy (Lockout/Tag-out), 01

July 2005

1 Jul 05

CJCSI 6212.01E Chairman of the Joint Chiefs of

Staff Instruction Interoperability and Supportability of Information

Technology and National Security

Systems

15 Dec 08

CJCSI 6510.01F Information Assurance (IA) and

Support to Computer Network

Defense (CND)

9 Feb 11

CJCSI 6511.01 Chairman of the Joint Chiefs of

Staff Instruction Information

Security Guidelines for the

Deployment of Deployable

Switched Systems

1 Feb 01

DOD 4140.1-R DOD Supply Chain Materiel

Management Regulation

23 May 03

DODI 5200.1-M Acquisition Systems Protection Program

16 Mar 94

DODI 5200.39 Critical Program Information

(CPI) Protection with the

Department of Defense;

Change 1

16 Jul 08

28 Dec 10

DODD 8500.1 Information Assurance (IA) 24 Oct 02

DOD 8500.01E Information Assurance(IA), 23 Apr 07

DODI 8510.01 DOD Information Assurance

Certification and Accreditation

Process (DIACAP)

28 Nov 07

DODD 8570.1 Information Assurance Training, Certification, and Workforce

Management

23 Apr 07

DOD 8570.01-M Information Assurance Workforce

Improvement Program

20 Apr 10

DODI 8581.1 Information Assurance (IA)

Policy for Space Systems used by the DOD

8 Jun 10

DODI 8320.04 Item Unique Identification

Standards for Tangible Personal

Property

16 Jun 08

DTM-8-27 Chg 1 Directive Type Memorandum

(DTM 8-27; Security of

Unclassified DOD Information on

Non-DOD Information Systems

31 Jul 09

Change 1

01Sep 10

DTM-09-016 Supply Chain Risk Management 25 Mar 10

(SCRM) to Improve the integrity of Components Used in DOD

Systems

MDA 5200.08-INS Critical Program Information

Protection Within the Missile

Defense Agency

01 Aug 11

MDA 8500.02-P MDA Information Assurance

Program Plan

3 Oct 07

MDA-QS-001-MAP Rev

A

MDA Assurance Provisions

(MAP)

29 Oct 06

MDA-QS-001-MAP Rev

A Change 1

MDA Assurance Provisions

(MAP)

20 May 09

MDA-QS-003-PMAP-

Rev A

MDA Parts, Materials, and

Processes Mission Assurance

Plan (PMAP)

26 Mar 08

MDA Instruction 4161.01 Accountability and Reporting of

MDA Accountable Property

29 Mar 11

MDA Directive 4161.02 Item Unique Identification 21 Apr 10

MDA 5004.01H MDA Integrated Baseline Review

Handbook 5004.01-H 8 Feb 06

MDA 6055.02-M Safety Investigations and

Reporting Manual

29 Mar 06

MDA IA Plan MDA Information Assurance

Plan

MDA Policy

Memorandum #50

MDA Policy on Purchasing

Electronic Parts

29 Jun 09

MDA Policy MDA Policy for Unfettered and

Unrestricted Access

30 Mar 09

MDA Memorandum Material Review Board (MRB)

Authority

23 Oct 09

National Security

Telecommunications and

Information Systems

Information (NSTISSI)

Protective Distribution Systems 13 Dec 06

NSA Guidance for

Addressing Malicious

Code Risk

National Security Agency

Guidance For Addressing

Malicious Code Risk

10 Sep 07

National Security

Telecommunications and

Information Systems

Security Policy

National Policy Governing the

Acquisition of Information

Assurance (IA) and IA-Enabled

Information Technology (IT)

Products (note: National Security

Original

Jan 22

R Jun 03

(NSTISSP) Number 11 Telecommunications and

Information Systems Committee now known as Committee on

National Security Systems

(CNSS))

NDAA 932 National Defense Acquisition Act FY 10

NEPA 42 National Environment Protection

Act (NEPA) 42 U.S.C. 4321-

4370d, implementing regulation

(40 C.F.R. 15000-1508) and associated Executive Orders (E.O.

12114 Environmental Effects

Abroad of Major Federal Actions, and E.O. 11514, Protection and enhancement of Environmental

Quality).

13 Sep 82

USSTRATCOM Directive

538-2

Global Ballistic missile Defense

Systems (GBMDS) Physical

Security Program

03 Oct 05

SAE AS 9100 Rev B SAE Aerospace Standard: Quality

Management Systems Aerospace

Requirements

1 Apr 07

MIL-STD-130N Department of Defense Standard Practice, Identification Marking of U.S. Military Property, 17 De Department of Defense Standard

Practice, Identification Marking of U.S. Military Property

17 Dec 07

MIL-STD-881C Work Breakdown Structure for

Defense Material Items

3 Oct 11

MIL-DTL-31000D Technical Data Packages 5 Nov 09

SS PPP Sensors Sustainment Program

Protection Plan(being updated)

17 Apr 09

TO 00-35D-54 USAF Deficiency Reporting and

Investigation System

1 Oct 09

CCPD UEWR Change Control Process

Document

May 08

UEWR Support Concept Dec 03

Pub L. No .91-190 Frequency Authorization Pub L.

No 91-190 (1970)

1 Jan 70

American National

Standards Institute

(ANSI)/Electronic

Industries Alliance (EIA)-

748-1998

Earned Value Management

Systems

GEIA-STD-0007 Logistics Product Data, Version1.0

31 May 07

2.2.1 UEWR Technical Documents 96

G760805 Hazardous Materials Management Program Plan (CDRL A018) 97

H292487 XBR/UEWR Product Assurance Plan (Automated Data Product (ADP) 22) 98

G761775 Electromagnetic Compatibility (EMC) Control Plan (ADP 32) 99

G760806 Human Systems Integration Program Plan (HSIPP) (ADP 28) 100

H292487 Reliability, Availability, Maintainability and Testability (RAM-T) Program Plan (ADP 23) 101

G760162 Software Design Description (SDD) of the Mission Application Software (MAS) (ADP 17) 102

H366713 Software Product Specification (SPS) (ADP 19) 103

G760923 Interface Design Description (IDD) for the Mission Application Software / Simulation & 104

Tools Software (MAS/STS) (ADP 43) 105

G760915 Software Requirements Specification (SRS) for the Mission Application Software (MAS) 106

(ADP 26) 107

2.2.2 UEWR Interface Control Documents (ICD)/Interface Design Documents (IDD) 108

1) UEWR to GFC IDD - D742-10109-2 Revision F 30 Jun 10 110

2) UEWR to SSF "Draft" ICD developed by Missile Defense System Engineering and Test 111

(MDSET) Government Team - 14 Oct 10 (replaces UEWR to ET IDD) 112

Item #2 above represents an in process update to UEWR to ET IDD - D742-10104-2 113

Revision B - PIRN 01 (update) - Dated 30 May 07, IRN 02 15May 08, IRN 03 19 May 09, 114

IRN 04 20 Apr 09 115

3) EWR to ITW/AA and Space Surveillance Network (SSN) Interface Control Document (ICD) 117

Document No. H38164, Rev G 15 Sep 10 118

4) UEWR Internal Network Processing Equipment (PE) Networking ICD Document No. G760210 119

Rev G 15 Sep 10 120

5) UEWR Stand-Alone Trainer (UST) ICD Document No. H329070 Rev. C 8Nov04 121

6) UEWR External Communication Interfaces ICD H337211 Rev. A 15 Jul09 122

7) VCN3/VCN4 Technical Data Package 123

3.0 Requirements 125

This Statement of Work (SOW) describes the effort required by the contractor for the Upgraded Early 126

Warning Radar (UEWR) Program. The contractor is responsible for the design, development, 127 manufacturing, delivery, installation and test of the operational Simulator Tester (S-T) and Signal 128

Processor/Data Processor (SP/DP) hardware/software herein referred to as the H/W S/W suite at Beale 129

AFB, CA, and the Clear Upgrade, with an option for the Cape Cod upgrade, while maintaining the 130 operational mission at all affected locations. The contractor shall leverage the latest UEWR operational 131

GEIA HDBK-0007 Logistics Product Data Jun 07

JSP 440 The Defence Manual of Security

Issue 3.8 Ministry of Defence

Jul 09

JSP 480 Defence Co-coordinating

Installation Design Authority

Manual of Regulations for

Installation of Communication and Information Systems

Jan 11 baseline which reflects the PIDS (Revision G). The contractor shall rehost the signal and data processors, 132 install and test that design at Beale, and verify that design through operational acceptance. The contractor 133 shall coordinate with and share information, subject to the restrictions in and of the established 134

Proprietary Information Agreements, with the UEWR and support contractors for the parallel Clear AFS 135 activities. This effort will culminate in operational acceptance of Beale, followed by Clear in FY16 and if 136 the option is exercised, at Cape Cod in FY17. The contractor shall complete final site configuration, 137 calibration (as needed), and restoration at each site following operational acceptance. 138

3.1 Program Management 140

The contractor shall provide the executive level leadership to implement and control the program 141 activities throughout the life of the program. These duties shall include, but are not limited to: serving as 142 the focal point to the UEWR Program Office; conducting and integrating all aspects of the program such 143 as contract schedule, cost, risk management and technical status to ensure successful design reviews and 144 execution. The contractor shall perform the necessary administration required to support the contract and 145 provide coordination for the development of presentations, the arrangement and coordination of Program 146

Management Reviews (PMR), and other reviews and meetings. 147

3.1.1 Integrated Product and Process Development (IPPD) 149

The contractor shall establish and implement an IPPD process in all technical and functional disciplines to 150 assist the Government Program Manager in effective communication and program execution. The IPPD 151 process shall allow for coordination/interaction with the Government and other designated contractors on: 152 schedule reconciliations, technical interchanges, comprehensive program management meetings, 153 integrated product team meetings, and related tasks necessary to deliver the requisite performance within 154 cost and schedule constraints. The contractor shall provide monthly program status reports to the 155

Government (Automated Data Product (ADP) 4). The Government shall be notified of all emergent 156 issues as they arise. 157

The contractor shall provide all administrative effort associated with issuing and monitoring sub-tier 159 contract efforts and products including cost and schedule requirements and reporting. The contractor 160 shall ensure flow down of applicable Government technical and administrative requirements to all sub-161 contractors. The contractor shall maintain and provide current status of sub-contracts including scope of 162 work, cost, schedule, and status of products and data items. 163

The contractor shall plan and implement Working Groups with approval provided by the Government. 165

The contractor shall ensure de-confliction and synergy where possible with subordinate working groups 166 to support the Joint Program Management Plan (JPMP). The subordinate working groups at a minimum 167 are: 168

Integrated Logistics Support Management Team (ILSMT) 169

Training Planning Team (TPT) 170

Test Planning Working Group (TPWG) 171

Joint Schedule Working Group (JSWG) 172

Security Working Group (SWG) 173

Communications Working Group (CWG) 174

Site Activation Task Force/Facility Working Group (SATF/FWG) 175

Interface Control Working Group (ICWG) 176

Engineering Working Group (EWG) 177

3.1.1.1 Technical Interchange Meeting (TIM) 179

The Government will schedule, or the contractor shall schedule with Government concurrence, TIMs, as 180 required. The purpose of these TIMs is to allow for technical interchange between the various UEWR 181 stakeholders (e.g., other Government contractors) and/or Government subject matter experts. 182

3.1.2 Program Management Reviews 184

The contractor shall conduct an initial Program Management Review (PMR) within 60 calendar days of 185 contract award and at least quarterly thereafter. External stakeholders (e.g., other Government prime 186 contractors) may be invited as jointly approved by the Government and the UEWR Contractor. Each 187

PMR shall address at a minimum: technical, financial, schedule, risk, action items, technical performance 188 measures, and quality assurance findings. To the extent feasible, the contractor shall schedule PMRs 189 concurrent with other meetings or TIMs in order to reduce costs. PMRs shall be held at the contractor’s 190 facility or at a location designated by the Government. The contractor shall coordinate an agenda with the 191

Government at least 10 working days in advance of each PMR. The PMR read ahead material shall be 192 available at least two working days prior to the PMR. The contractor shall plan, prepare for, conduct, and 193 provide minutes of all program and technical reviews within 10 working days of completion of these 194 reviews (ADP 4). 195

3.1.3 Business Operations 197

The contractor shall establish, maintain, and use an integrated performance management system in the 198 performance of this contract. A validated Earned Value Management System (EVMS) shall be a part of 199 this integrated system that is compliant with the EVMS guidelines contained in ANSI/EIA-748. The 200

EVMS shall use the Contract Work Breakdown Structure (CWBS) IAW MIL-STD 881C and CWBS 201

Dictionary (Contract Data Requirements List (CDRL) A003). The contractor shall develop, maintain and 202 deliver: 203

The Contract Funds Status Report (CFSR) (CDRL A004) 204

Contract Performance Report (CPR) (CDRL A005) 205

Cost Data Summary Report (CDSR - DD Form 1921) (CDRL A001) 206

Functional Cost-Hour Report (FCHR)/Progress Curve Report (CDRL A002) 207

The EVMS shall be linked to, and supported by the contractor’s management processes and systems to 209 include the Integrated Master Schedule (IMS), change management, material management, procurement, 210 cost estimating, and accounting. The correlation and integration of these systems and processes shall 211 provide for early indication of cost and schedule problems, and their relation to technical achievement. 212

3.1.3.1 Integrated Baseline Reviews (IBR) 216

The contractor shall engage jointly with the Government’s Program Manager in IBRs to evaluate the risks 217 inherent in the contract’s planned performance measurement baseline IAW MDA 5004.1H and BMDS 218

5004.01. The initial IBR shall occur not later than four months after contract award. Subsequent IBRs 219 shall occur after each major change to the baseline, and at Government direction. The totality of the 220 baseline may be reviewed and evaluated annually by the Government. The Contractor shall use the latest 221 approved performance measurement baseline (to include the entire contract scope of work), be consistent 222 with contract schedule requirements, and assign adequate resources. IBRs shall be conducted on 223 subcontracts that meet or exceed the EVMS application threshold. The UEWR Contractor shall lead the 224 subcontractor IBRs, with active participation by the Government. 225

3.1.3.2 Integrated Master Schedule (IMS) 227

The Contractor shall develop, maintain, and manage the execution of the program using an Integrated 228

Master Schedule (IMS) and Integrated Master Plan (CDRL A006) as part of the day –to –day execution 229 tools. The Integrated Master Plan (IMP) shall incorporate the events, criteria and tasks the contractor will 230 use to manage the execution of the program and shall be mapped to the SOW. The IMS shall contain the 231 networked, detailed tasks necessary to manage program execution. 232

The IMP and IMS shall be traceable to the Contract Work Breakdown Structure (CWBS), Earned Value 234

Management System (EVMS) and the Statement of Work (SOW). The IMS shall be used to evaluate 235 progress toward meeting program objectives, and to integrate the program schedule activities. The IMS 236 shall contain program events, accomplishments, criteria, detail tasks, and Section F-02 milestone events, 237 from contract award to contract completion. 238

3.1.3.3 Joint Master Schedule (JMS) 239

The contractor shall use the Government prepared JMS to support the continual maintenance of the JMS 240

(ADP 41) as a Government owned, contractor-maintained product. Configuration Control will be by the 241

Government via the JSWG. The JMS includes dates, durations, and dependencies from the Government 242 and other prime contractors, as well as, dates, dependencies, and durations for key tasks from the 243 contractor IMS. The contractor-maintained JMS shall comprise necessary links and dependencies to 244 include at a minimum: USACE site Construction contractor, all C2BMC GFCC Government agencies 245 and contractors, the SSF contractor (and follow-on contractor), the USAF radar sustainment contractor, 246

AFSPC contractors, and the BMDS test effort. The contractor shall establish a process for obtaining the 247 updates from the Government and other impacting contractors. The contractor shall update the JMS 248 monthly. The JMS aids the Government, UEWR contractor, and other contractors, in coordinating tasks 249 on the SP/DP Rehost and the Clear upgrade. The contractor shall provide stringent maintenance and 250 updating of the JMS and IMS tools to identify and resolve conflicting activities for the duration of the 251

Clear Upgrade. Should conflicts occur that cannot be resolved by the contractor, the contractor shall 252 notify the Government for resolution. 253

3.1.4 Security 257

The contractor shall ensure coverage, by a Facility Security Officer (FSO) and an Information Assurance 258

Officer (IAO), at the contractor and radar sites when needed. The contractor shall prepare and implement 259 a Site Security Management Plan (SSMP) (CDRL A012). The contractor shall work with the site 260 commander on coordination of facility access required by the contractor and its sub-contractors. The 261 contractor shall provide access to all existing contract related data and documentation. 262

3.1.4.1 Information Security 263

The contractor shall support execution of the MDA Information Security Program. The contractor shall 264 execute tasks listed below and as otherwise defined in this SOW. 265

The Contractor shall ensure that cleared subcontractor facilities shall schedule and conduct 267 annual Information Security Program Reviews (IPRs) and self-inspections. Serious 268 deficiencies at the subcontractor location shall be reported to the Contractor. When a security 269 risk has been identified at an uncleared location the Contractor will conduct a security 270 program review or SAV with the concurrence of the COR. Develop IPR reports and conduct 271 briefings with programs to identify and review goals, processes, and findings. 272

Assist with implementation of the Security Incident and Preliminary Inquiry (PI) process 274

IAW DOD and Agency policy. Analyze security incidents to verify incident descriptions and 275 address cause, impact, mitigation, and recommended courses of action. Coordinate, discuss, 276 and resolve discrepancies. Submit reports to MDA Security. 277

3.1.4.2 Program Protection 280

The contractor shall support the execution of the MDA Program Protection activities. The contractor shall 281 execute tasks listed below: 282

Plan and implement an Acquisition System Protection program encompassing program 284 security, program protection, and systems security engineering for this contract based upon 285 the requisite threat documents provided by MDA. 286

The Contractor and MDA shall conduct a joint analysis based upon relative threat 288 information to determine the protection required for the Critical Program Information (CPI) 289 and develop a plan to implement the required protection in accordance with the Government 290 directed Program Protection Plan (PPP). Assess, develop, and draft, update, maintain, and 291 implement a Program Protection Management Plan (PPMP) A007 and Critical Program 292

Information (PPP/CPI) and training guidelines for the protection of CPI for the BMDS. 293

The Contractor shall generate, update, maintain and implement a Program Protection 295

Management Plan (PPMP) (CDRL A007) which will be a stand-alone document for this 296 contract. The PPMP shall include compliance implementation planning in accordance with 297 the Sensors Sustainment PPP, DODI 5200.39, DOD5200.1-M, USSTRATCOM Directive 298

538-2, DOD 5200.1-R, DTM-09-016, DTM-08-027 change 1, NDAA 932, DODD 8500.1, 299

DOD 5200.8-R, CJCSI 6510.01F, CJCSI 6511.01, NSTISSAM Tempest 2/95, NSTISSP No. 300

11, and MDA 5200.08. The Contractor shall provide inputs to and support Government 301 security analyses, including system security analyses, the System Vulnerability Analysis 302

(SVA), Operations Security (OPSEC) Plan, System Security Engineering (SSE) requirements 303 analysis, and Information Assurance (IA)/Computer Network Defense (IA/CND) technical 304 assessments. The Contractor shall support government Protection Assessment Reviews 305

(PAR) and audits/inspections for compliance monitoring of CPI protection initiatives, and 306

Security and Program Protection Working Groups. 307

Develop PP Training Plans and conduct Contractor training of how to assess criticality of 309 technologies and mitigate CPI risks from known or postulated threats IAW government 310 issued PPPs. 311

Conduct periodic self-assessments to evaluate Program adherence to PPMP and processes. 313

Develop security policy and procedures. Provide government updates on implementing the 314

BMDS System Security Engineering (SSE) requirements IAW the BMDS and UEWR system 315 specifications. 316

Develop System Security Engineering (SSE) requirements, System Connection Authorization 318

Requirements documents, and Security Accreditation Agreements documents. 319

The Contractor shall comply with security requirements in accordance with NSA Guide for 320

Addressing Malicious Code Risk throughout the development cycle. 321

3.1.4.3 Supply Chain Risk Management 322

The contractor shall demonstrate that the contractor has visibility into its supply chain for 323 critical components, understands the risks to that supply chain, and has implemented or plans 324 to implement risk mitigations to counter those risks in the PPMP in accordance with DOD 325

4140.-R and DTM-08-27. 326

The provisions of this SOW shall be included in the solicitations and subcontracts for all 327 suppliers, suitably modified to identify the security risks suppliers must address to ensure the 328 protection of CPI within the supply chain. 329

3.1.5 Small Business 330

The contractor shall provide Small Business utilization and participation data (CDRL A038). 331

3.2 Systems Engineering 333

The contractor's System Engineering and Software Development efforts on this program shall be 334 conducted IAW the the contractor’s Capability Maturity Model Integration (CMMI) processes. The 335 contractor’s processes shall be no less than maturity Level Three.. The contractor shall also maintain or 336 improve their CMMI certification maturity level throughout the execution of the contract. The contractor 337 shall implement robust systems engineering processes (as documented in a Contractor-developed System 338

Engineering Management Plan (SEMP) (ADP 3)) to develop, fabricate, integrate, test, evaluate, 339 document, deliver, and support the SP/DP rehost and the Clear upgrade as described in this SOW. All 340 system engineering processes shall be flowed to the subcontractors. System Engineering overall technical 341 management shall include but not be limited to the conduct of systems analyses, engineering trade 342 studies, preparation and implementation of the SEMP. This design shall be based on the latest 343 operational baseline, be backward compatible to Beale, Fylingdales and Thule and be forward compatible 344 for Cape Cod inclusion. All changes, deviations and waiver requests, to the PIDS Rev G baseline shall be 345 presented to the Government for review through the UEWR System Requirements/Design Review 346

(SRDR) (CDRL A027), Preliminary Design Review (PDR) (CDRL A028), and Critical Design Review 347

(CDR) (CDRL A029). The CDR shall be conducted in accordance with the CDR Checklist (included in 348 contract section J) using MIL-STD-1521B as a guide. All component designs being incorporated into 349

Beale (SP/DP suite only), Clear, and Cape Cod shall be compliant with JSP-440/480 so that they can be 350 deployable to all other UEWR sites (Beale, Fylingdales, and Thule). Redesign due to parts obsolescence, 351 shall be form, fit, function replacements to the maximum extent practical. If replacement is not form, fit, 352 function replaceable the contractor shall identify this at the earliest design review practical for 353

Government consideration, decision, and direction. The contractor shall prepare and deliver Scientific 354 and Technical Reports (CDRL A019), as directed by the Government. The contractor shall maintain a 355

Technical Performance Measurement (TPM) (ADP 46) baseline. TPMs shall be identified at the SRDR 356 and refined, as necessary, at the PDR and CDR. Expected system performance compared to the TPMs 357 shall be briefed at all PMRs. 358

3.2.1 Specialty Engineering 359

The contractor shall prepare a Specialty Engineering Management Plan (SpEMP) (ADP 42). The 360 contractor shall implement a Specialty Engineering Program for this contract. At a minimum; this shall 361 include updates to the following plans and documentation: 362

RAM-T Program Plan (ADP 23) IAW MAP and XBR/UEWR Product Assurance Plan, Rev B 363

Reliability Design Criteria (ADP 30) 364

Maintainability Design Criteria (ADP 31) 365

Human Systems Integration Program Plan (ADP 28) IAW MIL-STD-1472F 366

Electromagnetic Interference (EMI)/Electromagnetic Compatibility (EMC) Control Plan (ADP 367

32) 368

The contractor shall establish and implement a UEWR Failure Review Board (FRB) process that provides 370 data packages identifying all failures, the failure description, root cause, and corrective action status 371 including related change request identifiers, age of the root cause/corrective action activity, and current 372 open actions on the Government Integrated Data Environment (IDE), as well as, minutes of the FRB. The 373 contractor shall submit quarterly Failure Reporting, Analysis and Corrective Action System (FRACAS) 374 data summaries (ADP 38). The contractor shall submit Maintainability Math Models, Allocations and 375

Predictions data (ADP 39) to address contract-unique design changes and associated impact on the overall 376

UEWR RAM assessment. Similar data shall be provided for Reliability Math Models, Allocations and 377

Predictions (ADP 40). This RAM data (ADP 39 & 40) shall include an initial data set to address design 378 changes and subsequent annual data sets to reflect operational performance. Using the GMD Program 379

Plan (GMD 286) as a guide, the contractor shall generate, maintain and execute a Failure Modes, Effects 380 and Criticality Analysis (FMECA) (CDRL A024) and maintain the Critical Items List (CIL) (CDRL 381

A024). 382

The Contractor shall support: test planning, development of test plan, developing or modifying existing 383

UEWR scripts in support of the test plan, performance of the measurements, schedule and coordination, 384 and data analysis in support of DD1494 Stage 4 testing, test report analysis and submittal of the DD1494 385 application for the Clear radar site. 386

3.2.2 MDA Sensors System Requirements Allocation/Management 387

The contractor will be provided the latest UEWR Dynamic Object Oriented Requirements System 388

(DOORS) database. The contractor shall maintain at least the 8.3 version of the DOORS to document 389 requirements traceability to upper level specifications (e.g. BMD SS) and allocation to lower-level 390 specification documentation in the database. The contractor shall provide for Government access to the 391 database (this may require coordination with the radar sustainment organization/contractor). The 392 contractor shall update the database through the VCN synchronization effort. The DOORS database shall 393 be delivered/ merged with the sustainment database. All future DOORS updates shall be provided to the 394

Government for inclusion by the sustainment contractor. The contractor shall generate Specification 395

Change Notices (SCN) (CDRL A013) for any systems design and requirements updates, as…