Generic Vehicle Architecture (GVA)

What is GVA?

Generic Vehicle Architecture (GVA) is a UK Ministry of Defence standard that defines how electronic systems inside military land vehicles should work together. Think of it as a common language that allows all the different computers, screens, sensors, and equipment inside a military vehicle to communicate seamlessly.

An Everyday Analogy

Imagine if every appliance in your home used a different type of electrical outlet. Your toaster would need one plug, your kettle another, and your phone charger yet another. You'd need adapters everywhere, and replacing any appliance would be complicated and expensive.

GVA solves this problem for military vehicles. Instead of every piece of equipment speaking its own language and using its own connectors, GVA provides:

• One common data network – like Wi-Fi for your vehicle's systems
• Standardised connectors – equipment plugs in the same way across all vehicles
• Unified screens and controls – crew members see the same familiar interface in any GVA vehicle

Why Does GVA Matter?

🎯 The Problem GVA Solves

Before GVA, military vehicles often had:

✅ The GVA Solution

GVA creates an "open architecture" – a standardised framework where:

• Equipment from different manufacturers works together – like how any USB device works on any computer
• Upgrades are simpler – swap out old equipment for new without redesigning the whole vehicle
• Crews train once – the same familiar screens and controls across all GVA vehicles
• Costs reduce over time – more suppliers can compete, driving down prices

Key Benefits of GVA

For Vehicle Crews

👤 Familiar Interface Everywhere

• Same screen layouts, menus, and controls across all GVA vehicles
• Reduced training time when moving between vehicle types
• Intuitive operation reduces workload in high-stress situations

For Vehicle Maintenance

🔧 Easier to Maintain and Upgrade

• Health monitoring systems track vehicle condition automatically
• Standardised diagnostics across the fleet
• Faulty equipment can be quickly identified and replaced

For Defence Acquisition

💷 Better Value for Money

• Multiple suppliers can provide compatible equipment
• Reduced integration time and cost for new capabilities
• Longer vehicle service life through easier technology refresh

The Land Data Model (LDM)

What is the Land Data Model?

The Land Data Model is the vocabulary and grammar that GVA systems use to communicate. Just as human languages have dictionaries and rules, the LDM defines:

Why is This Important?

When a fuel sensor wants to tell the crew display how much fuel is left, both systems must agree on:

1. What to call it – "Fuel Level" not "Tank Amount" or "Gas Remaining"
2. How to measure it – litres, not gallons or percentages
3. When to send it – every second, or only when it changes

The LDM standardises all of this, ensuring that:

• A fuel sensor from Company A can talk to a display from Company B
• New equipment understands existing systems immediately
• All vehicles report data in the same format for fleet management

LDM Versions

The Land Data Model evolves as new capabilities are added:

How Information Flows in a GVA Vehicle

The Publish-Subscribe Model

GVA uses a communication pattern called publish-subscribe (or "pub-sub"). Here's how it works:

How it works:

1. Publishers send information to the network without knowing who's listening

   • "The engine temperature is 85°C"

2. Subscribers receive only the information they're interested in

   • The display shows temperature to the crew
   • The computer logs it for maintenance records

3. Nobody needs to know about each other

   • Add a new display? It just subscribes to the information it needs
   • Remove a sensor? The network adapts automatically

This is called DDS (Data Distribution Service) – an industry standard used in many demanding applications including air traffic control and medical devices.

GVA Services in Our Software

Our LDM SDK provides ready-to-use implementations of key GVA services:

🔔 Alarms Service

Manages warnings and alerts across the vehicle platform.

The Alarms Service ensures that critical warnings reach crew members consistently, following the GVA specification for how alarms are presented, acknowledged, and cleared.

📋 Registry Service

Keeps track of all devices and systems on the vehicle.

When a new piece of equipment connects to the GVA network, it:

1. Requests registration – "Hello, I'm a thermal camera, model XYZ"
2. Receives an ID – The registry assigns it a unique identifier
3. Becomes visible – Other systems can now find and communicate with it

This is similar to how devices on your home network get IP addresses automatically.

📊 Usage and Condition Monitoring (UACM)

Automatically tracks vehicle health for maintenance purposes.

UACM data helps maintainers know which vehicles need attention before they break down – moving from "fix when broken" to "maintain when needed".

🖥️ Human-Machine Interface (HMI)

The GVA HMI standard ensures consistent crew interfaces:

• Standardised screen layouts – Same areas for status, controls, and information
• Common control patterns – Familiar buttons and navigation
• Role-based access – Commanders, drivers, and operators see appropriate information

Our Software Stack

Architecture Overview

Available Applications

Development Tools

Getting Started

For Developers

1. Build the SDK – Follow the Quick Start Guide
2. Run the examples – See real GVA communication in action
3. Explore with LDMX – Monitor live data traffic

For System Integrators

1. Understand your LDM version – Match your project requirements
2. Define your topics – What information will you publish and subscribe to?
3. Integrate with our wrappers – Qt6 signal/slot classes make integration straightforward

For Project Managers

1. GVA Compliance – Our SDK helps meet Def Stan 23-09 requirements
2. Multi-vendor support – DDS interoperability means flexibility in equipment choices
3. Reduced risk – Proven implementations of GVA services