EWPMT_PBS_(DRAFT)_03JUN12.pdf

UNCLASSIFIED//FOUO

PERFORMANCE BASED SPECIFICATION – GOVERNMENT (PBS-G) 7

FOR THE 8

INTEGRATED ELECTRONIC WARFARE SYSTEM (IEWS) 9

ELECTRONIC WARFARE PLANNING AND MANAGEMENT TOOL (EWPMT) 10

Prepared for: 12

Prepared by: 14

Project Manager Electronic Warfare 15

Building 4117 16

Aberdeen Proving Grounds, MD 17

Contents 18

1 Scope ............................................................................................................................................. 4 19

1.1 Scope ..................................................................................................................................... 4 20

1.2 System Overview ................................................................................................................... 5 21

2 Applicable Documents .................................................................................................................. 5 22

2.1 General .................................................................................................................................. 5 23

2.2 Government Documents ....................................................................................................... 6 24

2.2.1 Specifications, Standards, and Handbooks ....................................................................... 6 25

2.2.2 Other Government Documents, Drawings, and Publications ........................................... 6 26

2.3 Non-Government Publications ............................................................................................. 7 27

2.4 Order of Precedence ............................................................................................................. 7 28

3 Requirements ................................................................................................................................ 7 29

3.1 System Performance Characteristics .................................................................................... 8 30

3.1.1 Command Post Integration ............................................................................................... 8 31

3.1.2 Electronic Warfare Message Format Interface (EW-MFI) ................................................. 9 32

3.1.3 Data Import ....................................................................................................................... 9 33

3.1.4 Compute .......................................................................................................................... 21 34

3.1.5 Archive ............................................................................................................................ 27 35

3.1.6 Interact with Operator .................................................................................................... 28 36

3.1.7 Interface .......................................................................................................................... 29 37

3.1.8 Manage ........................................................................................................................... 31 38

3.1.9 Export Data ..................................................................................................................... 32 39

3.1.10 Display Data ................................................................................................................ 33 40

3.2 Training ............................................................................................................................... 35 41

3.2.1 Facilitate EW Staff Training ............................................................................................. 36 42

3.2.2 EWPMT Training Help Tool ............................................................................................. 36 43

3.3 Information Assurance ........................................................................................................ 36 44

3.3.1 User Security ................................................................................................................... 36 45

3.3.2 EWPMT Classified Information ....................................................................................... 36 46

3.4 Other System Attributes ..................................................................................................... 37 47

3.4.1 System Safety .................................................................................................................. 37 48

3.4.2 Maintenance and Support .............................................................................................. 37 49

3.4.3 Expected Mission Capabilities ......................................................................................... 37 50

3.4.4 Technical Data ................................................................................................................. 37 51

3.4.5 Human Factors Engineering ............................................................................................ 38 52

4 Verification .................................................................................................................................. 38 53

4.1 Classification of Design Verification Methods .................................................................... 38 54

4.2 Verification Conditions ........................................................................................................ 39 55

4.3 Requirements Verification Matrix....................................................................................... 39 56

5 Packaging .................................................................................................................................... 50 57

5.1 Packaging ............................................................................................................................ 50 58

6 Notes ........................................................................................................................................... 51 59

6.1 Potential EWPMT Architecture ........................................................................................... 51 60

6.2 Definitions ........................................................................................................................... 51 61

6.3 Acronyms ............................................................................................................................ 52 62

1 Scope 66

1.1 Scope 67

This specification covers the Electronic Warfare Planning and Management Tool (EWPMT) for the 68

Integrated Electronic Warfare System (IEWS). IEWS will provide commanders from Corps to Company 69 focusing on the Brigade Combat Team (BCT) with an organic EW capability that dramatically improves a 70 land force’s ability to seize, retain, and exploit an advantage within the electromagnetic spectrum (EMS) 71 in order to execute decisive operations successfully. EWPMT will provide the Electronic Warfare Officer 72

(EWO) with a mission command capability to plan, coordinate, manage, and deconflict unit EW activities 73 in support of maneuver operations from the Corps down to the Company echelon. 74

The EWPMT is a software system that will be instantiated as a set of services to be run within the 75

Command Post Computing Environment (CPCE) and one or more presentation-layer widgets to be run 76 on a thin client laptop. This specification covers EWPMT Increment 1 focusing on Capability Drops (CD) 77

1 and 2. The EWPMT Increment 1 is divided into six CDs as follows: 78

(1) Capability Drop 1. EWPMT CD 1 will provide software that integrates data for friendly, 79 enemy, and non-aligned emitters and provide for the planning and management of EW capabilities 80 across the range of military operations. EW personnel will use EWPMT to provide input to the 81 operations process via the detailed information on EW effects that it provides within the operational 82 environment. This CD will reduce the risk of frequency fratricide by identifying potential frequency 83 conflicts between friendly systems. EWPMT CD 1 will focus on the development effort from Systems 84

Requirements Review through the Critical Design Review. CD 1 will result in a Limited Deployment 85 leading to a Milestone C decision and approval of an Initial Operational Capability (IOC). 86

(2) Capability Drops 2-6. Future capability drops will: 1) graphically display friendly emitter 88 interference, disruption, and degradation and allow EW personnel to determine the proper program EW 89 technique for EW systems 2) allow EW personnel to transfer control of the EW mission resources to any 90 echelon in order to provide backup support 3) provide the capability to conduct post mission analysis 91 that will aid in determining mission accomplishment 4) provide the capability to rapidly reconfigure 92 organic EW assets 5) provide reprogramming of organic EW assets and the ability to provide immediate 93 targeting information to fires and maneuver elements. 94

(3) All future capabilities will be based on evolving requirements, established through the GOSC, 96 and documented in future documentation. 97

