11 juillet 2018 | International, Aérospatial, C4ISR
By: Shawn Snow
The Corps is looking to install antennas in its F/A-18 C/D Hornets to help the aircraft defeat GPS jammers.
In a request for information posted in early June by Naval Air Systems Command, or NAVAIR, the Corps wants to install the anti-jam antennas known as the Air Navigation Warfare Program, or NAVWAR, in 120 of the legacy Hornets.
The anti-jamming antenna “provides Global Positioning System (GPS) protection for Naval Air platforms by allowing for continued access to GPS through the use of Anti-Jam (AJ) Antenna Systems designed to counter GPS Electronic Warfare threats from intentional and unintentional interference,” Michael Land, a spokesman for NAVAIR, told Marine Corps Times in an emailed statement Tuesday.
The development comes as U.S. aircraft have faced mounting electronic warfare attacks against aircraft in Syria.
Army Gen. Tony Thomas, the commander of U.S. Special Operations Command, told audience members at a conference in April that adversaries were trying to bring down AC-130 gunships in Syria using electronic warfare, or EW.
“Right now in Syria, we're in the most aggressive EW environment on the planet, from our adversaries,” Thomas said. “They're testing us every day, knocking our communications down, disabling our AC-130s, et cetera.”
The Corps is amid an overhaul of its forces and equipment to prepare for a potential fight with near-peer adversaries like Russia and China.
Both countries boast an impressive array of electronic warfare capabilities. Russia has been using the Syrian battlefield to hone its EW skills.
The top Marine has oft repeated the threats posed to GPS systems from rising adversaries and says the Corps needs to be prepared to fight in GPS denied environments.
The F/A-18 is the Corps' bridging aircraft as it moves to the new high-tech F-35. As the Corps transitions the older legacy Hornets are undergoing a service life extension, meaning the aircraft are being updated to handle the modern battlefield.
“Installation in F/A-18 A-D helps ensure continued mission capability as the service life of the aircraft is extended and facilitates supportability by using more common equipment,” Land said.
The Navy and the Marine Corps already use the anti-jamming GPS antenna in a number of airframes, according to Land.
“Typical installations replace a platform's existing GPS antenna with a NAVWAR antenna and separate antenna electronics, while leaving a platform's GPS receiver in place,” Land added.
The Corps expects the F/A-18 to be in sunset by 2030.
As the Corps moves to the F-35 and phases out its Hornets, the legacy fighters will consolidate on the West Coast by 2018 with the exception of VMFA (AW)‐242, which will remain aboard the Corps' air station at Iwakuni, Japan until it transitions to the F-35 in 2028, according to the Corp's 2018 aviation plan.
16 octobre 2018 | International, Aérospatial
General Electric [GE] and Advanced Turbine Engine Company (ATEC) touted the capabilities of their respective engines in the quest by the U.S. Army to find new engines for the AH-64 Apache and UH-60 Black Hawk fleets under the Improved Turbine Engine Program (ITEP).ATEC... http://www.defensedaily.com/ge-atec-running-hot-us-army-helicopter-engine-upgrades/
16 janvier 2020 | International, Terrestre
By: Jen Judson WASHINGTON — The U.S. Army is taking a step back on its effort to replace its Bradley Infantry Fighting Vehicle after receiving only one bid in its competitive prototyping program, but this does not mean the end of the road for the future optionally manned fighting vehicle, service leaders told reporters Jan. 16 at the Pentagon. Until now, the Army has been tight-lipped ever since it appeared the competitive effort was no longer competitive, as the service had received only one prototype submission. “Today the U.S. Army will cancel the current solicitation for the Section 804 Middle Tier acquisition rapid prototyping phase of the [optionally manned fighting vehicle]. Based on feedback and proposals received from industry, we have determined it is necessary to revisit the requirements, acquisition strategy and schedule moving forward,” said Bruce Jette, the Army's acquisition chief. “Since its inception, the OMFV program has represented an innovative approach to Army acquisition by focusing on delivering an essentially new capability to armored brigade combat teams under a significantly reduced timeline compared to traditional acquisition efforts. The Army asked for a great deal of capability on a very aggressive schedule and, despite an unprecedented number of industry days and engagements to include a draft request for proposals over a course of nearly two years, all of which allowed industry to help shape the competition, it is clear a combination of requirements and schedule overwhelmed industry's ability to respond within the Army's timeline,” Jette said. “The need remains clear. OMFV is a critical capability for the Army, and we will be pressing forward after revision." In October, the Army ended up with only one bidder in the OMFV competition — General Dynamics Land Systems. The service had planned to hold a prototyping competition, selecting two winning teams to build prototypes with a downselect to one at the end of an evaluation period. Defense News broke the news that another expected competitor — a Raytheon and Rheinmetall team — had been disqualified from the competition because it had failed to deliver a bid sample to Aberdeen Proving Ground, Maryland, by the deadline. A bellwether for what was to come in the prototyping competition happened earlier in the year when BAE Systems, which manufactures the Bradley, decided not compete, Defense News first reported. And, according to several sources, Hanwha also considered competing but decided against the opportunity. The CEO of BAE Systems' U.S.-based business, Jerry DeMuro, told Defense News in a recent interview that the company didn't regret its decision not to pursue OMFV as the requirements and schedule were previously laid out, but said it continues to talk to the Army about future opportunities. “It was a very challenging program,” DeMuro said. “It always comes down to three things: requirements, schedule and funding. The schedule was very, very aggressive, especially early on, and at the same time trying to get leap-ahead technologies. There's a little bit of dichotomy there. “The requirements that were being asked for was going to require, in our estimation, significantly more development that could not be done in that time frame and significantly more capital than the Army was willing to apply.” Jette said the Army had a large number of vendors interested in the effort, hosted 11 industry days and had a number of draft requests for proposals on the street, but, he said, “it's always a challenge for industry. I was on the outside two years ago, and you get an RFP in after the discussions — it still cannot align with what you thought, and that is what you have to respond to is the RFP.” The acquisition chief believes what happened in this case is there was “a large number interested, they started paring down, which started causing us some uncertainty about the competition, but we still had viable vendors in. And when you get out to actually delivering on those requirements, we had one vendor who had challenges meeting compliance issues with delivery, and the second vendor had difficulty meeting responsive issues, critical issues within the requirement — not knowing how to fulfill that.” When pressed as to whether GDLS met the requirements with its bid sample, the Army's program executive officer for ground combat systems, Brig. Gen. Brian Cummings, who was present at the media roundtable along with the Next-Generation Combat Vehicle Cross-Functional Team leader Brig. Gen. Ross Coffman, said the Army could not discuss results and findings regarding the company's submission. Several sources confirmed a letter was circulating around Capitol Hill from GDLS to the Army secretary that strongly urged the service to continue with the program without delay. So now it's back to the drawing board to ensure the Army gets the prototyping program right. Jette took pains to stress that the OMFV effort is not a failed program with the likes of Comanche, Future Combat Systems, Crusader or the Armed Reconnaissance Helicopter. “This is a continuing program. This is an initial effort at trying to get to a programmatic solution yielded, input that we needed to evaluate, which said we needed to revise our approach, not abandon the program or that it was a failure.” Some major failed programs in the past, Jette noted, were canceled after spending large amounts of money and still moving along even though problems were identified as the service proceeded. Crusader cost about $2 billion, Comanche about $6.9 billion and Future Combat Systems about $19 billion, Jette said. “We've spent a very small amount of money in trying to get to where we are, and in fact a good bit of the technology development that was part of the assessment phase is still totally recoverable," he added. Army Futures Command chief Gen. Mike Murray told the same group of reporters he is hesitant to call OMFV a program because it's a prototyping program, not a program of record. “We are still committed to this. This is like a tactical pause,” he said. The effort so far “gave us a great deal of clarity in understanding what is truly doable,” Jette noted. Army leaders said they would be unable to estimate how long its renewed analysis on the program might take before proceeding with a new solicitation to industry, or what that would mean for the program's schedule in its entirety. The original plan was to field OMFV in 2026. Last month, Congress hacked funding for the OMFV prototyping program, providing $205.6 million in fiscal 2020, a reduction of $172.8 million, which would have made it impossible to conduct a competitive prototyping effort. What happens to that funding or congressional support for the overall program is unclear. While sources confirmed to Defense News in early October that the failure with the OMFV prototyping effort revealed rifts between the acquisition community and the Army's new modernization command, Army Futures Command, Jette said while there is a bit of “scuffing here and there" the two organizations are working together “much better.” Murray added it is his view that the acquisition community and Army Futures Command is moving forward as “one team” with “one goal in mind.” https://www.defensenews.com/land/2020/01/16/army-takes-step-back-on-bradley-replacement-prototyping-effort/
11 juin 2020 | International, Aérospatial, C4ISR, Sécurité
Roper expects GBSD, B-21 and F-35 to migrate parts of their development to cloudONE as he pushes the Air Force to embrace advanced software practices. By THERESA HITCHENSon June 11, 2020 at 4:01 AM WASHINGTON: Air Force acquisition czar Will Roper says he is considering taking over DoD's artificial intelligence (AI) experiment, Project Maven, to make it operational while the service pushes its own AI capabilities into the field. “I was just speaking with USDI today about the potential of transitioning Maven over to the Air Force and making it an operational reality day-to-day,” Roper said. Project Maven begun in 2017, was designed to put machine-learning to work to sort through the masses of intelligence, surveillance and reconnaissance (ISR) data generated by DoD and Intelligence Community (IC) platforms. It has been a bit controversial, with Google pulling out of the effort in 2018; and the head of Air Combat Command head Gen. Mike Holmes saying he didn't believe it was ready for prime time. Roper explained that the Air Force was best positioned to take on Project Maven because of its progress in standing up capabilities under its Advanced Battle Management System (ABMS) family of systems, each dubbed with the prefix ONE. This includes the cloudONE for remote data storage, processing and access; platformONE for securely building software; the dataONE library; and the deviceONE that allows secure remote access to classified data. Via the ABMS effort, which is the Air Force's flagship for enabling Joint All Domain Command and Control, the Air Force has been able to build the “AI infrastructure” that allows an AI system to actually do analysis, Roper stressed. “That boring part, the AI infrastructure, is what has been critically absent in the Department, and we are finally doing it in the Air Force,” Roper said. “So cloudONE, platformONE, dataONE — this family of ONE systems — builds a tech stack that really is about getting data in proper custody so that analytics can be built on top of it and we can finally go do AI at scale.” The key, he said, is “data curation and custody, so that that data is discoverable by analytics algorithms that are able to assess its import to different missions, and then push it to the machine, without having to have people be inside the loop.” And that, of course, is what Project Maven focused on, the algorithms. Roper said the Air Force already has an “AI at scale operational today with the Distributed Common Ground System” as well as one being used for “predictive maintenance” that the service hopes have in use for 16 different assets within the next 18 months. The DCGS family of systems, an effort that began way back in 1998, is DoD's flagship capability for providing daily processing, exploitation and production of analysis from DoD to ISR platforms. Predictive maintenance is using AI to figure out what parts of a weapon system or platform are likely to break next, to ease and speed logistics planning. In both these instances, he explained, the environment is benign. That won't be so on the battlefield, where adversaries will be attempting to hack and spoof US AI systems — something that he says is all too easily done today. “It's harder than meets the eye to try to teach an algorithm to know that something is messing with them,” he said. “They inherently trust their data.” “I think there is this belief that that AI will just churn through it — throw enough data at it and everything will be okay — and that's not the case,” he elaborated. “We need another generation of this technology.” Thus, for the moment, the best solution is for humans and machines to work in tandem — as the Air Force is looking to do with the Skyborg project and the development of an AI co-pilot Roper has nicknamed R2D2. “We need to be pairing our AI with people,” Roper stressed. Still, Roper is enthusiastic about the progress made by the ABMS effort toward AI, including working with Northern Command on its response to COVID-19 — helping predict where pandemic hot spots might arise. “We're excited that we have that first taste of AI changing operations,” he enthused. “That AI flag has now been planted for the department. We have seen a future that only silicon was able to see; the human brain was not. If we can get that out onto the battlefield and use the ABMS event in September as our stepping stone, then what a wonderful step towards getting our department and our military away from thinking of itself primarily in terms of the platforms that produce data, and rather instead of the insights that are created by that data, many of them being created by AI,” he said. (The Air Force is planning the second “ABMS OnRamp,” to follow the debut field demonstration in December, for the first week of September. As Breaking D readers know, that second exercise will feature a scenario centered on Space Command operations.) Roper also waxed enthusiastic about the recent decision by the Joint Artificial Intelligence Center (JAIC) to move its development operations to cloudONE. They are not alone, he said. “I believe that portions of the Aegis Weapon System, and the F-18 are also using cloudONE for development,” he said. The Air Force has “put a ton of effort into getting it certified at the various security levels, classified to critical unclassified information,” he added. CloudONE now can be used with secret-level and Top Secret/Special Access Program (TS/SAP) level data, and Roper said that by the end of June it will be certified for use with Secret/Special Access Program level data. This makes it available to software developers across security levels, and opens the door for use by more Air Force weapons development programs, he explained. For example, Roper said that the Ground-Based Strategic Deterrent Program (GBSD) “will absolutely be using cloudONE and platformONE for its development.” And, he said, in talking with the F-35 program office he expects “they will do some portion of their development” using cloudONE. Further, he said the highly classified B-21 bomber program will be “moving in at the right point for them.” He noted that prime contractor Northrop Grumman has just demonstrated the use of Kubernetes — a software development technique that helps manage multiple “containerized applications” (i.e. with its own operating system) across multiple machines in a secure manner — on flight-ready hardware. Indeed, he noted, the B-21 program involves an initiative called DevStar that is trying to establish an autonomous testing capability. An Air Force spokesperson said in a statement that DevStar is “an Air Force initiative to use modern software development paradigms to rapidly deliver software to weapon systems while continually meeting safety, security, airworthiness and other compliance requirements that traditionally are performed in serial.” The Air Force website on the initiative shows it is trying to go beyond DevSecOps that seeks to build IT security into software upfront — to include super-high security and safety measures that will allow use in developing highly classified nuclear weapons-related systems. “And you're gonna keep seeing more of the Air Force move into this,” Roper said. “You will hear people use terms like Agile Development and DevOps and DevSecOps — they are not all the same. The tech stack underneath that is producing the software matters.” PlatformONE, he said, is one critical tool in producing software for the Air Force. “It is what is automating all those things that we have people doing today and people doing them in serial,” he said. And, he added, the use of platformONE and cloudONE in combination is “magic” that allows the sharing of software code across weapon systems development programs. “One of my ambitions for this year is to have code that's been written for, say, B-21 run on F-16 and vice versa, and not have any humans check it in between.” https://breakingdefense.com/2020/06/roper-pushes-moving-project-maven-to-air-force