Def Stan 23-09 Part 2

Defence Standard 23-09
Part 2
Issue 03 Date: 17 May 2013
_______________________________________
Generic Vehicle Architecture (GVA)
Human Machine Interface
_______________________________________
DEF STAN 23-09 Part 2 Issue 3
Contents
Foreword................................................................................................................................................. vi
0 Introduction ...................................................................................................................................... 1
0.1 Purpose .................................................................................................................................. 1
0.2 Application of the Standard ....................................................................................................1
0.3 Precedence ............................................................................................................................ 1
1 Scope............................................................................................................................................... 2
2 Warning ........................................................................................................................................... 2
3 Normative References..................................................................................................................... 2
4 Abbreviation and Definitions............................................................................................................ 3
4.1 Abbreviations ......................................................................................................................... 3
4.2 Definitions............................................................................................................................... 3
5 GVA Human Machine Interface....................................................................................................... 6
5.1 Introduction ............................................................................................................................ 6
5.2 GVA HMI Components........................................................................................................... 6
5.3 GVA Display Screen .............................................................................................................. 6
5.4 Operation with Night Vision Aids............................................................................................ 7
5.5 Display Blackout..................................................................................................................... 7
5.6 Environmental Factors ........................................................................................................... 8
5.6.4 Reflectance and Glare ....................................................................................................... 8
5.6.5 Viewing Distance and Direction ......................................................................................... 8
5.7 Control and Input Devices......................................................................................................9
5.8 Hand Controllers .................................................................................................................. 11
5.9 Hard Control Panel............................................................................................................... 12
5.9.1 General Principles ........................................................................................................... 12
6 GVA HMI Modes and Crew Roles................................................................................................. 13
6.1 GVA HMI Modes ..................................................................................................................13
6.2 Vehicle Crew Roles.............................................................................................................. 14
7 Presentation and Layout................................................................................................................ 14
7.1 Display Layout...................................................................................................................... 14
7.2 Status Information Bar .........................................................................................................16
7.3 Top Level Menu Buttons ...................................................................................................... 17
7.4 Common Function Labels and Buttons................................................................................ 17
7.5 Reconfigurable Labels and Buttons ..................................................................................... 18
7.6 Plan Position Indicator ......................................................................................................... 19
7.6.2 Example Images of the PPI ............................................................................................. 20
7.7 Symbology............................................................................................................................ 21
7.8 Use of Colour ....................................................................................................................... 21
7.9 Text and Icons...................................................................................................................... 22
8 Top Level Menus ........................................................................................................................... 25
8.1 General Principles................................................................................................................ 25
i
8.2 GVA Functional Areas.......................................................................................................... 26

8.3 GVA Functional Area Descriptions ...................................................................................... 26
8.3.2 Additional Guidance......................................................................................................... 31
8.4 System Start Up ................................................................................................................... 31
9 Data Entry...................................................................................................................................... 31
10 Alerts.............................................................................................................................................. 32
10.1 General Principles................................................................................................................ 32
10.2 Alarms .................................................................................................................................. 32
10.2.1 Alarm Categories ............................................................................................................. 32
10.2.2 Terminology ..................................................................................................................... 33
10.2.3 Visual Presentation of Alarms.......................................................................................... 33
10.2.4 Alarms Menu Page .......................................................................................................... 34
10.3 Threats ................................................................................................................................. 36
10.3.2 Visual Presentation of Threats......................................................................................... 36
10.3.3 Threats Menu Page ......................................................................................................... 36
10.4 Audio Presentation of Alerts................................................................................................. 37
Annex A. Abbreviations ................................................................................................................... 39
Annex B. GVA Human Machine Interface Requirements Table (DOORS Baseline 1.0)................ 41
1 GVA Human Machine Interface (HMI)................................................................................................ 41
1.1 GVA HMI ......................................................................................................................................... 41
1.2 GVA Display Screen........................................................................................................................ 41
1.2.1 GVA Display Screen Characteristics............................................................................................ 41
1.2.2 Operation using Night Vision Aids................................................................................................ 42
1.2.3 Display Blackout ........................................................................................................................... 43
1.2.4 Viewing Distance and Direction.................................................................................................... 43
1.3 Controls & Input Devices ................................................................................................................. 44
1.3.1 Bezel Buttons ............................................................................................................................... 44
1.3.2 Physical Keyboards ...................................................................................................................... 44
1.3.3 On-Screen Keyboards .................................................................................................................. 45
1.3.4 Touch Screens ............................................................................................................................. 45
1.4 Hand Controllers.............................................................................................................................. 46
1.4.1 General Principles ........................................................................................................................ 46
1.4.2 Hand Control of Weapon/Sight Systems...................................................................................... 47
1.5 Hard Control Panel .......................................................................................................................... 48
1.5.2 HCP Layout .................................................................................................................................. 48
1.5.3 HCP Labelling............................................................................................................................... 48
1.5.4 HCP Conventions ......................................................................................................................... 49
2 GVA HMI Modes and Crew Roles...................................................................................................... 50
2.1 GVA HMI Modes.............................................................................................................................. 50
2.2 Management of System Control...................................................................................................... 50
ii
2.3 Vehicle Crew Roles ......................................................................................................................... 51

3 GVA HMI Display Presentation and Layout ....................................................................................... 51
3.1 Display Screen Layout..................................................................................................................... 51
3.2 Status Information Bar..................................................................................................................... 51
3.3 Top Level Menu Buttons.................................................................................................................. 53
3.4 Common Function Labels and Buttons ........................................................................................... 53
3.4.1 Bottom Bezel Button Function Allocation ..................................................................................... 53
3.5 Reconfigurable Labels and Buttons ................................................................................................ 54
3.6 Plan Position Indicator..................................................................................................................... 54
3.6.2 Weapon Orientation...................................................................................................................... 56
3.6.3 Sight Orientation........................................................................................................................... 56
3.6.4 Threat Warning Indication ............................................................................................................ 56
3.7 Symbology....................................................................................................................................... 56
3.8 Use of Colour................................................................................................................................... 56
3.8.1 Use of colour across the GVA HMI .............................................................................................. 56
3.8.2 Use of Colour on the GVA Display Screen .................................................................................. 57
3.9 Text and Icons ................................................................................................................................. 58
3.9.1 Size 58
3.9.2 Text Case ..................................................................................................................................... 58
3.9.3 Fonts 59
3.9.4 Labelling ....................................................................................................................................... 59
4 Top Level Menus ................................................................................................................................ 60
4.1 General Principles ........................................................................................................................... 60
4.2 GVA Functional Areas ..................................................................................................................... 61
4.3 GVA Functional Area Descriptions.................................................................................................. 61
4.3.1 SA - Situational Awareness.......................................................................................................... 61
4.3.2 WPN - Weapons........................................................................................................................... 63
4.3.3 DEF - Defensive Systems ............................................................................................................ 65
4.3.4 SYS - Systems ............................................................................................................................. 65
4.3.5 DRV - Driver ................................................................................................................................. 66
4.3.6 STR - Special to Role ................................................................................................................... 67
4.3.7 COM - Communication ................................................................................................................. 67
4.3.8 BMS - Battlefield Management System........................................................................................ 67
4.4 System Start Up .............................................................................................................................. 68
5 Data Entry........................................................................................................................................... 68
6 Alerts................................................................................................................................................... 69
6.1 Visual Presentation of Alarms ......................................................................................................... 69
6.1.1 Warnings ...................................................................................................................................... 69
6.1.2 Cautions ....................................................................................................................................... 70
6.1.3 Advisories ..................................................................................................................................... 71
6.2 Alarms Menu Page .......................................................................................................................... 71
iii
6.2.1 Alarm Menu Information ............................................................................................................... 71

6.2.2 Alarm Menu Functions.................................................................................................................. 72
6.3 Visual Presentation of Threats ........................................................................................................ 73
6.4 Threats Menu Page ......................................................................................................................... 73
6.5 Audio Presentation of Alerts............................................................................................................ 74
6.6 Audio Speaker System .................................................................................................................... 76
iv
Requirements Tables
Table 1 GVA HMI Components Requirement .........................................................................................6
Table 2 GVA Display Screen Characteristic Requirements .................................................................... 7
Table 3 Operation using Night Vision Aid Requirements ........................................................................ 7
Table 4 Display Blackout Requirements ................................................................................................ 8
Table 5 Viewing Distance and Direction Requirements .......................................................................... 9
Table 6 Control and Input Devices Requirements ................................................................................ 10
Table 7 Hand Controller Requirements................................................................................................. 11
Table 8 Hard Control Panel General Principal Requirements............................................................... 12
Table 9 Hard Control Panel Control Conventions Requirements.......................................................... 13
Table 10 Modes and System Control Management Requirements ...................................................... 14
Table 11 GVA Display General Principle Requirement......................................................................... 15
Table 12 Status Information Bar Requirements .................................................................................... 17
Table 13 Top Level Menu Selection Buttons Requirements ................................................................. 17
Table 14 Common Labels and Button Requirements ........................................................................... 18
Table 15 Reconfigurable Label and Button Requirements ................................................................... 18
Table 16 PPI Indicator General Principle Requirements....................................................................... 20
Table 17 Symbology Requirement ........................................................................................................ 21
Table 18 Use of Colour Requirements .................................................................................................. 22
Table 19 Text and Icon Requirements .................................................................................................. 24
Table 20 Top Level Menu General Principle Requirements ................................................................. 26
Table 21 Functional Area Requirement................................................................................................. 26
Table 22 GVA HMI Functional Area Requirements .............................................................................. 31
Table 23 Data Entry Requirements ....................................................................................................... 32
Table 24 Visual Presentation of Alarm Requirements .......................................................................... 34
Table 25 Alarms Menu Requirements................................................................................................... 36
Table 26 Visual Presentation of Threat Requirements ......................................................................... 36
Table 27 Threats Menu Page Requirements ........................................................................................37
Table 28 Audio Presentation of Alerts Requirements ........................................................................... 38
Figures
Figure 1 Example of a QWERTY On-Screen Keyboard ....................................................................... 10
Figure 2 Example of a 'phone style' On-Board Keyboard ..................................................................... 11
Figure 3 GVA Display Presentation and Layout.................................................................................... 15
Figure 4 Examples of the PPI with weapon and sight orientation icons ............................................... 20
Figure 5 Examples of the PPI with bar threat indication icons .............................................................. 20
Figure 6 Example of the PPI with lollipop threat indication icons.......................................................... 21
Figure 7 Soft Key Labels Colours and States ....................................................................................... 24
Figure 8 Recommended character sizes at different viewing distances ............................................... 25
v
Foreword
AMENDMENT RECORD
Amd No. Date Text Affected Signature and Date
REVISION NOTE
Iss No. Date Text Affected Signature and Date

3.0 June 2012 There have been significant changes to
GVA HMI aspects of Def Stan 23-09 Issue
2.
A DOORS requirements set has been

created based on the textual content of Def
Stan 23-09 Issue 2 and the GVA HMI
Definition Document. The DOORS
requirement set included in this document
is at Baseline 1.0
There has been significant rewording to

remove ambiguity, reduce duplication and
to align with other Parts of 23-09.
The intent is that the requirements are now

easier to use and contract against within a
vehicle platform SRD.
Added Requirements
GVA_HMI_22 - Display screen Blackout

vehicle interlocks
GVA_100-104 Added requirements for
locking/unlocking of functions between GVA
HMIs
GVA_HMI_113 – Extra Position grid display
formats required
GVA_HMI_277-283 Added requirements for
map displays in BMS functional area
Amended Requirements
GVA_HMI_58-65 – Update to hand controller

requirements
GVA_HMI_67-74 Updates to Weapon and
Sight controller requirements
GVA_HMI_107 – PPI replaces Compass
Rose/GPI
GVA_HMI_124-143 – Update to allocation of
functions to bezel buttons for common function
labels and buttons
GVA_HMI_161-169 Compass rose
requirements updated to PPI requirements
GVA_HMI_182 – 185 – RGB values added
vi
GVA_HMI_182 – Text colour change to white

from yellow
GVA_HMI_338 – Provision for 2 spare audio
tones instead of one.
Cancelled Requirements
GVA_HMI_96 –Def Stan 23-09 Part 2 now only

covers an “operational” mode. Training mode
and maintenance mode requirements removed.
Will be addressed in future issues
Requirements for linking of crew roles to

functions removed.
Requirements for symbology sets removed
HISTORICAL RECORD
Defence Standard 23-09 Issue 3 supersedes Defence Standard 23-09, Issue 2, dated 21st October
2011 and the associated guidance and definition documents.
GENERAL NOTES
a) Defence Standard (Def Stan) 23-09 has been produced on behalf of the Ministry of Defence (MOD)
by UK Defence Standardization (DStan).
b) Def Stan 23-09 has been agreed by the Authorities concerned with its use and is to be applied to
all future Land vehicle platform designs, orders, contract action and whenever practicable by
amendment to those already in existence. If any difficulty arises which prevents application of the Def
Stan, the GVA Office shall be informed through the UK MOD project or delivery team concerned so
that a remedy may be sought.
c) Please address any enquiries regarding this Def Stan, whether in relation to an Invitation to Tender
(ITT) or to a contract in which it is incorporated, to the responsible technical or supervising authority
named in the ITT or contract.
d) Compliance with Def Stan 23-09 shall not in itself relieve any person from any legal obligations
imposed upon them.
e) Def Stan 23-09 has been devised solely for the use of the MOD and its contractors in the execution
of contracts for the MOD. To the extent permitted by law, the MOD hereby excludes all liability
whatsoever and howsoever arising (including, but without limitation, liability resulting from negligence)
for any loss or damage however caused when the Def Stan is used for any other purpose.
f) Def Stan 23-09 includes the technical aspects for Health and Usage Monitoring Systems (HUMS)
and supersedes Def Stan 25-24 (Health and Usage Monitoring Capability for Land Platforms).
Development of Def Stan 23-09
a) Def Stan 23-09 has been developed through the collaborative efforts of the MOD and industry, and
builds on the extant Vehicle Systems Integration (VSI) research project and previous research work
including the Vehicle Technology Integration Demonstrator (VTID).
b) There are a number of areas in which further work is needed and future iterations of Def Stan 23-
09 will be expanded to cover these as relevant technologies and processes develop to the appropriate
level of maturity.
vii
c) Def Stan 23-09 shall be reviewed, revised and re-released as necessary.
Arrangement of Def-Stan 23-09
Part 0 – GVA Approach
Part 1 – GVA Infrastructure
Part 2 – GVA Human Machine Interfaces (HMI)
Part 3 – GVA Health Usage Monitoring System (HUMS)
Part 4 – GVA Physical Interfaces (TBC)
Defence Standard 23-09 is structured so that requirements pertinent to each technical area are
presented in a table with an accompanying description of the requirements. Each part of Def Stan 23-
09 also includes an annex which contains a more detailed requirements set relevant to that part. The
annexes bring together the requirements contained within each part along with the justifications,
measures of performance and verification associated with them. This should allow delivery teams to
construct more consistent GVA system requirements and vehicle platform integrators to better
understand how to achieve GVA compliance.
MOD Point of Contact:

GVA Office, Director Land Equipment, Defence Equipment and Support, MOD Abbey Wood, Bristol
BS34 8JH. E-mail: DESLE-DEFSTANS@mod.uk
viii
0 Introduction
0.1 Purpose
0.1.1 The purpose of Def Stan 23-09 is to enable the MOD to realise the benefits of an open
architecture approach to Land vehicle platform design and integration, especially in regard to
the vehicle platform electronic and power infrastructure and the associated Human Machine
Interface (HMI). The aim is to improve operational effectiveness across all Defence Lines of
Development (DLOD), reduce integration risks, and reduce the cost of ownership across the
fleet by applying appropriate standards and design constraints.
0.1.2 Defence Standard 23-09 is an architecture requirements document and should be used to
create appropriate equipment solutions by influencing the specific vehicle platform/project
technical requirements. The standard is written in the context of informing MOD departments
and industry supplying equipment.
0.2 Application of the Standard
0.2.1 Def Stan 23-09 is owned, sponsored and managed by the Director Land Equipment (D LE),
Defence Equipment and Support (DE&S), as the authority on behalf of the MOD and it is to
be applied to all future land vehicle platform and vehicle platform installed, sub-system
procurement, including current vehicle platform refurbishment and upgrade programmes.
0.2.2 The processes required to be undertaken by delivery teams for the application of Defence
Standard 23-09 throughout the acquisition cycle, will be published in a Joint Services
Publication (JSP). This JSP is yet to be created but when published; it will be linked to
Defence Standard 23-09. These aspects are currently addressed in Part 0 of this Defence
Standard.
0.2.3 Def Stan 23-09 is applicable to the full spectrum of land vehicle platforms, ranging from
simple to complex implementations. The requirements for these implementations are
determined by the functionality required of the vehicle platform as a whole system including
all sub-systems, and not the automotive or power elements alone. The requirements
address both equipments to be fitted as part of the initial operating capability and those likely
to be fitted through life. These requirements are expressed in the System Requirements
Document (SRD) and/or the Sub-System Requirements Documents (SSRDs) for the
individual vehicle platforms concerned.
0.2.4 It is important to understand where systems are not compliant with the requirements of Def
Stan 23-09 and why. Deviations from Def Stan 23-09 shall be agreed by the GVA Office in
conjunction with the project or delivery team concerned through a process which agrees the
requirements that are applicable to a particular project. After tailoring, the agreed GVA
system requirements for a specific project will be baselined and recorded by the Delivery
team and the baseline supplied to the GVA Office.
0.3 Precedence
0.3.1 Def Stan 23-09 shall be considered the foundation standard for new build and legacy
upgrade vehicle platform architectures, and should any conflict arise between this and other
extant documentation referenced by this Def Stan, this document shall take precedence,
unless otherwise agreed with the GVA Office.
1
1 Scope
1.1 The application of Def Stan 23-09 is mandatory within the UK Ministry of Defence, on new
and legacy upgrade vehicle projects. It specifies requirements and the standards to be used
in the design and implementation of Land vehicle platform electronic and power
infrastructures, physical interfaces, HMI and Health & Usage Monitoring Systems (HUMS).
2 Warning
2.1 The MOD, like its contractors, is subject to both United Kingdom and European laws
regarding health and safety at work. Many Defence Standards set out processes and
procedures that could be injurious to health if adequate precautions are not taken.
Adherence to those processes and procedures in no way absolves users from complying
with legal requirements relating to health and safety at work.
3 Normative References
3.1 The documents and publications shown in the list below are referred to in the text of this part
of the Def Stan. Documents and publications are grouped and listed in alpha-numeric order:
APP6A Military Symbols for Land Based Systems
BS5499 (Parts 1-6) Safety Signs, Including Fire Safety Signs

BS EN ISO 9241-
Ergonomics of Human-System Interaction
303:2008E
Human Factors for Designers of Equipment- Military Land
Def Stan 00-25 Part 14
Vehicle Design
Def Stan 00-250 Human Factors for Designers of Systems
Road Vehicles – Symbols for Controls, Indicators and
ISO 2575:2010
Tell-tales
Graphical symbols for use on equipment – Registered
ISO 7000:2012
Symbols
Ergonomic requirements for office work with visual display
ISO 9241-11:1998
terminals (VDTs) -- Part 11: Guidance on usability
STANAG 2211 (Edition 6) Geodetic Datums, Projections, Grids and Grid References
3.2 Reference in Def Stan 23-09 to any normative references refers to, in any ITT or contract,
the edition and all amendments current at the date of such tender or contract, unless a
specific edition is indicated. For some standards, the most recent editions shall always apply
due to safety and regulatory requirements.
3.3 In consideration of the clause above, specifiers shall be fully aware of the issue, amendment
status and application of all normative references, particularly when forming part of an ITT or
contract. Responsibility for the correct application of standards rests with specifiers.
3.4 UK DStan can advise regarding where to obtain normative referenced documents. Requests
for such information can be made to the DStan Helpdesk. Details of how to contact the
helpdesk are shown on the outside rear cover of Def Stans.
2
4 Abbreviation and Definitions

