Att 4 - N0002415R5370 4C EASR_J-01_SOW.pdf

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 March 2015 16 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 ............................................................................................... 7 31

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

3.1.3 EMD Production ........................................................................................... 29 33

3.1.4 Integration and Test ...................................................................................... 30 34

3.1.5 Specialty Engineering ................................................................................... 36 35

3.1.6 Configuration Audit ...................................................................................... 49 36

3.1.7 Program Management ................................................................................... 49 37

3.2 OPTION- ENGINEERING SERVICES (CLIN 0101,0201, AND 0301) .................. 54 38

3.3 OPTION-TRAVEL IN SUPPORT OF CLIN 0101 (CLIN 0102) ........................... 54 39

3.4 OPTION-TRAVEL IN SUPPORT OF CLIN 0201 (CLIN 0202) ........................... 55 40

3.5 OPTION-TRAVEL IN SUPPORT OF CLIN 0301 (CLIN 0302) ........................... 55 41

3.6 OPTION-PRODUCTION LONG LEAD MATERIAL (FIRST UNIT) (CLIN 0303 AND 42

0304) ................................................................................................................. 55 43

3.7 PRODUCTION (CLINS 0303[UPON SUBSUMPTION OF 0401-0402]/0304[UPON 44

SUBSUMPTION OF 0403-0404]/0501-0504/0601-0602/0701-0704/0801-0802) 55 45

3.7.1 Production General Requirements ................................................................ 55 46

3.7.2 Option-Production Units (CLINs 0401-0404) .............................................. 63 47

3.7.3 Option- Non-Recurring Engineering Effort For Transition to Production, 48

First Article Testing, and Physical Configuration Audit (CLIN 0407-0408) ........... 64 49

3.7.4 Options-Production Units (0501-0504/0601-0602/0701-0704/0801-0802) . 66 50

3.8 OPTION- ENGINEERING SERVICES (CLIN 0405, 0505, 0603, 0705, AND 0803)51

.......................................................................................................................... 66 52

3.9 OPTION-TRAVEL IN SUPPORT OF CLIN 0405 (CLIN 0406) ........................... 66 53

3.10 OPTION-TRAVEL IN SUPPORT OF CLIN 0505 (CLIN 0506) ........................... 66 54

3.11 OPTION-TRAVEL IN SUPPORT OF CLIN 0603 (CLIN 0604) ........................... 66 55

3.12 OPTION-TRAVEL IN SUPPORT OF CLIN 0705 (CLIN 0706) ........................... 66 56

3.13 OPTION-TRAVEL IN SUPPORT OF CLIN 0803 (CLIN 0804) ........................... 66 57

3.14 OPTION- FIELD ENGINEERING SERVICES (CLINS 0507, 0605, 0707, AND 0805)58

.......................................................................................................................... 66 59

3.15 OPTION-TRAVEL IN SUPPORT OF CLIN 0507 (CLIN 0508) ........................... 67 60

3.16 OPTION-TRAVEL IN SUPPORT OF CLIN 0605 (CLIN 0606) ........................... 67 61

3.17 OPTION-TRAVEL IN SUPPORT OF CLIN 0707 (CLIN 0708) ........................... 67 62

3.18 OPTION-TRAVEL IN SUPPORT OF CLIN 0805 (CLIN 0806) ........................... 67 63 ii

1 SCOPE 66

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

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

(SCSC), Wallops Island, VA (hereafter refered to as SCSC). In addition, Options will be 72 included for Production. 73

EASR will serve as the primary sensor for ship self-defense, situational awareness and air 74 traffic control in a dense EMI and clutter environment for carrier and amphibious ship 75 classes. 76

DRAFT RFP Commentary and Instructions for Requesting GFI: It is the Government’s 77 intent that EASR will leverage existing radar systems to minimize development. An 78 example of an existing radar system that can be leveraged is Affordable Common Radar 79

Architecture (ACRA). A description of ACRA is availabe upon request as part of the 80

Draft RFP; however,this information is covered by Distribution Statement D. 81

Leveraging ACRA into the Contractor design is not a requirement. In addition, the 82

ACRA design as described may not meet all requirements for EASR. 83

