Back to news

October 9, 2019 | International, C4ISR

How airmen can work together for persistent ISR

By: Brig. Gen. Gregory Gagnon and Lt. Col. Nishawn Smagh

There is always a next war. Great power competition is here. Now is the time, while the United States maintains a position of strength, to ensure we are not outmatched, out-thought, or out-witted. Rapidly and realistically positioning the Intelligence, Surveillance, and Reconnaissance enterprise for first-mover advantage in today's data-driven environment is beginning with purposeful urgency.

The past paradigm: crew-to-aircraft model

During our careers, the Air Force ISR enterprise grew in both capability and capacity. In the late 1990s, the Air Force operated an ISR enterprise dominated by manned aircraft, each with their own specialized team operating unique systems that turned data into initial intelligence. Only a few organizations could turn raw airborne sensor data into intelligence in near-real time. We were only beginning to move data to the analyst, versus deploying the analyst to the data.

As battlefield demand of ISR grew, we scaled up. We were fortunate to help build and execute airborne intelligence operations on a global scale, connected via a global network — we called them “reachback” operations. Reachback operations were the first step in transmitting ISR sensor collection across the globe in seconds. Even today, few nations can conduct this type of ISR operational design. The enterprise has continued to advance, achieving fully distributed operations around the world. We also made it possible to remove humans from aircraft, allowing missions to fly nearly three times longer and expand the data available to exploit. Correspondingly, the Air Force increased the number of organizations that could accept data and create intelligence.

Following 9/11, our nation's needs changed; the fight necessitated the Air Force grow its capacity to deliver intelligence for expanded operations in the Middle East. We bought more unmanned vehicles, trained more ISR Airmen, and created more organizations to exploit data. Collection operations were happening 24/7 and most sorties required multiple crews to fly, control sensors and turn collection tasks into intelligence. As reachback operations grew, they became the Distributed Common Ground System and developed the ability to exploit aircraft sensor data. This growth was significant, but at the tactical level we employed the same crew model and simply grew at scale. This resulted in manpower growth, but also in disparate, distributed crews working similar tactical requirements with little unity of effort or larger purpose. This limited the ability of ISR airpower to have broader operational effects. While suitable for counter-terrorism, history tells us this approach is ill advised for great power conflict.

Observe and orient: the data explosion and sense-making

The traditional crew-to-aircraft model for exploitation must fast forward to today's information environment. The Pentagon has shifted its guidance to this new reality. The Defense Department recently declared information a seventh core function, and the Air Force's formal ISR flight plan maps a course for digital-age capabilities to turn information into intelligence. This “sense-making” must be able to handle both the complexity of a diverse information environment and scale to contend with an exploding volume of data. Access to expanded data sets, from diverse collection sources and phenomenology, is near and urgently needed. The Department's focus on artificial intelligence and machine learning in this realm remains stable and necessary. The next step is to retool how we task, organize, and equip both intelligence collection and analytic crews.

As the Pentagon focuses on open architectures, artificial intelligence and machine learning, and data standards, the field is rapidly moving out. Air Combat Command , the Air Force lead command for ISR, is attacking the crew-to-aircraft model to test a sensor-agnostic approach using multiple data sources to address intelligence requirements. Cross-functional teams of Airmen are now assigned broader operational problems to solve, rather than a specific sensor to exploit. This will change joint and service collection management processes.

ACC is tackling this future. We are supporting Air Force commanders in Europe and the Pacific with a pilot project that allows Airmen to explore these sensor-agnostic approaches. An additional element to our future success is partnering with our joint and allied partners, as well as national agencies, to bring resources, tools, and insights to bear. As we field the open architecture Distributed Common Ground System, we are shifting the focus from airmen operating specific sensors to airmen leveraging aggregate data for broader analysis.

Headquarters Air Force and ACC are installing technologies to ensure readiness for the future ISR enterprise. Cloud technology paired with artificial intelligence and machine learning promises to speed human-machine teaming in generating intelligence across warfighting domains at the speed and scale necessary to inform and guide commanders. Underpinning this effort is a new data strategy and agile capability development for rapid prototyping and fielding. The Defense Department and the Air Force must continue to prioritize this retooling. Our adversaries see the opportunities; this is a race to the future.