4.1 Abbreviations
4.1.1 Abbreviations referred to in this part of Def Stan 23-09 are given in Annex A
4.2 Definitions
4.2.1 For the purposes of Def Stan 23-09, the following terms and definitions apply:
4.2.1.1 Base Vehicle: The basic vehicle structure and those systems needed to enable it to perform
its automotive functions and mobility. Where fitted it also includes those systems needed to
control turrets and other physical elements e.g. a mine plough.
4.2.1.2 Base Vehicle Sub-System: A system that forms part of the base vehicle
4.2.1.3 BCIP (BOWMAN): BCIP (Bowman) is the principal tactical command and control system for
Land Forces, including supporting aviation and amphibious elements. BCIP provides secure
voice communications and is delivering increasingly capable data communications,
situational awareness and interoperability. The BCIP acronyms is derived from the following
elements:
B Bowman (HF, VHF and UHF radio systems)
C ComBAT (software tools for battlefield planning and management)
I Infrastructure (items such as printers, servers and computers)
P Platform Battlefield Information System Application (hardware and software)
4.2.1.4 Crewstation: A physical position in a vehicle platform occupied by a person fulfilling one or
more vehicle crew operational roles.
4.2.1.5 Electronic Architecture: The interfaces and protocols to be used when fitting vetronics
based sub-systems to a vehicle platform that support the vehicle crew to undertake their
operational tasks.
4.2.1.6 Generic Vehicle Architecture (GVA): The term ‘Generic Vehicle Architecture’ refers to the
open, modular and scalable architectural approach applied to the design of vehicle platforms
to deliver the MOD’s desired operational, technical and cost benefits.
4.2.1.7 GVA Compliant: GVA Compliant applies to a whole vehicle platform and means:
a) GVA Data Infrastructure connected physical power interfaces comply with the
requirements of Def Stan 23-09.
b) GVA Data Infrastructure sub-system physical data interfaces comply with the
requirements of Def Stan 23-09.
c) GVA Data Infrastructure data interfaces are DDS enabled.
d) Data Infrastructure data flows conform to the format requirements of the GVA Data
Model.
e) GVA Data Infrastructure sub-systems controlled via the GVA HMI
f) Information presentation and sub system control conforms to GVA HMI requirements
g) Vehicle video distribution conforms to Def Stan 00-82
h) HUMS minimum data set captured from vehicle sub-systems via DDS
i) All physical interfaces conform to Def Stan 23-09 where applicable.
4.2.1.8 GVA Data Infrastructure: The physical cables and connectors that provide means of
distributing data around a base vehicle. It also includes any enabling logical components and
functions e.g. interface software, transport protocols and message definitions.
4.2.1.9 GVA Data Model: A logical information model describing the data topics (messages) to be
exchanged between vehicle sub systems via publish and subscribe middleware.
4.2.1.10 GVA Display: The term used for the GVA display screen and bezel buttons mounted around
the edge.
3
4.2.1.11 GVA HMI: The vehicle platform crewstation display and controls that are common between
different physical positions in a vehicle platform, it is used to control a number of vehicle
platform sub-systems. The GVA HMI includes controls and operator input devices and
means of presenting information to the operator such as the display screen, bezel buttons,
any associated keyboards, hand controllers and hard control panel.
4.2.1.12 GVA Interface Panel: A panel installed in a vehicle platform that provides connection to the
GVA power and data infrastructure.
4.2.1.13 GVA Power Infrastructure: The physical cables, connectors and other components that
provide the means of distributing electrical power around a vehicle platform.
4.2.1.14 GVA Office: The MOD GVA Office is the authority for all matters relating to Def Stan 23-09
and can be contacted through the GPOC (See General Notes).
4.2.1.15 GVA Ready: GVA Ready applies at a sub-system level and means that sub–systems and
components have been developed to a level where they can be efficiently integrated within a
“GVA Compliant” whole vehicle EA system. This would mean:
j) Physical power interfaces comply with the requirements of Def Stan 23-09.
k) Physical data interfaces comply with the requirements of Def Stan 23-09.
l) Applicable data interfaces are DDS enabled.
m) Data flows conform to the format requirements of the GVA Data Model.
n) Video distribution conforms to Def Stan 00-82
4.2.1.16 Hard Control Panel: Control panels, separate from the main GVA display in a vehicle
platform that houses one or a number of hard switches and/or indicators used to control or
monitor safety /security or mission critical functions.
4.2.1.17 Hard Switching: The ability to control or operate a sub-system using physically based
means.
4.2.1.18 Health and Usage Monitoring System (HUMS): A generic term for the technology used on
platforms to gather process and store system data onboard a vehicle platform.
4.2.1.19 Infrastructure: The underpinning hardware and software that is used to connect multiple
sub-systems together.
4.2.1.20 Modular: A modular architecture is designed in such a way as to allow the replacement or
addition of sub-systems and upgrades as required without any undesirable emerging
properties.
4.2.1.21 Open: Openness is defined as the use of published and freely available standards to define
software and hardware interfaces, in order to allow a common approach to be taken. An
open standard has no barriers to implementation by a third party. Open standards facilitate
rapid replacement and upgrade of equipment as required. Open standards are used
throughout Def Stan 23-09.
4.2.1.22 Operational System: The complete item that can be used for military purposes which
includes the equipment Lines of Development e.g. base vehicle and items needed from all
the other lines of development to create a viable system such as the vehicle crew.
4.2.1.23 Operator: Any person required to interface and control vehicle platform sub-systems via the
GVA HMI
4.2.1.24 Platform Equipment (PE): (refer to Def Stan 61-5) the original equipment fitted to COTS
and MOTS platforms at procurement. These systems are permanent and connected to the
Platform Power Distribution System. The classification, Platform or Terminal Equipment,
shall be decided at the Power Critical Design Review.
4.2.1.25 Power Management: The process of prioritising and controlling the electrical power loads
throughout the vehicle platform.
4.2.1.26 Soft Switching: The ability to control or operate a sub-system using software functionality.
4
4.2.1.27 Sub-Systems: Separable elements or collections of equipment or software added to a base

vehicle that provide operationally required capabilities over and above those delivered by the
base vehicle.
4.2.1.28 Vehicle Platform: The base vehicle and all its integrated sub-systems
4.2.1.29 Terminal Equipment (TE): (refer to Def Stan 61-5) Equipment that is fitted to COTS and
MOTS platforms to make them fit for purpose. These systems can be permanent or
temporary, and are connected to the platform or APU using the Terminal Equipment Power
Distribution System. The classification, Platform or Terminal Equipment, shall be decided at
the Power Critical Design Review.
4.2.1.30 Vehicle Crew: All personnel located in the vehicle platform with defined roles needed to fulfil
the necessary operational functions
4.2.1.31 Vehicle Users: The individuals and groups of people who interact locally to operate,
support, sustain, maintain or otherwise interface directly with the Vehicle Platform and its
sub-systems through the GVA HMI.
5
5 GVA Human Machine Interface

5.1 Introduction
5.1.1 This part of Def Stan 23-09 defines the design principles and functional characteristics
against which the GVA Human Machine Interface (HMI) shall be designed. This includes, but
is not limited to: the display screen characteristics; functional areas; colour usage; and alerts
philosophy. These HMI “building blocks” can then be scaled according to the needs of a
particular application.
5.1.2 The aim of Def Stan 23-09 Part 2 is to provide requirements for the design and
implementation of HMIs in order to create, as far as is possible, a generic GVA HMI design
which can be used across a wide variety of vehicle platforms, to control, monitor or display
information from the majority of subsystems fitted to them. The GVA HMI needs to operate in
conjunction with an underpinning GVA electronic infrastructure as defined in Def Stan 23-09
Part 1. This will:
o) Minimise the number of HMIs required within the vehicle platform, reducing equipment
space, weight and power claims;
p) Ensure HMIs can be placed in optimised locations;
q) Simplify and standardise user interactions thereby reducing workload, training
requirements and the opportunity for human error.
5.1.3 The requirements and supporting guidance provided in Part 2 currently only covers the
operational mode of the system (not maintenance or training), and does not define detailed
descriptions of individual applications, nor does it negate the need for an HMI Design
Specification for specific projects. Furthermore, it does not cover any of the base platform
HMI features such as seating or direct vision.
5.1.4 The complete requirements table, containing the appropriate measures of performance and
justifications for the GVA HMI requirements can be found in Annex B. These are maintained
in a DOORS database and a copy of the DOORS module can be requested from the GVA
Office.
5.2 GVA HMI Components
5.2.1 The GVA HMI is the means by which the vehicle crew and maintainers interact with the
vehicle platform sub-systems.
5.2.2 Requirement Table 1 shows the requirement that relates to the components of the GVA HMI.
Unique Identifier Priority Requirement Text
GVA HMI
GVA_HMI_2 K The following items shall be included as part of the [GVA

HMI]:
a) GVA Display Screen
b) Bezel Buttons
GVA_HMI_353 1 Where necessary, the following items shall be included as
part of the [GVA HMI]:
a) Physical Keyboard
b) Audio interface to Headsets and Speakers
c) Hand Controller
d) Hard Control Panel
Table 1 GVA HMI Components Requirement
5.3 GVA Display Screen

5.3.1 Requirement Table 2 shows the requirements that relates to the characteristics of the GVA
display screen.
6
GVA Display Screen Characteristics
GVA_HMI_6 1 GVA display screens shall be capable of displaying at

least 256 (8 bit) level greyscale.
GVA_HMI_7 1 GVA display screens shall have a response time of less
than 16ms.
GVA_HMI_8 1 GVA display screens shall have a minimum resolution of
95 pixels per inch.
GVA_HMI_9 1 GVA display screens shall be a minimum of 18 bit colour
capable (24 bit colour - objective).
GVA_HMI_10 1 The backlight luminance of a GVA display screen shall
not vary by more than 5% over the whole surface.
GVA_HMI_11 1 GVA display screens shall have a minimum contrast ratio
of 50:1.
GVA_HMI_12 1 The luminance of the GVA display screen and backlit
labels on controls and dials shall be adjustable between
0-50 cd/m2.
GVA_HMI_13 1 There shall be a means to select between linked and
decoupled luminance adjustment of backlit labels on
controls and dials, and display screen.
Table 2 GVA Display Screen Characteristic Requirements
5.4 Operation with Night Vision Aids

5.4.1 It is the intention that the GVA HMI will be used in a range of different environmental
conditions. The use of displays at night has implications for the retention of night vision and
impacts on the use of night vision aids. Display luminance should be able to be lowered to a
point where it can be used at night without: significantly adversely affecting the dark
adaptation of the user, affect legibility when viewed with night vision aids, or adversely
affecting the colour palette of the display. Def Stan 00-250 Part 3 Section 13 provides
additional guidance on night vision.
5.4.2 Methods of preserving the sensitivity of the dark-adapted eye have importance for military
purposes. If an expected degree of dark adaptation is required, then pre-adapted personnel
should wear goggles that pass only long-wavelength (>620 nm) red light.
5.4.3 Requirements Table 3 shows the requirements for operating the GVA HMI whilst wearing
night vision aids.
Operation using Night Vision Aids
GVA_HMI_15 K The [GVA HMI] luminance shall be compatible with the

use of current in-service night vision aids.
GVA_HMI_16 K The range of luminance adjustment for all [GVA HMI]
equipment shall be compatible with the range of external
ambient night conditions expected in the operational
environment.
GVA_HMI_17 K It shall be possible to access and interpret the information
from the [GVA HMI] whilst wearing current in-service night
vision equipment.
Table 3 Operation using Night Vision Aid Requirements
5.5 Display Blackout

5.5.1 It is crucial that the GVA display screen(s) and bezel buttons can be quickly blacked out to
provide a covert or reduced light signature during operations. When the display screen and
7
bezel buttons are blacked out, the auditory aspect of the GVA HMI (tones are transmitted
through the headset) will not be affected.
5.5.2 Requirement Table 4 shows the requirements relating to display screen blackout.
Display Blackout
GVA_HMI_20 1 A hardware control shall be used to reduce the luminance

to zero (blackout) on a single [GVA display], including
screen and backlit bezel buttons, independent of the
underlying GVA processing.
GVA_HMI_21 1 The same hardware control used to blackout a [GVA
display] shall be used to restore luminance to the screen
and backlit bezel buttons.
GVA_HMI_22 1 It shall be possible to blackout the complete [GVA HMI] on
command from the vehicle platform blackout function or
interlock, independent of the underlying GVA processing.
GVA_HMI_23 1 Whenever a [GVA display] is blacked out, all input
functions, apart from the operation of associated hand
controllers, [Hard Control Panel], and the display blackout
switch shall be disabled.
Table 4 Display Blackout Requirements
5.6 Environmental Factors

5.6.1 There are no GVA HMI specific requirements for environmental factors to be included in this
Part. Therefore all the components of the GVA HMI shall meet the environmental
requirement for the vehicle platform as defined in the SRD.
5.6.2 When a GVA display is used outside the protection of the vehicle platform it should be
protected from environmental conditions, as specified in the SRD.
5.6.3 Rain falling on a display screen will distort any displayed image, to the point where text
becomes illegible. Display screens which are used outdoors should therefore be
mechanically shielded from such weather effects. In addition, any interaction with the display
should not be impeded by the effects of weather.
5.6.4 Reflectance and Glare
5.6.4.1 Reflections that cause glare and reduce screen contrast should be avoided. If necessary, the
screen should have antiglare and/or antireflection treatment. Unavoidable reflections should
be as small as possible. Specular reflections of ambient light sources (lamps, windows, etc.)
on a display screen reduce the contrast and thus the legibility of displayed information.
Often, they are the cause of glare, leading to discomfort or inability to recognize the
information for the user.
5.6.5 Viewing Distance and Direction
5.6.5.1 The recommended viewing distance of the display from the operator's normal operating
position is dependent on several factors, including: the task being conducted, display size,
information type and size being presented and whether this display is to be read whist on the
move.
5.6.5.2 Requirement Table 5 shows the requirements relating to viewing distance and direction.
Viewing Distance and Direction
GVA_HMI_29 1 The information on the [GVA display] shall be legible from

any angle of inclination up to 40° from a perpendicular
8
viewing direction, measured in any plane.

GVA_HMI_31 1 The [GVA display] shall be positioned between 500mm
and 635mm from the [operator]'s eyes to the centre of the
screen.
Table 5 Viewing Distance and Direction Requirements
5.7 Control and Input Devices

5.7.1 The nature of the input devices required will be dependent on the vehicle type, subsystems
fitted and the operator's role. It is possible that different input devices will be required to
provide functionality at different stages of an operation.
5.7.2 The GVA HMI controls and input devices include bezel buttons, physical keyboards, on-
screen keyboards touch screens and hand controllers.
5.7.3 Requirement Table 6 shows the requirements relating to bezel buttons, keyboards, touch
screen controls and other input devices.
Bezel Buttons
GVA_HMI_34 K The [GVA HMI] shall include hard buttons (bezel buttons),
positioned around the edge of the display screen:
a) 8 buttons across the top (Top Level Menu Buttons)
b) 8 across the bottom of the display (Common Function
Buttons)
c) 6 buttons on each side of the display (reconfigurable
Buttons)
GVA_HMI_35 K Where reconfigurable menus are used, each bezel button
shall be unambiguously associated with a label.
GVA_HMI_355 K Bezel buttons shall be the primary method of interaction
when the vehicle platform is in motion.
GVA_HMI_37 K The bezel buttons shall provide a tactile response to
indicate that the operation of a button has been
successful.
GVA_HMI_36 1 The size of the bezel buttons shall be in accordance with
guidance laid down in Def Stan 00-250 Part 3 Section 15.
GVA_HMI_38 1 Labels on the bezel buttons shall be backlit.
Physical Keyboards
GVA_HMI_44 K The [GVA HMI] shall be designed to prevent inadvertent
operation of any physical keyboard
GVA_HMI_43 K Physical keyboard keys shall provide a tactile response to
indicate that the operation has been successful.
GVA_HMI_42 1 The size of physical keyboard keys shall be in accordance
with guidance laid down in Def Stan 00-250 Part 3 Section
15.
GVA_HMI_45 1 Physical keyboards shall be able to be placed in a state
where the operation of the keys does not result in a
system response i.e. locked.
GVA_HMI_358 1 It shall not be possible to unintentionally "lock” a physical
keyboard.
GVA_HMI_46 1 Physical keyboards shall be able to be returned to a fully
operational state by the same method used to initiate a
lock.
GVA_HMI_47 2 The [GVA HMI] display should provide an indication that
the physical keyboard, key lock is in operation.
9
On Screen Keyboards
GVA_HMI_49 K On screen keyboards shall provide a visual response
when a key is selected.
Touch Screens
GVA_HMI_51 K Touch screens shall function with and without the
[operator] wearing gloves.
GVA_HMI_360 K There shall be a means to enable and disable any touch
screen.
GVA_HMI_52 K An alternative method of physical interaction shall be
provided in addition to any touch screen interaction.
GVA_HMI_54 1 On a touch screen, the size of soft keys or areas intended
to be selected or manipulated by touch shall be in
accordance with the guidance laid down in Def Stan 00-
250 Part 3 Section 15.
GVA_HMI_53 2 On a touch screen, the soft labels used to indicate the
functionality of bezel buttons should also act as soft keys.
Table 6 Control and Input Devices Requirements
5.7.4 Examples of onscreen keyboards are shown in Figure 1 and Figure 2.
Figure 1 Example of a QWERTY On-Screen Keyboard
10
Figure 2 Example of a 'phone style' On-Board Keyboard
5.7.5 N.B the colours applied to any on screen keyboard should follow the guidance in section 7.8
of this document and also be discussed with users as part of the User Centered Design
(UCD) approach.
5.8 Hand Controllers
5.8.1 Requirement Table 7 shows the requirements for the GVA HMI hand controllers including
the general set up and control of trainable weapons and sights.
Hand Controller General Set Up
GVA_HMI_58 K Weapon and sighting systems shall be controlled by a

hand controller.
GVA_HMI_361 K On screen cursors or pointing devices shall be controlled
by a hand controller.
GVA_HMI_362 K The weapon system, sighting system and cursor control
pointing demands shall be input using the thumb.
GVA_HMI_59 K All thumb controls shall be “stiff stick” (force transducer)
controller types
GVA_HMI_363 K The isometric operating force for the thumb controllers
shall be 9 to 22N.
GVA_HMI_364 K Thumb controls used for cursor pointing demand input
shall be accompanied by at least 1 "selection input" for
use with the same thumb.
GVA_HMI_64 K Control of trainable [sub-systems] and cursors shall be
implemented on separate hand controllers, or used by
different hands on a single hand controller.
GVA_HMI_65 K All hand controller buttons that perform 'critical' functions
shall have different tactile properties to any other button on
the same hand controller.
GVA_HMI_60 2 Control devices used for positional movement of [sub-
systems] on the hand controller should be able to provide
a tactile response to indicate an end of travel state.
Hand control of weapon / sight systems
GVA_HMI_67 K The manual demanded movement of a trainable weapon

or sight system shall require the simultaneous activation of
a safety mechanism and movement control.
GVA_HMI_68 1 Hand controllers used for sighting [sub-system] control
shall provide a mechanism to activate a laser range finder.
GVA_HMI_71 1 If a weapon or sight [sub-system] is automatically slewed,
the [GVA HMI] shall include an indication as to the
direction of travel it will take when it moves.
shall provide a mechanism to change the magnification
level.
shall provide a mechanism to change the Field of View
(FOV) of the sight.
GVA_HMI_74 1 Where sight systems are used that include more than one
sensor, the hand controllers used for sighting [sub-system]
control shall provide a mechanism to toggle between the
sensors.
Table 7 Hand Controller Requirements
11
5.8.2 The hand controllers should be mounted with consideration given to vibration isolation in
order to reduce the problem frequencies across the spectrum. This could include fixing them
to the seats depending on platform constraints.
5.8.3 The zoom behaviour (e.g. fixed level or continuous zoom or zoom linkage between cameras)
will be equipment dependant and therefore should be agreed with the users as part of the
UCD approach.
5.9 Hard Control Panel
5.9.1 General Principles
5.9.1.1 The GVA Hard Control Panel is a unit (or units) dedicated for functions which are identified
as being critically important from a safety or operational perspective (including GVA itself)
and these functions will be monitored and operated by dedicated controls.
5.9.1.2 Requirement Table 8 shows the requirements relating to the GVA HMI hard control panel.
Hard Control Panel General Principles
GVA_HMI_365 K Dedicated controls and indicators for operational or safety

critical functions shall be mounted on a [Hard Control
Panel](s).
GVA_HMI_77 K The controls on the [Hard Control Panel](s) shall be
designed according to Def Stan 00-250 Part 3 Section 15.
Table 8 Hard Control Panel General Principal Requirements
5.9.1.3 In vehicles that have a rear access door for passengers, a hard control panel (HCP) may be
required in the rear of the vehicle (e.g. to allow passengers to purge vehicle systems in case
the vehicle is abandoned).
5.9.1.4 To ensure that controls are optimally laid out on the control panel, analysis should be
conducted to determine the frequency of use and importance of each control function and to
identify any controls that form sensible functional groupings or are used together/in
sequence.
5.9.1.5 Requirement Table 9 shows the requirements relating to the design of the HCP including the
layout, labelling and control conventions.
Hard Control Panel Layout
GVA_HMI_81 2 Controls mounted on a [Hard Control Panel] which are

functionally similar should be grouped together.
GVA_HMI_82 2 Controls mounted on a [Hard Control Panel] which are
used in sequence should be laid out in the sequence in
which they will be typically used (left to right).
Hard Control Panel Labelling
GVA_HMI_86 K Where labelling is provided on the [Hard Control Panel]

rather than on the control, the following convention shall
be applied:
a) Where the control is located below head height, the
label shall be located above the control; to prevent it from
being covered by the hand when it is being operated
b) Where the control is located above head height the
label shall be located below the control; to prevent the
control from masking the label
12
GVA_HMI_84 1 Labelling of individual controls and groups of controls on

the [Hard Control Panel] shall be provided either on the
control panel itself or unambiguously associated with it.
GVA_HMI_85 1 Groups of related controls and associated indicators or
displays on the [Hard Control Panel] shall be bounded by
a border and a label provided within the border that
describes the grouping.
Hard Control Panel Conventions
GVA_HMI_91 K Where unintentional operation of a control is unwanted or

