Module 11 - A313a

A313a: Understanding User Needs for ESS Systems Based on NTCIP 1204 v03 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:

A313a: Understanding User Needs for ESS Systems Based on NTCIP 1204 v03 Standard

 

Slide 4:

Target Audience

 

Slide 5:

Instructor

Head shot photo of the instructor, Kenneth Vaughan, P.E.

Ken Vaughn, P.E.

President
Trevilon Corporation
Herndon, VA, USA

Course Developer: Joerg 'Nu' Rosenbohm

 

Slide 6:

Recommended Prerequisites

 

Slide 7:

Curriculum Path (SEP)

Curriculum Path (SEP) Flowchart. Please See extended text description below.

(Extended Text Description: A graphical illustration indicating the sequence of training modules for the standards related to specifying environmental sensor stations (ESS). Each module is represented by a box with the name of the module in it and an arrow showing the logical flow of the modules and the current module highlighted. The first box is labeled “I101 Using ITS Standards: An Overview.” An arrow from this box connects it to a highlighted box labeled “A101 Introduction to Acquiring Standards-based ITS Systems,” representing this module. An arrow from this box connects it to a box labeled “A102 Introduction to User Needs Identification.” An arrow from this box connects it to a box located at the start of the next line labeled “A201 Details on Acquiring Standards-based ITS Systems.” An arrow from this box connects it to a box labeled “A313a Understanding User Needs for ESS Systems Based on NTCIP 1204 v03 Standard.” Finally, an arrow from this box connects it to a box labeled “Specifying Requirements - A311b-A321b.”)

 

Slide 8:

Value of ESS Path Sequence

 

Slide 9:

Learning Objectives

  1. Understand the structure of the standard
  2. Identify specific ESS operational needs
  3. Use the Protocol Requirements List (PRL) to select the user needs and link to requirements
  4. Explain how the PRL fits into an ESS specification

 

Slide 10:

Module Outline

 

Slide 11:

Learning Objective #1

NTCIP Family

NTCIP diagram. Please see extended text description below.

(Extended Text Description: Relevant descriptive information provided by author for this figure: A graphic of the communication levels of the NTCIP standards. The bottom level is the Plant Level and includes boxes for Dial-up, Fiber, Coax, Wireless, Twisted Pair, and Leased Line. 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. 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. 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 NTCIP Data Dictionaries is highlighted with a circle indicating that it is the subject of the NTCIP 1204 v03 standard. )

 

Slide 12:

Learning Objective #1

What is NTCIP 1204?

 

Slide 13:

Learning Objective #1

History of NTCIP 1204

 

Slide 14:

Learning Objective #1

Structure of the Standard

 

Slide 15:

Learning Objective #1

Structure of the Standard (Cont.)

Table of Contents

Section 1 General
Section 2 Concept of Operations
Section 3 Functional Requirements
Section 4 Dialogs
Section 5 Object Definitions (Management Information Base)
Annex A Requirements Traceability Matrix (RTM)
Annex B Object Tree
Annex C Test Procedures
Annex D Documentation of Revisions
Annex E User Requests
Annex F Generic Clauses
Annex G Encoding of Sample Block Objects
Annex H Controller Configuration Objects

 

Slide 16:

Learning Objective #1

Advantages of NTCIP 1204 v3

 

Slide 17:

Learning Objective #2

Concept of Operations

 

Slide 18:

Learning Objective #2

Primary Uses of ESS Data

 

Slide 19:

Learning Objective #2

Primary Uses of ESS Data (Cont.)

 

Slide 20:

A placeholder graphic of a hand typing on a computer keyboard indicating an activity.

 

Slide 21:

Exercise #1

Question 1: What is the purpose of the Systems Engineering Process?

Answer: It provides a structured and reproducible approach to designing, creating, testing, and ending a system with check points at each various stage to ensure the system will deliver what is needed.

Type answers in the chat pod

 

Slide 22:

Exercise #1

Question 2: What is the purpose of the Concept of Operations?

Answer: To define the Why and What of a system via definition of the User Needs and selection of User Needs by the system designer.

Type answers in the chat pod

 

Slide 23:

Learning Objective #2

User Needs - Basics

 

Slide 24:

Learning Objective #2

NTCIP 1204 v03 User Needs Overview

 

Slide 25:

Learning Objective #2

