ISO/TS 22741-10:2024

Technical
Specification
ISO/TS 22741-10
First edition
Intelligent transport systems —
2024-10
Roadside modules AP-DATEX data
interface —
Part 10:
Variable message signs
Systèmes de transport intelligents — Interface de données AP-
DATEX pour les modules en bord de route —
Partie 10: Panneaux à messages variables
Reference number
© ISO 2024
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms. 2
5 Conformance . 2
6 Physical architecture . 5
7 User needs . 6
7.1 Manage the control mode of the VMS .6
7.2 Manage the sign display .7
7.3 Monitor the sign display doors .7
7.4 Monitor the sign display mains power .7
7.5 Monitor the sign display power supplies .7
8 Requirements . 7
8.1 Message sign control mode .7
8.1.1 Message sign control mode definition .7
8.1.2 Message sign control mode data exchange requirements .7
8.1.3 Message sign control mode capabilities .8
8.2 Message library .8
8.2.1 Message library definition .8
8.2.2 Message library data exchange requirements .8
8.2.3 Message library capabilities.10
8.3 Sign display . 12
8.3.1 Sign display definition . 12
8.3.2 Sign display data exchange requirements . 12
8.4 Sign display doors . 13
8.4.1 Sign display doors definition . 13
8.4.2 Sign display doors data exchange requirements . 13
8.4.3 Sign display door capability requirements .14
8.4.4 Sign display door design constraints .14
8.5 Sign display mains power .14
8.5.1 Sign display mains power definition .14
8.5.2 Sign display mains power data exchange requirements .14
8.5.3 Sign display mains power capability requirements .14
8.5.4 Sign display mains power design constraints .14
8.6 Sign display power supplies .14
8.6.1 Sign display power supplies definition .14
8.6.2 Sign display power supplies exchange requirements . 15
8.6.3 Sign display power supplies capability requirements . 15
8.6.4 Sign display power supplies design constraints . 15
8.7 Sign display light sensors . 15
8.7.1 Sign display light sensors definition . 15
8.7.2 Sign display light sensors exchange requirements. 15
8.7.3 Sign display light sensors capability requirements . 15
8.7.4 Sign display light sensors design constraints . 15
8.8 Sign display pixels .16
8.8.1 Sign display pixels definition .16
8.8.2 Sign display pixels data exchange requirements .16
8.8.3 Sign display pixels capability .16
9 Dialogues . 16

iii
9.1 Get elemental data .16
9.2 Set elemental data .17
Annex A (normative) Data packet structures .18
Annex B (normative) Requirements traceability matrix .25
Bibliography .30

iv
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
A list of all parts in the ISO 22741 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

v
Introduction
0.1  Background
A variable message sign (VMS) is an electronic traffic sign installed on the roadside to provide real-time
traffic information to travellers, thereby improving their efficiency in using road traffic. A VMS is a major
physical component of the intelligent transportation system (ITS), to which it supplies information for
improvement of the safety on the road.
More VMSs are expected to be installed and operated due to increasing demand for the establishment of ITS
and the replacement of existing VMSs which have exceeded their durability terms.
Operators of traffic management centres need real-time data exchange between a VMS and the centre in
order to supply information to the VMS in real time and to control and manage the VMS.
However, no standards for the information transmitted and received between the traffic management centre
and the VMS have been established, leading to the development of various protocols and their application
to each VMS construction project. As a result, a variety of problems have arisen, including redundant
investment in development costs and forced dependence on the protocol of the previous operator when
replacing the existing VMSs with new ones.
This document therefore defines the data items (messages), formats and communication protocols
(application, presentation, session and transport layers) required to ensure the interoperability of the
information transmitted and received between the VMS and the traffic management centre, thereby
ensuring interoperability between the VMS and the centre.
0.2  Overview
This document defines the message, the data elements making up the message, and the application layer
profile for message transmission in order to ensure the interoperability between the VMS and the traffic
management centre.
In particular, in order to ensure the interoperability between the VMS and the traffic management centre,
the interoperability is developed based on OSI (open system interconnection) 7 layers. A collection of
standard protocols for each layer is referred to as a "profile".
ISO/IEC TR 10000-2 defines the basic classification and object presentation of OSI profiles as follows.
a) Interchange format and representation profiles define the information on and message structure of the
data exchanged by applications.
b) Application profiles define the transmission mechanism for data exchange (concerning OSI layers 5 to
7 – session, presentation and application layers).
c) Transport profiles define the procedures and methods to exchange data packets between systems
(concerning ;OSI layers 1 to 4 – transport, network, data link and physical layers).
d) Relay profiles define the relaying function which enables the interconnection between systems while
using different transmission profiles.
This document specifies "interchange format and representation" as defined in ISO/IEC TR 10000-2,
covering the following points:
1) components and data elements of basic messages define the messages and detailed data elements which
the operator of the traffic information system needs for operation of the VMS;
2) the data exchange communication profile defines the procedures and encoding methods for information
exchange between the traffic management centre and the VMS.

