EASR_Att_J-01_SOW.pdf

Attachment J-01 EASR SOW 2015-07-31 1646

SOURCE SELECTION INFORMATION – SEE FAR 2.101 AND 3.104

Attachment J-01 1

STATEMENT OF WORK (SOW) 6

for the 8

Enterprise Air Surveillance Radar (EASR) 10

Engineering and Manufacturing Development and 11

Production 12

31 July 2015 16

SOURCE SELECTION INFORMATION – SEE FAR 2.101 AND 3.104 i

TABLE OF CONTENTS 21

1 SCOPE ............................................................................................................... 1 23

1.1 BACKGROUND ..................................................................................................... 1 24

2 APPLICABLE DOCUMENTS ....................................................................... 1 25

2.1 MANDATORY DOCUMENTS ................................................................................ 1 26

2.2 GUIDANCE PUBLICATIONS ................................................................................. 4 27

2.3 PRECEDENCE ...................................................................................................... 7 28

3 REQUIREMENTS ........................................................................................... 7 29

3.1 ENGINEERING AND MANUFACTURING DEVELOPMENT (CLIN 0001) .............. 7 30

3.1.1 EMD Overview ............................................................................................... 8 31

3.1.2 Systems Engineering ....................................................................................... 8 32

3.1.3 EMD Production ........................................................................................... 30 33

3.1.4 Integration and Test ...................................................................................... 32 34

3.1.5 Specialty Engineering ................................................................................... 39 35

3.1.6 Configuration Audit ...................................................................................... 51 36

3.1.7 Program Management ................................................................................... 51 37

3.2 OPTION-PRODUCTION LONG LEAD MATERIAL (FIRST UNIT) (CLIN 0303 AND 38

0304) ................................................................................................................. 58 39

