\u00a0Electronic warfare (EW)<\/a>\u00a0is another component of these new platforms, as jamming, spoofing and spectrum dominance are all top priorities on the battlefield.<\/p>\nThese platforms require solutions that can be quickly adapted and implemented to keep pace with the threats. Breaking Defense spoke with BAE Systems\u2019 Ed Leonard and Dan Mooney, product line director and business development director for small form factor solutions, respectively, about how drones, precision weapons and their electronic warfare systems are changing and how those challenges are being met.<\/p>\n
Breaking Defense: How is the EW environment evolving, especially with respect to drones?<\/strong><\/p>\nMooney:<\/strong>\u00a0It\u2019s about having the ability to have scalable and adaptable systems in that environment. The electromagnetic spectrum or EMSO (electromagnetic spectrum operations) is something that\u2019s changing within a matter of minutes, days, weeks, not years. It takes time to adapt some legacy systems to address that. Our ability to scale and have an adaptable architecture leads to the ability to respond to threats in a timely manner.<\/p>\nThe threats are evolving rapidly. How do we keep pace with that? Not only do we want to have a match in terms of a peer-to-peer capability, we want to have greater power than our adversaries in that moment and in a timely manner. Responding as quickly as possible within that threat environment is the primary factor.<\/p>\n
There are both low-cost, affordable mass drones and larger Group 3 and above drones. What are the advanced high-end weapons that we\u2019re talking about here in this discussion?<\/strong><\/p>\nI would define it the way that the Air Force defines it. They have a pyramid of systems that they call exquisite strike, sufficient strike, and then affordable mass-type weapons. We\u2019re talking about the entirety of that spectrum of weapons categories. In the exquisite strike category, the burden of success is mainly all on the weapon itself. It is a single kill chain in of itself \u2013 single system, single kill. There will always be a need for those systems to address the entire threat domain of just about every target that there is out there.<\/p>\n
Sufficient strike is a balance between those two. Typically, you\u2019ll see similar-type ranges, but the systems themselves aren\u2019t necessarily exquisite, not to the point of being sole custodians of kill chain responsibilities.<\/p>\n
Affordable mass is just as in its name, which is about the ability to produce tens of thousands to hundreds of thousands of those systems because mass in and of itself is an advantage. But mass paired with advanced effects, i.e., electronic warfare, is game changing.<\/p>\n
How does BAE address this pyramid of three categories?<\/strong><\/p>\nLeonard:\u00a0<\/strong>We\u2019re working to make to the lowest common building blocks of an EW system, like a power supply and a clock for example, that would be common from affordable mass to sufficient strike to exquisite strike. Then it becomes the simultaneity of the number of channels, the processing power you scale straight up through. Then you\u2019re building many thousands of common components, common hardware building blocks to use a Lego analogy. Then we piece them together in different configurations for different applications.<\/p>\nMooney:<\/strong>\u00a0Because we embrace the agile and digital design process, we will know our system to the core as it\u2019s designed and as metal gets cut. Like Ed said, in terms of the common building blocks, that\u2019ll simply be defined by mission needs in terms of what power amplification you need or what have you. The other key part of that Lego analogy, though simplistic, is I view a drone system or a weapon system or an unmanned aerial vehicle as the Lego box set itself. When you go to the Lego store, there\u2019s always a cache of available piece parts stockpiled for when the need is there. We\u2019re also looking into a stockpile to have our subsystems on hand for when they need to be integrated into the all-around solutions.<\/p>\nWhat is the demand signal you\u2019re hearing from the services?<\/strong><\/p>\nLeonard:\u00a0<\/strong>For drones and weapon-type systems, they want information and survivability information. What\u2019s around, where are they, what can I do about it?<\/p>\nDepending on the platform, be it a UAV or a weapon, for whatever is the requirement set from the customer, we layer on the software algorithms as required. In a UAV type scenario, we would bring a transmit antenna and a power amplifier and could do offensive jamming and electronic attack. We could do self-protection jamming to protect the UAV.<\/p>\n
We\u2019re looking into everything from Group 1 to Group 5. Group 1 and 2 are very challenging given their size and cost. But we\u2019re looking to scale from everything. What drones are being targeted, what\u2019s their cost? Then can we offer self-protection equipment and radar warning receiver type equipment.<\/p>\n
Mooney:<\/strong>\u00a0I see the demand signal from all of the services. The beauty of it is the ingenuity that our services have been doing. It doesn\u2019t really matter to us whether it\u2019s air launched, ground launched, there\u2019s utility for every service.<\/p>\nWe talk about leverage and reuse. A lot of the changes for us will simply be in the firmware or software. I view the software as being the game-changing capability. For us it\u2019s a common system with a lot of leverage and reuse able to be adaptable to whatever system it is.<\/p>\n
What\u2019s the importance of a Modular Open Systems Approach (MOSA) or Weapon Open Systems Architecture (WOSA)? How are those shaping your development of these technologies?<\/strong><\/p>\nMooney:<\/strong>\u00a0It gives the Air Force, Navy, or Army the ability to access best of breed throughout the supply chain. It\u2019s intended to break the traditional vertical vendor lock, have non-traditionals involved, have small businesses involved who may have fancy algorithms or some capability that really has game to bring to bear.<\/p>\nWith WOSA, there\u2019ll be common messages passed between systems so everybody\u2019s speaking the same language throughout the entire weapon or drone system itself. They\u2019ve also implemented something called WOSA X, which is the hardware component to it. Back to that Lego analogy, they all have those same pips or studs on all Legos. You piece it together, it\u2019s about common connectors, and then industry, again, best of breed, having their special sauce within their boxes, sensors, seekers, data links, what have you.<\/p>\n
How have you demonstrated these systems at military exercises, or through testing in EW environments?<\/strong><\/p>\nLeonard:<\/strong>\u00a0If you\u2019ve done your research on Army MOSA, everyone wants a VPX connector. Everyone wants a single-board computer. They want to upgrade their current system with more memory or faster compute by swapping in a new processor. They want to plug it in and have the software to download when the pilot or whomever walks out with the hard drive.<\/p>\nIn that context, we had a hard drive that went out to a jet with an open-system architecture, Big Iron software framework \u2013 that\u2019s an industry initiative with the Air Force and other partners. Our Big Iron software framework was given the stamp of approval and then loaded onto a GFE (government furnished equipment) payload, and flew flight testing with a third-party algorithm running on it.<\/p>\n
Fuente: <\/strong>https:\/\/breakingdefense.com\/<\/em><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"El presente art\u00edculo es una entrevista de Breaking Defense a autoridades de BAE SYSTEMS, relacionada con la necesidad que las costosas armas de precisi\u00f3n como… <\/p>\n","protected":false},"author":1,"featured_media":17693,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[18,2],"tags":[],"_links":{"self":[{"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/posts\/17692"}],"collection":[{"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=17692"}],"version-history":[{"count":1,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/posts\/17692\/revisions"}],"predecessor-version":[{"id":17694,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/posts\/17692\/revisions\/17694"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/media\/17693"}],"wp:attachment":[{"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=17692"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=17692"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=17692"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}