Module 14 - A311b

A311b: Specifying Requirements for DMS Systems Based on NTCIP 1203 Standard

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:

Slide 1: ITS Welcome - see the extended text description below

(Extended Text Description: Slide 1: 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” 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 are the words “RITA Intelligent Transportation Systems Joint Program Office.”)

 

Slide 2:

Welcome

Head shot photo of Shelley Row, P.E., PTOE - Director - ITS Joint Program Office

Shelley Row, P.E., PTOE

Director

ITS Joint Program Office

Shelley.Row@dot.gov

Screen capture snapshot of RITA website - for illustration only - see the extended text description below.

(Extended Text Description: Slide 2: Screen capture snapshot of RITA website - for illustration only. Below this image is a link to the current website: http://www.pcb.its.dot.gov - this screen capture snapshot shows an example from the RITA website from June 3, 2011. At the top of the page it shows the RITA logo with the text Research and Innovative Technology Administration - Intelligent Transportation Systems. Below the main site banner, it shows the main navigation menu with the following items: About RITA, Communities of Interest, Contact Us, Press Room, RITA Offices, Site Map, and a Search button. Below the main navigation menu, it shows a sub-navigation menu with the following items: About Us, T3 Webinars, ITS Peer-to-Peer, Resources, Local ITS PCB and Testimonials. Beneath the sub-navigation menu, the page is sub-titled "ITS Professional Capacity Building Program" and is divided into sub-sections such as "Welcome to ITS Professional Building", "News", "ITS Technical Assistance" and "Scheduled T3 Webinars". Again, this image serves for illustration only. The current website link is: http://www.pcb.its.dot.gov)

WWW.PCB.ITS.DOT.GOV

(Note: There is additional text attached to this slide that includes the following introductory information from Shelley Row):

"ITS Standards can make your life easier. Your procurements will go more smoothly and you’ll encourage competition, but only if you know how to write them into your specifications and test them. This module is one in a series that covers practical applications for acquiring and testing standards-based ITS systems.

I am Shelley Row the director of the ITS Joint Program Office for USDOT and I want to welcome you to our newly redesigned ITS standards training program of which this module is a part. We are pleased to be working with our partner, the Institute of Transportation Engineers, to deliver this new approach to training that combines web based modules with instructor interaction to bring the latest in ITS learning to busy professionals like you.

This combined approach allows interested professionals to schedule training at your convenience, without the need to travel. After you complete this training, we hope that you will tell colleagues and customers about the latest ITS standards and encourage them to take advantage of the archived version of the webinars.

ITS Standards training is one of the first offerings of our updated Professional Capacity Training Program. Through the PCB program we prepare professionals to adopt proven and emerging  ITS technologies that will make surface transportation safer, smarter and greener which improves livability for us all. You can find information on additional modules and training programs on our web site www.pcb.its.dot.gov.

Please help us make even more improvements to our training modules through the evaluation process. We look forward to hearing your comments. Thank you for participating and we hope you find this module helpful."

 

Slide 3:

A311b
Specifying Requirements for DMS Systems Based on NTCIP 1203 Standard

 

Slide 4:

Target Audience

 

Slide 5:

Instructor

Slide 5:  Instructor.  Headshot of instructor Patrick Chan, P.E. Senior Technical Staff, Consensus Systems Technologies (ConSysTec).

Patrick Chan
P.E. Senior Technical Staff
Consensus Systems Technologies (ConSysTec)
Flushing, NY
USA

 

Slide 6:

Recommended Prerequisites

 

Slide 7:

Curriculum Path (SEP)

Slide 7:  Curriculum Path (SEP).  Please see the Extended Text Description below.

(Extended Text Description: Slide 7: A chart showing the curriculum path for implementing a system that uses standards that are based on the systems engineering process. A linear box chart starting with I101 – Using Standards: An Overview with an arrow leading to A101 – Introduction to Acquiring Standards-based ITS Systems with an arrow leading to A102 – Introduction to User Needs Identification with an arrow leading to A201 – Details on Acquiring Standards-based ITS Systems with an arrow leading to Understanding User Needs (A311a NTCIP 1203, A313a NTCIP 1204 v03, A321a TMDD v3.0) with an arrow leading to A311b – Specifying Requirements for DMS Systems Based on NTCIP 1203 Standard.)

 

Slide 8:

Value of DMS Sequence

 

Slide 9:

Learning Objectives

  1. Discuss the structure of the standard
  2. Use the requirements traceability matrix (RTM) and protocol requirements list (PRL) to specify the standardized structure of requirements
  3. Include the requirements from the PRL and RTM in the specification
  4. Specify requirements not covered by the standard

 

Slide 10:

Learning Objective #1

Review of NTCIP 1203

What is NTCIP 1203?

Slide 10:  Review of NTCIP 1203. Please see the Extended Text Description below.

(Extended Text Description: Slide 10: A figure with a graphic depicting a computer, labeled a management station, with a line connected to a graphic depicting another computer, labeled a sign controller. The line between the management station and the sign controller is labeled “Subject of NTCIP”. The figure also contains a graphic of a dynamic message sign mounted on a gantry over a 3-lane roadway. There is a line connecting the dynamic message sign with the sign controller, and labeled “Comm Line between Sign Controller and Sign Housing (NOT covered by NTCIP)".)

 

Slide 11:

Learning Objective #1

Review of NTCIP 1203

What is NTCIP 1203?

 

Slide 12:

Slide 12:  Polling:  A placeholder graphic of hands raised to indicate polling activity.

 

Slide 13:

Poll

Please indicate if your agency has deployed dynamic message signs using standards before.

  1. Using NTCIP 1203 v01 DMS Standard
  2. Using NTCIP 1203 v02 DMS Standard
  3. Not using any DMS Standard
  4. Not sure

 

Slide 14:

Learning Objective #1

Review of NTCIP 1203

Comparison of Table of Contents

NTCIP 1203 v01

Section 1 General
Section 2 DMS Object Definitions
Section 3 MULTI
Section 4 Group Definitions
Section 5 Conformance Statements

NTCIP 1203 v02

Section 1 General
Section 2 Concept of Operations
Section 3 DMS Functional Requirements
Section 4 Dialogs
Section 5 Management Information Base
Section 6 MULTI
Annex A Requirements Traceability Matrix
Annex D Documentation of Revisions

 

Slide 15:

Learning Objective #1

Requirements in NTCIP 1203

What are Requirements?

 

Slide16:

Learning Objective #1

Requirements in NTCIP 1203 v02

 

Slide 17:

Learning Objective #1

Requirements in NTCIP 1203

Architectural Requirements

 

Slide 18:

Learning Objective #1

Requirements in NTCIP 1203

Data Exchange Requirements

 

Slide 19:

Learning Objective #1

Requirements in NTCIP 1203

Data Exchange Requirements

 

Slide 20:

Learning Objective #1

Requirements in NTCIP 1203

Data Exchange Requirements

 

Slide 21:

Learning Objective #1

Requirements in NTCIP 1203

Data Exchange Requirements

 

Slide 22:

Learning Objective #1

Requirements in NTCIP 1203

Supplemental Requirements

 

Slide 23:

Slide 23:  Activity.  A placeholder graphic of a hand typing on a computer keyboard indicating an activity.

 

Slide 24:

Learning Objective #2

Exercise

Which of the following requirements fulfill this user need?

This feature enables the operator to determine which component(s) of a subsystem are reporting errors and/or warnings so that the operator can plan a proper response.

  1. Monitor power errors
  2. Manage the exercise of pixels
  3. Manually control brightness

Type your answer in the chat pod

 

Slide 25:

Learning Objective #2

Protocol Requirements List (PRL)

Definition

 

Slide 26:

Learning Objective #2

Protocol Requirements List (PRL)

User Needs and Requirements

USER NEED SECTION NUMBER

USER NEED

FR SECTION NUMBER

FUNCTIONAL REQUIREMENT

CONFORMANCE

SUPPORT/ PROJECT REQUIREMENT

ADDITIONAL PROJECT REQUIREMENTS

2.5.3

Monitor the Status of the DMS

M

Yes

2.5.3.1

Perform Diagnostics

M

Yes

2.5.3.1.1

Determine Sign Error Conditions - High-Level Diagnostics

M

Yes

3.5.3.1.1.1 (LampTest)

Execute Lamp Testing

Lamp OR FiberM

Yes/NA

3.5.3.1.1.2 (PixelTest)

Activate Pixel Testing

Matrix:M

Yes/NA

3.5.3.1.1.3 (ClimateTest)

Execute Climate-Control Equipment Testing

O

Yes/No

3.5.3.1.2

Provide General DMS Error Status Information

M

Yes

 

Slide 27:

Learning Objective #2

Protocol Requirements List (PRL)

Conformance

USER NEED SECTION NUMBER

USER NEED

FR SECTION NUMBER

FUNCTIONAL REQUIREMENT

CONFORMANCE

SUPPORT/ PROJECT REQUIREMENT

ADDITIONAL PROJECT REQUIREMENTS

2.5.3

Monitor the Status of the DMS

M

Yes

2.5.3.1

Perform Diagnostics

M

Yes

2.5.3.1.1

Determine Sign Error Conditions - High-Level Diagnostics

M

Yes

3.5.3.1.1.1 (LampTest)

Execute Lamp Testing

Lamp OR FiberM

Yes/NA

3.5.3.1.1.2 (PixelTest)

Activate Pixel Testing

Matrix:M

Yes/NA

3.5.3.1.1.3 (ClimateTest)

Execute Climate-Control Equipment Testing

O

Yes/No

3.5.3.1.2

Provide General DMS Error Status Information

M

Yes

 

Slide 28:

Learning Objective #2

Protocol Requirements List (PRL)

Support / Project Requirement

USER NEED SECTION NUMBER

USER NEED

FR SECTION NUMBER

FUNCTIONAL REQUIREMENT

CONFORMANCE

SUPPORT 1 PROJECT REQUIREMENT

ADDITIONAL PROJECT REQUIREMENTS

2.5.1.4 (Graphics)

Manage Graphics

VMS:O

Yes/No/NA

3.5.1.4.1

Determine Maximum Number of Graphics

M

Yes

The DMS shall support at least      graphics.

3.5.1.4.2

Determine Maximum Graphic Size

M

Yes

The DMS shall support a maximum graphic size of      bytes.

3.5.1.4.3

Determine Available Graphics Memory

M

Yes

The DMS shall support a maximum graphic block size of      bytes.

 

Slide 29:

Learning Objective #2

Protocol Requirements List (PRL)

Additional Project Requirements

USER NEED SECTION NUMBER

USER NEED

FR SECTION NUMBER

FUNCTIONAL REQUIREMENT

CONFORMANCE

SUPPORT 1 PROJECT REQUIREMENT

ADDITIONAL PROJECT REQUIREMENTS

2.5.1.4 (Graphics)

Manage Graphics

VMS:O

Yes/No/NA

3.5.1.4.1

Determine Maximum Number of Graphics

M

Yes

The DMS shall support at least      graphics.

3.5.1.4.2

Determine Maximum Graphic Size

M

Yes

The DMS shall support a maximum graphic size of      bytes.

3.5.1.4.3

Determine Available Graphics Memory

M

Yes

The DMS shall support a maximum graphic block size of      bytes.

 

Slide 30:

Learning Objective #2

Protocol Requirements List (PRL)

Completing the PRL - Review

 

Slide 31:

Learning Objective #2

Protocol Requirements List (PRL)

Example

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

3.5.2.3.6

Activate a Message with Status

Drum:M

Yes/NA

3.6.5 t

Supplemental Requirements for Message Activation Request

M

Yes

3.6.7 t

Supplemental Requirements for Locally Stored Messages

M

Yes

(Additional Notes from the Author: Slide 31: The figure is a snapshot of a PRL table. The table headings are UN Section Number, User Need, FR Section Number, Functional Requirements, Conformance, Support / Project Requirement and Additional Project Requirements. On this slide, the first row is shaded dark, the UN Section Number is 2.5.2.3, the User Need is Control the Sign Face, the Conformance is M, and Support / Project Requirement is Yes circled in red. The second row is shaded light, the UN Section Number is 2.5.2.3.1, the User Need is Activate and Display a Message, the Conformance is M, and Support / Project Requirement is Yes circled in red. On the third row, the FR Section Number is 3.5.2.3.1, the Functional Requirement is Activate a Message, the Conformance is M, and the Support / Project Requirement is Yes circled in red. On the fourth row, the FR Section Number is 3.5.2.3.3.5, the Functional Requirement is Retrieve Message, the Conformance is M, and the Support / Project Requirement is Yes circled in red. On the fifth row, the FR Section Number is 3.5.2.3.6, the Functional Requirement is Activate a Message with Status, the Conformance is Drum:M, and the Support / Project Requirement is Yes / NA, with NA circled in red. On the sixth row, the FR Section Number is 3.6.5, the Functional Requirement is Supplemental Requirements for Message Activation Request, the Conformance is M, and the Support / Project Requirement is Yes circled in red. On the seventh row, the FR Section Number is 3.6.7, the Functional Requirement is Supplemental Requirements for Locally Stored Messages, the Conformance is M, and the Support / Project Requirement is Yes circled in red.)

 

Slide 32:

Slide 32: Polling. A placeholder graphic of  hands raised to indicate polling activity.

 

Slide 33:

Learning Objective #2

Poll Exercise

Which of the following elements is not a purpose of the PRL?

 

Slide 34:

Learning Objective #2

Requirements Traceability Matrix (RTM)

 

Slide 35:

Learning Objective #2

Requirements Traceability Matrix (RTM)

 

Slide 36:

Learning Objective #2

Requirements Traceability Matrix (RTM)

Requirements Traceability Matrix (RTM)

FR ID

Functional Requirement

Dialog ID

Object ID

Object Name

Additional Specifications

3.5

Data Exchange and Operational Environment Requirements

3.5.1

Manage the DMS Configuration

3.5.1.1

Identify DMS

3.5.1.1.1

Determine Sign Type and Technology

G.1

5.2.2

dmsSignType

5.2.9

dmsSignTechnology

 

Slide 37:

Learning Objective #2

Requirements Traceability Matrix (RTM)

Requirements Traceability Matrix (RTM)

FR ID

Functional Requirement

Dialog ID

Object ID

Object Name

Additional Specifications

3.5

Data Exchange and Operational Environment Requirements

3.5.1

Manage the DMS Configuration

3.5.1.1

Identify DMS

3.5.1.1.1

Determine Sign Type and Technology

G.1

5.2.2

dmsSignType

5.2.9

dmsSignTechnology

 

Slide 38:

Learning Objective #2

Requirements Traceability Matrix (RTM)

Example

Requirements Traceability Matrix (RTM)

FR ID

Functional Requirement

Dialog ID

Object ID

Object Name

Additional Specifications

3.5.2.3

Control the Sign Face

3.5.2.3.1

Activate a Message

4.2.3.1

5.7.3

dmsActivateMessage

5.11.2.1.1

shortErrorStatus

5.7.17

dms ActivateMsgError

5.7.24

dmsActivateErrorMsgCode

5.7.18

dmsMurtiSyntax Error

5.7.19

dmsMultiSyntaxErrorPosition

5.7.20

dmsMultiOtherErrorDescriptiori

 

Slide 39:

Learning Objective #2

Requirements Traceability Matrix (RTM)

Example 4.2.3.1 Activating a Message

The standardized dialog for a management station to activate a message on the sign display shall be as follows:

a. (Precondition) The management station shall ensure that the desired message is supported by the DMS. This may entail downloading the desired message contents to the DMS. (See Section 4.2.3.2.)

b. The management station shall SET dmsActivateMessage.0 to the desired value. This causes the controller to perform a consistency check on the message. (See Section 4.3.5 for a description of this consistency check.)

NOTE—dmsActivateMessage.0 is a structure that contains the following information: message type (permanent, changeable, blank, etc.), message number, duration, activation priority, a CRC of the message contents, and a network address of the requester.

 

Slide 40:

Learning Objective #2

Requirements Traceability Matrix (RTM)

Example

c. If the response indicates "noError," the message has been activated and the management station shall GET shortErrorStatus.0 to ensure that there are no errors preventing the display of the message (e.g., a "criticalTemperature" alarm). The management station may then exit the process.

d.  If the response from Step b) indicates an error, the message was not activated. The management station shall GET dmsActivateMsgError.0 and dmsActivateErrorMsgCode.0 to determine the type of error.

e.  If dmsActivateMsgError equals "syntaxMULTI," then the management station shall GET the following data to determine the error details:

  1. dmsMultiSyntaxError.0
  2. dmsMultiSyntaxErrorPosition.0

 

Slide 41:

Learning Objective #2

Requirements Traceability Matrix (RTM)

Example

Some dialogs are accompanied by an informative figure that provides a graphical depiction of the normative text.

Slide 41:  Requirements Traceability Matrix (RTM).  Please see the Extended Text Description below.

(Extended Text Description: Relevant descriptive information provided by author for this figure: Slide 41: Content notes as highlighted by the author. There is a figure on this slide showing a UML sequence diagram. This sequence shows the sequence of events to perform a GET operation, with a stick figure on the left representing the Management Station that issues the GET command. A box to the right represents the controller, which receives the command, processes it, assembles the response package, and sends it back to the requesting management station.)

 

Slide 42:

Learning Objective #2

Requirements Traceability Matrix (RTM)

 

Slide 43:

Slide 43: Polling.  A placeholder graphic of  hands raised to indicate polling activity.

 

Slide 44:

Learning Objective #2

Poll Exercise

Which of the following elements are not part of the RTM?

  1. User needs supported by the standard
  2. Requirements supported by the standard
  3. Standardized dialogs to fulfill requirements
  4. Data objects to fulfill requirements

 

Slide 45:

Learning Objective #3

Building the Project Specification

Slide 45:  Building the Project Specifications. Please see the Extended Text Description below.

(Extended Text Description: Slide 45: There is a figure depicting a box with the words, “Contract Documents”. Within this box are two other boxes, one box is labeled “Product Specifications”, and the other box is labeled “Contract Requirements”. Within the box labeled “Product Specifications” are three boxes, labeled “Hardware Specifications”, “Software Specifications”, and “Communication Interface Specifications”. The box labeled “Contract Requirements” consists of contractual requirements during system development, contractual requirements during testing, contractual requirements during deployment/integration, and contractual requirements during operations/maintenance. The box labeled “Hardware Specifications” consists of Functional Reqts., Performance Reqts., Structural Reqts., Mechanical Reqts., Electrical Reqts., and Environmental Reqts. The box labeled “Software Specifications” consists of Functional Reqts. And Performance Reqts. The box labeled “Communication Interface Specifications” consists of Functional Reqts., Performance Reqts., and Protocol Reqts.)

 

Slide 46:

Learning Objectives #2,3

Building the Project Specification

 

Slide 47:

Learning Objective #3

Building the Project Specification

3.2.4 Response Time

The SNMP agent shall process all requests in accordance with Section 3, including processing the request sufficiently to generate the transmission of the appropriate response (assuming that the SNMP agent has peimission to transmit) within the maximum Response Time. If the specification does not indicate the maximum Response Time, the maximum Response Time shall be 100 milliseconds plus one millisecond for each byte in the response variable-bindings field.

 

Slide 48:

Learning Objective #3

Building the Project Specification

 

Slide 49:

Learning Objective #4

Extensions

 

Slide 50:

Slide 50: Activity.  A placeholder graphic of a  hand typing on a computer keyboard indicating an activity.

 

Slide 51:

Learning Objective #4

Extensions - Activity about Benefits/Drawbacks

What do you think are the benefits and drawbacks associated with extensions (allowing and creating them) to the NTCIP standards?

Type answer in the chat pod

 

Slide 52:

Learning Objective #4

Extensions

Benefits

 

Slide 53:

Learning Objective #4

Extensions

Example

 

Slide 54:

Learning Objective #4

Extensions

Example

 

Slide 55:

Learning Objective #4

Extensions

Drawbacks

 

Slide 56:

Learning Objective #4

Extensions

Conformance

 

Slide 57:

Summary

 

Slide 58:

Summary

 

Slide 59:

Summary

 

Slide 60:

Resources

 

Slide 61:

Next Module

 

Slide 62:

Slide 62: Questions. A placeholder graphic of a  light bulb indicating questions.