Specific functions within CDs 3-6 are subject to change, but the overall system is expected to 99 implement all of the above functions by the end of drop 6. Requirements specific to drops 1 and 2 are 100 detailed in the following sections. Requirements that do not indicate a specific drop are anticipated to 101 be implemented within CDs 3-6. 102

1.2 System Overview 103

EWPMT is a part of a Family of Systems called IEWS. IEWS is a family of distributed, modular and 104 configurable systems focusing on the BCT that functionally exploits the electromagnetic spectrum 105 through a variety of offensive, defensive, and enabling capabilities to achieve the commander’s intent. 106

The IEWS is required to address the current and anticipated deficiencies in EW warfighting capabilities. 107

IEWS will mitigate these current and emerging risks to ground forces, increase situational awareness on 108 the battlefield, strengthen force protection, and provide increased options to the warfighter. IEWS will 109 integrate existing capabilities and provide new EW capabilities to the Army. IEWS will be developed 110 along three lines of effort, which are EWPMT, Multi-Function EW (MFEW) and Defensive EA (DEA). 111

Building blocks of IEWS will be modular, scalable and interoperable to allow system growth in responses 112 to a variety of threats and scenarios. 113

The proliferation of EW technologies worldwide and the ease, with which they are acquired, 114 necessitates EW as a core capability in the Army. In order to provide an EW capability across the force it 115 is necessary to first develop the framework to integrate all future capabilities into a networked, modular 116 system that is achievable and affordable. Electronic Warfare Planning and Management Tool (EWPMT) 117 is the framework that coherently incorporates EW into full spectrum operations. Given an ever 118 changing and electromagnetic rich target environment, the Army requires mission planning capabilities 119 to ensure it develops timely and effective plans. 120

EWPMT relies on a capability drop approach that utilizes fielded and emerging EW platforms, 121 communication system technologies and architectures, and space-based systems. These systems will 122 virtually interconnect through networks to maximize Army EW capabilities. EWPMT will seamlessly 123 exchange information horizontally and vertically between service and joint mission partners. EWPMT 124 will be adaptable enough to be accessed from all echelons as well as the Global information Grid at the 125

Secret. EWPMT supports several warfighting functions in order to support EW missions and tasks at the 126 operation and tactical levels of command within the current and future force. 127

EWPMT is software giving EWOs a mission planning capability to plan, coordinate, manage, and 128 deconflict unit EW activities. It will provide battle management for distributed, networked EW 129 capability, aligned with fires and synchronize air and ground electromagnetic spectrum operations 130 across the G2/3/6. EWPMT capabilities include producing EW orders and estimates, plan and 131 appropriately employ EW assets, conduct effective EW targeting using lethal and non-lethal fires 132 support; enhance development of the Electronic Order of Battle; and conduct EW battle damage 133 assessment. EMPMT will provide a risk assessment and Course of Action (COA) development for EW 134 missions with all software applications and tools being hosted on existing CPCE servers. 135

2 Applicable Documents 136

2.1 General 137

The documents listed in this section are cited in sections 3, 4, or 5 of this specification. This section 138 does not include documents cited in other sections of this specification or recommended for additional 139 information or as examples. While every effort has been made to ensure the completeness of this list, 140 document users are cautioned that they must meet all specified requirements of documents in sections 141

3, 4, or 5 of this specification, whether or not they are listed here. 142

2.2 Government Documents 143

2.2.1 Specifications, Standards, and Handbooks 144

The following specifications, standards, and handbooks form a part of this document to the extent 145 specified herein. Unless otherwise specified, the issues of these documents are those cited in the 146 solicitation or contract. 147

DEPARTMENT OF DEFENSE SPECIFICATIONS 148

MIL-PRF-89020B Digital Terrain Elevation Data, May 2000 149

MIL-STD-2361C Digital Publications Development, July 2010 150

MIL-STD-6040B U.S. Message text Format Description, August 2009 151

MIL-STD-40051-1 Preparation of Digital Technical Information for Interactive 152

Electronic Technical Manuals, October 2004 153

DEPARTMENT OF DEFENSE INSTRUCTION 154

DoDI 8520.02 Public Key Infrastructure and Public Key Enabling, May 2011 155

DEPARTMENT OF DEFENSE DIRECTIVES 156

DoDD 8500.01E Information Assurance, April 2007 157

2.2.2 Other Government Documents, Drawings, and Publications 158

The following other Government documents, drawings, and publications form a part of this 159 document to the extent specified herein. Unless otherwise specified, the issues of these documents are 160 those cited in the solicitation or contract. 161

CHAIRMAN OF THE JOINT CHIEFS of STAFF 162

CJCSI 6212.01F Interoperability and Supportability of Information Technology 163 and National Security Systems, March 2012 164

MCEB PUB 7 Military Communications Electronic Board Publication 7, 165

December 2003 166

MCEB PUB 8 Military Communications Electronic Board Publication 8, March 167

2009 168

DEPARTMENT OF THE ARMY 169

AR 25-2 Information Assurance, March 2009 170

FM 3-09.32 Multi-Service Tactics, Techniques, and Procedures for the Joint 171

Application of Firepower, December 2007 172

FM 3-36 Electronic Warfare in Operations, February 2009 173

ASSISTANT SECRETARY OF THE ARMY 174

COE Implementation Common Operating Environment Implementation Plan Core 175

Version 3.0, November 2011 176

UNITED STATES ARMY CHIEF INFORMATION OFFICE 177

COE Architecture Guidance for End State Army Enterprise Network Version 2.0 178

Appendix C, October 2010 179

INTELLIGENCE & INFORMATION WARFARE DIRECTORATE 180

I2WD IS V1.3 IRON Symphony EW Network Protocol Specification Version 1.3 181

PROJECT MANAGER BATTLE COMMAND 182