3.3 PRODUCTION (CLINS 0303 [UPON SUBSUMPTION OF 0401(0401AA & 40

0401AB-0402 (0402AA, 0402AB, 0402AC, & 0402AD)] / 0304 [UPON 41

SUBSUMPTION OF 0403-0404 (0404AA & 0404AB)] / 0501 / 0502 (0502AA & 42

0502AB) / 0503/0504 (0504AA & 0504AB) / 0601 / 0602 (0602AA & 0602AB) 43

/ 0701 / 0702 (0702AA & 0702AB) / 0703 / 0704 (0704AA & 0704AB) / 0801 / 44

0802 (0802AA & 0802AB)) ............................................................................. 58 45

3.3.1 Production General Requirements ................................................................ 58 46

3.3.2 Option - Production Units (CLINs 0401 (0401AA & 0401AB) or 0402 47

(0402AA, 0402AB, 0402AC, & 0402AD)) .............................................................. 67 48

3.3.3 Option- Non-Recurring Engineering Effort For Transition to Production, 49

First Article Testing, and Physical Configuration Audit (CLIN 0407-0408) ........... 67 50

3.3.4 Options-Production Units (0501/0502 (0502AA & 0502AB) / 0503 / 0504 51

(0504AA & 0504AB) / 0601 / 0602 (0602AA & 0602AB) / 0701 / 0702 (0702AA & 52

0702AB) / 0703 / 0704 (0704AA & 0704AB) / 0801 / 0802 (0802AA & 0802AB))53

69 54

1 SCOPE 57

The objective of this Statement of Work (SOW) is to define the work necessary to design 58 the Enterprise Air Surveillance Radar (EASR) and to build, integrate and test an EASR 59

Engineering Development Model (EDM). This SOW will include a base contract 60 beginning with design work leading to Preliminary Design Review and culminating at 61 system acceptance of the EDM at the end of testing at the Surface Combat System Center 62

(SCSC), Wallops Island, VA (hereafter referred to as SCSC). In addition, Options will 63 be included for Production. 64

EASR will serve as the primary sensor for ship self-defense, situational awareness and air 65 traffic control in a dense Electromagnetic Interference (EMI) and clutter environment for 66 carrier and amphibious ship classes. 67

1.1 Background 69

EASR will be one sensor in a new sensor suite that is designed to meet the performance 70 needs contained in the Battlespace Awareness Initial Capabilities Document dated 13 71

August 2014. EASR is to be fielded in two variants. Variant 1 is a single-face array 72 rotating design to provide AN/SPS-48 and AN/SPS-49 capabilities for installation on 73

Amphibious Warfare Ships such as new construction America Class Amphibious Assault 74

Ships (LHA-8+), LPD, LX(R), and any other designated ship class. Variant 2 is a three-75 face fixed array design slated for Aircraft Carriers and any other designated ship class. 76

2 APPLICABLE DOCUMENTS 77

2.1 Mandatory Documents 78

The following documents form a basis for the work to be performed under this SOW: 79

a. Enterprise Air Surveillance Radar (EASR) System Requirements 80

Document (SRD) with Appendices, included as Attachment J-02. 81

b. Department of Defense Security Classification Specification (DD-254), 82 and Enterprise Air Surveillance Radar (EASR) Program Security 83

Classification Guide, included as Attachment J-04. 84

c. Enterprise Air Surveillance Radar (EASR) Program Work Breakdown 85

Structure (WBS) and Data Dictionary, included as Attachment J-06 86

d. Department of Defense Instruction (DODI) 8500.01, Cybersecurity, dated 87

14 March 2014 88

e. Enterprise Air Surveillance Radar (EASR) Cybersecurity Strategy, 89

Version 1.0, included as Attachment J-26 90

f. GAO-04-678, Defense Acquisitions: Knowledge of Software Suppliers 91

Needed to Manage Risks, dated 25 May 2004 92

g. ISO/IEC 15408, Common Criteria v3.1. Release 4, dated September 2012 93

h. Enterprise Air Surveillance Radar (EASR) Program Protection Plan (PPP), 94

Version 1.0, included as Attachment J-22 95

i. MIL-STD-3022-1 – DoD Standard Practice Documentation of VV&A for 96

Models and Simulations, dated 05 April 2012 97

j. MIL-STD-31000A – Technical Data Packages, dated 26 February 2013 98

k. Enterprise Air Surveillance Radar (EASR) Programmatic, Environmental, 99

Safety and Health Evaluation (PESHE) Plan, Version 1.0, included as 100

Attachment J-28 101

l. MIL-STD-882E – System Safety, dated 11 May 2012 102

m. NAVSEA S9310-AQ-SAF-010, Technical Manual for Batteries, Navy 103

Lithium Safety Program and Procedures, dated 19 Aug 2004 104

n. NAVSEAINST 9310.1B, Naval Lithium Battery Safety Program, dated 13 105

Jun 1991 106

o. MIL-HDBK-189C, Reliability Growth Management, dated 14 June 2011 107

p. GEIA-STD-0009 - Reliability Program Standard For Systems Design, 108

Development And Manufacturing, dated 13 Nov 2008 109

q. ASQC Q9001-2008, Quality Systems-Model for Quality Assurance In-110

Depth, Development, Production, Installation, and Servicing 111

r. Enterprise Air Surveillance Radar (EASR) Life Cycle Sustainment Plan 112

(LCSP), Version 1.0, included as Attachment J-24 113

s. Cost and Software Data Reporting (CSDR) Plan, included as Attachment 114

J-15 115

t. Enterprise Air Surveillance Radar (EASR) Systems Engineering Plan 116

(SEP), Version 1.0, included as Attachment J-23 117

u. PEO IWS / Naval Sea Systems Command Research & System 118

Engineering Warfare System Engineering and Human Systems Integration 119

Directorate Technical Review Manual (TRM), Version 2, dated 18 120

December 2009 121

v. CVN-79/80 Topside Emitters List 122

w. LHA-8 Topside Emitters List 123

x. OPNAVINST 5100.24B, Navy System Safety Program Policy, dated 06 124

Feb 2007 125

y. NAVSEAINST 5100.12B, Requirements For Naval Sea Systems 126

Command System Safety Program For Ships, Shipborne Systems And 127

Equipment, dated 03 Aug 2011 128

z. Executive Order (EO) 12856, 03 Aug 1993 129

aa. Executive Order (EO) 13148, 21 April 2000 130

bb. National Aerospace Standard (NAS) 411, dated July 1993 131

cc. SAE GEIA-STD-0007B, Logistics Product Data, dated May 01, 2013 132

dd. MIL-STD-1472G, Human Engineering, dated 11 January 2012 133

ee. ASTM F1166-07, Marine Systems, Equipment and Facilities, Human 134

Engineering Design for, dated 15 August 1994 135

ff. MIL-STD-130N, Identification Marking of U.S. Military Property, dated 136

17 December 2007 137

gg. ANSI/EIA-748, Earned Value Management Systems, dated 17 August 138

1999 139

hh. DoD Manual 5000.04-M-1, Cost and Software Data Reporting (CSDR) 140

Manual, 4 November 2011 141

ii. MIL-STD-881C – Work Breakdown Structures for Defense Materiel 142

Items, dated 03 October 2011 143

jj. V-95 Radar Facility, Surface Combat Systems Center, Wallops Island, 144

VA, 27 May 2015, included as Attachment J-27 145

kk. NFPA70E, Standard for Electrical Safety in the Workplace, 2012 Edition, 146

31 August 2011. 147

ll. Enterprise Air Surveillance Radar (EASR) Anti-Tamper (AT) Process, 148 included as Attachment J-29 149

mm. OPNAVINST 1500.76C, Naval Training Systems Requirements, 150

Acquisition, and Management, 14 August 2013 151

nn. MIL-PRF-29612B, Training Data Products 31 August 2001 152

oo. DoDI 8510.01, Risk Management Framework (RMF) for DoD 153

Information Technology (IT), 12 March 2014 154

pp. National Institute of Standards and Technology (NIST) Special 155

Publication 800-37 (Feb 2010, as amended) 156

qq. Subchapter III of Chapter 35 of Title 44, U.S. Code (aka "Federal 157

Information Security Management Act (FISMA) of 2002") 158

rr. Committee on National Security Systems Instruction 1253, 15 March 159

2012, as amended 160

ss. National Institute of Standards and Technology (NIST) Special 161

Publication 800-53, February 2009 162

tt. National Institute of Standards and Technology (NIST) Special 163

Publication 800-18, Revision 1, February 2006 164

uu. Enterprise Air Surveillance Radar (EASR) Technical Performance 165

Measures (TPMs), included as Attachment J-21 166

vv. IEEE Std. 12207:2008, Systems and software engineering, Software life 167 cycle processes 168

ww. ISO/IEC/IEEE 15289:2011, Systems and Software Engineering, Content 169 of life-cycle information products (documentation) 170

xx. ASD-S1000D, Version 4.1, International Specification for Technical 171

Publications Utilising a Common Source Data Base 172

yy. MIL-STD-3034A, Reliability-Centered Maintenance (RCM) Process, 173 dated 29 April 2014 174

2.2 Guidance Publications 175

The following publications are available as guidance: 176

zz. ISO 10303/AP 233 – Standard for the Exchange of Product Model 177

Data/Application Protocol 233 (Systems Engineering Data 178

Representation) 179 aaa. DoD Modeling and Simulation for the Acquisition Workforce, Version 180

1.0.1, dated October 2008 181 bbb. SAE GEIA-HB-0007B, Logistics Product Data Handbook 182 ccc. PEOIWSINST 5000.8, PEO IWS 2.0 Risk Management Policy, 13 183

January 2014 184 ddd. Naval SYSCOM Risk Management Policy, NAVSEAINST 5000.8, dated 185

21 Jul 2008 186 eee. Risk Management Guide for DoD Acquisition, 7th Edition (Interim 187

Release), dated December 2014 188 fff. DoDI 5200.39 with Change 1, Security, Intelligence, and 189

Counterintelligence Support to Acquisition Program Protection, 28 190

December 2010 191 ggg. NAVSEAINST 9400.2, Implementation of Naval Sea Systems Command 192

(NAVSEA) Afloat IA Governance and Guidance, dated 18 Aug 2010 193 hhh. Department of Defense Anti-Tamper (AT) Guidelines, Version 2.0, 01 194

April 2010, included as Attachment J-30 195

iii. DoD Manufacturing Readiness Level (MRL) Deskbook,V2.2.1 dated 196

October 2012 197 jjj. MIL-S-901D – Shock Tests, H.I. (High-Impact) Shipboard Machinery, 198

Equipment, and Systems, Requirements for, dated 17 Mar 1989 199 kkk. MIL-HDBK-2155, Failure Reporting, Analysis and Corrective Action 200

Taken, 11 Dec 1995 201 lll. DoD Joint Software Systems Safety Engineering Handbook, dated 27 Aug 202

2010 203 mmm. NAVSEAINST 8020.6E - Department of the Navy Weapon Systems 204

Explosive Safety Review Board, dated 11 March 2008 205 nnn. NAVSEA SW020-AH-SAF-010, Weapons System Safety Guidelines 206

Handbook, 01 Feb 2006 207 ooo. DoDI 5000.02, Operation of the Defense Acquisition System, dated 07 Jan 208

2015 209 ppp. MIL-HDBK-217F-2 – Reliability Prediction of Electronic Equipment, 210 dated 28 Feb 1995 211 qqq. MIL-HDBK-472-1 – Maintainability Prediction, dated 12 Jan 1984 212 rrr. MIL-HDBK-61A, Configuration Management Guidance, dated 07 Feb 213

2001 214 sss. ANSI/EIA 649B, National Consensus Standard for Configuration 215

Management, dated 01 Apr 2011 216 ttt. PEO IWS 2.0 Above Water Sensors Configuration Management 217

Plan/Procedures 218 uuu. DoD Product Support Business Case Analysis (BCA) Guidebook, dated 219

April 2011 220

vvv. NAVSEA A Program Manager’s Guide to the Application of Performance 221

Based Logistics (PBL), Revision A, dated 08 October 2008 222 www. DoD Corrosion Prevention and Control Planning Guidebook for Military 223

Systems and Equipment, Spiral 4, 04 February 2014 224

xxx. DoD Diminishing Manufacturing Sources and Material Shortages 225

(DMSMS) Guidebook: A Guidebook of Best Practices for Implementing a 226

Robust DMSMS Management Program (SD-22), February 2015 227 yyy. Enterprise Air Surveillance Radar (EASR) Item Unique Identification 228

Implementation (IUID) Plan, Version 1.0, included as Attachment J-25 229 zzz. DoD Suppliers’ Passive RFID Information Guide, Version 15, dated 230

January 2010 231 aaaa. DoDI S-5230.28 , Low Observable (LO) and Counter Low Observable. 232

(CLO) Programs (U), 26 May 2005 233 bbbb. North Atlantic Treaty Organization (NATO) Allied Ordnance Publication 234

52 (AOP-52), Guidance on Software Safety Design and Assessment of 235

Munition-Related Computing Systems, November 2008 236 cccc. DELETED 237 dddd. DoDI 4140.67, DoD Counterfeit Prevention Policy, 26 April 2013 238 eeee. DODI 5200.44, Protection of Mission Critical Functions to Achieve 239

Trusted Systems and Networks, 05 November 2012 240 ffff. SECNAVINST 4855.3C, Product Data Reporting and Evaluation 241

Program, 27 June 2014 242 gggg. Deputy Assistant Secretary of Defense, Systems Engineering PPP Outline 243 and Guidance, Version 1.0, July 2011 244 hhhh. SECNAVINST 5000.2E, Department of the Navy Implementation and 245

Operation of the Defense Acquisition System and the Joint Capabilities 246

Integration and Development System, dated 01 September 2011 247

iiii. Weapons Specification (WS) 23302G, Interface Design Description for 248 the Ship Self-Defense System MK 2 MOD () (SSDS MK 2 MOD ()) / 249

Cooperative Engagement Capability (CEC) Cooperative Engagement 250

Processor (CEP), 03 October 2012, Attachment J-31C 251 jjjj. Weapon Specification (WS) 35556, Dual Band Radar Integration 252

(DBRIN) Software Requirements Specification (SRS), 27 August 2014, 253

Attachment J-31A 254 kkkk. Weapon Specification (WS) 35569, Interface Description for the Dual 255

Band Radar Integration Software Configuration Item (DBRIN SCI) of the 256

Ship Self Defense System MK2 MOD () (SSDS MK 2 MOD 257

())/Cooperative Engagement Capability (CEC) Cooperative Engagement 258

Processor (CEP), 08 February 2012, Attachment J-31B 259 llll. MIL-HDBK-470A, Designing and Developing Maintainable Products and 260

Systems, Volume I, 04 August 1997 261 mmmm. MIL-HDBK-1390, Level of Repair Analysis, 29 January 2015 262 nnnn. Navy Education and Training Manual 138 (NAVEDTRA 138), Naval 263

Education and Traing Command-Front End Analysis Management 264

Manual, June 2012 265 oooo. MIL-HDBK 29612/1A, Guidance for Acquisition of Training Data 266

Products and Services (Part 1 of 5 Parts), 31 August 2001 267 pppp. MIL-HDBK 29612/2A, Instructional Systems Development/Systems 268

Approach to Training and Education (Part 2 of 5 Parts), 31 August 2001 269 qqqq. MIL-HDBK 29612/3A, Development of Interactive Multimedia 270

Instruction (IMI) Part 3 of 5 Parts), 31 August 2001 271 rrrr. MIL-HDBK 29612/4A, Glossary for Training (Part 4 of 5 Parts), 31 272

August 2001 273 ssss. MIL-HDBK 29612/5A, Advanced Distributed Learning (ADL) Products 274 and Systems (Part 5 of 5 Parts), 31 August 2001 275 tttt. MIL-HDBK-729, Corrosion and Corrosion Prevention Metals, 21 November 276

1983 277

2.3 Precedence 278

In the event of a conflict between the documents listed in Section 2.1, Mandatory 279

Documents, and Section 2.2, Guidance Publications, the documents in Section 2.1 shall 280 take precedence. 281

In the event of a conflict between the documents listed in Section 2.2, the Contractor 282 shall contact the Government and the Government will adjudicate on a case-by-case 283 basis. 284

3 REQUIREMENTS 285

3.1 Engineering and Manufacturing Development (CLIN 0001) 286

The exit criteria for Engineering and Manufacturing Development (EMD) (CLIN 0001) 287 are as follows: 288

a. The Contractor shall finalize design of EASR that meet EASR A-Specification 289

(CDRL A013) and EASR External (Logical) Interface Requirements 290

Specifications (IRS) (CDRL A021); 291

b. The Contractor shall build, integrate, and deliver a Variant 1, single face array 292 with rotating positioner, production representative EASR Engineering 293

Development Model (EDM), EASR Interface Simulator, Emulator, two (2) 294

System Displays and Control (SDCs) with computing hardware, Maintenance 295

Manual with computing hardware, and EASR Land Based Test Site (LBTS) Spare 296

Parts; 297

c. The Contractor shall verify that the EASR EDM meets the EASR A-Specification 298

(CDRL A013) and EASR External (Logical) IRS (CDRL A021); 299

d. The Contractor shall conduct Test and Evaluation (T&E) of the EASR EDM at 300

SCSC in accordance with the approved Land Based Test Plan (CDRL A071) and 301 deliver the Government approved Land Based Testing Summary (LBTS)(CDRL 302

A075); 303

e. The Contractor shall correct all issues associated with Trouble Reports (TRs) 304

(CDRL A103) and implement all corresponding Revisions (CDRL A104) 305

(Subject to Government approval within Local Configuration Control Board 306

(LCCB)); 307

f. The Contractor shall successfully conduct a System Verification Review (SVR), 308

Functional Configuration Audit (FCA), and Production Readiness Review (PRR) 309 to support a Production decision. The Government will determine and document 310 closure of each review; 311

g. The Contractor shall provide a final Total Ownership Cost (TOC) Model (CDRL 312

A047) that reflects actual costs incurred during EMD phase and clearly shows the 313 relationship of EDM hardware costs to Production and future production costs; 314

h. The Contractor shall close or have a Government-approved closure plan for 315

Action Items (CDRL A003); and 316

i. The Contractor shall deliver all required Contract Data Requirements Lists 317

(CDRLs) (Exhibit A) and receive Government approval for approval CDRLs. 318

3.1.1 EMD Overview 319

The purpose of the EMD is to develop the system; complete full system integration; 320 develop an affordable and executable manufacturing process; ensure operational 321 supportability with particular attention to minimizing the logistics footprint; implement 322 human systems integration (HSI); design for producibility; ensure affordability; protect 323

Critical Program Information (CPI); and demonstrate system integration, interoperability, 324 safety, and utility. 325

3.1.2 Systems Engineering 326

3.1.2.1 System Engineering Technical Reviews (SETRs) 327

The Contractor shall host and participate in formal SETRs. The following is a list of the 328

SETRs to be conducted under CLIN 0001. These reviews shall be event driven and 329 predicated upon satisfying the SETR Entrance Criteria. 330

a. System Requirements Review (SRR)/System Functional Review (SFR), chaired 331 by the Government 332

b. Preliminary Design Review (PDR), chaired by the Government 333

c. Critical Design Review (CDR), chaired by the Government 334

d. Software Build Review (SBR) for each Software Build as defined in the Software 335

Development Plan (SDP) (CDRL A050), chaired by the Government 336

e. System/Subsystem Test Readiness Review (TRR), chaired by the Government 337

f. Land Based Test Site (LBTS) Test Readiness Review (TRR), chaired by the 338

Government 339

g. Transition CDR, chaired by the Government 340

h. System Verification Review (SVR)/Functional Configuration Audit (FCA), 341 chaired by the Government 342

i. Production Readiness Review (PRR), chaired by the Government 343

The Contractor shall recommend all reviews (scheduling, location, security requirements, 344

Agenda (CDRL A001) and content), subject to Government approval. The content and 345 the entrance and exit criteria of the reviews is defined in the Program Executive Office 346 for Integrated Warfare Systems (PEO IWS)/Naval Sea Systems Command Research & 347

System Engineering Warfare Systems (SEA 05) Technical Review Manual (TRM), 348

Version 2 and the EASR Systems Engineering Plan (SEP). Additionally, for each SETR 349 a Technical Review Action Plan (TRAP) will be provided as Government Furnished 350

Information (GFI) which describes the plan for a particular SETR and refines the 351 entrance and exit criteria. The Contractor shall place read ahead material and 352

Presentation Material (CDRL A002) on the Government Integrated Digital Environment 353

(IDE) preceding each review. The Contractor shall place final Presentation Materials on 354 the Government IDE following the reviews. The Contractor shall prepare Minutes 355

(CDRL A003) to include a database to capture and manage all Government and 356

Contractor Action Items from the reviews. The database shall reside on the Government 357

IDE. The Contractor shall update Action Item status, including closure plans, at least 358 weekly. 359

The Contractor shall conduct a series of design disclosure meetings prior to the PDRs and 360

CDRs. These meetings shall address the engineering material and documentation 361 sufficient to convey a detailed understanding to the Government technical team, and to 362 complete comment adjudication activities. The content of the design disclosures shall be 363 delivered in the Engineering Design Notebook (EDN) (CDRL A046) or design 364 descriptions. 365

In addition to the exit criteria defined in the Program Executive Office for Integrated 366

Warfare Systems (PEO IWS)/Naval Sea Systems Command Research & System 367

Engineering Warfare Systems (SEA 05) Technical Review Manual (TRM), the Contractor 368 shall provide high fidelity analysis of four (4) multi-mission scenario cases to demonsrate 369 the robustness of the system design. The multi-mission scenario cases will be provided 370 by the Government as GFI. These cases will be chosen by the Government to assess the 371 following: 372

a. Elevation Coverage, 373

b. Ancillary Functions, and 374

c. Mulit-Mission Resource Loading 375

3.1.2.2 Systems Engineering Management 376

This section describes the effort required to conduct Systems Engineering Management. 377

3.1.2.2.1 Systems Engineering Planning and Execution 378

The Contractor shall generate, maintain, and execute the Systems Engineering Master 379

Plan (SEMP) (CDRL A004) in accordance with the EASR Systems Engineering Plan 380

(SEP). The SEMP shall address the EASR program through Production. The SEMP 381 shall describe how a fully integrated engineering effort will be managed and conducted. 382

The plan shall provide details of the flow of requirements from the Government’s top 383 level requirements to the Contractor’s design documents. In addition, the Contractor 384 shall include Technical Performance Measures (TPMs) in the SEMP to be utilized for the 385 program. The Contractor shall include the TPMs in the EASR TPMs Document. 386

3.1.2.2.2 Integrated Product and Process Development 387

The Contractor shall form Integrated Product Teams (IPTs) and Working Groups (WGs) 388 to support an integrated product development process. The Contractor shall generate the 389 organizational structure and document it in the SEMP (CDRL A004). The Government 390 will assign representatives to participate in IPT/WG meetings as necessary. Government 391 participation will be coordinated through the Contracting Officer’s Representative 392

(COR). 393

The Contractor shall host IPT/WG meetings and Technical Interchange Meetings (TIMs), 394 and coordinate meetings with the Government. The Contractor shall coordinate and post 395

Meeting Agendas (CDRL A001) on the Government IDE prior to meetings. The 396

Contractor shall post Presentation Materials (CDRL A002) and Action Items (CDRL 397

A003) on the Government IDE. 398

The Contractor shall participate in the following Government / Industry Teams 399 established by the Government. 400

a. Radar/Ship Integration Working Group (RSIWG) is established to manage and 401 maintain the interfaces with the Ship Hull, Mechanical, and Electrical (HM&E) 402 systems. The RSIWG is anticipated to meet monthly in the Washington, DC area. 403

Personnel involved in this review process may be required to sign non-disclosure 404 agreements and firewall their efforts and participation from vendor/company 405 internal R&D efforts [as directed by the Procurement Contracting Officer (PCO) 406 and/or COR]. 407

b. Combat System/Air Traffic Control Integration Working Group (CS/ATCIWG) is 408 established to manage interfaces and ensure that the functional allocation and the 409 performance of EASR is a fully utilized Combat System (CS) (including weapon 410 system components, electronic warfare systems, missiles and track databases), 411

Cooperative Engagement Capability (CEC) and Air Traffic Control (ATC) 412 system. The CS/ATCIWG is anticipated to meet monthly in the Washington, DC 413 area. Personnel involved in this review process may be required to sign non-414 disclosure agreements and firewall their efforts and participation from 415 vendor/company internal R&D efforts [as directed by the PCO and/or COR]. 416

c. Topside Integration Working Group (TIWG) is established to study and manage 417 the electromagnetic environment aboard the ship. The TIWG is anticipated to 418 meet quarterly in the Washington, DC area. 419

d. Cost & Affordability Working Group (CAWG) is established to ensure that a 420 highly capable system is affordable by coordinating the TOC model development 421 and affordability assessments for EASR. The CAWG will establish TOC model 422 assumptions, evaluate life cycle cost metrics and monitor the Cost and Earned 423

Value on the contract. The CAWG will also interface with the other IPTs. The 424

CAWG is anticipated to meet quarterly in the Washington, DC area. 425

e. System Safety Working Group (SSWG) is established to study and manage 426 system and software safety issues. The Government will identify an EASR 427

Principal For Safety (PFS), who will co-chair the SSWG. The SSWG will also 428 interface with the CS PFS. During this phase, the SSWG is anticipated to meet 429 quarterly in the Washington, DC area. 430

These Government / Industry Teams will include members from Navy and other industry 431 partners. 432

3.1.2.2.3 Modeling and Simulation Plan 433

The Contractor shall generate, maintain, and execute the Modeling and Simulation 434

(M&S) Plan as part of the SEMP (CDRL A004). DoD Modeling and Simulation for the 435

Acquisition Workforce, Version 1.0.1, dated October 2008, is available as guidance. The 436

M&S Plan shall address the development of Models & Simulations (CDRL A008) for all 437

EASR Variants and the use of Models & Simulations through Production. The M&S 438

Plan shall identify the Models and Simulations to be delivered to the Government. The 439 identified Models & Simulations shall provide the Government with a high-fidelity 440 capability to represent EASR performance, including 1) Active array antenna 441 performance, 2) Intentional and spurious harmonic electromagnetic emissions, 3) 442

