GEA-NZ v3.1 Infrastructure Reference Model and Taxonomy

Government
Enterprise
Architecture
GEA-NZ v3.1
Infrastructure
Reference Model and Taxonomy
Approved June 2015

GEA-NZ v3.1 Infrastructure Reference Model and Taxonomy Page 2 of 40
Crown copyright ©. This copyright work is licensed under the Creative Commons Attribution 3.0 New Zealand licence. In essence, you are free to
copy, distribute and adapt the work, as long as you attribute the work to the Department of Internal Affairs and abide by the other licence terms.
To view a copy of this licence, visit http://creativecommons.org/licenses/by/3.0/nz/. Please note that neither the Department of Internal Affairs
emblem nor the New Zealand Government logo may be used in any way which infringes any provision of the Flags, Emblems, and Names Protection Act 1981 or would
infringe such provision if the relevant use occurred within New Zealand. Attribution to the Department of Internal Affairs should be in written form and not by
reproduction of the Department of Internal Affairs emblem or New Zealand Government logo.
Published by the Department of Internal Affairs www.ict.govt.nz

Document
Purpose
The Government Enterprise Architecture for New Zealand (GEA-NZ) Reference Models outline the following
artefacts for each dimension of the architecture:
- Reference taxonomy
- Structure and description
- Context within the GEA-NZ v3.1
- Description of artefacts and relationships with other artefacts across all dimensions
The objective of a Reference Model is to provide widely accepted core taxonomy, and an appropriate visual
representation of that taxonomy. A Reference Taxonomy defines the terminology, and provides a useful,
coherent, consistent, and structured description of the components of an Enterprise Architecture. The need
for reference architectures and associated taxonomies as part of a Government Enterprise Architecture is
described in the GEA-NZ v3.1 Context Document.
There are eight architecturally significant dimensions within the Government Enterprise Architecture for
New Zealand v3.1 framework (GEA-NZ v3.1). Each of these dimensions has a Reference Model which
includes relevant reference artefacts and relationships. Where appropriate the Reference Model has an
associated Reference Taxonomy.
GEA-NZ v3.1 uses reference taxonomies to provide categorisation terms to describe the architecture of
capabilities for use across All of Government (AoG), sectors, clusters, and agencies. Reference taxonomies
reduce complexity by abstracting, organising and simplifying complex information sets.
The overall consistency and cohesiveness of cross government services, shared services and common
capabilities, can be improved when government entities apply common reference taxonomies to deliver
consistent and aligned views of commonly required operational and technological services.
The usage of the GEA-NZ reference taxonomy, at government, agency and sector level, will help drive ICT
efficiencies and Transformation programmes through identification of opportunities for development or and
reuse of common solutions. This will enable the implementation of the Government ICT Strategy and Action
Plan to 2017 and Better Public Services: Results for New Zealanders.
Use of the GEA-NZ v3.1 reference model will:
- Provide common language to promote service, information, system and technology interoperability
- Promote the identification and demand aggregation of sharable and common capabilities to improve
the efficacy, utility and cost effectiveness of ICT across government
- Foster traceability of features to meet requirements
- Support the re-use of solutions and services
- Support the development and delivery of coherent AoG Common Capabilities portfolio
- Support the AoG Data Governance initiatives

Scope
This document provides a description of the GEA-NZ v3.1 Infrastructure Reference Model and Taxonomy. It
provides the basis for developing specific infrastructure reference architectures and patterns. These
reference architectures and reference patterns can be more readily used across government where the
terms from the reference taxonomy are used consistently.
This document does not include the description of the business reference architecture or the use of software
tools to construct and manage GEA-NZ v3.1 models.
References to related documents are contained within the context of the document.
Audience
The intended audience of this document is (but not limited to):
- Agencies’ Enterprise, Infrastructure and Solution Architects
- Business partners involved in development and delivery of business and technology solutions
- ICT and Architect Managers
- Infrastructure and Implementation Specialists
- ICT Security Specialists for Certification & Accreditation activities (C&A)
Authors
Regine Deleu – All-of-Government Enterprise Architect
Jim Clendon – Senior Enterprise Architecture Modeller
Approval
This document has been created following engagement with the Chief Architect Forum (CAF) and the
Government Enterprise Architecture Group (GEAG). The content will be subject to yearly review and
improvement. The Government Enterprise Architect team will manage revisions and will indicate priorities
for this work. Approval for changes will be sought through the GEAG.
Acknowledgements
This version of the GEA-NZ Infrastructure Reference Model and Taxonomy was developed by the
Government Enterprise Architecture team, part of System Transformation Team, Department of Internal
Affairs, New Zealand. It was peer-reviewed and approved by GEAG members.
Additionally, feedback received from a number of experts from various agencies was greatly appreciated.

Version Control
Version Date Comment Modified by Approved
by
Next Review
Date
v3.0 November 2014 Initial version Regine Deleu GEAG End 2015
V3.1 June 2015 Major Changes
1
:
Regine Deleu
Jim Clendon
GEAG June 2016
- I1 Platform
- I1.04 Facility Infrastructure from I1 Platform to I3 Facility – I3.02 Facility Infrastructure.
- I1.01.02.03 Removable Storage Media description change
- I3 Facility
- I3.01.07 Temporary Facility corrected to I3.01.08 Temporary Facility
- I3.01.08 Field Facility corrected to I3.01.07 Field Facility
- I3.02 Geographic Location removed – now part of Data and Information Taxonomy
- I3.02 Facility Infrastructure moved from I1.04 Facility Infrastructure
- The following categories were moved to the GEA-NZ Data and Information Reference Model and
Taxonomy:
o I3.03 Operational Control removed - now part of Data and Information Taxonomy
o I3.04 Acquisition Method removed - now part of Data and Information Taxonomy
o I3.05 Physical Security and related categories renumbered under I3.03 Physical Security
- Changed number of Facility Physical Security from I3.05 to I3.03.
- I4 Desktop Equipment
- I4.01.02 Personal Computer (PC) added Thick Client Device and made Thin Client Device and Zero Client
Device categories under this Personal Computer (PC).
- I4.01.06 Telephone Handset removed.
- I4.02 Mobility Equipment added; Mobile Modem, Mobile Wi-Fi, and Phablet
- I4.02.13 Wireless Headset number corrected to I4.02.14
- I4.03.01 Display added; Monitor, Touchscreen, TV, Smart TV, Projector
- I4.03 User Peripheral added; Fax Machine, Multimedia Device, Radio Receiver, and Memory Media
- Removed the Appendix – GEA-NZ v3.0 Infrastructure Reference Taxonomy in Context with Other Artefacts. The
relationships between the GEA-NZ Reference Models and the other artefacts have been implemented into a
GEA-NZ Reference Models / Artefacts matrix.
1
A detailed ‘What’s Changed - GEA-NZ v3.0 vs v3.1” overview can be requested.

Table of Contents
Document.....................................................................................................................................3
Purpose............................................................................................................................................ 3
Scope................................................................................................................................................ 4
Audience .......................................................................................................................................... 4
Authors ............................................................................................................................................ 4
Approval........................................................................................................................................... 4
Acknowledgements ......................................................................................................................... 4
Version Control................................................................................................................................ 5
Table of Contents............................................................................................................................. 6
Executive Summary.......................................................................................................................7
Infrastructure Reference Model and Taxonomy .............................................................................8
Introduction..................................................................................................................................... 8
Principles.......................................................................................................................................... 9
Context within GEA-NZ v3.1 .......................................................................................................... 10
Benefits.......................................................................................................................................... 10
Development ................................................................................................................................. 12
Background.......................................................................................................................... 12
Approach ............................................................................................................................. 12
Tools .................................................................................................................................... 13
Use of the taxonomy ........................................................................................................... 13
Infrastructure Reference Model ..................................................................................................14
Structure ........................................................................................................................................ 14
Domain Relationships.................................................................................................................... 15
Domains......................................................................................................................................... 16
Platform............................................................................................................................... 17
Network............................................................................................................................... 22
Facility.................................................................................................................................. 29
End User Equipment............................................................................................................ 34

Executive Summary
The Government Enterprise Architecture for New Zealand (GEA-NZ) Reference Models outline the following
artefacts for each dimension of the architecture framework:
- Reference taxonomy
- Structure and description
- Context within the GEA-NZ v3.1
- Description of artefacts and relationships with other artefacts across all dimensions
The objective of a Reference Model is to provide widely accepted core taxonomy, and an appropriate visual
representation of that taxonomy. A Reference Taxonomy defines the terminology, and provides a useful,
coherent, consistent, and structured description of the components of an Enterprise Architecture.
The GEA-NZ Infrastructure Reference Taxonomy consistently categorises and describes the government –
wide infrastructure using common infrastructure domains instead of a siloed, agency-by-agency view. It is
used for identifying opportunities for cost reduction, collaboration, shared services, common capabilities and
solution reuse in ICT portfolios within and across agencies to effectively and efficiently support citizen centric
service transformation.
The usage of the GEA-NZ reference taxonomy, at government, agency and sector level, will help drive ICT
efficiencies through identification of opportunities for development or and reuse of common solutions. This
will ultimately support the implementation of the Government ICT Strategy and Action Plan to 2017 and
Better Public Services: Results for New Zealanders.
Use of the GEA-NZ v3.1 reference model will:
- Provide common language to promote service, information, system and technology interoperability
- Promote the identification and demand aggregation of sharable and common capabilities to improve
the efficacy, utility and cost effectiveness of ICT across government
- Foster traceability of features to meet requirements
- Support the re-use of solutions and services
- Support the development and delivery of coherent AoG Common Capabilities portfolio
- Support the AoG Data Governance initiatives