could have safety or mission critical consequences,
suitable protection of the control shall be provided.
GVA_HMI_88 1 The following recognised control conventions shall be
adopted if they are fitted on the Hard Control Panel:
a) Rotary Knobs: Knobs are suitable for high-precision
adjustments in the control of continuous variables, when
little force is necessary for operation, e.g. for small
potentiometers. A clockwise rotation shall increase the
controlled value or turn a system on and an anticlockwise
rotation shall decrease the controlled value or turn a
system off
b) Sliders: A motion to the right shall increase the
controlled value, turn a system on or move a cursor/
controlled system to the right and a motion to the left shall
decrease the controlled value, turn a system off or move a
cursor/ controlled system to the left
c) Arrows: An up arrow (i.e. push button) shall increase the
controlled value or move a cursor/ controlled system up
and a down arrow shall decrease the controlled value, turn
a system on or move a cursor/ controlled system down.
d) Unguarded Two Position toggle switches: Shall operate
with the down position corresponding to ‘On’ and the up
position corresponding to ‘Off’’
e) Unguarded three position toggle switches on the HCP:
the centre position shall correspond to ‘Off’
f) For arming a weapon system flip guarded toggle
switches shall be used where up is arm and down is safe
g) Emergency Stop: Where a user activated emergency
switch is required, it shall conform to Def Stan 00-250 part
3 Section 15.6.8.1
GVA_HMI_89 1 Indications shall be provided to reflect the status of the
functions which are controlled from the [Hard Control
Panel](s).
GVA_HMI_93 1 The spacing of controls shall comply with the requirements
detailed in Def Stan 00-250 Part 3 Section 15.6.
Table 9 Hard Control Panel Control Conventions Requirements
6 GVA HMI Modes and Crew Roles

6.1 GVA HMI Modes
6.1.1 The requirements and supporting guidance in this section covers the operational mode of the
system (not maintenance or training).
6.1.2 Requirement Table 10 shows the requirements relating to the GVA HMI modes and
management of system control.
13
GVA HMI Modes
GVA_HMI_96 K The [GVA HMI] shall provide an 'Operational mode' that

provides functions to enable the [vehicle crew] to
undertake their operational task.
GVA_HMI_97 K The [GVA HMI] shall clearly indicate the current mode
when not in the operational mode.
GVA_HMI_98 K Where changes of GVA mode include changes of [GVA
HMI] safety-related behaviour, the mode shall be selected
by way of a [Hard Control Panel].
Management of System Control
GVA_HMI_100 K [Vehicle platform] [GVA HMI]s shall be operable

independently of other [GVA HMI]s.
GVA_HMI_101 K Each [GVA HMI] in the [vehicle platform] shall be capable
of performing the functions of any [vehicle crew] role
except where role specialised controls are required.
GVA_HMI_102 K When a single [GVA HMI] is interacting with an interface or
controlling a [sub-system] those functions shall not be
available ('locked') to other [GVA HMI]s.
GVA_HMI_103 1 If a particular [GVA HMI] has initiated a 'lock' on GVA
interfaces or control of [sub-systems] then the 'lock' shall
be removable from a different [GVA HMI].
GVA_HMI_104 1 If a particular [GVA HMI] has initiated a 'system lock' on
control of GVA interfaces or control of [sub-systems], and
that [GVA HMI] has subsequently failed, then any 'system
locks' shall be automatically cancelled.
Table 10 Modes and System Control Management Requirements
6.2 Vehicle Crew Roles

6.2.1 Within the vehicle platform there may be a number of crew roles e.g. commander, driver and
gunner. Depending on the level of functionality of the vehicle, the commander may be
required to allocate roles to each GVA HMI by enabling or disabling sub-systems, thereby
managing the information and sub-system control available at each GVA HMI.
6.2.2 For some roles, the functionality available at their GVA HMI may need to change during the
course of the mission. For example, the driver may only require access to the functionality
required for driving tasks whilst the vehicle is in motion, but may need much greater access
to vehicle other sub-systems when static.
6.2.3 Access to the different sub-systems via the GVA HMI for different crew roles and the
possibility of having 'role profiles' should be addressed on a case by case basis.
7 Presentation and Layout
7.1 Display Layout
7.1.1 It is envisaged that the majority of operators will require a single screen, multifunctional
display. However, where a specific crew role requires it, and if the space allows, a GVA HMI
may employ two or more multifunctional displays located next to, or near to each other.
7.1.2 Figure 3 shows the layout of the GVA display (including the display screen and bezel
buttons. The image is provided for illustrative purposes only and it is not to scale.
14
Top Level Menu Buttons
Figure 3 GVA Display Presentation and Layout
7.1.3 Requirement Table 11 shows the general principle requirement relating to the layout of the
GVA display.
General Principles
GVA_HMI_107
K The [GVA display] will comprise of the following items:
a) Status Information Bar
b) Top Level Menu Buttons
c) Reconfigurable Labels and Buttons
d) Common Function Labels and Buttons
e) Plan Position Indicator
Table 11 GVA Display General Principle Requirement
15
7.2 Status Information Bar

7.2.1 The Status Information Bar contains essential status information to the operator and will be
present along the top of all GVA displays screen menu pages.
7.2.2 Requirement Table 12 shows the requirements relating to the Status Information Bar on the
GVA display screen.
Status Information Bar
GVA_HMI_109
K The Status Information Bar shows essential status
information and shall be present on all displays, unless
temporarily hidden.
GVA_HMI_111
K The Status Information Bar shall show the time and date,
displayed in 'Date Time Group' format on the far left hand
side.
GVA_HMI_113 The Status Information Bar shall show the [vehicle
K
platform's] position selectable between the following grid
formats:
MGRS - Military Grid Reference System
British National Grid Format
Irish Grid Format
Local Grid Format
GVA_HMI_366
K There shall be an indication on the GVA display screen of
the selected grid format.
GVA_HMI_115
K The Status Information Bar shall show the [vehicle
platform's] position grid reference in between the time date
group and the alarms.
GVA_HMI_116 K The number of current alarms shall be displayed on the far
right hand side of the Status Information Bar.
GVA_HMI_117 K The current alarms shall be displayed as active counters in

the format Wn, Cn and An (where n is the number of active
alarms in that category).
GVA_HMI_118
K The Status Information Bar shall show the current vehicle
heading in NATO angular mils (1 mil = 1/6400 of a circle)
consistent with the PPI selection.
GVA_HMI_110
1 It shall be possible to temporarily hide labels and the
Status Information Bar from the GVA display screen.
GVA_HMI_112
1 The Time Zone used to display of the 'date time group' on
the Status Information Bar shall be configurable on each
16
[GVA display].
GVA_HMI_114
1 The Status Information Bar shall show the vehicle
platform's grid reference in an 8 figure format plus any
leading characters.
Table 12 Status Information Bar Requirements
7.3 Top Level Menu Buttons

7.3.1 The GVA display includes 28 bezel buttons positioned around the outside of the display
screen (see figure 3).
7.3.2 The 8 along the top of the screen are the Top Level Menu Buttons. F13-F20, along the
bottom of the display are the Common Function Labels and Buttons and F1-F12 down the
sides are the Reconfigurable Labels and Buttons.
7.3.3 Requirement Table 13 shows the requirements which relate to the Top Level Menu Buttons
on the GVA display.
Priorit
Unique Identifier Requirement Text
y
Top Level Menu Buttons
GVA_HMI_120 K The Top Level Menu Buttons shall be used for the sole
purpose of selecting the functional area with which the
operator wishes to interact.
Table 13 Top Level Menu Selection Buttons Requirements
7.3.4 The functional areas are explained in more detail in Section 8.2 of this document.
7.4 Common Function Labels and Buttons
7.4.1 Requirement Table 14 shows the requirements relating to the Common Function Labels and
Buttons.
Common Function Labels and Buttons
GVA_HMI_124 K The bottom row of bezel buttons shall be reserved for

those controls that are used in many or all the GVA
Functional Areas.
GVA_HMI_125 K The label describing the functionality of each bottom bezel

button shall be provided on the display screen.
GVA_HMI_126 1 F13 shall be labelled 'Up' or 'Cancel' dependent on current

function.
GVA_HMI_127 1 F13 shall navigate up a level in the menu structure if a

dialog function is not active.
GVA_HMI_128 1 F13 shall be the equivalent to a cancel function if a dialog

function is active.
GVA_HMI_129 1 F14 shall be labelled ‘Alarms’.
GVA_HMI_130 1 Operation of F14 shall display the ‘Alarms’ table.
GVA_HMI_131 1 F15 shall be labelled ‘Threats’.
17
GVA_HMI_132 1 Operation of F15 shall bring up a display detailing all

threat events.
GVA_HMI_133 1 F16 shall be labelled ‘Ack’.
GVA_HMI_134 1 Operation of F16 shall acknowledge alerts, stopping any

associated audio tone.
GVA_HMI_135 1 F17 shall be labelled ‘Arrow Up’.
GVA_HMI_136 1 Operation of F17 shall scroll up through menu options or

increase values where required.
GVA_HMI_137 1 F18 shall be labelled ‘Arrow Down’.
GVA_HMI_138 1 Operation of F18 shall scroll down through menu options

or reduce values where required.
GVA_HMI_139 1 F19 shall be labelled ‘Labels’.
GVA_HMI_140 1 Operation of F19 shall hide or display the labels

associated with the bezel buttons, the Status Information
Bar and non critical overlays, such as the Plan Position
Indicator (PPI).
GVA_HMI_141 2 When operating F19, a multi-state function should be

implemented that provides the ability to select and hide
various combinations of display features.
GVA_HMI_142 1 F20 shall be labelled ‘Enter’.
GVA_HMI_143 1 Operation of F20 shall enter data into a form field, activate
a highlighted menu option or accept the input into a dialog
box.
GVA_HMI_367 1 The label describing the functionality of each common

function bezel button shall be provided on the display
screen.
Table 14 Common Labels and Button Requirements
7.5 Reconfigurable Labels and Buttons

7.5.1 The reconfigurable menu buttons labels are the active information tags associated with the
programmable functionality, which reconfigure depending on the page content.
7.5.2 Requirement Table 15 shows the requirements which relate to the Reconfigurable Labels
and Buttons
Reconfigurable Labels and Buttons

GVA_HMI_157 K Bezel buttons F1-F12, and associated on-screen labels,
shall be reconfigurable depending on the functional area
selected and the page content.
GVA_HMI_158 1 Where there are common functions within and across

functional areas and menu pages, these shall be allocated
to the same bezel button.
Table 15 Reconfigurable Label and Button Requirements
18
7.6 Plan Position Indicator

7.6.1.1 A Plan Position Indicator (PPI) shall be displayed on the GVA display screen. The PPI shall
display key tactical and operational information to the GVA HMI operators. This section
provides requirements and supporting guidance on the design of the PPI, including some
example images.
7.6.1.2 Requirements table 17 shows the general requirements relating to the Plan Position
Indicator (PPI).
PPI General Principles

GVA_HMI_161 K The Plan Position Indicator (PPI) shall be present by
default in the SA, WPN and DRV functional areas when
displaying video feeds.
GVA_HMI_163 K The PPI shall include:
a) A marker showing the orientation of North
b) 32 equally spaced marks around the edge
c) An icon to represent the vehicle platform, located at the

centre of the PPI, where the orientation of the vehicle
platform is clearly identifiable
d) An indication of the orientation of weapons in relation to

the vehicle platform body
e) A graphical view showing the orientation of any weapon

sights
f) An icon showing the position of any high priority threats
g) The position and size of the Field of View (FOV) of any

sensor selected in a specific functional area
GVA_HMI_165 K The PPI shall be located in the top left of the display
screen area by default.
GVA_HMI_167 K The PPI shall be ‘Heading’ Up on all non map displays.
GVA_HMI_168 K The PPI orientation shall be consistent with the map

orientation as selected on any map display.
GVA_HMI_169 K If a threat warning is received while the PPI is hidden, the

PPI shall reappear with an indication of the threat
orientation relative to the [vehicle platform].
GVA_HMI_166 1 The position of the PPI shall be configurable so it can be

optimally positioned for the page layout.
GVA_HMI_162 2 The PPI should be displayable in all functional areas.
PPI Weapon Orientation
19
GVA_HMI_171 K Weapon orientation shall be represented by a line which

can be seen against all potential background colours,
whilst not causing confusion by contradicting other colour
conventions.
Table 16 PPI Indicator General Principle Requirements
7.6.1.3 A heading readout line, (in mils) below the PPI may be considered as an option if the same
data is not displayed on the status bar.
7.6.1.4 Potential threats detected by equipment systems (e.g. shot detection systems) should be
shown, using symbology, around the edge of the PPI to indicate type and relative orientation
of the threat to the vehicle platform.
7.6.2 Example Images of the PPI
7.6.2.1 Some examples of the PPI, including icons which may be used for weapon orientation (blue
line), sight orientation (white lines) and threats (either red bars or lollipop icons) are shown in
Figure 4, Figure 5 and Figure 6. (N.B the background may be opaque)
Figure 4 Examples of the PPI with weapon and sight orientation icons
Figure 5 Examples of the PPI with bar threat indication icons
20
Figure 6 Example of the PPI with lollipop threat indication icons
7.7 Symbology
7.7.1 The symbology for the GVA HMI has not yet been agreed and standardised and therefore is
not included in this document. However where symbols are used, the following principles
should apply:
a) Symbols should be comprehensible.
b) If there is doubt that operators will recognise a symbol, then it should be supplemented
with a label.
c) The symbol should not be positioned on any rotary control, as the symbol will appear
upside down.
d) Symbols should be placed within a border to separate them from other display items.
e) Symbols should be only as complex as is required to support recognition, as too much
detail leads to symbols looking more similar.
7.7.2 Requirement Table 17Table 17 shows the requirement which relates to symbology on the
GVA HMI.
Symbology
GVA_HMI_175 1 Any symbols that are associated with hard controls that
rotate shall be located adjacent to the control.
Table 17 Symbology Requirement
7.7.3 As part of the UCD process, the design team and operators should agree a set of
standardised icons and / or text for the GVA HMI.
7.7.4 Many civilian standards and conventions exist concerning the design of symbols for different
domains, such as ISO 2575 for displays in road vehicles and ISO 7000 for symbols for use
on general equipment).
7.7.5 Similarly, specific standards already exist for symbols (and text) used in signs where
consistency and clarity of presentation is vital to understanding, e.g. BS 5499 (parts 1-6).
Standards are also in preparation for symbols or ‘icons’ used to represent control actions in
software GUIs. The designer should follow these standards where applicable.
7.7.6 On maps and BMS where a symbol is defined in APP6B, the NATO standard for Military
Symbology, then the symbol used may be as per APP6B. The APP6B symbols may be
scaled down or simplified for application on vehicle platform HMIs.
7.8 Use of Colour
7.8.1 Requirement Table 18 shows the requirements which relate to the use of colour on the GVA
Display and its graphical user interface. (The RGB values given in Table 18 relate to a 24 bit
colour numbering system.)
21
Use of Colour across the GVA HMI
GVA_HMI_177 K The [GVA HMI] shall comply with the colour conventions
stated in Def Stan 00-250 Table 15.2
GVA_HMI_178 K Colour coding shall only be used as a supplementary

method of presenting information.
GVA_HMI_184 K The following colour conventions shall be used across

the [GVA HMI]:
a) Green (RGB 0,255,0): On, Good, OK Safe
b) Yellow (RGB 255,255,0): Advisory Warning
c) Amber (RGB 255,153,0): Caution
d) Red (RGB 255,0,0): Armed, Danger, Critical Warning,

Failure, Stop
e) Grey (RGB 127,127,127): Not available or Off
f) Green (RGB value of 0,75,0). Background colour for

soft keys and soft key labels which are available for
selection
GVA_HMI_179 1 The number of combined background and foreground

colour combinations used shall be limited to 24 with the
exception of mapping and colour video.
Use of Colour on the GVA Display Screen
GVA_HMI_181 K The background colour shall be maintained across all

related areas of the GVA display screen.
GVA_HMI_180 1 No more than 7 colours shall be used on a GVA display

screen with the exception of mapping and colour video.
GVA_HMI_182 1 The text on soft keys and soft key labels shall be white
(RGB 255,255,255).
GVA_HMI_183 1 In text entry fields, text shall be black (RGB 0,0,0) on a

white (in a 24 bit colour system it shall be RGB
255,255,255) background.
GVA_HMI_185 1 Colours used for overlays, such as reticules, shall have a

high contrast with each other and all potential
background colours.
Table 18 Use of Colour Requirements
7.9 Text and Icons

7.9.1 The optimum size of a displayed character depends on the viewing distance, ambient
illumination, the importance of the text, numerals or symbols and the display medium.
7.9.2 Vibration and motion from the vehicle may make it difficult for the operator to read displays
or interact with controls.
7.9.3 Requirement Table 19 shows requirements which relates to text and icons on the GVA HMI.
22
Unique ID Priority Requirement Text
Text and Icons Size
GVA_HMI_188 1 Alphanumeric characters presented on the GVA display

screen shall subtend an angle of at least 0°22' vertically at
the [operator's] eye.
GVA_HMI_189 1 Alphanumeric characters presented on the GVA display

screen shall subtend an angle of at least 0°14' horizontally at
the [operator's] eye.
GVA_HMI_190 1 Icons presented on the GVA display screen shall subtend an

angle of at least 0°24' vertically at the [operator's] eye.
GVA_HMI_191 1 Icons presented on the GVA display screen shall subtend an

angle of at least 0°26' horizontally at the [operator's] eye.
GVA_HMI_192 1 No alphanumeric characters on the GVA display screen shall

subtend an angle of more than 0°37' vertically at the
[operator's] eye.
Text Case
GVA_HMI_194 K Block capitals shall only be used for headlines, key phrases
or acronyms.
GVA_HMI_195 K Labels and titles shall use an initial capital letter for each
word.
Font
GVA_HMI_197 K ‘Monospace typewriter’ font shall be used for all

alphanumeric characters on the GVA display screen.
Labelling
GVA_HMI_200 K Soft key labels shall indicate the function that will be
performed or the state that will be entered when the
associated bezel button is activated.
GVA_HMI_201 K Where it is not obvious what is currently displayed there shall

be a textual indication on the screen of the current displayed
state.
GVA_HMI_203 K Text shall be left aligned for labels on the left of the [GVA
display].
GVA_HMI_204 K Text shall be right aligned for labels on the right of the [GVA
display].
GVA_HMI_205 K Text shall be centrally aligned for labels along the top or
bottom of the [GVA display.]
GVA_HMI_206 K The style of the soft key labels shall change depending on
state:
a) A soft key label for a function which is available but not

selected shall have white text on a green background as
illustrated below.
23
b) A soft key label for a function which is available and

selected shall have white text on a green background, a
yellow border with a black outline
c) A soft key label for a function which is unavailable shall be

white text on a grey
The RGB values are specified in GVA_HMI_184.
GVA_HMI_370 1 All soft keys and hard controls shall be labelled with text
which provides a clear unambiguous representation of the
function, except where graphical representation has been
accepted by the operator community.
Table 19 Text and Icon Requirements
7.9.4 Figure 7 illustrates the presentation of the soft key labels when they are available, selected
or unavailable.
Figure 7 Soft Key Labels Colours and States
7.9.5 The recommended minimum, optimum and maximum character sizes (mm) for different
viewing distances are displayed in Figure 8.
24
12
Minimum Character Height (mm) - 20 min of Arc
11
Minimum Character Height (mm) for vibration effects - 22 min of Arc
10
Maximum Character Height (mm) - 37 min of arc
9
Character Size (mm)
0
0 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 950 1000 1050
Viewing Distance (mm)
Figure 8 Recommended character sizes at different viewing distances
8 Top Level Menus

8.1 General Principles
8.1.1 This section gives more detailed requirements and guidance relating to the Top Level Menus
and describes of what should be presented under each of the 8 GVA HMI functional areas.
8.1.2 Requirement Table 20 shows the requirement relating to the functional behaviour of the Top
Level Menus.
Top Level Menu General Principles
GVA_HMI_209 K The correct page shall be displayed within 1 second of

making a top level menu button selection.
GVA_HMI_210 K When a top level menu button is pressed once, for the
functional area currently selected, the top level menu
page for that functional area shall be displayed.
GVA_HMI_211 K When a top level menu button is pressed once, for a

different functional area than that currently selected, the
page that was last viewed for that functional area shall be
displayed.
GVA_HMI_212 K Pressing a top level menu button twice, for a different

functional area than that currently selected, shall display
the top level menu for that functional area.
GVA_HMI_218 K A green bar shall be displayed directly underneath top

level menu buttons that have available functions.
25
GVA_HMI_213 1 It shall take no more than three button presses to access

the most commonly used functions and those of
operational importance.
GVA_HMI_214 1 There shall be consistency with menu and option labels

across functional areas.
GVA_HMI_215 1 Drop down menus shall only be provided for

maintenance purposes, set-up functions or operational
reporting functions.
GVA_HMI_219 1 When a top level menu button is selected the displayed

green bar shall have a yellow outline.
GVA_HMI_220 1 A grey bar shall replace the green bar if a functional area
is temporarily unavailable.
GVA_HMI_374 2 If a functional area has not been implemented then the

bar should be black.
Table 20 Top Level Menu General Principle Requirements
8.2 GVA Functional Areas

8.2.1 The subsystems integrated onto the GVA infrastructure shall be split into the functional areas
which are selected by pressing the corresponding functional area bezel buttons positioned
along the top of the display.
8.2.2 Requirement Table 21 shows the requirements relating to the functional areas.
Functional Areas
GVA_HMI_376 K The top bezel buttons shall be labelled:
a) SA
b) WPN
c) DEF
d) SYS
e) DRV
f) STR
g) COM
h) BMS
Table 21 Functional Area Requirement
8.2.3 The top level bezel buttons may be labelled even without there being the underlying
functionality installed.
8.3 GVA Functional Area Descriptions
8.3.1 The default screens, after power up, shall be determined at the time of design; however
requirement Table 22 shows the requirements relating to the functional areas.
26
Situational Awareness
GVA_HMI_223 K Selecting SA shall provide access to the SA functional

