2 octobre 2020 | International, C4ISR

Pentagon’s CIO shop teams with armed services to prep for move to JEDI cloud

WASHINGTON — The Pentagon's top IT official said Wednesday that his office has spent the last few months preparing the armed services to migrate to the department's long-delayed enterprise cloud as soon as it becomes available.

“We're doing a lot of work with the services on getting them prepared to move their [software] development processes and cycles to DevOps so when the [Joint Enterprise Defense Infrastructure] cloud finally does get awarded, we're not starting at Day One,” Dana Deasy, Pentagon chief information officer, said during a Defense Writers Group roundtable.

The JEDI cloud contract was originally awarded to Microsoft over Amazon Web Services 11 months ago, and then was halted by a federal judge in February. Though the court case remains unresolved, Deasy said the services must now identify tools, integration environments and directories that need set up to connect users into the cloud when it's available.

Despite the judge's decision, “that's all work that we can do because it sits inside our ownership all ready,” Deasy said.

While the Department of Defense has faced criticism for its single-award structure, particularly as cloud technologies have advanced during the yearslong delay, Deasy insisted the JEDI cloud still fills a critical capability gap the department needs to deliver to the war fighter: data at the tactical edge and DevOps.

The JEDI cloud is the platform the department still envisions for those needs and is an important piece of the Joint All-Domain Command and Control concept, an initiative through which the services want to connect sensors and shooters. Deasy said the DoD has solutions in place to form that connection, but still needs “that tactical cloud out at the tactical edge.”

“JADC2 is going to point out, time and time again, about the need of being able to swiftly bring data together. And guess what? That data is going to be of different classifications, and bringing that together in a cross-domain way in a very quick-to-need [way] is something that is still a need we have across the Department of Defense that JEDI was specifically designed to solve for,” Deasy said.

Cloud, data and artificial intelligence are core elements to enabling JADC2. Using data for joint war fighting is the top priority of the department's forthcoming data strategy, which Deasy said he expects will be released in the next 30 days.

The department has a lot of data, but it is not necessarily prepared or stored in a way that is ready to be used for any sort of operations. The data strategy is expected to outline how to approach those challenges.

The DoD's new chief data officer, Dave Spirk, will finalize the data strategy. After he started in June, Spirk went on a “listening tour” across the department to inform the strategy.

Deasy said Spirk was told by many components that the department needs to set goals to ensure data is visible, understandable and trustworthy, while also easily within classification levels. They also said the data needs to be interoperable and secure, while also linked and integrated between sensors and shooters.

The Pentagon's Joint Artificial Intelligence Center, the department's AI hub that's situated under Deasy's office, is tackling joint war fighting this year under a new project that uses AI to link intelligence gathering systems to operations and effects systems for commanders.

The JAIC recently awarded its Joint Common Foundation contract to Deloitte. The company is to provide an environment for an enterprisewide AI development platform. That platform, which uses the Air Force's Cloud One enterprise cloud, was originally supposed to operate inside the JEDI cloud.

Therein lies the challenge for the DoD: Components that have been waiting for the JEDI cloud have had to look elsewhere — a problem Deasy recognizes he'll have to grapple with. Right now, Deasy is encouraging components that are waiting for JEDI but have an “urgent war-fighting need” to look elsewhere for platforms.

“That is obviously OK in the short term, but over time that starts to become problematic because now you're starting to set up a lot of different solutions in different environments where you're going to have to go back and sort out in an enterprise way,” Deasy said.

https://www.c4isrnet.com/battlefield-tech/it-networks/2020/09/30/pentagons-cio-shop-teams-with-armed-services-to-prep-for-move-to-jedi-cloud/