vi
0.3  Document approach and layout
This document specifies the following:
a) physical architecture for varible message signs (Clause 6);
b) user needs that are deemed to be common to many types of field devices (Clause 7);
c) requirements for implementing the identified user needs, organized by major feature (Clause 8);
d) dialogues for exchange data between varible message signs and the central/local computer (Clause 9);
e) the data packet structures for the features defined by this document (Annex A);
f) a requirements traceability table that traces requirements to the design elements (Annex B).
In addition, a simplified version of the conformance table and the data packet structures are available
electronically at https://standards.iso.org/iso/ts/22741/-10/ed-1/en/.
ISO 22741-1 provides additional details about how the ISO 22741 series relates to the overall ITS architecture.

vii
Technical Specification ISO/TS 22741-10:2024(en)
Intelligent transport systems — Roadside modules AP-DATEX
data interface —
Part 10:
Variable message signs
1 Scope
Variable message signs (VMSs) are installed in areas where traffic managers identify a frequent need
to convey information to the travelling public, such as upstream from interchanges to alert the public to
downstream congestion in time for them to alter their routes. This allows traffic managers to improve the
efficiency, safety and quality of traveller journeys.
In order to manage the operation of a VMS and the messages displayed, information exchange between the
management systems and the VMS is needed.
This document identifies basic user needs for the management of light-emitting diode (LED) matrix VMSs and
traces these needs to interoperable designs. This includes the ability to identify the device, its capabilities,
and its status.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 22741-1, Intelligent transport systems — Roadside modules AP-DATEX data interface — Part 1: Overview
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 22741-1 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
architecture
fundamental concepts or properties of a system in its environment embodied in its elements, relationships,
and in the principles of its design and evolution
3.2
centre system
intelligent transport systems (ITS) component that provides application, management and/or administrative
functions from a centralized location (i.e. not at the roadside)
3.3
message
data concept consisting of a grouping of data elements, data frames, or data elements and data frames, that
is used to convey a complete set of information

3.4
traffic management system
centre system that monitors and controls traffic and the road network
3.5
variable message sign
VMS
field device that can display real-time traveller information to the public
Note 1 to entry: A VMS can display the message predefined in a stored library by the operator. A VMS can also
immediately display the message desired by the operator.
Note 2 to entry: A VMS typically consists of one sign display, one sign controller, a cabinet that houses the sign
controller, and potentially other components.
4 Symbols and abbreviated terms
ASCII american standard code for information interchange
AP-DATEX application profile-data exchange
CRC cyclical redundancy check
I/O input and output
ITS intelligent transportation systems
MULTI markup language for transportation information
NTCIP national transportation communications for its protocol
RTM requirements traceability matrix
UTF-8 universal coded character set transformation format – 8-bit
VMS variable message signs
5 Conformance
This clause follows the rules defined in ISO 22741-1. Table 1 traces each user need to a set of software
features. Table 2 traces each feature to a set of requirements. For a full understanding of these tables and
codes, see ISO 22741-1.
NOTE 1 The development of the content of this document followed a formal systems engineering process, which
entails:
a) defining needs;
b) developing a set of interface requirements;
c) developing features as a part of a high-level design to meet the requirements;
d) refining the interface requirements from Step 2 to reflect the high-level design; and
e) developing a low-level design defining the dialogues and data elements necessary to implement the requirements.
The documentation omits the original requirements as they are refined in Step 4 and listing the original requirements
would make the document highly redundant.

