Back to news

July 16, 2020 | International, Naval

Congress skeptical of Navy’s unmanned vessels plans

The U.S. Navy wants $464 million for unmanned surface vessels, but Congress is not on the same page.

Legislators have so far declined to fully fund the massive investment into research and development for large and medium unmanned surface vessels as they work through the annual defense bill, citing the request as “excessive procurement ahead of satisfactory testing.”

Among other things, that budget request would give the Navy $239 million to purchase two Overlord large unmanned surface vehicle (LUSV) prototypes for testing.

While the Senate Armed Services Committee has declined to authorize any of the $464 million request, the House Armed Services Committee agreed to authorize just $270 million of that request — specifically cutting funding for the two LUSVs. Instead, the House version would provide the Navy $45 million to convert a Spearhead-class expeditionary fast transport ship into a LUSV for further testing.

In a report on the bill issued by the Senate Armed Services Committee, lawmakers argued that the Navy already has the LUSVs that can fill the Strategic Capabilities Office's needs in this area.

But perhaps more importantly, the committee members do not seem convinced that LUSVs are ready for prime time.

“The committee remains concerned that the budget request's concurrent approach to LUSV design, technology development, and integration as well as a limited understanding of the LUSV concept of employment, requirements, and reliability for envisioned missions pose excessive acquisition risk for additional LUSV procurement in fiscal year 2021,” the report reads. “The committee is also concerned by the unclear policy implications of LUSVs, including ill-defined international unmanned surface vessel standards and the legal status of armed or potentially armed LUSVs.”

Furthermore, legislators remain unconvinced that the current unmanned vessels can hold up to the physical environment of extended operations at sea. While the Navy requires its unmanned platforms to be able to operate continuously at sea for 30 days without maintenance or repairs, the committee report notes the Strategic Capabilities Office's prototypes have only demonstrated two to three days of continuous operation.

The Senate version of the bill would require the Navy to formally qualify two main engines and electrical generators — including successfully demonstrating 30 days of continuous operations at sea — before Milestone B approval is granted.

An industry group hit back July 9.

In a letter to leaders of the Senate and House Armed Services Committees, the Association for Unmanned Vehicle Systems International called on legislators to fully fund the Navy's fiscal 2021 request.

“It is imperative that Congress continues to fund the research and development (R&D) efforts included in the Navy's FY21 budget request,” wrote President and CEO Brian Wynne. “Failing to do so will disrupt the significant investment industry has made in unmanned systems over the last several years. The severe reduction in funding being considered in the FY21 NDAA would eliminate jobs, drive many small companies out of business, and cause larger companies to shift their R&D investments to more stable opportunities”

The committee report argues that its requirements do not delay these programs, but in fact will enable the delivery of unmanned surface vehicles faster by ensuring they are “capable, reliable and sustainable.”

In the meantime, the Navy has moved forward with its unmanned surface vehicle efforts.

On July 13, the Navy awarded L3Harris $35 million to develop a medium unmanned surface vehicle prototype, with an option to buy eight more later on. If all options are exercised, the contract could be worth up to $294 million.

“The award of Medium USV is the culmination of a great dialogue with industry to right-size the requirements for a capable, reliable, and affordable unmanned surface vehicle that will employ a variety of modular payloads,” said Capt. Pete Small, program manager of Unmanned Maritime Systems within the Unmanned and Small Combatants Program Executive Office. “Leveraging new rapid prototyping authorities and mature commercial technology will allow us to quickly deliver a capable prototype to the Surface Development Squadron to conduct experimentation and learning in support of the Navy's plans for a future fleet incorporating unmanned vessels.”

The prototype is expected to be delivered in fiscal 2023. However, the Navy press release announcing the award notes that funding for future MUSV prototypes is uncertain. While the Navy has asked for additional fiscal 2021 funding for a second MUSV prototype in fiscal 2023, that acquisition strategy is yet to be determined.

https://www.c4isrnet.com/unmanned/2020/07/15/congress-skeptical-of-navys-unmanned-vessels-plans/