Command Web BC 13.0.1/13.02 Command Web Widget Developer Guide, January 2012 183

DDS CONOPS Data Dissemination Services Concept of Operations, January 184

2008 185

2.3 Non-Government Publications 186

The following documents form a part of this document to the extent specified herein. Unless 187 otherwise specified, the issues of these documents are those cited in the solicitation or contract. 188

RAYTHEON COMPANY 189

DCGA-A V3 DCGS-A Ozone Widget Developer’s Guidance Version 3.0, 2010 190

2.4 Order of Precedence 191

In the event of a conflict between the text of this document and the references cited herein, the 192 text of this document takes precedence unless otherwise noted. 193

3 Requirements 194

The following requirements detail a set of performance characteristics and functions that must be 195 employed by EWPMT Increment 1 CDs 1-6. In addition, requirement paragraphs comprising EWPMT 196

Increment CDs 1 and 2 are labeled at the end of the paragraph. Requirements are denoted by ‘shall’ 197 statements and are typically found at the lowest hierarchical level of the outline of this section; other 198 statements are intended for informational purposes only. For a possible architecture view within which 199 these functions might operate, see Section 6.1. 200

3.1 System Performance Characteristics 201

3.1.1 Command Post Integration 202

3.1.1.1 CPCE Standardized Hardware and Command Software 203

The EWPMT shall operate on the Local Area Network (LAN) as a virtual machine hosted on server 204 stacks provided by CPCE. In addition, EWPMT shall maximize the use of standardized hardware and 205 common software components used in the CPCE including the Tactical Mission Command (TMC) Rich 206

Web Client Profile to support the seamless integration of EW capability. CPCE will throughout the 207 document refer to CPCE Version 2. (CD 1) 208

3.1.1.1.1 Common Operating Environment 209

When unable to use standardized hardware and common software components of the CPCE, 210

EWPMT shall comply with common operating environment (COE) standards for hardware and software. 211

(COE Architecture) (CD 1) 212

3.1.1.1.2 Ozone Widget Framework (OWF) 213

The EWPMT Web-based User Interface (UI) design and implementation shall be based on the 214 versions of OWF and Inter-Widget Communications Framework included in CPCE. (Command Web BC 215

13.0.1/13.02) (CD 1) 216

3.1.1.1.2.1 Common Widgets 217

The EWPMT Web-based UI implementation shall re-use the Common Widgets available in the 218

CPCE. (CD 1) 219

3.1.1.1.3 Data Dissemination Service (DDS) Integration 220

The EWPMT shall interoperate with DDS, and at a minimum be compliant with CPCE DDS schemas. 221

Additional DDS information is described in Sections 3.1.3.2.2.2 and 3.1.7.3.2. (DDS CONOPS) (CD 1) 222

3.1.1.1.4 Minimum Server Performance 223

3.1.1.1.4.1 Processors 224

The EWPMT shall operate with a minimum of four core processors operating at 3.3 GHz. (CD 1) 225

3.1.1.1.4.2 Random Access Memory (RAM) 226

The EWPMT shall operate with a minimum of 16 Gigabits (GB) of RAM. (CD 1) 227

3.1.1.1.4.3 Available Storage 228

The EWPMT shall have access to a maximum of 900 GB of useable storage space. (CD 1) 229

3.1.1.2 Modular Open System Approach (MOSA) 230

Within the constraints of CPCE and COE, the EWPMT overall design shall be a framework that 231 supports future extension of core capabilities with new and improved propagation models, EW asset, 232

EW threat, and dynamical reprogramming of EW equipment in an open modular approach. (CD 1) 233

3.1.2 Electronic Warfare Message Format Interface (EW-MFI) 234

The EWPMT shall utilize the EW-Message Format Interface to communicate between separate 235 control nodes and workstations as well as for communications with EW assets. (I2WD IS V1.3) (CD 1) 236

3.1.2.1 EW-MFI Registry Service 237

The EWPMT shall implement the EW registry node for local and potential enterprise deployment 238 within the CPCE. EWPMT shall support communications and coordination with the EW registry node. 239

This is a node supporting the EW registry service that collects the identification information associated 240 with EW nodes and EW Services by means of advertisement and discovery protocol exchanges, and also 241 responds to queries about the collected information. The registry also defines the hierarchy of 242 precedence of authority for individual nodes, as well as node associations. (CD 1) 243

3.1.2.2 EW-MFI Future Growth 244

The EWPMT shall support the fielding of the new capability for controlling different EW assets 245 utilizing the EW-MFI in a manner with minimal impact on the operation of existing EWPMT systems in 246 the field. 247

3.1.2.3 EW-MFI EW Information Transfer 248

The EWPMT shall support transfer of EW information communicated over the EW-MFI including 249

EW asset information such as reporting the detection and characteristics of Signals of Interest (SOIs). 250

(CD 1) 251

3.1.3 Data Import 252

3.1.3.1 Environment Data 253

3.1.3.1.1 Terrain Data 254

The EWPMT will have the capability to import global terrain digital elevation models (DEM), terrain 255 imagery data, terrain map data, and urban terrain data. It is anticipated that the primary source of this 256 data will be National Geospatial-Intelligence Agency (NGA) data products. The terrain data will be used 257 for the purposes of radio frequency (RF) propagation computations and terrain/situational awareness 258 visualization. The EWPMT software will give the user the option to use DEM data in RF propagation loss 259 computations that model the effects of electromagnetic (EM) wave terrain blockage, EM terrain 260 diffraction, and earth reflected EM waves. 261

3.1.3.1.1.1 Import Digital Terrain Elevation Data (DTED) 262

The EWPMT shall have the capability to import DTED for level 0, 1, and 2 formats as specified in 263

U.S. Military Specification Digital Terrain Elevation Data (DTED) MIL-PRF-89020B. The EWPMT shall also 264 have the capability to import level 3 DTED from specific databases as designated by the government. 265

