2015_10_02_1020_EASR_J-01_SOW_REDLINE.pdf

Attachment J-01 EASR SOW 2015-0710-31 02 16461020

SOURCE SELECTION INFORMATION SEE FAR 2.101 AND 3.104

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 ........................................................................... 525251 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)) ..................................................................... 595958 45

3.3.1 Production General Requirements ........................................................ 595958 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) ... 686867 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

707069 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

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

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

3.1.1 EMD Overview 321

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

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

3.1.2 Systems Engineering 328

3.1.2.1 System Engineering Technical Reviews (SETRs) 329

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

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

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

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

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

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

Development Plan (SDP) (CDRL A050A050A050), chaired by the Government 338

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

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

Government 341

g. Transition CDR, chaired by the Government 342

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

a. Elevation Coverage, 375

b. Ancillary Functions, and 376

c. Mulit-Mission Resource Loading 377

3.1.2.2 Systems Engineering Management 378

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

3.1.2.2.1 Systems Engineering Planning and Execution 380

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

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

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

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

3.1.2.2.2 Integrated Product and Process Development 389

The Contractor shall form Integrated Product Teams (IPTs) and Working Groups (WGs) 390 to support an integrated product development process. The Contractor shall generate the 391 organizational structure and document it in the SEMP (CDRL A004A004A004). The 392

Government will assign representatives to participate in IPT/WG meetings as necessary. 393

Government participation will be coordinated through the Contracting Officer’s 394

Representative (COR). 395

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

Meeting Agendas (CDRL A001A001A001) on the Government IDE prior to meetings. 398

The Contractor shall post Presentation Materials (CDRL A002A002A002) and Action 399

Items (CDRL A003A003A003) on the Government IDE. 400

The Contractor shall participate in the following Government / Industry Teams 401 established by the Government. 402

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

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

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

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

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

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

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

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

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

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

These Government / Industry Teams will include members from Navy and other industry 433 partners. 434

3.1.2.2.3 Modeling and Simulation Plan 435

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

(M&S) Plan as part of the SEMP (CDRL A004A004A004). DoD Modeling and 437

Simulation for the Acquisition Workforce, Version 1.0.1, dated October 2008, is 438 available as guidance. The M&S Plan shall address the development of Models & 439

Simulations (CDRL A008A008A008) for all EASR Variants and the use of Models & 440

Simulations through Production. The M&S Plan shall identify the Models and 441

Simulations to be delivered to the Government. The identified Models & Simulations 442 shall provide the Government with a high-fidelity capability to represent EASR 443 performance, including 1) Active array antenna performance, 2) Intentional and spurious 444 harmonic electromagnetic emissions, 3) Adaptive processing, 4) Multi-mission 445 scheduling, 5) Anti-Air Warfare (AAW), 6) (ATC), and 7) system power interface. All 446

M&S used to support System/Subsystem Testing, LBTS Testing, and Operational Testing 447 shall also be identified in the M&S Plan and delivered to the Government. The M&S 448

Plan shall describe the intended use of all M&S used in System/Subsystem Testing, 449

LBTS Testing, and Operational Testing. The Government will accredit M&S prior to use 450 during System/Subsystem, LBTS Testing, and Operational Testing. The M&S Plan shall 451 document the development plans and incremental build delivery schedule for each Model 452

& Simulation, and specify the level of capability for each of these incremental deliveries. 453

The M&S Plan shall describe the computing environment necessary for each Model & 454

Simulation such that delivered code can be hosted and run at equivalently configured 455

Government computing sites. The M&S Plan shall describe the integration of lower level 456 component models into higher level simulations, the interfaces, and input data 457 requirements for these, and how these models will be used to evaluate overall system 458 level performance. The M&S Plan shall describe how the EASR system will be 459 integrated and used with Models & Simulations for design, evaluation, and test. The 460

M&S Plan shall identify those models to be used to process data extracted from the 461

EASR system and how these models will be used in design, evaluation, and test 462 activities. The M&S Plan shall document the configuration management, interactions 463 and dependencies, and verification, validation, and accreditation (VV&A) of Models & 464

Simulations. 465

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

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

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

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

d. Signal processor algorithm chain model; 476

e. Signal processor latency/throughput model; 477

f. Radar control and data processor timing model; 478

g. Threat models; 479 safeguards to protect any and all Government systems and data, to ensure the 559 confidentiality, integrity, availability, authentication, and non-repudiation of Government 560 data. This shall include provisions for personnel security, electronic security and 561 physical security. 562

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

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

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

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

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

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