The GFI data may be requested by submitting a signed statement on company letterhead 84 that states your company is a United States Department of Defense Contractor to 85 dennis.j.cole@navy.mil with a cc to sheila.utz1@navy,mil and john.butto@navy.mil. 86

This statement will be verified in System for Award Management located at 87

(https://www.sam.gov/portal/SAM/). 88

1.1 Background 90

EASR will be one sensor in a new sensor suite that is designed to meet the performance 91 needs contained in the Battlespace Awareness Initial Capabilities Document. EASR is to 92 be fielded in two variants. Variant 1 is a single-face array rotating design to provide 93

SPS-48 and SPS-49 capabilities for installation on Amphibious Warfare Ships such as 94 new contruction America Class Amphibious Assault Ships (LHA-8+), LPD, and LX(R), 95 and any other designated ship class. Variant 2 is a three-face fixed array design slated for 96

Aircraft Carriers and any other designated ship class. 97

2 APPLICABLE DOCUMENTS 98

2.1 Mandatory Documents 99

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

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

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

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

Classification Guide, included as Attachment J-04. 105 mailto:sheila.utz1@navy,mil mailto:john.butto@navy.mil https://www.sam.gov/portal/SAM/

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

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

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

14 March 2014 109

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

Version 1.0, included as Attachment J-26 111

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

Needed to Manage Risks, dated 25 May 2004 113

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

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

Version 1.0, included as Attachment J-22 116

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

Models and Simulations, dated 05 April 2012 118

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

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

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

Attachment J-28 122

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

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

Lithium Safety Program and Procedures, dated 19 Aug 2004 125

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

Jun 1991 127

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

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

Development And Manufacturing, dated 13 Nov 2008 130

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

Depth, Development, Production, Installation, and Servicing 132

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

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

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

J-15 136

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

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

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

Engineering Warfare System Engineering and Human Systems Integration 140

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

December 2009 142

v. CVN-79/80 Topside Emitters List 143

w. LHA-8 Topside Emitters List 144

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

Feb 2007 146

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

Command System Safety Program For Ships, Shipborne Systems And 148

Equipment, dated 03 Aug 2011 149

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

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

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

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

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

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

Engineering Design for, dated 15 August 1994 156

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

17 December 2007 158

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

1999 160

hh. CSDR Manual (DoD 5000.04-M-1), dated 04 November 2011 161

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

Items, dated 03 October 2011 163

jj. ARTIST Radar Facility, Surface Combat Systems Center, Wallops Island, 164

VA, 20 September 2007, included as Attachment J-27 165

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

31 August 2011. 167

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

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

Acquisition, and Management, 14 August 2013 171

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

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

Information Technology (IT), 12 March 2014 174

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

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

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

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

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

2012, as amended 180

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

Publication 800-53, February 2009 182

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

Publication 800-18, Revision 1, February 2006 184

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

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

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

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

2.2 Guidance Publications 191

The following publications are available as guidance: 192

xx. ISO 10303/AP 233 – Standard for the Exchange of Product Model 193

Data/Application Protocol 233 (Systems Engineering Data 194

Representation) 195

yy. DoD Modeling and Simulation for the Acquisition Workforce, Version 196

1.0.1, dated October 2008 197

zz. SAE GEIA-HB-0007B, Logistics Product Data Handbook 198 aaa. PEOIWSINST 5000.8, PEO IWS 2.0 Risk Management Policy, 13 199

January 2014 200 bbb. Naval SYSCOM Risk Management Policy, NAVSEAINST 5000.8, dated 201

21 Jul 2008 202 ccc. Risk Management Guide for DoD Acquisition, 7th Edition (Interim 203

Release), dated December 2014 204 ddd. DoDI 5200.39 with Change 1, Security, Intelligence, and 205

Counterintelligence Support to Acquisition Program Protection, 28 206

December 2010 207 eee. NAVSEAINST 9400.2, Implementation of Naval Sea Systems Command 208

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

April 2010, included as Attachment J-30 211 ggg. DoD Manufacturing Readiness Level (MRL) Deskbook,V2.2.1 dated 212

October 2012 213 hhh. MIL-S-901D – Shock Tests, H.I. (High-Impact) Shipboard Machinery, 214

Equipment, and Systems, Requirements for, dated 17 Mar 1989 215

iii. MIL-HDBK-2155, Failure Reporting, Analysis and Corrective Action 216

Taken, 11 Dec 1995 217 jjj. DoD Joint Software Systems Safety Engineering Handbook, dated 27 Aug 218

2010 219 kkk. NAVSEAINST 8020.6E - Department of the Navy Weapon Systems 220

Explosive Safety Review Board, dated 11 March 2008 221 lll. NAVSEA SW020-AH-SAF-010, Weapons System Safety Guidelines 222

Handbook, 01 Feb 2006 223 mmm. DoDI 5000.02, Operation of the Defense Acquisition System, dated 07 Jan 224

2015 225 nnn. MIL-HDBK-217F-2 – Reliability Prediction of Electronic Equipment, 226 dated 28 Feb 1995 227 ooo. MIL-HDBK-472-1 – Maintainability Prediction, dated 12 Jan 1984 228 ppp. MIL-HDBK-61A, Configuration Management Guidance, dated 07 Feb 229

2001 230 qqq. ANSI/EIA 649B, National Consensus Standard for Configuration 231

Management, dated 01 Apr 2011 232 rrr. PEO IWS 2.0 Above Water Sensors Configuration Management 233

Plan/Procedures 234 sss. DoD Product Support Business Case Analysis (BCA) Guidebook, dated 235

April 2011 236 ttt. NAVSEA A Program Manager’s Guide to the Application of Performance 237

Based Logistics (PBL), Revision A, dated 08 October 2008 238 uuu. DoD Corrosion Prevention and Control Planning Guidebook for Military 239

Systems and Equipment, Spiral 4, 04 February 2014 240

vvv. DoD Diminishing Manufacturing Sources and Material Shortages 241

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

Robust DMSMS Management Program (SD-22), February 2015 243 www. Enterprise Air Surveillance Radar (EASR) Item Unique Identification 244

(IUID) Plan, Version 1.0, included as Attachment J-25 245

xxx. DoD Suppliers’ Passive RFID Information Guide, Version 15, dated 246

January 2010 247 yyy. DoDI S-5230.28 , Low Observable (LO) and Counter Low Observable. 248

(CLO) Programs (U), 26 May 2005 249 zzz. North Atlantic Treaty Organization (NATO) Allied Ordnance Publication 250

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

Munition-Related Computing Systems, November 2008 252 aaaa. DoD Manual 5000.04-M-1, Cost and Software Data Reporting (CSDR) 253

Manual, 4 November 2011 254 bbbb. DoDI 4140.67, DoD Counterfeit Prevention Policy, 26 April 2013 255 cccc. DODI 5200.44, Protection of Mission Critical Functions to Achieve 256

Trusted Systems and Networks, 05 November 2012 257 dddd. SECNAVINST 4855.3C, Product Data Reporting and Evaluation 258

Program, 27 June 2014 259 eeee. Deputy Assistant Secretary of Defense, Systems Engineering PPP Outline 260 and Guidance, Version 1.0, July 2011 261 ffff. SECNAVINST 5000.2E, Department of the NavyImplementation and 262

Operation of the Defense Acquisition System and the Joint Capabilities 263

Integration and Development System, dated 01 September 2011 264 gggg. Weapons Specification (WS) 23302G, Interface Design Description for 265 the Ship Self-Defense System MK 2 MOD () (SSDS MK 2 MOD ()) / 266

Cooperative Engagement Capability (CEC) Cooperative Engagement 267

Processor (CEP), 03 October 2012 268 hhhh. Weapon Specification (WS) 35556, Dual Band Radar Integration 269

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

iiii. Weapon Specification (WS) 35569, Interface Description for the Dual 271

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

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

())/Cooperative Engagement Capability (CEC) Cooperative Engagement 274

