Joint All-Domain Command & Control (JADC2)
Download our capabilities overview to read how EIZO is uniquely positioned to help implement JADC2 with broad capability for supporting mission-critical data.
Why OpenVPX?
The US Department of Defense and other users are mandating improved implementation of open standards and interoperability. VPX specifications have been focused at the board level, but there is also a need for considering system-level requirements to improve interoperability and reduce customization, testing, cost, and risk.
The goal of OpenVPX is to encourage the development of interoperable COTS modules by providing a set of vendor-neutral architectural guidelines for designers and integrators.
Open Architectures – We Design to Industry Standards
- VITA 47.x Environments, Design and Construction, Safety and Quality for Plug-In Units
- VITA 48.x VPX REDI
- VITA 65.x OpenVPX System
What is OpenVPX?
The standard defines OpenVPX system topologies to promote interoperability. OpenVPX is based on VITA 46.0 and 46.1 VPX standards that allow the design and implementation of high-speed, high-power switched fabric-based systems. OpenVPX (VITA 65) was designed as a system-level VPX specification which defines backplane and board level profiles from COTS vendors to ensure interoperability of products used in developing systems and subsystems.
