21 avril 2021 | International, Aérospatial, Naval, Terrestre, C4ISR, Sécurité

DoD SBIR/STTR Pre-Release: DoD SBIR BAA 21.2, DoD STTR BAA 21.B, Air Force CSO X21.2, Air Force CSO X21.B

The DoD Small Business and Technology Partnerships Office announces the pre-release of the following Broad Agency Announcements (BAAs) and Commercial Solutions Openings (CSOs):
• DoD Small Business Innovation Research (SBIR) BAA 21.2
• DoD Small Business Technology Transfer (STTR) BAA 21.B
• Air Force CSO X21.2
• Air Force CSO X21.B
• April 21, 2021: Pre-release begins
• May 19, 2021: BAA opens, begin submitting proposals in DSIP
• June 3, 2021: Topic Q&A closes to new questions at 12:00 p.m. ET
• June 17, 2021: BAA closes, full proposals must be submitted in DSIP no later than 12:00 p.m. ET
The instructions and topics for these BAAs and CSOs are available on DSIP at https://www.dodsbirsttr.mil/submissions/login and at https://rt.cto.mil/rtl-small-business-resources/sbir-sttr/.

Updated DoD SBIR/STTR Program & Proposal Requirements
The following requirements are in place for all SBIR and STTR proposal submissions. Details on these requirements can be found in section 5.0 of the 21.2 SBIR and 21.B STTR BAAs and relevant attachments can be found in both BAAs and CSOs.
1. Foreign Ownership Disclosure Requirement
• Any offeror submitting a proposal under these BAAs and CSOs will be required to disclose via self-report any foreign ownership or control. Proposers must review Attachment 2: Foreign Ownership or Control Disclosure to determine applicability. Offerors shall also require any proposed subcontractors included in their proposal under this BAA to disclose via self-report any foreign ownership or control. If applicable, an authorized firm representative must complete the Foreign Ownership or Control Disclosure (attached to both 21.2 SBIR and 21.B STTR BAAs). The completed and signed disclosure must be uploaded to Volume 5 of the proposal submission.
2. Contractor Certification Regarding Provision of Prohibited Video Surveillance and Telecommunications Services and Equipment
• DoD must comply with Section 889(a)(1)(B) of the National Defense Authorization Act (NDAA) for Fiscal Year 2019; therefore, all proposals must include certifications in Federal Acquisition Regulation clauses 52.204-24, 52.204-25, and 52.204-26, executed by the proposer's authorized company representative. The Federal Acquisition Regulation clauses may be found as attachments to both 21.2 SBIR and 21.B STTR BAAs and will be available to download during proposal submission and uploaded to Volume 5: Supporting Documents.
3. Company Commercialization Report (Volume 4)
• The Company Commercialization Report (CCR) will be required for all proposal submissions. Proposers must complete the CCR by logging into their account at https://www.sbir.gov/, downloading a PDF copy of the CCR, and uploading the PDF to the DSIP proposal submission.
• WARNING: Uploading a new Company Commercialization Report (CCR) under the Firm Information section of DSIP or clicking “Save” or “Submit” in Volume 4 of one proposal submission is considered a change for ALL proposals under any open BAAs or CSOs. If a proposing firm has previously certified and submitted any Phase I or Direct to Phase II proposals under any BAA or CSO that is still open, those proposals will be automatically reopened. Proposing firms will have to recertify and resubmit such proposals. If a proposing firm does not recertify or resubmit such proposals, they will not be considered fully submitted and will not be evaluated.
4. Fraud, Waste and Abuse Training (Volume 6)
• The Fraud, Waste and Abuse (FWA) training is required for all proposal submissions. This training can be accessed in the Volume 6 section of the DSIP proposal submission. The training material must be thoroughly reviewed once per year. Plan ahead and leave ample time to complete the training based on the proposal submission deadline.
In addition to the proposal requirements above, the BAAs and CSOs have been updated to reflect applicable Federal Acquisition Regulation (FAR) and/or Defense Federal Acquisition Regulation Supplement (DFARS) clauses that will be included in SBIR and STTR contracts. Proposers are encouraged to thoroughly review the BAAs/CSOs to remain apprised of programmatic and contractual changes.