Adaptive processing, 4) Multi-mission scheduling, 5) Anti-Air Warfare (AAW), 6) 443

(ATC), and 7) system power interface. All M&S used to support System/Subsystem 444

Testing, LBTS Testing, and Operational Testing shall also be identified in the M&S Plan 445 and delivered to the Government. The M&S Plan shall describe the intended use of all 446

M&S used in System/Subsystem Testing, LBTS Testing, and Operational Testing. The 447

Government will accredit M&S prior to use during System/Subsystem, LBTS Testing, 448 and Operational Testing. The M&S Plan shall document the development plans and 449 incremental build delivery schedule for each Model & Simulation, and specify the level 450 of capability for each of these incremental deliveries. The M&S Plan shall describe the 451 computing environment necessary for each Model & Simulation such that delivered code 452 can be hosted and run at equivalently configured Government computing sites. The 453

M&S Plan shall describe the integration of lower level component models into higher 454 level simulations, the interfaces, and input data requirements for these, and how these 455 models will be used to evaluate overall system level performance. The M&S Plan shall 456 describe how the EASR system will be integrated and used with Models & Simulations 457 for design, evaluation, and test. The M&S Plan shall identify those models to be used to 458 process data extracted from the EASR system and how these models will be used in 459 design, evaluation, and test activities. The M&S Plan shall document the configuration 460 management, interactions and dependencies, and verification, validation, and 461 accreditation (VV&A) of Models & Simulations. 462