Processor (CEP), 08 February 2012 275 jjjj. MIL-HDBK-470A, Designing and Developing Maintainable Products and 276

Systems, Volume I, 04 August 1997 277 kkkk. MIL-HDBK-1390, Level of Repair Analysis, 29 January 2015 278 llll. Navy Education and Training Manual 138 (NAVEDTRA 138), Naval 279

Education and Traing Command-Front End Analysis Management 280

Manual, June 2012 281 mmmm. MIL-HDBK 29612/1A, Guidance for Acquisition of Training Data 282

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

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

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

August 2001 289 qqqq. MIL-HDBK 29612/5A, Advanced Distributed Learning (ADL) Products 290 and Systems (Part 5 of 5 Parts), 31 August 2001 291 rrrr. MIL-HDBK-729, Corrosion and Corrosion Prevention Metals, 21 292

November 1983 293

2.3 Precedence 294

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

Documents, and Section 2.2, Guidance Publications, the documents in Section 2.1 shall 296 take precedence. 297

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

3 REQUIREMENTS 301

3.1 Engineering and Manufacturing Development (CLIN 0001) 302

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

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

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

Specifications (IRS) (CDRL A021); 307

b. The Contractor shall build, integrate, and deliver a Variant 1,single face array 308 with rotating positioner, production representative EASR EDM, EASR Interface 309