NTCIP 1204 v03 User Needs Overview (Cont.)

NTCIP User Needs Overview. Please See extended text description below.

(Extended Text Description: Relevant descriptive information provided by author for this figure: A graphic depicting the connections among various components. The Management Station is connected to the ESS, and this connection is the subject of the NTCIP standards. The ESS itself consists of multiple components which may include various sensors, a sprayer, a chemical tank, and a controller. The controller can be logically divided into an ESS Manager, a Sensor Manager, and a Pavement Treatment System (PTS) Manager.)

 

Slide 26:

Learning Objective #2

NTCIP 1204 v03 - Physical Architectural Needs Sample Physical Architectures

 

Slide 27:

Learning Objective #2

NTCIP 1204 v03 - Physical Architectural Needs Sequence Diagram for "Provide Live Data"

Physical Architectural Needs Sequence Diagram for Provide Live Data. Please See extended text description below.

(Extended Text Description: Relevant descriptive information provided by author for this figure: Physical Architectural Needs Sequence Diagram for Provide Live Data. Bullet items as follows, poiting to three graphic diagrams: Provide Live Data, GET, SET, GET-NEXT pointing to three graphics depicting sample dialogs shown as UML sequence diagrams. In each case, the Management Station sends a message to the Controller, either a Get, GetNext, or Set. In all three cases, the Controller responds with a GetResponse message. Bullet item at bottom of slide: Basic command set to manage an ESS.)

 

Slide 28:

Learning Objective #2

NTCIP 1204 v03 - Physical Architectural Needs "Provide Compressed Data"

 

Slide 29:

Learning Objective #2

NTCIP 1204 v03 - Physical Architectural Needs "Provide Off-Line Log Data"

 

Slide 30:

Learning Objective #2

NTCIP 1204 v03 - Operational Needs "Features"

 

Slide 31:

Learning Objective #2

NTCIP 1204 v03 - Operational Needs ESS Manager Needs

 

Slide 32:

Learning Objective #2

NTCIP 1204 v03 Operational Needs Sensor Manager Needs

 

Slide 33:

Learning Objective #2

NTCIP 1204 v03 Operational Needs

Pavement Treatment System Manager Needs

 

Slide 34:

A placeholder graphic of hands raised to indicate polling activity.

 

Slide 35:

POLL: NTCIP 1204 v03 Operational Needs

What if a user need is not supported by the standard?

Student to select correct answers:

Graphic image of a checkmarkThe standard, like the entire suite of NTCIP protocols, allows for extensions

Graphic image of a checkmarkProprietary extensions are not desired (interoperability problems) but sometimes necessary

Graphic image of a checkmarkProprietary extensions might become part of a future version of the standard

Graphic image of a checkmarkThe standard supports interoperability for all contained features

 

Slide 36:

Learning Objective #3

Protocol Requirements List (PRL) -

Definition

 

Slide 37:

Learning Objective #3

PRL - Addressing User Needs

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Retirement

Additional Project Requirements

2.5.2.1 (Weather)

Monitor Weather Conditions

0.2(1..*)

Yes / No / NA

(Additional notes for this slide: Arrows lead from the bullet items as follows: "User Need Section Number - Section Number of the user need" points to the User Need ID column, and "User Need (UN) - Title (description of the user need)" points to the User Need Column)

 

Slide 38:

Learning Objective #3

PRL - Addressing User Needs (Cont.)

2.5.1.2 Monitor Door Status

A transportation system operator may wish to determine if any doors on the ESS equipment are open: this may assist the operator in determining whether maintenance crews have properly secured the controller after maintenance and/or may act as an indication to the system to treat any data as suspect.

 

Slide 39:

Learning Objective #3

PRL - Conformance

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Recuirernent

Additional Project Requirements

2.5.2.1 (Weather)

Monitor Weather Conditions

0.2(1..*)

Yes / No / NA

(Additional notes for this slide: An arrow points from the word "Conformance" to the Conformance column in the table above.)

 

Slide 40:

A placeholder graphic of a hand typing on a computer keyboard indicating an activity.

 

Slide 41:

Activity - User Needs

Answer: Did you find all six (6)?

2.5.2.1 - Monitor Weather Conditions
2.5.2.2 - Monitor Pavement
2.5.2.3 - Monitor Subsurface Conditions
2.5.2.4 - Monitor Human Readings
2.5.2.5 - Monitor Water Level
2.5.2.6 - Monitor Air Quality and Biohazards