Sur le même sujet

  • Pentagon, Lockheed Martin Failed to Ensure Proper Parts for F-35

    20 juin 2019 | International, Aérospatial

    Pentagon, Lockheed Martin Failed to Ensure Proper Parts for F-35

    CHARLES S. CLARK A major contractor and the Pentagon's top management office came in for criticism from an inspector general for cutting corners in assuring that the massive joint-service F-35 stealth fighter is equipped with ready-for-issue parts. In a report dated June 13, the Defense Department watchdog found that parts for the department's largest acquisition—with an estimated $406 billion price tag and sales planned to foreign allies—were not being received according to the contracts and performance incentives. The parts contracted for delivery by Lockheed Martin Corp. include wheel, seat, and window assemblies, said the audit addressed to the Defense secretary for acquisition, the Air Force secretary, the Air Force inspector general and the Defense Contract Management Agency. The federal contracting offices and the corporate teams working on the plane are supposed to ensure the sustaining parts are delivered “ready for aircraft maintenance personnel to install on the aircraft,” as well as have an Electronic Equipment Logbook assigned that spells out each part's history and remaining life. Too often, however, the parts arrived not ready in accordance with contracts and incentive fees on the sustainment contracts because of “inflated and unverified F‑35A aircraft availability hours. This occurred because the [Joint Program Office] did not conduct adequate oversight of contractor performance related to receiving F‑35 spare parts and aircraft availability hours,” the report said, calling the inflation of hours unintentional. As a result, the department received non-ready spare parts and spent up to $303 million in labor costs since 2015, “and it will continue to pay up to $55 million annually” for such parts until a fix is made. In addition, the Defense Department has “potentially overpaid” $10.6 million in performance incentive fees by not independently collecting and verifying aircraft availability hours. “The lack of available [ready-for-issue] spare parts could result in the F‑35 fleet being unable to perform required operational and training missions,” the report warned. The Joint Program Office was aware of the problem, auditors found during their review from June 2018 to April 2019, but did not resolve the issue or require the services to better track the non-compliant parts. Interviews with the Joint Program Office staff in Arlington, Va.; the DCMA administrative office in Lockheed Martin's facility in Fort Worth, Texas; and Lockheed staff at three sites found, for example, that of 74 spare parts delivered to Hill Air Force Base in Utah from Sept. 17-30, 2018, 59 spare parts (80 percent) were non-ready for issue. Of the 263 spare parts delivered to Luke Air Force Base in Arizona in June 2018, 213 spare parts (81 percent) were non‑ready. And of 132 spare parts delivered to the Marine Corps Air Station in Beaufort, S.C., in September 2017, 58 spare parts (44 percent) were non‑ready. The IG recommended that the F-35 program executive officer improve oversight by coordinating with DCMA to pursue compensation from the contractor for the costs of mishandling the supply of spare parts since 2015. It also recommended that he direct the contracting officer to add clarifying language to future sustainment contracts, and task the lead contracting office with updating its Quality Assurance Surveillance Plan. Navy Vice Adm. Mathias Winter, the program executive, agreed, stating that there is value added in tracking and using contractor performance data. https://www.govexec.com/defense/2019/06/pentagon-lockheed-martin-failed-ensure-proper-parts-f-35/157822/

  • First ten armoured vehicles promised to Ukraine to be delivered by summer, Blair says | CBC News

    28 avril 2024 | International, Terrestre

    First ten armoured vehicles promised to Ukraine to be delivered by summer, Blair says | CBC News

    Defence Minister Bill Blair says the first ten of 50 Armoured Combat Support Vehicles (ACSVs) promised to Ukraine last year will be delivered to the war-torn country by this summer, but likely won’t be fully in service until the fall.

  • Boeing’s KC-46 tanker now has a pathway for autonomous aerial refueling

    9 avril 2020 | International, Aérospatial

    Boeing’s KC-46 tanker now has a pathway for autonomous aerial refueling

    By: Valerie Insinna WASHINGTON — Last week's deal between Boeing and the U.S. Air Force on a fix for the KC-46 could pave the way for the tanker to refuel other aircraft without a person needed to manually control the process, a top service official said Thursday. On April 2, Boeing agreed to fix the KC-46's troubled Remote Vision System by creating an overhauled RVS 2.0 with new hardware and software. Air Force acquisition executive Will Roper told reporters those changes would include the addition of 4K high-definition cameras that will display imagery in color as well as modern processors and LiDAR (light detecting and ranging) sensors that will help improve depth perception. “A proper RVS like that is right on the doorstep to autonomy,” Roper said. “All you have to do is take that data that tells the world inside the jet the reality of geometries between the airplane and the boom outside the jet. Once you have that, you simply need to translate it into algorithms that allow the tanker to tank itself.” The KC-46's Remote Vision System has been a thorn in the side of the aircraft program since 2017, when issues with the system were first discovered. The RVS is basically a suite of cameras, sensors and software that is supposed to allow boom operators sitting inside the aircraft to safety steer the boom into the aircraft needing fuel. But in certain conditions, the system produces distorted imagery that increases the risk of the boom hitting another aircraft. The new LIDAR system will be key to fixing that problem, said Roper, who likened it to a backup camera on a car that also provides cues to a driver for parallel parking or assessing whether a vehicle is aligned flush to a curb. “We'll have something very similar to that for the boom operators, so telling them are they left, right and how close are they getting to the airplane,” he said. “[It's] something very intuitive and easy to work with, and I think that will help significantly with them understanding their distance [from the other aircraft] because LIDAR is extremely accurate.” Because Boeing is locked into a firm fixed-price contract for the development of the KC-46, it will have to pay for the upgrade to RVS 2.0 out of its own pocket, as the Air Force maintains that the current system does not meet requirements. But the service is so confident in the prospect of using the RVS 2.0 as a stepping stone to an autonomous tanker that it included an option in last week's agreement to fund the development of technologies that enable autonomous or semiautonomous refueling. “We have added an engineering change proposal into the deal with a not-to-exceed threshold of $55 million, so that when RVS 2.0 is done, we can then take the next step beyond 2.0 to develop those autonomy algorithms and install them if we think we can certify them for safe use,” Roper said. “We took that step because, one, we're excited about being on the doorsteps of autonomy and, [two], we wanted to send a clear signal in the deal that this is our tanker for the future,” he said. If the Air Force decides to move forward with those design changes, more will need to be done to hammer out the contractual details, said Jamie Burgess, Boeing's KC-46 program manager. “There was no commitment one way or another on who pays for what. But there's definitely a strong partnership between Boeing and the Air Force as far as developing this technology,” he said. Autonomous refueling capability has been of increasing interest to the Air Force over the past few years, as sensing and artificial intelligence technologies grow by leaps and bounds. Boeing previously signaled it could include such technology as part of a menu of potential upgrade options for the KC-46, as reported by FlightGlobal in 2018. https://www.defensenews.com/air/2020/04/08/boeings-kc-46-tanker-now-has-a-pathway-for-autonomous-aerial-refueling

Toutes les nouvelles