Example DMS NTCIP Communications Specification

53 Pages·2007·0.28 MB·English

Appendix J
New York State ITS Standards Specification Development
Guide

Example New York State ITS Project
Dynamic Message Sign (DMS)
Information Level
NTCIP Communications Specification

Prepared for

New York State Department of Transportation

Prepared by

Consensus Systems Technologies Corp.

January 16, 2007
New York State ITS Standards Specification Development Guide
Table of Contents

1 Introduction.............................................................................................................................1
1.1 Project Background..........................................................................................................1
1.2 Specification Development Approach.............................................................................1
1.3 Document Organization...................................................................................................2
2 DMS Specification Operations Plan.......................................................................................3
2.1 Normal Operations...........................................................................................................3
2.1.1 Default Messages......................................................................................................3
2.1.2 Sign Display Behavior After Bootup........................................................................3
2.1.3 Sign Display After a Momentary Power Loss..........................................................4
2.1.4 Sign Display Behavior During Communications Loss.............................................4
2.1.5 Sign Display After End Duration..............................................................................4
2.1.6 Sign Display After Controller Reset.........................................................................4
2.1.7 Polling.......................................................................................................................5
2.1.8 Activate Messages....................................................................................................6
2.2 Exception Operations.......................................................................................................6
2.3 Control Modes..................................................................................................................6
2.3.1 Central Mode............................................................................................................6
2.3.2 Local Mode...............................................................................................................7
2.3.3 Central Override Mode.............................................................................................7
2.4 Monitoring........................................................................................................................7
2.4.1 Monitoring Status......................................................................................................7
2.4.2 Event History............................................................................................................8
2.4.3 Diagnostics................................................................................................................8
3 NTCIP Communications Specification...................................................................................9
3.1 General NTCIP Requirements.........................................................................................9
3.1.1 Definitions.................................................................................................................9
3.1.2 References.................................................................................................................9
3.1.3 Conformance.............................................................................................................9
3.1.4 Property Rights.......................................................................................................10
3.2 Physical Features............................................................................................................10
3.2.1 Type of Sign............................................................................................................10
3.2.2 LEDs.......................................................................................................................10
3.2.3 Communications Ports............................................................................................10
3.2.4 Fonts........................................................................................................................11
3.2.5 Photosensors...........................................................................................................11
4 Protocol Implementation Conformance Specification..........................................................12
4.1 Protocol Implementation Conformance Specification and Requirements.....................13
4.1.1 Protocol Implementation Conformance Specification (PICS)................................13
4.2 Functional Requirements................................................................................................15
4.2.1 Requirements Traceability Matrix..........................................................................18
4.3 Dialogs...........................................................................................................................21
4.3.1 Dialog 4.3.2.1 Activate a Message.........................................................................21
4.3.2 Dialog 4.3.3.14 Monitor the Current Message.......................................................22
i
New York State ITS Standards Specification Development Guide
4.4 DMS Object Definitions.................................................................................................24
4.4.1 Object 5.6.8.1 Message Memory Type Parameter..................................................24
4.4.2 5.6.8.2 Message Number Parameter.......................................................................25
4.4.3 Object 5.6.8.3 Message MULTI String Parameter.................................................25
4.4.4 Object 5.6.8.4 Message Owner Parameter..............................................................26
4.4.5 Object 5.6.8.6 Message Beacon Parameter.............................................................26
4.4.6 5.6.8.7 Message Pixel Service Parameter...............................................................27
4.4.7 Object 5.6.8.8 Message Run Time Priority Parameter...........................................27
4.4.8 Object 5.6.8.10 Message Name Parameter.............................................................27
4.4.9 Object 5.7.3 Activate Message Parameter..............................................................28
4.4.10 Object 5.7.4 Message Display Time Remaining Parameter...............................28
4.4.11 Object 5.7.5 Message Table Source Parameter...................................................29
4.4.12 Object 5.7.6 Message Requester ID Parameter...................................................29
4.4.13 Object 5.7.7 Message Source Mode Parameter...................................................30
4.4.14 Object 5.7.17 Activate Message Error Parameter...............................................31
4.4.15 Object 5.7.18 MULTI Syntax Error Parameter...................................................33
4.4.16 Object 5.7.19 Position of MULTI Syntax Error Parameter................................34
4.4.17 Object 5.7.20 Other MULTI Error Parameter.....................................................34
4.4.18 Object 5.7.19 Position of MULTI Syntax Error Parameter................................35
4.4.19 Object 5.7.20 Other MULTI Error Parameter.....................................................35
4.4.20 Object 5.7.26 Activate Message State.................................................................35
4.4.21 Object 5.8.5 Status of Illumination Brightness Level Parameter........................36
4.4.22 Object 5.8.9 Status of Illumination Light Output Parameter..............................36
5 Software and Integration Support.........................................................................................38
5.1.1 Software..................................................................................................................38
5.1.2 Integration Support.................................................................................................38
6 Installation and Testing.........................................................................................................40
6.1.1 Factory Tests...........................................................................................................41
6.1.2 Visual Inspection Test.............................................................................................42
6.1.3 Startup Tests............................................................................................................43
6.1.4 Stand-alone Tests....................................................................................................44
6.1.5 Operational Tests....................................................................................................45
6.2 Workstation....................................................................................................................47
7 Documentation......................................................................................................................49