The following shall be addressed in the M&S Plan: 463

a. Antenna (including distributed receiver/exciter and fixed-weight and adaptive 464 digital beamforming) model(s) including evaluation of the following parameters – 465 main beam characteristics, spatial sidelobes, spectral emissions, wide band 466 steering characteristics, wide band time sidelobes, channel matching, noise figure, 467 and third order intercept; 468

b. Scheduler and resource loading model(s) that address long term planning and 469 long/short term scheduling for EASR; 470

c. High Fidelity AAW, ATC, Anti-Surface Warfare (ASuW), and Weather Mapping 471 models; 472

d. Signal processor algorithm chain model; 473

e. Signal processor latency/throughput model; 474

f. Radar control and data processor timing model; 475

g. Threat models; 476

h. Environmental models (natural and jamming); 477

i. Detailed description of the required computing environment(s) (platforms, 478 libraries, compilers, commercially licensed tools, etc.) for each M&S item; 479

j. Schedule for all M&S development, integration, test, and VV&A activities; and 480

k. Build and delivery schedule for Models & Simulations; 481

l. EASR system power interface model that accurately represents EASR's stability, 482 input impedance, inrush current, current ripple and ramp rate, from the 483 perspective of the ship power interface to EASR during start up, shut down, mode 484 transitions (e.g., in and out of radar modes) and power substate transitions. 485