Infrastructure Reference Model and
Taxonomy
Introduction
The GEA-NZ Infrastructure Reference Taxonomy provides the basis for categorising infrastructure assets at a
department or agency level, as well as at Sector and All-of-Government (AoG) level. It is used for identifying
opportunities for cost reduction, collaboration, shared services, common capabilities and solution reuse in
ICT portfolios within and across agencies to effectively and efficiently support citizen centric service
transformation. It includes insourced, outsourced or cloud capabilities.
At an All-of-Government level, the GEA-NZ Infrastructure reference model guides the development of
maintenance of common capabilities and the sharing and reuse of infrastructure to reduce costs, increase
interoperability across agencies, support efficient acquisition and deployment, and enable greater access to
information across organisations.
At an agency level, the GEA-NZ Infrastructure reference model describes the infrastructure assets of the
agency, and helps ICT asset management. It also helps agencies plan their migrations away from internally
owned and managed infrastructure to cloud and common capability of offerings as required in the ICT
Strategy and Action Plan.
For the purpose of the GEA-NZ Infrastructure reference model, Infrastructure is defined as: The generic
(underlying) platform[s] consisting of hardware, software and delivery platform upon which
specific/customised capabilities (solutions, applications and ICT services) may be deployed. The term
platform used in this context covers physical as well as technology infrastructure components.

The GEA-NZ Infrastructure Reference Taxonomy is an integral part of the Government Enterprise
Architecture for New Zealand v3.1 framework (GEA-NZ v3.1).
Principles
The value of reference models comes from applying them as part of business as usual practices and
capability acquisition across agencies in a consistent manner. They are used to provide a consistent view
across a complex system of business services and supporting ICT so that the delivery of government services
can become customer centric, and that investments can be made that benefits the system as a whole, not
just specific agencies in accordance with the guiding principles of the Government ICT Strategy and Action
Plan to 2017:
- Centrally led, collaboratively delivered
The Strategy and Action Plan will be led by the GCIO and delivered in collaboration with agency
chief executives.
- Customer centricity
Customer insights must inform service design and delivery. Customers should be shielded from
the internal complexities of Government.
- Trust and Confidence
Build public trust and confidence in government’s ability to maintain the privacy and security of
information. This underpins our ability to use digital channels.
- Simplify by design
Remove complexity, fragmentation and duplication, and reengineer business processes end–to-
end.
- Share by default
Capabilities must be shared by default rather than by exception.

