13 août 2020 | International, Aérospatial

Pentagon Rethinks Troubled F-35 Logistics System

Lee Hudson August 12, 2020

The Pentagon is in the early stages of replacing the troubled Lockheed Martin F-35's autonomous logistics system with a new, cloud-based network, and hopes to get it up and running by the end of 2022.

The Operational Data Integrated Network (ODIN) is intended to reduce workload and increase F-35 mission readiness rates by using a smaller, deployable, commercial and cloud-native architecture. Right now, F-35 users operate the Autonomic Logistics Information System (ALIS) that collects inflight information for maintainers to predict part failures.

However, the problem-plagued logistics system has encountered numerous issues that range from directing unnecessary maintenance actions, taking too long to boot up and time-consuming data entry. For example, users told the Government Accountability Office (GAO) that electronic records are frequently corrupt or missing, resulting in ALIS signaling the jet should not fly. This occurs in cases where maintainers know the aircraft is safe for flight. Maintainers at one location told the GAO they experienced as many as 400 issues per week for one six-month period in 2019.

The F-35 Joint Program Office (JPO) plans to begin installing hardware this September that can run software from both the legacy and new systems until ODIN is deployed fully. ODIN initial delivery is planned for September 2021.

ODIN hardware is designed to have a 75% smaller footprint than the legacy system, and be approximately 94% lighter—50 lb. compared with 891 lb. Another radical difference between the two systems is F-35 prime contractor Lockheed owns ALIS development and the new network is being developed by the JPO.

The JPO is using agile software development tools that allow rapid updates and improvements like how Apple updates its iPhones, while Lockheed employs waterfall development that allows for updates every 12-18 months.

In January, the JPO hit its first milestone by moving existing F-35 data into a new, integrated environment that will support applications designed by organizations such as Kessel Run, one of the Air Force's software factories. Kessel Run formed a team called Mad Hatter and tasked it to build software applications to render F-35 logistics more user-friendly.

A key complaint about ALIS was the lack of realistic operational requirements. In other words, user needs can become outdated. To address this shortcoming, the JPO partner nations agreed in January to update a requirements document for ODIN annually—if needed. Instead of crafting a rigid requirements document that will be outdated in 10 years, the new strategy calls for updating protocols based on reality, according to a program office maintenance systems expert. This strategy complies with the software acquisition policy of Under Secretary of Defense for Acquisition and Sustainment Ellen Lord. It calls for the users, developers and software designers to come together and produce a customer-centric design as development progresses.

The requirements document features six capability needs: deployment planning and execution; unit maintenance planning; sortie generation; sustainment readiness; information management, and ODIN support. The document also includes 43 performance measurements that the JPO will use as metrics to track ODIN development.

Beyond better programmatic planning, the Pentagon is facing a considerable obstacle as it transitions from ALIS to ODIN. The JPO is having trouble receiving technical data from Lockheed, Lord told the House Committee on Oversight and Reform.

“While the department recognizes industry's interest in protecting intellectual property, there is technical data that the department has rights to and needs in order to enable effective organic sustainment,” Lord noted in written testimony submitted to the committee.

In response to Lord's comments, Lockheed noted the company does not own all the logistics system's intellectual-property and data rights.

“ALIS software is also government-owned, per contract requirements with Lockheed, and our suppliers retaining intellectual property and data rights to portions of software that were developed using industry's investment funds is in accordance with the Defense Federal Acquisition Regulations Supplement,” Lockheed spokesman Brett Ashworth tells Aviation Week.

The Pentagon's overarching goal is to drive down F-35 sustainment pricing, which is where most of a program's cost resides. The government is still upgrading ALIS, an effort known as ALIS Next, before ODIN comes online to manage costs.

ALIS Next consists of more regular software updates, instead of the program's current 12-18 month cycle. An updated version of ALIS, known as 3.5, is outfitted with 300 stability fixes, says F-35 Program Executive Officer Lt. Gen. Eric Fick. Air Force software developers and Lockheed Martin personnel are simultaneously continuing to issue ALIS software patches. ALIS Next provides an opportunity to reduce the amount of administrative personnel needed to support the logistics system's operations in the field.

An important step to lowering the overall F-35 sustainment price is reducing the cost per flying hour. The goal is for the F-35A conventional takeoff and landing jet, the most popular variant, was $25,000 by 2025.

“We are confident $25,000 is attainable, but it will require collaboration with the JPO, services, allies and our industry partners to reduce overall cost,” Lockheed F-35 Vice President and General Manager Greg Ulmer submitted in written testimony to the House Committee on Oversight and Reform.