Table 1 — User need to feature conformance
User Need Feature Conformance
Inherited user needs
ISO/TS 22741-2:2024, 7.1: Monitor the field device M
ISO/TS 22741-2:2024, 7.3.1: Monitor cabinet doors O
ISO/TS 22741-2:2024, 7.3.2: Monitor and control cabinet fans O
ISO/TS 22741-2:2024, 7.3.3: Monitor and control cabinet heaters O
ISO/TS 22741-2:2024, 7.3.4: Monitor cabinet humidity O
ISO/TS 22741-2:2024, 7.3.5: Monitor cabinet temperature O
ISO/TS 22741-2:2024, 7.3.6: Monitor cabinet AC power O
ISO/TS 22741-2:2024, 7.3.7: Monitor cabinet battery power O
ISO/TS 22741-2:2024, 7.3.8: Monitor cabinet generator power O
ISO/TS 22741-2:2024, 7.3.9: Monitor cabinet solar power O
ISO/TS 22741-2:2024, 7.3.10: Monitor cabinet wind power O
User needs defined in this document
7.1: Manage the control mode of the VMS M
8.1: Message sign control mode M
7.2: Manage the sign display M
8.2: Message library M
8.3: Sign display M
8.7: Sign display light sensors O
8.8: Sign display pixels O
7.3: Monitor the sign display doors O
8.4: Sign display doors M
ISO/TS 22741-2:2024, 8.2: General-purpose I/O M
7.4: Monitor the sign display mains power O
8.5: Sign display mains power M
ISO/TS 22741-2:2024, 8.2: General-purpose I/O M
7.5: Monitor the sign display power supplies O
8.6: Sign display power supplies M
ISO/TS 22741-2:2024, 8.2: General-purpose I/O M
Table 2 — Feature to requirement conformance
a
Feature Requirement Conformance
8.1: Message sign control mode
8.1.2.1: Configure control mode 8.1.3.2:M
8.1.2.2: Verify control mode M
8.1.3.1: Support central control mode M
8.1.3.2: Support local control mode O
8.1.3.3: Support central override control mode 8.1.3.2:M
8.2: Message library
8.2.2.1: Discover capabilities of the message library M
8.2.2.2: Configure default flash times O
8.2.2.3: Verify default flash times 8.2.2.2:M
8.2.2.4: Configure default page times O
a.
Conformance column follows the rules defined in ISO 22741-1:2022, Clause 5