Topic Q&A
Topic Q&A is now available on the Topics and Topic Q&A page in DSIP. Proposers may submit technical questions through the Topic Q&A page at https://www.dodsbirsttr.mil/submissions/login.
During pre-release, proposers can contact TPOCs directly or submit questions via Topic Q&A. Once DoD begins accepting proposals on May 19, 2021, no further direct contact between proposers and topic authors is allowed. All questions and answers are posted electronically for general viewing. Topic Q&A will close to new questions on June 3, 2021 at 12:00 p.m. ET, but will remain active to view questions and answers related to the topics until the BAA close.
Questions submitted through the Topic Q&A are limited to technical information related to improving the understanding of a topic's requirements. Any other questions, such as those asking for advice or guidance on solution approach, or administrative questions, such as SBIR or STTR program eligibility, technical proposal/cost proposal structure and page count, budget and duration limitations, or proposal due date WILL NOT receive a response. Refer to the Component-specific instructions given at the beginning of that Component's topics for help with an administrative question.
Proposers are advised to monitor Topic Q&A during the BAA period for questions and answers and frequently monitor DSIP for updates and amendments to the topics.

Learning & Support
Visit the Learning & Support section for Job Aids and Help Videos to guide you through submitting and viewing questions and answers in the Topic Q&A, preparing and submitting your proposal in DSIP, and more: https://www.dodsbirsttr.mil/submissions/learning-support/training-materials

Email the DSIP Help Desk at DoDSBIRSupport@reisystems.com for assistance with using DSIP. Questions regarding DSIP can be emailed to the DSIP Help Desk and will be addressed in the order received, during normal operating hours (Monday through Friday, 9:00 a.m. to 5:00 p.m. ET).
General questions pertaining to a particular DoD Component and the Component-specific BAA instructions should be submitted in accordance with the instructions given at the beginning of that Component's topics.

Thank you for your interest in the DoD SBIR/STTR Program.
DoD SBIR/STTR Support Team