Over the past five years, the company has reduced a portion of the F-35's operations and sustainment costs by 38%. Lockheed is responsible for 39% of all F-35 sustainment costs, according to Ulmer.

The company estimates it will drive down controlled cost another 50% in the next five years, and it is working with the government to achieve similar savings on the remaining 61% of flight-hour costs that are under the purview of the Defense Department and propulsion suppliers.

Although in its infancy, ODIN is set to be the cornerstone for the next major wave of F-35 sustainment improvements over the next two years as ALIS is retired.

https://aviationweek.com/defense-space/aircraft-propulsion/pentagon-rethinks-troubled-f-35-logistics-system

Sur le même sujet

  • France confirms Fincantieri-STX shipyard deal, cautious on defense merger

    1 août 2018 | International, Naval

    France confirms Fincantieri-STX shipyard deal, cautious on defense merger

    ROME (Reuters) - The French government continues to support Italian shipbuilder Fincantieri's (FCT.MI) takeover of STX France, finance minister Bruno Le Maire said on Wednesday, but cautioned against hastening a related defense naval merger. Speaking in Rome after a meeting with the Italian government, he told journalists France had not changed its position on the deal, quelling concerns the takeover could be hampered by tenser relations between Paris and Italy's new anti-establishment government. However, he warned against hastening a merger between Fincantieri and French military shipyards operator Naval Group which has been seen as a possible follow-up to the takeover of STX. “It would not be wise” to discuss a defense merger now, Le Maire told reporters, stressing that this was not part of the deal reached in 2017. Under the terms of that agreement between France and Italy, Fincantieri bought a 50 percent share in STX, but it took effective control of the French shipyards thanks to a 12-year loan of a 1 percent stake by the French state, which is subject to review clauses. Relations between France and Italy have soured in recent weeks over spats on migrants and after the Italian government raised doubts on the TAV French-Italian rail link project which would connect Lyon and Turin. Le Maire said after his meeting on Wednesday with Italian Deputy Prime Minister Luigi Di Maio that Paris was still waiting for Italy's position on the project. https://www.reuters.com/article/us-stx-m-a-fincantieri-lemaire/frances-le-maire-confirms-backing-to-fincantieri-stx-shipyard-deal-idUSKBN1KM4E8

  • Future US Navy weapons will need lots of power. That’s a huge engineering challenge.

    26 juin 2018 | International, Naval

    Future US Navy weapons will need lots of power. That’s a huge engineering challenge.

    David B. Larter WASHINGTON ― The U.S. Navy is convinced that the next generation of ships will need to integrate lasers, electromagnetic rail guns and other power-hungry weapons and sensors to take on peer competitors in the coming decades. However, integrating futuristic technologies onto existing platforms, even on some of the newer ships with plenty of excess power capacity, will still be an incredibly difficult engineering challenge, experts say. Capt. Mark Vandroff, the current commanding officer of the Carderock Division of the Naval Surface Warfare Center and the former Arleigh Burke-class destroyer program manager who worked on the DDG Flight III, told the audience at last week's American Society of Naval Engineers symposium that adding extra electric-power capacity in ships currently in design was a good idea, but that the weapons and systems of tomorrow will pose a significant challenge to naval engineers when it comes time to back-fit them to existing platforms. “Electrical architecture on ships is hard,” Vandroff said. Vandroff considered adding a several-megawatt system to a ship with plenty of power to spare, comparing it with simultaneously turning on everything in a house. “When you turn everything on in your house that you can think of, you don't make a significant change to the load for [the power company],” Vandroff explained. “On a ship, if you have single loads that are [a] major part of the ship's total load, [it can be a challenge]. This is something we had to look at for DDG Flight III where the air and missile defense radar was going to be a major percentage of the total electric load ― greater than anything that we had experienced in the previous ships in the class. That's a real technical challenge. “We worked long and hard at that in order to get ourselves to a place with Flight III where we were confident that when you turned things on and off the way you wanted to in combat, you weren't going to light any of your switchboards on fire. That was not a back-of-the-envelope problem, that was a lot of folks in the Navy technical community ... doing a lot of work to make sure we could get to that place, and eventually we did.” In order to get AMDR, or SPY-6, installed on the DDG design, Vandroff and the team at the DDG-51 program had to redesign nearly half the ship — about 45 percent all told. Even on ships with the extra electric-power capacity, major modifications might be necessary, he warned. “We're going to say that in the future we are going to be flexible, we are going to have a lot of extra power,” Vandroff said. “That will not automatically solve the problem going forward. If you have a big enough load that comes along for a war-fighting application or any other application you might want, it is going to take technical work and potential future modification in order to get there.” Even the powerhouse Zumwalt class will struggle with new systems that take up a large percentage of the ship's power load, Vandroff said. “Take DDG-1000 ― potentially has 80-odd megawatts of power. If you have a 5- or 6-megawatt load that goes on or off, that is a big enough percentage of total load that it's going to be accounted for. Electrical architecture in the future is still an area that is going to require a lot of effort and a lot of tailoring, whatever your platform is, to accommodate those large loads,” he said. In 2016, when the Navy was planning to install a rail gun on an expeditionary fast transport vessel as a demonstration, service officials viewed the electric-power puzzle as the reason the service has not moved more aggressively to field rail gun on the Zumwalt class. Then-director of surface warfare Rear Adm. Pete Fanta told Defense News that he wanted to move ahead with a rail gun demonstration on the JHSV because of issues with the load. “I would rather get an operational unit out there faster than do a demonstration that just does a demonstration,” Fanta said, “primarily because it will slow the engineering work that I have to do to get that power transference that I need to get multiple repeatable shots that I can now install in a ship.” https://www.defensenews.com/naval/2018/06/24/future-navy-weapons-will-need-lots-power-thats-a-huge-engineering-challenge/

  • Senate bill promises more funding for space-based hypersonic defense, but mum on details

    12 juin 2020 | International, Aérospatial

    Senate bill promises more funding for space-based hypersonic defense, but mum on details

    Nathan Strout An early version of the Senate's annual defense bill would provide additional funding for space-based sensors capable of detecting and tracking hypersonic weapons, according to a summary released June 11. However, details on the proposal are scant. Congress has become increasingly concerned over the threat posed by hypersonic weapons under development by China and Russia. Too dim to be reliably picked up by current space-based sensors and able to maneuver around terrestrial sensors, hypersonic weapons make much of the current missile warning system obsolete, as it was designed for ballistic missile threats. To counter this threat, the Defense Department has proposed a solution: a proliferated constellation of satellites operating in low Earth orbit. Once a hypersonic threat is detected, the constellation tracks it while passing custody from satellite to satellite as the weapon moves around the globe. This Hypersonic and Ballistic Tracking Space Sensor, or HBTSS, will be part of the new National Defense Space Architecture, a proliferated constellation that will eventually be made up of hundreds of small satellites operating primarily in low Earth orbit. The Space Development Agency is overseeing this effort and plans to begin placing its first satellites on orbit in fiscal 2022. The Missile Defense Agency listed HBTSS as an unfunded priority during the prior budget cycle, and ultimately Congress did allocate $108 million to the agency for the program in FY20. Now the Senate Armed Services Committee says it will provide additional funding for the program for FY21, but it has yet to say by how much. The summary also does not note where the funding for HBTSS will go. Determining which agency would be in charge of HBTSS was a source of friction between the Pentagon and Congress in 2019, with the latter pushing for MDA to take primary responsibility for the effort, while the White House claimed it was too early to put one agency in charge. Ultimately, legislation passed by Congress in December directed MDA to be the lead agency for the development and deployment of HBTSS. However, the Missile Defense Agency's proposed FY21 budget transfers HBTSS funding responsibility to the Space Development Agency. At the same time, MDA awarded four $20 million contracts to companies to develop HBTSS prototypes in October. The four companies selected were Northrop Grumman, Leidos, Harris Corporation and Raytheon. The SDA recently issued a request for proposals for wide field of view satellites that references medium field of view satellites which are expected to be launched in 2023. According to SDA Director Derek Tournear, those will be the first space components of MDA's HBTSS. Still, it's unclear whether Congress will endorse moving HBTSS funding responsibility to SDA in FY21. When faced with criticism over that move from legislators at a March hearing, MDA Director Vice Adm. Jon Hill assured them that his agency would remain in charge of sensor development for HBTSS, with SDA providing money to MDA for the effort. Hill said the decision to move the funding was made by Under Secretary of Defense for Research and Engineering Michael Griffin SDA is asking for $137 million for space technology development in FY21, which includes funding for space sensor technology. The agency expects to begin placing payloads on orbit in FY22. The budget request does not specifically break out funding for HBTSS. MDA has also asked for $207 million for hypersonic defense. That funding will help the agency develop a regional glide phase weapon system and maturing technologies for future hypersonic defense architectures. It does not include funding specifically for HBTSS, as that has transitioned to SDA. CORRECTION: This story has been corrected to show that the medium field of view satellites are not part of the SDA's wide field of view solicitation. https://www.c4isrnet.com/battlefield-tech/space/2020/06/11/senate-bill-promises-more-funding-for-space-based-hypersonic-defense-but-mum-on-details/

Toutes les nouvelles