1
Integrated Electronic Warfare System Program
Update
IEWS Outreach 2
Michael E. Ryan Deputy Project Manager
Electronic Warfare michael.e.ryan_at_us.army.mil 410
-306-1602
27 Mar 2012
2
Agenda

• Since We Last Met
• IEWS Defined
• EW Capability Gaps, Targets Threats
• Emerging CONOPS
• Multi-Function EW (MFEW)
• Defensive EA (DEA)
• EW Planning Management Tool (EWPMT)
• Master Schedule
• Way Forward
• Summary

3
Progress Since Last Outreach.

• IEWS FY12 New Start program with initial
  increment of funding
• Two Materiel Development Decisions (MDDs)
  approving entry into the Materiel Solution
  Analysis (MSA) Phase
• MFEW Analysis of Alternatives initiation
• EWPMT Analysis of Alternatives initiation
• Offensive Electronic Attack Support to Current
  Operations
• Duke V2 Electronic Attack (DV2EA) fielded by PM
  CREW
• Communications Electronic Attack Surveillance
  and Reconnaissance (CEASAR) fielded by Rapid
  Equipping Force (REF)
• Ground Auto-Targeting Observation / Reactive
  Jammer (GATOR) initial versions fielded by
  CERDEC I2WD
• RMD 700 Implications
• Transition of Ground-Based CREW Executive Agent /
  Single Manager responsibility to Army
• CREW ST responsibility
• Defensive EA AoA path forward remains TBD
• Stand-up of Product Director Raven Fire
  (provisional organization)
• Support to AoAs and JCIDS process
• Initiation of MS documentation
• RFP development for MFEW and EWPMT

4
What is the IEWS ??
Protect Personnel,Platforms and Systems
Attack and Exploit Personnel,Platforms and
Systems

• Family of systems that provide offensive
  electronic attack (OEA) and electronic warfare
  support (ES) capability organic to the BCT

Family of systems that provide defensive
electronic attack (DEA) and electronic warfare
support (ES) to protect vehicles and convoys,
dismounted troops, and fixed site locations
Plan, Coordinate and Integrate EW Activities
Suite of software tools and applications that
enhance the Electronic Warfare Elements ability
to coordinate and synchronize EW throughout the
operations process
5
EW Capability Gaps in BCT Operations
Joint Electronic Attack (EA) assets lack the
capacity (low density / high demand) and specific
capability to meet BCT requirements

• Rapid fielding of BCT Electronic Warfare (EW)
  systems have saved lives BUT
• Lack of integration results in electronic
  fratricide
• Compatibility is a systemic issue

Control of EW is not integrated with BCT Mission
Command systems
6
EW Targets and Threats

• Primary Targets in BCT AO
• Brigade and below command, control, and
  communications (C3).
• Unmanned aerial system (UAS) control links
• Sensor data links
• Ground surveillance radars
• Counter-battery radars
• Position, navigation, and timing (PNT)
• Radio controlled improvised explosive devices
  (RCIED)
• Proximity fuzed rockets, artillery, and mortars

• Primary Joint Aerial EA Targets
• Integrated air defense systems (IADS)
• Air defense radars and C2
• Division and above C3
• TV and radio broadcast receivers

Target Framework
All EW targets in a scenario
EW targets in BCT AO
EW targets critical to the success of the
commanders mission
Targets addressed by Joint Aerial EA
The MFEW AoA will focus on the set of targets
from these demands
Note high demand, low density Joint EW assets
can address these targets, however they do not
reliably meet commanders needs
AoA will not assess targets primarily addressed
by Joint aerial assets
7
Emerging CONOPS

• Joint EW ICD, Appendix K
• Aerial, vehicle mounted, dismounted, and fixed
  site variants organic to BCT echelons
• Multi-function offensive/defensive EA systems
  employed to the tactical edge (Bn, Co, Plt)
• Capability to deny or deceive communications,
  radars, sensors, RCIED, weapon seekers
  triggers, and other electromagnetic systems