Type answers in the chat pod

 

Slide 42:

Learning Objective #3

PRL - Conformance (Cont.)

 

Slide 43:

A placeholder graphic of a hand typing on a computer keyboard indicating an activity.

 

Slide 44:

Activity - User Needs Conformance

User Need ID

User Need FR ID Functional Requirement

Conformance

Project Requirement

2A

Architectural Meeds

M

Yes

2.4.1

Generic Architectural Needs

M

Yes

2.5

Features

M

Yes

2.5.1

ESS Manager Features

M

Yes

2.5.1.1

Generic Fea:ures

M

Yes

2.5.2.2 (Pavement)

Monitor Pavement

0.2 (1..*)

Yes / No / NA

2.5.2.2.1

Monitor Pavement Surface Condition

M

Yes / NA

2.5.3

Pavement Treatment System Manager Features

0.1 (1..*)

Yes / No / NA

2.5.3.1

2.5.3.2

Manage Stationary Spray System

Manage Mobile Spray System

Mobile :X; M

Mobile: M

Yes / No / NA

Yes / No / NA

F.1.1

Yes

F.1.1.1 (ESS)

Provide Live Da:a

M

Yes

F.1.2

Yes

F. 1.2.1

Retrieve the Device Identity

Yes

See, not that many!

See Supplement pages 4 and 5, PRL Table - use chat pod

 

Slide 45:

Learning Objective #3

User Needs Selection Relationship

(Pavement)

Monitor Pavement

0.2 (1..*)

NA

2.5.2.2.1

Monitor Pavement Surface Condition

M

Yes / NA

 

Slide 46:

A placeholder graphic of hands raised to indicate polling activity.

 

Slide 47:

Learning Objective #3

PRL - User Needs - Project Requirements Relationship

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirernent

Additional Project Requirements

2.5.2.1 (Weather)

Monitor Weather Conditions

0.2(1..*)

Yes / No / NA

Question: What is the Project Requirement value for a Mandatory User Need?

Answer: A value of "Yes" (versus a value of "Yes/No" or "NA")

(Additional notes for this slide: An arrow points from the text "Support/Project Requirement" to the Project Requirement column in the table above.)

 

Slide 48:

A placeholder graphic of a hand typing on a computer keyboard indicating an activity.

 

Slide 49:

Exercise #2 - User Needs

Yes, User Needs are to monitor and report back temperature, wind, surface, visibility, and subsurface readings

Type answers in the chat pod

 

Slide 50:

Exercise #2 - User Needs

2.5.2.1.2 - Monitor Winds
2.5.2.1.3 - Monitor Temperature
2.5.2.1.7 - Monitor Visibility
2.5.2.2.1 - Monitor Pavement Surface Condition
2.5.2.3 - Monitor Subsurface Conditions

 

Slide 51:

Learning Objective #3

Importance of PRL - User Needs - FR Relationship

 

Slide 52:

Learning Objective #3

PRL - User Needs - Functional Requirements (FR) Relationship

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

2.5.1.3

Monitor Power

O

Yes / No

3.5.1.2.2

Retrieve Battery Status

0.6(1..*)

Yes / No / NA

3.5.1.2.3

Retrieve Line Volts

0.6(1..*)

Yes / No / NA

(Additional notes for this slide: Arrows lead from the bullet items as follows: "Functional Requirement Identifier" points to the FR ID column, and "Functional Requirement" points to the Functional Requirement Column)

 

Slide 53:

Learning Objective #3

PRL - User Needs - FR Relationship (Cont.)

 

Slide 54:

Learning Objective #3

Using the PRL

User Need ID

User Need

FRID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

2.4

Architectural Needs

M

Yes

2.4.1

Generic Architectural Needs

M

Yes

(See F.1.1)

2.5

Features

Yes

2.5.1

Yes

2.5.1.1

Generic Features

M

Yes

(See F.1.2)

2.5.1.2 Monitor Door Status 0 Yes / No  

3.5.1.2.1

Retrieve ESS Door Status

M

Yes / NA

2.5.1.3

Monitor Power

0

Yes / No

3.5.1.2.2

Retrieve Battery Status

0.6(1..*)

Yes / No / NA

3.5.1.2.3

Retrieve Line Volts

0.6(1..*)