a. Cybersecurity Control Requirements Traceability Matrix to include tailored-out 583 controls; 584

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

(SRG) and Security Checklists); 586

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

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

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

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

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

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

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

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

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

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

3.1.2.3.2 Anti Tamper 602

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

AAA007) for the EASR through production, in accordance with the EASR AT Process. 604

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

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

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

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

AT design. 615

The AT Plan shall include: 616

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

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

i. Identification vulnerabilities of CT in the system; 620

j. Attack tree analysis; 621

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

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

m. Anti-Tamper development schedule, including SETRs, TIMs, and verification and 624 validation schedule; 625

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

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

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

Engineering); 629

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

r. AT Verification and Validation Plan. 631 installation on Amphibious Warfare Ships, and Variant 2, a three-face fixed array design 672 slated for Aircraft Carriers. 673

3.1.2.6 System Architecture 674

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

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

A013A013A013). These architecture products shall provide the context, operation, 678 functions, interfaces and activities of EASR. Context for EASR and CS/ATC operation, 679 functionality, interfaces and activity shall be included. The Contractor shall develop these 680 architecture products using Unified Modeling Language / System Modeling Language 681

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

Government approved Contractor formats. 683

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

a. Complete description of all operational activities; 689

b. Mapping of operational activities to subsystem; 690

c. Allocation of functions to configuration items; 691

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

e. Identification of parallelism or sequential operation; 694

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

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

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

3.1.2.7 Concept of Operations Document 700

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

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

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

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

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

c. Description of waveforms, processing algorithms to be used and associated 708 rationale; and 709

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

3.1.2.8 Hardware Specification (B2-Specification) 711

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

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

Specifications to the B2-Specifications for each CI. 718

3.1.2.9 Software Requirements Specification (B5-Specification) 719

The Contractor shall generate and maintain EASR Software Requirements Specifications 720

(SRSs) (B5-Specifications) (CDRL A017) for each software CI. The Contractor shall 721 maintain a traceability matrix with rationale for each B5-Specification that indicates the 722 source of each requirement from the EASR A-Specification (CDRL A013A013A013) 723 and shall include these matrices as part of each respective B5-Specification. The 724

Contractor shall also provide analyses to verify the flow-down of requirements from the 725

A-Specifications to the B5-Specifications for each CI. The Contractor shall also identify 726 the associated software Build (from the approved SDP (CDRL A050A050A050)) and 727 associated Build Function for each B-5 requirement. 728

3.1.2.10 Interface Specifications 729

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

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

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

(from the approved SDP (CDRL A050A050A050)) and associated Build Function for 734 each Software Internal IRS requirement. 735

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

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

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

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

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

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

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

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

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

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

3.1.2.11 System/Subsystem Design Description (SSDD) 749

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

Design Descriptions (SSDDs) (CDRL A022). The SSDDs shall contain the detailed 751

A summary for each Build Function including agreements, actions, conclusions, and 792 supporting backup material. 793

3.1.2.13 Interface Design Description (IDD) 794

The Contractor shall document the internal hardware interface design in an EASR 795

Internal Interface Design Description (IDD) (Hardware) (CDRL A026). The Contractor 796 shall document the internal software interface design in an EASR Interface Design 797

Description (IDD) (Software) (CDRL A027). 798

The Contractor shall generate the EASR External (Logical) IDD (CDRL A028). The 799

EASR External (Logical) IDD shall address the interfaces between EASR/CS, 800

EASR/Electronic Warfare System, EASR/ATC, and EASR/Missiles. The Contractor 801 shall participate in the CS/ATCIWG to further refine these interfaces. 802

The Contractor shall generate an EASR Product Line Data Model (PLDM) (CDRL 803

A029) for the interfaces between EASR and the CS. This shall include creating and 804 delivering the Unified Modeling Language (UML) model. The EASR PLDM shall be 805 used in generating and delivering the EASR External (Logical) IDD and the EASR 806

External (Logical) Interface Description Language (IDL) (CDRL A030). 807

Starting the month after SRR/SFR until finalized, the Contractor shall conduct monthly 808 reviews with the Government at the Contractor’s facilities to review progress of the 809

PLDM, IDD, and IDL. 810

3.1.2.14 Interface Control Document 811

The Contractor shall generate and maintain the EASR Interface Control Document (ICD) 812