• Networked to enable dynamic reprogramming,
  dynamic tasking, cooperative targeting, and ES
  cooperation with intelligence
• OIF/OEF Tactics, Techniques and Procedures (TTPs)
  
• Capability to affect narrow comms bands for comms
  denial, EMS shaping, and C-RCIED
• CEASAR provides theater/corps Army aerial EA, in
  conjunction with Joint aerial EA
• GATOR V2 and Duke V2 EA are employed at select
  combat outposts for persistent OEA, networked ES,
  and support to military information support
  operations (MISO)
• TRADOC IEWS CONOPS
• Few, capable aerial and ground systems organic to
  the BCT provide EA to the BCT or supported
  commander
• Capability to deny or deceive communications,
  radars, sensors, RCIED, weapon seekers
  triggers, and other electromagnetic systems
• Networked to enable dynamic reprogramming,
  dynamic tasking, cooperative targeting, and ES
  cooperation with intelligence

8
Multi-Function EW (MFEW) What Does it Mean?

• Electronic PROTECT
• Warning and Indication
• Situational
• Awareness
• Tip or Cue other Assets
• Battle Damage Assessment

• Electronic ATTACK
• Deny
• Disrupt
• Degrade
• Deceive
• Destroy
• Offensive
• Defensive
• Cyber Enabler

MFEW
Electronic SUPPORT Detect, Identify, Geo-locate,
Enable Cyber, Work with SIGINT, Spectrum
Management, Mission Command
TAKEAWAY MFEW will converge and bring together
individual functions of EW. MFEW will
collaborate with the complementary functions of
SIGINT, Spectrum Management, Mission Command,
and Cyber Activities.
9
MFEW Overview
MFEW is a family of systems that provides
electronic attack (EA) and electronic warfare
support (ES) capability to the BCT, including
aerial, mounted, dismounted, and fixed site
variants

• Capabilities
• ES Search for, intercept, locate, and identify
  enemy EMS use
• Offensive EA Deny, disrupt, degrade, deceive,
  destroy enemy use of the EMS, to include
• Defensive EA Protect friendly personnel,
  platforms and facilities from enemy weapons that
  use the EMS
• Benefits to the Warfighter
• Responsive, organic capability mitigates EW
  capacity shortfalls from current high demand, low
  density Joint EW systems
• Provides the commander non-lethal options to
  shape and control the EMS to his advantage

Multi Function EW Systems
Potential Targets

• Provides combat information and targeting data
  for maneuver and lethal and non-lethal fires.
• Degrades enemy mission command capability
• Degrades or deceives enemy sensors and
  situational awareness
• Protects friendly forces from enemy EMS
  guided/triggered weapons

Enabled through EW Planning Management (EWPMT)
Capability
10
Initial Mix Alternatives
Initial mixes informed by various employment
concepts.
Joint EW ICD, App K
TRADOC IEWS CONOPS
OEF Lessons Learned
Blend
Note MFEW only based on MFEW AoA DEA
mix alternatives TBD (pending AoA)
Mixes represent initial estimates of system
quantity and employment echelon that will be
refined through operational benefit, gap
mitigation, and cost analyses.
11
MFEW Tasks
12
MFEW Acquisition Approach
27 Mar 2012
MSA Phase
PROD
DEPLOYMENT
EMD Phase
Technology Development
AoA
FRP Decision Review

• Multiple Competitive Contracts
• Architecture
• Networking
• Technology Risk

Network EW Planning Mgmt (NEWPM) in support of
Offensive EA QRCs
MS B
MDD
MS C
MS A
PCA
CDR
EMD/LRIP Contracts

• MFEW-Gnd
• Mounted
• Dismounted
• Fixed
• MFEW-Air

MFEW-Gnd
LRIP
TD Phase Competitive Prototyping Contracts
DV2EA
EDMs
MFEW-Air
LRIP
MFEW-Air/Gnd
GATOR
EDMs
MFEW-Gnd FRP
PDR
Production Contracts
MFEW-Air/Gnd
MFEW-Air FRP
OA
IOTE
DT
IOC