area.
GVA_HMI_224 K The SA functional area shall display video feeds from the
LSA cameras fitted to the [vehicle platform].
GVA_HMI_225 K The top level menu for the SA functional area shall
provide an overview of LSA capabilities available.
GVA_HMI_229 K It shall not be possible to initiate munitions from the SA

functional area.
GVA_HMI_230 K Direction of video feed views shall be shown relative to

the [vehicle platform] direction.
GVA_HMI_226 1 Display of video feeds shall be selectable between single

video feed and a multiple (mosaic) video feed.
GVA_HMI_227 1 When viewing a single video feed in the SA functional

area, the following functions should be available.
a) select all video feeds in a logical sequence;
b) select the video feeds from weapon sight system(s) or

other sensors;
c) the means to designate a point on the image being

viewed such that the point coordinates can be handed
over to a weapon or sight [sub-system].
GVA_HMI_228 1 When viewing multiple video feeds in the SA Functional

area, in a mosaic view, the following functions shall be
available:
a) an indication of which feeds are being viewed
b) selection of a different combination or arrangement of

video feeds
c) selection of the video feeds to form the mosaic view

from weapon sight system(s) or other sensors
d) the means to designate a point on any of the images

being viewed such that it handed over to a weapon or
sight [sub-system]
e) selection of any one of the mosaic video feeds to view

as a single video feed
f) an indication of what video feeds the operator is

viewing.
GVA_HMI_231 1 Composite (stitched) video from multiple feeds shall

include a means to easily identify the orientation of the
"stitched" image relative to the [vehicle platform] hull
alignment.
27
GVA_HMI_232 1 Where an area of a composite (stitched) video image can

be selected for magnification, a method of highlighting
the selected area shall be provided.
GVA_HMI_233 1 Video feeds from rearward looking cameras used for

non-driving functions shall not be ‘mirrored’ by default.
GVA_HMI_234 1 There shall be a textual indication of mirroring overlaid to

the outside of the main viewing area on any mirrored
imaged.
GVA_HMI_235 1 If the [vehicle platform] is fitted with an electro-optic or

thermal imaging [sub-system] which is not linked to a
weapon system, then it shall be possible to control
functions related to those [sub-systems] from the SA
functional area.
GVA_HMI_236 1 Changing between cameras views in the SA functional

area shall take less than 0.5 seconds.
GVA_HMI_237 1 Changing between magnification levels for camera views

shall take less than 0.5 seconds.
GVA_HMI_238 1 Pan/tilt functionality for sensors and cameras shall be

available when the SA functional area is selected
Weapon
GVA_HMI_240 K Selecting WPN shall provide access to the WPN

functional area.
GVA_HMI_241 K All weapon [sub-system]s shall be controlled and initiated

from the WPN functional area.
GVA_HMI_244 K When in the WPN functional area there shall be a clear

indication of which GVA HMI has control of a weapon
[sub-system].
GVA_HMI_245 K There shall be the capability to monitor, interact with and

control a selected weapon [sub-system].
GVA_HMI_247 K When in the WPN functional area, the [GVA HMI] shall
clearly indicate weapon states.
GVA_HMI_248 K The [GVA HMI] hand controller(s) shall provide all the
controls required to engage a target with the selected
weapon [sub-system].
GVA_HMI_249 K The information and aiming marks for a selected weapon

[sub-system] shall be displayed.
GVA_HMI_242 1 Where multiple weapon [sub-systems] are available, the

WPN top level menu page shall show an overview of the
status of each of the weapon [sub-systems].
GVA_HMI_243 1 The WPN function area top menu page shall display the
sight picture appropriate information and aiming marks if
a single weapon [sub system] is fitted.
GVA_HMI_245 1 Bezel Buttons or soft keys shall be used to gain access

to information on each weapon [sub system], when more
28
than one weapon [sub-system] is fitted.
Defensive
GVA_HMI_251 K Selecting DEF shall provide access to the DEF functional

area.
GVA_HMI_252 K The DEF functional area shall control and initiate all
defensive [sub-systems].
GVA_HMI_257 K There shall be the capability to access more detailed

information about a selected [sub-system].
GVA_HMI_253 1 The DEF functional area shall display the options and
information relevant to the selected defensive capability.
GVA_HMI_254 1 The DEF functional area top level menu screen shall give
an overview of the status of all the installed defensive
[sub-systems].
GVA_HMI_255 1 Defensive [sub-systems] shall be selected by a bezel

button (or soft key), where there is more than one
defensive [sub-system] fitted.
System
GVA_HMI_259 K Selecting SYS shall provide access to the SYS functional

area.
GVA_HMI_260 K The SYS functional area shall provide monitoring and

control of GVA wide functions and configuration along
with [sub-system] health, status and configuration.
GVA_HMI_261 K Access to individual vehicle platform [sub-systems]

information and control shall be by selection of a bezel
button (or soft key).
GVA_HMI_262 K The SYS Functional area shall provide:
a) A 'top-level' menu page with an overview of all mission

essential [sub-systems] (MES) as defined in the
individual [vehicle platform] SRD.
b) Access to more detailed information about each of the

[vehicle platform] [sub-systems].
c) The means to configure the position and format of

information presented on the GVA display screen (e.g.
position of the PPI, time format).
d) Access to the power management functions within the

[vehicle platform].
GVA_HMI_377 1 The SYS functional area shall provide:
a) Access to historical information stored in the HUMS

[sub-system]
b) Access to real time 'system' data from the GVA

Infrastructure
c) Access to Interactive Electronic Technical Publications
29
(IETP)/manuals for [vehicle platform] and [sub-systems]
GVA_HMI_378 2 The SYS functional area should provide the means to

configure the [GVA HMI] to reflect the needs of various
[vehicle crew] roles.
Driver
GVA_HMI_264 K Selecting DRV shall provide access to the DRV

functional area.
GVA_HMI_265 K The DRV functional area shall provide information

relating to driving functions and automotive information.
GVA_HMI_266 K The DRV functional area shall provide the means to

select and view the following driving aid information on
video feeds.
a) Tramlines with distance markers
b) A heading indication in NATO angular mils
GVA_HMI_268 K There shall be a textual indication of mirroring overlaid to

the outside of the main viewing area on any mirrored
imaged.
Special to Role
GVA_HMI_270 K Selecting STR shall provide access to the STR functional

area dedicated to specialist [sub systems], which are not
common across [vehicle platforms].
Communication
GVA_HMI_273 K Selecting COM shall provide access to the COM

functional area
GVA_HMI_274 K The COM functional area shall control and configure

[vehicle platform] communication [sub-systems].
Battlefield Management System
GVA_HMI_276 K Selecting BMS shall provide access to the BMS

functional area.
GVA_HMI_277 K The BMS functional area shall display and manipulate

information and mapping relating to Battlefield Situational
Awareness.
GVA_HMI_278 K The BMS functional area shall display and manipulate

information relating to tactical and operational C2.
GVA_HMI_279 K The BMS functional area shall provide the displays for
[vehicle platform] navigation information and mapping.
Mapping Displays
GVA_HMI_281 K Grid overlays on maps shall be [operator] selectable

between:
a) MGRS - Military Grid Reference System
30
b) British National Grid Format (when in the applicable

area)
c) Irish Grid Format (when in the applicable area)
d) Local Grid Format
GVA_HMI_282 K Grid overlays on maps shall be [operator] configurable to

display any local grid reference system using NATO
approved local to WGS84 datum transformation
parameters.
GVA_HMI_283 K Grid overlays on maps shall be presented with grids

projected as squares.
Table 22 GVA HMI Functional Area Requirements
8.3.2 Additional Guidance

8.3.2.1 In the SA functional area, if multiple mosaic views (e.g. 2, 3, 4 or more videos combined in
one view) are implemented, they may either be operator configurable (i.e. the operators
creating combinations of camera views they wish to see) or the layout of these "mosaic"
views may be predetermined arrangements. The precise view will depend on the exact
camera configuration and role of the vehicle.
8.3.2.2 Consideration should be given to providing enhanced threat information on video sources to
indicate the relative threat location e.g. a marker to indicate shot detection.
8.3.2.3 In the DEF functional area, defensive aid set up may include the selecting of individual
sensors to enable configuration (e.g. sensitivity, direction) and response priorities depending
upon the defensive system, including sensor capabilities. For these type of functions,
consideration should be given to setting privileges for specific operators i.e. Commander
only.
8.4 System Start Up
8.4.1 Following start-up, the operators (possibly a single operator, may be presented with the SYS
overview screen. This could show the status of the vehicle platform and all of its sub-
systems and indicate any faults.
8.4.2 Only essential test information should be presented to the vehicle platform operators, with all
other test data being stored separately, and possibly telemetered, for interrogation by the
Royal Electrical and Mechanical Engineers (REME).
8.4.3 Appropriate remedial action (crew task or local repair) as described in the relevant technical
publications, for example, Army Equipment Support Publication (AESP) should be displayed
to the operator. As part of power management, different sub-systems may need to be
powered up or down in specific orders.
8.4.4 Views following start up for the other roles within the vehicle platform shall be defined on
design.
9 Data Entry
9.1 Requirement Table 23 shows requirements which relate to entering data via the GVA HMI.
Data Entry
GVA_HMI_286 K The [GVA HMI] shall have the facility to enter free text
and numerical data.
GVA_HMI_288 K Templates or fill-in forms shall be provided for data entry
31
for common tasks.
GVA_HMI_289 K A template or fill-in form shall provide visual indication

where text or numbers can be entered.
GVA_HMI_292 K There shall be a method of moving the GVA display

screen cursor between data entry fields.
GVA_HMI_293 K Entered text shall be left justified.
GVA_HMI_294 K Entered numerical data shall be right justified.
GVA_HMI_287 1 The following functions shall be available to support data

entry and navigation:
a) Accept a value and move to the next data field
b) Move back to the previous data field
c) Save the data field changes and exit data entry
d) Exit data entry without saving changes
GVA_HMI_290 1 Data entry fields shall be logically grouped.
GVA_HMI_291 1 Data entry field titles shall be meaningful.
GVA_HMI_295 1 Functions to delete information shall require confirmatory

action.
GVA_HMI_296 1 The GVA display screen shall provide visual responses

to the input or selection of data.
Table 23 Data Entry Requirements
10 Alerts
10.1.1 Alerts consist of alarms and threats. Alarms consist of events or failures that relate to vehicle
platform sub- systems and Threats consist of external events that will affect the mission.
10.1.2 Alerts need be to attention-getting and indicate unambiguously, their meaning and urgency
without overloading or inducing a startle reaction from the vehicle crew.
10.1.3 The choice, designation and allocation of all signal types, including visual and audio
indications should be considered alongside other systems used within the vehicle platform,
to ensure that a coherent approach is adopted and confusion is avoided.
10.2 Alarms
10.2.1 Alarm Categories
10.2.1.1 Alarms are categorised into Warnings, Cautions and Advisories.
a) A warning is the highest category of alarm. A warning indicates a safety condition and / or
loss of a sub-system(s) that the vehicle crew must be made immediately aware of. (The
warnings may be sub-categorised.)
b) A caution indicates a loss of functionality for which the vehicle crew must be informed. (It
may result in the need to amend the mission plan, some degradation in GVA HMI sub-
system performance or the need for unscheduled maintenance.)
c) An advisory is the lowest category of alarm. An advisory indicates that an event has
occurred but it does not impact on the performance of the vehicle platform. (It may result
in the need for maintenance activity after mission completion.)
32
10.2.1.2 Visual and auditory features will be provided for all categories of alarms; however the exact
format may differ. E.g. text messages shall appear for Warning alarms but are optional for
Caution and Advisory alarms.
10.2.1.3 A higher category of alarm will override a lower category of alarm.
10.2.2 Terminology
10.2.2.1 The following terms are used throughout section 10:
a) 'Active': Alarms that have not been corrected, overridden nor resolved and are either in
the state of acknowledged or unacknowledged. The total number of active alarms by
type (Warning, Caution or Advisory) is reported on the status bar;
b) 'Acknowledge': A function which moderates the audio and / or the visual features of the
alarm and leaves the alarm in the active alarm list. The exact behaviour of the visual and
audio features shall depend on the category of alarm;
c) 'Override': A function used to suppress the source of the alarm to prevent it from
triggering again. The alarm remains on the active alarm list. On Mission System power
up, all previously overridden alarms shall be removed;
d) 'Clear': A function which removes the alarm from the active alarm list through resolution of
the trigger condition;
e) 'Resolved Alarm' is one where the alarm trigger condition is no longer extant.
10.2.3 Visual Presentation of Alarms
10.2.3.1 Requirement Table 24Table 24 shows requirements which relate to the visual presentation
of alarms on the GVA display screen.
Visual Presentation of Alarms
GVA_HMI_307 K Alarms shall be categorised into Warnings, Cautions and

Advisories
GVA_HMI_308 K Any alarm text messages shall appear directly beneath the
Status Information Bar.
GVA_HMI_309 K Alarms that are overridden shall be redisplayed on GVA

start up.
GVA_HMI_379 1 Text messages shall be structured according to the

following syntax:
Category - Subsystem – Component – Nature - Type
E.g. W – Engine Oil Low Pressure
Warnings
GVA_HMI_311 K A warning alarm shall generate a text message.
GVA_HMI_312 K Warning alarm text messages shall describe the nature of

the associated alarm.
GVA_HMI_313 K A Warning alarm text message cannot be overwritten by

an alarm of a lower category.
GVA_HMI_314 K Upon selection of F16 after a warning, the associated

[GVA HMI] text message shall remain until the warning is
cleared or overridden in the Alarms menu table.
33
GVA_HMI_315 K The [GVA HMI] used by the driver shall have the means to
suppress and hide the display of a warning text message
with a single bezel button selection.
Cautions
GVA_HMI_325 K The [GVA HMI] shall handle multiple Caution alarms

presenting each one in turn for acknowledgement.
GVA_HMI_326 K Cautions alarms triggered while a Warning alarm text

message is displayed, shall only be presented if:
a) The warning alarm is resolved or overridden
and;
b) The presentation time of the caution alarm has not

expired.
GVA_HMI_318 2 A Caution alarm should generate a text message.
GVA_HMI_319 2 Caution alarm text messages shall describe the nature of

the associated alarm.
GVA_HMI_320 2 If a Caution text message is displayed, it should disappear

if the alarm is acknowledged.
GVA_HMI_321 2 If the Caution text message is displayed it should be

automatically acknowledged after 10 seconds.
GVA_HMI_322 2 Cautions once acknowledged should be repeated after 2

hours if the event is still valid.
GVA_HMI_323 2 Cautions once acknowledged should be repeated after

GVA start up if the event is still valid.
Advisories
GVA_HMI_381 2 Advisory alarms should not trigger a text message on the

display screen.
GVA_HMI_382 2 Advisories should be repeated every 24 hours if the event

is still valid.
GVA_HMI_383 2 Advisories should be repeated at start up if the event is

still valid.
Table 24 Visual Presentation of Alarm Requirements
10.2.4 Alarms Menu Page

10.2.4.1 Requirement Table 25 shows the requirements which relate to the Alarms menu page once
F14 is selected.
Alarm Menu Information
GVA_HMI_146 K When F14 is selected the Alarms menu page shall be

displayed.
34
GVA_HMI_148 1 The alarms menu page displayed shall provide the

following information:
a) The total number of acknowledged warnings, cautions

and advisories
b) The total number of unacknowledged warnings,

cautions and advisories
c) The current and total number of pages of alarms e.g.

Page 1 of 2
d) A table displaying all alarms (paged table if required)
GVA_HMI_149 1 The table displayed in the alarms menu page shall provide
the following for each alarm:
a) Alarm title
b) Time of the alarm
c) Category of alarm
d) Whether the alarm has been acknowledged
GVA_HMI_384 1 The alarm table shall following the syntax below:
Category - Subsystem – Component – Nature - Type
GVA_HMI_147 1 The Alarms menu page shall by default list all alarms
sorted by category (most important first) then time (most
recent first).
Alarm Menu Functions
GVA_HMI_151 1 When displaying the table in the alarms menu page it shall
be possible to:
a) Sort by category (warnings, cautions, advisories) –

arranges the alarms displayed by category and then time
(most recent first)
b) Sort by time – arranges the alarms displayed by time

(most recent first) and then priority (most important first)
c) To individually select alarms
c) Include/exclude acknowledged alarms – shows or hides

acknowledged alarms
d) View alarm detail – brings up more detail regarding the

alarm (if available)
e) Page Up and Page Down – navigate to the

next/previous page of alarms (if applicable)
f) Acknowledge individual alarms
g) Acknowledge all alarms
h) Clear an individual alarm
35
i) Clear all alarms
j) Override an individual alarm
Table 25 Alarms Menu Requirements
10.3 Threats
10.3.1.1 Threat categorisation will be dependent upon the capability of the threat detection systems
and the ability to discern the exact nature of the threat.
10.3.1.2 Threats, due to the immediacy and potential life threatening nature, should result in a clearly
defined set of operator actions and Standard Operating Procedures (SOPs). (The action
options given by the GVA HMI should be considered during the design process.)
10.3.2 Visual Presentation of Threats
10.3.2.1 Requirement Table 26 shows requirements which relate to the visual presentation of Threats
on the GVA display screen.
Visual Presentation of Threats
GVA_HMI_330 K Threats text messages shall appear in a different location

to Alarm text messages.
GVA_HMI_385 K The syntax for a threat text message shall be the same as
the alarms text messages.
GVA_HMI_331 1 If a graphical threat display is implemented, individual

threats shall be displayed as icons with ranges and
bearings relative to the [vehicle platforms] position.
GVA_HMI_333 1 A threat display shall identify the status of all sensor [sub-
systems] fitted to the [vehicle platform].
GVA_HMI_332 2 If a graphical threat display is used, a means should be

provided to de-clutter the display by removing nonessential
and out-of-date threat information.
Table 26 Visual Presentation of Threat Requirements
10.3.2.2 Additional information, such as Local Situational Awareness System (LSAS) camera views,
may be available on the threats display, but a means should be provided for the operator to
de-clutter the display by removing non-essential information.
10.3.2.3 The definition of essential and non-essential items on the display should be defined as part
of the design implementation and with operators. However the inter-vehicle consistency
needs to be balanced with individual operator opinions.
10.3.3 Threats Menu Page
10.3.3.1 Requirement Table 27 shows the requirements which relate to the Threats menu page once
F15 is selected.
Threats Menu
GVA_HMI_153 K When F15 is pressed the threats menu page shall be
36
presented.
GVA_HMI_154 1 The threat menu page shall provide the following

information:
a) Type of threat
b) Location of threat
c) Time of the threat detection
d) Threat description/type (if appropriate)
e) Status of the threat
GVA_HMI_155 1 If displaying a table in the threats menu page, it shall be

possible to:
a) Sort by type - arranges the threats by type and then

time (most recent first)
b) Sort by time – arranges the threats displayed by time

(most recent first) and then type (most important first)
c) View threat detail – brings up more detail regarding the

threat (if available)
d) Select an individual threat
e) Page Up and Page Down – navigates to the

next/previous page of threats (if applicable)
f) Cancel an individual threat
g) Cancel all threats
GVA_HMI_386 1 The threats menu page shall following the same syntax as
the alarms menu page.
Table 27 Threats Menu Page Requirements
10.4 Audio Presentation of Alerts

10.4.1 Requirement Table 28Table 28 shows requirements which relate to the audio presentation of
GVA alerts.
Audio Presentation of Alerts
GVA_HMI_335 K There shall be an alert tone for Warning alarms, Caution

alarms and Threats.
GVA_HMI_336 K The GVA alert tones for Warning alarms, Cautions alarms
and Threat shall be different.
GVA_HMI_337 K The GVA alert tones shall be adjustable to be audible

above all expected background noise conditions.
GVA_HMI_387 K There shall be separate volume controls for headsets and

any speakers shall be decoupled.
37
GVA_HMI_339 K The GVA alerts shall use multi-frequency audio tones.
GVA_HMI_338 1 There shall be provision within the [GVA HMI] of at least

two additional alert tones (not including voice alerts).
GVA_HMI_341 1 Alert tones for Warnings and Cautions shall be of a similar

tonal family with modulation and frequency spectrum
adjusted to create greater or lesser perceived urgency
appropriate to the alert category.
GVA_HMI_388 1 Upon selection of F16 the audio alerts tones shall stop.
GVA_HMI_342 1 Alerts tones for threat events shall be distinguishable from

the Warning and Caution audio alerts.
GVA_HMI_343 1 An individual alert tone shall last between 1 and 2

seconds.
GVA_HMI_344 1 An alert tone shall continue to be repeated until

acknowledged by the [vehicle crew].
GVA_HMI_389 1 The audio tone for Warnings shall play through a full cycle
even when acknowledged.
GVA_HMI_390 1 Alerts tones for acknowledged warnings shall be reinitiated

after a 15 minutes.
GVA_HMI_346 1 Alerts tones for acknowledged warnings shall be re-

initiated on GVA start up if the warning is still valid.
GVA_HMI_340 2 Alert tones should be routed to all operator headsets as