3.1.2.2.4 Risk Management and Reporting 486

The Contractor shall generate, maintain, and execute the Risk Management Plan (RMP) 487 as part of the SEMP (CDRL A004) for the EASR program through Production. The 488

Contractor shall implement and maintain a risk management program in accordance with 489 the approved RMP to identify and manage risks associated with achievement of the 490 program’s technical (including performance), cost, and schedule requirements. Risks 491 shall be reported to the Government during IPT/WG meetings, In-Progress Reviews 492

(IPRs), and SETRs. Risk management and reporting shall be in accordance with 493

PEOIWSINST 5000.8, PEO IWS 2.0 Risk Management Policy, and NAVSEAINST 494

5000.8 (Naval SYSCOM Risk Management Policy). Risk Management Guide for DoD 495

Acquisition, 7th Edition (Interim Release), dated December 2014, is available as 496 guidance. 497

The Contractor shall capture risks and associated mitigation plans in a risk database and 498 provide status updates for all documented risks in the Engineering Design Notebook 499

(EDN) (CDRL A046). 500

3.1.2.2.5 Life Cycle Support Concept 501

The Contractor shall generate the product support concept for EASR in the SEMP 502

(CDRL A004). The concept shall include life cycle support planning and development of 503 manning levels, manuals, sustainment requirements, continuous improvement, 504 performance based lifecycle product support, human systems integration, corrosion 505 prevention and control, diminishing manufacturing sources and material shortages, an 506 approach to implementation of item unique identification and radio frequency 507 identification, distance support, quality assurance, configuration management, and 508 system safety. 509