ii
New York State ITS Standards Specification Development Guide

Revision History

Filename Version Date Author Comment
NYStateSpecGuide-ApJ.doc 0.1 10/08/06 P. Chan / M. Initial Draft
Insignares
NYStateSpecGuide-ApJ.doc 0.3 11/22/06 P. Chan / M. Updated formatting of appendices in standards
Insignares specification guide.
NYStateSpecGuide-ApJ.doc 0.4 1/16/07 P. Chan / M. Updated specification to reflect V2 of the
Insignares NTCIP 1203 DMS specification.

iii
New York State ITS Standards Specification Development Guide
1 Introduction

1.1 Project Background
The New York State Department of Transportation (NYSDOT) has initiate a project to deploy an end-to-
end communications system to improve transportation information dissemination to motorist and
neighboring agencies. This deployment will result in the expansion of the NYSDOT ITS program, and
work towards the deployment of transportation operations communications network.
This (Draft) NY State Dynamic Message Sign NTCIP Communications Specification has been developed
through the consensus input of regional stakeholders to standardize the communication interfaces of
DMS. Only the DMS interface (the way the sign communicates with a traffic management center) is
being standardized, the DMS firmware and software, design, algorithms and methodologies that
implement the interface, provided by numerous system integrators and vendors, are not covered by this
specification.
1.2 Specification Development Approach
Following a Systems Engineering Methodology, a user-needs assessment and concept of operations
(ConOps) were developed. Based on the ConOps, functional requirements and stakeholder agreement
were developed. The figure below shows the application of the 'VEE' model to the development of the
NY State C2C Interface Specification Development.

Feasibility Study Operations Changes
Regional Retirement/
Architecture(s) / Concept and and Replacement
Exploration Maintenance Upgrades
Concept of System Validation Plan System
Operations Validation
System Verification Plan n
o
Decom ReSqyusirteemments (SystSeumb sAycscteepmtance) DVeeprlioSfiycymastteieonmnt & mpositi
po Verification Plan co
siti High-Level (Subsystem Acceptance) Subsystem Re
on Design Verification nd
and UnTiet s/t DPelavnice on a
Defi DDeetsaiiglend UnTiet s/ tDinegvice grati
nition Software / Hardware Inte
Document/Approval
Development
Field Installation
Time Line

1
New York State ITS Standards Specification Development Guide
The system functional requirements for NY State DMS (Dynamic Message Sign) System are the basis for
development of this technical specification.
Stepping from problem (requirements) to solution (design) a requirements traceability matrix (RTM) was
developed to document how the analysis of requirements translates to the project-specific design of center
interfaces.
1.3 Document Organization
This document is comprised of five Sections and three Appendices.
• Section 1 - Introduction. This section provides an overview of the document and introductory
material.
• Section 2 - General Requirements. Contains a list of references to other documents, a
conformance statement, and a glossary of terms.

2
New York State ITS Standards Specification Development Guide
2 DMS Specification Operations Plan