well as internal [vehicle platform] speaker/s if fitted.
Audio Speaker System
GVA_HMI_348 K The [GVA HMI] shall have a function to disable all audio
output from speakers.
GVA_HMI_349 K When the [GVA HMI] speakers are disabled there shall be
a clear indication on each speaker that there is no audio
output.
Table 28 Audio Presentation of Alerts Requirements
10.4.2 When an individual GVA display screen and associated bezel buttons is blacked out, the
operators will be alerted to an incoming Warning alarm, Caution alarm and Threat by the
associated audio tone.
10.4.3 Further guidance on audio alarms can be found in Def Stan 00-250 Part 3 Section 15.
38
Annexes
Annex A. Abbreviations
Local Situational Awareness
BMS Battlefield Management System LSAS
Systems
COM Communication Systems MES Mission Essential Systems
Def Stan Defence Standard MOD Ministry of Defence
DEF Defensive Systems MOTS Military Off-The-Shelf

Director Land Equipment (DE&S,
D LE NATO North Atlantic Treaty Organisation
UK MOD)
Defence Equipment and Support
DE&S REME Royal Electrical and Mechanical
(UK MOD)
Engineers
DLOD Defence Lines of Development SA Situational Awareness Systems
DRV Driver Systems SAE Society of Automotive Engineers
ECM Electronic Counter Measures SRD System Requirement Document
GPOC GVA Point of Contact STR Special to Role Systems
GVA Generic Vehicle Architecture SYS System Status
HF Human Factors URD User Requirements Document
HMI Human Machine Interface V&V Verification and Validation

Health and Usage Monitoring
HUMS VSI Vehicle Systems Integration
Systems
International Standards Vehicle Technology Integration
ISO VTID
Organisation Demonstrator
Intelligence, Surveillance, Target
ISTAR
Acquisition and Reconnaissance
Integrated Test Evaluation and
ITEAP
Acceptance Plan
ITT Invitation to Tender
JSP Joint Services Publication
39
Annex B. GVA Human Machine Interface Requirements Table (DOORS Baseline 1.0)
Verification
Unique ID Priority Requirement Text Measure of Performance Justification Remarks Verification Description
Method
GVA_HMI_352 N/A N/A N/A

1 GVA Human Machine Interface (HMI)
1.1 GVA HMI
GVA_HMI_3 Key The following items shall be included as part of the [Vehicle platform] [sub- This is a key top level Review and Review design documentation to
[GVA HMI]: systems] are controllable requirement for GVA and Inspection ensure that the GVA HMI
through the [GVA HMI] and provides a common 'open' components are present.
a) GVA Display Screen confirmation that the method for controlling platform
necessary [GVA HMI] [sub-systems] and displaying
b) Bezel Buttons elements exist information. Adoption will
reduce integration costs and Inspect to ensure that the
time, and will help to reduce implemented design matches the
the number of screens and documentation
controls which the [vehicle
crew] need to use. The
common [GVA HMI] interface
will reduce the training needs
through life and across
[vehicle platforms]
GVA_HMI_353 1 Where necessary, the following items shall be Review and Review design documentation to
included as part of the [GVA HMI]: Inspection ensure that the GVA HMI
components are present.
a) Physical Keyboard
b) Audio interface to Headsets and Speakers

Inspect to ensure that the
c) Hand Controller implemented design matches the
documentation
d) Hard Control Panel

1.2 GVA Display Screen
1.2.1 GVA Display Screen Characteristics
GVA_HMI_6 1 GVA display screens shall be capable of displaying at least 256 (8 bit) level BS EN ISO 9241-303:2008(E) Review Review design documentation to
at least 256 (8 bit) level greyscale. greyscale. check the display screen is capable
of displaying at least 256 (8 bit)
level greyscale
GVA_HMI_7 1 GVA display screens shall have a response time of response time of less than BS EN ISO 9241-303:2008(E) Review Review design documentation to
less than 16 ms. 16 millisecs. check the display screen has a
response time of less than 16 ms.
Time the response time to check it

meets the requirement criteria
GVA_HMI_8 1 GVA display screens shall have a minimum minimum resolution of 95 BS EN ISO 9241-303:2008(E) Review Review design documentation to
resolution of 95 pixels per inch. pixels per inch check the display screen has a
minimum resolution of 95 pixels per
inch
GVA_HMI_9 1 GVA display screens shall be a minimum of 18 bit Threshold: minimum of 18 BS EN ISO 9241-303:2008(E) Review Review design documentation to
check the display screen
41
Verification
Method
colour capable (24 bit - Objective). bit colour capable characteristics
Objective: 24 bit colour
GVA_HMI_10 1 The backlight luminance of a GVA display screen variance of no more than 5% BS EN ISO 9241-303:2008(E) For guidance in the Test Measure the display screen
shall not vary by more than 5% over the whole over the whole display appropriate luminance ranges luminance with an lux meter to
surface. screen surface. for day, night and night vision ensure the variance is no more than
equipment, refer to ISO 9241. 5%
GVA_HMI_11 1 GVA display screens shall have a minimum contrast minimum contrast ratio of BS EN ISO 9241-303:2008(E) Review Review design documentation to
ratio of 50:1. 50:1. check the display screen
characteristics
GVA_HMI_12 1 The luminance of the display screen and backlit adjustable between 0-50 BS EN ISO 9241-303:2008(E) For guidance in the Test Measure the display screen
labels on controls and dials shall be adjustable cd/m2. appropriate luminance ranges luminance with an lux meter to
between 0-50 cd/m2. for day, night and night vision ensure the luminance is adjustable
equipment, refer to ISO 9241. between 0-50 cd/m2.
ISO 9241
The method and granularity of

Def Stan 00-250 Part 3 adjustment will be platform
Section 13 specific
Should provide sufficient

luminance to be readable in
all expected lighting
conditions
GVA_HMI_13 1 There shall be a means to select between linked linked and decoupled BS EN ISO 9241-303:2008(E) For guidance in the Test Test to ensure that luminance
and decoupled luminance adjustment of backlit adjustment provided appropriate luminance ranges adjustment is decoupled
labels on controls and dials, and display screen. for day, night and night vision
equipment, refer to ISO 9241.

1.2.2 Operation using Night Vision Aids
GVA_HMI_15 Key The [GVA HMI] luminance shall be compatible with Compatible with: BS EN ISO 9241-303:2008(E) For guidance in the Test Test to ensure that the luminance of
the use of current in-service night vision aids. appropriate luminance ranges the GVA HMI can be reduced
for day, night and night vision sufficiently to not cause flares from
equipment, refer to ISO 9241. the light emitted from the GVA HMI
a) LUCIE ISO 9241 when the operators are wearing the
in service night vision equipment.
b) HMNVS
Def Stan 00-250 Part 3
Def Stan 00-250 Part 3 Section 13 provides additional
Section 13 guidance on night vision.
GVA_HMI_16 Key The range of luminance adjustment for all [GVA useable under ambient night All GVA HMI equipment Test Test to ensure that the range of
HMI] equipment shall be compatible with the range conditions required needs to be compatible with luminance to ensure that
of external ambient night conditions expected in the elsewhere in the SRD NVG operation in a range of information displayed on the GVA
operational environment. external scene lighting HMI is legible in the full range of
conditions expected ambient conditions
GVA_HMI_17 Key It shall be possible to access and interpret the Read and interpret the text THe [GVA HMI] needs to be Test Test to ensure that legibility of
information from the [GVA HMI] whilst wearing and information on the able to be used safely in information displayed on the GVA
screen under ambient night conjunction with other tasks HMI with operators wearing the in
42
Verification
Method
current in-service night vision equipment. conditions required with the [vehicle crew] service night vision equipment.
elsewhere in the SRD wearing NVG equipment
Useable with:
a) LUCIE
b) HMNVS

1.2.3 Display Blackout
GVA_HMI_20 1 A hardware control shall be used to reduce the hardware controlled, display Allows an individual [vehicle Test Test to provide evidence that the
luminance to zero (blackout) on a single [GVA screen and button crew] member to blackout screen and bezel buttons can be
display], including screen and backlit bezel buttons, backlighting 'blackout' their own display for a covert blacked out independent of the
independent of the underlying GVA processing. available mode or to reduce the underlying GVA processing, using a
signiture of the vehicle hardware control.
platform
GVA_HMI_21 1 The same hardware control used to blackout a GVA Luminance restored with reduce training and ensure Test Test to provide evidence that the
display shall be used to restore luminance to the same hardware control as the system follows an intuitive screen and bezel buttons can be
screen and backlit bezel buttons. used to blackout the display design restored to the previous luminance
screen level using the same hardware
control
GVA_HMI_22 1 It shall be possible to blackout the complete [GVA [GVA HMI] is 'blacked' out To prevent light emission in Test Test to provide evidence that it
HMI] on command from the [vehicle platform] on activation of the tactical situations on opening accomplishes the required functions
blackout function or interlock, independent of the appropriate [vehicle [vehicle platform] hatches and under specific scenarios.
underlying GVA processing. platform] lighting interlocks doors.
GVA processing continues

when all [GVA HMI]
luminance is zero
GVA_HMI_23 1 Whenever a [GVA display] is blacked out, all input Input functions disabled on Because the screen is Test Test to provide evidence that Input
functions, apart from the operation of associated 'blackout'. 'blacked' out there is no way functions are disabled on 'blackout'.
hand controllers, [Hard Control Panel], and the an [operator] can determine
display blackout switch shall be disabled. the impact of input functions
as there will be no visual
response.

1.2.4 Viewing Distance and Direction
GVA_HMI_29 1 The information on the GVA display shall be legible Inclination up to 40° from a To allow for a range of Test Test to ensure that all the
from any angle of inclination up to 40° from a perpendicular viewing viewing angles as [vehicle information displayed on the GVA
perpendicular viewing direction, measured in any direction, measured in any crew] members change HMI display is legible from and
plane. plane. position or the information on angle inclination up to 40ø from a
the screen needs to be seen perpendicular viewing direction,
by others not directly at the measured in any plane.
[crewstation]
GVA_HMI_31 1 The GVA display shall be positioned between 500 500 mm and 635 mm from Distance will vary on The recommended viewing Review and Review design documentation /
mm and 635 mm from the [operators] eyes to the the [operators] eyes. functional reach to the bezel distance of the display from Test layouts of the vehicle platform.
centre of the screen. buttons but the display should the [operator's] normal
be legible at these distances operating position is
43
Verification
Method
with recommended text and dependent on several factors,

icon sizes including: the task being
conducted, display size, Measure that the GVA HMI display
information type and size screens are located between 500
being presented and whether mm and 635 mm from the
this display is to be read whist [operators] eyes.
on the move. See
ISO9241:303 for guidance
Distance will depend on

functional reach to the bezel
buttons

1.3 Controls & Input Devices
1.3.1 Bezel Buttons
GVA_HMI_34 Key The [GVA HMI] shall include hard buttons (bezel Necessary bezel buttons To establish a common button All GVA displays will have a Review Review design documentation to
buttons), positioned around the edge of the display exist layout on all [GVA HMI] common layout reducing ensure the bezel buttons are laid
screen: displays across all [vehicle [operator] training needs out as required.
platform] types.
a) 8 buttons across the top (Top Level Menu

Buttons)
b) 8 across the bottom of the display (Common

Function Buttons)
c) 6 buttons on each side of the display

(reconfigurable Buttons)
GVA_HMI_35 Key Where reconfigurable menus are used, each bezel Labels are clear and align To make sure it is absolutely Inspection Inspect to ensure that labels are
button shall be unambiguously associated with a with bezel buttons clear what a button will do clear and are unambiguously
label. associated with the bezel buttons
GVA_HMI_355 Key Bezel buttons shall be the primary method of Review and Review the design documentation
interaction when the [vehicle platform] is in motion. Inspection and inspect the design to ensure
that the bezel buttons are the
primary method of interaction when
the [vehicle platform] is in motion
GVA_HMI_37 Key The bezel buttons shall provide a tactile response to Tactile response to all bezel Makes it clear the button has Test Demonstration that a tactile
indicate the operation of a button has been button operations exist been operated response to all successful bezel
successful. button operations has been
provided
GVA_HMI_36 1 The size of the bezel buttons shall be according to Complies with Def Stan 00- standard sizes should allow Inspection Measure the bezel buttons and
guidance laid down in Def Stan 00-250 Part 3 250 Part 3 Section 15 button for easy selection and check against the guidance in Def
Section 15. sizes operation of buttons without Stan 00-250 part 3 section 15
error
GVA_HMI_38 1 Labels on the bezel buttons shall be backlit. Backlighting present To make it clear what the Inspection Inspect the design to ensure the
button does bezel buttons are backlit
GVA_HMI_356 1 N/A N/A

1.3.2 Physical Keyboards
44
Verification
Method
GVA_HMI_44 Key The [GVA HMI] shall be designed to prevent To prevent inadvertent key Review and Review design documentation to
inadvertent operation of any physical keyboard. presses when stowed. Test understand how inadvertent
operation has been prevented and
test to see if the method has been
implemented
GVA_HMI_43 Key Physical keyboard keys shall provide a tactile Tactile response to all Makes it clear the key has Test Test to ensure that a tactile
response to indicate that the operation of a key has physical keyboard keys been operated response to all successful keyboard
been successful. pushes exist operations has been provided
GVA_HMI_42 1 The size of physical keyboard keys shall be Keyboard key sizes conform To minimise entry errors and Inspection Measure the keys and check
according to guidance laid down in Def Stan 00-250 to Def Stan 00-250 Part 3 to be suitable for gloved use against the guidance in Def Stan
Part 3 Section 15. Section 15. 00-250 part 3 section 15
GVA_HMI_45 1 Physical keyboards shall be able to be placed in a To ensure speed and ease of Review and Review design documentation to
state where the operation of the keys doesn't result locking Test understand how operation has been
in a system response [i.e locked]. prevented and test to see if the
method has been implemented
GVA_HMI_358 1 It shall not be possible to unintentionally "lock” a Review and Review design documentation to
physical keyboard. Test understand how unintentional
locking has been prevented and
test to see if the method has been
implemented
GVA_HMI_46 1 Physical keyboards shall be able to be returned to a To ensure speed and ease of Test Test to ensure that the keyboards
fully operational state by the same method used to unlocking can be returned to a operational
initiate a lock. state by the same method
GVA_HMI_47 2 The [GVA HMI] display should provide an indication Indication exists So an [operator] knows if the Review and Revie design documentaiton and
that the physical keyboard, key lock is in operation. keyboard can be used Inspection inspect to ensure an indication of
"key lock" is displayed

1.3.3 On-Screen Keyboards
GVA_HMI_49 Key On screen keyboards shall provide visual response visual or auditory response So an [operator] knows if a Test Test to ensure a visual response is
when a key is selected. exists soft key has been selected provided when a soft key is
selected

1.3.4 Touch Screens
GVA_HMI_51 Key Touch screens shall function with and without the functions with and without [Vehicle crew] members may Test Test the screen functionality with
[operator] wearing gloves. the [operator] wearing need to wear gloves operators wearing the current issue
gloves gloves
GVA_HMI_360 Key There shall be a means to enable and disable any Test Test to ensure there is a way to
touch screen. enable and disable the touch
screen
GVA_HMI_52 Key An alternative method of physical interaction shall Alternative methods exist Test Test to ensure there is an
be provided in addition to any touch screen alternative method of physical
interaction. interaction in addition to any touch
45
Verification
Method
screen
GVA_HMI_54 1 On a touch screen, the size of soft keys or areas Soft key sizes are compliant For acceptable selection error Inspection Measure the soft keys to ensure
intended to be selected or manipulated by touch with Def Stan 00-250 Part 3 rates and to be usable with they comply with Def Stan 00-25
shall be according to the guidance laid down in Def Section 15. gloves part 3 section 15
Stan 00-250 Part 3 Section 15.
GVA_HMI_53 2 On a touch screen, the soft labels used to indicate Bezel button soft key labels To remove the need for Test Test to ensure the bezel button soft
the functionality of bezel buttons should also act as also have soft key additional soft keys that would key labels also have soft key
soft keys. functionality use screen space functionality

1.4 Hand Controllers
GVA_HMI_58 Key Weapon and sighting systems shall be controlled by Pointing device and trainable Exact hand controller Review and Review the design documentation
a hand controller. [sub-system] control devices functionality will be dependent Test and test to ensure that all weapon
exist on the [subsystems] fitted to and sight systems are controlled by
the [vehicle platform] and the hand controllers
manner in which they are
used.
As a rule, the hand controllers

should include all the controls
required to complete a
sequence of actions e.g. a
target engagement without the
user taking their hands off the
hand controllers.
GVA_HMI_361 Key On screen cursors or pointing devices shall be Review and Review the design documentation
controlled by a hand controller. Test and test to ensure that all cursors
and pointing devices are controlled
by hand controllers
GVA_HMI_362 Key The weapon system, sighting system and cursor Review and Review the design documentation
control pointing demands shall be input using the Test and test to ensure that all cursors
thumb. and pointing devices are controlled
by the thumb
GVA_HMI_59 Key All thumb controls shall be “stiff stick” (force Hand controller uses 'stiff' thumbs provide the best fine Review and Analysis of design documentation to
transducer) controller types. stick thumb controllers deterous manipulation Test ensure that stiff stick thumb
controllers are used.
GVA_HMI_363 Key The isometric operating force for the thumb Test Test to measure the forces required
controllers shall be 9 to 22N. to move the thumb controllers
GVA_HMI_364 Key Thumb controls used for cursor pointing demand Review Review design documentation to
input shall be accompanied by at least 1 "selection ensure that at least one selection
input" for use with the same thumb. button is provided for sequential
operation whilst using the thumb
controller.
46
Verification
Method
GVA_HMI_64 Key Control of trainable sub-systems and cursors shall Controls for any trainable Controls for training [sub- Review and Compliance statement from
be implemented on separate hand controllers, or [sub-systems] are systems] are implemented on Test manufacturer. Design
used by different hands on a single hand controller. implemented either on a dedicated hand controller, documentation inspection.
separate hand controllers, or separate from the cursor
operated by different hands control for normal use to
on a single hand controller. ensure they are not confused
during normal use
GVA_HMI_65 Key All hand controller buttons that perform 'critical' Different tactile properties to allow identification without Test Test to ensure that all hand
functions shall have different tactile properties to confirmed visual reference. controller buttons that perform
any other button on the same hand controller. 'critical' functions have different
tactile properties to any other button
on the same hand controller.
GVA_HMI_60 2 Control devices used for positional movement of End of travel state tactile So an [operator] knows when Test Test to ensure that a tactile
[sub-systems] on the hand controller should be able response exits the range of movement has response has been provided when
to provide a tactile response to indicate an end of been reached the end of travel state is reached
travel state.

1.4.2 Hand Control of Weapon/Sight Systems
GVA_HMI_67 Key The manual demanded movement of a trainable Safety mechanism present to prevent unintended e.g. a palm switch that acts as Review and Review design documentation to
weapon or sight system shall require the and must be activated to operation a 'deadmans switch' Test ensure a safety mechanism has
simultaneous activation of a safety mechanism and enable control been provided.
movement control.
Test to ensure the manual
demanded movement only occurs
when the safety mechanism is
activated.
GVA_HMI_68 1 Hand controllers used for sighting [sub-system] Laser activation mechanism Review Review design documentation to
control shall provide a mechanism to activate a present ensure a mechanism has been
laser range finder. provided.
GVA_HMI_71 1 If a weapon or sight [sub-system] is automatically Auto slew indication present to enable the [operator] to de- Inspection Inspect to ensure that the direction
slewed, the [GVA HMI] shall include an indication as conflict any potential collision of travel is shown on the GVA HMI
to the direction of travel it will take when it moves. during traverse.
GVA_HMI_72 1 Hand controllers used for sighting [sub-system] Magnification level Review Review design documentation to
control shall provide a mechanism to change the mechanism present ensure a mechanism has been
magnification level. provided.
GVA_HMI_73 1 Hand controllers used for sighting [sub-system] FOV change mechanism Review Review design documentation to
control shall provide a mechanism to change the present ensure a mechanism has been
Field of View (FOV) of the sight. provided.
GVA_HMI_74 1 Where sight systems are used that include more A sensor toggle mechanism e.g. toggle between thermal Review Review design documentation to
than one sensor, the hand controllers used for present on a multi-sensor imaging and TV imaging ensure a toggle has been provided.
sighting [sub-system] control shall provide a sight system controller modes
47
Verification
Method
mechanism to toggle between the sensors.

1.5 Hard Control Panel
GVA_HMI_365 Key Dedicated controls and indicators for operational or Review Review design documentation to
safety critical functions shall be mounted on a Hard ensure that all safety critical
Control Panel(s). functions are mounted on a Hard
Control Panel(s)
GVA_HMI_77 Key The controls on the hard control panel(s) shall Controls conform to Def Commonality of controls Review Review the design documentation
conform to Def Stan 00-250 Part 3 Section 15. Stan 00-250 Part 3 Section to ensure that the design of the
15. HCP complies with Def Stan 00-250
part 3 section 15

1.5.2 HCP Layout
GVA_HMI_81 2 Controls mounted on a Hard Control Panel which Controls with similar for efficient and logical Review Review design documentation to
are functionally similar should be grouped together. functionality are adequately presentation ensure that controls with similar
grouped functionality are adequately
grouped
GVA_HMI_82 2 Controls mounted on a Hard Control Panel which Control layout is consistent for efficient and logical Review Review design documentation to
are used in sequence should be laid out in the with sequence of use (left to presentation ensure that the control layout is
sequence in which they will be typically used (left to right) consistent with sequence of use
right). (left to right)

1.5.3 HCP Labelling
GVA_HMI_86 Key Where labelling is provided on the HCP rather than Conforms to label position To prevent the control label Inspection Inspect the HCP to ensure that
on the control, the following convention shall be requirement form being obscured by the labelling of controls follow the
applied: control. required conventions
a) Where the control is located below head height,

