Electromagnetic Battle Management Ok, so why am I here today? What I want to provide you is the current status of what we at the Joint Electronic Warfare Center believe is a critical piece for collaborative EW across the Joint community. Major Jay Yniguez (E-knee-guess) Lead EW Engineer Future Capabilities Division Joint Electronic Warfare Center United States Strategic Command Lackland Air Force Base, Texas

Congested & Contested EM Spectrum ADVERSARY FACTORS MCO IW Congested EMS Contested EMS DE (EMP, HPM, laser) DRFM AESA MMW Investment $Billions to collect Information: Advanced C2 nets Weaponized COTS Proliferation Investment $Billions on Capabilities that use the information: AIR SPACE CYBER- LAND SEA MANEUVER SPACE LAND EW AIRCRAFT C4 NETS SHIPS GEN-5 PGM AESA PNT EMS So, here’s the issue. I don’t believe I need to go deeply into this since this is the slide that’s become well known and has very effectively carried the message of what our problem is. We know that we have to operate in both a congested and contested Electromagnetic Operational Environment or EMOE.  The key now is that folks ARE finally realizing that we absolutely cannot assume full spectrum access. Because of this realization, those same folks now know that they have to take action to successfully fight in the EMOE.  (Introduce Acronym Use acronym to save saying it over and over) CIVIL / COMMERCIAL IEEE Standards Speed Wireless Spread-spectrum Low Cost J2 J3 J6 We assume full EMS access

EMBM Requirement 2009 Electronic Warfare Initial Capabilities Document Approved by Joint Requirements Oversight Council Memorandum 177-09 Repeatedly states the need for the battle management of systems in the EMS COCOM and JTF requirements for EMS dependant systems are increasing The electromagnetic operational environment (EMOE) has changed considerably Electronic Warfare Initial Capabilities Document (ICD) Validation Authority: JROC Approval Authority: JROC Milestone Decision Authority: Multiple Designation: JROC Interest Prepared per JROCM 190-08 Approved per JROCM 177-09 Version 1.0, 30 Oct 2009 The requirement to have a capability to do this was officially stated in the Fall of 2009 by the JROC in the Joint EW ICD. It highlighted the need for more effective and efficient management of EMS resources. We’ve also consistently seen the demand signal stated in the COCOM IPLs and JTF JUONS that there’s a need for EMS related capabilities. So, the bottom line is that all of us in this room know that we’re obviously going to have to fight the EMS and therefore control the EMS in any conflict in the future. EMBM is the framework we’re proposing to help solve this issue and ensure interoperability, compatibility, and collaboration across the Services and domains.

Current Ops A/G/N/J-2 A/G/N/J-3 A/G/N/J-6 Electromagnetic Environment So, another part of our problem is that current EMS processes and tools  do not support integrated Combined Arms maneuver in the EMS. From an Airmen’s perspective, the EMS is still predicated on the big sky theory or ’big EMS, little photon’ theory. Our functional subdivisions operate throughout the EMS in a stove-piped fashion between the intel, ops, and communications communities with very little integration. Deconfliction is often conducted on the fly during execution and most of this deconfliction isn’t even close to being automated. Again, from an aviator’s perspective, this is concept is similar to not having an integrated Air Operations plan or Air Battle Management Concept.   (EMBM is about updating the processes and tools for JEMSO) Separate orgs / processes / people working the same operational environment!

The Problem Congested & Contested EMOE Stove-piped Planning & Execution So, combining the congested and contested EMOE with our stove-piped processes results in big, big problems which are manifested in comm fratricide, UAV losses, and even loss of life when soldiers are turning off CREW devices just so they can talk. The bottom line is that commanders can’t efficiently accomplish their mission and, against an adversary who will truly fight the EMS, that commander can’t effectively accomplish his mission. Inability to maneuver in the Battlespace Limits JFC’s C2, puts mission at risk, lives at risk

Situational Awareness EMBM Provides the framework for integrating all the elements of Joint EMS Ops (JEMSO) Integrates JEMSO with other aspects of operations (Air, Land, Sea, Space, Cyberspace) Provides effective and efficient use of EMS resources and capabilities Situational Awareness Decision Support Command & Control Spectrum Management Electronic Warfare ISR & Non-Traditional ISR So, how do we deal with all of this? What we’ve adopted is a pyramid structure to represent the EMBM concept. EMBM was created to provide the framework for integrating intel collection activities, ops command and control issues, and spectrum management issues across the EMS. It’s intent is to facilitate connectivity and automation in order to integrate Joint EMS Operations, or JEMSO,  across all the domains (air, land, maritime, space, and cyber). It’s designed to make effective and efficient use of resources to prevent EM fratricide, deal with interference and jamming, and rapidly respond to new requirements and time sensitive tasks.   (First use of acronym. Also spelled out on slide) Supports CC’s EMS Scheme of Maneuver Takes the Fight to the Adversary

