×

Please register to view this content

First Name
Last Name
Company
Job Title
Country
State
Opt me in to receive communications from Mercury Systems
Thank you
Error - something went wrong!
   

White Paper: Managing Life Cycle and Network Interoperability Challenges on Navy Platforms

Learn how commercial open computing strategies used by social media giants and advanced manufacturing practices employed by the automotive and logistics industries can be leveraged by the Navy to:

  • Improve interoperability
  • Lower costs
  • Enable technology upgrades

Whitepaper Excerpt

Navy combat, C4ISR [command, control, communications, computers, intelligence, surveillance, and
reconnaissance], and machinery control systems are characterized by a wide range of programs, all of which have their own system architecture, configuration, and composition, mostly program-specific and irrespective of adjacent systems. This disconnected environment creates roadblocks to cost-effective technology refresh and generates institutional inefficiencies, resulting in increased program expense in the long term and less effective warfighting capabilities overall. However, open computing strategies – such as those initiated by social media giants Facebook and LinkedIn – as well as manufacturing practices common in the auto and freight transport industry can be leveraged by the Navy embedded computing industry to solve the interoperability and long-term cost challenges created by these disparate systems.

 

Previous Article
Can GPS be Trusted? Part 1
Can GPS be Trusted? Part 1

Learn why commercial GPS position, navigation and timing (PNT) cannot be trusted for critical systems. Part...

Next Article
Can GPS be Trusted? Part 2
Can GPS be Trusted? Part 2

In part 2 of this blog series, learn what Assured PNT (A-PNT) is and how a trusted PNT system can still use...

×

Interested in our technology? Contact Sales

First Name
Last Name
Company
Country
State
Phone Number
Comments or Inquiry
Thank you, we will get back to you soon!
Error - something went wrong!