the label shall be located above the control; to
prevent it from being covered by the hand when it is
being operated
b) Where the control is located above head height

the label shall be located below the control; to
prevent the control from masking the label
GVA_HMI_84 1 Labelling of individual controls and groups of HCP labelling clear and For ease of identification Inspection Inspect the HCP to ensure that all
controls on the HCP shall be provided either on the associated with specific labelling is clear and associated
control panel itself or unambiguously associated controls or groups of with specific controls or groups of
48
Verification
Method
with it. controls controls
GVA_HMI_85 1 Groups of related controls and associated indicators Control group borders in logical presentation Inspection Inspect the HCP to ensure that
or displays on the HCP shall be bounded by a place border are used to group similar
border and a label provided within the border that controls.
describes the grouping.

1.5.4 HCP Conventions
GVA_HMI_91 Key Where unintentional operation of a control is Suitable protection for To prevent unintentional Inspection Inspect the HCP to ensure that
unwanted or could have safety or mission critical operation of HCP controls operation adequate protection of safety or
consequences, suitable protection of the control provided critical controls is provided
shall be provided.
GVA_HMI_88 1 The following recognised control conventions shall All HCP controls follow Inspection Inspect the HCP to ensure that
be adopted if they are fitted on the Hard Control conventions labelling of controls follow the
Panel: required conventions
a) Rotary Knobs: Knobs are suitable for high-

precision adjustments in the control of continuous
variables, when little force is necessary for
operation, e.g. for small potentiometers. A clockwise
rotation shall increase the controlled value or turn a
system on and an anticlockwise rotation shall
decrease the controlled value or turn a system off
b) Sliders: A motion to the right shall increase the

controlled value, turn a system on or move a cursor/
controlled system to the right and a motion to the
left shall decrease the controlled value, turn a
system off or move a cursor/ controlled system to
the left
c) Arrows: An up arrow (i.e. push button) shall

increase the controlled value or move a cursor/
controlled system up and a down arrow shall
decrease the controlled value, turn a system on or
move a cursor/ controlled system down
d) Unguarded Two Position toggle switches: Shall

operate with the down position corresponding to
‘On’ and the up position corresponding to ‘Off’’
e) Unguarded three position toggle switches on the

HCP: the centre position shall correspond to ‘Off’
49
Verification
Method
f) For safety critical controls (e.g. arm / fire) a 'flip'

guarded toggle switch shall be used and guidance
on the toggle direction shall be sought from the
Defence Ordnance Safety Group (DOSG)
g) Emergency Stop: Where a user activated

emergency switch is required, it shall conform to Def
Stan 00-250 part 3 Section 15.6.8.1
GVA_HMI_89 1 Indications shall be provided to reflect the status of Indications provided to show For ease of identification Note: This may include the Inspection Inspect the HCP to ensure that
the functions which are controlled from the hard system status use of status LEDs, displays indications are provided which
control panel(s). or the position of the control reflect the status of the functions.
itself.
GVA_HMI_93 1 The spacing of controls shall comply with the Spacing of controls complies to ensure accurate and safe Review Review the design documentation
requirements detailed in Def Stan 00-250 Part 3 with Def Stan 00-250 Part 3 operation of controls including to ensure that the design of the
Section 15.6. Section 15.6. when wearing current in- HCP complies with Def Stan 00-250
service summer and winter part 3 section 15
gloves

2 GVA HMI Modes and Crew Roles
2.1 GVA HMI Modes
GVA_HMI_96 Key The [GVA HMI] shall provide an 'Operational mode' Necessary operational Test Test with operators to ensure all
that provides functions to enable the [vehicle crew] functions available functions for their operational tasks
to undertake their operational task. are provided in this mode
GVA_HMI_97 Key The [GVA HMI] shall clearly indicate the current Mode indications present To clearly show the [operator] Inspection Inspect to ensure that the current
mode when not in the operational mode. the current mode the GVA is mode is clearly indicated
set to
GVA_HMI_98 Key Where changes of GVA mode include changes of Safety related modes To ensure safety related Review and Review design documentation and
[GVA HMI] safety-related behaviour, the mode shall selectable via HCP only controls are performed via Inspection inspect the GVA HMI to ensure
be selected by way of a hard control panel. hardware not software safety related modes are selectable
via HCP only

2.2 Management of System Control
GVA_HMI_100 Key [Vehicle platform] [GVA HMI]s shall be operable [GVA HMI]s operation are Different users will want to Test Vehicle test checking that the [GVA
independently of other [GVA HMI]s. independent of each other. access different information at HMI]s can be operated
Changing one does not the same time on different independently
affect another screens, e.g. driver and
commander
GVA_HMI_101 Key Each [GVA HMI] in the [vehicle platform] shall be All [crewstations] have full Operational functions may role specialised controls may Test Vehicle test checking that the [GVA
capable of performing the functions of any [vehicle functionality with the need to be performed at any include, control handles and HMI]s [crewstations] have full
crew] role except where role specialised controls exception of role specialised [crewstation] hard panel controls functionality with the exception of
are required. controls role specialised controls
GVA_HMI_102 Key When a single [GVA HMI] is interacting with an Interaction with or control of There cannot be any Test Test to ensure that two [GVA HMIs]
interface or controlling a [sub-system] those a [sub-system] cannot be ambiguity over which [GVA cannot control [sub systems]
50
Verification
Method
functions shall not be available ('locked') to other achieved from 2 [GVA HMIs] HMI] is controlling a particular simultaneously
[GVA HMI]s. simultaneously. [sub-system]
GVA_HMI_103 1 If a particular [GVA HMI] has initiated a 'lock' on Any control and interface So any member of a [vehicle Test Test to ensure that any control or
GVA interfaces or control of [sub-systems] then the lock can be overridden by crew] can take control of a interface lock can be overridden
'lock' shall be removable from a different [GVA HMI]. deliberate action by a [sub-system] from their from any other [GVA HMI]
[vehicle crew] member from [crewstation] if there is an
another [GVA HMI] operational need.
GVA_HMI_104 1 If a particular [GVA HMI] has initiated a 'system lock' Any [sub-system] control If a [GVA HMI] fails then Test Test to ensure that any control or
on control of GVA interfaces or control of [sub- locks are automatically control needs to be able to interface lock can be automatically
systems], and that [GVA HMI] has subsequently released on the failure of move to another [GVA HMI] released on the failure of any [GVA
failed, then any 'system locks' shall be automatically any [GVA HMI] HMI]
cancelled.

2.3 Vehicle Crew Roles
3 GVA HMI Display Presentation and
Layout
3.1 Display Screen Layout
GVA_HMI_107 Key The GVA HMI display screen shall comprise of the Display conforms to physical With a standardised GVA A common layout does not Review and Review the design documentation
following items and conform to the general layout layout display physical layout across necessarily mean the same Inspection at PDR and inspect the GVA HMI
diagram in main Def Stan 23-09 text (Figure 3): all [vehicle platform] types the physical item. display to ensure all the items are
training overhead will be as per the requirement
reduced and the opportunity
for hardware reuse increased.
a) Status Information Bar
b) Top Level Menu Buttons
c) Reconfigurable Labels and Buttons
d) Common Function Labels and Buttons
e) Plan Position Indicator

3.2 Status Information Bar
GVA_HMI_109 Key The Status Information Bar shows essential status Status Information Bar Shows essential tactical and Test Got through all the menus to ensure
information and should be present on all screens present on all screens and operational information the Status Information Bar is
and menu pages, unless temporarily hidden. menu pages present on all screens and menu
pages
GVA_HMI_111 Key The Status Information Bar shall show the time and 'Date Time Group' Inspection Ensure the time and dates is
date, displayed in 'Date Time Group' format on the information displayed on the displayed appropriately in the
far left hand side. Status Information Bar correct location
51
Verification
Method
GVA_HMI_113 Key The Status Information Bar shall show the [vehicle 'Grid position' information All 3 grid references may be JSP 465 - Geospatial Inspection and Inspect to ensure the vehicle
platform's] position selectable between the following displayed on the Status used in operational scenarios Information Policy for UK Test platforms position is displayed and
grid formats: Information Bar is based on Defence test to ensure that all the grid
the correct grid system. formats are selectable

STANAG 2211 Edition 6
British National Grid Format
Irish Grid Format
Local Grid Format
GVA_HMI_366 Key There shall be an indication on the display of the Inspection Inspect to ensure that there is an
selected grid format. indication as to which gird format is
being displayed
GVA_HMI_115 Key The Status Information Bar shall show the [vehicle 'Grid position' information JSP 465 - Geospatial Inspection Inspect to ensure the vehicle
platform's] position grid reference in between the displayed on the Status Information Policy for UK platforms position is displayed in
time date group and the alarms. Information Bar is in the Defence the correct location
correct position.
GVA_HMI_116 Key The number of current alarms shall be displayed on Number of current alarms Inspection Inspect to ensure the alarm
the far right hand side of the Status Information Bar. are displayed in the correct notifications are displayed in the
position correct location
GVA_HMI_117 Key The current alarms shall be displayed as 'active Current alarm display format Inspection Inspect to ensure the alarm
counters' in the format Wn, Cn and An, where n is is correct and alarm notifications are displayed in the
the number of active alarms in that category. counters update within 1 correct format (Wn, Cn, An)
seconds of an alarm
condition being generated.
GVA_HMI_118 Key The Status Information Bar shall show the current The heading is shown in the Inspection Inspect to ensure that the heading
vehicle heading in NATO angular mils (1 mil = correct format consistent is shown in the same format as the
1/6400 of a circle) consistent with the PPI selection. with the PPI selection PPI
GVA_HMI_110 1 It shall be possible to temporarily hide labels and Status Information Bar 'Hide' In certain situations the full Inspection and Inspect to ensure the function is
the Status information Bar from the GVA display function exists and removes screen is required for other Test provided and test to ensure the
screen. the Status Information bar information labels and status bar can be hidden
from view when it is pressed.
GVA_HMI_112 1 The Time Zone used to display of the 'date time 'Date Time Group' Test Test to ensure that the Date and
group' on the Status Information Bar shall be information displayed on the Time can be configured at each
configurable on each [GVA HMI] display. Status Information Bar can GVA HMI display
be configured on each [GVA
HMI]
GVA_HMI_114 1 The Status Information Bar shall show the vehicle 'Grid position' information Accuracy of grid references JSP 465 - Geospatial Inspection Inspect the display to ensure that
platform's grid reference in an 8 figure format plus displayed on the Status may need to be increased for Information Policy for UK the grid reference is in the correct
any leading characters. Information Bar is presented certain tasks. Leading Defence format
to the necessary level of characters are required when
operating near grid
52
Verification
Method
accuracy boundaries.

3.3 Top Level Menu Buttons
GVA_HMI_120 Key The Top Level Menu Buttons shall be used for the GVA functional areas can Review Review design documentation to
sole purpose of selecting the functional area with only be accessed via the ensure the TLMBs are provided a
which the operator wishes to interact. Top Level Menu Buttons the sole means of accessing the
functional areas

3.4 Common Function Labels and Buttons
3.4.1 Bottom Bezel Button Function Allocation
GVA_HMI_124 Key The bottom row of bezel buttons shall be reserved Bottom Bezel Button are Review Review design documentation to
for those controls that are used in many or all the only used for cross ensure the bottom bezel buttons are
GVA functional areas. functional area controls only used for cross functional area
controls
GVA_HMI_125 Key The label describing the functionality of each Each Botttom Bezel Button Inspection Inspection to ensure that each
common function bezel button shall be provided on has an associated soft label bottom bezel button has an
the display screen. associated soft label
GVA_HMI_126 1 F13 shall be labelled 'Up' or 'Cancel' dependant on F13 is appropriately labelled Inspection Inspection to ensure the correct
current function. 'Up' or 'Cancel' button - label allocation.
GVA_HMI_127 1 F13 shall navigate up a level in the menu structure if F13 navigates up the menu Test Test to ensure the bottom behaves
dialog is not active. structure accordingly
GVA_HMI_128 1 F13 shall be the equivalent to a cancel function if a F13 cancels dialogs Inspection Inspection to ensure the correct
dialog is active. button - label allocation.
GVA_HMI_129 1 F14 shall be labelled 'Alarms'. F14 is labelled 'Alarms' Inspection Inspection to ensure the correct
button - label allocation.
GVA_HMI_130 1 Operation of F14 shall display the 'Alarms' Table. Alarms Table displays when Test Test to ensure the bottom behaves
F14 is pressed accordingly
GVA_HMI_131 1 F15 shall be labelled 'Threats'. F15 is labelled 'Threats' Inspection Inspection to ensure the correct
GVA_HMI_132 1 Operation of F15 shall brings up a display detailing Threat event display is Test Test to ensure the bottom behaves
all threat events. activated when F15 is accordingly
pressed
GVA_HMI_133 1 F16 shall be labelled 'Ack'. F16 is labelled 'Ack' Inspection Inspection to ensure the correct
GVA_HMI_134 1 Operation of F16 shall acknowledge alerts, stopping Alerts are 'Acknowledged' Test Test to ensure the bottom behaves
the associated audio tone. when F16 is pressed accordingly
GVA_HMI_135 1 F17 shall be labelled 'Arrow Up'. F17 is labelled 'Arrow Up' Inspection Inspection to ensure the correct
53
Verification
Method
GVA_HMI_136 1 Operation of F17 shall scroll up through menu Scrolls up menu options or Test Test to ensure the bottom behaves
options or increase values where required. increases values accordingly
GVA_HMI_137 1 F18 shall be labelled 'Arrow Down'. F18 is labelled 'Arrow Down' Inspection Inspection to ensure the correct
GVA_HMI_138 1 Operation of F18 shall scroll down through menu Scrolls down menu options Test Test to ensure the bottom behaves
options or reduce values where required. or deccreases values accordingly
GVA_HMI_139 1 F19 shall be labelled 'Labels'. F19 is labelled 'Labels' Inspection Inspection to ensure the correct
GVA_HMI_140 1 Operation of F19 shall hide or display the labels Hides and displays the bezel The Plan Position Indicator Test Test to ensure the bottom behaves
associated with the bezel buttons, the Status button labels, Status (PPI) would be considered a accordingly
Information Bar and non critical overlays, such as Information Bar and non- non-critical overlay.
the Plan Position Indicator (PPI). critical overlays
GVA_HMI_141 2 When operating F19, a multi-state function should Multi-state function exists for example press once and Test Test to ensure the bottom behaves
be implemented that provides the ability to select bezel button labels are accordingly
and hide various combinations of display features. hidden. Press again and bezel
button labels and status
information bar are hidden,
press again and all overlays
are hidden, press again all
visible.
GVA_HMI_142 1 F20 shall be labelled 'Enter'. F20 is labelled 'Enter' Inspection Inspection to ensure the correct
GVA_HMI_143 1 Operation of F20 shall enter data into a form field, Performs the correct funtion Test Test to ensure the bottom behaves
activate a highlighted menu option or accept the for form fields, menu accordingly
input into a dialog box. selections and dialog box
acceptance.

3.5 Reconfigurable Labels and Buttons
GVA_HMI_157 Key Bezel buttons F1-F12, and associated on-screen Buttons F1-F12 are Review Review design documentation to
labels, shall be reconfigurable depending on the reconfigured depending on ensure the F1-F12 are
functional area selected and the page content. the functional area and are reconfigurable depending on the
be labelled according to functional area and are be labelled
function accordingly
GVA_HMI_158 1 Where there are common functions within and Common functions appear To aid learning and to make Review Review design documentation to
across functional areas and menu pages, these on the same buttons within the system more intuitive to ensue that common functions are
shall be allocated to the same bezel button. and across the functional use. allocated to the same button
areas throughout the system

3.6 Plan Position Indicator
GVA_HMI_161 Key The Plan Position Indicator (PPI) shall, be present PPI exists in SA, WPN, DRV Review and Review the design documentation
by default in the SA, WPN and DRV functional screens displaying video Test and test to ensure that the PPI is
present as default on the required
54
Verification
Method
areas when displaying video feeds. feeds pages
GVA_HMI_163 Key The PPI shall include: A PPI includes the Sight system orientation could Inspection Inspect the PPI to ensure to
necessary features and be represented by a segment consists of the required elements
information graphic (line outlines or block
colour) indicative of FOV and
a) A marker showing the orientation of North central line (for non weapon-
aligned trainable sights) to
b) 32 equally spaced marks around the edge indicate the centre of the
FOV.
c) An icon to represent the [vehicle platform],
located at the centre of the PPI, where the
orientation of the [vehicle platform] is clearly
identifiable
d) An indication of the orientation of weapons in Potential threats detected by

relation to the [vehicle platform] body equipment systems (e.g. shot
detection systems) could be
e) A graphical view showing the orientation of any shown, using symbology,
weapon sights around the edge of the PPI to
indicate type and relative
f) An icon showing the position of any high priority
orientation of the threat to the
threats
[vehicle platform].
g) The position and size of the Field of View (FOV)
of any sensor selected in a specific functional area
GVA_HMI_165 Key The PPI shall be located in the top left of the display PPI is located in the top left Inspection Inspect to ensure that the PPI is
screen area by default. of the display positioned as default in the top left
corner
GVA_HMI_167 Key The PPI orientation shall be 'Heading Up' on all non- PPI displays in a 'Heading To be common with other Inspection Inspect to ensure that the PPI is
map displays. up' orientation similar HMI displays to reduce 'heading up' on all non map
the training burden displays
GVA_HMI_168 Key The PPI orientation shall be consistent with the map PPI orientation is consistent To be common with other Inspection Inspect to ensure that the PPI
orientation as selected on any map display. with map orientation similar HMI displays to reduce orientation is consistent with the
selection the training burden map orientation
GVA_HMI_169 Key If a threat warning is received while the PPI is The PPI reappears from a If the user hides the status Test Test to ensure that when a threat
hidden, the PPI shall reappear with an indication of hidden state if a new threat bar/PPI and a new threat is warning enters the system an
the threat orientation relative to the [vehicle warning is received detected the user needs to be indication appears on the PPI in the
platform]. informed of the threat location. correct position relative to the
vehicle platform
GVA_HMI_166 1 The position of the PPI shall be configurable so it The PPI position is If the top left hand corner is Review and Review design documentation to
can be optimally positioned for the page layout. configurable not suitable i.e. covers Test ensure that the PPI doesn't cover
important information or an critical information on any of the
image menu pages
GVA_HMI_162 2 The PPI should be displayable in all functional PPI is available for display in Review and Review design documentation to
areas. all funtional areas Test ensure that the PPI can be
displayed in all functional areas
55
Verification
Method

3.6.2 Weapon Orientation
GVA_HMI_171 Key Weapon orientation shall be represented by a line Weapon orientation icon is Ensure the weapon icon is e.g. red should not be used Review and Review the design documentation
which can be seen against all potential background visible on all possible GVA clear and unambiguous Test and test the line colour to ensure it
colours, whilst not causing confusion by HMI background colours and contrasts with all background
contradicting other colour conventions. does not contradict with any colours used on the screen and
other use of colour ensure that it does not contradict
conventions

3.6.3 Sight Orientation
3.6.4 Threat Warning Indication
3.7 Symbology
GVA_HMI_175 1 Any symbols that are associated with hard controls To prevent the symbol from Inspection Inspect to ensure there are labels
that rotate, shall be located adjacent to the control. rotating and to maintain adjacent to the controls
interpretability

3.8 Use of Colour

3.8.1 Use of colour across the GVA HMI
GVA_HMI_177 Key The [GVA HMI] shall comply with the colour Complies with the colour for example the colour red Review and Review the design documentation
conventions stated in Def Stan 00-250 Table 15.2 conventions stated in Def shall only be used for Test and test to ensure the use of colour
Stan 00-250 Table 15.2 emergency controls. complies with Def Stan 00-250 table
15.2
GVA_HMI_178 Key Colour coding shall only be used as a Colour is never relied on To account for colour blind Colour is such a dominant cue Inspection Inspect to ensure that colour is
supplementary method of presenting information. alone for presenting [operators] and to reduce the that it can influence task never the sole method of presenting
information incidence of misinterpretation performance even when it is information
irrelevant to the task at hand,
and can therefore inhibit
discrimination based on other
coding dimensions.
[Guidance]
Consideration should be given

to the choice of colours to be
used in displays. Ambient
lighting levels and display
contrast and luminance all
affect the way colour is
perceived by a human
operator, and shall be taken
into account when selecting
colours for use in
displays.[Guidance]
GVA_HMI_184 Key The following colour conventions shall be used Required colours are used (e.g. grey label text indicated Review and Review the design documentation
across the [GVA HMI]: option not available) Inspection to confirm the RGB values and
inspect the colours used on the
GVA HMI to ensure they comply
56
Verification
Method
a) Green (RBG 0,255,0): On, Good, OK, Safe with the conventions
b) Yellow (RGB 255,255,0): Advisory Warning
c) Amber (RGB 255,153,0): Caution
d) Red (255,0,0): Armed, Danger, Critical Warning,

Failure, Stop
e) Grey (RGB 127,127,127): Not available or Off
f) Dark Green (RGB 0,75,0): Background colour for

soft keys and soft key labels which are available for
selection
GVA_HMI_179 1 The number of combined background and Def Stan 00-250 Section Review and Review the design documentation
foreground colour combinations used shall no more 15.2.4 Inspection and inspect the GVA HMI to count
than 24, with the exception of mapping and colour the number of colour combinations
video.