TTabablele 2 2 ((ccoonnttiinnueuedd))
a
Feature Requirement Conformance
8.2.2.5: Verify default page times 8.2.2.4:M
8.2.2.6: Configure default line justification O
8.2.2.7: Verify default line justification 8.2.2.6:M
8.2.2.8: Configure default page justification O
8.2.2.9: Verify default page justification 8.2.2.8:M
8.2.2.10: Configure default colours M
8.2.2.11: Verify default colours M
8.2.2.12: Configure message encoding M
8.2.2.13: Verify message encoding M
8.2.2.14: Configure a message M
8.2.2.15: Verify message configuration M
8.2.2.16: Verify message code M
8.2.2.17: Retrieve message enabled status M
8.2.2.18: Toggle message enabled status M
8.2.2.19: Delete message M
8.2.2.20: Delete all messages M
8.2.3.1.1: Supported minimum flash time 8.2.2.2:M
8.2.3.1.2: Supported maximum flash time 8.2.2.2:M
8.2.3.1.3: Supported flash time step size 8.2.2.2:M
8.2.3.2.1: Supported minimum page time 8.2.2.4:M
8.2.3.2.2: Supported maximum page time 8.2.2.4:M
8.2.3.2.3: Supported page time step size 8.2.2.4:M
8.2.3.3.1: Line justification – Left 8.2.2.6:M
8.2.3.3.2: Line justification – Centre 8.2.2.6:M
8.2.3.3.3: Line justification – Right 8.2.2.6:M
8.2.3.3.4: Line justification – Full 8.2.2.6:M
8.2.3.4.1: Page justification – Top 8.2.2.8:M
8.2.3.4.2: Page justification – Middle 8.2.2.8:M
8.2.3.4.3: Page justification – Bottom 8.2.2.8:M
8.2.3.5.1: Message encoding – ASCII O.1 (1.*)
8.2.3.5.2: Message encoding – UTF-8 O.1 (1.*)
8.2.3.6.1: Circular moving text O
8.2.3.6.2: Linear moving text O
8.3: Sign display
8.3.2.1: Discover characteristics of the sign display M
8.3.2.2: Configure location of sign display M
8.3.2.3: Verify location of sign display M
8.3.2.4: Configure end duration message M
8.3.2.5: Verify end duration message M
8.3.2.6: Display a message on the sign display M
8.3.2.7: Monitor current message M
8.3.2.8: Monitor dynamic fields of current message O
8.4: Sign display doors
a.
Conformance column follows the rules defined in ISO 22741-1:2022, Clause 5

TTabablele 2 2 ((ccoonnttiinnueuedd))
a
Feature Requirement Conformance
8.4.3.1: Sign display doors monitored M
8.4.4.1: Sign display doors monitored through general-purpose I/O M
8.5: Sign display mains power
8.5.3.1: Sign display mains power voltage M
8.5.3.2: Sign display mains power current M
8.5.4.1: Sign display mains power voltage monitored through general-purpose I/O M
8.5.4.2: Sign display mains power current monitored through general-purpose I/O M
8.6: Sign display power supplies
8.6.3.1: Sign display power supplies voltage M
8.6.3.2: Sign display power supplies current M
8.6.4.1: Sign display power supplies voltage monitored through general-purpose I/O M
8.6.4.2: Sign display power supplies current monitored through general-purpose I/O M
8.7: Sign display light sensors
8.7.3.1: Sign display light sensors monitored M
8.7.4.1: Sign display light sensors monitored through general-purpose I/O M
8.8: Sign display pixels
8.8.2.1: Discover characteristics of sign display pixels M
8.8.2.2: Perform pixel test M
8.8.3.1: Sign display pixels monitored M
8.8.3.2: Colourful pixel O
a.
Conformance column follows the rules defined in ISO 22741-1:2022, Clause 5
Each requirement specifying a need for a data exchange traces to one dialogue and one or more data
element(s) that an implementation claiming conformance to the requirement shall support.
Data packet structure and dialogue for data exchange based on ISO 22741-1 shall conform to Annex A and
Annex B.
NOTE 2 The dialogues defined in this document are specified to promote a common interface for testing purposes
and are not intended to restrict otherwise allowable requests or notifications. The file for the maintenance portal is
attached
6 Physical architecture
The physical architecture of the key components for a VMS system is depicted in Figure 1. A VMS, which
may be portable or permanent, can be controlled from either a centre system (such as a traffic management
system) or field support equipment (such as a laptop computer). The telecommunications network between
these units can be wired or wireless. The local VMS typically includes a roadside module containing a
processor and a sign display that displays the actual message, typically through a matrix of pixels.