(HM&E) (CDRL A031) documenting the interfaces for Variants 1 and 2, including 813 subsystem to subsystem cable runs external to the system. The Contractor shall work 814 with the RSIWG to refine these interfaces. The Contractor shall use this ICD to 815 implement EASR to HM&E interfaces. 816

3.1.2.15 Combat System/ATC and Ship Integration 817

The Contractor shall work with the CS/ATCIWG during EMD phase to refine the EASR 818

CS, CEC, and ATC interfaces. In addition, the Contractor shall perform trade studies and 819 analysis in support of the CS/ATCIWG and document the results in the EDN (CDRL 820

A046A046A046). 821

The Contractor shall work with the RSIWG during EMD phase to refine the EASR ship 822 interfaces for Variants 1 and 2 on multiple ship classes to include Amphibious Ships and 823

Aircraft Carriers. Through the RSIWG, the Contractor shall develop a Ship Integration 824

Plan (CDRL A032) for EASR Variants 1 and 2 that defines the requirements and 825 responsibilities to install and check-out the equipment. The Ship Integration Plan shall 826 include radar system equipment list, radar equipment installation requirements, 827 environmental requirements, definitions of the Installation and Checkout Kits, and an 828 installation concept. 829

In addition, the Contractor shall maintain estimates for specific items that are included in 830 ship’s budgets, but are directly impacted by the EASR design. These items include 831 weights of piping from the EASR Cooling Equipment Units (CEUs) to array spaces, 832 weights of DC power cables, weight of additional ship structure necessary for deckhouse 833 interface to arrays, and weight of spares required to meet performance requirements. The 834

Contractor shall include these estimates in the EDN (CDRL A046A046A046). 835

3.1.2.16 System Display and Control (SDC) 836

In order to support testing, the Contractor shall develop and deliver System Display and 837

Control (SDC) Software (CDRL A033) and Hardware that communicates directly with 838 the EASR system to display all published data and provide all functions necessary to 839 operate and test the system without the combat system present. The development of the 840

SDC Software shall follow the same processes and procedures for development and 841 verification of tactical code that are defined in the SDP (CDRL A050A050A050). The 842

SDC shall provide all operational, engineering and maintenance displays and controls 843 that are necessary for LBTS Testing, including the ability to perform individual 844 waveform control and all of the tools necessary to generate simulated target injection 845 scenarios. The SDC shall be developed using the open system practices defined in this 846

SOW (Section 3.1.2.24 and subsections). Communication between the SDC and the 847

EASR system shall use the interfaces as defined in the EASR External (Logical) IRS 848

(CDRL A021A021A021). All Graphical User Interface (GUI) display and control 849 functionality shall be based on industry best practices. 850

The Contractor shall generate and maintain a Local Control Software Module (LCSM) as 851 part of SDC Software. The LCSM shall be tactical software that is separable and 852 modular. The LCSM will be hosted external to the EASR data/control processor in a 853 future militarized shipboard console. 854

The Contractor shall generate and maintain a SDC SSS (A-Specification), (CDRL A034). 855

The Contractor shall perform required system engineering studies and analysis to develop 856 the SDC A-Specification. 857

The Contractor shall generate and maintain an SDC Specification (B2-Specification) 858

(CDRL A035) and Local Control Software Module SRS (B5-Specification) (CDRL 859

A036). The Contractor shall maintain a traceability matrix with rationale for each 860

B2/B5-Specification that indicates the source of each requirement from the SDC A-861

Specification and shall include these matrices as part of the B2/B5-Specification. The 862

Contractor shall also provide analyses to verify the flow-down of requirements from the 863

SDC A-Specification to the B2/B5-Specifications for each CI. The Contractor shall also 864 identify the associated software Build (from the approved SDP (CDRL A050A050A050)) 865 and associated Build Function for each SDC B5 requirement. 866

The Contractor shall deliver the SDC Software as executable and source code to include 867 any supporting configuration files and data libraries. The Contractor shall ensure that 868 source code is documented to permit validation with software design documentation. 869

3.1.2.17 Drawings/Models and Associated Lists 870

The Contractor shall generate a set of EASR Product Drawings/Models and Associated 871

Lists (CDRL A037), Commercial Drawings/Models and Associated Lists (CDRL A038), 872

