November 18, 2022 | International, C4ISR
Raytheon tests information-sharing technology with JADC2 in mind
The demonstration included two locations as well as a range of hardware, waveforms and data formats.
July 14, 2020 | International, Naval
By PAUL MCLEARYon July 13, 2020 at 5:37 PM
WASHINGTON: Despite deep and bipartisan skepticism from Capitol Hill over its plans to build three new classes of unmanned warships, the Navy went ahead today with its plans to begin building as many as 40 Medium Unmanned Surface Vessels.
The service awarded L3 Technologies Inc. a $34.9 million contract for a prototype MUSV, along with an option for up to eight additional ships. If the company builds those eight unmanned ships, the contract will be worth $281 million through June 2027.
Overall, the Navy wants to build about 40 MUSVs in coming years, which will clock in at between 45 to 190 feet long, with displacements of roughly 500 tons. The medium ships are thought to skew more toward mission modules revolving around intelligence, surveillance and reconnaissance payloads and electronic warfare systems.
In their versions of the 2021 National Defense Authorization Act, however, both the House and Senate told the Navy to slow down on its acquisition of some unmanned ships, specifically the Large Unmanned Surface Vessel. Both documents boost Congressional oversight over the LUSV, an ambitious new ship the Navy hoped to begin building in 2023.
While the MUSV will focus on gathering intelligence, the LUSV will act as a forward-deployed missile launcher, bristling with missile tubes and other weapons, Navy planners have said.
Lawmakers are looking to ensure the Navy finalizes its design and operational plans before building the larger ship, something the service has struggled with as it built other classes such as the Littoral Combat Ship, the Ford class of aircraft carriers, and the Zumwalt destroyers, all of which fell behind schedule, went over budget and struggled with new technologies.
“USVs are one of the centerpieces of distributed maritime operations,” Rear Adm. Casey Moton, head of the Unmanned and Small Combatants office, said last month at a U.S. Naval Institute event. The ships will act as platforms to enable the fleet to spread out and counter China's ambitions in the Pacific either as a forward screen for a carrier strike group or as vessels pressed forward with an acceptable risk of attrition.
The Navy hasn't yet fully prepared to deploy or sustain a new fleet of unmanned vessels, Capt. Pete Small, program manager for unmanned maritime systems said in May. “Our infrastructure right now is optimized around manned warships,” Small said. “We're gonna have to shift that infrastructure for how we prepare, deploy, and transit” over large bodies of water before the navy begins churning out unmanned ships in greater numbers, he added.
https://breakingdefense.com/2020/07/navy-inks-deal-for-new-unmanned-fleet
November 18, 2022 | International, C4ISR
The demonstration included two locations as well as a range of hardware, waveforms and data formats.
March 3, 2020 | International, Aerospace, Naval
Un Rafale de la Marine nationale vient d'effectuer son premier vol avec une pièce imprimée en 3D avec succès : dessinée et prototypée sur le porte-avions Charles de Gaulle, la pièce est un boîtier de commande de vidanges des réservoirs de carburant. C'est une première pour la marine qui peut ainsi compter sur la fabrication additive pour concevoir des pièces détachées rapidement et proposer diverses itérations à moindre coût. Le composant final a été imprimé en 3D par Dassault Systèmes et pourrait bien être le premier d'une longue série. En février 2019, le porte-avions Charles de Gaulle s'équipait d'une imprimante 3D, probablement d'une machine de bureau à dépôt de matière fondue, afin de concevoir toutes sortes d'objets pour dépanner l'équipage parti en mission. Un ravitaillement ou une réparation en pleine mer est très coûteux et long, un temps que les techniciens de la Marine nationale ne peuvent parfois pas s'offrir. La fabrication additive pourrait être une première solution : en ayant une imprimante 3D à bord du porte-avions, son équipage produirait ce dont il a besoin sur place, s'affranchissant de nombreuses contraintes. La Marine nationale possède aujourd'hui 40 Rafale, dont 28 en ligne. C'est aujourd'hui l'avion de combat le plus moderne en service sur le territoire français. L'Etat-major des armées (EMA) explique qu'une équipe de techniciens de la Marine nationale a proposé d'utiliser l'imprimante 3D à bord du porte-avions Charles de Gaulle pour imaginer différentes pièces détachées intégrées à leur Rafale. Ils ont donc dessiné une maquette de renfort qui a ensuite été imprimée en 3D sur le bateau directement. L'EMA ajoute : “Le projet est immédiatement retransmis à la Direction de la maintenance aéronautique pour analyse au sein du plateau technique central mis en place dans le cadre du premier marché verticalisé de la flotte et rassemblant les spécialistes étatiques et industriels du domaine.” Le marché évoqué concerne le contrat RAVEL obtenu en mai 2019 par Dassault Aviation et ce pour une durée de 10 ans. Celui-ci a notamment pour objectif d'assurer l'entretien des Rafale, une assistance technique et une meilleure gestion des stocks. Après quelques jours d'études, le modèle imprimé sur le porte-avions a été adapté afin que le groupe Dassault puisse imprimer en 3D un produit fini. On ne sait pas quels matériaux et technologie ont été utilisés mais les pièces auraient été montées sur l'ensemble des Rafale embarqués dans le cadre de la mission Foch qui a débuté le 22 janvier dernier. La direction de la maintenance aéronautique (DMAé) conclut : « L'endommagement d'un aéronef en mer étant plus sévère qu'à terre, il revient à la DMAé de calculer et d'anticiper les besoins des différents aéronefs embarqués pour soutenir au mieux les équipes du porte-avions dans leur travail quotidien. » La fabrication additive pourrait donc répondre à ces objectifs et aider les équipes à concevoir des pièces détachées plus rapidement et efficacement. On espère que d'autres Rafale pourront être équipés de pièces imprimées en 3D ! En attendant, vous pouvez retrouver davantage d'informations ICI. https://www.3dnatives.com/rafale-marine-nationale-impression-3d-03032020/
October 2, 2020 | International, C4ISR
Andrew Eversden 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/