9 juillet 2019 | International, Aérospatial

US Air Force’s acquisition chief talks new B-52 engines and the future of battle management

By:

LE BOURGET, France — Will Roper, the U.S. Air Force's acquisition executive, wants the service to shift to a faster, more modern approach for buying software and hardware. But that's easier said than done.

The service has selected a number of programs where it will create technology in a new way, whether that involves creating digital prototypes, using agile software development or adopting a family-of-systems approach to address a changing threat environment.

To be successful, the Air Force will need to grapple with cultural and institutional pressures from those who champion tried-and-true acquisition practices. And in some cases, it also needs to prove to Congress that it is not taking inordinate risk and that its ambitions are executable.

Defense News spoke with Roper at the 2019 Paris Air Show on June 19 about some of the programs in which the Air Force is using new tools to develop technology.

Can you provide an update on Mad Hatter, the Air Force's project to use agile software development to try to fix some of the problems with the F-35's logistics system? You said in February that several improvements were to be fielded to the Autonomic Logistics Information System within weeks.

Mad Hatter is doing great. I have to give the team an A+ on being able to get started and start pulling apart the problems that our maintainers had.

They already deployed several apps that are helping maintainers. They fixed problems with the electronic equipment logs that were showing false positives, so those have been fixed, and the maintainers get to focus on things that are actually broken — not things that are reported as broken.

They fixed the scheduler, which had mismatches between the flight line system and ALIS, and they are currently working on things that are going to help maintainers do their own workflow on the flight line. There is a lot more to go for them. They're putting Wi-Fi out on the line so that you can touch ALIS at the flight line, which currently you can't. Maintainers have to go do their maintenance and then come back and enter data in the subsequent systems, and it doesn't make sense to create data once and then replicate it again.

We want maintainers to be able to have ALIS in a protected, secure Wi-Fi network at the flight lines; that data is instantly uploaded. We've got work to go to get the accreditation done so that we could reach all the way back into the standard operating unit that touches Lockheed Martin. But we got a great partnership with Lockheed. They've been with us every step of the way.

What happens next?

I don't have the answer yet, but one of the things that I think we should consider is the next variant of ALIS to be delivered. That's 3.6. It's currently going through negotiation and we're approaching it as traditional ALIS, but if we believe in agile development, eventually we need to pull a development module of ALIS out of the traditional and put it into the Mad Hatter process. [Version] 3.6 is a candidate for that. If it's not 3.6, is it 3.7 or 3.8?