Simulator, Emulator, two (2) System Displays and Control (SDCs) with 310 computing hardware, Maintenance Manual with computing hardware, and EASR 311

Land Based Test Site (LBTS) Spare Parts; 312

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

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

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

SCSC in accordance with the approved Test Plan (CDRL A071) and deliver the 316

Government approved LBTS Summary Test Report (CDRL A075); 317

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

(CDRL A100) and implement all corresponding Revisions (CDRL A101) 319

(Subject to Government approval within LCCB); 320

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

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

g. The Contractor shall provide a final TOC Model (CDRL A047) that reflects 325 actual costs incurred during EMD phase and clearly shows the relationship of 326

EDM hardware costs to Production and future production costs; 327

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

Action Items (CDRL A003); and 329

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

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

3.1.1 EMD Overview 332

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

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

3.1.2 Systems Engineering 339

3.1.2.1 System Engineering Technical Reviews (SETRs) 340

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

SETRs to be conducted under CLIN 0001. These reviews will be event driven and 342 predicated upon satisfying the SETR Entrance Criteria. 343

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

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

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

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

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

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

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

Government 352

g. Transition CDR, chaired by the Government 353

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

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

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

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

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

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

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

Material (CDRL A002) on the Government Integrated Digital Environment (IDE) 366 preceding each review. The Contractor shall place final Presentation Materials on the 367

Government IDE following the reviews. The Contractor shall prepare Minutes (CDRL 368

A003) to include a database to capture and manage all Government and Contractor 369

Action Items from the reviews. The database shall reside on the Government IDE. The 370

Contractor shall update Action Item status, including closure plans, at least weekly. 371

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

CDRs. These meetings shall address the engineering material and documentation 373 sufficient to convey a detailed understanding to the Government technical team, and to 374 complete comment adjudication activities. The content of the design disclosures shall be 375 delivered in the EDN (CDRL A046) or design descriptions. 376

3.1.2.2 Systems Engineering Management 377

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

3.1.2.2.1 Systems Engineering Planning and Execution 379

The Contractor shall generate, maintain, and execute the SEMP (CDRL A004). The 380

SEMP shall address the EASR program through Production. The SEMP shall describe 381 how a fully integrated engineering effort will be managed and conducted. The plan shall 382 provide details of the flow of requirements from the Government’s top level requirements 383 to the Contractor’s design documents. In addition, the Contractor shall include Technical 384

Performance Measures (TPMs) in the SEMP to be utilized for the program. The 385

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 COR. 392

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

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

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

A003) on the Government IDE. 397

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

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

b. Combat System/Air Traffic Control Integration Working Group (C/ATIWG) is 403 established to manage interfaces and ensure that the functional allocation and the 404 performance of EASR is fully utilized Combat System (CS) (including weapon 405 system components, electronic warfare systems, missiles and track databases), 406

Cooperative Engagement Capability (CEC) and Air Traffic Control (ATC) 407 system. The C/ATIWG is anticipated to meet monthly in the Washington, DC 408 area. 409

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

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

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

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

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

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

These Government / Industry Teams will include members from Navy and other industry 424 partners. 425

3.1.2.2.3 Modeling and Simulation Plan 426

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

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

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

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

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

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

Adaptive processing, 4) Multi-mission scheduling, 5) AAW, 6), and 7) system power 436 interface. All M&S used to support System/Subsystem Testing, LBTS Testing, and 437