Yes / No / NA

2.5.1.4

Monitor Mobile Station Data

Mobile:M

Yes / NA

3.5.1.3.1

Retrieve Mobile ESS Movement

M

Yes / NA

3.5.1.3.3

Retrieve Compressed Mobile Station Data

M

Yes / NA

 

Slide 55:

Learning Objective #3

PRL - Functional Requirements (FR)

(Cont.)

 

Slide 56:

A placeholder graphic of a hand typing on a computer keyboard indicating an activity.

 

Slide 57:

Activity-Selecting User Needs

Assume you are procuring a stationary ESS system that monitors the conditions of the roadway pavement. Which user need is mandatory for this RFP?

Answer: No

2.5.1

ESS Manager Features

M

Yes

2.5.1.1

Generic Features

M

Yes

2.5.1.2

Monitor Do or Status

o

Yes / No

Answer: Yes

2.5.2.2 (Pavement)

Monitor Pavement

0.2

Yes / No / NA

2.5.2.2.1

Monitor Pavement Surface Condition

M

Yes / NA

Answer: No

2.5.2.3 (Subsurface)

Monitor Subsurface Conditions

0.2 (1 ..*)

Yes / No / NA

Answer: Yes

F.1.2

Generic Fea:ures

M

Yes

F. 1.3.1

Retrieve the Device Identity

M

Yes

Enter answers in the chat pod

 

Slide 58:

Learning Objective #3

PRL - Functional Requirements (FR)

 

Slide 59:

Learning Objective #4

Integration-PRL into ESS Specification

Vendor's Perspective

From a vendor's perspective

 

Slide 60:

Learning Objective #4

Integration: PRL into ESS Specification

Agency's Perspective

From an agency's perspective

 

Slide 61:

Learning Objective #4

Integration: PRL into ESS Specification

Contract Documents

Contract Document Diagram. Please See extended text description below.

(Extended Text Description: This is a snapshot of a Contract Documents table. The table consists of two boxes, one embedded into the other. The larger, outer box is entitled "Contract Documents". The inner box is entitled "Product Specifications". Within the "Product Specifications" box is a table. The table is divided into 3 columns. The first column is titled "Hardware Specifications". Below the "Hardware Specifications" heading are the following bullet points: "Functional Reqts.", "Performance Reqts.", "Structural Reqts.", "Mechanical Reqts.", "Electrical Reqts.", and "Environmental Reqts." The second column is titled "Software Specifications". Under the "Software Specifications" heading are the following bullet points: "Functional Reqts." and "Performance Reqts.". The third column is titled "Communication Interface Specifications". Under the "Communication Interface Specifications" heading are the following bullet points: "Functional Reqts.", "Performance Reqts.", and "Protocol Reqts." (highlighted in red).)

A completed PRL is part of the overall specification, in addition to the hardware and software specifications

 

Slide 62:

Integration: PRL into ESS Specification

Contract Documents (cont.)

 

Slide 63:

Integration: PRL into ESS Specification

Conformance vs. Compliance

 

Slide 64:

A placeholder graphic of hands raised to indicate polling activity.

 

Slide 65:

Poll- Conformance

Yes - NTCIP 1204 does not require an ESS to monitor every environmental parameter.

 

Slide 66:

Poll - Conformance

Potentially - the standard neither defines nor prohibits a gate closure function. The device conforms as long as it properly implements the standardized features and does not violate any rules for adding functionality.

 

Slide 67:

Poll - Conformance

No - every ESS must support the identification of the device

 

Slide 68:

Learning Objective #4

Backwards Compatibility

 

Slide 69:

Summary - NTCIP 1204 v3

 

Slide 70:

Summary - Contained Features

 

Slide 71:

Summary - PRL Issues

 

Slide 72:

What Did We Learn Today?

  1. NTCIP 1204 v03 defines the concept of operations and user needs for environmental sensor stations
  2. NTCIP 1204 v03 follows the SEP approach
  3. There are three categories of operational needs:
    1. ESS Manager
    2. Sensor Manager
    3. PTS Manager
  4. A Protocol Requirements List (PRL) is used to link the user needs to the functional requirements
  5. A completed PRL should be integrated into the specifications as part of the PS&E package

 

Slide 73:

Resources

 

Slide 74:

Next Steps

 

Slide 75:

A placeholder graphic of a light bulb indicating questions.