Objectives, Effects, Guidance Operations Cycle Objectives, Effects, Guidance EM Users Requirements Air Land Sea Cyberspace Space Assess Develop EMS Plan Situational Awareness Decision Support Command & Control Execution Plan / Force Execution Weaponeer / Allocate EMS The current JEMSO ops cycle is fragmented across functions. Each mission area  is working within its own cycle. The intent of the EMBM framework is to take all user EMS requirements and integrate processes. It’s meant to synchronize the JEMSO operations cycle with the other operations cycles across JTF. (Domains are places, mission areas are capabilities (air operations, space ops, amphibious ops) that may or may not be cross domain) Produce / Distribute JCEOI / JRFL Synchronizes the overall JEMSO cycle

Notional Organization Air DATA Control JTF Geo DATA EMBM Sync External Orgs EMOC EM DATA EMOC: EM Ops Cell EMC: EM Cell Air Land Sea Space Cyberspace EMOC EMOC EMOC EMOC EMOC JEMSO occurs across all components and at every echelon. Like air battle management, EMBM provides the processes and connectivity for integrating JEMSO and other ops elements.  So, let’s take a look at the primary aspects of EMBM. (JEMSO already spelled out. EMBM integrates JEMSO elements with each other as well as external elements of operations (Air Ops, Land Ops, Special Ops, etc). Updated slide notes) Assigned Forces EMC Assigned Forces EMC Assigned Forces EMC Assigned Forces EMC Assigned Forces EMC Synchronizes JEMSO across components/echelons

Situational Awareness Situational Awareness Aspects of EMBM Shared Situational Awareness EM Operational Environment EOBs (red, blue, gray) Blue / host EMS use plans / restrictions EM maneuver boundaries Blue EMS asset locations (ID, status, etc.) Think in terms of any operations center. The first piece of THAT concept and the EMBM concept is situational awareness. As they say, a picture is worth a thousand words and successful operations begin with visualization of the Battlespace. EMBM brings together disparate data sources to present an integrated picture of the EMOE. Think in terms of users sharing common EMOE information at all levels, that ultimately feeds the overall COP.   Being able to see where we are allows us to begin planning where we need to go. And automation allows us to go there at the speed of the net. (There is only 1 COP, EMBM integrates the EMS elements into it) Situational Awareness Situational Awareness

Situational Awareness Aspects of EMBM Decision Support Progress towards CC’s intent / objectives Red potential COAs JEMSO COAs / target / nth-order effects ID EM interference EMI impact on friendly systems / ops EM interactions / effects prediction Based on our SA, we can integrate JEMSO with the rest of the scheme of maneuver and look at second and third order effects of operations in the EMS. You can also get true integration of  space and cyberspace capabilities with traditional JEMSO capabilities and communicate effects clearly to commanders for rapid and informed decision making. Effective decision making ultimately supports the final aspect of EMBM which is command and control.   Again, from an Airmen’s perspective, imagine if there was no Air Control Order or Air Tasking Order and aircraft flew wherever they wanted without any overall control or knowledge of where they were. We, in essence do that now in the EMS. (Advanced capabilities are not limited to space and cyberspace. Updated slide notes) Decision Support Attack Waveform Target Situational Awareness

Situational Awareness Aspects of EMBM Command and Control Capability tasking Authority delegation (e.g. M2M rule sets) Indications and warning Command & Control In air battle management, strong situational awareness and planning are essential to effective command and control. This is even more critical for Joint Electromagnetic Spectrum Operations given the tens- of- thousands of EMS dependent systems required to interoperate simultaneously. An extremely fluid EMOE dictates a robust, responsive C2 requirement. Automation for reporting up, down, and across echelon is absolutely key to success in this environment. So, let’s look at the aspects of EMBM holistically Decision Support Situational Awareness

Achieving EMS Control Electromagnetic Battle Management Unity of Effort Command & Control Electromagnetic Battle Management Spectrum Management Decision Support Electronic Warfare ISR & Non-Traditional ISR We've gone over the primary aspects of EMBM with visualization, planning, and execution BUILD This directly supports the JEMSO elements of EW ops, intel collections, and spectrum management One critical piece is that all of this is built on a foundation of standardized EMS data, architecture and protocols Resulting in the objective of unity of effort and EMS Control Let’s take a quick look of the components required to make this happen Situational Awareness Architecture, Data & Standards Joint Electromagnetic Spectrum Operations