Key
1 wire/wireless direct communication between a local computer and fixed/portable VMS [covered by ISO/TS 22741-
10 (this document)]
2 wireless communication between central computer and portable VMS [covered by ISO/TS 22741-10 (this document)]
3 wire/wireless communication between central computer and fixed VMS [covered by ISO/TS 22741-10 (this
document)]
4 communication between roadside module and the sign display is out of scope
Figure 1 — View of a physical architecture
This document is only concerned with the interface between an external computer (e.g. at the centre or the
field support equipment) and the VMS. The interface between the roadside module and the sign display is
out of scope in this document.
NOTE This document is designed with the expectation that all communications conform with ISO 15784-3, but
the design is not necessarily restricted to that environment.
7 User needs
7.1 Manage the control mode of the VMS
After a VMS is installed in the field, a manager needs to be able to control and manage the VMS through any
of the following modes:
a) central mode: the VMS is controlled and managed from a computer located in a (typically remote) centre,
such as a traffic management centre;
b) local mode: the VMS is controlled and managed from field support equipment, such as a technician’s
laptop computer by activating a switch at the device;
c) central override mode: the VMS is controlled and managed from a computer located in a (typically
remote) centre, such as a traffic management centre, even though the local control switch has been
activated. This mode is primarily intended to overcome the problem of a technician failing to reset the
switch before leaving the VMS. As the VMS can be in a remote location, forcing central control remotely
can save time and expenses in placing the VMS back into the desired state.

7.2 Manage the sign display
A manager needs to be able to control the message on the sign display and monitor its overall operation
and status.
7.3 Monitor the sign display doors
A manager needs to be able to monitor the open/closed status of doors associated with the sign display
cabinet.
NOTE The doors on the controller cabinet are monitored through a separate user need defined in ISO/TS 22741-2.
7.4 Monitor the sign display mains power
A manager needs to be able to monitor the mains power associated with the sign display cabinet.
NOTE The power for the controller cabinet is monitored through a separate user need defined in ISO/TS 22741-2.
7.5 Monitor the sign display power supplies
A manager needs to be able to monitor the power supplies within the sign display.
8 Requirements
8.1 Message sign control mode
8.1.1 Message sign control mode definition
The term “variable message sign” (VMS) comprises the sign display, sign controller, the cabinet that houses
the sign controller, and potentially other components. The VMS can potentially be controlled remotely (i.e.
from a centre) or locally (i.e. from a local laptop interface or directly through the sign controller’s interface).
The control mode allows a manager to configure and determine which input has control over a sign to prevent
conflicts from different sources. For example, the control mode allows a manager to ensure a message is not
inadvertently overwritten by the other (i.e. local/remote) source. Both connections always have access to
retrieve (i.e. subscription) any information, but only the selected source is able to control (i.e. publication)
most information in the sign. The control mode feature defines the rules for configuring and monitoring the
control mode.
The control mode is ideally controlled via a switch provided by the controller to select either local or remote
control. However, an override mode is also provided.
8.1.2 Message sign control mode data exchange requirements
8.1.2.1 Configure control mode
The field device shall allow a manager to force the controller into a central override mode, which will
override the local control switch on the controller.
8.1.2.2 Verify control mode
The field device shall allow a manager to verify the current control mode.

8.1.3 Message sign control mode capabilities
8.1.3.1 Support central control mode
The field device shall support the central control mode.
8.1.3.2 Support local control mode
The field device shall support a local control mode that allows a user at the sign to take control of the sign
display.
8.1.3.3 Support central override control mode
The field device shall support the central override control mode.
8.2 Message library
8.2.1 Message library definition
The message library is a table that stores messages that can be displayed on the sign.
Each message consists of numbers, letters, images, symbols, etc. along with formatting information (e.g.
flash codes and colour codes) to provide various information to the travelling public. The information to be
conveyed by the message is defined by the manager.
Each message is stored in the message library and referenced or deleted as needed.
8.2.2 Message library data exchange requirements
8.2.2.1 Discover capabilities of the message library
The field device shall allow a manager to determine the capabilities of the message library, including:
a) maximum number of pages supported within a message;
b) maximum number of bytes in a message MULTI string;
c) support for message MULTI tags.
[14]
NOTE MULTI is defined in NTCIP 1203.
8.2.2.2 Configure default flash times
The field device shall allow a manager to configure default flash times.
8.2.2.3 Verify default flash times
The field device shall allow a manager to verify default flash time configuration.
8.2.2.4 Configure default page times
The field device shall allow a manager to configure default page times.
8.2.2.5 Verify default page times
The field device shall allow a manager to verify default page time configuration.