• Acquisition Approach
• MS A Entry ACAT II (est)
• TD Phase Either multiple BAAs or competitive
  prototyping contracts
• EMD/LRIP Phase Two competitive contracts one
  each for MFEW-Gnd FoS and MFEW-Air
• PROD Phase Two competitive FRP contracts one
  each for MFEW-Gnd FoS and MFEW-Air TDP
  build-to-print

• Technology Development Phase
• Define the System of Systems Architecture
• Identify cost/schedule/performance drivers
• Conduct trade space studies with focus on
  achievable/affordable system requirements
• Demonstrate Maturity Of Critical Technologies
  Prototyping activities
• Focus on architecture, SWaP-C, aerial platform
  integration, cost drivers, and high risk
  components
• Complete System PDR Requirements

13
Defensive EA Lineage
Duke designated PoR 20 August 2010
Legacy CREW Systems Demilitarized or Upgraded
2003
2012
2018
?Joint CREW Composite Squadron-One (JCCS-1)?
Warlock Family
2005
Current CREW Mission
2006
2010
Duke V1

• Warlock Variants
• Green
• Red
• ICE
• SSVJ
• MMBJ
• LX
• Blue
• Red/Green

Duke V2 (Primary Unit) 32,608 Total
2011
2008
CDRT Duke APC
Duke Secondary Unit 27,444 Total
First RCIED Incident in OIF Mar 2003
First Warlock Fielding Warlock-Green Apr 2003
Technology Transition
Duke V1 Jan 2006
Duke V2 Mar 2007
DTI NRE 20 Total
Fielding of SEC EW Engineering SMEs
Technology Transition
Technology Transition
DEA
August 2006 to April 2010 22,908 Duke V2 systems
were procured Duke V1 converted to Duke V2
Re-Purposing
IEWS
30 June 2005 9,700 Duke V1 systems competitively
awarded Best Value to SRCTec over 4 other
proposals
Duke V3 Mar 2009
EWPMT
May 2008 to December 2008 6,421 Secondary Units
were procured 28 August 2009 21,023 Duke
secondary units competitively awarded Best Value
to SRCTec SRCTec was the only vendor that
submitted a proposal
DTI NRE
MFEW
August 2010 to November 2011 (20) DTI systems
went through FAT and Rel. Demo.
Shortstop Electronic Protection System
(SEPS) Counter-fuse mission
Family of Systems
Countermeasures Protection System (CMPS) Funded
by REF
Leverage existing technologies from CREW and JCREW
2013
Demil Warlock Systems
Duke Electronic Attack
Transition Duke Sustainment to LRC and SEC
CREW Model is NOT a Good Long Term Investment
Strategy!
2005 All CREW loadsets managed and fielded using
ARAT
2009 TYAD and SRCTec PPP
Fixed Site CREW
2009 Army Establishes EW (29 series) Career Field
Filter/Communications Mitigation Development
First Recorded Spectrum Interference Incident in
OIF Oct 2006
GMR SRW Filters
CMS Filters
SINCGARS Filters
BFT I-FIX Antenna
? Repair Center Asset Visibility Tool? PBUSE
14
Duke Technology Insertion (DTI)
Wideband Software Defined DEA System
On Hold Pending Requirement

• Completed Environmental Testing, First Article
  and Operational Test
• Improved performance
• DTI Growth Features
• Embedded networked EW operations
• Defeat RCIED and Non-RCIED threats
• Programmable subsystems
• Support specialized EW and cyber missions
• Training/Test Mode

15
Defensive Electronic Attack (DEA)
TBD Pending AoA
27 Mar 2012
DEA-Dismounted
DEA-Mounted

• Acquisition Approach
• MS C Entry ACAT III (est)
• PROD Phase procure from either JCREW I1B1
  Dismounted , modify/upgrade, or Best Value