3.1.2.3 Program Protection Implementation Plan 510

The Contractor shall generate and execute a Program Protection Implementation Plan 511

(PPIP) (CDRL A005) through production, in accordance with the EASR Program 512

Protection Plan (PPP). DoDI 4140.67, DoDI 5000.02, DoDI 5200.39 including Change 513

1, DODI 5200.44, SECNAVINST 4855.3C, SECNAVINST 5000.2E, and the Deputy 514

Assistant Secretary of Defense, Systems Engineering PPP Outline and Guidance are 515 available as guidance. This PPIP shall address program protection requirements outlined 516 in the PPP template, Sections 2 through 11 including identification of the Critical 517

Program Information (CPI) and Mission Critical Functions and components, 518 identification of vulnerabilities, risk assessment and the identification of potential 519 countermeasures. 520

The PPIP shall address the protection of EASR and all interfaces included in the EASR 521

External (Logical) IRS (CDRL A021). 522

The PPIP shall be prepared in order to ensure effective and efficient protection of 523 essential program information, technologies and systems. The PPIP shall include: 524

a. Description of the security management structure; 525

b. Identification of CPI (Inherent and Inherited); 526

c. Identification of CPI physical locations under the Contractor’s or Subcontractors’ 527 control; 528

d. Assessment of the vulnerability of the CPI to intelligence collection in the 529 following areas: Human Intelligence (HUMINT); Open Source Intelligence 530

(OSINT); Signals Intelligence (SIGINT); Imagery Intelligence (IMINT); 531

Computer Network Operations (CNO); 532

e. Identification of the countermeasures to be implemented at each site where CPI is 533 held; 534

f. Special handling procedures required for CPI, and procedures for recovering CPI 535 in the event of a mishap; 536

g. Description of Criticality Analysis to be performed in support of SETRs; 537

h. Identification of risk mitigation techniques to counter threats to the Contractor’s 538 supply chain; and 539

i. Procedures for ensuring compliance with U.S. Government export statutes and 540 regulations. 541

3.1.2.3.1 Cybersecurity 542

The Contractor shall implement cybersecurity processes and procedures in accordance 543 with DoDI 8510.01, Risk Management Framework (RMF) for DoD Information 544

Technology (IT), NAVSEAINST 9400.2, National Institute of Standards and Technology 545

