Nexus UI – A Fully Customizable Vehicle Interface

A configurable operator interface and integration layer for controls, telemetry, sensing and third-party hardware.

NEXUS UI – USER CUSTOMIZABLE

One interface.
Total control.

Nexus UI brings OMI's mechanical, electrical, energy, controls, software and integration capabilities together in one functioning vehicle architecture. The interface can be personalized by the end user and expanded with third-party hardware, accessories and connected features while keeping vehicle controls, diagnostics, telemetry, cameras and connectivity in one operator environment.

DEPLOYABLE ACROSS VEHICLE PLATFORMS

Nexus UI can be adapted for boats, submersibles, defense platforms, utility vehicles, trucks, drones and other specialized mobile equipment.

DISCUSS YOUR VEHICLE ARCHITECTURE →
OMI Nexus vehicle dynamics and camera interface
CONTROLVehicle and machine functions presented through one configurable interface.
TELEMETRYBattery, energy, diagnostics and operating data visible in real time.
SENSINGCamera and Eagle Eye inputs integrated into the same operator environment.
CONNECTIVITYRemote, cloud and third-party device integration designed into the platform.
OPEN ARCHITECTUREDesigned to accommodate customer-specific hardware, functions and workflows.
01 / CONFIGURABLE OPERATOR EXPERIENCE

The interface adapts to the vehicle—not the other way around.

Nexus can be configured around the OEM's machine functions, operating modes and hardware. Controls, data and third-party devices can be brought into a single operator environment rather than spread across separate displays and control boxes.

02 / SYSTEM INTEGRATION

Mechanical, electrical, controls and software working as one architecture.

Nexus is not simply a display. It is the visible operator layer of a broader system architecture that can coordinate power, controls, sensors, diagnostics and third-party hardware.

Vehicle controls

  • Drive-mode selection
  • Auxiliary functions
  • Machine / implement control
  • Operating-state visualization
  • Application-specific logic

Data & diagnostics

  • Battery and energy status
  • System diagnostics
  • Fault and warning display
  • Performance telemetry
  • Service information

Sensing & connectivity

  • Camera integration
  • Eagle Eye 360 capability
  • Remote access
  • Cloud connectivity
  • Third-party device integration
03 / OPEN VEHICLE ARCHITECTURE

Built to accept customer-specific hardware and functions.

A key Nexus differentiator is its ability to integrate third-party equipment into the same vehicle environment. OEMs can define the functions, sensors, accessories and controls required for their application while OMI engineers the electrical, software and user-interface integration.

Third-party hardware integrationAccessory controlsHand warmers and lightingAncillary equipmentSensor interfacesCamera systemsVehicle / machine diagnosticsRemote accessCloud connectivityCustomer-specific UI workflows
OMI Nexus configurable vehicle interface
04 / OEM APPLICATION DEVELOPMENT

Use Nexus as a platform, then configure it around the customer application.

OMI can support the OEM from system definition through hardware integration, UI development, validation and production implementation.

Define

  • Operator requirements
  • Vehicle functions
  • Hardware interfaces
  • Data and diagnostic needs

Integrate

  • Controls and software
  • Sensors and cameras
  • Battery / power systems
  • Third-party equipment

Validate & Deploy

  • Vehicle testing
  • UI refinement
  • Fault / diagnostic validation
  • Production configuration
ONE PLATFORM. MULTIPLE APPLICATIONS.

Controls. Software. Sensing. Connectivity. Integration.

Nexus demonstrates how OMI can bring multiple engineering disciplines together in a configurable architecture built around an OEM's specific machine.

DISCUSS YOUR NEXUS APPLICATION →