8.2.2.6 Configure default line justification
The field device shall allow a manager to configure default line justification.
8.2.2.7 Verify default line justification
The field device shall allow a manager to verify default line justification configuration.
8.2.2.8 Configure default page justification
The field device shall allow a manager to configure default page justification.
8.2.2.9 Verify default page justification
The field device shall allow a manager to verify default page justification configuration.
8.2.2.10 Configure default colours
The field device shall allow a manager to configure default background and default foreground colours.
8.2.2.11 Verify default colours
The field device shall allow a manager to verify default background and default foreground colours
configuration.
8.2.2.12 Configure message encoding
The field device shall allow a manager to configure the message encoding format (i.e. ASCII or UTF-8).
8.2.2.13 Verify message encoding
The field device shall allow a manager to verify the message encoding.
8.2.2.14 Configure a message
The field device shall allow a manager to configure a message for display.
NOTE The format of the message string conforms to the MarkUp Language for Transportation Information
[14]
(MULTI) format defined in NTCIP 1203:2011, Section 6.
8.2.2.15 Verify message configuration
The field device shall allow a manager to verify the configuration settings of a message.
8.2.2.16 Verify message code
The field device shall allow a manager to quickly verify message contents by retrieving an abbreviated
reference code.
NOTE In practice, this is a CRC code of the message contents.
8.2.2.17 Retrieve message enabled status
The field device shall allow a manager to retrieve the enabled status of the message.
NOTE Enabled messages are available for immediate display.

8.2.2.18 Toggle message enabled status
The field device shall allow a manager to toggle the enabled status of a message.
8.2.2.19 Delete message
The field device shall allow a manager to delete a message.
8.2.2.20 Delete all messages
The field device shall allow a manager to delete all non-permanent messages.
8.2.3 Message library capabilities
8.2.3.1 Supported flash times
8.2.3.1.1 Supported minimum flash time
The field device shall support minimum flash on and off times as defined in the specification. If the
specification does not define these values, the minimum flash on time shall be 0,5 s and the minimum flash
off time shall be 0,5 s.
NOTE The flash on time indicates the duration that the text remains visible during one flash; the flash off time
indicates the duration between flashes, when the text is not visible.
8.2.3.1.2 Supported maximum flash time
The field device shall support maximum flash on and off times as defined in the specification. If the
specification does not define these values, the maximum flash on time shall be 10,0 s and the maximum flash
off time shall be 10,0 s.
8.2.3.1.3 Supported flash time step size
The field device shall support flash time on and off step sizes as defined in the specification. If the
specification does not define these values, the flash on time step size shall be 0,5 s and the flash off time step
size shall be 0,5 s.
NOTE The step size indicates the valid values when configuring the flash on and flash off values. For example, the
minimum allowed value is defined by the minimum flash time, the next valid value is the minimum flash time plus one
step size.
8.2.3.2 Supported page times
8.2.3.2.1 Supported minimum page time
The field device shall support minimum page on and off times as defined in the specification. If the
specification does not define these values, the minimum page on time shall be 0,5 s and the minimum page
off time shall be 0,5 s.
NOTE 1 The page on time indicates the duration for which each page of the message is displayed prior to going to
the page off time and then the next page display. The page off time indicates the duration between pages, when the
sign display is blank.
NOTE 2 The page timer operates independently of any flashing text timers. For example, if a page with an on time
of 5,0 s contains flashing text that flashes on for 1,0 s followed by flashing off for 1,0 s, the flashing text will appear 3
times, but the final flash off will be superseded by the page off time.

