Module 10 - A311a

A311a: Understanding User Needs for DMS Systems based on NTCIP 1203 Standard v03

HTML of the PowerPoint Presentation

(Note: This document has been converted from a PowerPoint presentation to 508-compliant HTML. The formatting has been adjusted for 508 compliance, but all the original text content is included, plus additional text descriptions for the images, photos and/or diagrams have been provided below.)

Slide 1:

(Extended Text Description: Author's relevant description: Welcome - Graphic image of introductory slide. A large dark blue rectangle with a wide, light grid pattern at the top half and bands of dark and lighter blue bands below. There is a white square ITS logo box with words "Standards ITS Training - Transit" in green and blue on the middle left side. The word "Welcome" in white is to the right of the logo. Under the logo box is the logo for the U.S. Department of Transpotation, Office of the Assistant Secretary for Research and Technology.)

Slide 2:

(Extended Text Description: Author's relevant description: This slide, entitled "Welcome" has a photo of Ken Leonard, Director, ITS Joint Program Office, on the left hand side, with his email address, Ken.Leonard@dot.gov. A screen capture snapshot of the home webpage is found on the right hand side - for illustration only - from August 2014. Below this image is a link to the current website: www.its.dot.gov/pcb - this screen capture snapshot shows an example from the Office of the Assistant Secretary for Research and Development - Intelligent Transportation Systems Joint Program Office - ITS Professional Capacity Building Program/Advanced ITS Education. Below the main site banner, it shows the main navigation menu with the following items: About, ITS Training, Knowledge Exchange, Technology Transfer, ITS in Academics, and Media Library. Below the main navigation menu, the page shows various content of the website, including a graphic image of professionals seated in a room during a training program. A text overlay has the text Welcome to ITS Professional Capacity Building. Additional content on the page includes a box entitled What's New and a section labeled Free Training. Again, this image serves for illustration only. The current website link is: https://www.its.dot.gov/pcb.)

Slide 3:

A311a: Understanding User Needs for DMS Systems based on NTCIP 1203 Standard v03

(Extended Text Description: Author's relevant description: The slide graphic includes an image of a Traffic Management Center from NYC DOT on the left side-an operator is looking at work station with DMS images. Another image is shown at top right corner that actually shows DMS messages with travel times in minutes. An image at right side bottom shows a DMS controller installed in the field with door open. The entire slide graphics together conveys the meaning and purpose of this module and what is expected from DMS deployments. )

Slide 4:

Instructor

Raman K. Patel Ph.D., P.E.

President

RK Patel Associates, Inc.

New York City, NY, USA

Slide 5:

Learning Objectives

• Review the structure of the DMS standard
• Identify specific DMS operational needs
• Describe the purpose of the Protocol Requirements List (PRL) matrix and benefits
• Discuss how to prepare a project level PRL with user needs and their associated requirements

Slide 6:

Learning Objective 1

• Review the structure of the DMS standard

Slide 7:

How This Standard Fits into the Family of NTCIP Standards

What Is a Dynamic Message Sign?

Dynamic Message Sign (DMS) is any sign system that can change the message presented to the viewer. --NTCIP 1203 v03 Standard

(Extended Text Description: Author's relevant description: What is a Dynamic Message sign? An image of a DMS sign with message appears at bottom of this slide.)

Source: FDOT

Slide 8:

How This Standard Fits into the Family of NTCIP Standards

(Extended Text Description: Author's relevant description: Major Components of a DMS System - An image of a DMS at right top is shown with an arrow showing the Housing portion of the sign and face. Another image at bottom shows a DMS controller with arrow pointing to the cabinet and controller. Together slide images explain major components of a DMS system.)

Slide 9:

How This Standard Fits into the Family of NTCIP Standards

NTCIP Framework

(Extended Text Description: Author's relevant description: How this standard fits into the family of NTCIP standards: NTCIP Framework: A graphic of the communication five levels of the NTCIP standards. On the right-side corner, there is a vertical text box that reads NTCIP 1203/NTCIP 1201 which points to Information Level Data Dictionaries and underneath arrow points to SNMP at Application level. This is shown to empathize where these standards are located. The next level is called the Application Level and includes C2C XML, DATEX, FTP, TFTP, SNMP, and STMP. The next level is called the Information Level and includes C2C Messages, Files, Data Objects, and Dynamic Objects. The next higher level is called the Subnetwork Level and includes PPP, Ethernet, and PMPP. The next level is called the Transport Level and includes TCP/IP, UDP/IP, and T2/NULL. These boxes are connected to an overarching box also in the Information Level labeled Functional Area Data Dictionaries with the left-hand side identifying C2C Data Dictionaries and the right-hand side labeled NTCIP Data Dictionaries. The bottom level, last level, is the Plant Level and includes boxes for Dial-up, Fiber, Coax, Wireless, Twisted Pair, and Leased Line.)

Slide 10:

Types of DMS and Technologies

DMS Characteristics Supported by the Standard

DMS Types

Capabilities the DMS offers for handling messages

DMS Technology

The technology that is used in the sign

DMS Display Matrix Configuration

The type of display layout employed by the sign

Slide 11:

Types of DMS and Technologies Examples

Blank-out Sign (BOS) One Message/Nothing

Source: ITE OET DMS-Patel

Changeable Message Sign (CMS), Predefined Messages

Source: ITE OET DMS-Patel

Variable Message Sign (VMS) Real-time Messages

Source: MNDOT

Slide 12:

Types of DMS and Technologies Examples

DMS Display Technologies

• Fiber Optic
• Light Emitting Diode (LED)
• Flip Disk or Shutter
• Lamp Matrix
• Drum (rotating, multifaceted cylinder)

Standard Supports all Display Technologies and Types-Matrix

(Extended Text Description: Author's relevant description: DMS Display Technologies Images of DMS signs are shown on right side to indicate Fiber optic and LED signs as examples.)

Slide 13:

Types of DMS and Technologies Examples

Display Surface Matrix Configurations

(Extended Text Description: Author's relevant description: Display Surface matrix Configurations Graphic on left side shows boxes of Full Matrix, Line Matrix and Character Matrix with layouts on right side. Graphic in middle shows Full matrix can display message anywhere on surface, line matrix can show separate lines with barrier and Character matrix displays letters with separate space.)

Slide 14:

Types of DMS and Technologies

How Messages are Organized and Displayed

(Extended Text Description: Author's relevant description: How Messages are Organized and Displayed - A sign in the field shows three-line message with arrows: first arrow indicates problem, followed by second line showing a Location and third line shows Action.)

Slide 15:

Types of DMS and Technologies

For Longer Messages, a Page is Added

Page is defined as the information that can fit on a sign at one time, together with its message attributes.

(Extended Text Description: Author's relevant description: For Longer Message, a Page is Added - A field map is shown with a DMS sign showing two pages of message: Page 1 shown with an arrow has three lines and Page 2 has three lines.)

Slide 16:

Types of DMS and Technologies

How a Message "Appears" on the Surface

Markup Language for Transportation Information (MULTI) is similar to HTML where text is transmitted,

and [tags define how the text appears-displayed]

(Extended Text Description: Author's relevant description: How a Message "Appears" on the Surface - A box shows three lines with MULTI message tags: Module, A311a Is and last line ABOUT DMS UN.)

Slide 17:

Structure of Standard (Sections)

Reference Architecture for DMS

(Extended Text Description: Author's relevant description: Reference Architecture for DMS Reference architecture is shown with a Management station connected to a DMS sign controller which in turn connects to the display sign housing.)

Slide 18:

Structure of Standard (Sections)

NTCIP 1203 v03 Documentation Organization (Part 1)

(Extended Text Description: This slide contains a stacked colored outline/index of the documentation with the following text:

Section 1 General

Section 2 Concept of Operations-User Needs

Section 3 Functional Requirements (Includes Protocol Requirements List-PRL)

Section 4 Dialogs

Section 5 Management Information Base (MIB)

Section 6 Markup Language for Transportation Information-MULTI

)

Slide 19:

Structure of Standard (Sections)

NTCIP 1203 v03 Documentation Organization (cont.)

(Extended Text Description: This slide shows the Annex sections of the documentation:

Part 1

Annex A Requirements Traceability Matrix (RTM)

Annex B Object Tree

Annex D Documentation of Revisions

Annex E Frequently Asked Questions

Annex F ASCII Table and Description

Annex G Simple Network Management Protocol (SNMP) Interface

Part 2

Annex C Test Procedures

)

Slide 20:

Structure of Standard (Sections)

What Is New in NTCIP 1203 v03 DMS Standard?

(Extended Text Description: Author's relevant description: What is new in NTCIP 1203 v03 Standard? On the left side three boxes shows v01, v02 and v03. On the right side a cover page of NTCIP 1203 1997 shown. v01 was published in 1997 Amended in 2001,Non-SEP based; v02 was published in 2007 Added new functionality, SEP-based; v03.03 was published in 2011 Annexes A, B, D-H Information Data Annex C: Added Test Procedures.)

Slide 21:

Structure of Standard (Sections)

What Is New in v03

• v03 added Test Procedures (Annex C)
• Made minor corrections (see Annex D)
• Published in Two Parts

Both versions are SEP based; provide User Needs/Requirements/Dialogs and PRL/RTM.

(Extended Text Description: Author's relevant description: What is New in v03? On the top a box shows NTCIP 1203 v03 connected to a bottom box showing NTCIP v02. NTCIP 1203 v03 Published 2011; Fully Compatible to v02; NTCIP 1203 v02 Published 2007.)

Slide 22:

Standard Structure (Sections)

What are user Needs?

• Standardized statements that describe what a DMS should do—features/functions
• Every user need has an Unique ID, provides a Major Desired Capability (MDC), has a rationale and it is solution-free

Slide 23:

Standard Structure (Sections)

Illustration of a DMS User Need

(Extended Text Description: Illustration of a DMS User Need - At the bottom two boxes are shown: first box on left has three lines, with arrow pointing to right side box with no message. The text above the two boxes reads:

2.5.2.3.4 Blank a Sign

This feature enables the operator (or logic within the management station) to remove any messages displayed on a sign (causing the sign to appear blank).

The text "2.5.2.3.4 Blank a Sign" points to Unique ID-Title; The text "remove any messages" points to MDC; The last line points to Rationale.)

Slide 24:

Standard Structure (Sections)

DMS User Needs Organization

2.4 Architectural Needs

2.4.1 Fundamental Needs

2.4.2 Operational Environment

2.4.2.1 Live Data Exchange

2.4.2.2 Logged Data Exchange

2.5 User Needs/Features

2.5.1 Manage the DMS Configuration

2.5.2 Control the DMS

2.5.3 Monitor the Status of the DMS

(Extended Text Description: Author's relevant description: DMS User Need Organization - At right a TMC with three people discussing something; at bottom, right a sign with three-line message is show connecting to TMC above. )

Source: FDOT Dist. 6

Slide 25:

Slide 26:

Question

Which of the following is a FALSE statement? Answer Choices

1. DMS Standard Contains SNMP Interface
2. DMS Standard Lacks Testing Documentation
3. DMS Standard Supports all Types of DMSs and Technologies
4. DMS Standard Includes Protocol Requirements List (PRL)

Slide 27:

Review of Answers

a) DMS Standard Contains SNMP interface
True statement. v03 provides SNMP interface in Annex G.

b) DMS Standard Lacks Testing Documentation
False statement. v03 provides test procedures in Annex C.

c) DMS Standard Supports all Types of DMSs and Technologies
True statement. Standard is independent of types of signs and technologies. It supports all.

d) DMS Standard Includes Protocol Requirements List (PRL)
True statement. v03 includes PRL in Section 3.

Slide 28:

Learning Objectives

• Review the structure of the DMS standard
• Identify specific DMS operational needs

Slide 29:

Learning Objective 2

• Identify specific DMS operational needs

Slide 30:

What Are You Trying to Do with a DMS System?

Concept of Operations (ConOPs)

• Communicates user needs and expectations for the proposed DMS system
• Provides an operational context of a DMS system

Fundamental Needs Driving DMS Deployment

"The provision of timely and reliable information to the traveling public improves public safety and convenience by providing advance notification of items that may be of interest (e.g., downstream road conditions or the arrival of a transit vehicle). DMS are typically dispersed along interstate highways, arterial roadways, and at transit stops." -NTCIP 1203 v03

Slide 31:

What Are You Trying to Do with a DMS System?

Example of ConOPs from Indiana DOT

"DMS provides dynamic operational information to motorists, including incident, traffic, and road condition information, emergency alerts, travel time information, and other advisories."

(Extended Text Description: Author's relevant description: Example of ConOps from Indiana DOT - At bottom an example of ConOps is shown with a DMS sign installed in the filed with vehicles passing on road and sign showing a three-line message.)

Slide 32:

What Are You Trying to Do with a DMS System?

Who Benefits from the Use of DMSs

Public Sector

• Achieve ITS objectives
• Safe and Efficient Mobility-Capacity
• Real-time Messages to Public

Road Users

• Obtain Visual Traffic Information
• Make Informed decisions

Private Sector

• Larger DMS Installed-base

Slide 33:

What Are You Trying to Do with a DMS System?

Operations Staff Use DMS System to Improve Operations

(Extended Text Description: Author's relevant description: Operations Staff Use DMS System to Improve Operations - A TMC photo on left is connected to three boxes on right side: Advisory Information, Regulatory Information and at bottom special Events Information. TMC Provides Real-time Traffic Information. Traveling Public Makes Decisions Based on Real-time Information.

Resulting in Improved:

• Traffic Flow
• Road Safety
• Environment
• Mobility Management

)

Slide 34:

What Are You Trying to Do with a DMS System?

Convey Advisory Information to the Traveling Public

Road Closures

Source: www.dot.ny.gov

Traffic Condition

Source: IN DOT

Slide 35:

What Are You Trying to Do with a DMS System?

Convey Advisory Information to the Traveling Public

Weather Warnings

Source: ntl.bts.gov

Curve Warning

Source: ODOT

Safety Benefits

Slide 36:

What Are You Trying to Do with a DMS System?

Convey Advisory Information to the Traveling Public:

Estimated Travel Times

(Extended Text Description: Author's relevant description: Convey Advisory Information to the Traveling Public - A DMS sign installed in the field shows a message that conveys advisory information-GCP 12 min etc.)

Source: NYSDOT

Slide 37:

What Are You Trying to Do with a DMS System?

Convey Advisory Information to the Traveling Public:

Transit Vehicle Arrival Times

(Extended Text Description: Author's relevant description: Convey Advisory Information to the Traveling Public - On left side: An image of a man standing on a Dupont Circle train station platform underneath a sign that shows train arrival times. On right two additional display signs show similar messages.)

Slide 38:

What Are You Trying to Do with a DMS System?

Convey Advisory Information to the Traveling Public:

HOV Lane Access Requirements

(Extended Text Description: Author's relevant description: Convey Advisory Information to the Traveling Public - A DMS sign conveys HOV lane access message. HOV lane is on left side of the roadway with a solid white lane and three lane traffic is moving on the right.)

Slide 39:

What Are You Trying to Do with a DMS System?

Convey Regulatory Information to the Traveling Public

• Mandatory detour information/evacuation
• Speed limits
• Variable Speed

(Extended Text Description: Author's relevant description: Convey Regulatory Information to the Traveling Public - Three signs convey Regulatory messages: Speed limits on left DMS image, one in middle shows a portable sign with Speed Ahead 30 MPH and on right displays Florida Keys evacuation underway message.)

Slide 40:

What Are You Trying to Do with a DMS System?

Convey Special Event Information to the Traveling Public

• High Value Information
• Require Urgent Attention

(Extended Text Description: Author's relevant description: Convey Special Event Information to the Traveling Public - The slide shows three DMSs with special event messages: One on left with High Value Information on Blasting 13 miles ahead; one in middle -All crossings to New York Closed and right most sign "New York City Closed to All Traffic".)

Slide 41:

What Are You Trying to Do with a DMS System?

Activate a Flashing Beacon to Draw Attention of Motorists

• Traffic Alert-Message Activation
• Change in Condition

Source: ITE

Source: Iowa DOT

Source: ops.fhwa.dot.gov

Source: WSDOT

Slide 42:

What Are You Trying to Do with a DMS System?

Manage Information from Multiple Facilities, Owning Centers

• Traffic Management Centers; Roadside, Moveable or Vehicle-based
• Transit platforms: Train Stations, Bus Depots
• Parking facility

Source: FHWA

Source: VDOT-Fairfax

Slide 43:

Support for Configuring/Monitoring and Controlling a Sign

Support Operational Environment with Communications Interface

(Extended Text Description: Author's relevant description: The slide illustrates Operational Environment with three images connected: a TMC on left side connects with a two-headed arrow to a sign controller which in turn is connected to a DMS Operation. Management Station, Architectural (Communications) Needs, Sign Controller, DMS Operation (Features): Configure Control Monitor.)

Slide 44:

Support for Configuring/Monitoring and Controlling a Sign

Support Operational Environment with Live Data Exchange

Connection Always ON:

Need to allow a management station to issue request for status and issue control commands to a DMS.

(Extended Text Description: Author's relevant description: Support Operational environment with Live Data exchange - The slide shows how the TMC is communicating with a sign with outbound arrow as Request for Status information, with inbound response arrow. Another set of arrows show a New message box on right side.)

Slide 45:

Support for Configuring/Monitoring and Controlling a Sign

Support Operational Environment with Logged-Data

When Connection is Broken or Using Dial-UP Connection:

Logged-Data is retrieved at later time when a broken connection is restored.

(Extended Text Description: Author's relevant description: Support Operational Environment with Logged Data exchange - Same as above (slide 44) except communication is to the DMS controller for logged data inquiry.)

Source: ITE OET DMS

Slide 46:

Support for Configuring/Monitoring and Controlling a Sign

Summary of Operational Needs Supported by the Standard?

1. Manage the DMS Configuration
2. Control the DMS
3. Monitor the Status of the DMS
4. Perform Diagnostics to the DMS System such as pixel testing

Slide 47:

Support for Configuring/Monitoring and Controlling a Sign

Managing the DMS Configuration

Determine the DMS Identity

(Extended Text Description: Author's relevant description: Managing the DMS Configuration - A regional map is shown on left side of the slide, with multiple single headed arrows pointing to DMS signs made by different manufacturers-located on map.)

Source: WSDOT

Slide 48:

Support for Configuring/Monitoring and Controlling a Sign

Managing the DMS Configuration (cont.)

• Manage Graphics
• Manage Fonts (color, height, width)
• Manage Brightness-LED (changing lighting conditions)
• Determine Sign Display Capabilities

(Extended Text Description: Author's relevant description: Managing the DMS Configuration (cont.) - A sign shows with I-95 logo on left and three-line message on right.)

Slide 49:

Support for Configuring/Monitoring and Controlling a Sign

Controlling the DMS

(Extended Text Description: Author's relevant description: Controlling the DMS - A layout is showing how a sign is controlled. TMC A on right side makes a request with a one-headed message to display a specific message to a TMC B on right side which owns a DMS sign their region. After taking an action to do so, TMC responds to TMC A with a response message. Additional details on major event near Exit 9 on line on I-87 highway is provide to show where a sigh is located and need for such as request to TMC B.)

Source: PCB-Patel

• Control the Sign Face
• Control External Devices
• Control the Brightness Outputs
• Remotely Reset the Sign Controller
• DMS Control by Multiple Locations Centers

Slide 50:

Support for Configuring/Monitoring and Controlling a Sign

Monitoring the Status of the DMS

(Extended Text Description: Author's relevant description: Monitoring the Status of the DMS - This slide brings up how we monitor a sign status and perform diagnostics. Four phots are used. A TMC on upper left corner is shown communicate with a DMS controller in the field that is connected to a DMS sign at left bottom with a message: travel time to... This message is confirmed at TMC software driven-display on workstation at TMC. This shows how a message is monitored at TMC with conformation.)

Slide 51:

Support for Configuring/Monitoring and Controlling a Sign

Performing Diagnostics to the DMS System

Test the Operational Status of System Components

• Determine Sign Error Conditions (High-Level Diagnostics)
• Monitor Message Errors
• Monitor Sign Environment

Source: Oregon DOT

Module/Driver Failure

Source: WSDOT

Slide 52:

Support for Configuring/Monitoring and Controlling a Sign

Performing Diagnostics to the DMS System (cont.)

(Extended Text Description: Author's relevant description: Performing Diagnostics to the DMS System (cont.) - Slide shows a testing desk on left with an operator sending message to a DMS sign controller on the right side.

Test the operational status of system components

• Monitor Door Status
• Monitor Controller Software Operations
• Monitor Power Source
• Monitor Power Voltage
• Pixel Status

)

Slide 53:

Support for Configuring/Monitoring and Controlling a Sign

What if a User Need is NOT Found in NTCIP 1203 v03?

• The standard allows for extensions
• Proprietary extensions are not desired
• Interoperability rests on standardized user needs; may be broken if a proprietary solution is imposed

Caution! Certain Automatic Actions are NOT supported

Slide 54:

Examples of DMS Operational Uses

Transportation Operations that Use DMSs

• Freeway Management
• Travel Information
• Incident Management
• Work Zone Management
• Traffic Control
• Parking Management

Source: www.roadtraffic-technology.com

Slide 55:

Examples of DMS Operational Uses

Transportation Operations that Use DMS (cont.)

• Route Diversion
• Evacuation
• Public Service & Safety
• Road Weather Information System

Warning on VMS boards gave drivers a chance to use alternate routes, helping to minimize the backup on northbound I-5.

Source: WSDOT TMC

Slide 56:

Examples of DMS Operational Uses

Key Outcomes from ITS Deployments (DMS)

• Improved Traffic Flow
• Coordinated Incident Management
• Reduced Travel Time
• Work Zones-Safety
• Speed Limits Enforcement

Source: FHWA OP

Source: City of Scottsdale

Slide 57:

Slide 58:

Question

Which of the following is NOT a DMS operational need?

Answer Choices

1. Management station remotely configures a DMS sign
2. Management station monitors and controls a DMS sign
3. Management station activates the beacon during an incident
4. Management requests current traffic flow data from the DMS controller

Slide 59:

Review of Answers

a) Management station remotely configures a DMS sign
True. This is a major DMS operational need. Management station configures a sign-type, location, direction, manufacture etc.

b) Management station monitors and controls a DMS sign
True. Management station remotely manages messages in realtime.

c) Management station activates the beacon during an incident
True. A beacon is activated to flash mode to make motorists aware of the current, perhaps urgent, message.

d) Management requests current traffic flow data from the DMS controller
False. DMS is a display device; it does not collect data such as traffic flow data.

Slide 60:

Learning Objectives

• Review the structure of the DMS standard
• Identify specific DMS operational needs
• Describe the purpose of the Protocol Requirements List (PRL) matrix and benefits

Slide 61:

Learning Objective 3

• Describe the purpose of the Protocol Requirements List (PRL) matrix and benefits

Slide 62:

What Is a PRL?

Protocol Requirements List (PRL) is a Table, a Matrix

• Provides the standardized relationship between user needs and their requirements
• As a template with fixed columns and multiple rows it guides users and DMS manufacturers/suppliers

USER NEED SECTION NUMBER	USER NEED	FR SECTION NUMBER	FUNCTIONAL REQUIREMENT	CONFORMANCE	SUPPORT/ PROJECT REQUIREMENT	ADDITIONAL PROJECT REQUIREMENTS
2.5	Features			M	Yes

Slide 63:

What Is a PRL?

Standardized Relationship Provided by the Standard

(Extended Text Description: Author's relevant description: Standardized Relationship Provided by the Standard - The slide depicts relationship of Requirements to user needs: One User Need connected to one Requirement with an arrow pointing left. Next one user need with arrow pointing to two requirements and finally Many user needs pointing to one user needs.)

Slide 64:

What is a PRL?

Provides Guidance

(Section 3.3, Page 31, Part 1)

• PRL template guides agency to select project user needs
• PRL then presents associated requirements to fulfill user needs 64

Agency completes the rows by entering selected user needs with associated requirements.

USER NEED SECTION NUMBER	USER NEED	FR SECTION NUMBER	FUNCTIONAL REQUIREMENT	CONFORMANCE	SUPPORT/ PROJECT REQUIREMENT	ADDITIONAL PROJECT REQUIREMENTS
2.5	Features			M	Yes

Agency completes the rows by entering selected user needs with associated requirements.

Slide 65:

Parts of PRL Provided in the Standard (Section 3.3)

User Need

(Extended Text Description: This slide contains the following text and table:

Parts of PRL Provided in the Standard (Section 3.3)

User Need

USER NEED SECTION NUMBER	USER NEED	FR SECTION NUMBER	FUNCTIONAL REQUIREMENT	CONFORMANCE	SUPPORT/ PROJECT REQUIREMENT	ADDITIONAL PROJECT REQUIREMENTS
2.5.1.2	Determine Sign Display Capabilities			0	Yes/No

The first column has a red arrow to the following text: 1^st line is the headings of the PRL Table (We cannot Modify Columns)

Determin Sign Display Capabilitiees has a ling to the following text: 2^nd line, an example of a user need, with section number-2.5.1.2 and its title

Section number 2.5.1.2, (page 25), find the user need; and determine if it is desired for your project implementation

)

Slide 66:

Parts of PRL Provided in the Standard (Section 3.3)

Determine if a User Need is Required

2.5.1.2 Determine Sign Display Capabilities

This feature allows the operator to retrieve the necessary information to produce a rendering of a suggested or active message. This feature also allows the system to ensure that a message can be displayed on the DMS. The feature allows the operator to determine the detailed physical limitations of the DMS as well as details regarding the current fonts and any graphics that are stored.

May be desired to provide a graphical rendering of how a DMS sign face may look like

May not be desired if a blank out sign (BOS) is procured

Slide 67:

Parts of PRL Provided in the Standard (Section 3.3)

Completing a Project PRL-Functional Requirements

(Extended Text Description: This slide contains the following table with the FR Section Number and Functional Requirement (FR) columns highlighted in red:

UN Section Number	User Need (UN)	FR Section Number	Functional Requirement (FR)	Conformance	Support/ Project Requirement	Additional Project Requirements
2.5.2.3.1	Activate and Display a Message			M	Yes
		35231	Activate a Message	M	Yes
		3.5.2.3.3.5	Retrieve Message	M	Yes
		35236	Activate a Message with Status	Drum M	Yes / NA

)

• Third/Fourth columns lists FR section number and title as described in Section 3.5 of the standard

Slide 68:

Parts of PRL Provided in the Standard (Section 3.3)

Conformance Column

(Extended Text Description: An arrow proceeds from the Conformance column of the following table to text below:

USER NEED SECTION NUMBER	USER NEED	FR SECTION NUMBER	FUNCTIONAL REQUIREMENT	CONFORMANCE	SUPPORT/ PROJECT REQUIREMENT	ADDITIONAL PROJECT REQUIREMENTS
2.5.1.2	Determine Sign Display Capabilities			0	Yes i No

)

• Identifies if the user need (or requirement) is Mandatory (M) or Optional (O)
• Certain basic user needs are considered Mandatory by the standard that must be selected YES

Example: DMS Matrix Configuration, must be selected (M)

Slide 69:

Parts of PRL Provided in the Standard (Section 3.3)

Conformance Column (cont.)

(Extended Text Description: Author's relevant description: Conformance Column (cont.) PRL table with three user needs are shown with entries in all columns. Last column has additional requirements. Text below has three arrows pointing to O means optional, 2 means three are two user needs, last arrow pointing to 1 in parenthesis, meaning at least 1 must be selected for conformance. The table is included below, along with the bulleted text:

UN Section Number	User Need (UN)	FR Section Number	Functional Requirement (FR)	Conformance	Support/ Project Requirement	Additional Project Requirements
2.3.2.3	DMS Display Matrix Configuration			M	Yes	The DMS shall be__millimeters wide (0..65535) and_millimeters high (0..65535). inclusive of borders. The Sign's Border shall be at least __millimeters wide (0..65535) and millimeters high (0..65535).
2.3.2.3.1	Non-Matrix			0.2(1)	Yes / No
23232 (Matrix)	Matrix			0.2(1)	Yes / No	The pitch between pixels shall be at least millimeters (0..255).

The designation means:

• This user need is optional (indicated by the 'O')
• The user need is one of several under the higher-level User Need (2.3.2.3 - DMS Display Matrix Configuration) (indicated by group '.2')
• One of the user needs selected under the higher-level user need must be selected (indicated by the (1)

)

Slide 70:

Parts of PRL Provided in the Standard (Section 3.3)

Conformance Column (cont.)

See page 32 of Standard for details

(Extended Text Description: Author's relevant description: This slide contains the following table and text. The VMS:O points to the Conformance column.

UN Section Number	User Need (UN)	FR Section Number	Functional Requirement (FR)	Conformance	Support/ Project Requirement	Additional Project Requirements
2.5.1.3 (Fonts)	Manage Fonts			VMS:O	Yes / No / NA

Predicate - <predicate>: Indicates whether this user need is mandatory, optional or applicable, and is dependent on a condition or another feature is supported

• E.g., for Manage Fonts, VMS:O indicates if the DMS is a variable message sign, the user need is optional
• Other conditions or features include type of DMS (BOS, CMS; requires no font management)-NA

)

Slide 71:

Parts of PRL Provided in the Standard (Section 3.3)

Support/Project Requirement Column

(Extended Text Description: The following table has the words Yes/No circled in red and pointing the bulleted text below:

USER NEED SECTION NUMBER	USER NEED	FR SECTION NUMBER	FUNCTIONAL REQUIREMENT	CONFORMANCE	SUPPORT/ PROJECT REQUIREMENT	ADDITIONAL PROJECT REQUIREMENTS
2.5.1.2	Determine Sign Display Capabilities			0	Yes / No

Agency/Specifier circles Yes, No or NA to indicate the agency's user needs for the proposed implementation.

• If the Conformance statement for the User Need is Mandatory, you must circle Yes.
• If the Conformance statement is not applicable for your implementation, circle (write) NA.

)

Slide 72:

Parts of PRL Provided in the Standard (Section 3.3)

(Extended Text Description: Author's relevant description: Additional Project Requirements-Last Column - A populated PRL is shown with requirements to a blank in last column text. A software Menu is shown at right bottom corner where a page is pointed. Illustrates How many Pages you need, must be stated in last column Blank space. One? Two?

Additional Project Requirements-Last Column

• Provides additional notes or requirements (implementation)

USER NEED SECTION NUMBER	USER NEED	FR SECTION NUMBER	FUNCTIONAL REQUIREMENT	CONFORMANCE	SUPPORT/ PROJECT REQUIREMENT	ADDITIONAL PROJECT REQUIREMENTS
		H.2.1	Determine Device Component Information	M	Yes
		H.2.4	Determine Supported Standards	M	Yes
2.5.1.2	Determine Sign Display Capabilities			0	Yes / No
		3.5.1.2.1.1	Determine the Size of the Sign Face	M	Yes
		3.5.1.2.3.1	Determine Maximum Number of Pages	VMS:M	Yes / NA	The DMS shall support at least ____ (1..255) paaes for a sinqle message.

)

Slide 73:

Parts of PRL Provided in the Standard (Section 3.3)

(Extended Text Description: Author's relevant description: Parts of PRL Provided in the Standard (Section 3.3). The Support/Project Requirement cells are highlighted in the table below:

Agency Prepares a Customized Project PRL by selecting YES for Support

USER NEED SECTION NUMBER	USER NEED	FR SECTION NUMBER	FUNCTIONAL REQUIREMENT	CONFORMANCE	SUPPORT/ PROJECT REQUIREMENT	ADDITIONAL PROJECT REQUIREMENTS
2.5	Features			M	Yes
2.5.1	Manage the DMS Configuration			M	Yes
2.5.1.1	Determine the DMS Identity			M	Yes
		3.6.1.1.1	Determine Sign Type and Technology	M	Yes
		H.2.1	Determine Device Component Information	M	Yes
		H.2.4	Determine Supported Standards	M	Yes
2.5.1.2	Determine Sign Display Capabilities			0	Yes / No
		3.5.1.2.1.1	Determine the Size of the Sign Face	M	Yes
2.5.3.1.5 (Environment)	Monitor Sign Environment			o	Yes / No
		3.5.3.1.4.7	Monitor Sign Housing Temperatures	M	Yes
		3.5.3.1.4.3	Monitor Sign Housing Humidity	O	Yes / No
		3.5.3.1.4.9	Monitor Control Cabinet Temperatures	o	Yes / No
		3.5.3.1.4.10	Monitor Control Cabinet Humidity	o	Yes / No
		3.5.3.1.7	Monitor Ambient Environment	Temp:M	Yes / NA

)

Slide 74:

Benefits of PRL to Stakeholders

Agency Perspective (Project PRL)

• "Communicates" the scope of the desired DMS communication interface
• Makes it easier to specify what the interface is to do (customize)
• "Spells out" conformance requirements
• Acts as a "checklist" to validate the built system
• Aids in achieving interoperability

Did they build RIGHT system?

Slide 75:

Benefits of PRL to Stakeholders

Vendors/System Developers Perspective

• Everyone is "connected" on the same page
• Eliminates "ambiguity"- reduces risks
• Vendors "confirms" DMS functionality + offer optional features

With a completed PRL, your agency, your vendors, system developers, all parties know what is expected from the DMS implementation.

Slide 76:

Slide 77:

Question

Which of the following is NOT a correct statement?

Answer Choices

1. PRL is used to ensure conformance to the standard
2. PRL only identifies mandatory user needs/requirements
3. PRL is used as a validation checklist
4. PRL may be used to provide additional notes

Slide 78:

Review of Answers

a) PRL is used to ensure conformance to the standard
True. The statement is valid; we do use PRL to ensure Conformance to the standard.

b) PRL only identifies Mandatory user needs/requirements
False. The statement is invalid; PRL also allows agency to select optional user needs and associated requirements, in addition to mandatory ones.

c) PRL is used as a validation checklist
True. PRL helps in validating user needs-Right system being built.

d) PRL may be used to provide additional notes
True, Last column of a PRL allows users to make special comments if required.

Slide 79:

Learning Objectives

• Review the structure of the DMS standard
• Identify specific DMS operational needs
• Describe the purpose of the Protocol Requirements List (PRL) matrix and benefits
• Discuss how to prepare a project level PRL with user needs and their associated requirements

Slide 80:

Learning Objective 4

• Discuss how to prepare a project level PRL with user needs and their associated requirements

Slide 81:

How PRL Fits into the DMS Specification

(Extended Text Description: Author's relevant description: Procurement Contract Specifications - At bottom, right a DMS is shown pointing to sign controller and a TMC Talking to DMS controller. An arrow points to a text box on upper right side. Procurement Contract Specifications text:

1 - Hardware Specifications

Functional Req.
Performance Req.
Structural Req.
Mechanical Req.
Electrical Req.
Environmental Req.

2 - Software Specifications

Functional Req.
Performance Req.

Contractual requirements during:

• System development
• Testing
• Deployment/integration
• Operations/maintenance
• Project management

3 - Communications Interface Specifications

User Needs
Functional Req.
Project PRL, RTM
Testing Documentation

DMS INTERFACE

SPECIFICATION

PRL)

Slide 82:

Review Steps (Tailoring) to Select User Needs and Associated Requirements

Key Points for Completing a Project PRL

(Extended Text Description: Author's relevant description: Key Points to Completing a Project PRL - Three text boxes are shown connected to PRL table on right side. A text box from top also connects to the PRL: Boxws with text point to an example table: Your DMS Specification Must have a fully completed PRL; PRL must be consistent with the hardware specification; Example: Temperature gauge, LED or Fiber Optic signs; PRL must be based on the NTCIP 1203 v03 with SNMP Interface; Include Need-based specific DMS parameters-NOT All YOU Can GET! Not a Wish list; Your DMS Specification Must have a fully completed PRL.)

Slide 83:

Review Steps (Tailoring) to Select User Needs and Associated Requirements

Conformance Versus Compliance

• Conformance: Meets a specified standard
  • To claim "Conformance" to NTCIP 1203 v03, the vendor shall minimally satisfy the mandatory requirements selected (YES)
  • Vendors that provide additional features beyond the completed PRL are still conformant as long as they conform with the requirements of NTCIP 1203 v03 and its normative references
• Compliance: Meets an agency specification

Slide 84:

Complete Project PRL with Entries (Populating Table)

Fill-in PRL with User Needs/Requirements

(Extended Text Description: This slide contains the following table with the Support/Project Requirement column highlighted and the word Yes circled in red on the first row:

USER NEED SECTION NUMBER	USER NEED	FR SECTION NUMBER	FUNCTIONAL REQUIREMENT	CONFORMANCE	SUPPORT/ PROJECT REQUIREMENT	ADDITIONAL PROJECT REQUIREMENTS
2.5.3.1.5 (Environment)	Monitor Sign Environment			0	Yes/No
		3.5.3.1.4.7	Monitor Sign Housing Temperatures	M	Yes
		3.5.3.1.4.3	Monitor Sign Housing Humidity	0	Yes/No
		3.5.3.1.4.9	Monitor Control Cabinet Temperatures	0	Yes/No
		3.5.3.1.4.10	Monitor Control Cabinet Humidity	0	Yes/No
		3.5.3.1.7	Monitor Ambient Environment	Temp:M	Yes/NA

)

• Use the Support/Project Requirement column to indicate if the user need is required for the implementation
• If the YES is selected, the requirements associated with that user need are also selected

Slide 85:

Commonly Used DMS User Needs in PRL

Fill-in PRL with User Needs/Requirements

(Extended Text Description: This slide contains the following tables with the Conformance column highlighted and the word Yes circled in red on the first row:

USER NEED SECTION NUMBER	USER NEED	FR SECTION NUMBER	FUNCTIONAL REQUIREMENT	CONFORMANCE	SUPPORT/ PROJECT REQUIREMENT	ADDITIONAL PROJECT REQUIREMENTS
2.4.2	Operational Environment M				Yes
2.4.2.1	Live Data Exchange			M	Yes
		3.4.1.1	Retrieve Data	M	Yes
		3.4.1.2	Deliver Data	M	Yes
		3.4.1.3	Explore Data	M	Yes
		3.4.4.1	Determine Current Access Settings	M	Yes
		3.4.4.2	Configure Access	M	Yes	The DMS shall support at least access levels in addition to the administrator.

DMS Specification MUST Select [YES] these User Needs and associated Requirements; First Step to Achieving Interoperability.

2.5	Features			M	Yes
2.5.1	Manage the DMS Configuration			M	Yes
2.5.1.1	Determine the DMS Identity			M	Yes
		3.5.1.1.1	Determine Sign Type and Technology	M	Yes

)

Slide 86:

Commonly Used DMS User Needs in PRL

Fill-in PRL with User Needs/Requirements

(Extended Text Description: This slide contains the following tables with the Conformance column highlighted and the word Yes circled in red on the first row:

USER NEED SECTION NUMBER	USER NEED	FR SECTION NUMBER	FUNCTIONAL REQUIREMENT	CONFORMANCE	SUPPORT/ PROJECT REQUIREMENT	ADDITIONAL PROJECT REQUIREMENTS
2.5.2.3	Control the Sign Face			M	Yes
2.5.2.3.1	Activate and Display a Message			M	Yes
		3.5.2.3.1	Activate a Message	M	Yes
		3.5.2.3.3.5	Retrieve Message	M	Yes

Specification Must selects YES.

2.5 3.1.8 (Door)	Monitor Door Status			0	Yes /No
		3.5 3 1 3.10	Monitor Door Status	M	Yes

Specification selects YES, if Door status is monitored.)

Slide 87:

Commonly Used DMS User Needs in PRL

(Extended Text Description: This slide contains the following tables with the Conformance column highlighted and the word Yes circled in red on the first row, then with an arrow pointing down the text below:

Commonly Used DMS User Needs in PRL

USER NEED SECTION NUMBER	USER NEED	FR SECTION NUMBER	FUNCTIONAL REQUIREMENT	CONFORMANCE	SUPPORT/ PROJECT REQUIREMENT	ADDITIONAL PROJECT REQUIREMENTS
2.5.2	Control the DMS			M	Yes
2.5.2.1	Control a DMS from More than One Location			M	Yes
		3.5.2.1	Manage Control Source	M	Yes
		3.6.4 t	Supplemental Requirements for Control Modes	M	Yes

2.5.2.1 Control a DMS from More than One Location

This feature addresses the need for DMS to be controlled both remotely (e.g., from one or more central computers) and locally (e.g., from the controller directly or from a laptop computer connected to the controller).

In summary, PRL has all your user needs and associated requirements-all in ONE place-together with solid relationship.)

Slide 88:

Slide 89:

Question

Which of the following is a FALSE statement related to a DMS specification?

Answer Choices

1. DMS specification includes a PRL
2. Conformance requires only meeting mandatory user needs
3. Compliance requires only mandatory user needs
4. Vendor must use the project PRL

Slide 90:

Review of Answers

a) DMS specification includes a PRL
True. The statement is true; PRL must be in every DMS specification.

b) Conformance requires only mandatory user needs
True. The statement is true; only Mandatory user needs must be met to conform to the DMS standard.

c) Compliance requires only meeting mandatory user needs
False. The vendor must meet mandatory and selected optional user needs for compliance to specification. (33)

d) Vendor must use the project PRL
True. The statement is true; the vendor must use agency PRL.

Slide 91:

Module Summary

• Review the structure of the DMS standard
• Identify specific DMS operational needs
• Describe the purpose of the Protocol Requirements List (PRL) matrix and benefits
• Discuss how to prepare a project level PRL with user needs and their associated requirements

Slide 92:

We Have Now Completed A311a in the DMS Curriculum

Module A311a:
Understanding User Needs for DMS Systems based on NTCIP 1203 Standard v03

Module A311b:
Specifying Requirements for DMS Systems based on NTCIP 1203 Standard v03

Module T311:
Applying Your Test Plan to the NTCIP 1203 v03 DMS Standard

Slide 93:

Next Course Module

Module A311b: Specifying Requirements for NTCIP 1203 v03 DMS Standard

Concepts taught in next module (Learning Objectives):

1. Briefly review the structure of the DMS Standard
2. Explain the purpose of requirements traceability matrix (RTM) and its benefits
3. Prepare a project-level RTM with standard supplied requirements and design content (concepts)
4. Prepare a DMS specification (check list)

Slide 94:

Thank you for completing this module.

Feedback

Please use the Feedback link below to provide us with your thoughts and comments about the value of the training.

Thank you!