• Production Phase
• JCREW I1B1 CPD may satisfy DEA Dismounted
  requirement (AoA TBD)
• Procurement of systems to replace Thor III
  Dismounted CREW QRC

• Acquisition Approach
• MS C Entry ACAT IC (potential )
• Duke Tech Insert Bridge to IEWS DEA-Mounted
• PROD Phase single award competitive production
  contract
• Production Phase
• JCREW I1B1 CPD or G3 Directed Requirement (DR)
• Upgraded DTI Systems for 5 BCTs (MRAP Vehicle
  Platforms) for GRF located at APS sites (includes
  25 FAT IOTE units) plus spares

16
EW Planning Management Tool

• Integrates the Electronic Attack (EA), Protect
  (EP) and Support (ES) functions.
• Enables Multi-Function Electronic Warfare and
  Defensive Electronic Attack synchronization.
• Supports overall mission command by adding EW
  into the electronic operations process.

• Capabilities
• Suite of software tools and applications that
  allow the Electronic Warfare Officer (EWO) a
  mission command capability to plan, coordinate,
  manage, and deconflict unit EW activities
• Integrates the Electronic Attack (EA), Protect
  (EP) and Support (ES) functions coordinates and
  synchronizes EW operations across the S-2/3/6
• Interfaces with fires, intelligence support, and
  spectrum management databases

• Benefits to the Warfighter
• Commander can plan, coordinate, manage, and
  deconflict EW activities such as denying,
  disrupting, or degrading the enemys command and
  control systems.
• Commander decreases electronic fratricide by
  coordinating, synchronizing and networking
  electromagnetic spectrum usage across the staff
• Informs the Electromagnetic Order of Battle

17
EWPMT Desired Functions

• 1.0 Conduct EW Mission Planning
• 1.1 Automatically send, receive and assimilate
  information from mission command and other
  systems (i.e. import spectrum plan, target list,
  EOB, JADOCS, terrain) with by-exception conflicts
  requiring user generated input
• 1.2 Monitor, update, store and display friendly
  EW asset availability and status
• 1.3 Determine proper program load set
• 1.4 Utilize information provided by available
  assets to build EA/ES/EP plans
• 1.5 Conduct modeling and simulation of EW effects
  for COA development and comparison/contrast
  (requires maintaining a database of EW system
  profiles)
• 1.6 Integrate, mitigate, and deconflict EW EMS
  resource requirements
• 1.7 Identify and depict mission conflicts between
  collection, jamming, and friendly systems (intel,
  EW and EMSO)
• 1.8 Generate proposed EW targets
• 1.9 Archive EW missions to enable replay
• 1.10 Facilitate EW staff training

• 2.0 Provide and Display Running Estimate of
  Electromagnetic Operational Environment (EMOE)
• 2.1 Graphically display the Electronic Order of
  Battle (EOB)
• 2.2 Display/report simulation results (selected
  items on the COP)
• 2.3 Display EW strike warning using integrated
  radar, EO/IR sensor, and RF inputs tied to all
  communication nodes
• 2.4 Provide (display) data on friendly emitter
  interference, disruption, or degradation (to
  include those set up for deception). (Friend on
  Friend)
• 2.5 Provide (display) data on the effects of
  destruction/degradation of friendly EW assets
  (Foe on Friend)
• 2.6 Display current and post-mission analysis to
  determine mission effectiveness (BDA). (Friend on
  Foe)
• 2.7 Interoperate with higher and lower HQ EWPMTs
  for transfer of control. Pass control to EWO at
  higher echelon
• 3.0 Manage, Task, and Enable Configuration/Reprogr
  amming of EW Assets
• 3.1 Generate EA and ES requests
• 3.2 Dynamic tasking of organic EA/ES assets
  (assumes operator final go/no-go authority)
• 3.3 Conduct real-time reprogramming (and
  zeroizing) of organic EW assets over the net to
  address change in EW missions
• 3.4 Manage EW requests and feedback from higher
  and lower echelons