On the same subject

  • China taps Mideast airshow to prime regional defense cooperation

    November 20, 2023 | International, Land

    China taps Mideast airshow to prime regional defense cooperation

    U.S. military officials have described a trend of Beijing trying to displace regional countries' ties with Washington.

  • Army Materiel Command boss says logistics are key to future warfare

    March 31, 2023 | International, Land

    Army Materiel Command boss says logistics are key to future warfare

    "Gone are the days when we had everything down to your favorite ice cream," warns Gen. Charles Hamilton.

  • Why the Navy wants more of these hard-to-find software developers

    April 20, 2018 | International, Naval

    Why the Navy wants more of these hard-to-find software developers

    By: Mark Pomerleau With a relative dearth of cyber expertise in the military, Congress mandated last year the services begin direct commissioning pilot programs. The Navy, however has been doing direct commissioning for highly skilled software engineers for a few years, albeit on a small scale. The cyber warfare engineer (CWE) program is a highly competitive program with officers on five year rotations performing software or tool development for cyber operators. CWEs serve as members of the cyber mission force, the Navy's cyber mission force teams that serve as the cyber warriors for U.S. Cyber Command, producing cyber tools, but can also conduct target analysis, vulnerability research, and counter-measure development against malicious cyber activities. Since 2011, the Navy has only recruited 25 of these commissioned officers to its ranks. “Twenty-five developers in the Navy as military officers is definitely not enough,” Lt. Christopher Liu, the most senior cyber warfare engineer told Fifth Domain in an interview at the Navy League's Sea Air Space conference April 9. With a relative dearth of cyber expertise in the military, Congress mandated last year the services begin direct commissioning pilot programs. The Navy, however has been doing direct commissioning for highly skilled software engineers for a few years, albeit on a small scale. The cyber warfare engineer (CWE) program is a highly competitive program with officers on five year rotations performing software or tool development for cyber operators. CWEs serve as members of the cyber mission force, the Navy's cyber mission force teams that serve as the cyber warriors for U.S. Cyber Command, producing cyber tools, but can also conduct target analysis, vulnerability research, and counter-measure development against malicious cyber activities. Since 2011, the Navy has only recruited 25 of these commissioned officers to its ranks. “Twenty-five developers in the Navy as military officers is definitely not enough,” Lt. Christopher Liu, the most senior cyber warfare engineer told Fifth Domain in an interview at the Navy League's Sea Air Space conference April 9. “We definitely need to increase the billets and increase the amount that we can hire ... to have more talents to be able to work on the cyber mission,” he said. “As soon as the number increases, we'll be able to expand the program rather than just five years to eight years, hopefully make it into a 20 year career so people can get trained up and work on missions and not be forced into different fields.” The Pentagon has been besieged by concerns about the DoD's ability to both retain and attract cyber talent among its ranks when similar jobs in the private sector pay significantly more. Vice Adm. Michael Gilday, commander of 10th Fleet/Fleet Cyber Command, acknowledged in recent congressional testimony that the military is not competitive with the private sector and noted that the base pay for the CWE position is around $37,000 a year. “That's what we pay somebody to answer the phones around here,” Senator Claire McCaskill, responded to Gilday interrupting him in frustration. “We're asking them to have incredible expertise. That seems to me totally unrealistic.” Some current CWEs feel the work they're doing inside the Navy has greater meaning than similar work they did in the private sector. “I find that this is a lot more fulfilling,” Ensign Jordan Acedera, the most junior CWE told Fifth Domain. “You finish a project, you're given something that's a lot more challenging and that really tests you.” For Lt. (j.g.) George John, who was formerly writing software at a stock trading company, work with the CWE provides a better environment that's not driven so much by profit margins and hitting quarterly revenue targets. “We don't have to worry about profitability or bringing to market,” he said. “We can pursue a little more ... what's possible. Throw stuff against the wall, see what sticks, take our time to figure out a plan of action.” One of the biggest challenges, however, is lack of knowledge of the program, even inside the Navy. “You still walk across captains and commander who say 'CWE, what in god's name is that,” John said. With more CWE personnel in the force, the Navy could build a more informed and skilled software engineering cadre, the group said. “There's tons of software. Everybody has some type of software pet project,” John said. “To be able to get more CWEs on those things and coordinate with one another and say here's what [Consolidated Afloat Networks and Enterprise Services] is doing with their communications and their infrastructure. How are we doing that differently on the base side? You can talk and address security concerns with one another. Just within the cyber operations realm, Liu said, as the headcount increases, the CWEs could work on the requirements the operational community within the cyber mission force rather than having to prioritize projects. They could even start to look at developing capability prior to a specific requirement coming in as a means of staying ahead of the game as opposed to waiting for and reacting on requirements from operators. https://www.defensenews.com/digital-show-dailies/navy-league/2018/04/11/why-the-navy-wants-more-of-these-hard-to-find-software-developers/

All news