Sur le même sujet

  • The Navy needs industry to tackle software-defined networks, data sharing

    8 octobre 2020 | International, Naval, C4ISR

    The Navy needs industry to tackle software-defined networks, data sharing

    Andrew Eversden WASHINGTON — The U.S. Navy needs to quickly modernize its fleet's network in order to be prepared for future fights, but one of the “greatest impediments” to that effort is that 5frwcgydtqr5s4eathe hardware inside ships requires hull cuts to be upgraded, a top Navy IT official said Monday. “These platforms need to be water-tight which means our entry points are small. The equipment that needs to be upgraded inside the hulls often requires hull cuts,” said Rear Adm. Susan BryerJoyner, Navy cyber security division chief in the Office of the Chief of Naval Operations. “That challenges our ability to pivot quickly in order to upgrade the traditional hardware that [delivers] the capabilities we're trying to provide to the warfighter.” The key to modernization is to get around the hull cuts, BryerJoyner said Wednesday at the AFCEA NOVA Naval IT Day. This is a time-consuming process that has long irked the Navy. Instead, the service is turning to industry for help getting around the large hardware requirements of traditional networking capabilities. BryerJoyner said that the Navy's future lies in software-defined networking. Software-defined networking relies on software applications for network management. “We need to get to software defined networks. We know we need to be able to share data more seamlessly across the Navy. The challenge is, how do we come up with modular platforms that don't require hull cuts in order for us to be able to swap in and out on board the ship,” she said. “That's honestly one of the greatest impediments to modernization.” She also added that the service is seeking help from industry for data sharing. Like the other services, Navy ships must be able to pass data in denied and degraded environments, whether that's caused by the weather, adversaries or the poor satellite connection. The service, she said, must adjust to a state of operations where applications do not have constant connectivity. The Navy also needs to understand if the data needs to be shared just locally aboard a ship or if it needs to be aggregated in some form to be shared with the rest of a strike group or across a theater, she said. Data sharing capabilities across the theater will also be a critical component for Joint All-Domain Command and Control, a major push by the services to connect sensors and shooters across domains. Tactical cloud computing in remote environments will be a cornerstone piece to data sharing. Speaking on the same webinar, Navy Chief Information Officer Aaron Weis said the shift to cloud, driven in part by the ongoing COVID-19 pandemic, was currently the top priority. But for tactical cloud, Weis said, “there's no better use case for tactical cloud than a ship afloat or an expeditionary marine force.” “If the end state is ‘I'm not going to be able to securely move data from anywhere to anywhere,' well, now we're back to that modernization and the network discussion," Weis said. https://www.c4isrnet.com/battlefield-tech/it-networks/2020/10/07/the-navy-needs-industry-to-tackle-software-defined-networks-data-sharing/

  • CACI Awarded $83 Million Task Order to Support Portsmouth Naval Shipyard

    16 avril 2020 | International, Naval

    CACI Awarded $83 Million Task Order to Support Portsmouth Naval Shipyard

    April 14, 2020 - CACI International Inc (NYSE: CACI) announced today that it has been awarded a single-award task order for one base-year and four option-years, with a ceiling value of more than $83 million, by the U.S. Navy to provide engineering, technical, and planning expertise to the Portsmouth Naval Shipyard in Kittery, Maine. Under the task order, which the Navy awarded under its SeaPort-NxG contract vehicle, CACI engineers and technicians will provide expanded mission expertise, including planning maintenance and repair for submarines by assisting the Ships Availability Planning and Engineering Center (SHAPEC) and Deep Submergence Systems Program (DSSP). The task order is CACI's first award under the SeaPort-NxG vehicle. CACI technical expertise across submarine engineering disciplines, such as structural, mechanical, electrical, and combat systems, will help the Navy to safely return submarines to the fleet as quickly as possible. For example, CACI has developed the Shipyard Planning Engineering Automated Reports (SPEAR), the software tool SHAPEC uses to more effectively conduct its planning. John Mengucci, CACI President and Chief Executive Officer, said, “CACI engineers and technicians help Navy shipyards overcome hurdles in their maintenance and repair efforts with expertise earned through long-standing support of the mission. CACI stands ready to support the Navy shipyards in any way they may need, including by providing acquisition and engineering support.” CACI Executive Chairman and Chairman of the Board Dr. J.P. (Jack) London, said, “CACI is proud to play a critical role in helping the Navy maintain its submarine fleet and continue to project power around the world.” CACI's 23,000 talented employees are vigilant in providing the unique expertise and distinctive technology that address our customers' greatest enterprise and mission challenges. Our culture of good character, innovation, and excellence drives our success and earns us recognition as a Fortune World's Most Admired Company. As a member of the Fortune 1000 Largest Companies, the Russell 1000 Index, and the S&P MidCap 400 Index, we consistently deliver strong shareholder value. Visit us at www.caci.com. There are statements made herein which do not address historical facts, and therefore could be interpreted to be forward-looking statements as that term is defined in the Private Securities Litigation Reform Act of 1995. Such statements are subject to factors that could cause actual results to differ materially from anticipated results. The factors that could cause actual results to differ materially from those anticipated include, but are not limited to, the risk factors set forth in CACI's Annual Report on Form 10-K for the fiscal year ended June 30, 2019, and other such filings that CACI makes with the Securities and Exchange Commission from time to time. Any forward-looking statements should not be unduly relied upon and only speak as of the date hereof. CACI-Contract Award View source version on businesswire.com: https://www.businesswire.com/news/home/20200414005058/en/

  • Remotely Piloted Aircraft: Implications for Future Warfare

    30 janvier 2020 | International, Aérospatial

    Remotely Piloted Aircraft: Implications for Future Warfare

    By Lt. Col. Johnny Duray When an MQ-1 Predator fired an AGM-114 Hellfire missile in the opening stage of Operation Enduring Freedom over Afghanistan, the world discovered a new form of power projection: kinetic force delivered from unmanned, remotely piloted aircraft (RPA). That proof of concept drove exponential growth in RPA usage, with combat air patrols (CAPs) swelling from just four in 2004 to 65 simultaneous, worldwide CAPs every day in 2014. Yet there is still more work to be done to fully realize the power of RPA technology. As the new US national defense strategy focuses on an era of great power competition, RPAs will provide valuable capabilities and capacity to address the persistent threat posed by violent extremist organizations. In doing so, RPAs will also allow other portions of America's air arsenal to focus on near-peer competitor challenges. Achieving this goal requires a new vector for the use of RPAs, as illustrated in the vignettes that follow. Though details have been obscured for operational sensitivity, the narratives and lessons remain largely intact. The Camp Strike. Graphic: Mike Tsukamoto and Dash Parham/staff View or download this infographic The Camp Strike In one recent RPA mission, intelligence sources helped the US military discover a remote jihadi training facility. Plans called for eliminating the radicals with airpower. Leaders initially sought bomber aircraft for the strike, which required scheduling and positioning refueling aircraft, obtaining overflight clearances, and coordinating for personnel recovery—all time- and resource-intensive factors that didn't apply to the RPAs already providing persistent ISR overhead, as explained in RAND publication Armed and Dangerous? UAVs and US Security. When bombers proved unavailable, a four-ship formation of fighter aircraft was requested. This option necessitated an even more robust support structure, as the fighters needed to forward deploy closer in theater. This also required a massive undertaking involving the movement of support personnel and equipment, despite the fact that multiple armed MQ-9 aircraft were already conducting daily surveillance and intelligence missions in the vicinity of the camp. Two environmental factors introduced further complexity into this mission. First, the camp was embedded deep inside a canyon with a valley floor only 15 feet wide. Any air-launched weapons would need to be precisely aimed to strike the narrow space between the canyon walls. Second, the jihadis were broken up into two distinct groups, two to three miles apart. A first-run attack would require delivery of simultaneous effects. Re-attacks on survivors would need to be conducted expeditiously. Once the bomber and fighter options proved unavailable, leaders finally selected four MQ-9 Reapers to execute the mission. Reaper One, Reaper Two, and Reaper Three were flown by squadrons in the same location, while Reaper Four was flown by a squadron at a separate location. The first three Reaper crews planned, briefed, and executed as a formation, or flight, bringing the geographically separated Reaper Four into the planning as much as possible before execution. The four Reapers were equipped with two 500-pound GBU-12 laser-guided bombs and 16 air-to-ground Hellfire missiles. Reaper One teamed with Reaper Four to make a run on the first target group, dropping the 500-pound bombs. Once established inbound, Reaper One passed an estimated “bombs-on-target” time to Reaper Two and Reaper Three, which targeted the second group of terrorists-in-training with four Hellfire missiles in order to achieve simultaneous effects. The synchronicity was near perfect. Weapons impacts from the bombs on the first group and the Hellfires on the second group were within a second of each other. The four MQ-9s hit two separate target sets with six munitions on four different aimpoints with a time on target calculation formulated as the mission progressed, based on outside clearance authority. Reaper Two and Reaper Three teamed up to immediately re-attack the survivors. Prior planning, internal communication, and near-real-time data sharing enabled an unprecedented display of efficiency. RPA pilots physically located together can speak into each other's headsets without delay on an intercom channel, for example. Reaper Three rifled off all four of its Hellfires on three separate re-attacks in under seven minutes. In one instance, Reaper Three fired a Hellfire on a group of terrorists without ever having even seen it, since Reaper Two had tracked the group and provided final weapons guidance for Reaper Three's missile. Reaper One and Reaper Four were left to conduct re-attacks as solo aircraft, since they lacked the prerequisites for the seamless integration enjoyed by Reapers Two and Three. As such, they were only able to employ three of their available eight Hellfires in the first 16 minutes following the initial strike. The final attack was conducted two hours later when Reaper Three found a group of eight enemy combatants hiding in a small ravine. Out of munitions, Reaper Three talked the crew of Reaper Four on to the group. The terrain only allowed a window of approximately 20 seconds for an MQ-9 to provide final guidance onto the target before becoming masked by rocks. Reaper Four shot a Hellfire into the ravine, target unseen, while Reaper Three came in from the opposite direction, crested the terrain, and timed the aircraft's positioning so that final guidance was placed on the enemy group in the last 10 seconds of the missile's flight. By the conclusion of the mission, some 85 percent of the combatants were killed with the other 15 percent wounded. Camp Strike Lessons Learned Some of the lessons from this operation: The MQ-9 Reaper delivers unique capabilities in combat. The Reaper's slow airspeed permits more time to strike targets in steep or inaccessible terrain, while supersonic fighters and bombers permit only brief execution windows before sensors and targeting capabilities are masked. Nevertheless, the training required to take advantage of this capability is akin to the demands for manned aircraft crews. The range and effectiveness of present-day RPA strikes is possible because of the robust training, US Air Force Weapons School caliber planning, and RPA technological advances made since 2001. Remotely piloted aircraft provide synergistic effects when employed together as a flight. The idea of operating RPAs in a flight is still new. Operational planners typically task the closest RPA available just prior to the execution of a complex strike, requiring extensive coordination among the participants. But an RPA flight generates synergistic effects, just like manned aircraft, through a mutual understanding of responsibilities and a shared awareness of the battlespace. This is best cultivated through extensive prestrike planning and briefing, along with real-time information sharing during execution. Bringing together single aircraft from separate squadrons just before a mission ignores the lessons of airpower history in the name of convenience. Decentralized execution is fundamental to successful RPA application. RPAs present an unprecedented opportunity for “reach-in.” With unparalleled observation and communication capabilities, commanders at all levels have violated the long-held tenet of decentralized airpower execution and exerted direct control. Focus on platforms rather than effects stifles RPA operations. The fluid, dynamic nature of kinetic engagements demands mission-command orders that rely on tactical expertise and the situational awareness of those employing the aircraft. Yet effects are what matter in operations, not platforms. As long as commanders tie specific aircraft to specific missions, rather than desired effects, RPAs will continue to be underutilized. RPA aircrews routinely participate in operational planning sessions where the ability to position fighters overhead to provide close air support (CAS) is deemed a “go/no-go” factor by ground and air planners alike. When queried to elaborate on desired effects, ground force representatives routinely reply that they want airpower to assist in “breaking contact with the enemy” to facilitate a return to safety. Although a flight of MQ-9s armed with a dozen Hellfire missiles and a few 500-pound bombs could achieve this effect, planners continue to revert to their default understanding that only aircraft with an A-, F-, or B-designation can provide effective CAS. The 15-Second Window. Graphic: Mike Tsukamoto and Dash Parham/staff Vignette: The 15-Second Window As part of global counterterrorism operations, US and coalition forces tracked a senior terrorist leader several years ago. After extensive study, a concept of operations (CONOPS) developed to facilitate a strike on this individual within an incredibly tight window—the time it took for him to ride his motorcycle to his home, after departing from a main road but before entering a courtyard near his residence. This strike window lasted only about 15 seconds. This broke down into two problems: First, successfully positioning a shooting aircraft within a 15-second engagement window within seven seconds of the target departing the main road, and second, planning around a fork in the main road that afforded the target two options. Route A was simple—there were no further intersections before the target left the main road and entered the engagement window. Route B was more nuanced, with one additional intersection before the target left the main road. The shooting aircraft would need to maneuver to get into position before the target hit the additional intersection. If the target was held up for even a few seconds, it could throw off timing and negate all previous planning. Three MQ-9s were allocated for the strike. Reaper One took the lead and began timing calculations to maneuver into position. Reaper Two followed the target motorcycle as it traveled toward the engagement site. Data sharing allowed Reaper One to position itself within the 15 second window at precisely the time the motorcycle turned off the main road and came into the field of view (FOV). Reaper Three stared at the additional intersection along Route B. Reaper One was able to view Reaper Three's feed to determine the possibility of the target getting held up at that intersection should he travel along Route B. As events unfolded, the target chose to continue down Route B. Updates on the target's distance and speed from Reaper Two and the intersection traffic from Reaper Three enabled Reaper One to successfully maneuver the aircraft into the 15-second window, fire, and eliminate the target with no collateral damage. 15-Second Lessons Learned The success of this strike was made possible by a flight-focused operations approach, paired with an intensive training program, and truly decentralized execution. It also introduced three new areas to reflect on. Data-sharing brings asymmetrical advantages to bear in modern warfare. The strike on the senior terrorist was heavily reliant on real-time data sharing between aircrews, which allowed the flight to get inside the adversary's decision loop and reorient quicker than the adversary. Risk acceptance enables rapid advancement. The rapid acceleration of software (and some hardware) enhancements have enabled RPA airmen to execute kinetic engagements that would not have been proposed just five or six years ago. These capabilities were largely possible because the RPA community's close working relationship with industry allowed it to accept imperfect solutions in the name of accelerated capability. Tactical oversight offers enhanced RPA capabilities. The ability of an MQ-9 squadron to place additional personnel in a ground control station (GCS) to support a traditional two-person crew transforms what that aircraft can bring to bear in combat. This tactical oversight boosts the capability of the crew, elevating success rates for complex engagements. This is especially important, since in modern operations, the MQ-9 pilot has neither a flight lead nor an experienced aircraft commander to rely on for decision- making, in most cases as a result of years of surging RPA demand. The Attempted Rescue. Graphic: Mike Tsukamoto and Dash Parham/staff Vignette: The Attempted Rescue On one calm, moonless night a few years ago, a small group of US special operations forces parachuted from a transport aircraft on a hostage rescue mission. Overhead, three MQ-9s and a U-28 manned ISR aircraft provided support to the SOF team from insertion, through the rescue operation, and the exfiltration. The three MQ-9s were co-located and operated out of the same RPA operations center, where a small staff stood up to support the three flying crews. As the SOF team worked its way toward the hostage's reported location, it became apparent to the RPA operations center director that key real-time intelligence was taking too long to get to the ground forces via the joint operations center (JOC)—the main mission hub. The MQ-9 elements overhead had direct radio contact with ground forces and, more importantly, instant access to the intelligence as well. After a quick discussion about transferring responsibility from JOC leadership to the MQ-9 pilots, the time frame for essential intelligence processing to ground forces went from a minute to under five seconds. A U-28 aircrew member was prepositioned inside the ROC to provide subject-matter expertise on the ISR aircraft, as well as techniques, tactics, and procedures to the MQ-9 crews and ROC staff. Unfortunately, as the team arrived at the location, it discovered that the hostage had been moved from the village just prior to the raid. However, the event offered a real-world opportunity to explore several underutilized capabilities that RPAs and the operations center could apply to future missions. Attempted Rescue Lessons Learned RPAs' ability to port talent into any cockpit at any time is unprecedented in the history of airpower. Because of the physical setup of the ground stations that operate RPAs, any individual can “enter” the airplane while airborne. In this example, a U-28 expert was brought in to assist with airborne integration. Airborne integration could also be extended to fighters, bombers, and any number of other assets. Ground forces could send delegates to a ROC to educate and enable integration between RPAs and supported surface elements. RPA operations centers are uniquely positioned to fuse and disseminate information. These centers allow operational directors to seamlessly communicate face-to-face with the aircrews that provide a majority of the center's data. It is the equivalent of a combined forces air component commander (CFACC)—while in charge of an AOC—being able to jump into the cockpit of any manned aircraft under his authority. Additionally, the land-based setup of the GCS enables an RPA cockpit to connect to modern combat untethered by bandwidth and connectivity limitations that plague most airborne manned aircraft. The Way Forward for Air Force RPAs These three vignettes provide substantial food for thought about how RPAs expand the flexibility and capability of air component commanders. This leads to four critical implications that policy makers, DOD leaders, and Air Force officials should consider: Reconsider airpower force posture in the fight against violent extremist organizations. In light of changing national priorities and finite resources, it is imperative to find ways to sustain the counter-extremist mission in a more cost-effective manner. The cost of employing fighter or bomber aircraft is so much greater than MQ-9s that it should be self-evident. MQ-9 RPAs provide cost-effective capability that can assume many of the mission sets now prosecuted by high-end aircraft in today's counter-terror missions. Redeploying the majority of American high-end fighter and bomber aircraft back to their home bases prolongs their service life and generates valuable aircrew training hours to recapture depleted high-end skills. Investment in information-sharing will bring transformational advantages. As a whole, the US military must tear down parochial walls and allow information between disparate elements of hard power—tanks, ships, aircraft, infantry, and other forces—to flow more freely. The successful execution of the time-sensitive targeted strike on a terrorist leader described above was made possible by the rapid exchange of information between platforms. Unfortunately, this type of interconnectivity is sporadic between air assets even within the same US military service, and even worse among multi-domain assets from other services. Investment in RPA infrastructure is necessary to better share data and information with other systems, services, and the rest of DOD's network. Airmen must understand and articulate appropriate command and control (C2) relationships for RPAs. To fully realize the potential of present and future RPAs in combat, airmen must oppose any effort to centralize execution and challenge command structures that fail to place airmen in positions where their “air-mindedness” could maximize the Air Force's contribution to joint operations. In other words, airmen should influence airpower decisions at all levels of warfare. RPAs offer unprecedented opportunities for outside “reach-in” during tactical execution—and while senior commanders have indeed attempted to control all sorts of tactical elements, from aircraft positioning, to weapons placement, to camera field-of-view, this type of centralized execution stifles RPA aircrews from successfully exploiting fluid operational situations. Expand RPAs mission sets to include close air support. MQ-9 capabilities and tactics have reached a stage where planners need to rethink allocation for key missions, especially close air support. RPAs have transformed both the amount of firepower they bring to bear on the battlefield and the speed at which this ordnance can be delivered. Despite this, the MQ-9 is still predominantly regarded across the Air Force as an ISR asset, and rarely incorporated into CAS scenarios. According to one Air and Space Power Journal article, a mission ISR plan “is completed on a different timeline by different people in a different division in the [Air and Space Operations Center] and published in a different document. If CAS and ISR integrate, they do so by luck.” While not all CAS scenarios are appropriate for MQ-9s, military planners should embrace an effects-based perspective and try to minimize platform-centric bias. Remotely piloted aircraft and their associated operations centers present an ideal platform for entry-level multi-domain exploitation and rapid acquisition trials. Compared with traditional aircraft, RPA cockpits offer a prodigious amount of space and connectivity. Limited only by bandwidth and imagination, RPA offer unique opportunities to take advantage of multi-domain exploitation and use rapid acquisition capabilities to further the state-of-the-art. In current combat operations, the Air Force's MQ-9 is as different from its Operation Enduring Freedom-era 2001 MQ-1 forbearer as an F-16 is from a P-51. However, this transformation has collided with cultural differences rooted in traditional notions of force employment—both in the air and on the ground. This has led to sub-optimal utilization and investment considerations. Today, fighters and bombers are no longer the only option for mass strike, and RPAs are no longer just airborne sniper rifles. RPAs can effectively conduct CAS, particularly with small ground team elements like SOF units. These two considerations alone should cause US military leaders to rethink American force posture for the fight against violent extremist organizations. Remotely piloted aircraft operations are ripe for exploitation with centralized execution, yet “mission-type tactics”—where operational outcomes are emphasized more than any specific means of achieving them—are a central tenet to maximizing RPA potential. Continued investment in the RPA community is crucial to building on the momentum these assets are gathering in operations around the world. This will require harnessing information-sharing through open system architectures. The United States' continued prosecution of low-intensity conflicts around the world, and the need to prepare for potential near-peer military confrontations, both benefit from an agile, decentralized, and well-connected RPA force whose lethality is intelligently incorporated into joint force operational planning. Military leaders with a commanding grasp on RPA capabilities and a willingness to think beyond traditional aircraft mission sets, will be best positioned to take full advantage of every capability RPA can bring to bear in future combat. Air Force Lt. Col. John D. Duray is a senior pilot with more than 3,200 flight hours in the MQ-9 and U-28 and extensive experience in combat and combat support missions. He has supported Operations Iraqi Freedom, Enduring Freedom, Inherent Resolve, and Freedom's Sentinel, and deployed to four different areas of responsibility. The opinions and assessments expressed in this article are the author's alone and do not reflect those of the Department of Defense or the US Air Force. This article is adapted from a forum paper published by the Mitchell Instititue for Aerospace Studies. https://www.airforcemag.com/article/remotely-piloted-aircraft-implications-for-future-warfare/

Toutes les nouvelles