Operational Testing shall also be identified in the M&S Plan for delivery to the 438

Government. The M&S Plan shall describe the intended use of all M&S used in 439

System/Subsystem Testing, LBTS Testing, and Operational Testing. The Government 440 will accredit M&S prior to use during System/Subsystem, LBTS Testing, and 441

Operational Testing. The M&S Plan shall document the development plans and 442 incremental build delivery schedule for each Model & Simulation, and specify the level 443 of capability for each of these incremental deliveries. The M&S Plan shall describe the 444 computing environment necessary for each Model & Simulation such that delivered code 445 can be hosted and run at equivalently configured Government computing sites. The 446

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

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

a. Antenna (including distributed receiver/exciter and fixed-weight and adaptive 457 digital beamforming) model(s) including evaluation of the following parameters – 458 main beam characteristics, spatial sidelobes, wide band steering characteristics, 459 wide band time sidelobes, channel matching, noise figure, and third order 460 intercept; 461

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

c. Search and track models for ancillary functions; 464

d. High Fidelity Anti-Air Warfare (AAW) surveillance/detection/track model; 465

e. Signal processor algorithm chain model; 466

f. Signal processor latency/throughput model; 467

g. Radar control and data processor timing model; 468

h. Threat models; 469

i. Environmental models; 470

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

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

l. Build and delivery schedule for Models & Simulations; 474

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

3.1.2.2.4 Risk Management and Reporting 479

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

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

Reviews (IPRs). Risk management and reporting shall be in accordance with 486

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

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

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

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

(EDN) (CDRL A046). 493

3.1.2.2.5 Life Cycle Support Concept 494

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

(CDRL A004). The concept shall include life cycle support planning and development of 496 manning levels, manuals, sustainment requirements, continuous improvement, 497 performance based lifecycle product support, human systems integration, corrosion 498 prevention and control, diminishing manufacturing sources and material shortages, an 499 approach to implementation of item unique identification and radio frequency 500 identification, distance support, quality assurance, configuration management, and 501 system safety. 502

3.1.2.3 Program Protection Implementation Plan 503

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

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

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

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

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

Program Information (CPI) and Mission Critical Functions and components, 511 identification of vulnerabilities, risk assessment and the identification of potential 512 countermeasures. 513

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

External (Logical) IRS (CDRL A021). 515

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

a. Description of the security management structure; 518

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

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

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

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

Computer Network Operations (CNO); 525

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

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

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

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

i. Procedures for ensuring compliance with U.S. Government export statutes and 533 regulations. 534

3.1.2.3.1 Cybersecurity 535

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

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

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

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

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

The Contractor shall establish appropriate administrative, technical, and physical 548 safeguards to protect any and all Government systems and data, to ensure the 549 confidentiality, integrity, availability, authentication, and non-repudiation of Government 550 data. This shall include provisions for personnel security, electronic security and 551 physical security. 552

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

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

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

Security (EMSEC). DISA publishes Security Technical Implementation Guides (STIGs) 564 for a variety of technologies. The Contractor shall evaluate applicability of the STIGs 565 and deliver the results of this review in the SSP. Cybersecurity technical reference 566 documents can be downloaded from the DISA IASE website at 567 http://iase.disa.mil/stigs/index.html. The Contractor shall provide an approach for 568 implementing cybersecurity controls for EASR with Impact Values and Security 569

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

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

a. Cybersecurity Control Requirements Traceability Matrix to include tailored-out 573 controls; 574

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

(SRG) and Security Checklists); 576

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

d. List of cybersecurity validation and test procedures performed by the Offeror to 579 verify that the stated cybersecurity requirements have been met (validation and 580 test results will be made available upon request) ; 581

e. IA Residual Risk Assessment and Mitigation Plan; and 582

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

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

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

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

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

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

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

3.1.2.3.2 Anti Tamper 592

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

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

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

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

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

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

AT design. 605

The AT Plan shall include: 606

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

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

i. Identification vulnerabilities of CT in the system; 610

j. Attack tree analysis; 611

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

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

m. Anti-Tamper development schedule, including SETRs, TIMs, and verification and 614 validation schedule; 615

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

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

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

Engineering); 619

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

r. AT Verification and Validation Plan. 621

3.1.2.3.3 Criticality Analysis 622

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

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