3.8.2 Use of Colour on the GVA Display Screen
GVA_HMI_181 Key The background colour shall be maintained across Background colour Review and Review the design documentation
all related areas of the GVA display screen. maintained inspection and inspect the display to ensure
the background colour is
maintained
GVA_HMI_180 1 No more than 7 colours shall be used on a GVA Review and Review the design documentation
Screen, with the exception of mapping and colour Inspection to count the number of colours and
video. inspect the HMI to ensure a
maximum of 7 colours are used
GVA_HMI_182 1 The text on soft keys and soft key labels, shall be Required colours are used Review and Review the design documentation
white (RGB 255,255,255) on a dark green Inspection to confirm the RGB values and
background. inspect the colours used on the
with the conventions
GVA_HMI_183 1 In text entry fields, text shall be black (RGB 0,0,0) Required colours are used Review and Review the design documentation
on a white (RGB 255,255,255) background. Inspection to confirm the RGB values and
inspect the colours used on the
GVA_HMI_185 1 Colours used for overlays, such as reticules, shall Colours used have high Review and Review the design documentation
have a high contrast with each other and all contrast as described in: Inspection to confirm the contrast levels and
potential background colours. inspect the colours used on the
http://snook.ca/technical/colo
57
Verification
Method
ur_contrast/colour.html

3.9 Text and Icons
3.9.1 Size
GVA_HMI_188 1 Alphanumeric characters presented on the GVA Angle subtended is within For effective presentation (i.e. Inspection Measure the text size to ensure it
display screen shall subtend an angle of at least limits to overcome vibration effects) complies
0°22' vertically at the [operator's] eye.
IAW Def Stan 00-250
Def Stan 00-250 part 3

Section 15
GVA_HMI_189 1 Alphanumeric characters presented on the GVA Angle subtended is within For effective presentation (i.e. Inspection Measure the text size to ensure it
display screen shall subtend an angle of at least limits to overcome vibration effects) complies
0°14' horizontally at the [operator's] eye.
IAW Def Stan 00-250

Section 15
GVA_HMI_190 1 Icons presented on the GVA display screen shall Angle subtended is within Inspection Measure the text size to ensure it
subtend an angle of at least 0°24' vertically at the limits complies
[operator's] eye.
GVA_HMI_191 1 Icons presented on the GVA display screen shall Angle subtended is within Inspection Measure the text size to ensure it
subtend an angle of at least 0°26' horizontally at the limits complies
[operator's] eye.
GVA_HMI_192 1 No alphanumeric characters on the GVA display Angle subtended is within IAW Def Stan 00-250 Inspection Measure the text size to ensure it
screen shall subtend an angle of more than 0°37' limits complies
vertically at the [operator's] eye.
Section 15

3.9.2 Text Case
GVA_HMI_194 Key Block capitals shall only be used for headlines, key Block capitals only used for Capital letters reduce the Inspection Ensure that block capitals are only
phrases or acronyms. headlines, key phrases or legibility of text used for acronyms, key phrases or
acronyms. headlines
GVA_HMI_195 Key Labels and titles shall use an initial capital letter for Labels and titles use initial Inspection Ensure that leading capitals are
each word. capitals used for labels and titles
58
Verification
Method

3.9.3 Fonts
GVA_HMI_197 Key ‘Monospace typewriter’ font shall be used for all Review Review design documentation to
alphanumeric characters on the GVA display ensure that Monospace typewriter
screen. font is used for alphanumeric
characters

3.9.4 Labelling
GVA_HMI_200 Key Soft key labels shall indicate the function that will be Soft keys labelled correctly Test Test to ensure that the soft key
performed or the state that will be entered, when the labels indicate the state that will be
associated bezel button is activated. entered when activated
GVA_HMI_201 Key Where it is not obvious what is currently displayed Textual indication of display This will avoid confusion and Test Test to ensure that there is a textual
there shall be a textual indication on the screen of state present on the screen make it easier for the indication of the state on the screen
the current displayed state. [operator] to rapidly interpret
the current state of the
displayed information.
GVA_HMI_203 Key Text shall be left aligned for labels on the left of the Text left aligned Inspection Inspect to ensure that labels on the
GVA display. left hand side of the display screen
are left justified
GVA_HMI_204 Key Text shall be right aligned for labels on the right of Text right aligned Inspection Inspect to ensure that labels on the
the GVA display. right hand side of the display screen
are right justified
GVA_HMI_205 Key Text shall be centrally aligned for labels along the Text centrally aligned Inspection Inspect to ensure that labels in the
top or bottom of the GVA display. centre of the display screen are
centrally aligned
GVA_HMI_206 Key The style of the soft key labels shall change Label styles change Test Test to ensure the soft key labels
depending on state: correctly change depending on state as
defined.
a) A soft key label for a function which is available

but not selected shall have white text on a green
background
b) A soft key label for a function which is available

and selected shall have white text on a green
background, a yellow border with a black outline
c) A soft key label for a function which is unavailable

shall be grey
Note: RGB values are specified in GVA_HMI_184
GVA_HMI_370 Key All soft keys and hard controls shall be labelled with Inspection Inspect to ensure the labels are
text which provides a clear unambiguous provided which unambiguously
59
Verification
Method
representation of the function, except where represent the function

graphical representation has been accepted by the
operator community.

4 Top Level Menus
GVA_HMI_209 Key The correct page shall be displayed with 1 second Menu pages display within 1 Appropriate system speed Test Test and time moving between
of making a top level menu button selection. second of selection menu pages
GVA_HMI_210 Key When a top level menu button is pressed once, for Correct menu page displays Test Test to ensure appropriate
the functional area currently selected, the top level within time limits behaviour is produced
menu page for that functional area shall be
displayed.
GVA_HMI_211 Key When a top level menu button is pressed once, for a Correct menu page displays Test Test to ensure appropriate
different functional area than that currently selected, within time limits behaviour is produced
the page that was last viewed for that functional
area shall be displayed.
GVA_HMI_212 Key Pressing a top level menu button twice, for a Correct menu page displays Test Test to ensure appropriate
different functional area than that currently selected, within time limits behaviour is produced
shall display the top level menu page for that
functional area.
GVA_HMI_218 Key A green bar shall be displayed directly underneath Green bar exists underneath To indicate which functional Inspection Inspection to ensure the appropriate
top level menu buttons that have available the buttons when functions areas are available for coloured bar is displayed in the
functions. are available selection. correct location
GVA_HMI_213 1 It shall take no more than three button presses to no more than three button Set up or rarely used Review Review the design documentation
access the most commonly used functions and pressess required to access functionality can if necessary, including the menu hierarchy
those of operational importance. the most commonly used sit below the third menu layer, diagram
functions if the menu requires more
than 3 layers.
GVA_HMI_214 1 There shall be consistency with menu and option Menu and option labels are This will help to prevent users Review and Review design documentation and
labels across functional areas. consistent across functional becoming lost within the menu Inspection inspect to ensure there is
areas structure. consistency with the menus and
option labels across functional
areas
GVA_HMI_215 1 Drop down menus shall only be provided for Drop down menus only used Only appropriate for these Inspection Inspect to ensure drop down menus
maintenance purposes, set-up functions or for stated purposes types of functions are only provided for stated
operational reporting functions. purposes
GVA_HMI_219 1 When a top level menu button is selected the Yellow outline around the To indicate the selection. Inspection Inspection to ensure the appropriate
displayed green bar shall have a yellow outline. box appears on selection coloured bar is displayed in the
correct location
GVA_HMI_220 1 A grey bar shall replace the green bar if a functional Grey bar is displayed Inspection Inspection to ensure the appropriate
area is temporarily unavailable. coloured bar is displayed in the
correct location
GVA_HMI_374 2 If a functional area has not been implemented then Inspection Inspection to ensure the appropriate
the bar should be black. coloured bar is displayed in the
correct location
60
Verification
Method

4.2 GVA Functional Areas
GVA_HMI_376 Key The top bezel buttons shall be labelled: Review and Review design documentation and
Inspection inspect the GVA HMI display to
a) SA ensure the bezel buttons are
labelled as specified
b) WPN
c) DEF
d) SYS
e) DRV
f) STR
g) COM
h) BMS

4.3 GVA Functional Area Descriptions
4.3.1 SA - Situational Awareness
GVA_HMI_223 Key Selecting SA shall provide access to the SA Enters SA functional area Test Test to ensure pressing the buttons
functional area. enters the correct functional area
GVA_HMI_224 Key The SA Functional area shall display video feeds Video feeds are displayed Inspection Inspect the SA functional area to
from the LSA cameras fitted to the vehicle platform. ensure video feeds are displayed
GVA_HMI_225 Key The top level menu for the SA functional area, shall LSA overview provided Inspection Ensure the correct overview page is
provide an overview of LSA capabilities available. displayed
GVA_HMI_229 Key It shall not be possible to initiate munitions from the No functions to initiate All safety related functions Test Test to ensure no munitions can be
SA functional area. munitions are initiated via the WPN initiated from the SA functional area
functional area or HCP
GVA_HMI_230 Key Direction of video feed views shall be shown relative Direction of view displayed To make it's orientation Inspection Inspect to ensure the video feeds
to the vehicle platform direction. in a manner which is easily immediately obvious. are shown relative to eh vehicle
identifiable by the [operator] platform
GVA_HMI_226 1 Display of video feeds shall be selectable between Single and multiple (mosaic) Test Test to ensure video feeds are
single video feed or a multiple (mosaic) video feed. views available selectable.
GVA_HMI_227 1 When viewing a single video feed in the SA Necessary functions c) So weapons or sight [sub- Note: Automatic or manual Inspection Inspect to ensure the correct
functional area, the following functions should be available systems] can be slewed transfer from SA to WPN information and functions are
available. functional area may follow, displayed in the SA function area
based upon the cued resource
type and its availability in a
multi-user system
a) select all LSA video feeds in a logical sequence
b) select the video feeds from weapon sight

system(s) or other sensors
c) The means to designate a point on the image

61
Verification
Method
being viewed such that the point co-ordinates can

be handed over to a weapon or or sight [sub-
system]
GVA_HMI_228 1 When viewing multiple video feeds in the SA Necessary functions Inspection Inspect to ensure the correct
Functional area, in a mosaic view, the following available information and functions are
functions shall be available: displayed in the SA function area
a) an indication of which feeds are being viewed
b) selection of a different combination or

arrangement of video feeds
c) selection of the video feeds to form the mosaic

view from weapon sight system(s) or other sensors
d) the means to designate a point on any of the

images being viewed such that it handed over to a
weapon or sight sub-system
e) selection of any one of the mosaic video feeds to

view as a single video feed
f) an indication of what video feeds the operator is

viewing
GVA_HMI_231 1 Composite (stitched) video from multiple feeds shall Image orientation identifiable To make it's orientation Test Test to ensure operators can
include a means to easily identify the orientation of by the [operator] immediately obvious. identify the orientation of the image
the 'stitched' image relative to the [vehicle platform] relative to the vehicle
hull alignment.
GVA_HMI_232 1 Where an area of a composite (stitched) video Area highlighting present Inspection Inspect to ensure there is an
image can be selected for magnification, a method indication as to which part of a
of highlighting the selected area shall be provided. stitched image has been magnified
GVA_HMI_233 1 Video feeds from rearward looking cameras used Video display not mirrored For a common approach and Inspection Inspect to ensure the rearward
for non-driving functions, shall not be 'mirrored' by by default to reduce the training burden video feeds are not mirrored by
default. default
GVA_HMI_234 1 There shall be a textual indication of mirroring Textual 'Mirror' indication Inspection Inspect to ensure there is a textual
overlaid to the outside of the main viewing area on overlaid on the image indication where video feeds are
any mirrored imaged. mirrored
GVA_HMI_235 1 If the [vehicle platform] is fitted with an Electro-optic EO & TI controllable via the Test Test to ensure that EO & TI are
or thermal imaging [sub-system], which is not linked SA functional area controllable via the SA functional
to a weapon system, then it shall be possible to area
control functions related to those [sub-systems] from
the SA functional area.
GVA_HMI_236 1 Changing between cameras views in the SA View changes in < 0.5 Appropriate speed to maintain Test Test and time moving between
functional area shall take less than 0.5 seconds. seconds SA video feeds
GVA_HMI_237 1 Changing between magnification levels for camera View changes in < 0.5 Appropriate speed to maintain Test Test and time moving between
views shall take less than 0.5 seconds. seconds SA video feeds
62
Verification
Method
GVA_HMI_238 1 Pan/tilt functionality for sensors and cameras shall Pan/Tilt functionality exists Inspection Inspect to ensure pan/tilt is
be available when the SA functional area is available
selected.

4.3.2 WPN - Weapons
GVA_HMI_240 Key Selecting WPN shall provide access to the WPN Enters WPN functional area Test Test to ensure pressing the buttons
GVA_HMI_241 Key All weapon [sub-systems] shall be controlled and All weapon [sub-systems] Inspection Inspect to ensure that all weapon
initiated from the WPN functional area. controlled and intitated via sub systems are controlled and
the WPN functional area initiated via the WPN functional
area
GVA_HMI_244 Key When in the WPN functional area there shall be a Control indication provided Inspection Inspect to ensure clear indications
clear indication of which [GVA HMI] has control of a are provided as to which GVA HMI
weapon sub-system. has control
GVA_HMI_257 Key There shall be the capability to access more Access to detailed Inspection Inspect to ensure that more detailed
detailed information about a selected [sub-system]. information provided information can be accessed
GVA_HMI_247 Key When in the WPN functional area, the [GVA HMI] Weapon states indicated Weapon states could include Inspection Inspect to ensure that the weapon
shall clearly indicate weapon states. the following: states are clearly shown
a) Set up / Configuration /
Maintenance (Safe mode)
b) Target acquisition (Not

armed)
c) Target engagement
(Armed)
GVA_HMI_248 Key the [GVA HMI] hand controller(s) shall provide all All controls provided to In addition to the functionality Test Test to ensure that all controls
the controls required to engage a target with the engage a target from the on the hand controllers, extra required to engage a target are
selected weapon [sub-system]. WPN functional area options may be required on provided in the WPN functional area
the display. Depending on the
specific system fitted, these
may include:
Sight functions:
a) Toggle between TI
white hot/black hot
b) Sight Set Up (takes

the [operator] to the set up
menu for whatever sight is
selected)
c) Focus in/focus
out/auto focus for current sight
selected
d) Select FOV or
63
Verification
Method
magnification
And Weapon functions:
a) Weapon set up –
boresight etc
b) Manual range entry
c) Laser Range Finder

mode
GVA_HMI_249 Key The information and aiming marks for a selected Information and aiming Information could include the Inspection Inspection to ensure all the required
weapon [sub-system] should be displayed. marks displayed following: information is displayed
a) Ammunition Type
b) Weapon [arming] status –

safe or armed
c) Weapon mode of operation

e.g. single shot, 3 round burst,
airburst
d) Quantity of ammunition
remaining
e) Distance to target
f) Default Range for currently

selected weapon and
ammunition type
g) Azimuth and elevation of

the weapon in NATO angular
mils
h) Sight Magnification level
i) Thermal Imaging Settings
GVA_HMI_242 1 Where multiple weapon [sub-systems] are available, Overview displayed as the Inspection Ensure the correct overview page is
the WPN functional area top level menu page shall top menu page displayed
show an overview of the status of each of the
weapon [sub-systems].
GVA_HMI_243 1 The WPN functional area top menu page shall Correct information To make it's orientation Inspection Inspection to ensure all the required
display the sight picture, appropriate information displayed immediately obvious. information is displayed
and aiming marks if a single weapon [sub-system] is
fitted.
GVA_HMI_245 1 Bezel Buttons or soft keys shall be used to gain Weapon [sub-systems] Test Test to ensure that, when more
access to information on each weapon [sub- selectable by bezel buttons than one weapon [sub-system] is
system], when more than one weapon [sub-system] fitted, weapons are selected via the
64
Verification
Method
is fitted. or soft keys bezel buttons

4.3.3 DEF - Defensive Systems
GVA_HMI_251 Key Selecting DEF shall provide access to the DEF Enters DEF functional area Test Test to ensure pressing the buttons
GVA_HMI_252 Key The DEF functional area shall control and intiate all All defensive [sub-systems] Test Test to ensure that defensive sub
defensive [sub-systems]. controlled and intitated systems are controlled from the
DEF functional area
GVA_HMI_253 1 The DEF functional area shall display the options Options and relevant DEF Inspection Inspect to ensure that all
and information relevant to the selected defensive information displayed information relevant to the selected
capability. defensive system is displayed in the
DEF functional area
GVA_HMI_254 1 The DEF functional area top level menu screen Status overview of all the Inspection Ensure the correct overview page is
shall give an overview of the status of all the DEF sub systems provided displayed
installed defensive [sub-systems]. as the top level menu page
GVA_HMI_255 1 Defensive [sub-systems] shall be selected by a Defensive [sub-system] Test Test to ensure that, when more
bezel button (or soft key), where there is more than selection by bezel button (or than one defensive [sub-system] is
one defensive [sub-system] fitted. soft key) where there is fitted, the sub systems are selected
more than one sub system via the bezel buttons

4.3.4 SYS - Systems
GVA_HMI_259 Key Selecting SYS shall provide access to the SYS Enters SYS functional area Test Test to ensure pressing the buttons
GVA_HMI_260 Key The SYS functional area shall provide monitoring Necessary functions Inspection Inspect to ensure that all
and control of GVA wide functions and configuration provided information for monitoring,
along with [sub-system] health, status and controlling and configuration GVA
configuration. wide functions and health, status
information is displayed in the SYS
functional area
GVA_HMI_261 Key Access to individual [vehicle platform] [sub-systems] Bezel buttons (or soft key) Test Test to ensure that sub system
information and control shall be by selection of a used to select [sub-systems] information is selected via the bezel
bezel button (or soft key). buttons
GVA_HMI_262 Key The SYS functional area shall provide: Provision of listed Inspection Ensure the correct information is
information and functions displayed
a) A 'top-level' menu page with an overview of all

mission essential [sub-systems] (MES) as defined in
the individual [vehicle platform] SRD
b) Access to more detailed information about each

of the [vehicle platform] [sub-systems]
c) the means to configure the position and format of

information presented on the GVA display screen
(e.g. position of the PPI, time format)
d) access to the power management functions
65
Verification
Method
within the [vehicle platform]
GVA_HMI_377 1 The SYS functional area shall provide: Inspection Ensure the correct information is
displayed
a) Access to historical information stored in the

HUMS [sub-system]
b) Access to real time 'system' data from the GVA

Infrastructure
c) Access to Interactive Electronic Technical

Publications (IETP)/manuals for [vehicle platform]
and [sub-systems]
GVA_HMI_378 2 The SYS functional area should provide the means Inspection Ensure the correct functions is
to configure the [GVA HMI] to reflect the needs of displayed
various [vehicle crew] roles

4.3.5 DRV - Driver
GVA_HMI_264 Key Selecting DRV shall provide access to the DRV Enters the DRV functional Advice on the standards for Test Test to ensure pressing the buttons
functional area. area driver information systems enters the correct functional area
may be sought from 'EN
Commission
Recommendations on Safe
and Efficient In-Vehicle
Information and
Communication System'
(2077/78/EC). [Guidance]
GVA_HMI_265 Key The DRV functional area shall provide information All driving functions Inspection Inspect to ensure that all
relating to driving functions and automotive accessed from the DRV information for driving and
information. functional area automotive functions is displayed in
the DRV functional area
GVA_HMI_266 Key The DRV functional area shall provide the means to Driving aids displayable Inspection Ensure the correct functions is
view the following driving aid information on video displayed
feeds.
a) tramlines with distance markers
b) a heading indication in NATO angular mils
GVA_HMI_268 Key There shall be a textual indication of mirroring Textual 'Mirrored' indication To make it's orientation Inspection Inspect to ensure there is a textual
overlaid to the outside of the main viewing area on overlayed on the image immediately obvious. indication of mirroring overlaid on
any mirrored imaged. the image
66
Verification
Method

4.3.6 STR - Special to Role
GVA_HMI_270 Key Selecting STR shall provide access to the STR Enters STR functional area Test Test to ensure pressing the buttons
functional area dedicated to specialist sub systems, enters the correct functional area
which are not common across vehicle platforms.

4.3.7 COM - Communication
GVA_HMI_273 Key Selecting COM shall provide access to the COM Enters COM functional area Test Test to ensure pressing the buttons
GVA_HMI_274 Key The COM functional area shall control and configure Communication [sub- This includes [sub-systems] Inspection Inspect to ensure that all
[vehicle platform] communication [sub-systems]. systems] can be configured that provide onboard and information for configuring
and controlled offboard communications communication sub systems is
including the[vehicle platform] displayed in the COM functional
intercom [sub-system]. area

4.3.8 BMS - Battlefield Management System
GVA_HMI_276 Key Selecting BMS shall provide access to the BMS Enters BMS functional area Test Test to ensure pressing the buttons
GVA_HMI_277 Key The BMS functional area shall display and BSA displayed and Inspection Inspect to ensure that all
manipulate information and mapping relating to manipulated appropriately information for manipulating
Battlefield Situational Awareness. information and mapping relating to
Battlefield Situational Awareness is
displayed in the BMS functional
area
GVA_HMI_278 Key The BMS functional area shall display and C2 displayed and Inspection Ensure the correct information is
manipulate information relating tactical and manipulated appropriately displayed
operational C2.
GVA_HMI_279 Key The BMS functional area shall provide the displays Inspection Inspect to ensure the displays for
for [vehicle platform] navigation information and [vehicle platform] navigation
mapping. information and mapping are
provided in the BMS functional area