(CD 1) 266

3.1.3.1.1.2 Light Detection and Ranging (LIDAR) Data 267

The EWPMT shall have the capability to import LIDAR DEM data from NGA product library sources. 268

(CD 1) 269

3.1.3.1.1.3 Terrain Imagery and Map Data 270

The EWPMT shall have the capability to import terrain imagery and map data. (CD 2) 271

3.1.3.1.1.4 Environment Types 272

The EWPMT shall have the capability to import geospatial data for urban, rural, mountainous, 273 desert, coastal and heavy vegetation environments. (CD 1) 274

3.1.3.1.2 Weather Data 275

The EWPMT will have the capability to import weather data for the purposes of extracting 276 parameters required for RF propagation computations and COA development. 277

3.1.3.1.2.1 Distributed Common Ground System – Army (DCGS-A) Weather Data 278

The EWPMT shall import weather data from DDS that is published by DCGS-A. The weather data 279 shall include but not be limited to temperature, precipitation and wind data which are required inputs 280 for operational planning and/or propagation modeling. (CD 1) 281

3.1.3.2 Operations Data 282

The EWPMT will have the capability to exchange data with the current versions of Mission 283

Command (MC) systems and spectrum data sources. 284

3.1.3.2.1 Electromagnetic Spectrum 285

The EWPMT will include software that exchanges data with key databases for friendly, enemy, and 286 non-aligned emitters and provides for: (1) importing spectrum plans directly from these databases; 287 and/or (2) providing for using the emitter spectrum information imported from these databases to 288 formulate or modify spectrum plans within the EWPMT. 289

3.1.3.2.1.1 Spectrum Knowledge Repository (SKR) 290

The EWPMT shall be capable of importing spectrum and Electromagnetic Operating Environment 291

(EMOE) data from the SKR in the Pub 7 Standard Spectrum Resource Format (SSRF); using an Open 292

Database Connectivity (ODBC) interface. The SKR includes spectrum information that is contained in the 293

International Telecommunication Union (ITU) records; the Government Master File (GMF) records; the 294

Joint Equipment, Tactical and Space (JETS) database; and the Army Reprogrammable Analysis Team 295

(ARAT) database. The EWPMT shall be capable of importing the SKR data from a local copy of the SKR 296 database that will reside on an SQL server located at the battalion (BN) and/or the Brigade Combat 297

Team (BCT) echelons; as well as be capable of importing a master copy of the SKR database from Joint 298

Spectrum Center (JSC) servers. (CD 1) 299

3.1.3.2.1.2 Spectrum XXI Online (SXXIO) 300

The EWPMT shall be capable of importing spectrum data using SXXIO web services. EWPMT shall 301 be able to interface with versions 2.0 through 4.0 of SXXIO. Information imported shall include 302 frequency assignment information, and the Joint Restricted Frequency List (JRFL). The EWPMT shall 303 import data from SXXIO using the Military Communications Electronics Board (MCEB) Pub 8 Standard 304

Spectrum Resource Format (SSRF). (CD 1) 305

3.1.3.2.1.3 Joint Spectrum Data Repository (JSDR) 306

The EWPMT shall be capable of importing spectrum data from the JSDR. The data shall be 307 imported in the MCEB Pub 8 SSRF. The JSDR will be included in the Global Electromagnetic Spectrum 308

Information System (GEMSIS) Increment 2. Direct on-line access to the JSDR will be available using the 309

JSC Data Access Web Server (JDAWS) tool. The JSDR will include the following databases: the JETS 310 database, the Background Environmental Information (BEI) database, the Government Master File 311

(GMF) database, the Frequency Resource Record System (FRRS) database, and the Electronic Order of 312

Battle (EOB) database. 313

3.1.3.2.1.4 DCGS-A 314

The EWPMT shall be interoperable with and able to import friendly, neutral, and enemy emitter 315 transmit frequency or spectrum data from DCGS-A. EWPMT shall be capable of importing this data in 316

DDS Extensible Markup language (XML) schema formats, via the DDS Web Services Description Language 317

(WSDL) interface. The EWPMT shall also be cable of importing DCGS-A information that is not available 318 through DDS, via the DCGS-A Integration Backbone (DIB). The DIB will allow access to the Tactical Entity 319

Database (TED). (DCGS-A V3) (CD 1) 320

3.1.3.2.1.5 ARAT 321

The EWPMT shall be capable of importing EW loadsets and software loader information from ARAT 322 website as a binary file via Hypertext Transfer Protocol Secure (HTTPS). (CD 1) 323

3.1.3.2.2 Target List 324

3.1.3.2.2.1 DCGS-A Target Information 326

The EWPMT shall be interoperable with and able to import enemy target information, including 327 target tracking information from DCGS-A. Enemy target information will include enemy asset location 328 and performance characteristics that will aid the EWO with formulating EA attack plans against the 329 target. The EWPMT shall be capable of importing the DCGS-A target information using the software 330 interface protocols and file format specifications described in Section 3.1.3.2.1.4. (CD 1) 331

3.1.3.2.2.2 Additional DDS Published Target Information 332

The EWPMT shall be capable of importing target information from systems that publish to DDS. 333

This shall include, but not be limited to, information published by Force XXI Battle Command Brigade 334 and Below (FBCB2), Global Command and Control System – Army (GCCS-A), Command Post of the 335

Future (CPOF), Air and Missile Defense Workstation (AMDWS), and Advanced Field Artillery Tactical Data 336

System (AFATDS). EWPMT shall be capable of importing this data in DDS XML schema formats, via the 337

DDS WSDL interface. (CD 1) 338

3.1.3.2.2.3 Joint Integrated Prioritized Target List (JIPTL) 339