EMBM Components EMBM Capability People EM Battle Manager EW, SM, ISR SMEs / teams Capability LNOs Ops Floor representative EMBM System UDOP/COP to view data and results of analysis EMBM Tools to analyze data Modeling and simulation Decision support Analysis / planning Relevant processes/data Supporting infrastructure (C2 links, computers, etc.) So, along with the overall EMBM concept, what are the notional components needed? As with any capability, people are the primary resource. An EM Ops Cell requires expertise in EMS control, communications, and collections. It requires representatives from primary EMS users like space, aviation, IO, comm., intel, and it must be represented in the operations center with other mission areas. Like air battle management, the EMBM system has to be comprised of many interoperable and compatible subsystems, not looking to build a new C2 infrastructure, but leverage existing infrastructure like Link-16 for instance. The key is that these systems have a common interface scheme using common data standards and common protocols. But, the need for commonality has to happen NOW as acquisition efforts are in progress….why….?

Service / Joint Efforts USA Integrated Electronic Warfare System (IEWS) - Electronic Warfare Planning and Management Tool (EWPMT) USAF AFRL/RYWZ EWBM Prototype / Proof of Concept USN/USMC Collaborative On-Line Reconnaissance Provider/Operationally Responsive Attack Link (CORPORAL) Link-16 collaboration with USAF Joint Global Electromagnetic Spectrum Information System (GEMSIS) Well, without direction and a unifying concept, each of the services is already working this issue and their piece of the puzzle. These are all systems and ideas that fall within an EMBM construct and need to be able to link, collect, and share data between them.

Contributors Jt/DoD Industry / Academia CCMDS Intel USA USN USAF USMC IDA N.G. Boeing Rohde & Schwarz ITT Raytheon GD LM DRT TAMU GTRI CCMDS USSOCOM USPACOM USSTRATCOM USCENTCOM Jt/DoD OUSD-ATL DISA JFCC/Space JCREW J65 JIEDDO JNWC Intel OUSD(I) DIA NSA USA HQ DA 3/5/6/7 TRADOC CERDEC FORSCOM USN OPNAV NAVAIR FEWC PMA 234/265/290 NAWC NSWC Crane ONR USAF AF/A5 ACC AFFMA AFRL AFSPC We’ve been working hard to make those connections as we’ve developed EMBM and we want to thank everyone in the audience for their help in getting us to this point. We’ve received lots of great input and folks have been very open to working this issue hard. We’re especially pleased with the degree of spectrum management input we’ve had and the collaboration that’s gone on there. USMC HQ/MC MCIOC

Draft JP 3-13.1 EW / JP 6-01 JEMSMO Joint Definitions Electromagnetic Spectrum Control (EMSC) The coordinated execution of joint electromagnetic spectrum operations with other lethal and nonlethal operations that enable freedom of action in the electromagnetic operational environment. Joint Electromagnetic Spectrum Operations (JEMSO) Those activities consisting of electronic warfare (EW) and joint electromagnetic spectrum management operations (JEMSMO) used to exploit, attack, protect, and manage the electromagnetic operational environment to achieve the commander’s objectives. Electromagnetic Battle Management (EMBM) The dynamic monitoring, assessing, planning and directing of JEMSO in support of the commander’s scheme of maneuver. Part of THAT teaming has helped unify the vision on things that can be politically sensitive, but absolutely critical like lexicon.   You heard me use terms today like Electromagnetic Spectrum Control, Joint Electromagnetic Spectrum Operations, and Electromagnetic Battle Management. Although they may sound a bit foreign at this point, they’re important to ensure we’re talking the same language and understanding things in the same way. The spectrum management community and our team as worked to ensure we had consensus on these and other basic terms. This lexicon has been thoroughly staffed and is just awaiting signature at the joint staff to be published. Draft JP 3-13.1 EW / JP 6-01 JEMSMO

EMBM supports JEMSO to achieve Electromagnetic Spectrum Control Way Ahead Staff EMBM CONOPs Provide a common Joint EMBM vision Draft DOTMLPF Change Recommendations EMS Control Joint Publication Architectural Steering group Data Standards Update DoD EMS Policy So, you’ve seen the requirement for EMBM and hopefully you understand the overall concept of operations as I’ve explained it. We’re now in the process of staffing the CONOP through STRATCOM. We’re working recommendations for DOTMLPF changes. With an agreed upon CONOPs, we plan to work with the Services and Joint Staff to start submitting the DCRs to implement EMBM. We plan to begin with standards at the base of the pyramid and the overarching doctrine at the top. As I said earlier, the Services are already hard at work on the details in between. Like air battle management supports joint air operations to achieve airspace control, EMBM supports JEMSO to achieve EMS Control. EMBM supports JEMSO to achieve Electromagnetic Spectrum Control

Questions Contact Information: Major Jay Yniguez Lead EW Engineer, Future Capabilities Division Joint Electronic Warfare Center Commercial: (210) 977-2172 (DSN: 969) Email UNCLASS: julian.yniguez@us.af.mil Email SIPR: julian.yniguez@jiowc.smil.mil Email JWICS: julian.yniguez@jiowc.ic.gov Presentation was UNCLASSIFIED