4.3.8.1 Mapping Displays
GVA_HMI_281 Key Grid overlays on vector maps shall be [operator] STANAG 2211 Ed6 Inspection and Ensure the correct options are
selectable between: Test available and that they are
selectable
British National Grid Format (When in applicable

area)
Irish Grid Format (When in applicable area)
67
Verification
Method
Local Grid Format
GVA_HMI_282 Key Grid overlays on maps shall be [operator] STANAG 2211 Ed6 Test Test to ensure that the grid overlays
configurable to display any local grid reference are operator configurable to any
system using NATO approved local to WGS84 local grid reference system
datum transformation parameters.
GVA_HMI_283 Key Grid overlays on vector maps shall be presented Inspection Inspect to ensure the grids are
with grids projected as squares. projected as squares

4.4 System Start Up
5 Data Entry
GVA_HMI_286 Key The [GVA HMI] shall have the facility to enter free The ability to input free text This may be achieved through Review and Review design documentation and
text and numerical data. and numerical day is the use of a physical Test test to ensure that free text and
available keyboard, an on-screen numbers can be entered
keyboard or similar
technology
GVA_HMI_288 Key Templates or fill-in forms shall be provided for data Templates and fill in form (such as contact reports) Review and Review design documentation and
entry for common tasks. provided for data entry for Inspection test to ensure that templates or fill-
common tasks in forms are provided for common
tasks
GVA_HMI_289 Key A template or fill-in form shall provide visual Data input fields provide Review and Review design documentation and
indication where text or numbers can be entered. visual indication of their Inspection inspect to ensure that templates or
existence fill-in forms are provided for
common tasks
GVA_HMI_292 Key There shall be a method of moving the GVA display Review and Review design documentation and
screen cursor between data entry fields. Test test to ensure that a method of
moving the GVA display screen
cursor between data entry fields is
provided
GVA_HMI_293 Key Entered text shall be left justified. Text is left justified Common approach and layout Inspection Inspect to ensure that entered text
is left justified
GVA_HMI_294 Key Entered numerical data shall be right justified. Numbers are right justified Common approach and layout Inspection Inspect to ensure that entered
numbers are left justified
GVA_HMI_287 1 The following functions shall be available to support The list controls are provided To maintain a common design Inspection Ensure the correct functions are
data entry and navigation: and function as described displayed
a) Accept a value and move to the next data field
b) Move back to the previous data field
c) Save the data field changes and exit data entry
68
Verification
Method
d) Exit data entry without saving changes
GVA_HMI_290 1 Data input fields shall be logically grouped. Input fields are logically Inspection Inspect to ensure that data inputs
grouped fields are logically grouped
GVA_HMI_291 1 Data input field titles shall be meaningful. The [operators] are able to Reduce the training burden Test Inspect to ensure that field titles are
understand the meaning of meaning to the operators
all field titles
GVA_HMI_295 1 Functions to delete information shall require All delete actions require Test Test to ensure that confirmatory
confirmatory action. confirmation action is required when deleting
information
GVA_HMI_296 1 The GVA display screen shall provide visual Visual responses provided responses could include Test Test to ensure that visual
responses to the input or selection of data. status (e.g. busy), responses are provided.
confirmation and verification
i.e. borders / colour changes
and / or audio tones.

6 Alerts
6.1 Visual Presentation of Alarms
GVA_HMI_307 Key Alarms shall be categorised into warning, caution alarms are categorised Review and Review the design documentation
and advisories. correctly Inspection and inspect to ensure that the
alarms are split into the necessary
categories
GVA_HMI_308 Key Any alarm text message shall be displayed directly Warning Text messages Inspection Inspect to ensure the text
beneath the Status Information Bar. appear in the correct messages are displayed in the
location correct location
GVA_HMI_309 Key Alarms that are overridden shall be redisplayed on Alarms redisplayed on GVA Test Test to ensure that overridden
GVA start up. start up alarms are redisplayed on GVA
start up.
GVA_HMI_379 1 Text messages shall be structured according to the Review Review design documentation to
following syntax: ensure the correct syntax is
adopted for all alarm text messages
Category - Subsystem – Component – Nature -
Type
E.g. W – Engine Oil Low Pressure

6.1.1 Warnings
GVA_HMI_311 Key A Warning alarm shall generate a text message. Text messages 'pop-up' on Review and Review the design documentation
waning events Test and test to ensure that text
messages are generated
GVA_HMI_312 Key Warning alarm text messages shall describe the Alarm descriptions include Review and Review the design documentation
nature of the associated alarm. enough detail for an Inspection and inspect to ensure that
[operator] to diagnose and messages describe the nature of
action the alarm the alarm
69
Verification
Method
GVA_HMI_313 Key A Warning alarm text message cannot be Lower priority alarms do not Test Test to ensure that a warning
overwritten by an alarm of a lower category. overwrite higher priority cannot be overridden by a caution
alarms of advisory
GVA_HMI_314 Key Upon selection of F16, after a warning, the Test Test to ensure the upon selection of
associated [GVA HMI] text message shall remain F16 the system behaves as
until the warning is cleared or overridden in the required
Alarms menu table.
GVA_HMI_315 Key The [GVA HMI] used by the [driver] shall have the Driver can 'hide' a warning To enable the driver to clearly Test Test to ensure the driver can
means to suppress and hide the display of a text message see video feeds. suppress and hide a text message
warning text message with a single bezel button in a single button press
selection.

6.1.2 Cautions
GVA_HMI_325 Key The [GVA HMI] shall handle multiple Caution alarms Multiple caution alarms are Test Test to ensure the system behaves
by presenting each one in turn for presented in turn as required
acknowledgement.
GVA_HMI_326 Key Cautions alarms triggered while a Warning alarm Caution alarms presented Test Test to ensure the system behaves
text message is displayed, shall only be presented correctly as required
if:
a) The warning alarm is resolved or overridden
and
b) The presentation time of the caution alarm has

not expired
GVA_HMI_318 2 A Caution alarm should generate a text message. Text messages 'pop-up' on Review and Review the design documentation
caution events Test and test to ensure that text
messages are generated
GVA_HMI_319 2 Caution alarm text messages should describe the Alarm descriptions include Review and Review the design documentation
nature of the associated alarm. enough detail for an Inspection and inspect to ensure that
[operator] to diagnose and messages describe the nature of
action the alarm. the alarm
GVA_HMI_320 2 If a Caution text message is displayed it should Caution text messages Test Test to ensure the system behaves
disappear if the alarm is acknowledged. disappear when as required
acknowledged
GVA_HMI_321 2 If a Caution text message is displayed it should be Caution text messages Test Test to ensure that a caution text
automatically acknowledged after 10 seconds. disappear automatically after message is automatically
[x] minutes/seconds acknowledged after 10 seconds
GVA_HMI_322 2 Cautions once acknowledged should be repeated Acknowledged Cautions Test Test to ensure that a caution text
after 2 hours if the event is still valid. repeated as required message is repeated after 2 hours if
70
Verification
Method
still valid
GVA_HMI_323 2 Cautions once acknowledged should be repeated Cautions repeated on GVA Test Test to ensure that a caution text
on GVA start up if the event is still valid. start up message is repeated at start up if
still valid

6.1.3 Advisories
GVA_HMI_381 2 Advisory alarms should not trigger a text message Review and Review the design documentation
on the display screen. Test and test to ensure that text
messages are not generated for
advisories
GVA_HMI_328 2 If a text message is implemented for Advisory Advisory alarms display Test Test to ensure the system behaves
alarms, the text message should: correctly as required
a) Automatically self clear after a set amount of time
b) Be overwritten by a higher priority alarm
c) Removed from the screen when ACK is pressed
GVA_HMI_382 2 Advisories should be repeated every 24 hours if the Test Test to ensure that a caution text
event is still valid. message is repeated every 24
hours if still valid
GVA_HMI_383 2 Advisories should be repeated at start up if the Test Test to ensure that a caution text
event is still valid. message is repeated at start up if
still valid

6.2 Alarms Menu Page
6.2.1 Alarm Menu Information
GVA_HMI_146 Key When F14 is selected the Alarms menu page shall Alarms menu page is Test Test to ensure the system behaves
be displayed. displayed as required when F14 is selected
GVA_HMI_148 1 The alarms menu page shall provide the following Correct information is Inspection Ensure the correct information is
information: presented displayed
a) The total number of acknowledged warnings,

b) The total number of unacknowledged warnings,

c) The current and total number of pages of alarms

e.g. Page 1 of 2
d) A table displaying all alarms (paged table if

required)
71
Verification
Method
GVA_HMI_149 1 The table displayed in the alarms menu page shall Alarm table contains the Status should include if the Inspection Ensure the correct information is
provide the following for each alarm: correct information alarm is still present/current displayed
a) Alarm title
b) Time of the alarm
c) Category of the alarm
d) Whether the alarm has been acknowledged
GVA_HMI_384 1 The alarm table shall following the syntax below: Review Review design documentation to
ensure the correct syntax is
Category - Subsystem – Component – Nature - adopted for all alarms in the alarm
Type table
GVA_HMI_147 1 The Alarms menu page shall by default list all Alarms are displayed sorted Inspection Inspection that the default is sort by
alarms sorted by category (most important first) then by category then time category (priority and then time)
time (most recent first).

6.2.2 Alarm Menu Functions
GVA_HMI_151 1 When displaying the table in the alarms menu page Listed functions exist and Inspection Ensure the correct functions are
it shall be possible to: operate correctly available
a) Sort by category (warnings, cautions, advisories)

– arranges the alarms displayed by category and
then time (most recent first)
b) Sort by time – arranges the alarms displayed by

time (most recent first) and then priority (most
important first)
c) To individually select alarms
c) Include/exclude acknowledged alarms – shows or

hides acknowledged alarms
d) View alarm detail – brings up more detail

regarding the alarm (if available)
e) Page Up and Page Down – navigate to the

next/previous page of alarms (if applicable)
72
Verification
Method
f) Acknowledge individual alarms
g) Acknowledge all alarms
h) Clear an individual alarm
i) Clear all alarms
j) Override an individual alarm

6.3 Visual Presentation of Threats
GVA_HMI_330 Key Threat text messages shall appear in a different Threat text messages to allow the messages for Inspection Inspect to ensure that the threat text
location to Alarm text messages. appear in a different location warnings and threats of equal messages appear in a different
to Alarm text messages priority to be presented on the location to alarm text messages
display simultaneously.
GVA_HMI_385 Key The syntax for a threat text message shall be the Review Review design documentation to
same as the alarms text messages. ensure the correct syntax is
adopted for all threat text messages
GVA_HMI_331 1 If a graphical threat display is implemented, Threats displayed correctly Review and Review design documentation and
individual threats shall be displayed as icons with Inspection inspect to ensure that the threat
ranges and bearings relative to the vehicle position. alerts are displayed correctly
GVA_HMI_333 1 A threat display shall identify the status of all sensor Sensor [sub-system] status to identify to the [operator that Test Test to ensure the correct status of
[sub-systems] fitted to the [vehicle platform]. is displayed what is displayed is not a all sub systems is shown on the
complete picture. threat display
GVA_HMI_332 1 If a graphical threat display is used, a means should De-clutter methods available test Test to ensure there is a function to
be provided to de-clutter the display by removing de-clutter the screen
nonessential and out-of-date threat information.

6.4 Threats Menu Page
GVA_HMI_153 Key When F15 is pressed the threats menu page shall Threat menu page displayed The threat events may be Test Test to ensure the system behaves
be displayed. presented to the user in a as required when F15 is selected
variety of formats e.g. tabular,
pictorial (a range card) or the
option for both. The method of
displaying the threats should
be defined in consultation with
the users. [Guidance]
GVA_HMI_154 Key The threat menu page shall provide the following Threat menu page displays Status includes if the threat is Inspection Ensure the correct information is
information: correct information still present/current available
73
Verification
Method
a) Type of threat
b) Location of threat
c) Time of the threat detection
d) Threat description/type (if appropriate)
e) Status of the threat
GVA_HMI_155 1 If displaying a table in the threats menu page, it Correct table functions exist Inspection Ensure the correct functions are
shall be possible to: available
a) Sort by type - arranges the threats by type and

then time (most recent first)
b) Sort by time – arranges the threats displayed by

time (most recent first) and then type (most
important first)
c) View threat detail – brings up more detail

regarding the threat (if available)
d) Select an individual threat
e) Page Up and Page Down – navigates to the

next/previous page of threats (if applicable)
f) Cancel an individual threat
g) Cancel all threats
GVA_HMI_386 1 The threats menu page shall following the same Review Review design documentation to
syntax as the alarms menu page. ensure the correct syntax is
adopted for all threat text messages
in the threats table

6.5 Audio Presentation of Alerts
GVA_HMI_335 Key There shall be an alert tone for Warning alarms, Review and Review design documentation and
Caution alarms, and Threats. inspection test to ensure alert tones are
produced for alarms and threats
GVA_HMI_336 Key The GVA alert tones, for Warning alarms, Caution Warnings, Cautions and redundant tone for either the Test Test to ensure alarm and threat
74
Verification
Method
alarms and Threats shall be different. Threats have different audio Advisories if implemented or tones are different
alert tones for potential future additional
sub-systems?
GVA_HMI_337 Key The alert tones shall be adjustable to be audible To maintain alert tone So alert tones can be heard Test Test to ensure that the alert tone
above all expected background noise conditions. volumes to 15dB above the volumes are adjustable to be
expected background noise audible over all expected
levels, at the [operators] ear. background noised levels
GVA_HMI_387 Key There shall separate volume controls for headsets Inspection Inspect to ensure there are
and any speakers. separate volume controls
GVA_HMI_339 Key GVA audio alerts shall use multi-frequency audio Multi-frequency audio tones Test Test to ensure that the alert tones
tones. used use multi frequency audio tones
GVA_HMI_338 1 There shall be provision within the [GVA HMI] of at At least two audio alert Review Review design documentation to
least two additional alert tones (not including voice tones, apart from those used ensure that there is provision for at
alerts). for warnings, cautions and least two extra alert tones
threats, are provided
GVA_HMI_341 1 Alert tones for Warnings and Cautions shall be of a Audio tones for Warnings Test Test to ensure alarm tones are from
similar tonal family with modulation and frequency and Cautions of correct the same tonal family, with
spectrum adjusted to create greater or lesser tones modulation to represent the
perceived urgency appropriate to the alert category. importance
GVA_HMI_388 1 Upon selection of F16 (Ack) the audio alerts tones Test Test to ensure the system behaves
shall stop. as required when F16 is selected
GVA_HMI_342 1 Alert tones for threat events shall be distinguishable Threat alert tones are Test Test to ensure that the audio tones
from the Warning and Caution audio alerts. distinguishable used for threats are distinguishable
from the alarms audio tones
GVA_HMI_343 1 An individual alert tone shall last between 1 and 2 Alert tones last no longer Test Test to ensure the audio alert tones
seconds. than 2 seconds are no longer than 2 seconds
GVA_HMI_344 1 An alert tone shall continue to be repeated until Alert tones repeat Test Test to ensure that an alert tone
acknowledged by the [vehicle crew]. continues to repeat until
acknowledged
GVA_HMI_389 1 The audio tone for Warnings shall play through a full Test Test to ensure that an alert tone
cycle even when acknowledged. plays through a full cycle even
when rapidly acknowledged
GVA_HMI_390 1 Alerts tones for acknowledged warnings shall be Test Test to ensure the system behaves
reinitiated after 15 minutes. correctly and acknowledged
warning alert tones are reinitiated
after 15 minutes if still valid
GVA_HMI_346 1 Alert tones for acknowledged warnings, shall be re- Audio alerts re-initiated Test Test to ensure the system behaves
initiated on [GVA] start up if the warning is still valid. correctly correctly and acknowledged
warning alert tones are reinitiated at
start up if still valid
GVA_HMI_340 2 Alert tones should be routed to all [operator] Audio signals routed for those [operators] who are Review and Review design documentation and
headsets as well as internal [vehicle platform] test to ensure alert tones are routed
75
Verification
Method
speaker/s. correctly not wearing a headset. Test to the necessary equipment
If some alerts are only routed

to the [vehicle platform]
speaker then there may be
instances where users fail to
hear an alert while wearing
the headset (i.e. the speaker
volume is turned down, there
is radio chatter both internal
and external, or the headset
ANR function masks the
speaker output)

6.6 Audio Speaker System
GVA_HMI_348 Key The GVA [HMI] shall have a function to disable all No audio output from Review and Review design documentation and
audio output from speakers. speakers Inspection inspect to ensure that there is a
function to mute all audio output
from the speakers
GVA_HMI_349 Key When the [GVA HMI] speakers are disabled there Audio output disabled Inspection Inspect to ensure that a indication is
shall be a clear indication on each speaker that indication exists provide when audio output has
there is no audio output. been muted
76
©Crown Copyright 2013
Copying Only as Agreed with DStan
Defence Standards are published by and obtainable from:
Defence Equipment and Support
UK Defence Standardization
Kentigern House
65 Brown Street
GLASGOW
G2 8EX
DStan Helpdesk
Tel: 44 (0) 141 224 2531/2
Fax: 44 (0) 141 224 2503
Internet e-mail: enquiries@dstan.mod.uk
File Reference
The DStan file reference relating to work on this standard is 36/9/2
Contract Requirements
When Defence Standards are incorporated into contracts users are responsible for their
correct application and for complying with contractual and statutory requirements.
Compliance with a Defence Standard does not in itself confer immunity from legal
obligations.
Revision of Defence Standards
Defence Standards are revised as necessary by an up issue or amendment. It is important
that users of Defence Standards should ascertain that they are in possession of the latest
issue or amendment. Information on all Defence Standards can be found on the DStan
Website www.dstan.mod.uk, updated weekly and supplemented regularly by Standards in
Defence News (SID News). Any person who, when making use of a Defence Standard
encounters an inaccuracy or ambiguity is requested to notify UK Defence Standardization
(DStan) without delay in order that the matter may be investigated and appropriate action
taken. Sponsors and authors shall refer to Def Stan 00-00 before proceeding with any
standards work.

Def Stan 23-09 Part 2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Def Stan 23-09 Part 2

Uploaded by

Copyright:

Available Formats

Defence Standard 23-09

8.2 GVA Functional Areas.......................................................................................................... 26

2.3 Vehicle Crew Roles ......................................................................................................................... 51

6.2.1 Alarm Menu Information ............................................................................................................... 71

Iss No. Date Text Affected Signature and Date

A DOORS requirements set has been

There has been significant rewording to

The intent is that the requirements are now

GVA_HMI_22 - Display screen Blackout

GVA_HMI_58-65 – Update to hand controller

GVA_HMI_182 – Text colour change to white

GVA_HMI_96 –Def Stan 23-09 Part 2 now only

Requirements for linking of crew roles to

Requirements for symbology sets removed

Development of Def Stan 23-09

c) Def Stan 23-09 shall be reviewed, revised and re-released as necessary.

Arrangement of Def-Stan 23-09

Part 0 – GVA Approach

Part 1 – GVA Infrastructure

Part 2 – GVA Human Machine Interfaces (HMI)

Part 3 – GVA Health Usage Monitoring System (HUMS)

Part 4 – GVA Physical Interfaces (TBC)

MOD Point of Contact:

APP6A Military Symbols for Land Based Systems

BS5499 (Parts 1-6) Safety Signs, Including Fire Safety Signs

4 Abbreviation and Definitions

4.2.1.27 Sub-Systems: Separable elements or collections of equipment or software added to a base

5 GVA Human Machine Interface

Unique Identifier Priority Requirement Text

GVA_HMI_2 K The following items shall be included as part of the [GVA

5.3 GVA Display Screen

Unique Identifier Priority Requirement Text

GVA Display Screen Characteristics

GVA_HMI_6 1 GVA display screens shall be capable of displaying at

5.4 Operation with Night Vision Aids

Unique Identifier Priority Requirement Text

Operation using Night Vision Aids

GVA_HMI_15 K The [GVA HMI] luminance shall be compatible with the

5.5 Display Blackout

Unique Identifier Priority Requirement Text

GVA_HMI_20 1 A hardware control shall be used to reduce the luminance

5.6 Environmental Factors

Unique Identifier Priority Requirement Text

Viewing Distance and Direction

GVA_HMI_29 1 The information on the [GVA display] shall be legible from

viewing direction, measured in any plane.

5.7 Control and Input Devices

Unique Identifier Priority Requirement Text

5.7.4 Examples of onscreen keyboards are shown in Figure 1 and Figure 2.

Figure 1 Example of a QWERTY On-Screen Keyboard

Figure 2 Example of a 'phone style' On-Board Keyboard

Unique Identifier Priority Requirement Text

Hand Controller General Set Up

GVA_HMI_58 K Weapon and sighting systems shall be controlled by a

GVA_HMI_67 K The manual demanded movement of a trainable weapon

Unique Identifier Priority Requirement Text

Hard Control Panel General Principles

GVA_HMI_365 K Dedicated controls and indicators for operational or safety

Unique Identifier Priority Requirement Text

Hard Control Panel Layout

GVA_HMI_81 2 Controls mounted on a [Hard Control Panel] which are

GVA_HMI_86 K Where labelling is provided on the [Hard Control Panel]

GVA_HMI_84 1 Labelling of individual controls and groups of controls on

GVA_HMI_91 K Where unintentional operation of a control is unwanted or