The EWPMT shall have the capability to import the JIPTL via a XML schema using MIL-STD 6040B. 340

(CD 1) 341

3.1.3.2.3 Air Tasking Order 342

The EWPMT shall have the capability to import Air Tasking Orders (ATO) via a XML schema using 343

MIL-STD 6040B. (CD 1) 344

3.1.3.2.4 Maneuver Plans 345

The EWPMT shall have the capability for importing maneuver plans including Operation Orders in 346

MS Word format; Fragmentation Orders in MS Word format, and Common Operating Picture (COP) 347 overlays from DDS. DDS data shall be imported using the software interface protocols and file format 348 specifications described in Sections 3.1.3.2.2.2 and 3.1.7.3.2.3. (CD 1) 349

3.1.3.2.5 EW Request Forms from Lower and Adjacent Echelons 350

The EWPMT shall have the capability for importing EW request forms including Joint Tactical Air 351

Strike Request (JTASR) and Electronic Attack Request Form (EARF) using FM 3-09.32 format from lower 352 and adjacent echelons. (CD 1) 353

3.1.3.3 EW Asset Data 354

3.1.3.3.1 General Import Capability 355

The EWPMT will have the capability for importing EW asset data that includes the asset’s 356 position/location (this information shall include the asset’s antenna height, if applicable), system 357 capabilities, system RF parameters, availability information, status, and information on available EW 358 techniques. 359

3.1.3.3.2 Organic EW Asset Data 360

The EWPMT shall have the capability for interfacing with and importing organic EW asset data 361 through military networks using the EW-MFI. (CD 1) 362

3.1.3.3.3 DCGS-A Data 363

The EWPMT shall have the capability for importing EW asset data from the DCGS-A system using 364 software interface and file format specifications described in Section 3.1.3.2.1.4. (CD 1) 365

3.1.3.3.4 Army Reprogrammable and Analysis Team (ARAT) Database Data 366

The EWPMT shall have the capability for importing from the ARAT database asset EW technique 367 and corresponding emission masks information for each asset utilized in the mission. (CD 1) 368

3.1.3.3.5 SKR Data 369

The EWPMT shall have the capability for importing EW asset data from the SKR using the Pub 7 370

SSRF and Open Database Connectivity (ODBC) interface. This data shall include, but not be limited to, 371

EW asset position/location information and equipment/platform operating parameter information. (CD 372

1) 373

3.1.3.3.6 EW Asset Position Update 374

The EWPMT shall have the capability for importing near real-time EW asset position updates 375 including altitude from systems that publish to DDS; throughout the course of the mission. The DDS 376 information shall be imported using software interface and file format specifications as described in 377

Section 3.1.3.2.2.2 and 3.1.7.3.2.3. These systems include, but are not limited to, AFATDS, FBCB2, and 378

CPOF. (CD 1) 379

3.1.3.4 Friendly Asset Data 380

3.1.3.4.1 General Import Capability 381

The EWPMT will have the capability to import friendly asset position and parameter data from 382 databases and information sources that are accessible within the CPCE. 383

3.1.3.4.2 Asset Position/Location Import Capability 384

3.1.3.4.2.1 SKR Position Import Capability 385

The EWPMT shall have the capability for importing friendly asset position/location data (including 386 the asset’s antenna height, if applicable) that resides in the SKR, as inputted from the JETS database. 387

The EWPMT shall be capable of accessing this information using the Pub 7 SSRF and ODBC interface (CD 388

1) 389

3.1.3.4.2.2 JSDR Position Import Capability 390

The EWPMT shall be capable of importing position data from the JSDR. The data shall be imported 391 in the MCEB Pub 8 SSRF. Direct on-line access to the JSDR will be available using the JDAWS tool. The 392

JSDR will include friendly asset position data that resides in the JETS database. 393

3.1.3.4.2.3 DDS Position Import Capability 394

The EWPMT shall have the capability for importing friendly asset position/location data (including 395 the asset’s antenna height, if applicable) from systems that publish information using DDS. The 396 information shall be imported using the software interface and file format specifications described in 397

Sections 3.1.3.2.2.2 and 3.1.7.3.2.3. Information source systems shall include, but not be limited to, 398

AFATDS, FBCB2, CPOF, UASGCS, and AMDWS. (CD 1) 399

3.1.3.4.3 Asset Equipment Parameter Import Capability 400

3.1.3.4.3.1 SKR Asset Parameter Import Capability 401

The EWPMT shall have the capability for importing friendly asset performance parameter 402 information from the SKR using the Pub 7 Standard Spectrum Resource Format (SSRF) and Open 403

Database Connectivity (ODBC) interface. The parameter data consists of equipment and network 404 parameters that are inputted to the SKR from the JETS database. The asset parameters will include 405 parameters that define asset frequency use, antenna performance, transmitter performance, and 406 receiver performance. These parameters will be used for modeling and simulation purposes. (CD 1) 407

3.1.3.4.3.2 JSDR Asset Parameter Import Capability 408

The EWPMT shall be capable of importing equipment/platform parameter data from the JSDR. The 409 data shall be imported in the MCEB Pub 8 SSRF. Direct on-line access to the JSDR will be available using 410 the JDAWS tool. The JSDR will include friendly asset parameter data that resides in the JETS database. 411

The asset parameters will include parameters that define asset frequency use, antenna performance, 412 transmitter performance, and receiver performance. These parameters will be used for modeling and 413 simulation purposes. 414

3.1.3.5 Enemy Asset Data 415

3.1.3.5.1 General Import Capability 416

The EWPMT will have the capability to import enemy asset data from databases and information 417 sources that are accessible within the CPCE. Sources shall include, but are not limited to, systems that 418 publish information via DDS. 419

3.1.3.5.2 Enemy Asset Type 420