Context within GEA-NZ v3.1
The GEA-NZ Infrastructure Reference Taxonomy is a core part of the GEA-NZ Infrastructure Reference Model
within the GEA-NZ v3.1 framework. The GEA-NZ Infrastructure Reference Model provides the basis for
categorising infrastructure assets at a department or agency level as well as Sector and AoG levels.
The following table shows the GEA-NZ Infrastructure Reference Model in context with the other GEA-NZ
reference models.
Infrastructure
helps policy compliance through the adoption of common
capabilities
Strategy, Investment, and Policy
provides the infrastructure that enables performance
measurement and governance controls, and offers
opportunities to improve business efficiency through
sharing and reuse
Governance and Performance
provides the infrastructure that support business
services, processes, capabilities, information sharing, and
reuse
Business
provides the infrastructure to support storage and
exchange of data
Data and Information
provides the internal or external infrastructure for
hosting applications and ICT services
Application and ICT Services
provides the infrastructure controls needed to support
security and privacy requirements
Security and Privacy
sets the infrastructure requirements that drive
development and scope of corresponding standards
Standards
In the Appendix you can find tables showing the GEA-NZ Infrastructure Reference Taxonomy in context with
other artefacts.
Benefits
The GEA-NZ Infrastructure Reference Model will provide the following benefits to agencies, sectors and their
business partners involved in the delivery of public services and joint capabilities:
- Drives standardisation at the technology layer, improving the overall manageability, ensuring
technologies are directly referenced to business outcomes, and making understanding the impact of
changes more unambiguous.
- Provides a government wide common language for infrastructure.
- Identification of opportunities for sharing, re-use and consolidation of services to improve efficiencies
and effectiveness of current capabilities. To guide change towards shared common services.
- It will enable both ‘horizontal’ assessments of where multiple products are delivering the same
business service (consolidation and sharing opportunities), and ‘vertical’ assessments of where
different technology products have been implemented for the same or similar services
(standardisation and re-use opportunities.
- Provides a basis for the objective review of ICT investment by the government.

- For agencies’ Four Year Plan to help show what they will achieve and how it will be achieved aligning
to Better Public Services and all-of-government shared services.
- Enables more cost-effective and timely delivery of ICT services through a repository of standards,
principles and templates that support repeatable and consistent design and delivery of ICT capability,
as well as business and operational support services.
- Identification of opportunities for the consolidation and standardisation of infrastructure.
- Baseline for agencies’ infrastructure catalogue;
- An engagement framework that translates a high-level logical view for capability definition and
delivery. From a practical perspective, to provide a tool kit for Enterprise Architects to use in their
daily work.
This will ultimately result in increased collaboration between agencies, reduced risks, reduced number of
incompatible systems across and within agencies, and it contributes to government-wide interoperability
commitments in an affordable manner.
In real terms, this will allow the Government to realise savings in two key areas:
Financial Management
Aligning the GEA-NZ Infrastructure Reference Model within the broader architectural framework enables
explicit links to be established from the governance and performance layer through to the data and
technology layers.
This will facilitate continuous, robust analysis of the relationship between ICT investments and the
associated impact on governance and Governance and Performance against required business outcomes.
Once established, these linkages will support evidence-based decision making around which technologies
and standards are most essential to ensure the continued provision of priority, fit-for-purpose and value for
money systems, services and applications.
User Productivity
Standardisation and rationalisation of diverse set of technical standards will improve productivity for not
only the user community and those responsible for the management and delivery of ICT services, but also
those involved with capability definition, development, acquisition, and delivery and integration
(introduction into service, and integrated logistics support management).
Improved standardisation will reduce existing barriers to workforce interoperability, service availability and
sharing, and data access and sharing capabilities, and deliver improved consistency across communication
and collaboration platforms.
ICT will realise increases in productivity driven by the reduced complexity which flows from having a
standardised, agreed set of technologies and platforms upon which existing and planned applications and
services are hosted.
Additionally, as a more standardised suite of approved technologies and platforms develops over time, the
number of applications which are supported by bespoke or specialised technologies will fall, reducing the
requirement to maintain highly specialised skills to support legacy applications.

Development
The GEA-NZ Infrastructure Reference Taxonomy has been adapted for New Zealand based on the United
States Federal Enterprise Architecture version 2 (US FEAF v2)2
Infrastructure Reference Model combined
with content developed for the NZ Defence Technology Reference Model. NZ Defence based the
development of their Technology Reference Model on the following sources:
- GEA-NZ v2.0 AoG Common Operating Environment (COE) and NZDF COE
- NATO C33 Taxonomy
- Australian Department of Defence (DoD) Integrated Defence Architecture4 (IDA)
- US Information Exchange Architecture (IEA).
- UK Government ICT Strategy, End User Device Programme – Conceptual Framework dated Apr 12.
The GEA-NZ v3+ framework separates Infrastructure from Applications and ICT Services, so only content
from the NZ Defence Technical Reference Model that relates to Infrastructure has been included.
Background
The GEA-NZ v3+ Infrastructure Reference Taxonomy replaces the GEA-NZ v2.0 Technology Reference
Taxonomy.
The GEA-NZ v2.0 Technology Reference Taxonomy was originally approved as part of the NZ FEAF in 2008
and was essentially the same as the taxonomy in the US FEAF v1.0 Technical Reference Model developed in
2006.
There has been some adoption of the NZ FEAF within agencies. However, it is now dated and does not
adequately support the Government ICT Strategy and Action Plan to 2017, or the Better Public Services
programme. As a result agencies have in turn adapted and expanded the taxonomy to the extent that it no
longer provides a common set of terms. Similarly, the GEA-NZ v2.0 COE Reference Architecture was defined
using a new set of terms, predominantly to support the development of the AoG DaaS5
and OPaaS6
common
capability, with very few terms from the older reference taxonomies being reused.
Approach
Our approach is to reuse and adapt reference taxonomies from other jurisdictions. Three major sources for
GEA-NZ v3+ are the Australian Government Architecture v3.0 (AGA v3.0), the UK Reference Architecture (UK-
RA 2012), and the US FEAF v2.0.
Representatives from the Chief Architects Forum (CAF) and the Government Enterprise Architecture Group
(GEAG), and other agencies review and contribute to the taxonomies.
2
http://www.whitehouse.gov/sites/default/files/omb/assets/egov_docs/fea_v2.pdf
3
NATO C3 = North Atlantic Treaty Organisation Command, Control and Co-ordination Agency
4
Note: The ADF IDA closely follows the US FEAF model.
5
Desktop as a Service
6
Office Productivity as a Service

Tools
The GEA-NZ v3.1 Infrastructure Reference Model has been developed using Sparx Systems Enterprise
Architect7
modelling tool. The diagrams are published using .png files, Sparx packages, and Microsoft Excel.
Use of the taxonomy
The GEA-NZ v3.1 Infrastructure Reference Taxonomy is a simple hierarchical structure made up of
infrastructure domains, which are divided into infrastructure areas, which have Infrastructure categories.
Infrastructure categories may have multiple levels where more detail is required.
As well as providing a standard categorisation vocabulary for infrastructure assets the GEA-NZ Infrastructure
Reference Taxonomy can also be used to define high level patterns and reference architecture.
7
Sparx Systems Enterprise Architect, Ultimate Edition, has been selected by Government Enterprise Architecture in
August 2014 as the go forward tool for developing and maintaining GEA-NZ.

Infrastructure Reference Model
Structure
The GEA-NZ Infrastructure Reference Taxonomy model is a simple hierarchical structure made up of
infrastructure domains, which are divided into infrastructure areas, which have Infrastructure categories.
Infrastructure categories may have multiple levels where more detail is required.
The diagram below shows the structure of the taxonomy and an approach for implementation using the
Open Group ArchiMate
8
elements and relationships. Note that the infrastructure reference taxonomy
includes domains for End User Equipment (ArchiMate Device), Network (ArchiMate Network) and within the
facility domain, an infrastructure area for Location (ArchiMate Location).
8
ArchiMate is an emerging standard for enterprise architecture modelling in the GEA-NZ Standards.
GEA-NZ v3.1 Infrastructure Reference Taxonomy Structure
Agency Implementation (Using ArchiMate 2.1 soecification elements)
Categorisation
I1.01.01-I4.99.99
I1.01-I4.99
I1-I4
Note: The GEA-NZ Infrastructure Reference
Taxonomy covers physical infrastructure and
operating system. To categorise other system
software use the GEA-NZ Application and ICT
Services Taxonomy; Core ICT Operating
Services.
Infrastructure Area
AchiMate Device AchiMate Network
Infrastructure Category
ArchiMate Infrastructure
Function
Infrastructure Domain
Infrastructure
Reference
Taxonomy
ArchiMate Node AchiMate
Communication Path
AchiMate System Software
«generalisation»
«generalisation»
«generalisation»
1
1
1
1
«aggregation»
«generalisation»
«realisation»
«assignment»
«realisation»
«assignment»
«realisation»
GEA-NZ v3.1 Infrastructure Reference Taxonomy Structure
I1.01.01-I4.99.99
«assignment»
«realisation»
«assignment»
«realisation»
«realisation»
ArchiMate Node
AchiMate System Software
AchiMate
Communication Path
Note: The GEA-NZ Infrastructure Reference
Taxonomy covers physical infrastructure and
operating system. To categorise other system
software use the GEA-NZ Application and ICT
Services Taxonomy; Core ICT Operating
Services.
Agency Implementation (Using ArchiMate 2.1 soecification elements)
Categorisation
ArchiMate Infrastructure
Function
Infrastructure Area
Infrastructure Domain
Infrastructure
Reference
Taxonomy
Infrastructure Category
1
1
1
1
«generalisation»
«generalisation»
AchiMate Network
«generalisation»
I1-I4
I1.01-I4.99
«aggregation»
AchiMate Device
«generalisation»

Domain Relationships
The following diagram shows the relationship between the four Infrastructure Reference Taxonomy
domains, and the related infrastructure areas.
The GEA-NZ v3.1 Infrastructure Reference Model has a domain focused on the End User Equipment. It is a
significant change from the previous Technology Reference Model which has only infrastructure.
The Facility domain has been added and includes new concepts not covered in the previous Technology
Reference Taxonomy. These are the acquisition method, facility type, geographic location, operation
control, and facility physical security.
Network Infrastructure
Network Type
Platform Operating System
TransmissionType
Traffic Type
Facility Type
Hardware
Facility
Platform
Virtualization
Network
Embedded Technology Device
Mobility Equipment
User Peripheral
Desktop Equipment
Equipment Operating System
End User Equipm ent
Facility Infrastructure
Network Protocol Layering
Facility Physical Security
1
communicates across carries traffic generated by and for
1
existsandoperateswithinprovidesphysicalenvironmentfor
1
1
1
1
1
providesconnectionbetweeninstancesofislinkedby
1
may exists and operates withinmay provide physical environment for
1
communicatesacrosscarriestrafficgeneratedbyandfor
1
1
1
may exists and operates withinmay provide physical environment for
communicatesacrosscarriestrafficgeneratedbyandfor
providesconnectionbetweeninstancesofislinkedby
1
1
1
1
1
1
1
1
1
communicates across carries traffic generated by and for
existsandoperateswithinprovidesphysicalenvironmentfor
1
Platform Network
Facility
Hardware
Platform Operating System
Virtualization
End User Equipm ent
Embedded Technology Device
Facility Infrastructure
Network Protocol Layering
Traffic Type
Network Infrastructure
Network Type
TransmissionType
Mobility Equipment
Desktop Equipment
Equipment Operating System
Facility Type
User PeripheralFacility Physical Security

Domains
The GEA-NZ Infrastructure Reference Taxonomy includes four domains that can be used as a common
language to classify infrastructure. These are the:
- Platform - Include a computer's architecture, operating system, as well as software platforms that
emulate entire hardware platforms (e.g., system virtualisation).
- Network - Describes the areas needed to allow efficient communication between devices via email,
instant messaging, chat rooms, telephone, video telephone calls, and video conferencing.
- Facility - Addresses how and/or where a particular asset acquired, deployed, and operated.
- End User Equipment - The physical interfaces between end users and suites of user applications.
The domains and their related infrastructure areas are shown in the following diagram:

Platform
Note: Detailed diagrams are available as .png files, and this table is available as an Excel file.
Name Description
I1 Platform The Platform Domain includes hardware architecture and a software framework,
where the combination allows software, particularly application software, to
run. For the purposes of the IRT, platforms include a computer's architecture,
operating system, as well as software platforms that emulate entire hardware
platforms (e.g., system virtualisation).
I1.01 Hardware Hardware, in a computer context, refers to the physical components that make
up a computer system, including the basic machine itself. There are many
different kinds of machines and different kinds of hardware that can be installed
inside, and connected to the outside, of a computer.
I1.01.01 Server A Server is a computer that provides data to other computers. It may serve data
to systems on a Local Area Network (LAN) or a Wide Area Network (WAN) over
the Internet.
I1.01.01.01 Blade Server A Blade server is a small form factor module that needs to be housed in a blade
enclosure. Blade servers support high-end computing in high-density
environments. The Blade Enclosure (or chassis) performs many of the non-core
computing services found in most computers. The blade enclosure houses
multiple server blade modules with room for storage, and many shared
components such as power, cooling, networking and other interconnects, all
controlled by an integrated management system. Blade server systems are also
known as 'modular servers', even though widely mounted in racks.
I1.01.01.02 Mainframe Server A Mainframe is a high-performance computer environment used for large-scale
computing purposes that require greater availability, processing capacity and
security than other server types. Usually differentiated by executing multiple
programs concurrently, though not necessarily in real-time. It often serves many
connected dumb terminals (rather than client computers) and is usually used by
large complex organisation. Typically housed in multiple racks in large computer
rooms, but are also common in a distributed virtualised architecture, using a
number of subscriber/donor servers and clients to conduct remote processing of
data chunks concurrently.
I1.01.01.03 Mobile Server A Mobile server is uniquely designed for on-the-road development, ad hoc
deployment, and smaller environments. It allows for quick deployment and can
be easily transported (hand carried) into emergency, disaster, or temporary
environments. Mobile servers typically are more compact, lighter and reduced
power consumption than other server types. Known as "server on the go"
technology, uses include network performance engineers, software or database
developers, training centers, military personnel, law enforcement, forensics,
emergency relief and service organisations, and home-users (Cube media
servers). To facilitate portability, features such as the keyboard, display, backup
power battery (UPS) and mouse are integrated into the chassis.

I1.01.01.04 Modular Server A modular server approach differs from a blade server system (enclosure) in that
it employs direct access to a shared storage array, in many cases with modular
storage, usually via SAS HBA. Modular servers are designed for cost-effective use
for small and medium sized businesses.
I1.01.01.05 Rack Server A Rack server is a self-contained device, specially designed for ultra-compact
vertical arrangement within a standardised 19-inch mounting rack or cabinet,
though fitted with its own power supply can be utilised independent of a rack.
Rack servers typically have expansion (mezzanine) slots, for adding network
interface cards (NICs) or Fibre Channel host bus adapter (HBA) cards as required.
This configuration uses floor space efficiently, and offers centralised cable and
server management. In addition, rack server configuration increases
infrastructure scalability by letting you add servers as needed, and connect to
external storage, such as network attached storage (NAS) or storage area
network (SAN). Rack servers are limited in the number of new drives and
memory you can install per unit. Rack servers are generally designed to work as
a logical and cohesive whole but without the tight integration found with server
blades. Rack servers from different manufacturers can operate in the same
rack/cabinet because the servers do not share proprietary components.
I1.01.01.06 Super Computing Server A Super Computing server is a high-performance computing machine designed
to have extremely fast processing speeds. Supercomputers have various
applications, such as performing complex scientific calculations, modelling
simulations, and rendering large amounts of 3D graphics. Usually differentiated
by executing a few programs as fast as possible, and applications requiring near
real-time processing. Supercomputers can be housed in multiple racks in large
computer rooms.
I1.01.01.07 Tower Server These are upright, self-contained free-standing units that contain all traditional
server components: hard disks, motherboards and central processing units
(CPUs), networking, cabling, power and so on. Tower servers generally require
more floor space than bladed environments or rack-mounted servers, and offer
less scalability by design. Tower servers rely on externally provided keyboard,
display, mouse and other peripherals.
I1.01.02 Storage Technology consisting of computer components and recording media used to
retain digital data.
I1.01.02.01 Direct Access Storage
(DAS)
Direct access storage device is a general term for magnetic disk storage devices
and solid state storage devices. Within the IRT, the term refers to magnetic
storage devices for mainframes, midranges, and PCs. "Direct access" means that
all data can be accessed directly in about the same amount of time, rather than
having to progress sequentially through the data.
This is also known as Direct-attached storage (DAS) which refers to a digital
storage system directly attached to a server or workstation, without a storage
network in between. It is a retronym, mainly used to differentiate non-
networked storage from the concepts of storage area network (SAN) and
network-attached storage (NAS).
I1.01.02.02 Network Attached
Storage (NAS)
Network-attached storage (NAS) is file-level computer data storage connected to
a computer network that can provide data access to a heterogeneous group of
clients. NAS not only operates as a file server, but is specialised for this task
either by its hardware, software, or configuration of those elements.
I1.01.02.03 Removable Storage
Media
Removable storage media is any type of storage device that can be removed
from a computer while the system is running.

I1.01.02.04 Storage Area Network
(SAN)
A storage area network (SAN) is a dedicated network that provides access to
consolidated, block level data storage. SANs are primarily used to make storage
devices, such as disk arrays, tape libraries, and optical jukeboxes, accessible to
servers so that the devices appear like locally attached devices to the operating
system.
I1.01.03 Specialised Hardware Specialised hardware covers industrial scale peripherals that connect to
networks such as; 3D manufacturing printers, industrial tooling and machinery,
large scale commercial printers, MRI scanners, Radio Telescopes etc.
I1.01.03.01 Industrial Hardware Hardware machines and tools used specifically in an industrial process or output
context. Examples: include agriculture, assembly line, industrial robot, oil
refinery, packaging and labelling, paper mill, sawmill, smelter, power stations
(turbines), specialised printing hardware covering a broad range of classes of
[digital] printing, such as for graphic arts, mass media production, marketing,
labelling & posters, large-scale 3D artefacts.
I1.01.03.02 Medical Hardware Medical hardware. For example an Magnetic Resonance Imaging (MRI) scanner;
these conduct diagnostic medical radiological testing using magnetic fields and
radio waves to produce a detailed image of the body’s soft tissue, muscles,
tendons and bones.
I1.01.03.03 Research and Scientific
Hardware
Research and Scientific Hardware. An example is a radio telescope; an
instrument consisting of a directional antenna, or system of antennas,
connected to one or more radio receivers, used in radio astronomy to detect and
analyse natural radio waves from space. Also used to receive data from man-
made satellites and space probes.
I1.01.04 Hardware Security
Equipment
Provides features necessary for the improvement of information system
equipment security.
I1.01.04.01 Cryptographic Equipment Secure telecommunications or information handling equipment,
associated cryptographic component or other hardware item which performs a
critical communications security (COMSEC) function.
I1.01.04.02 Firewall This is hardware based firewall equipment. A firewall can be software or
hardware based network security system that controls the incoming and
outgoing network traffic by analysing the data packets and determining whether
they should be allowed through or not, based on an applied rule set. A firewall
establishes a barrier between a trusted, secure internal network and another
network (e.g., the internet) that is not assumed to be secure or trusted.
I1.01.04.03 Hardware Security
Module
Provides a hardened, tamper resistant environment for performing secure
cryptographic processing, key protection and key management.
I1.01.04.04 Hardware Security Token Physical device used to enable physical access to buildings, controlled spaces
and/or to support logical access control in a cyber-environment. Includes
smartcards, USB tokens, Passport RFID, and similar devices.
I1.01.04.05 Trusted Platform Module Standard based microprocessor that is built into computing devices to enable
the secure generation of crypto keys and to limit the use of them (to
signing/verification or encryption/decryption). Typically associated with Type 1
crypto equipment.

I1.02 Platform Operating
System
An Operating System (OS) is a computer program, implemented in either
software or firmware, which acts as an intermediary between users of a
computer and the computer hardware. The purpose of an operating system is to
provide an environment in which a user can execute applications.
I1.02.01 Embedded OS An embedded OS is intended for controlling embedded computer systems.
These OS are designed to be compact, efficient and reliable, forsaking many
functions that other OS provide, and which may not be used by the specialist
applications they run. Application and Embedded OS typically are statically
linked together into a single executable image. Embedded OS are frequently also
real-time OS, with the term RTOS being synonymous with Embedded OS on
critical systems.
I1.02.02 Server OS Operating system intended for controlling server devices rather than client side
devices.
I1.03 Virtualisation In computing, virtualisation is the creation of a virtual (rather than actual)
version of something, such as a hardware platform, Operating System (OS),
storage device, or network resources. This section of the IRT categorizes those
mechanisms to create virtual platforms.
I1.03.01 Application
Virtualisation
For the purposes of the IRT, application virtualisation encapsulates application
from the underlying operating system on which they are executed. A fully
virtualised application is not installed in the traditional sense, although it is still
executed as if it were. The application is fooled at runtime into believing that it is
directly interfacing with the original operating system and all the resources
managed by it, when in reality it is not. In this context, the term "virtualisation"
refers to the artefact being encapsulated (application), which is quite different to
its meaning in hardware virtualisation, where it refers to the artefact being
abstracted (physical hardware).
I1.03.02 End-User
Environment Virtualisation
End-User Environment virtualisation is a broad term including desktop and client
virtualisation. End-User virtualisation separates a personal computer desktop or
mobile computing environment from a physical machine using the client–server
model of computing.
I1.03.03 Hypervisor The hypervisor or virtual machine manager (VMM) is computer software,
firmware or hardware that creates and runs virtual machines. The hypervisor
presents a virtual operating platform to the guest operating system and
manages the execution of the guest operating systems on the host machine.
Multiple instances of a variety of operating systems may share the virtualised
hardware resources.
I1.03.04 Print Server
Virtualisation
Print server virtualisation extends the virtualisation concept to the access to and
management of print resources. For the purposes of the IRT, a print server can
be a dedicated device, a standalone computer, specialised software, or some
combination that handles receipt, queuing, delivery, and status of print jobs for
printers on the network.
I1.03.05 Server Virtualisation Virtual servers are virtual machines where each server, although running in
software on the same physical computer as other customers' servers, is in many
respects functionally equivalent to a separate physical computer. A virtual server
is dedicated to the individual customer's needs, has the privacy of a separate
physical computer, and is configured to run server software. The term cloud
server is also used to describe the same concept, normally where such systems
can be setup and re-configured on the fly.

I1.03.06 Storage Virtualisation Storage virtualisation applies virtualisation concepts to enable better
functionality and more advanced features within the storage system. Storage
systems use special hardware and software along with disk drives in order to
provide very fast and reliable storage for computing and data processing.

Network
Name Description
I2 Network The Network describes the areas needed to allow efficient communication
between devices via email, instant messaging, chat rooms, telephone, video
telephone calls, and video conferencing. A network allows sharing of files,
data, and other types of information giving authorised users the ability to
access information stored on other computers on the network.
I2.01 Network Infrastructure For the purposes of the GEA-NZ Infrastructure Reference Taxonomy, Network
Infrastructure is a broad term covering the various forms of basic hardware
and software that comprise the foundation of a network.
I2.01.01 Communications
Hardware
Communications Hardware refers broadly to hardware intended primarily to
create a link to the network from the user or another computational device.
I2.01.01.01 Antenna Device to convert electric current to radio waves and vice versa. There are
different types including; Omni-Directional which receive or radiate more or
less equally in all directions; Directional / Beam which are intended to
preferentially radiate or receive in a particular direction or directional
pattern.
I2.01.01.02 Radio Equipment Equipment that provides voice and data communications over wireless
medium and across the spectrum.
I2.01.01.03 Radio/Network
Management Device
Hardware platforms and software dedicated to providing functionality
required for management and programming of software defined radios
(SDR), including frequencies, encryption, addressing.
I2.01.01.04 Satellite Communication The basic elements of satellite communications are a space segment, a
control segment, and a terminal segment (air, ship, ground, etc.). An
implementation of a typical satellite link will require the use of satellite
terminals, a user communications extension, and military or commercial
satellite resources.
I2.01.01.05 Tactical Data Link System
(TDL)
TDL systems comprise radio transceivers, modems, software and
transmission protocol standards that meet specific military and emergency
response tactical messaging requirements, particularly in terms of speed of
transmission, accuracy, auditing and logging, simplified user interface and
interaction. Typically uses bespoke (or multiple versioned closed standards)
'tactical messaging access services'.
I2.01.01.06 Transponder A series of interconnected units forming a communications channel between
the receiving and transmitting antennas. Typically are part of a radio relay
station.
I2.01.01.99 Other Communications
Hardware
Other Communications Hardware not specified.

I2.01.02 Network Hardware Specifically for Networks, Hardware refers to many different kinds of devices
and their firmware. These devices provide many things including routing,
security, etc. The software included here is the firmware and/or Operating
System (OS) associated with specific network devices.
I2.01.02.01 Hub An Ethernet hub, active hub, network hub, repeater hub, multiport repeater
or hub is a device for connecting multiple Ethernet devices together and
making them act as a single network segment. It has multiple input/output
(I/O) ports, in which a signal introduced at the input of any port appears at
the output of every port except the original incoming. A hub works at the
physical layer (layer 1) of the OSI model. Repeater hubs also participate in
collision detection, forwarding a jam signal to all ports if it detects a collision.
Note: Hubs are now largely obsolete, having been replaced by network
switches except in very old installations or specialised applications.
I2.01.02.02 Load Balancer In computing, load balancing distributes workloads across multiple
computing resources, such as computers, a computer cluster, network links,
central processing units or disk drives. Load balancing aims to optimize
resource use, maximize throughput, minimize response time, and avoid
overload of any single resource. Using multiple components with load
balancing instead of a single component may increase reliability through
redundancy. Load balancing usually involves dedicated software or hardware,
such as a multilayer switch or a Domain Name System server process.
I2.01.02.03 Router A router is a networking device, commonly specialised hardware, which
forwards data packets between computer networks.
Multiple routers are used in interconnected networks, the routers exchange
information about destination addresses using a dynamic routing protocol.
Enterprise routers, connect large business or ISP networks up to the powerful
core routers that forward data at high speed along the optical fibre lines of
the Internet backbone. Though routers are typically dedicated hardware
devices, use of software-based routers has grown increasingly common.
I2.01.02.04 Switch A switch is a device used on a computer network to physically connect
devices together. Multiple cables can be connected to a switch to enable
networked devices to communicate with each other. Switches manage the
flow of data across a network by only transmitting a received message to the
device for which the message was intended. Each networked device
connected to a switch can be identified using a MAC address, allowing the
switch to regulate the flow of traffic. This maximises security and efficiency of
the network.
Switches may operate at one or more layers of the OSI model, including the
data link and network layers. A device that operates simultaneously at more
than one of these layers is known as a multilayer switch.
Switches exist for various types of networks including Fibre Channel,
Asynchronous Transfer Mode, InfiniBand, Ethernet and others.
I2.01.02.99 Other Network Hardware Other Network Hardware not specified.
I2.01.03 Network Interface For the purposes of the IRT, a Network Interface is a broad term that includes
devices that serve as a demarcation point between networks, such as the
carrier's local loop and the customer's on-premises wiring, where the data
wires end and a customer's premise wiring starts, and network interface
controllers (also known as a network interface card, network adapter, LAN
adapter and by similar terms) which may be internal or external to a piece of
computer hardware.

I2.01.04 Network
Virtualisation
A virtual network is a computer network that consists, at least in part, of
virtual network links. A virtual network link is a link that does not consist of a
physical (wired or wireless) connection between two computing devices but
is implemented using methods of network virtualisation. The two most
common forms of network virtualisation are protocol-based virtual networks
(such as Virtual Local Area Networks (VLAN), Virtual Private Networks (VPN),
and Virtual Private LAN Services (VPLS)) and virtual networks that are based
on virtual devices (such as the networks connecting virtual machines inside a
hypervisor).
I2.01.05 Transmission Medium Transmission Medium is a material substance (solid, liquid, gas, or plasma)
that can propagate energy waves. For the purposes of the infrastructure
reference taxonomy transmission medium is the material and/or technology
that carries signal from one location to another.
I2.01.05.01 Air - Radio Waves Air is the media through which radio waves are carried. Radio wave
frequencies are easy to generate, can travel long distances, and can
penetrate buildings easily, so they are widely used for communication, both
indoors and outdoors. Radio waves also are omnidirectional, meaning that
they travel in all directions from the source, so the transmitter and receiver
do not have to be carefully aligned physically.
I2.01.05.02 Air - Microwave Air is the media through which microwaves are carried. Microwaves are
highly directional and the sending and receiving antennas must be aligned
with a clear line of sight from transmitter to receiver.
I2.01.05.03 Air - Infrared Air is the media through which infrared signals are carried. Infrared signals do
not pass through solid objects, therefore they have to operate with a clear
line of sight from transmitter to receiver.
I2.01.05.04 Optical Fibre Cable Cable containing one or more optic fibres, and light frequency signals are
transmitted.
I2.01.05.05 Twisted Pair Twisted pair cabling is a type of wiring in which two conductors of a single
circuit are twisted together for the purposes of cancelling out
electromagnetic interference (EMI) from external sources; for instance,
electromagnetic radiation from unshielded twisted pair (UTP) cables, and
crosstalk between neighbouring pairs.
I2.01.05.06 Unshielded Twisted Pair UTP cable is also the most common cable used in computer networking.
Modern Ethernet, the most common data networking standard, can use UTP
cables. Twisted pair cabling is often used in data networks for short and
medium length connections because of its relatively lower costs compared to
optical fibre and coaxial cable.
I2.01.05.07 Coaxial Cable Coaxial cable has an inner conductor surrounded by a tubular insulating layer,
surrounded by a tubular conducting shield. Coaxial cable is used as a
transmission line for radio frequency signals. Its applications include feed
lines connecting radio transmitters and receivers with their antennas,
computer network (Internet) connections, and distributing cable television
signals. One advantage of coaxial over other types of radio transmission line
is that in an ideal coaxial cable the electromagnetic field carrying the signal
exists only in the space between the inner and outer conductors providing
protection from electromagnetic interference.

I2.01.05.08 Power Line Power-lines within facilities and homes can be used to carry data signals. It is
based on the concept of "no new wires." in that you will always have an
electrical outlet near a computer.
I2.01.06.99 Other Transmission
Mediums
Other transmission mediums not specified.
I2.02 Network Type For the purposes of the GEA-NZ Infrastructure Reference Taxonomy, Network
Type is a conceptual dimension of the network into areas that are separated
(usually by security measures) from one another.
I2.02.01 Wide Area Network
(WAN)
A wide area network (WAN) is a network that covers a broad area (i.e., any
telecommunications network that links across metropolitan, regional,
national or international boundaries) using leased telecommunication lines.
Business and government entities utilize WANs to relay data among
employees, clients, buyers, and suppliers from various geographical locations.
In essence, this mode of telecommunication allows a business to effectively
carry out its daily function regardless of location. The Internet can be
considered a WAN as well, and is used by businesses, governments,
organisations, and individuals for almost any purpose imaginable.
I2.02.02 Local Area Network
(LAN)
A local area network (LAN) is a computer network that interconnects
computers within a limited area such as a home, school, computer
laboratory, or office building, using network media.[1] The defining
characteristics of LANs, in contrast to wide area networks (WANs), include
their smaller geographic area, and non-inclusion of leased telecommunication
lines.
I2.02.03 Metropolitan Area
Network (MAN)
A metropolitan area network (MAN) is a computer network larger than a local
area network, covering an area of a few city blocks to the area of an entire
city, possibly also including the surrounding areas.
I2.02.04 Personal Area
Network (PAN)
A personal area network (PAN) is a computer network used for data
transmission among devices such as computers, telephones and personal
digital assistants. PANs can be used for communication among the personal
devices themselves (intrapersonal communication), or for connecting to a
higher level network and the Internet (an uplink).
A wireless personal area network (WPAN) is a PAN carried over wireless
network technologies.
I2.03 Traffic Type For the purposes of the GEA-NZ Infrastructure Reference Taxonomy, Traffic
Type categorises the major types of traffic.
I2.03.01 Bulk Data Traffic Reliable bulk transfer of data that is not time critical, but may be high
volume, e.g. network backups.
I2.03.02 Interactive Traffic Traffic that needs to support interactive response time requirements such as
secure shell, and desktop virtualisation. It needs to be reliable.

I2.03.03 Messaging Traffic Messaging traffic tends to be characterised by low to medium bandwidth
requirements, can have latency / transmission delay, but needs to be reliable.
Examples of messaging types are:
- SMS is Short Message Service; a form of text messaging communication on
phones and mobile phones.
- MMS is Multimedia Message Service; it is a standard way to send messages
that include multimedia content to and from mobile phones. It extends the
core SMS (Short Message Service) capability that allowed exchange of text
messages only up to 160 characters in length.
- Email
I2.03.04 Transactional Traffic Traffic that needs to support reliable delivery of system to system interaction
including database and business to business transactions.
I2.03.05 Telemetry Traffic Telemetry is the highly automated communications process by which
measurements are made and other data collected at remote or inaccessible
points and transmitted to receiving equipment for monitoring.
I2.03.06 Video
Communications Traffic
Video Communications traffic includes support for video conferencing. This is
distinct from Video streaming traffic which can be buffered. As with Voice
traffic, Video is often a type of traffic carried on data networks using some
form of packet-switching technology. Video traffic is distinct from Data traffic
in the delivery requirements (it needs to arrive nearly synchronously and be
assembled in order without drop-outs) and bandwidth usage (which is very
high). Timely delivery of packets is more important than reliable delivery of
packets - there can be some loss of packets.
I2.03.07 Voice Traffic Voice networks are sometimes dedicated, as in the original public switched
telephone network (PSTN), but have changed to be a type of traffic carried on
data networks using some form of packet-switching technology. Voice traffic
is distinct from Data traffic in the delivery requirements (it needs to arrive
nearly synchronously and be assembled in order without drop-outs) and
bandwidth usage (which is high). Timely delivery of packets is more important
than reliable delivery of packets - there can be some loss of packets.
I2.03.08 Quality of Service
(QoS)
Quality of service (QoS) is the overall performance of a telephony or
computer network, particularly the performance seen by the users of the
network. It is included in the IRT as it is an important consideration when
designing solutions to meet the needs of various traffic types.
To quantitatively measure quality of service, several related aspects of the
network service are often considered, such as error rates, bandwidth,
throughput, transmission delay, availability, jitter, etc. In the field of
computer networking and other packet-switched telecommunication
networks, the traffic engineering term refers to resource reservation control
mechanisms rather than the achieved service quality. Quality of service is the
ability to provide different priority to different applications, users, or data
flows, or to guarantee a certain level of performance to a data flow.
Quality of service guarantees are important if the network capacity is
insufficient, especially for real-time streaming multimedia applications such
as voice over IP, online games and IP-TV, since these often require fixed bit
rate and are delay sensitive, and in networks where the capacity is a limited
resource, for example in cellular data communication.
I2.04 Transmission Type The Transmission Type category allows for identification of the low-level
infrastructure "applications" that form the core of the network, as well as the
foundational protocols.

I2.04.01 Global Positioning
System (GPS)
The Global Positioning System (GPS) is a space-based satellite navigation
system that provides location and time information in all weather, anywhere
on or near the Earth, where there is an unobstructed line of sight to four or
more GPS satellites. It is maintained by the United States government and is
freely accessible to anyone with a GPS receiver.
I2.04.02 Mobile Device
Networking
Mobile Device Networking covers the sets of standards commonly used for
mobile devices and mobile telecommunication services and networks that
comply with specifications by the International Telecommunication Union.
Such standards find applications in wireless voice telephony, mobile Internet
access, fixed wireless Internet access, video calls and mobile TV, among
others.
I2.04.03 Radio Control over IP
(RCoIP)
Radio Control over Internet Protocol (RCoIP) builds on the concepts of RoIP,
but can be used in combination with analogue radio units. In RCoIP, handsets
and other mobile units are remotely controlled using IP-delivered commands.
I2.04.04 Radio over IP (RoIP) Radio over Internet Protocol (RoIP) is similar to VoIP, but augments two-way
radio communications rather than telephone calls. From the system point of
view, it is essentially VoIP with PTT (Push To Talk). To the user it can be
implemented like any other radio network. With RoIP, at least one node of a
network is a radio (or a radio with an IP interface device) connected via IP to
other nodes in the radio network. The other nodes can be two-way radios,
but could also be dispatch consoles either traditional (hardware) or modern
(software on a PC), POTS telephones, softphone applications running on a
computer such as a Skype phone, PDA, smartphone, or some other
communications device accessible over IP. RoIP can be deployed over private
networks as well as the public Internet.
I2.04.05 Voice over IP (VoIP) Voice over IP (VoIP, or Voice over Internet Protocol) commonly refers to the
communication protocols, technologies, methodologies, and transmission
techniques involved in the delivery of voice communications and multimedia
sessions over Internet Protocol (IP) networks, such as the Internet. Other
terms commonly associated with VoIP are IP telephony, Internet telephony,
Voice over Broadband (VoBB), broadband telephony, IP communications, and
broadband phone.
Internet telephony refers to communications services — voice, fax, SMS,
and/or voice-messaging applications — that are transported via the Internet,
rather than the Public Switched Telephone Network (PSTN). The steps
involved in originating a VoIP telephone call are signalling and media channel
setup, digitisation of the analogue voice signal, encoding, packetisation, and
transmission as Internet Protocol (IP) packets over a packet-switched
network. On the receiving side, similar steps (usually in the reverse order)
such as reception of the IP packets, decoding of the packets and digital-to-
analogue conversion reproduce the original voice stream.
Even though IP Telephony and VoIP are terms that are used interchangeably,
they are actually different; IP telephony has to do with digital telephony
systems that use IP protocols for voice communication, while VoIP is actually
a subset of IP Telephony. VoIP is a technology used by IP telephony as a
means of transporting phone calls.

I2.04.06 Wi-Fi Wi-Fi is a popular technology that allows an electronic device to exchange
data wirelessly (using radio waves) over a computer network, including high-
speed Internet connections. The Wi-Fi Alliance defines Wi-Fi as any "wireless
local area network (WLAN) products that are based on the Institute of
Electrical and Electronics Engineers' (IEEE) 802.11 standards". However, since
most modern WLANs are based on these standards, the term "Wi-Fi" is used
in general English as a synonym for "WLAN".

Facility
Name Description
I3 Facility The Facility domain addresses how and/or where a particular asset acquired,
deployed, and operated.
I3.01 Facility Type Facility type categorises the different kind of facilities.
I3.01.01 Data Centre A data centre is a facility used to house computer systems and associated
components, such as telecommunications and storage systems. Depending on the
tier it generally includes redundant or backup power supplies, redundant data
communications connections, environmental controls (e.g., air conditioning, fire
suppression) and security devices. Tier 1 to 4 data center is nothing but a
standardised methodology used to define uptime of data center. This is useful for
measuring: Data center performance, Investments, and ROI.
I3.01.01.01 Tier 1 Basic Data Centre Tier 1 is the basic level, providing non-redundant capacity components and a
single, non-redundant distribution path serving the computer equipment. Tier 1
basic site infrastructure typically expects 99.671% availability (or approx. 29 hours
downtime per year).
I3.01.01.02 Tier 2 Redundant
Capacity Components Data Centre
Tier 2 data centre has redundant capacity components and a single, non-
redundant distribution path serving computer equipment. Tier 2 redundant site
infrastructure capacity components typically expect 99.741% availability (or
approx. 23 hours downtime per year).
I3.01.01.03 Tier 3 Concurrently
Maintainable Data Centre
Tier 3 data centre has redundant capacity components and multiple independent
distribution paths serving the computer equipment. Typically only one
distribution path serves the computer equipment at any time (i.e. failover
redundancy). All IT equipment is dual-powered and installed to be compatible
with the topology of the site’s architecture. Tier 3 concurrently maintainable site
infrastructure typically expects 99.982% availability (or approx. 1.5 hours
downtime per year).
I3.01.01.05 Tier 4 Fault Tolerant Data
Centre
Tier 4 data centre has multiple, independent, physically isolated systems that
each has redundant capacity components and multiple, independent, diverse,
active distribution paths simultaneously serving the computer equipment. All IT
equipment is dual-powered and installed to be compatible with the topology of
the site’s architecture. Tier 4 fault tolerant site infrastructure typically expects
99.995% availability (or approx. 0.5 hours downtime per year).
I3.01.02 Specialist Facilities Specialist Facilities covers a range of facility types that have unique
characteristics.

I3.01.02.01 Border Border facilities, typically designed to handle passengers and/or cargo in transit.
Contain specialist customs and immigration equipment including passport
scanning equipment, X-ray and Metal detection equipment etc.
I3.01.02.02 Correctional Correctional facilities such as prisons and remand centres, designed to high
physical and personal security specifications. Tend to house unique IT and
security equipment as well as other facilities types such as staff offices for the
handling of offenders.
I3.01.02.03 Educational Educational facilities can house other facility types such as data centres and
offices as well as housing specialist education related networks and educational
equipment such as public access Wi-Fi, computers, and kiosks.
For the purposes of the IRT, educational facilities include all types of Schools,
Museums, and Libraries.
I3.01.02.04 Hospital Hospital facility is a permanent building where patients are treated for illnesses
by specialised staff and equipment.
I3.01.02.05 Manufacturing and
Processing
Industrial facilities specifically producing products or conducting manufacturing
processes.
I3.01.02.06 Mining Mining facilities house specialised mining and mine safety equipment.
I3.01.02.07 Power Plant and
Substation
Power plants of all types and the related transmission networks and substations
house specific sensor and control equipment. Includes types such as; hydro-dam,
geothermal, gas, fossil fuels, wind, solar, wave.
I3.01.02.08 Scientific Scientific facilities house specialist equipment and can include other facility types
such as staff offices and data centres which may in turn house specialist IT
equipment.
Scientific facilities include research facilities, laboratories, and observatories.
I3.01.02.09 Storage Tank Facility Storage Tank Facility includes petroleum storage, chemicals, water reservoirs and
tanks, waste water storage etc. that host sensors to monitor levels, leakage, flow,
and quality.
I3.01.03 Operations Centre
Facility
An operations centre is designed to monitor IT assets deployed elsewhere on an
enterprise network. There are many different kinds of operations centres,
including "Network Operations Centre" (NOC) and "Security Operations Centre"
(SOC).
I3.01.03.01 Network Operations
Centre (NOC)
A network management centre, is one or more locations from which network
monitoring and control, or network management, is exercised over a computer,
telecommunication, or satellite network.
NOCs are implemented by business organisations, public utilities, universities,
and government agencies that oversee complex networking environments that
require high availability. NOC personnel are responsible for monitoring one or
many networks for certain conditions that may require special attention to avoid
degraded service. Organisations may operate more than one NOC, either to
manage different networks or to provide geographic redundancy in the event of
one site becoming unavailable.
NOCs analyse problems, perform troubleshooting, communicate with site
technicians and other NOCs, and track problems through resolution. When
necessary, NOCs escalate problems to the appropriate stakeholders. For severe
conditions that are impossible to anticipate, such as a power failure or a cut
optical fibre cable, NOCs have procedures in place to immediately contact
technicians to remedy the problem.

I3.01.03.02 Security Operations
Centre (SOC)
An information security operations centre. SOC is a location where enterprise
information systems (web sites, applications, databases, data centers and servers,
networks, desktops and other endpoints) are monitored, assessed, and defended.
SOC consists of the people, processes and technologies involved in providing
situational awareness through the detection, containment, and remediation of IT
threats. SOC manages incidents for the enterprise, ensuring they are properly
identified, analysed, communicated, actioned/defended, investigated and
reported. The SOC also monitors applications to identify a possible cyber-attack
or intrusion (event) and determine if it is a real, malicious threat (incident), and if
it could have a business impact. This category specifically includes the NZ
National Cyber Security Centre (NCSC) facility.
I3.01.04 Commercial Commercial facilities include retail trading from dairy to supermarkets, and malls
containing multiple retail outlets.
I3.01.05 Staff Office Facility For the purposes of the IRT, a staff office is any physical location/building
intended to be a destination for actual individuals to regularly report for work
functions, including locations primarily devoted to research, development, and/or
science.
I3.01.06 Virtual Office Facility For the purposes of the IRT, a Virtual Office is a workspace not set in a specific
geographic location, but rather connected (via the Internet) to the wider
enterprise. Virtual Offices include telework arrangements for employees (when
they are off-site), contract staff that works remotely, or some combination.
I3.01.07 Field Facility For the purposes of the IRT, the Field includes any active deployment outside of
traditional staff facilities, including anything from highway gantries to on-site
research and data-gathering.
I3.01.07.01 Highway Gantry Highway Gantry facilities can house electronic signs, camera and other
equipment used for monitoring and informing traffic. This covers fixed Speed
Camera facilities which house equipment to connect to buried sensors, or sensors
such as radar or laser, as well as camera equipment and communications
equipment to transmit the data. Related term: Road safety, Speed limits
I3.01.07.02 Underground For the purposes of the IRT Underground includes ducting in the streets, tunnels,
manholes and other ground facilities which may house IT equipment, sensors and
the like.
I3.01.07.03 Cabinet Equipment cabinets often located on the berms of streets that contain data,
communications, and control equipment. For example much of the high speed
broadband equipment is located in cabinets.
I3.01.07.04 Ground Radar Installation Navigational radar installations as used at airports, sea ports etc. house specialist
equipment to control the radar and send the information detected to ground
based facilities such as a control tower.
I3.01.07.05 Meteorological Station A weather station which measures humidity, pressure, temperatures, wind
speeds, ultraviolet radiation etc.
I3.01.07.06 Environmental
Monitoring Station
A station which measures air quality, water quality, gas emissions, ice, snow, soil
etc.
I3.01.07.07 Air Based Includes air based vehicles such as airplanes, drones, helicopters, gliders, balloons
etc.

I3.01.07.08 Land Based Includes land based vehicles such as truck cars, cranes, mobile robots, trains,
trucks, etc.
I3.01.07.09 Water Based Includes surface and sub-surface vehicles, in both sea and inland waterways roles.
I3.01.08 Temporary Facility For the purposes of the IRT, a Temporary Facility may be something like incident
command that includes smaller, often temporary locations for crisis / emergency
management. Also includes mobile capabilities. In the military context, includes
locations such as "forward operating bases" (FOBs)..
I3.01.09 Warehouse Facility For the purposes of the IRT, Warehouse covers any place in which IT assets are
stored or staged. The storage or staging may be for any purpose, including, but
not limited to delivery to an eventual service location, disposal, or further
decisions. The intent of this category is to identify IT assets not currently in active
use.
I3.01.10 Home For the purposes of the IRT, home covers residential locations.
I3.01.99 Other Facility Type For the purposes of the IRT, other facility type covers facilities not currently
categorised.
I3.02 Facility Infrastructure The physical infrastructure that may be part of a facility.
I3.02.01 Cabling Refers to the electrical cables used to communicate between hardware
equipment. Cables can be securely fastened and organised, such as by using
trunking, cable trays, cable ties or cable lacing.
I3.02.02 Power Supply Facilities power supplies are integral to maintaining the availability of the
services provided. These can involve uninterruptible power supply (UPS). It is
usually powered directly from the AC mains, while simultaneously charging a
storage battery. Should there be a dropout or failure of the mains, the battery
instantly takes over so that the load never experiences an interruption. Other
UPS schemes may use an internal combustion engine or turbine to continuously
supply power to a system in parallel with power coming from the AC and
batteries. In many configurations the power for the facility is direct current from
the batteries, with these being charges by with either mains or engine alternator
systems as required.
I3.02.03 Property
Management Control
Provides building management services, typically incorporating one or more of
the other control categories (environment, lifts, security access, fire, audio-
visual) in a single coherent system. Provides additional property management
functions pertinent to the occupancy (e.g. hardware to allow centralised
booking of shared resources, routing and setup of audio/video conferencing
sessions, etc.).
Also known as Building Automation System (BAS), defined as a computer-based
control system installed in buildings that controls and monitors the building’s
mechanical and electrical equipment.
I3.02.03.01 Environmental Control Provides control systems for heating, ventilation, air-conditioning, cooling (liquid
cooling for ICT server rooms), and lighting. Also known as HVAC systems. Where
appropriate, also covers more general electrical and plumbing system controls.

I3.02.03.02 Fire Control Fire control warning systems and equipment for reducing the heat output of a
fire, reducing the area over which the fire exists, or suppressing or extinguishing
the fire by depriving it of fuel, oxygen, or heat. In data centre type facilities
often inert gas is used for extinguishing fire without damaging equipment.
Includes systems for controlling building perimeter and internal access to aid
egress and fire fighters access, as well as lift/elevator restrictions.
I3.02.03.03 Lift Control Provides management of building lift and elevator services.
I3.02.03.04 Security Control System(s) that provide the required building security mechanisms, for physical
access and people access controls, as well as security warnings (intruder
detection, alarms) and observation monitoring. Includes CCTV, sensors, remote
locking mechanisms, external visibility reduction (electronic blinds, opaque
glass), access controls (swipe-cards, etc.), and other control mechanisms as
required for the building occupants/business.
I3.02.04 Rack Standardised frame or enclosure for mounting multiple ICT and/or Audio-Visual
equipment modules.
I3.02.05 Sound and Video
Systems
Embedded building sound and video systems that provide audio and visual
services, such as public address (tannoy, speakers), media centres (for
recreational and public areas), and video conferencing and presentation suites.
I3.03 Facility Physical Security For the purposes of the IRT facility physical security is about the level of physical
security required. The level can be determined by a number of factors including
but not limited too; the information security levels that applies to the activity or
artefacts in the facility, ensuring privacy of information in accordance with the
privacy act, through to prevention of theft of equipment and resources, and to
protect personnel and property from damage or harm.
I3.03.01 Unsecured Facility This is a facility, or area in a facility, where members of the public have access
too.
I3.03.02 Restricted Access
Facility
This is a facility, or area within a facility, where access is restricted to people who
have been identified and some form of access security measures are in place such
as access cards etc. Accompanied visitors who have signed in may be allowed
access.
I3.03.03 Secure Facility This is a facility, or an area within a facility, where access is restricted to people
who have been identified and authorised to be there. High security identification
measures such as biometric security may be in use. No unauthorised people are
allowed into such an area even as visitors.
I3.03.99 Other Facility Physical
Security
This covers more specialised physical security requirements, for example the
security arrangements required at prisons.

End User Equipment
Name Description
I4 End User Equipment End User Equipment provides the physical interfaces between end users and a
provided suite of user applications. Includes instruments and/or devices for a
particular purpose or use. Includes ICT devices with all platform and facility types.
I4.01 Desktop Equipment User equipment that is typically designed to perform a specific function operated
at a desk and powered by a dedicated power line and cannot be used away from
dedicated outlets.
I4.01.01 Desktop
Communication Device
User equipment that provides telepresence, video and voice communications
solutions.
I4.01.02 Personal Computer
(PC)
User equipment that provides general purpose operating system, which uses the
hardware resources of the local commodity computing platform, in a form
intended for regular use at a single fixed location.
I4.01.02.01 Thick Client Device A thick client device has a local operating system and usually have applications
installed locally. This can be thought of as the traditional desktop or under
desktop PC.
I4.01.02.02 Thin Client Device A Thin Device boots from a kernel that loads minimal services and allows
connection to a Presentation Virtualisation server. Processing is performed at the
server. Thin clients are fixed in one location and require permanent network
connectivity. As such, they cannot provide access to applications when offline.
I4.01.02.03 Zero Client Device A Zero Client is a device that has the OS and a Virtual Desktop Client running in
firmware. They are typically lower cost than thin clients, but are less flexible.
Some examples of 'ultra-thin' clients fall into this group. Same as thin clients,
these zero clients are fixed in one location and require permanent network
connectivity. As such, they cannot provide access to applications when offline.
I4.01.05 Console / Control
Terminal
Consoles are the text entry and display device for system administration
messages, particularly those from the BIOS or boot loader, the kernel, from the
initiating system and from the system logger. It is a physical device consisting of a
keyboard and a screen, and traditionally is a text terminal, but may also be a
graphical terminal. System consoles are generalised to computer terminals, which
are abstracted respectively by virtual consoles and terminal emulators.
I4.01.99 Other Desktop
Equipment
Other desktop equipment not specified.

I4.02 Mobility Equipment Mobility equipment ranges from hand held pocket-sized computing and/or
communication device held with one hand, through to portable equipment used
in the field or attached to vehicles. They typically have a display screen, and
various input capabilities.
I4.02.01 Laptop Computer User equipment that provides equivalent personal computing capability for
mobile use. Integrates most common components of a desktop computer into a
single unit, or will integrate with same ancillaries (e.g. keyboard, mouse, display,
printer, speakers/headphones), and is powered by mains electricity but can be
used away from an outlet through use of rechargeable battery. Laptops are not
fixed in any location and have variable network connectivity, including uniquely
the ability to operate majority of user functionality and applications (local or
cached) in offline mode.
I4.02.02 Tablet Computer User equipment that provides a complete mobile personal computer typically
larger than a mobile phone but smaller and lighter than a laptop computer,
though key differentiator with PC is a tablet always has a touch-screen user
interface and applications optimised for touch-screen interface. A tablet will
usually have Wi-Fi connectivity and some models feature mobile data
connectivity such as 3G, 4G. They typically do not have mobile phone capabilities
although they can run applications such a Skype for calling.
I4.02.03 Personal Radio User equipment specifically designed to meet the demands of providing secure
and reliable voice, data and situational awareness communications at the soldier
level. This equipment is typically optimised across the highly variable
environments soldiers operate in.
A Radio unit is a device that transmits signals through free space by
electromagnetic waves with frequencies significantly below visible light, in the
radio frequency range, from about 3 kHz to 300 GHz. These devices may be
analogue or digital, and mobile or stationary. Includes receive-only (i.e. scanner,
receiver) and transmit-only (i.e. jammer) devices.
I4.02.04 Vehicle Mounted
Equipment
User equipment that is integrated into vehicles (i.e. a self-propelled, boosted, or
towed conveyance for transporting a burden on land, sea or through air or
space). This equipment is typically ruggedised and mounted in the vehicle using a
standard mounting system, or universal "gripping type" mounts. Includes the
mounting system and ancillaries’ necessary to connect it to the system. Includes
vehicle-mounted radios in this category. Vehicle types include remote vehicles,
drones, and robots, as well as road vehicles, ships and aircraft.
I4.02.05 Mobile Phone User equipment used to make mobile telephone calls across a wide geographic
region. In addition to functioning as a telephone, a modern mobile phone
typically supports additional GSM/UMTS services such as Short Message Service
(SMS), also known as text messaging.
I4.02.06 Smart Phone A type of user equipment that offers more advanced computing ability and
connectivity than a contemporary feature mobile phone. Smartphones and
feature phones may be thought of as handheld computers with touch-screen
user-interface, integrated with a mobile telephone. With screen sizes constantly
increasing more and more smart phones are being referred to as Phablets.
I4.02.07 Camera User equipment that is able to take video, still photographs or typically both by
recoding images via an electronic image sensor. Some are GPS capable and can
produce geo-tagged images. Includes video and digital cameras.
I4.02.08 Temporary Signalling Removable signalling equipment that is used for signalling such as temporary
traffic control signals.

I4.02.09 Pager An electronic device that sends or receives numeric, text or voice messages via
radio waves. Typically a small, portable one-way receiver used to contact people
for messaging; or a two-way device with limited user acknowledgement
functionality. Part of a 'pager system' relying on base stations and repeaters for
user management and message generation/ingestion.
I4.02.10 GPS Unit GPS devices may have capabilities such as; maps, including streets maps,
displayed in human readable format via text or in a graphical format; turn-by-turn
navigation directions to a human in charge of a vehicle or vessel via text or
speech; directions fed directly to an autonomous vehicle such as a robotic probe;
traffic congestion maps (depicting either historical or real time data) and
suggested alternative directions; and information on nearby amenities such as
restaurants, fuelling stations, and tourist attractions. Consumer GPS navigation
devices include; Dedicated GPS navigation devices; GPS modules that need to be
connected to a computer to be used; GPS loggers that record trip information for
download (such GPS tracking is useful for trailblazing, mapping by hikers and
cyclists, and the production of geocoded photographs); Converged devices,
(including GPS Phones and GPS cameras), in which GPS is a feature rather than
the main purpose of the device. Military use extends to more accurate and
resilient (jamming resistant) technologies such as the Defence Advanced GPS
Receiver (DAGR).
I4.02.11 Remote Video
Terminal
Man portable equipment that displays imaging from remote platforms, such as
drones, robots, etc. This equipment typically supports multi-band digital and
analogue signals. Does not include the telemetry control component for remote
vehicle, unless built-into the terminal.
I4.02.12 Manpack Radio Rugged, lightweight, waterproof equipment that provides reliable voice and data
communications. It has minimum setup and teardown time, operates for many
days on a single battery charge and satisfies a need for extended distance
communications. Includes receive-only (i.e. scanner, receiver) and transmit-only
(i.e. jammer) devices.
I4.02.13 Wearable Equipment Wearable equipment is user equipment that provides computer and
communications devices worn on the body. This equipment is especially useful
for applications that require computational support while the user's hands, voice,
eyes, arms or attention are actively engaged with the physical environment.
There is a constant interaction between the wearable equipment and user i.e.
there is no need to turn the device on or off. Another feature is the ability to
multi-task.
I4.02.14 Wireless Headset A wireless headset is a device the user wears on the head containing microphone
and speaker and can work with various devices. Can use Wi-Fi, Bluetooth, or
Infrared for communication.
I4.02.15 Mobile Modem A plug in device, often with a USB interface, containing a SIM card that
allows data connectivity over a mobile network.
I4.02.16 Mobile Wi-Fi A standalone device containing a SIM card and a Wi-Fi interface that
allows Wi-Fi connection over a mobile network
I4.02.17 Phablet A new class of devices that blurs the line between a smart phone and a
tablet, in that it combines features of both, but typically includes a larger
screen more suitable for business productivity applications.

I4.02.99 Other Mobility
Equipment
Other end mobility equipment not specified.
I4.03 User Peripheral User peripherals are computer devices that are not part of the essential
computer (i.e. the memory and microprocessor). User peripheral devices are
external.
The human–computer interface can be described as the point of communication
between the human user and the computer, and, as such, all devices that
primarily facilitate such ongoing interactions are grouped here.
For the purposes of the IRT:
- Computer input devices are those that provide data to the machine/application
combination for further processing or for manipulation by users through the
human-computer interface devices.
- Computer output devices are those that provide data from the
machine/application combination to other machines or to the user for
asynchronous consumption.
I4.03.01 Display Any peripheral device that is used to display the computer visual/video/gui
output for user viewing. Includes personal computer displays, large-screen
monitors for group viewing, video projectors (overhead or portable), secondary
monitors and televisions (in computing display mode).
I4.03.01.01 Monitor A dedicated screen that displays computer visual/video/gui output to the user.
I4.03.01.02 Touchscreen A touchscreen is an electronic visual display that the user can control through
simple or multi-touch gestures by touching the screen with a special stylus/pen
and-or one or more fingers.
Touchscreens are common in devices such as game consoles, personal
computers, tablet computers, and smartphones. They can also be attached to
computers or, as terminals, to networks. They also play a prominent role in the
design of digital appliances such as personal digital assistants (PDAs), satellite
navigation devices, mobile phones, and video games and some books (Electronic
books).
I4.03.01.03 TV A device with a screen for receiving television signals. A TV can be connected to a
multimedia device as a display.
I4.03.01.04 Smart TV A smart television sometimes referred to as connected TV or hybrid TV, is a
television set or set-top box with integrated Internet and Web 2.0 features, and is
an example of technological convergence between computers and television sets
and set-top boxes. Besides the traditional functions of television sets and set-top
boxes provided through traditional broadcasting media, these devices can also
provide Internet TV, online interactive media, over-the-top content, as well as on-
demand streaming media, and home networking access. These TVs come pre-
loaded with an operating system
I4.03.01.05 Projector A device which projects computer visual/video/gui output onto a screen or wall.
I4.03.02 Keyboard In computing, a keyboard is a typewriter-style device, which uses an arrangement
of buttons or keys used to input of alphanumeric data into computers. Despite
the development of alternative input devices, such as the mouse, touchscreen,
pen devices, character recognition and voice recognition, the keyboard remains
the most commonly used device for direct (human) input of alphanumeric data
into computers.
I4.03.03 Mouse In computing, a mouse is a pointing device that detects two-dimensional motion
relative to a surface. This motion is typically translated into the motion of a
pointer on a display, which allows for fine control of a graphical user interface.

I4.03.04 Multifunction Device A Multifunction Device (MFD) is an office machine which incorporates the
functionality of multiple devices in one, so as to have a smaller footprint in a
home or small business setting, or to provide centralised document
management/distribution/production in a large-office setting. A typical MFP may
act as a combination of some or all of the following devices; E-mail, Fax,
Photocopier, Printer, and Image Scanner.
I4.03.05 Image Scanner In computing, an image scanner is a device that optically scans images, printed
text, handwriting, or an object, and converts it to a digital image. Image scanner
is often abbreviated to just scanner, although the term is ambiguous out of
context e.g. barcode scanner.
I4.03.06 Printer A peripheral which makes a representation of an electronic document on physical
media. This User equipment category provides the capability to print digital
content directly to a variety of media. It allows for on-demand printing, short
turnaround time and modifications of the content used for each impression.
Includes 3D personal printers.
I4.03.08 Sensor Device Input devices such as sensors, readers, measuring equipment. Includes RFID and
barcode readers.
I4.03.09 Wired Headset A wired headset is a device the user wears on the head that contains a speaker
and may contain a microphone. It can work with various devices.
I4.03.10 Speaker A device which converts an electrical audio signal into a corresponding sound.
I4.03.11 Microphone A device which converts audio sound into a corresponding an electrical signal.
I4.03.12 Point of Sale Terminal
(POS)
A POS Terminal typically includes a cash register (which in recent times comprises
a computer, monitor, cash drawer, receipt printer, customer display and a
barcode scanner) and the majority of retail POS systems also include a
debit/credit card reader. It can also include a conveyor belt, weight scale,
integrated credit card processing system, a signature capture device and a
customer pin pad device
Fax Machine Fax machine is short for facsimile machine. It is a device that sends and receives
reproductions of documents over telephone lines by converting them to and from
electronic signals. These are now often integrated with multifunction devices. As
analogue phone lines are replaced with pure digital mediums services such as fax
are becoming problematic as there is no analogue line on which they depend.
Multimedia Device Multimedia devices are electronic media devices used to store and experience
multimedia content. These are often used with a display such as a TV to access
internet services.
Radio Receiver A device for receiving radio signals. Typically these receive AM and FM
transmissions from commercial and public radio broadcasting stations. Many
devices such as some mobile phones and smart phones can include a radio.
There is an emerging use of the term Radio known as Internet Radio where the
transmissions are over the internet as data.
Memory Media "Encrypted or unencrypted memory media and devices such as portable hard
drive, SD card, Micro SD card, USB drive, Blu-ray, DVD, and CD.
I4.03.99 Other End User
Peripheral
Other end user peripheral not specified.

I4.04 Embedded Technology
Device
This refers to the various devices and parts that make up a server or computer as
well as devices that perform specific functionality outside of a server or
computer.
I4.04.01 Remote Systems
Control
Remote Systems Control is a general term that encompasses various types of
control systems, including Supervisory Control And Data Acquisition (SCADA)
systems, Distributed Control Systems (DCS), and other smaller control system
configurations such as Programmable Logic Controllers (PLC). They are used
across multiple industrial sectors and critical high-risk infrastructure
environments; in uses such as motorised cable reels, radio remote control units
and power connectors. Found in Defence and Security sectors in UAVs, sensors,
probes and other devices that are remotely controlled (telemetry) and/or have
remote data payloads. Includes the more specific radio frequency based Remote
Control System.
Remote Control Systems are typically used in industries such as electrical, water,
oil, gas, mining and data. Based on data received from remote stations,
automated or operator-driven supervisory commands can be pushed to remote
station control devices, which are often referred to as field devices. Field devices
control local operations such as opening and closing valves and breakers,
collecting data from sensor systems, and monitoring the local environment for
alarm conditions.
Based on definition of 'Industrial Control Systems' (ICS) in NIST SP 800-82.
I4.05 Equipment Operating
System
An operating system (OS) is software that manages computer hardware and
software resources and provides common services for computer programs.
Operating systems can be found on almost any device that contains a computer
including end user equipment.
I4.05.01 Mobile device OS Mobile Device OS is the Operating System that is installed on the device. There
are many flavours of mobile device OS available, each with their own user
interface which dictates look and feel. This functional component includes the
ability to support the “pushing” of corporate applications to these devices.
Mobile Device OS is intended for use in controlling any mobile device (phones,
tablets, slates, etc.). Modern Mobile OS combine the features of a thick client OS
with touchscreen, cellular, Wi-Fi, GPS mobile navigation, camera, near-field
communications, voice recorder, PDA, telephony, and other features.
I4.05.02 Thin device OS Thin Device OS is the Operating System that is installed onto the device. Many
thin devices have thin or zero OS options and just boot from firmware that can be
refreshed from a central repository when required. There are major advantages
with these options, as the maintenance around Operating System patching is
dramatically reduced or removed.
Can be installed on a thick-client device in order to re-purpose the hardware as a
thin-client.
I4.05.03 Thick device OS Thick Device OS is the Operating System that is installed onto desktop or laptop
devices. Of all the devices, this Operating System should provide the richest
functionality, but on the flip side, is likely to be the one that requires the most on-
going maintenance.
I4.05.04 Virtual Desktop OS The Virtual Desktop OS is the Operating System that is installed onto the virtual
desktop. It may be the same OS as is installed on Fat Devices, but may often be
based on a different image.

GEA-NZ v3.1 Infrastructure Reference Model and Taxonomy

More Related Content

What's hot (20)

Similar to GEA-NZ v3.1 Infrastructure Reference Model and Taxonomy (20)

GEA-NZ v3.1 Infrastructure Reference Model and Taxonomy