The discussions we're having now is about where's the chalk line that we switch to the new methodology. We have to have enough development teams to do it and support the level and scope of the software, but I think we're ready. We've got the team in the Air Force. We have 800 people in Kessel Run, [the Air Force's software development team], that are currently doing amazing work for us.

With agile software development, you want to have exposure with the user. Once those apps were deployed, what was the feedback like? Did users want to see additional fixes, or were the apps coming out well already?

When final deployment was done, it was software as the users wanted. The users are involved from the beginning. Step one is the coders leaving their coding shop and going out to the flight line in Nellis [Air Force Base, Nevada], and sitting down, walking through how ALIS works and how the rest of the maintenance planning tools work. Understanding the pain points: What do you not like? What takes up your time? What do you want to change? Storyboarding that out to understand how it might be fixed, turning that into a development back log; so what am I going to attack and when? And then having the user touch products before they become final.

What the Mad Hatter team does is continues to iterate during design so that by the time you deploy, it's in the image of what the operators have requested, not in the image of what the developers expected they wanted, and that's the secret to “agile.”

Earlier this year, you said that once the Air Force hires an architect for the Advanced Battle Management System program, it can begin prototype work in the summer. Has that started?

We have. We've made great progress since we've hired our chief architect, Preston Dunlap. The Air Force has done a great job of rallying around him. ABMS and multidomain command and control is a top priority for our chief of staff, Gen. [Dave] Goldfein. He made it clear we've got to get ABMS over the goal line.

The rule that we're using at ABMS is we don't start talking platforms until the end. That's probably going to be biblical for us, for the first few years of the program. It is so easy to start talking about satellites and airplanes and forget what ABMS is going to have to uniquely champion. That's the data architecture that will connect them.

Preston's done a great job of starting to write down requirements for our data architecture, leveraging a lot of work that's already underway in our space-development portfolio. There's an initiative no one's heard of called Unified Data Library. It's not a very exciting name, it's like Castle Anthrax from Monty Python. But its super awesome. Unified Data Library is used currently for space situational awareness. Data pipes in through a variety of sources — commercial, academic, government — it's able to be addressed in multiple layers of classification and we do microservices on top of it that are used by different users.

Step one, the thing we got to get right in the first year of ABMS, is that data architecture because people need to build systems that populate according to whatever standards we've fixed.

Step two, once we get the data architecture defined, will be the requirements for the population of the data. Maybe one sensor needs to be able to fill a gap that others are creating. We're going to have to look at requirements at the system level and then tell satellites: “You need to be able to provide this level of data at this refresh rate. UAVs need to be able to [meet[ this rate" and so on and so forth.

Once we do that, then we'll be into the traditional part of the acquisition, which is building those satellites, building those UAVs.

What I've told Preston, we've got to do demonstrations along the way, so expect to do yearly demonstrations. The first one we want to get to is ad hoc mesh networking so that we get the same kind of internet of things effect where things start working together without humans having to control them and to not wait for the full architecture to be fielded. And it really will never be done; ABMS will merge over time as we put up satellites and UAVs. More things connecting to the network will make the system of systems better.

I think by the time we get to our 2021 budget, ABMS should be well definitized in terms of the lines of effort, the data architecture, you know we'll have to have a line for artificial intelligence because we are not going to be able to pass all the data collected across the networks, a networking component, and then at the end, the platforms that provided. But the chief says it best: This has got to be about the highway, not the trucks that are on it. Step one is getting the highway paved.

How can industry accommodate this new paradigm? How do you monetize this to incentivize businesses?

That's a question I don't have all the answers to.

Openness in the internet of things makes sense because you can monetize the data, and that's not going to exist for us. We're going to have to have a contracting incentive that replicates it.

The best theory we have now is some kind of royalty scheme that the more open you are and the more adaptation we do at the top of your system, the more you benefit from it. If you create the system that allows us to put 100 apps on top of it, you benefit differently than if we can only put one. But the details are going to be difficult because maybe that one app is super important.

We've brought in industry early and we plan to have a series of industry days where we talk about what does it take to create that structure. Industry appears interested because if we can build open — yes, there has to be a way to get the profit and cash flow — but it gives more opportunities to bring new technologies in. But if we can't replicate profit and cash flow on which their quarterlies depend, then they're going to have to go back to the old model of saying they're for open, but secretly giving you closed.

What are the immediate next steps for this program?

With the money that we have this year, we're able to get this kind of data architecture, analysis and demonstration work done. The bigger money for ABMS really begins in '20 and '21. That's where we'll ramp up fuller-scale prototyping.

I'm actually glad that we don't have big money this year because it can't go build a drone or satellite. We've got to focus on the part that's less sexy, which is that data architecture. We're going to have to be able to do software development at multiple levels of classification and do it securely: All those are things that are hard to get people energized about but they're going to be what makes or breaks for this program.

There's been pushback from the House about the Air Force's approach to replacing the B-52 engine. Lawmakers don't like that you're using Section 804 authorities. Why is that approach necessary?

It lets you get on contract a year and half earlier for an MDAP [major defense acquisition program]. And we found that for a variety of MDAPs, including the B-52 re-engine, you can use that year and a half to great effect. It's much better to be on contract with industry and working from Day One than sitting around twiddling your thumbs.

In the case of B-52 re-engine, we are using that time to do digital engineering for the engine and pod integration, so we have all three industry bidders on one contract. We have Boeing on contract. They are working together as part of the source selection. They will deliver their virtual prototype to us by October. We would normally not even be on contract, and already we have a deliverable that will help us understand the challenges of integration. Are they able to keep the center of gravity and the fluid flow around the power pod? Are they able to keep that the same? We will have that earlier.

Because we have a year and a half, we can go from virtual prototyping into physical prototyping. We'll select a vendor, and then we'll do round two, which is: You gave us your digital twin, now give us the physical twin. Show us you can do it in the real world.

And then we'll downselect and we'll award a contract and move to the integration side of the program, move into the production side.

What I view in this program, because I had an extra year and half, I can spend more time in EMD, engineering manufacturing and development. I can take on more engineering rigor and retire risks faster than I would if I was denied that time and trying to meet a near-term operational need.

In the case of the B-52, the TF33 engine has been flown hard. It is an old engine. We have maintainers up in places like Minot [Air Force Base, North Dakota], that are doing heroes' work to piece these engines back together. The depot is doing heroes' work to try and do maintenance overhaul with a supply chain that is gone. We are at high risk for keeping that engine far into the future, and when my war fighter says I need a new engine and I have one path, which is the 804 path, which I can start a year and a half faster than I could the traditional path, I can't tell that war fighter I'm going slow because that's what others think is the best path. I can go fast and I can do it with rigor and discipline.

And to close off, why I don't think it's a wholesale overhaul of the acquisition system is that we do all of the same documentation we would have in a traditional program. We just do it after we award contract, so we get the benefit of jump-starting but we still do all the discipline and documentation. And I think the pushback we see from the Hill is a misunderstanding that we still do the rigor.

https://www.defensenews.com/digital-show-dailies/paris-air-show/2019/07/08/us-air-forces-acquisition-chief-talks-new-b-52-engines-and-the-future-of-battle-management/

Sur le même sujet

  • Contract Awards by US Department of Defense - June 11, 2019

    12 juin 2019 | International, Aérospatial, Naval, Terrestre, C4ISR, Sécurité, Autre défense

    Contract Awards by US Department of Defense - June 11, 2019

    DEFENSE LOGISTICS AGENCY LB&B Associates Inc., Columbia, Maryland, has been awarded a maximum $37,018,357 modification (P0006) exercising the third one-year option period of a one-year base contract (SPE60016D0493) with four one-year option periods for transportation services. This is a firm-fixed-price contract. This was a competitive acquisition with five responses received. Locations of performance are Connecticut, Maine, Massachusetts, New Hampshire, Rhode Island, New Jersey, New York, Delaware, Maryland, Pennsylvania, Virginia, West Virginia, Alabama, Florida, Georgia, Kentucky, Mississippi, North Carolina, South Carolina, Tennessee, Arkansas, Louisiana, New Mexico, Oklahoma, Texas, Colorado, Montana, North Dakota, South Dakota, Utah, Wyoming, Arizona, California, Nevada, Idaho, Oregon, and Washington, with a June 30, 2020, performance completion date. Using customer is Department of Defense. Type of appropriation is fiscal 2020 procurement and war-stopper funds. The contracting activity is the Defense Logistics Agency Energy, Fort Belvoir, Virginia. Transaero Inc., Melville, New York, has been awarded a maximum $8,827,535 firm-fixed-price, indefinite-delivery/indefinite-quantity contract for a hydraulic manifold. This was a sole-source acquisition using justification 10 U.S. Code 2304 (c)(1), as stated in Federal Acquisition Regulation 6.302-1. This is a five-year contract with no option periods. Locations of performance are California and New York, with a June 5, 2024, performance completion date. Using military service is Army. Type of appropriation is fiscal 2019 through 2024 Army working capital funds. The contracting activity is the Defense Logistics Agency Land and Maritime, Warren, Michigan (SPRDL1-19-D-0127). ARMY General Dynamics Land Systems, Sterling Heights, Michigan, was awarded a $16,269,197 modification (P00082) to domestic and foreign military sales (Morocco) contract W56HZV-17-C-0067 to provide systems technical support for the Abrams family of vehicles. Work will be performed in Sterling Heights, Michigan, with an estimated completion date of June 30, 2020. Fiscal 2019 research, development, test and evaluation; Army working capital; foreign military sales; and other procurement, Army funds in the amount of $16,269,197 were obligated at the time of the award. U.S. Army Contracting Command, Warren, Michigan, is the contracting activity. NAVY General Electric Co., Cincinnati, Ohio, is awarded $9,211,724 for firm-fixed priced delivery order N0002419F4127 under a previously awarded basic ordering agreement N00024-18-G-4113 for LM2500 Single Shank Hot Section Kits. The material procured under this delivery order will be used to replace worn out nozzles and blades during the repair process, thus extending the life of the engine. Work will be performed in Cincinnati, Ohio, and is expected to be completed by August 2020. Fiscal 2019 operations and maintenance (Navy) funding in the amount of $9,211,724 will be obligated at time of award and will expire at the end of the current fiscal year. In accordance with 10 U.S. Code 2304(c)(1), this order was not competitively procured -- only one responsible source and no other supplies or services will satisfy agency requirements. The Naval Sea Systems Command, Washington, District of Columbia, is the contracting activity. *Small business https://dod.defense.gov/News/Contracts/Contract-View/Article/1872748/source/GovDelivery/

  • Embraer and Boeing Welcome Brazilian Government Approval of Strategic Partnership

    11 janvier 2019 | International, Aérospatial

    Embraer and Boeing Welcome Brazilian Government Approval of Strategic Partnership

    SAO PAULO and CHICAGO, Jan. 10, 2019 /PRNewswire/ -- Embraer [B3: EMBR3, NYSE: ERJ] and Boeing [NYSE: BA] have welcomed approval by the Government of Brazil of the strategic partnership that will position both companies to accelerate growth in global aerospace markets. The government's approval comes after the two companies last month approved terms for the joint venture that will be made up of the commercial aircraft and services operations of Embraer. Boeing will hold an 80 percent ownership stake in the new company and Embraer will hold the remaining 20 percent. The companies have also agreed to the terms of another joint venture to promote and develop new markets for the multi-mission medium airlift KC-390. Under the terms of this proposed partnership, Embraer will own a 51 percent stake in the joint venture, with Boeing owning the remaining 49 percent. Once Embraer's Board of Directors ratifies its prior approval, the two companies will then execute definitive transaction documents. The closing of the transaction will be subject to shareholder and regulatory approvals and customary closing conditions. Assuming the approvals are received in a timely manner, the transaction is intended to close by the end of 2019. Forward-Looking Information Is Subject to Risk and Uncertainty Certain statements in this release may be "forward-looking" within the meaning of the Private Securities Litigation Reform Act of 1995, including statements regarding the proposed terms of the transaction, the ability of the parties to satisfy the conditions to executing or closing the transaction and the timing thereof, and the benefits and synergies of the proposed transaction, as well as any other statement that does not directly relate to any historical or current fact. Forward-looking statements are based on current assumptions about future events that may not prove to be accurate. These statements are not guarantees and are subject to risks, uncertainties and changes in circumstances that are difficult to predict. Many factors could cause actual results to differ materially from these forward-looking statements. As a result, these statements speak only as of the date they are made and neither party undertakes an obligation to update or revise any forward-looking statement, except as required by law. Specific factors that could cause actual results to differ materially from these forward-looking statements include the effect of global economic conditions, the ability of the parties to reach final agreement on a transaction, consummate such a transaction and realize anticipated synergies, and other important factors disclosed previously and from time to time in the filings of The Boeing Company and/or Embraer with the Securities and Exchange Commission. Media Contacts: Chaz Bickers Boeing Communications charles.n.bickers@boeing.com 312-544-2002 Valtecio Alencar Global Corporate Communications Embraer Valtecio.alencar@embraer.com.br 11-3040-6891 SOURCE Boeing https://boeing.mediaroom.com/2019-01-10-Embraer-and-Boeing-Welcome-Brazilian-Government-Approval-of-Strategic-Partnership

  • Boeing to introduce flat satellite antenna to bring high-speed broadband to military aircraft

    22 mai 2019 | International, Aérospatial, C4ISR

    Boeing to introduce flat satellite antenna to bring high-speed broadband to military aircraft

    WASHINGTON – Boeing Phantom Works, the company's advanced technology arm, is introducing a new flat satellite communications (SATCOM) broadband antenna that would bring high-speed data to military aircraft. Space News reports. 9 May 2019 -- The low-profile electronically steered flat conformal antenna and a multi-channel terminal will be in production next year and the launch customer will be the Navy's future unmanned mid-air refueling tanker, the MQ-25, which Boeing is developing under an $805 million contract. The initial market for the phased array antenna and terminal will be operators of militarized Boeing jets like the Navy's P-8 surveillance aircraft and the Air Force's KC-46 aerial refueling tanker, to bring a smart skin design approach these contemporary aircraft. Compared to airborne command centers such as the president's Air Force One, most military aircraft have limited connectivity. The majority of military aircraft have narrowband terminals that get kilobits of data. A phased array antenna would give them access to government and commercial Ka-band satellites that provide from 10s to 100s of megabits of data throughput, Gathmann said. https://www.militaryaerospace.com/unmanned/article/16711555/boeing-to-introduce-flat-satellite-antenna-to-bring-highspeed-broadband-to-military-aircraft

Toutes les nouvelles