February 1, 2024 | International, Naval
Vendors are pitching their systems’ cheaper costs in comparison to other expensive technologies that carry out similar missions.
October 3, 2023 | International, Land, Security
OTS was awarded a similar contract in February 2023 for M795 LAP facilitization of 20,000 rounds per month
September 24, 2020 | International, Aerospace, Naval, Land, C4ISR, Security, Other Defence
Aaron Mehta WASHINGTON — While the phrase “tsunami of data” seems to have exited everyday use by Defense Department officials, the problem remains the same: The Pentagon simply cannot exploit the sheer amount of information that comes in every day to its fullest. It's a challenge that will only get worse as more sources of information come online, with each branch having its own data sets, which often don't talk to each other. At the same time, the lack of ability to properly sort, catalog and exploit the data means the department cannot fully achieve its goals of using artificial intelligence to its fullest. After almost a decade of talking about the problem, military leaders appear to have a target date for when the department will get its arms around the problem, according to Gen. John Hyten, the vice chairman of the Joint Chiefs of Staff. By 2030, the Pentagon expects handling data will no longer be an overwhelming challenge, Hyten said Monday during an event organized by the Defense Innovation Unit. But, he added, the department is looking at any way to move that date closer, including by reworking how requirements are developed in the Joint Requirements Oversight Council, or JROC, a group chaired by Hyten, which serves as an oversight body on the development of new capabilities and acquisition efforts. Currently, “a service develops the capability, it comes up through the various coordination boards in the JROC, eventually getting to the JROC where we validate a service concept and make sure it meets the joint interoperability requirement,” Hyten explained. “But what was intended is the JROC would develop joint requirements and push those out to the services and tell the services ‘you have to meet those joint requirements.'” To get back to that top-down model, Hyten plans to push out a list of joint requirements for two major department priorities in all domain command and control and logistics for joint fires, which will have specific requirements for data and software. “They're not going to be the traditional requirements that you've looked at for years, capability description documents and capability production documents. They're going to capabilities and attributes that programs have to have,” he said. “And if you don't meet these, you don't meet the joint requirements and therefore you don't get through the gate, you don't get money. That's how we're going to hold it.” Hyten added that the goal is to have those data requirements out to the services around the end of the year, shortly after the expected publication of the new joint warfighting concept. That concept — which Hyten has previously described as essentially eliminating lines between units and services on the battlefield — inherently relies on the ability to combine data to be successful, he noted. https://www.defensenews.com/pentagon/2020/09/23/hyten-to-issue-new-joint-requirements-on-handling-data/
August 12, 2020 | International, Naval
By: David B. Larter WASHINGTON – The U.S. Navy Saturday commissioned its latest littoral combat ship amid a top-level push to fix the ship's nagging reliability issues and forge a path to make the small surface combatants useful in the years ahead. The monohull Freedom-variant LCS St. Louis was commissioned at a private event in its namesake city, the 22nd LCS and 10th Freedom variant to join the fleet. There will be 35 LCS in the fleet once all are commissioned. Change is in the wind for LCS once again, which has already seen several shakeups to its system. A high-level effort is underway to address problems with its complicated drive train built for high speeds that have limited the ships availability for tasking as well as to finally field its long-delayed mission packages. Mission packages will make the ships either a surface warfare hull, a mine hunter or an antisubmarine ship. Chief of Naval Operations Adm. Michael Gilday told Defense News in a July 16 interview that he was preparing to increase LCS deployments by two-and-a-half times over the next two years to finally shake out how to best employ the ships, as well as develop a plan to finally field the mine and ASW mission modules. “There are things in the near term that I have to deliver, that I'm putting heat on now, and one of them is LCS,” Gilday said. “One part is sustainability and reliability. We know enough about that platform and the problems that we have that plague us with regard to reliability and sustainability, and I need them resolved. “That requires a campaign plan to get after it and have it reviewed by me frequently enough so that I can be sighted on it. Those platforms have been around since 2008 — we need to get on with it. Experts who spoke to Defense News in July said the Navy would most likely need to accept less capability than they had planned for the ships to have if the service is to get the most out of the ships. https://www.defensenews.com/naval/2020/08/10/us-navy-commissions-another-littoral-combat-ship-amid-renewed-push-to-fix-the-program/