The EWPMT shall have the capability to import enemy asset type intelligence information from 421 sources that publish to DDS including, but not limited to, DCGS-A and FBCB2. The DDS information shall 422 be imported using the software interface and file format specifications described in Sections 3.1.3.2.2.2 423 and 3.1.7.3.2.3. The EWPMT shall also have the capability to import DCGS-A asset type information 424 using a DIB query as described in Section 3.1.3.2.1.4. Asset types will include radio nodes (transmit and 425 receive), RF broadcast nodes (transmit only), navigation receiver nodes (receive only), signals collection 426 sensors (receive only), radar sensors (transmit and receive), and EO/IR sensors (no RF functionality, for 427 visualization/SA only). (CD 1) 428

3.1.3.5.3 Enemy Asset Position Data 429

3.1.3.5.3.1 DDS Position Data 430

The EWPMT shall be capable of importing enemy asset position information (including antenna 431 height, if applicable) from systems that publish to DDS. These systems include, but are not limited to, 432

AFATDS, FBCB2, CPOF, and DCGS. The DDS information shall be imported using the software interface 433 and file format specifications described in Sections 3.1.3.2.2.2 and 3.1.7.3.2.3. (CD 1) 434

3.1.3.5.3.2 JSDR Position Data 435

The EWPMT shall be capable of importing enemy asset position information (including antenna 436 height, if applicable) from the JSDR. The JSDR information shall be imported using the software 437 interface and file format specifications described in Section 3.1.3.2.1.3. 438

3.1.3.5.3.3 Enemy Asset Position Update 439

The EWPMT shall have the capability for importing near real-time enemy asset position updates 440 including altitude from systems that publish to DDS; throughout the course of the mission. These 441 systems shall include, but not be limited to, DCGS-A and FBCB2. The DDS information shall be imported 442 using software interface and file format specifications as described in Sections 3.1.3.2.2.2 and 443

3.1.7.3.2.3. (CD 1) 444

3.1.3.5.3.4 Sensor Fused Enemy Position Data 445

The EWPMT shall be capable of importing sensor fused enemy position data. (CD 1) 446

3.1.3.5.4 Enemy Asset Dependency Information 447

The EWPMT shall have the capability of importing information for enemy assets that are dependent 448 on enemy RF operations (i.e. weapon systems). (CD 1) 449

3.1.3.5.5 Enemy Battle Damage Assessments (BDA) 450

The EWPMT shall be capable of importing Enemy BDA. 451

3.1.3.5.6 Enemy Emitter Parameters 452

The EWPMT shall be able to import enemy emitter equipment parameter information as specified 453 in the following sub-sections; as provided by available information sources during mission planning and 454 operations. Information sources shall include, but not be limited to, systems that publish to DDS 455

(primarily DCGS-A) and DCGS-A information that is available from the TED via a DIB query. It is 456 recognized that all the parameters listed may not always be available. The DDS and DIB information 457 shall be imported using software interface and file format specifications as described in Sections 458

3.1.3.2.2.2, 3.1.3.2.1.4, and 3.1.7.3.2.3. (CD 1) 459

3.1.3.5.6.1 Output Power 460

The EWPMT shall be able to import emitter RF output power level values; as a function of transmit 461 frequency and transmit mode. (CD 1) 462

3.1.3.5.6.2 Peak Antenna Gain 463

The EWPMT shall be able to import the emitter peak antenna gain values, as a function of 464 frequency. (CD 1) 465

3.1.3.5.6.3 Antenna Pointing Angle 466

If the emitter antenna has a fixed (stationary) pointing angle, the EWPMT shall be able to import 467 the azimuth and elevation angle values that define the pointing angle. If the emitter antenna scans in 468 elevation and/or azimuth; the EWPMT shall be able to import the rate-of-scan parameters and angular 469 region of scan information. (CD 1) 470

3.1.3.5.6.4 Peak Effective Radiated Power (ERP) 471

The EWPMT shall be able to import peak ERP values, as a function of frequency and operational 472 mode. (CD 1) 473

3.1.3.5.6.5 3 dB Antenna Beamwidths 474

The EWPMT shall be able to import transmitter 3 dB antenna beamwidth values, as a function of 475 frequency. (CD 1) 476

3.1.3.5.6.6 Antenna Polarization 477

The EWPMT shall be able to import transmitter antenna polarization designations as either vertical, 478 horizontal, right-hand circular, or left-hand circular. (CD 1) 479

3.1.3.5.6.7 Antenna Pattern Data 480

The EWPMT shall be able to import transmitter antenna pattern data files. (CD 1) 481

3.1.3.5.6.8 Emitter In-Band Spectrum Data 482

The EWPMT shall be able to import emitter in-band transmit power spectral density data files. (CD 483

1) 484

3.1.3.5.6.9 Emitter Out-of-Band Spectrum Data 485

The EWPMT shall be able to import emitter spectrum characteristics that are outside its 486 operational frequency band. This out-of-band data will be in the form of power levels as a function of 487 frequency; and shall include harmonics, spurious emissions, and broadband noise levels. (CD 1) 488

3.1.3.5.6.10 Emitter Frequency Use and Channelization Data 489

The EWPMT shall be able to import the minimum frequency used by the emitter, the maximum 490 frequency used by the emitter; and the channelization information including the number of channels 491 and channel frequency spacing. (CD 1) 492

3.1.3.5.6.11 Modulation Types and Emission Designators 493

The EWPMT shall be able to import modulation type information and/or emissions designators for 494 the emitter waveforms. (CD 1) 495

3.1.3.5.7 Enemy Receiver Parameters 496

The EWPMT shall be able to import enemy receiver equipment parameter information as specified 497 in the following sub-sections; as provided by available information sources during mission planning and 498 operations. Information sources shall include, but not be limited to, systems that publish to DDS 499