Special Inspection Equipment (SIE) Drawings/Models and Associated Lists (CDRL 873

A039) and Special Tooling (ST) Drawings/Models and Associated Lists (CDRL A040) in 874 accordance with MIL-STD-31000A to support the fabrication, coding, integration and 875 testing of the subsystems, Lowest Replaceable Units (LRUs), software, firmware, and 876 overall EASR. 877

In support of drawings/models development, the Contractor shall generate and maintain 878

EASR Source Control Drawing Approval Requests (CDRL A041), Drawing Number 879

Assignment Reports (CDRL A042), and Proposed Critical Manufacturing Process 880

Descriptions (CDRL A043) in accordance with MIL-STD-31000A to support the 881 fabrication, coding, integration and testing of the subsystems, LRUs. software, firmware 882 and overall EASR. 883

3.1.2.18 LRU Documentation 884

The Contractor shall generate an EASR LRU Description Document (CDRL A044). The 885

LRU Description Document shall be a stand-alone document containing all drawings and 886 documentation required to reproduce, test, qualify and repair each non-COTS LRU. The 887

EASR LRU Description Document shall include the following for each LRU: 888

Mechanical, electrical and cooling interface design; 889

Functional interface design; 890

Functional description; 891

Qualification Provisions; 892

Repair procedures; and 893

Associated TDP information. 894

3.1.2.19 Technical Data Package 895

The Contractor shall maintain a TDP (CDRL A045) for EASR, as defined in the CDRLs 896

(Block C/Category TDP). 897

3.1.2.20 Engineering Design Notebook 898

The Contractor shall maintain an Engineering Design Notebook (EDN) (CDRL A046) 899 which includes technical documents not specifically covered in other CDRLs that are 900 produced in the course of the work on this contract. The Contractor shall document the 901 rationale for design decisions. The Engineering Design Notebook is a compendium of 902 working-level documents normally produced in support of the Contractor’s system design 903 definition efforts. Examples of the types of documents within the notebook include, but 904 are not limited to: analyses, trade study reports generated during this contract and studies 905 conducted on the existing radar system or systems from which the EASR design is 906 derived, technical memoranda, back-up data for presentation material, and subcontractor 907 or third party selection criteria. The EDN and its index shall be maintained on the 908

Government IDE and updated monthly. Access to working level documentation 909 identified during IPT/WG participation shall be provided in the EDN. 910

3.1.2.21 Total Ownership Cost (TOC) 911

The intent of TOC is to ensure that a highly capable system is affordable. By designing 912 to TOC, both the Contractor and the Government Team can understand cost implications 913 of EASR A-Specification (CDRL A013A013A013) requirements and associated design 914 decisions and thereby minimize life cycle cost while achieving the program’s objectives. 915

The Contractor shall generate and maintain an EASR TOC Model (CDRL A047) that 916 will be used for system design trades. The model shall include all development, 917 production, operations and sustainment, and disposal Contractor costs. The TOC model 918 shall include costs for all equipment. The Contractor shall include Hazardous Material 919

Management impact inputs to the TOC model. For Operations and Support (O&S), the 920

Contractor shall provide LRU unit cost estimates based on vendor input or bottoms up 921 engineering analysis. The Contractor shall provide LRU repair cost estimates based on 922 vendor data for COTS equipment and material and labor costs for developmental items. 923

The Contractor shall use the Reliability, Availability, Maintainability, and Support Cost 924

(RAMSC) Model (CDRL A097A097A097) for O&S cost inputs. The Contractor shall 925 separately identify impacts to the ship and combat system, e.g., maintenance personnel, 926 overall efficiency and coolant temperature. The Government will provide top-level 927 assumptions for the TOC Model as J-20. The Contractor shall work with the 928

Government team within the CAWG in order to establish an agreed-to set of assumptions 929 included in the model. The model shall follow the approved Contract Work Breakdown 930

Structure (CWBS) (CDRL A131). 931

In addition, applicable data shall be reflected in the TOC models to project production 932 unit cost by CWBS for each unit. The cost shall be broken down to the LRUs even if that 933 is below the level of the CWBS. 934

3.1.2.22 Manufacturing Planning 935

3.1.2.22.1 EMD Manufacturing Plan 936

The Contractor shall generate and execute an EASR EMD Phase Manufacturing Plan 937

(CDRL A048). The Manufacturing Plan shall document methods by which the design is 938 to be built. The Manufacturing Plan shall contain sequence and schedule of events at 939 contractor and subcontractor levels that define use of materials, fabrications flow, test 940 equipment, tools, facilities, throughput rates and personnel.