3.1.2.4 Modeling and Simulation Development 626

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

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

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

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

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

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

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

STD-3022-1: 639

a. V&V Plan (CDRL A009); 640

b. Accreditation Plan (CDRL A010); 641

c. V&V Report (CDRL A011); and 642

d. Accreditation Report (CDRL A012), except for sections D.9 “Accreditation 643

Assessment” and D.10 “Accreditation Recommendations” which will be written 644 by the Government. 645

3.1.2.5 System/Subsystem Specification (A-Specification) 646

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

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

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

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

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

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

A006), ATIP (CDRL A007), Human Engineering System Analysis Report (HESAR) 654

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

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

ATIP, HESAR, and SEMP. 658

The A-Specification shall address two EASR configurations: Variant 1, a single-face 659 array with rotating positioner to provide SPS-48 and SPS-49 capabilities for installation 660 on Amphibious Warfare Ships, and Variant 2, a three-face fixed array design slated for 661

Aircraft Carriers. 662

3.1.2.6 System Architecture 663

The Contractor shall generate and maintain a Systems Architecture Document (CDRL 664

A014). The Systems Architecture Document shall contain the architecture products that 665 describe the functional allocation consistent with the EASR SRD and EASR A-666

Specification (CDRL A013). These architecture products shall provide the context, 667 operation, functions, interfaces and activities of EASR. Context for EASR and CS/ATC 668 operation, functionality, interfaces and activity shall be included. The Contractor shall 669 develop these architecture products using Unified Modeling Language / System 670

Modeling Language (UML/SysML), Department of Defense Architecture Framework 671

(DoDAF), or other Government approved Contractor formats. 672

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

a. Complete description of all operational activities; 678

b. Mapping of operational activities to subsystem; 679

c. Allocation of functions to congifuration items; 680

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

e. Identification of parallelism or sequential operation; 683

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

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

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

3.1.2.7 Concept of Operations Document 689

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

(CDRL A015) document that describes the operation of EASRe and captures the 691

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

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

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

c. Description of waveforms, processing algorithms to be used and associated 697 rationale; and 698

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

3.1.2.8 Hardware Specification (B2-Specification) 700

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

Specifications) (CDRL A016) for each hardware CI. The Contractor shall maintain a 702 traceability matrix for each B2-Specification that indicates the source of each 703 requirement from the A-Specifications (CDRLs A013) and shall include these matrices 704 with rationale as part of each respective B2-Specification. The Contractor shall also 705 provide analyses to verify the flow-down of requirements from the A-Specifications to 706 the B2-Specifications for each CI. 707

3.1.2.9 Software Requirements Specification (B5-Specification) 708

The Contractor shall generate and maintain EASR Software Requirements Specifications 709

(SRSs) (B5-Specifications) (CDRL A017) for each software CI. The Contractor shall 710 maintain a traceability matrix with rationale for each B5-Specification that indicates the 711 source of each requirement from the A-Specifications (CDRL A013) and shall include 712 these matrices as part of each respective B5-Specification. The Contractor shall also 713 provide analyses to verify the flow-down of requirements from the A-Specifications to 714 the B5-Specifications for each CI. The Contractor shall also identify the associated 715 software Build (from the approved SDP (CDRL A050)) and associated Build Function 716 for each B-5 requirement. 717

3.1.2.10 Interface Specifications 718

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

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

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

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

Internal IRS requirement. 724

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

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

The Contractor shall generate and maintain an EASR External (Logical) IRS (EASR/CS, 728

EASR/Electronic Warfare System, EASR/ATC, and EASR/Missiles) (CDRL A021). 729

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

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

Weapon Specification (WS) 23302G, 35556, and WS 35569 are available for guidance. 732

The Contractor shall participate in the C/ATIWG to further refine these interfaces. This 733

IRS shall be used by the Contractor for implementing all EASR external interfaces. 734

The Contractor shall provide a copy of all IRSs in its Technical Data Package (TDP) 735

(CDRL A045). 736

3.1.2.11 System/Subsystem Design Description (SSDD) 737

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

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

Production. 745

3.1.2.12 Software Design Description (SDD) 746

The Contractor shall document the software design in an EASR Software Design 747

Descriptions (SDDs) (CDRL A023).