8.2.3.2.2 Supported maximum page time
The field device shall support maximum page on and off times as defined in the specification. If the
specification does not define these values, the maximum page on time shall be 10,0 s and the page flash off
time shall be 10,0 s.
8.2.3.2.3 Supported page time step size
The field device shall support page time on and off step sizes as defined in the specification. If the
specification does not define these values, the page on time step size shall be 0,5 s and the page off time step
size shall be 0,5 s.
8.2.3.3 Supported line justification
8.2.3.3.1 Line justification — Left
The field device shall support left line justification by supporting the [jl2] MULTI tag as defined in NTCIP
1203:2011, Section 6.
8.2.3.3.2 Line justification — Centre
The field device shall support centre line justification by supporting the [jl3] MULTI tag as defined in NTCIP
1203:2011, Section 6.
8.2.3.3.3 Line justification — Right
The field device shall support right line justification by supporting the [jl4] MULTI tag as defined in NTCIP
1203:2011, Section 6.
8.2.3.3.4 Line justification — Full
The field device shall support full line justification by supporting the [jl5] MULTI tag as defined in NTCIP
1203:2011, Section 6.
8.2.3.4 Supported page justification
8.2.3.4.1 Page justification — Top
The field device shall support top page justification by supporting the [jp2] MULTI tag as defined in NTCIP
1203:2011, Section 6.
8.2.3.4.2 Page justification — Middle
The field device shall support middle page justification by supporting the [jp3] MULTI tag as defined in
NTCIP 1203:2011, Section 6.
8.2.3.4.3 Page justification — Bottom
The field device shall support bottom page justification by supporting the [jp4] MULTI tag as defined in
NTCIP 1203:2011, Section 6.
8.2.3.5 Supported message encodings
8.2.3.5.1 Message encoding — ASCII
The field device shall support defining messages using ASCII encoded character strings.

8.2.3.5.2 Message encoding – UTF-8
The field device shall support defining messages using UTF-8 encoded character strings.
8.2.3.6 Supported moving text
8.2.3.6.1 Circular moving text
The field device shall support circular moving text by supporting the [mvc…] MULTI tag as defined in NTCIP
1203:2011, Section 6.
NOTE Circular moving text displays text in a defined region of the display and moves it across this region at a
defined rate. If the text is shorter than the defined region, multiple copies of the text are shown appended to one
another.
8.2.3.6.2 Linear moving text
The field device shall support linear moving text by supporting the [mvl…] MULTI tag as defined in NTCIP
1203:2011, Section 6.
NOTE Linear moving text displays text in a defined region of the display and moves it across this region at a
defined rate. The region is initialized with the text string and it is moved across the defined region. Once the entire
text string has been displayed, the region is cleared and reset to the original display.
8.3 Sign display
8.3.1 Sign display definition
The sign display includes the sign housing, associated doors, power supplies and the display that is visible
to the public. The message sign housing is the enclosure that environmentally protects all of the other
components of the sign display.
8.3.2 Sign display data exchange requirements
8.3.2.1 Discover characteristics of the sign display
The field device shall allow a manager to discover characteristics of the sign display, including:
a) sign type (e.g. portable or permanent and matrix arrangement);
b) sign access (e.g. walk-in versus rear access);
c) sign dimensions;
d) sign border dimensions;
e) legend;
f) beacon type.
8.3.2.2 Configure location of sign display
The field device shall allow a manager to configure the detailed location of the sign display in textual format.
NOTE 1 The location of the sign display can be different from the location of the controller (as defined in
ISO/TS 22741-2).
NOTE 2 The latitude and l
...