2 avril 2024 | International, Terrestre

Rheinmetall is contracted to manufacture 22 undercarriages and weapon systems for self-propelled howitzers PzH 2000

Rheinmetall delivers 22 weapon systems L52 of 155 mm calibre and just as many chassis for the PzH 2000 for the German Bundeswehr.

https://www.epicos.com/article/794767/rheinmetall-contracted-manufacture-22-undercarriages-and-weapon-systems-self

Sur le même sujet

  • Defense authorization bill delayed until after election

    10 septembre 2020 | International, Aérospatial, Naval, Terrestre, C4ISR, Sécurité

    Defense authorization bill delayed until after election

    By: Joe Gould WASHINGTON — A bipartisan compromise and vote on the 2021 defense policy bill isn't likely before the Nov. 3 elections, but it should come “quickly” thereafter, the House Armed Services Committee's top Republican said Wednesday. The vote would delay a decision from Congress about whether the Defense Department to rename military bases honoring Confederate leaders. It's defining issue for the $740.5 billion defense authorization bill, which includes must-pass provisions like military pay hikes, defense equipment purchase plans and strategic posturing of forces in coming years. “There are more negotiations that have to occur, and part of that negotiation is talking with the White House about the shape of that provision,” Rep. Mac Thornberry, of Texas, said at the Defense News Conference. “Is there a way to get everybody to ‘good?' Of course there is. Is it likely to happen before the election? No, it's not.” Republicans and Democrats in the House and Senate voted overwhelmingly to back language requiring the changes, though the House requires the names changed within one year and the Senate bill requires them within three years. President Donald Trump has threatened to veto the 2021 National Defense Authorization Act over the Confederate name changes among other issues. Trump has said Senate Armed Services Chairman Jim Inhofe, R-Okla., personally assured him that Congress will not force the Pentagon to change the names. That's fueled speculation that bipartisan negotiations to reconcile the bills could drag on. The summer's sustained protests over racial injustice have buoyed the provision, while Trump has argued that changing the names would dishonor troops who have served at the sites and that Confederate symbols aren't racist. “We can't cancel our whole history,” he told Fox News last month. Thornberry, who had offered a softer alternative as a House amendment, said Wednesday that both sides have political incentives not to compromise on the base renaming provision, among other issues. “I don't know how that will come out in conference, but I do think we are in a time when neither party is rewarded for compromise, and coming together and getting things done,” he said. “On the other hand, I think we should be able to get a conference report pretty quickly after the election.” https://www.defensenews.com/congress/2020/09/09/no-defense-authorization-bill-before-election-says-thornberry/

  • How the Army is modernizing the old, introducing the new

    13 septembre 2019 | International, C4ISR

    How the Army is modernizing the old, introducing the new

    By: Mark Pomerleau Maj. Gen. Randy Taylor led the Army's sustainment efforts for the past two years as leader of Communications-Electronics Command at Aberdeen Proving Ground, Maryland. CECOM works to repair, restore and maintain all the Army's communications, electronics, cyber and intelligence equipment once it's been used by soldiers. In June, Maj. Gen. Mitchell Kilgo took over Taylor's position at CECOM and Taylor departed for U.S. Strategic Command. Before he left, Taylor spoke with C4ISRNET staff reporter Mark Pomerleau. C4ISRNET: You are leaving CECOM this summer after two years. What's changed? MAJ. GEN. RANDY TAYLOR: Fifty-five to 70 percent of, not just time, but expense is in sustainment. Every dollar that we don't use appropriately on the sustainment side takes a dollar away from [new programs]. One simple, but not glamorous thing that has made a tremendous impact is just making sure that — when it comes to sustaining C5ISR on the battlefield — the parts we need are at the right place at the right time. We've gone from, no kidding, like 77 percent supply availability with these parts two years ago to now this year we are currently at 90 percent and we're going to finish this fiscal year at 93 percent supply availability. Transformational. In our world, a part — the piece of a complicated platform or just the mission command system — might be the difference between it working or not, between somebody fighting or winning or not ... living or dying. C4ISRNET: Are you using any emerging technologies to get those parts in the right place at the right time? TAYLOR: We're looking at these platforms that already have built-in sensors and built-in discipline of really getting that feedback on usage, on wear and sustainment demand. We're starting there when it comes to applying AI to sustainment. I see C5ISR being a natural progression of that, but not the best place to start because even though things are becoming more and more connected, a lot of this is still very disparate networks, the disparate ability to monitor usage and age, etc. C4ISRNET: What about using AI with the network? TAYLOR: That's incredibly interesting because it is so tempting for us as an institution to go out and modernize the network by buying the latest and greatest, spiral develop it — field a different capability set every two years and get all this new stuff and all the varieties between different units and this piece of network gear and that piece of network gear and then forget about sustainment in our hubris or excitement to modernize. Then this all comes crashing down a couple years from now because we didn't have the demand history to know how to start the parts, train the technicians, and different units have different equipment. Organically, we just haven't prepared ourselves to take all that on. So, on the new modernized network, we have a mnemonic device to help remember this: Five-three-one. Starting with five: that is acquire these new C5ISR capabilities with a five-year warranty from the manufacturer. Even though that doesn't sound exciting, it is very significant. Most of the time this stuff just comes with a one-year warranty. And these warranties cost money and every dollar a program manager spends on a warranty is one less dollar he can put toward a quantity increase. That five-year warranty gives us the lead time we need as an Army and at CECOM; it gives us lead time so by year three — that's the three in five-three-one — the Army makes a decision to keep or kill. Basically, to sustain or not the thing we just modernized. Some of it we'll kill by saying, “Okay, that technology is perishable, Moore's Law. We want to replace it with the next best thing so why sustain it?” Or we might say, “It's low cost; it's essentially disposable.” C4ISRNET: Is that a new approach from years past? TAYLOR: Absolutely. Institutionally, we do a terrible job deciding to end things. We have a tendency to perpetuate indefinitely until there's some kind of compelling decision point that forces us to that. We're not really designed now to think about it that deliberately, that early. So, we're working with Army Futures Command, who can help lead that decision-making. And then — if the Army decides to sustain it, keep it past its warranty period ... five years in most cases — we have to decide, okay, then who's going to sustain it? Most of that will be sustained by CECOM. Then we have to work out a plan to transition it over to sustainment. C4ISRNET: Does that change how the network will look? TAYLOR: The network writ large, for as long as this discussion is relevant, will consist of new parts and old parts. Modernized network cross-functional team parts and legacy? That's already in the field that will be out there in some form. The biggest thing on an enterprise level that's keeping the rates from being higher is the fact that a large amount of what is fielded in the network has never gone back to the depot for reset, repair, overall, anything like that. When you pick that apart, the reason it hasn't gone back is we've made it, in the past, too hard to get it back to the depot. It's taken too long. All of the legacy radios. All of the WIN-T components to include Point-of-Presence and Soldier Network Extension, radars, generators, night-vision devices ... Back under the [Army Force Generation] model when we had about six months to reset, this was alright. But still, people didn't turn their stuff in. Nobody wanted to be without their equipment for six months because we were taking all of six months and then some at the depot to turn this thing and send it back to them. We've since completely changed that. C4ISRNET: How so? TAYLOR: Now, the C5ISR units can bring in basically all their major C5ISR platforms, turn them all in and then almost immediately drive away with something that's been totally refurbished. We've started already to do that in partnership with Forces Command, which gives us the priorities. We've seen a big spike in turning this stuff around, which really helps improve operational readiness. At the same time, we're doing all that. We made great strides in something we call “repair cycle time.” Take something like a Satellite Transportable Terminal. We used to take over six months to turn an STT to overhaul it, send it back. We do that now in less than two months. But units don't even have to wait that long because they have a repair cycle flow. Everything is accelerated now so that we can better modernize the old, introduce the new and keep this capable as we go forward. C4ISRNET: What kinds of challenges are ahead in software? TAYLOR: A big challenge with software is intellectual property. It used to be the way we looked at intellectual property rights is we kind of saw it as a binary decision. The government either bought it or we didn't. Most times we didn't because it was very expensive to buy it ... They developed it, they give us capabilities we contracted for, but they own the inner workings of it. Same thing on the hardware side. We have someone build a platform, they give us a platform, but they don't give all the engineering diagrams and all the specs on how to build the subcomponents. But we found we were at these very vulnerable points where something became obsolete, meaning we had a part on a platform and then, for example, the manufacturer stopped making it because there was no business case or maybe a sub vendor went out of business, and now we had to manufacture it organically or hire someone else, but we didn't have the intellectual property. So, it took forever to re-engineer it. C4ISRNET: And the same with software? TAYLOR: Same thing on the software side. We didn't have the code and it would just be too expensive then to try to figure it out on our own. What we do now is we have an agreement saying if any of these trigger events occur in the future, I'm going to have rights to this intellectual property you developed. I, the government, will have rights, and it's going to be at a pre-negotiated price. And what we're going to do to protect each one of us here is we're going to hold your intellectual property with a third, neutral party that will hold your software. You'll be required to update it, keep it current, they will protect it from the government or any competitor seeing it until these trigger events occur and then I will pay you for what I need when I need it. That is a brand-new way of doing business. It's been in practice a little bit in industry but not in the Department of Defense. C4ISRNET: That's important if a new radar signature comes up and you need to make a quick change. TAYLOR: Absolutely. Anything. The threat environment changes, you've got to get in there. C4ISRNET: What about software licenses? TAYLOR: If you look at the trend of how software sustainment was going, before we did a big course correction, we were approaching the point theoretically where all our sustainment dollars would go to software and [we would] have nothing left for the hardware. We got that under control now. A big part of that rebalancing is reducing the licensing cost. It first started with getting to fewer baselines because it kind of got away from us in the surge and in the war years. We had so many different versions of different software and different platforms. So, we worked with the [program executive offices] and consolidated that down to the minimum feasible number of baselines. We've also negotiated some better enterprise licenses and there have been some efficiencies there. Right now, on the sustainment side, the folks that go in and make these modifications for the government, we're going from what was 43 contracts now being reduced to 34 sustainment contracts. That's still a lot but that's a huge inefficiency there. https://www.c4isrnet.com/opinion/2019/09/12/how-the-army-is-modernizing-the-old-introducing-the-new

  • Six things on the Pentagon’s 2019 acquisition reform checklist

    31 décembre 2018 | International, Aérospatial, Naval, Terrestre, C4ISR, Sécurité

    Six things on the Pentagon’s 2019 acquisition reform checklist

    By: Aaron Mehta WASHINGTON — Under the purview of Defense Secretary Jim Mattis, reform has become a buzzword inside the Department of Defense, with every office trying to find ways to be more efficient, whether through cost savings or changes to bureaucracy. The department's Acquisition and Sustainment office, headed by Ellen Lord, manages billions of dollars in materiel; and by Lord's own belief, it is ripe for changes that could net the department big savings. On Dec. 17, Lord sat down with reporters and outlined a series of goals for 2019 that she hopes will help transform how the Pentagon buys equipment. Here, then, are six key items to watch for in the coming year. 1. Rework the department's key acquisition rules: The DoD Instruction 5000.02 is a key bedrock that forms the basis of how the defense acquisition system works, guiding acquisition professionals in their day-to-day program execution. And if Lord gets her way, she'll largely rip it up and start over. “In 2019, one of my key objectives is to rewrite 5000.02. We have, right now, this huge, complicated acquisition process that we encourage our acquisition professionals to tailor to their needs,” Lord said. “We are going to invert that approach and take a clean sheet of paper and write the absolute bare minimum to be compliant in 5000.02, and encourage program managers and contracting officers to add to that as they need for specific programs.” Lord envisions taking the massive, unwieldy 5000.02 guidance and getting it down to “a couple page outline of what you need to do,” with “simple” contract language and an easy-to-follow checklist “so that this isn't an onerous process.” “I'm encouraging what I call creative compliance. I want everyone to be compliant, but I want people to be very thoughtful and only use what they need,” she said. “This is literally starting with a clean sheet of paper, looking at the law and the intent, and working to vastly simplify this.” Andrew Hunter, a former Pentagon acquisition official now with the Center for International and Strategic Studies, notes that the instruction is supposed to be rewritten every five years to keep it fresh, and now is probably the right time to start looking into that. But, he added, “a lot of what she says she wants to do are things that sound very similar to my ear to what [Lord's predecessor] Frank Kendall was trying to do in the last rewrite. He tossed stuff out left and right, worked very hard to create the different models, put in extended discussions of different potential models of programs so that it would be obvious to people there's not one single way to do a program.” Hunter is cautious when it comes to a massive shift in the 5000.02 system. “If you literally tell the system, ‘All the rules are repealed, go do everything you want,' the reaction won't be a sudden flood of creativity that astounds you with the amazing talent at the department, even though there is a lot of talent there," he said. “What's more likely to happen is you have total paralysis because everyone is sitting around going: ‘Oh no, the rules are gone. How do we know what we can do? What do we do now?' But over time that might shake out.” If Congress needs to get involved, Lord said, she's prepared to go to Capitol Hill “because I know they are partnering with us and they want to make sure we do things in a simpler, most cost-effective manner.” 2. Intellectual property rules: A long-standing fight between the department and industry is over who should own the intellectual property used by the American military. Before fully taking on 5000.02, Lord hopes to write a departmentwide intellectual property policy. Lord pointed to the “very good job” done by the Army on creating an IP policy and said her goal is to build on that to create a standard across the DoD. “From an industry perspective, we are trying to be consistent across all the services and agencies, so that we don't have different requirements for similar needs,” Lord said. “So intellectual property is a good example. We'd like to have the same kind of contract language that can be tailored to individual needs, but basically have consistent language.” David Berteau, a former Pentagon official who is now the president and CEO of the Professional Services Council, noted it is hard to read the tea leaves for what Lord may be planning based on her public comments. But he pointed out the long-standing challenge for the Pentagon — that nearly 70 percent of all program costs are life-cycle sustainment and maintenance costs — as a sign that something needs to change so the department can avoid major issues in the future. Depending on how new rules are implemented, the use of IP might drive down costs — or, he warned, it might lead to companies unable to compete, forcing the Pentagon to pay more or be less prepared for challenges. Put plainly, Berteau said, “it's complicated.” He hopes Lord will begin interacting with industry on this issue in ways similar to the current “listening tour” on changes to progress payments. 3. Better software development: It's become almost cliché that the department needs to do better at developing software, but in this case it's a cliché that experts, including Lord, agree with. The Defense Innovation Board, a group of tech experts from outside the department, is working on a series of studies on software, including one focused on how to drive agile development techniques inside the building. Lord said to expect that report before the end of March, adding: “I think that will be important in terms of capturing a road map forward on how to do this correctly.” 4. Increase use of OTAs: In 2018, Lord's office released a handbook on when and how to use other transaction authorities — legal standards designed to speed acquisition that critics say are underutilized by the department. Lord called it “sort of a warmup” for creating more useful handbooks for the acquisition community, but said that the goal for 2019 is to get people to correctly employ OTAs. “Usually they should be used when you don't have a clear requirement. So, true prototyping when you don't know what you're going to get,” Lord said. “Prototyping early on, probably before you get to the middle-tier acquisition.” 5. Greater use of prototyping: Speaking of which, Lord said the department has about 10 projects underway for rapid prototyping at the mid-tier level, with the goal of growing to about 50 in the next year. The goal is to take the systems into the field, test them out and then grow the next iteration of the capability based on what is learned. “We're taking systems that are commercially available and perhaps need a little modification, or defense systems that need a modicum of modification to make them appropriate for the war fighter,” Lord said. “That's one of the authorities we are very appreciative for, and we will continue to refine the policy. I signed out very broad policy on that this year. We'll write the detailed policy coming up early next year.” 6. Making the Selected Acquisition Reports public again: Until recently, the department publicly released annual Selected Acquisition Reports for each of the major defense programs. Those reports can inform the public of where programs stand and the costs associated. However, under the Trump administration, those reports have been largely classified as “For Official Use Only,” or FOUO, a higher level of security. Critics, including incoming House Armed Services Committee Chairman Adam Smith, D-Wash., have argued there is no need for those once-public reports to be listed as FOUO. It appears Lord is working to open those back up. “We're going to try to minimize the FOUO on that,” Lord said in response to a question about it. “There are certain information [issues] that we have to protect, but [we] understand the need, the requirement, and I will put our guidance to make everything open to the public to the degree we can.” https://www.defensenews.com/pentagon/2018/12/27/six-things-on-the-pentagons-2019-acquisition-reform-checklist/

Toutes les nouvelles