(primarily DCGS-A) and DCGS-A information that is available from the TED via a DIB query. It is 500 recognized that all the parameters listed may not always be available. The DDS and DIB information 501 shall be imported using software interface and file format specifications as described in Sections 502

3.1.3.2.2.2, 3.1.3.2.1.4, and 3.1.7.3.2.3. (CD 1) 503

3.1.3.5.7.1 Sensitivity Level 504

The EWPMT shall be able to import the receiver front end sensitivity value. (CD 1) 505

3.1.3.5.7.2 Jammer-to-Signal (J/S) Threshold 506

The EWPMT shall be able to import the receiver front end J/S threshold value at which receiver 507 performance is considered to be degraded due to jamming interference. Multiple J/S threshold values 508 may exist for different levels of jamming severity. For most cases the J/S threshold can be considered to 509 be the same as the inverse of the minimum required receiver signal-to-noise (SNR) ratio. (CD 1) 510

3.1.3.5.7.3 Peak Antenna Gain 511

The EWPMT shall be able to import the receiver peak antenna gain value, as a function of 512 frequency. (CD 1) 513

3.1.3.5.7.4 Antenna Pointing Angle 514

If the receiver antenna has a fixed (stationary) pointing angle, the EWPMT shall be able to import 515 the azimuth and elevation angle values that define the pointing angle. If the emitter antenna scans in 516 elevation and/or azimuth; the EWPMT shall be able to import the rate-of-scan parameters and angular 517 region of scan information. (CD 1) 518

3.1.3.5.7.5 3 dB Antenna Beamwidths 519

The EWPMT shall be able to import receiver 3 dB antenna beamwidth values, as a function of 520 frequency. (CD 1) 521

3.1.3.5.7.6 Antenna Polarization 522

The EWPMT shall be able to import receiver antenna polarization designations as either vertical, 523 horizontal, right-hand circular, or left-hand circular. (CD 1) 524

3.1.3.5.7.7 Antenna Pattern Data 525

The EWPMT shall be able to import receiver antenna pattern data files. (CD 1) 526

3.1.3.5.7.8 RF 3 dB Bandwidth 527

The EWPMT shall be able to import receiver 3 dB RF bandwidth values. (CD 1) 528

3.1.3.5.7.9 RF Filter Data 529

The EWPMT shall be able to import files containing magnitude and phase data, as a function of 530 frequency, for the receiver RF input filter. (CD 1) 531

3.1.3.5.7.10 IF 3 dB Bandwidth 532

The EWPMT shall be able to import receiver 3 dB IF bandwidth values. (CD 1) 533

3.1.3.5.7.11 IF Filter Data 534

The EWPMT shall be able to import files containing magnitude and phase data, as a function of 535 frequency, for the receiver IF input filter. (CD 1) 536

3.1.3.5.7.12 1 dB Compression Point (Saturation Level) 537

The EWPMT shall have the capability to import the receiver 1 dB compression point (saturation 538 level) value. (CD 1) 539

3.1.3.5.7.13 Receiver Frequency Use and Channelization Data 540

The EWPMT shall be able to import the minimum frequency used by the receiver, the maximum 541 frequency used by the receiver; and the channelization information including the number of channels 542 and channel frequency spacing. (CD 1) 543

3.1.3.5.7.14 Modulation Types and Emission Designators 544

The EWPMT shall be able to import modulation type information and/or emissions designators for 545 the receiver waveforms. (CD 1) 546

3.1.3.6 Neutral Data 547

3.1.3.6.1 General Import Capability 548

The EWPMT will have the capability to import neutral system data from intelligence databases, and 549 information sources that are accessible within the CPCE. 550

3.1.3.6.2 Neutral System Type 551

The EWPMT shall have the capability to import intelligence information that specifies the type of 552 neutral systems that will be encountered during the mission from the SKR, systems that publish to DDS, 553 and the JSDR. Neutral system type information shall be imported using software interface and file 554 format specifications for SKR, DDS, and JSDR as described in Sections 3.1.3.2.1.1, 3.1.3.2.2.2, and 555

3.1.3.2.1.3, respectively. System types will include radio nodes (transmit and receive), RF broadcast 556 nodes (transmit only), and navigation receiver nodes (receive only). (CD 1, except for JSDR) 557

3.1.3.6.3 Neutral System Position 558

The EWPMT shall have the capability to import information that specifies the location coordinates 559 for each neutral system; including the asset’s antenna height, if applicable. The EWPMT shall be capable 560 of importing position information from SKR, DDS, and JSDR using software interface and file format 561 specifications as described in Sections 3.1.3.2.1.1, 3.1.3.2.2.2, and 3.1.3.2.1.3, respectively (CD 1, except 562 for JSDR) 563

3.1.3.6.3.1 Neutral System Position Update 564

The EWPMT shall be capable of importing neutral system position updates throughout the course 565 of the mission. (CD 1) 566

3.1.3.6.4 Neutral System Asset Dependency Information 567

The EWPMT shall have the capability of importing information for friendly assets that are 568 dependent on neutral system operations (i.e. weapon systems). (CD 1) 569

3.1.3.6.5 Neutral System Emitter Parameters 570

The EWPMT shall have the capability to import neutral system parameter information from the 571

SKR, systems that publish to DDS, and the JSDR. Neutral system parameter information shall be 572 imported using software interface and file format specifications for SKR, DDS, and JSDR as described in 573

Sections 3.1.3.2.1.1, 3.1.3.2.2.2, and 3.1.3.2.1.3, respectively. Emitter equipment parameter 574 information of interest is specified in the following sub-sections. It is recognized that all the parameters 575 listed may not always be available. (CD 1, except JSDR) 576

3.1.3.6.5.1 Output Power 577

The EWPMT shall be able to import emitter RF output power level values; as a function of transmit 578 frequency and transmit mode. (CD 1) 579