This document section contains detailed operational and functional specification for the
Dynamic Message Sign (DMS) to be installed as part of this project.
The intent of this document is to present:
• the functions and capabilities available by the DMS to be procured by this project
• a discussion on how the DMS is envisioned to be controlled and monitored from the
ATMS software, and
• the functions and capabilities accessible from the manufacturer-provided software
The document describes the behavior of the DMS under the various modes and conditions that
the signs may experience. This concepts described in this document will be used to develop
the Technical Specification for the DMS, to define the objects and ranges for the NTCIP
standard, and to determine the test procedures for the DMS.
Variables that can be changed are provided in italics. These variables were selected based on
the consultant’s understanding from the Standards workshop conducted on MM/DD/YYYY, or
are the consultant’s recommendation. These values can be changed prior to completion of the
Technical Specification. Variables are that require further discussion or a decision by the
agency(ies) are in bold italics. When reviewing this Concept of Operations, ASSUME that if
the capability is NOT explicitly mentioned in this document, that the feature is not a requirement.
2.1 Normal Operations
2.1.1 Default Messages
Several default messages will be stored on the DMS Controller. These messages will be stored
in non-volatile memory. These default messages can be changed using the manufacturer-
provided software.
2.1.2 Sign Display Behavior After Bootup
When the DMS is first powered on, the DMS face shall remain blank during the power-up and
boot-up cycle. Once the boot-up cycle is complete, the DMS will display a default message until
a message is commanded.
The default message to be displayed can be a blank message, a specific defined message, or
the last message commanded before the DMS was shut down. Note that a different default
message may be displayed if the DMS controller was shut down due to a controller software
reset command or a momentary power loss (see below). The duration of time which constitutes
a momentary power loss is user-defined.
The default message to be displayed after a DMS Bootup is currently a blank message.
3
New York State ITS Standards Specification Development Guide
2.1.3 Sign Display After a Momentary Power Loss
If the elapsed time is less than the defined time duration, for example, one second, the DMS
can be configured to display a default message. The default message to be displayed can be a
blank message, a specific defined message, or the last message commanded before the DMS
momentarily lost power.
The current default message to be displayed after a Momentary Power Loss shall remain the
current message, and the defined time duration shall be 1 second. The assumption is that if
the DMS momentarily loses electrical power for less than 1 second, the message should not
change from what is currently displayed before the momentary power loss.
2.1.4 Sign Display Behavior During Communications Loss
This parameter defines what message should be displayed on the DMS if the DMS controller
has not received a valid poll from any source for a defined time period. The message to be
displayed can be a blank message, the current message, or a specific defined message. This
parameter does not apply if the DMS is in Local Mode.
A determinant of the defined time period will be how often the ATMS software polls the DMS. If
the polling period is one hour (dialup modem), the defined time period should be longer than 1
hour, say, 121 minutes (2 hours, or 2 polling periods, + 1 minute). If the polling period is 15
minutes (direct-connect), the defined time period may be 46 minutes (45 minutes, or 3 polling
periods, + 1 minute).
Assuming a direct connection, the DMS will be set to display a blank message is no valid
communications with the AGENCY STATEWIDE TOC is detected within 46 minutes. Once
valid communications is received, the DMS will display the same message (in this case, the
blank message) until a new message is commanded.
2.1.5 Sign Display After End Duration
Messages on the DMS can be activated for a fixed duration, either from a scheduler or manually
(e.g., Display Message X for 30 minutes). If a message ends, and no other message has been
assigned to replace the message, the DMS will display a blank message. The DMS will
continue to display this message until a valid message is commanded.
2.1.6 Sign Display After Controller Reset
If the controller is reset (software), the DMS can be set to display a specific message after the
reset. This parameter is optional and assumes that the DMS controller can differentiate
between a power loss and controller reset. The default message to be displayed can be a blank
message, a specific defined message, the last message commanded before the DMS was
reset. The current default message to be displayed after a Controller Reset should be a blank
message. The DMS will continue to display this message until a valid message is commanded.
ATMS Software
Under normal conditions, the DMS will be monitored and controlled from the AGENCY
Operations Center, using the ATMS software.
4
New York State ITS Standards Specification Development Guide
The ATMS software provides the following functions:
• polls the DMS for operational status (errors) and checks the current message on a
periodic basis (currently once per hour)
• selects a message to display from the center’s library on the DMS based on current
traffic conditions and incidents (subject to operator approval)
• once a message has been selected for display, the software downloads the message to
the DMS and activates the message.
2.1.7 Polling
The ATMS software polls each DMS on a periodic basis for operational status and verifies the
message currently displayed. The periodic basis is adjustable (by communications channel)
and is currently set for once per hour. The one-hour period was selected because the
communications media for a majority of the DMSs operated and monitored by AGENCY is on
dial-up telephone lines. For DMSs that uses direct-connect serial lines for communications,
such as optical fiber, a shorter polling period may be programmed, such as 15 minutes.
The ATMS software will poll each DMS for operational status, such as pixel failures, photocell
failures, message failures, fan failures, module failures and communications failures. Certain
types of failures are deemed to be severe, such as module failures and communication failures.
If a severe failure is detected, the GUI will turn that DMS icon red.
The ATMS software cannot diagnose the severity, number, or exact location of any failure. For
example, the ATMS software will note a pixel failure in its event logs, but cannot determine how
many pixels or which pixels have failed.
The ATMS software will also verify the message being displayed. If the message currently
displayed on the DMS does not match what the ATMS software believes it should be, the GUI
will turn that DMS icon red.
2.1.7.1 Selecting Messages
The ATMS software suggests a message for display on each DMS from its central library based
on current traffic conditions and any detected incidents. Operators must approve the suggested
message before the command to display that message is sent to the DMS. Operators may also
manually select a message from the central library to display on a DMS. The ATMS software
assigns priorities to operators, so messages sent by an operator with a higher priority will
“override” messages commanded by an operator with a lower priority.
The ATMS software provides tools for adding and editing messages in the central library. Users
may create new messages that are to be displayed on the sign from the workstation. Messages
may be text only and will support the basic ASCII character set (ASCII 30-126, inclusive), which
includes all the characters on the full keyboard set. All messages are checked by the ATMS
software for allowable words and that the message will fit on the DMS display (e.g., a 21-
character line message on a DMS display that can only fit 20 characters per line).
5
New York State ITS Standards Specification Development Guide
Only one font is currently available for each DMS. The ATMS software can support multiple
fonts for a DMS, but requires configuring the software.
The ATMS software currently limits all messages to two phases, but the limit can be adjusted.
Each phase can be programmed with a different page duration (amount of time the phase
appears before displaying the next phase). Each phase will be displayed for the user-defined
duration before the next phase is displayed. Once all the phase has been displayed, phase 1
will be displayed again. The default page duration is 2.0 seconds.
The ATMS software also defaults all messages to be center justified, both horizontal (left,
center, right justify) and vertical (top, center, bottom).
2.1.8 Activate Messages
Upon an operator commanding a message to be displayed on a DMS, the ATMS software will
download the message to the DMS controller, followed by a command to activate that message.
The ATMS software downloads every commanded message to the exact same message table
slot in the DMS controller and with the same priority. No other messages other than the
commanded message are downloaded to the DMS controller. Thus, the “old” commanded
message is always overwritten with the “new” commanded message.
2.2 Exception Operations
ATMS Software
Normally, the DMS will be monitored and controlled from the ATMS software at the AGENCY
STATEWIDE TOC. On occasion, situations may occur that requires control of the DMS be
transferred to some other party or software. These situations may include:
• For maintenance purposes – use of the manufacturer-provided software at the AGENCY
STATEWIDE TOC or a laptop at DMS controller
• For emergency use, such as communications loss from AGENCY STATEWIDE TOC –
use of the manufacturer-provided software at some other location, e.g., AGENCY, and
through a dialup modem
It is expected that when control of the DMS is transferred from the ATMS software at the
AGENCY STATEWIDE TOC to some other party or software, that proper operating procedures
will be followed. This includes properly informing the AGENCY STATEWIDE TOC that the
transfer of control is about to take effect, and when transfer of control is to be returned.
2.3 Control Modes
The DMS has three (3) modes of operation, Central, Local and Central Override. The mode of
operation determines the source that the sign will accept commands from.
2.3.1 Central Mode
In Central mode, the DMS sign will display only those messages that originate through the
CENTRAL communications port at the DMS controller. Commands through the CENTRAL
6