(NIST) Special Publication 800-37 (Feb 2010, as amended); Subchapter III of Chapter 35 546 of Title 44, U.S. Code (aka "Federal Information Security Management Act (FISMA) of 547

2002"); Committee on National Security Systems Instruction 1253 (15 Mar 2012, as 548 amended); and NIST Special Publication 800-53. The Contractor shall implement all 549 relevant cybersecurity controls and configuration requirements as defined within DoDI 550

8500.01, Cybersecurity. This shall be satisfied by employing tenets of defense-in-depth 551 for layering cybersecurity solutions within a given IT asset and among assets; and 552 ensuring appropriate robustness of the solution, as determined by the relative strength of 553 the mechanism and the confidence that it is implemented and will perform as intended. 554

The Contractor shall establish appropriate administrative, technical, and physical 555 safeguards to protect any and all Government systems and data, to ensure the 556 confidentiality, integrity, availability, authentication, and non-repudiation of Government 557 data. This shall include provisions for personnel security, electronic security and 558 physical security. 559

The Contractor shall generate, maintain and execute an EASR System Security Plan 560

(SSP) (CDRLA006), using the EASR Cybersecurity Strategy and NIST SP 800-18 as 561 guidance. The SSP shall provide a mechanism to identify and resolve implementation 562 issues related to an acquisition program's Information Technology (IT), including 563

National Security Systems (NSS), infrastructure support and IT and NSS interface 564 requirements. The SSP shall identify IT needs, dependencies, and interfaces for programs 565 in all acquisition categories, focusing attention on interoperability, supportability, 566 synchronization, sufficiency, and net-centricity concerns. In addition, the SSP shall 567 identify and address the cybersecurity strategy for both technical exchange of information 568 and the end-to-end operational effectiveness of that exchange between systems. The SSP 569 shall include the strategy to address TEMPEST and Emission Security or Emanations 570

Security (EMSEC). DISA publishes Security Technical Implementation Guides (STIGs) 571 for a variety of technologies. The Contractor shall evaluate applicability of the STIGs 572 and deliver the results of this review in the SSP. Cybersecurity technical reference 573 documents can be downloaded from the DISA IASE website at 574 http://iase.disa.mil/stigs/Pages/index.aspx. The Contractor shall provide an approach for 575 implementing cybersecurity controls for EASR with Impact Values and Security 576

Objectives of Confidentiality: HIGH, Integrity:HIGH, and Availability:HIGH. 577

The Contractor shall also develop and deliver the following cybersecurity-related 578 information in the SSP: 579

a. Cybersecurity Control Requirements Traceability Matrix to include tailored-out 580 controls; 581

b. STIG Applicability Review and Report (including Security Requirements Guides 582

(SRG) and Security Checklists); 583

c. Objective Defense-in-Depth (DID) Architecture Diagrams for the system, the sub-584 network, or platform network into which the system will be integrated; 585

d. List of cybersecurity validation and test procedures performed by the Contractor 586 to verify that the stated cybersecurity requirements have been met (validation and 587 test results shall be made available upon request) ; 588

e. Information Assurance (IA) Residual Risk Assessment and Mitigation Plan; and 589

f. System Security Administrator Operations Manual (SSAOM). 590

3.1.2.3.1.1 Commercial Off-The-Shelf (COTS) Authentication 591

The Contractor shall evaluate COTS software used in EASR prior to implementation of 592 cybersecurity capabilities in accordance with GAO-04-678; DODI 8500.01; and ISO/IEC 593

15408, Common Criteria v3.1. Release 4. 594

3.1.2.3.1.2 Government Off-The-Shelf (GOTS) Capabilities 595

The Contractor shall evaluate GOTS cybersecurity capabilities utilized in EASR in 596 accordance with NSA-approved processes prior to implementation in accordance with 597

GAO-04-678; DODI 8500.01; and ISO/IEC 15408, Common Criteria v3.1. Release 4. 598

3.1.2.3.2 Anti Tamper 599

The Contractor shall generate, maintain, and execute the Anti-Tamper (AT) Plan (CDRL 600

A007) for the EASR through production, in accordance with the EASR AT Process. The 601

AT Plan shall include a list of critical technologies, identified vulnerabilities, an analysis 602 of AT methods that apply to the system, including cost/benefit assessments, and an 603 explanation of which AT method(s) will be implemented. 604

The Contractor shall develop and implement AT hardware and software protection 605 measures for the case of unplanned loss, to protect CPI and AT Critical Technologies 606

(CT) defined by DoDI 5200.39 with Change 1. DoDI S-5230.28 and DoD Anti-Tamper 607

(AT) Guidelines, Version 2.0, are available as guidance. AT measures shall deter efforts 608 to Reverse Engineer (RE), exploit, or develop countermeasures. AT measures shall 609 prevent unauthorized access to critical software functionality regardless of the system 610 configuration. The Contractor shall consider the potential for international sales in the 611

AT design. 612

The AT Plan shall include: 613

g. AT Critical Technology (CT) for proposed architecture, and locations of CT in 614 the architecture; 615

h. Identification of impacts if CT is exploited by an adversary; 616

i. Identification vulnerabilities of CT in the system; 617

j. Attack tree analysis; 618

k. Identification of available AT techniques for the system; 619

l. Identification of AT solution sets and AT architectures for the system; 620

m. Anti-Tamper development schedule, including SETRs, TIMs, and verification and 621 validation schedule; 622

n. Key Management Plan that addresses all cryptographic requirements; 623

o. Plan to integrate AT into logistics support concept; 624

p. AT implementation costs (Non-Recurring Engineering and Recurring 625

Engineering); 626

q. Future applicability for Foreign Military Sales (FMS); and 627

r. AT Verification and Validation Plan. 628

3.1.2.3.3 Criticality Analysis 629

In accordance with the PPIP (CDRL A005), the Contractor shall generate the EASR 630

Criticality Analysis Report and deliver in the EDN (CDRL A046) prior to PDR, CDR, 631 and SVR/FCA. 632

3.1.2.4 Modeling and Simulation Development 633

The Contractor shall code, test, document and deliver Models & Simulations (CDRL 634

A008) in accordance with the M&S Plan in the SEMP (CDRL A004). The 635 documentation provided for each Model & Simulation shall include a user manual 636 sufficient to allow the Government to utilize the Model & Simulation. In addition, the 637

Contractor shall train Government personnel on the operation of each delivered Model & 638

Simulation. Training sessions shall be limited to one (1) per delivery of each Model & 639

Simulation and the Government personnel attending each session will be limited to nine 640

(9). Each delivered Model & Simulation shall include commented source code, 641 executable code, block/flow diagrams, algorithm descriptions, and input data files 642 necessary for execution. 643

For Models & Simulations that have been identified for VV&A, the Contractor shall 644 provide the following plans and reports and all supporting data in accordance with MIL-645

STD-3022-1: 646

a. Verification and Validation (V&V) Plan (CDRL A009); 647

b. Modeling and Simulation (M&S) Accreditation Plan (CDRL A010); 648

c. Verification and Validation (V&V) Report (CDRL A011); and 649

d. Modeling and Simulation (M&S) Accreditation Report (CDRL A012), except for 650 sections D.9 “Accreditation Assessment” and D.10 “Accreditation 651

Recommendations” which will be written by the Government. 652

3.1.2.5 System/Subsystem Specification (A-Specification) 653

EASR shall meet all requirements in the EASR System Requirements Document (SRD). 654

The Contractor shall update and maintain the EASR System/Subsystem Specification 655

(SSS) (A-Specification), (CDRL A013). 656

The Contractor shall perform required analyses, modeling and simulation, functional 657 allocation, and flow down of requirements from the EASR System Requirements 658

Document (SRD) to the EASR A-Specification (CDRL A013). In addition, the A-659

Specification shall capture requirements based on the PPIP (CDRL A005), SSP (CDRL 660

A006), AT Plan (CDRL A007), Human Engineering System Analysis Report (HESAR) 661

(CDRL A106), and ISP within the SEMP (CDRL A004). The A-Specification shall 662 include a traceability matrix with rationale that traces each requirement in the A-663

Specification to the requirement in the SRD or a derived requirement from the PPIP, AT 664

Plan, HESAR, and SEMP. 665

The A-Specification shall address two EASR configurations: Variant 1, a single-face 666 array with rotating positioner to provide AN/SPS-48 and AN/SPS-49 capabilities for 667 installation on Amphibious Warfare Ships, and Variant 2, a three-face fixed array design 668 slated for Aircraft Carriers. 669

3.1.2.6 System Architecture 670

The Contractor shall generate and maintain a Systems Architecture Document (SAD) 671

(CDRL A014). The SAD shall contain the architecture products that describe the 672 functional allocation consistent with the EASR SRD and EASR A-Specification (CDRL 673

A013). These architecture products shall provide the context, operation, functions, 674 interfaces and activities of EASR. Context for EASR and CS/ATC operation, 675 functionality, interfaces and activity shall be included. The Contractor shall develop these 676 architecture products using Unified Modeling Language / System Modeling Language 677

(UML/SysML), Department of Defense Architecture Framework (DoDAF), or other 678

Government approved Contractor formats. 679

The Systems Architecture Document shall also contain operationally-oriented diagrams 681 that describe the functionality of EASR using UML/SysML. The operational activity & 682 sequence diagrams shall contain information on the following: 683

a. Complete description of all operational activities; 685

b. Mapping of operational activities to subsystem; 686

c. Allocation of functions to configuration items; 687

d. Identification of driving system throughput and timing (stated in the context of 688 operational requirements (e.g., support of raids); 689

e. Identification of parallelism or sequential operation; 690

f. Concurrent radar operations support, including overload processing; and 691

g. Supporting context of Software Configuration Items (CI) 692

The Contractor shall keep the Systems Architecture Document up to date for any changes 693 during the execution of CLIN 0001 as a result of incremental development of software 694 requirements and design. 695

3.1.2.7 Concept of Operations Document 696

The Contractor shall generate and maintain the Concept of Operations (CONOPS) 697

(CDRL A015) document that describes the operation of EASR and captures the 698

CONOPS for all mission areas described in the EASR SRD. The CONOPS document 699 shall contain information on the following: 700

a. Narrative description of radar operation in each functional area; 701

b. High-level description of performance along with a discussion of key 702 performance drivers and associated rationale; 703

c. Description of waveforms, processing algorithms to be used and associated 704 rationale; and 705

d. Interface data flow, including interaction with the CS and ATC. 706

3.1.2.8 Hardware Specification (B2-Specification) 707

The Contractor shall generate and maintain EASR Hardware Specifications (B2-708

Specifications) (CDRL A016) for each hardware CI. The Contractor shall maintain a 709 traceability matrix for each B2-Specification that indicates the source of each 710 requirement from the EASR A-Specification (CDRL A013) and shall include these 711 matrices with rationale as part of each respective B2-Specification. The Contractor shall 712 also provide analyses to verify the flow-down of requirements from the A-Specifications 713 to the B2-Specifications for each CI. 714

3.1.2.9 Software Requirements Specification (B5-Specification) 715

The Contractor shall generate and maintain EASR Software Requirements Specifications 716

(SRSs) (B5-Specifications) (CDRL A017) for each software CI. The Contractor shall 717 maintain a traceability matrix with rationale for each B5-Specification that indicates the 718 source of each requirement from the EASR A-Specification (CDRL A013) and shall 719 include these matrices as part of each respective B5-Specification. The Contractor shall 720 also provide analyses to verify the flow-down of requirements from the A-Specifications 721 to the B5-Specifications for each CI. The Contractor shall also identify the associated 722 software Build (from the approved SDP (CDRL A050)) and associated Build Function 723 for each B-5 requirement. 724

3.1.2.10 Interface Specifications 725

The Contractor shall generate and maintain an EASR Hardware Internal Interface 726

Requirements Specification (IRS) (CDRL A018) and an EASR Software Internal IRS 727

(CDRL A019) documenting the functional, physical, and electrical specifications of the 728 interfaces within EASR. The Contractor shall identify the associated software Build 729

(from the approved SDP (CDRL A050)) and associated Build Function for each Software 730

Internal IRS requirement. 731

The Contractor shall generate and maintain an EASR Hull, Mechanical & Electrical 732

(HM&E) IRS (CDRL A020) for Variants 1 and 2. The Contractor shall identify the 733 interfaces based on the functional architecture. 734

The Contractor shall generate and maintain an EASR External (Logical) IRS (CDRL 735

A021). The EASR External (Logical) IRS shall address the interfaces between 736

EASR/CS, EASR/Electronic Warfare System, EASR/ATC, and EASR/Missiles. The 737

External (Logical) IRS shall contain information and controls available to Ship Self 738

Defense System (SSDS), Cooperative Engagement Capability (CEC) and AN/TPX-42. 739

The Contractor shall develop the EASR External (Logical) IRS in accordance with the 740

EASR SRD. The Contractor shall use Weapon Specifications (WS) 23302G, 35556, and 741

35569 as guidance in developing the EASR External (Logical) IRS. The Contractor shall 742 participate in the CS/ATCIWG to further refine these interfaces. This IRS shall be used 743 by the Contractor for implementing all EASR external interfaces. 744

3.1.2.11 System/Subsystem Design Description (SSDD) 745

The Contractor shall document the hardware design in an EASR System/Subsystem 746

Design Descriptions (SSDDs) (CDRL A022). The SSDDs shall contain the detailed 747 design requirements, key drivers for meeting the requirements, system thread definitions, 748 and underlying rationale. The SSDDs shall include the EASR hardware detailed designs, 749 the requirements hierarchy and the analyses and experimental results that support the 750 requirements flow-down. The SSDDs shall be delivered as part of the design disclosures 751 leading to EASR Hardware PDR and CDR and maintained through the EMD and 752

Production. 753

3.1.2.12 Software Design Description (SDD) 754

The…