Situational awareness in the next war will require the development and fielding of AI/ML to replace the limited and manpower-intensive processes across the Air Force ISR enterprise. Employing AI/ML against repetitive data exploitation tasks will allow the service to refocus many of its ISR Airmen on AI/ML-assisted data analysis and problem solving.

ISR and multi domain command and control ... enabling decide and act

A headquarters-led initiative, with eyes toward a joint capability, is the creation of a collaborative sensing grid that operates seamlessly across the threat spectrum. Designs call for a data-centric network of multi domain platforms, sensors, and airmen that work together to provide persistent ISR. Equipped with manned and unmanned platform sensors capable of computing via AI/ML, these capabilities will link commanders to real-time information, plus tip and cue data from sensors-to-sensors, joint commanders, and weapons. This collaborative sensing grid is a foundational element for multi domain command and control . The vision of MDC2 is to outpace, outthink and outmaneuver adversaries.

Creatively and rapidly applying new technology to operational problems is a long-held characteristic of airmen. Our DCGS airmen are no different. Non-material solutions deserve as much attention as hardware. This pilot project is our vanguard initiative to prepare for rapidly changing future systems environments.

https://www.c4isrnet.com/opinion/2019/10/08/how-airmen-can-work-together-for-persistent-isr/

On the same subject

  • What’s standing in the way of multidomain operations?

    September 6, 2018 | International, C4ISR

    What’s standing in the way of multidomain operations?

    By: Daniel Cebul WASHINGTON — Mutlidomain operations are set to become standard for the U.S. armed services in the coming years, but technical, doctrinal and organizational hurdles remain. One impediment to multidomain operations involves issues in linking the service's disparate communication and information networks to share targeting data and communications. Rebecca Grant, a national security analyst with IRIS Independent Research, identified her “No. 1 problem" as “the communications architecture.” This stuff is not there yet," she said Wednesday at the Defense News Conference. "I'm less worried about the platforms, we've got some magnificent platforms. We've got to have that communication architecture. All the ability to do that is there, whether that's secure waveforms or the [radio frequency] links, but we have to take the plunge now, immediately, to go out and experiment with this next year.” The need for an integrated communications network was echoed by L3 Technologies' vice president of communications technology. “You need a network that can take all the networks we have right now, a systems-of-systems-level approach, that can tie these disparate networks together because you don't want to get rid of that install base because its too expensive to replace,” Keith Gentile said. Another challenge involves changing the services' doctrinal approaches to operations, especially as each branch becomes more dependent on one another. Gentile said that if the U.S. plans to quickly respond to enemy developments, doctrine surrounding operations in the domains must change. “There's a role mission and function issue that needs to be addressed when you talk about cross-domain or multidomain capabilities because each of the services operates in different domains," he said. "You got to go ahead and get away from the parochial pieces of service stovepipes, mission roles and functions — and realize you are talking about cross-domain capabilities.” Jaret Riddick, the director of the Vehicle Technology Directorate at the Army Research Laboratory, cited the service's recently stood-up Futures Command as one example of change within the services. “I would not downplay the steps the Army is making in standing up Futures Command. To take a four-star command and make the type of reorganization that has not happened since the early 1970s — I would not call that incremental,” he said. https://www.defensenews.com/smr/defense-news-conference/2018/09/05/whats-standing-in-the-way-of-multidomain-operations

  • New Flaws in Microsoft macOS Apps Could Allow Hackers to Gain Unrestricted Access

    September 3, 2024 | International, C4ISR, Security

    New Flaws in Microsoft macOS Apps Could Allow Hackers to Gain Unrestricted Access

    Eight vulnerabilities in Microsoft macOS apps allow attackers to bypass permissions, gaining unauthorized access to sensitive data.

  • Turkey’s ‘chronic engine problem’ is harming defense projects, warn officials

    June 29, 2020 | International, Aerospace

    Turkey’s ‘chronic engine problem’ is harming defense projects, warn officials

    By: Burak Ege Bekdil ANKARA, Turkey — Turkey's inability to produce a fully indigenous engine is harming some of the country's otherwise successful domestic defense programs, according to industry and government officials. “We had it 15 years ago, we had it 10 years ago and we are still having it,” said a former defense industry chief. “It's our chronic engine problem.” A government procurement official agreed, telling Defense News that “at best the problem causes major delays, and at worst it can be an existential threat [to programs].” The Altay, a multibillion-dollar program for the production of Turkey's first indigenous tank, has long been delayed due to difficulties surrounding the engine and transmission used to power the new-generation tank. BMC, a Turkish-Qatari joint venture that in 2018 won the serial production contract for the Altay, said in October 2020 that the tank would be fielded within 24 months. The original target was to have the Altay in the field this year 2020. Today, procurement officials and industry sources say even 2022 is an optimistic deadline. Western countries with power pack technology, particularly Germany, have been reluctant to share technology or sell to Turkey for political reasons. “Lack of a feasible power pack [engine and transmission] is depriving the program of any sensible progress,” noted an industry source. Turkey also needs an engine for the new-generation TF-X fighter jet as well as indigenous helicopter models in the making. At the center of these engine efforts is Tusas Engine Industries, a state-controlled engine maker. TEI announced June 19 that it successfully tested its locally made TJ300 miniature turbojet engine, which the company produced for medium-range anti-ship missiles. The engine features a thrust rating of 1.3 kilonewtons. Company officials say the TJ300 engine's more advanced, future versions could power larger anti-ship cruise missiles and land-attack cruise missiles. Turkey hopes to power its anti-ship and land-attack cruise missiles with locally developed engines. “The effort is about ending dependency on imported designs,” a TEI official said. Turkey currently imports miniature air-breathing engines from Microturbo — a unit of French company Safran — to power its domestically developed cruise missiles. Separately, Turkey's Kale Group is developing a larger, albeit miniature turbojet engine called the KTJ-3200. It has a 3.2-kilonewton thrust rating, and will power the Atmaca and SOM missile systems. On a much bigger scale, Kale Group has ambitions to develop an engine to power the TF-X. In 2017, Kale Group and British company Rolls-Royce launched a joint venture to develop aircraft engines for Turkey, initially targeting the TF-X. But the £100 million (U.S. $124 million) deal was effectively put on hold due to uncertainties over technology transfer. In December, Turkish Foreign Minister Mevlüt Çavusoğlu said the government is keen to revive talks with Rolls-Royce. When asked for an update on negotiations, a Rolls-Royce spokesperson told Defense News: “We submitted an engine co-development proposal to Turkey, but the customer has not elected to pursue this to date.” A year before the Kale Group-Rolls-Royce partnership, Turkish Aerospace Industries — a sister company of TEI — signed a $125 million heads of agreement with U.K.-based firm BAE Systems to collaborate on the first development phase of the TF-X. Turkey originally planned to fly the TF-X in 2023, but aerospace officials are now eyeing 2025 at the earliest. TEI is also developing the TS1400, a turboshaft engine it intends to power the T625 Gökbey, a utility and transport helicopter developed and built by TAI. The Gökbey currently flies with the CTS-800A turboshaft engine supplied by Light Helicopter Turbine Engine Company, a joint venture between American firm Honeywell and Rolls-Royce. The Gökbey made its maiden flight in September. TEI says it successfully tested the “core” of its TS1400 turboshaft engine and plans to deliver the prototype to TAI in late 2020. But analysts remain cautious. “These efforts may eventually fail to materialize without meaningful foreign know-how,” said a London-based Turkey specialist. “Or they may come at costs not viable for mass production.” Andrew Chuter in London contributed to this report. https://www.defensenews.com/industry/techwatch/2020/06/26/turkeys-chronic-engine-problem-is-harming-defense-projects-warn-officials/

All news