3.1.3.6.5.2 Peak Antenna Gain 580

The EWPMT shall be able to import the emitter peak antenna gain values, as a function of 581 frequency. (CD 1) 582

3.1.3.6.5.3 Antenna Pointing Angle 583

If the emitter antenna has a fixed (stationary) pointing angle, the EWPMT shall be able to import 584 the azimuth and elevation angle values that define the pointing angle. If the emitter antenna scans in 585 elevation and/or azimuth; the EWPMT shall be able to import the rate-of-scan parameters and angular 586 region of scan information. (CD 1) 587

3.1.3.6.5.4 Peak Effective Radiated Power 588

The EWPMT shall be able to import peak effective radiated power (ERP) values, as a function of 589 frequency. (CD 1) 590

3.1.3.6.5.5 3 dB Antenna Beamwidths 591

The EWPMT shall be able to import transmitter 3 dB antenna beamwidth values, as a function of 592 frequency. (CD 1) 593

3.1.3.6.5.6 Antenna Polarization 594

The EWPMT shall be able to import transmitter antenna polarization designations as either vertical, 595 horizontal, right-hand circular, or left-hand circular. (CD 1) 596

3.1.3.6.5.7 Antenna Pattern Data 597

The EWPMT shall be able to import transmitter antenna pattern data files. (CD 1) 598

3.1.3.6.5.8 Emitter In-Band Spectrum Data 599

The EWPMT shall be able to import emitter in-band transmit power spectral density data files. (CD 600

1) 601

3.1.3.6.5.9 Emitter Out-of-Band Spectrum Data 602

The EWPMT shall be able to import emitter spectrum characteristics that are outside its 603 operational frequency band. This out of band data will be in the form of power levels as a function of 604 frequency; and shall include harmonics, spurious emissions, and broadband noise levels. (CD 1) 605

3.1.3.6.5.10 Emitter Frequency Use and Channelization Data 606

The EWPMT shall be able to import the minimum frequency used by the emitter, the maximum 607 frequency used by the emitter; and the channelization information including the number of channels 608 and channel frequency spacing. (CD 1) 609

3.1.3.6.5.11 Modulation Types and Emission Designators 610

The EWPMT shall be able to import modulation type information and/or emissions designators for 611 the emitter waveforms. (CD 1) 612

3.1.3.6.6 Neutral System Receiver Parameters 613

The EWPMT shall have the capability to import neutral system parameter information from the 614

SKR, systems that publish to DDS, and the JSDR. Neutral system parameter information shall be 615 imported using software interface and file format specifications for SKR, DDS, and JSDR as described in 616

Sections 3.1.3.2.1.1, 3.1.3.2.2.2, and 3.1.3.2.1.3, respectively. Receiver equipment parameter 617 information of interest is specified in the following sub-sections. It is recognized that all the parameters 618 listed may not always be available. (CD 1, except JSDR) 619

3.1.3.6.6.1 Sensitivity Level 620

The EWPMT shall be able to import the receiver front end sensitivity value. (CD 1) 621

3.1.3.6.6.2 J/S Threshold 622

The EWPMT shall be able to import the receiver front end J/S threshold value at which receiver 623 performance is considered to be degraded due to jamming interference. Multiple J/S threshold values 624 may exist for different levels of jamming severity. For most cases the J/S threshold can be considered to 625 be the same as the inverse of the minimum required receiver signal-to-noise (SNR) ratio. (CD 1) 626

3.1.3.6.6.3 Peak Antenna Gain 627

The EWPMT shall be able to import the receiver peak antenna gain value, as a function of 628 frequency. (CD 1) 629

3.1.3.6.6.4 Antenna Pointing Angle 630

If the receiver antenna has a fixed (stationary) pointing angle, the EWPMT shall be able to import 631 the azimuth and elevation angle values that define the pointing angle. If the emitter antenna scans in 632 elevation and/or azimuth; the EWPMT shall be able to import the rate-of-scan parameters and angular 633 region of scan information. (CD 1) 634

3.1.3.6.6.5 3 dB Antenna Beamwidths 635

The EWPMT shall be able to import receiver 3 dB antenna beamwidth values, as a function of 636 frequency. (CD 1) 637

3.1.3.6.6.6 Antenna Polarization 638

The EWPMT shall be able to import receiver antenna polarization designations as either vertical, 639 horizontal, right-hand circular, or left-hand circular. (CD 1) 640

3.1.3.6.6.7 Antenna Pattern Data 641

The EWPMT shall be able to import receiver antenna pattern data files. (CD 1) 642

3.1.3.6.6.8 RF 3 dB Bandwidth 643

The EWPMT shall be able to import receiver 3 dB RF bandwidth values. (CD 1) 644

3.1.3.6.6.9 RF Filter Data 645

The EWPMT shall be able to import files containing magnitude and phase data, as a function of 646 frequency, for the receiver RF input filter. (CD 1) 647

3.1.3.6.6.10 IF 3 dB Bandwidth 648

The EWPMT shall be able to import receiver 3 dB IF bandwidth values. (CD 1) 649

3.1.3.6.6.11 IF Filter Data 650

The EWPMT shall be able to import files containing magnitude and phase data, as a function of 651 frequency, for the receiver IF input filter. (CD 1) 652

3.1.3.6.6.12 1 dB Compression Point (Saturation Level) 653

The EWPMT shall have the capability to import the receiver 1 dB compression point (saturation 654 level) value. (CD 1) 655

3.1.3.6.6.13 Receiver Frequency Use and Channelization Data 656

The EWPMT shall be able to import the minimum frequency used by the receiver, the maximum 657 frequency used by the receiver; and the channelization information including the number of channels 658 and channel frequency spacing. (CD 1) 659

3.1.3.6.6.14 Modulation Types and Emission…