• 3.5 Provide Find-Fix-Target (FFT) info to fires
  and maneuver elements as necessary

Relatively higher functional importance related
to key planning tasks (See-Manage-Control Ops
18
EWPMT Acquisition Approach
27 Mar 2012

• Acquisition Approach
• IT Box solution incremental builds/fielding
• CDD only incremental approach to 22 desired
  functions
• Pre-MS B Entry ACAT III AIS (est)
• EMD/PROD Phase Single award base year plus 5
  additional annual builds
• MS C approval for limited deployment of initial
  Build 1 capability

• EMD Phase
• Evolutionary acquisition continuous RDTE to
  develop/incorporate new capability and evolution
  of IEWS FoS within each build
• S/W builds to be integrated into some TBD Battle
  Command application (e.g. AFATDS)
• Utilize NIE for agile acquisition approach
  (potential to accelerate)
• Align test events with MFEW and DEA programs for
  integration and efficiencies

19
IEWS Master Schedule
Increment 1
27 Mar 2012
MSA Phase
PPSS
PROD
DEPLOYMENT
EMD Phase
AoA
Full Deployment Decision Review
MS B
MDD
MS C
IOC
FOC
EWPMT Contract
Build 1
Tech Refresh
Build 2
Build 3
Build 4
Build 5
Build 6
OA
OA
OA
OA
IOTE
Limited Deployment
Build 2 Deployment
Full Deployment
Build 4 Deployment
Build 5 Deployment
MSA Phase
PROD
DEPLOYMENT
EMD Phase
Technology Development
AoA
FRP Decision Review

• Multiple Competitive Contracts
• Architecture
• Networking
• Technology Risk

MS B
MDD
MS C
MS A
PCA
CDR
EMD/LRIP Contracts

• MFEW-Gnd
• Mounted
• Dismounted
• Fixed
• MFEW-Air

MFEW-Gnd
LRIP
TD Phase Competitive Prototyping Contracts
EDMs
LRIP
MFEW-Air
MFEW-Air/Gnd
EDMs
MFEW-Gnd FRP
PDR
Production Contracts
MFEW-Air/Gnd
MFEW-Air FRP
OA
IOTE
DT
IOC
Sustainment
PROD
DEPLOYMENT
MSA
AoA
FRP Decision Review
MS C
IOC
FOC
DEA Mounted Production
MDD
Mounted
DTI NRE
LRIP
FRP 1
IOTE
FRP 2
FRP 3
Dismounted
JCREW I1B1 SDD / EMD Phase
LRIP
DEA Dismounted Production
IOC
FOC
MS C
OA
MOTE
20
Way Forward

• EWPMT
• AoA completion (3QFY12)
• Additional RFIs to Industry (TBD)
• Acquisition Strategy
• MS B documentation
• Program Office Estimate (POE) and cost target
• Pre-MS B Decision (4QFY12)
• Issue RFP (4QFY12)
• MFEW
• AoA completion (4QFY12)
• Additional RFIs to Industry
• Technology Development Strategy
• MS A documentation
• Program Office Estimate (POE) and cost target
• Issue RFP (1-2QFY13)
• DEA
• Materiel Development Decision (3QFY12)
• AoA initiation and support
• MS C documentation

Seeking Input from Industry on Acquisition
Strategy Concepts
Focus IRD on high risk, low TRL and cost drivers
Need help in defining EW reference architecture
standards
21
Summary

• Materiel Solution Analysis efforts shaping IEWS
  way forward
• Analysis of Alternatives
• Engagement with Industry and other Services
• Beginning to shape initial acquisition
  strategies
• More RFIs are likely
• Offensive EA QRCs supporting current fight
• Bridge to future MFEW capability
• Need to gather and incorporate lessons learned
• Defining System of System Architecture key to
  IEWS program success
• Collaborative approach with Industry
• Leverage existing architecture investments where
  possible
• Defensive EA path forward still to be defined
• Transition IPTs to implement RMD 700 guidance
• Expect DEA AoA to initiate soon