Module 3 - A102

A102: Introduction to User Needs Identification

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

"Welcome" graphic. See extended text description below.

(Extended Text Description: “Welcome.” Graphic image of introduction information. 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 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:

Title graphic "A102 Introduction to User Needs Identification." Footer graphic with long blue rectangle, white DOT logo, RITA, US Department of Transportation, Research and Innovative Technologies Administration with Standards ITS Training logo on left side.

 

Slide 4:

Target Audience

 

Slide 5:

Instructor

Head shot photo of instructor, Tomas Guerra.

Tomas Guerra
President
OZ Engineering, LLC Phoenix, AZ, USA

 

Slide 6:

Recommended Prerequisites

 

Slide 7:

Curriculum Path (SEP)

"Curriculum Plan (SEP)" See extended text description below.

(Extended Text Description: "Curriculum Plan (SEP)." There are a series of six boxes in two rows of three. The first blue box (upper left) is labeled “I101 Using ITS Standards: An Overview” with an arrow pointing to the right, connecting it to the middle blue box, labeled “A101 Introduction to Acquiring Standards-based ITS Systems,” which connects to the third highlighted purple box with an arrow pointing to the right, labeled “A102 Introduction to User Needs Identification.” This box connects to the the left blue box on the second row with an arrow moving down and to the left between the rows. The first blue box on the second row is labeled “A201 Details on Acquiring Standards-based ITS Systems,” with an arrow pointing to the right to the middle box, labeled “Understanding User Needs, A311a NTCIP 1203, A313a NTCIP 1204 v03, A321a TMDD v3.0” which connects to the last blue box with an arrow pointing to the right. The last box on the lower right is labeled “Specifying Requirements, A311a NTCIP 1203, A313a NTCIP 1204 v03, A321a TMDD v3.0.” )

 

Slide 8:

Curriculum Path (Non-SEP)

Curriculum Path (Non-SEP). See extended text description below.

(Extended Text Description: "Curriculum Plan (Non-SEP)." There are a series of nine blue boxes in three rows of three. The first box (upper left) is labeled “I101 Using ITS Standards: An Overview” with an arrow pointing to the right, connecting it to the middle box, labeled “A101 Introduction to Acquiring Standards-based ITS Systems,” which connects to the third highlighted purple box with an arrow pointing to the right, labeled “A102 Introduction to User Needs Identification.” This box connects to the the left box on the second row with an arrow moving down and to the left between the rows. The first blue box on the second row is labeled “A201 Details on Acquiring Standards-based ITS Systems,” with an arrow pointing to the right to the middle box of the second row labeled “A202 Identifying and Writing User Needs When ITS Standards Do Not Have SEP Content,” with an arrow pointing to the right to the last box of the second row labeled “A103 Introduction to ITS Standards Requirements Development.” There is an arrow that points down and back to the left between the second and third row to the first blue box on the third row labeled “A203 Writing Requirements When ITS Standards Do Not Have SEP Content,” with an arrow pointing to the right to the middle box of the third row labeled “*A3xxa Identifying and Writing Specific User Needs NTCIP 12xx vxx,” with an arrow pointing to the right to the last box (lower right corner) labeled “*A3xxb Developing and Writing Specific Requirements for NTCIP 12xx vxx.” There is a note at the bottom in the footer graphic that says “*Expected in year 2 training modules.”)

*Expected in year 2 training modules.

 

Slide 9:

Learning Objectives

  1. Identify user needs
  2. Identify standards that have gone through the Systems Engineering Process (SEP)
  3. Select user needs for standards that have been through SEP

 

Slide 10:

“Polling” A placeholder graphic of seven open palm raised hands indicating polling. DOT logo, RITA, Department of Transportation, Research and Innovative Technologies Administration in lower left corner and “Standards ITS Training” logo in lower right corner.

 

Slide 11:

Did you follow the SEP?

 

Slide 12:

“Activity” A placeholder graphic of a hand typing on a computer keyboard indicating an activity. DOT logo, RITA, Department of Transportation, Research and Innovative Technologies Administration in lower left corner and “Standards ITS Training” logo in lower right corner.

 

Slide 13:

Do You Know What a User Need is?

 

Slide 14:

Learning Objective #1

What is a User Need?

 

Slide 15:

Learning Objective #1

From IEEE Std 1362-1998 Guide for Information Technology

System Definition Concept of Operations Document

"A user requirement for a system that a user believes would solve a problem experienced by the user."

"The user's set of qualitative and quantitative requirements in a particular problem domain. "

 

Slide 16:

Learning Objective #1

Who Establishes a User Need?

 

Slide 17:

Learning Objective #1

From Where are User Needs Derived?

 

Slide 18:

Learning Objective #1

Why Focus on User Needs?

 

Slide 19:

Learning Objective #1

Systems Engineering Process-SEP

"Systems Engineering Process - SEP." "Subject of our discussion." See extended text description below.

(Extended Text Description: "Systems Engineering Process (SEP)." A graphic of the systems engineering process (SEP). The main graphic of the SEP is a V-shaped diagram in gradated blue with some additional horizontal extensions on the left and right side of the top of the V shape. Each section is separated with dark blue lines. There is a key at the lower right showing the blue separator lines, and designating them as “Document/Approval.” The left horizontal extension is labeled as “Lifecycle Processes” and include the sections “Regional Architecture” (separated by a white space) to the second section labeled “Needs Assessment,” (blue line) “Concept Selection,” (blue line) “Project Planning,” (blue line) and “Systems Engineering Management Planning.” At this point the sections begin to descend the left side of the V with “Concept of Operations,” “System Requirements,” “High-level Design,” “Subsystem Requirements,” “Detailed Design,” and “Software Coding / Hardware Fabrication” at the bottom juncture of the V shape. Underneath the bottom point of the V shape are the words “Implementation” then “Development Processes” and a long thin arrow pointing to the right labeled “Time Line.” There is a long thin diagonal arrow pointing down along the left side of the V labeled “Decomposition and Definition.” From the bottom point of the V, the sections begin to ascend up the right side of the V with “Unit Testing,” (blue line) “Subsystem Integration,” (blue line) “Subsystem Verification,” (blue line) “System Integration,” (blue line) “System Verification,” (blue line) “Initial Deployment,” (blue line) “System Validation,” and (blue line) “Operations and Maintenance.” There is a long thin arrow pointing up along the right side of the V shaped labeled “Integration and Recomposition.” At this point the sections on the right “wing” of the V are labeled with “Changes and Upgrades” and (white space) “Retirement/Replacement.” Between the V shape there are a series of gray dashed arrows connecting the related sections on each left/right side of the V shape. The first arrow (top) is labeled “System Validation Plan” and connects “Concept of Operations” on the left and “System Validation” on the right. The second arrow is labeled “System Verification Plan (System Acceptance)” and connects “System Requirements” on the left and “System Verification and Deployment” on the right. The third arrow is labeled “Subsystem Verification Plan (Subsystem Acceptance)” and connects “High-Level Design” on the left and “Subsystem Verification” on the right. The last arrow (at the bottom) is labeled “Unit/Device Test Plan” and connects “Detailed Design” on the left and “Unit/Device Testing” on the right. There is a dashed line bracket surrounding the upper left side of the V-shape labeled “User Needs Assessment” with a black arrow pointing directly down to the section on the left side diagonal labeled “Concept Operations.” Above right side of the V-shape and extension are the words “Reassess Needs,” with an arrow pointing down from this label to the “Changes and Upgrades” step on the right diagonal side of the V-shape. Source: V diagram adopted from U.S. Department of Transportation, Systems Engineering for ITS, U.S. Department of Transportation, January 2007.)

Source: V diagram adopted from U.S. Department of Transportation, Systems Engineering for ITS,U.S. Department of Transportation. January 2007

 

Slide 20:

Learning Objective #1

Well-Written User Needs

  1. Uniquely Identifiable: Each need must be uniquely identified (i.e., each need shall be assigned a unique number and title).
  2. Major Desired Capability (MDC): Each need shall express a major desired capability in the system, regardless of whether the capability exists in the current system or situation or is a gap.
  3. Solution Free: Each need shall be solution free, thus giving designers flexibility and latitude to produce the best feasible solution.
  4. Capture Rationale: Each need shall capture the rationale or intent as to why the capability is needed in the system.

 

Slide 21:

Learning Objective #1

Real-World User Need Example

TMC Upgrade & ITS Enhancements

December 8, 2008

No.

Gaps and Deficiencies

Needs

Operational Scenarios

12

Stakeholders agreed thai there is an operational gap in signal coordination between Minneapolis and neighboring jurisdictional areas.

Procure and deploy a traffic control system that has the capability to monitor and implement signal coordination for the arterials that cross the neighboring jurisdictional boundaries.

13

Stakeholders agreed that there is a gap in sharing cameras to monitor real-time traffic among agencies.

Improve the capability to share surveillance cameras between the City and related stakeholders.

2,3,4

14

Stakeholders agreed that there is a gap in coordinating the dissemination of traveler and incident information to the public.

Improve the capability and partnership with related stakeholders to exchange, report and disseminate traveler information and incident information to the public.

2,3,4, 5, 6, 11, 12

 

Slide 22:

Learning Objective #1

Poorly Written User Needs

 

Slide 23:

“Polling” A placeholder graphic of seven open palm raised hands indicating polling. DOT logo, RITA, Department of Transportation, Research and Innovative Technologies Administration in lower left corner and “Standards ITS Training” logo in lower right corner.

 

Slide 24:

Learning Objective #1

Poorly-Written User Needs (Examples)

Which of the following criteria is violated?

  1. Uniquely Identifiable
  2. Major Desired Capability
  3. Solution Free
  4. Capture Rationale

 

Slide 25:

Learning Objective #1

Poorly Written User Needs (Examples)

Which of the following criteria is violated?

  1. Uniquely Identifiable
  2. Major Desired Capability
  3. Solution Free
  4. Capture Rationale

 

Slide 26:

Learning Objectives #1 & 2

ITS Standards with SEP Content (as of Oct-27-2010)

C2F Device Standards (Recommended, pending SDOs approvals)

1. National Transportation Communications for ITS Protocol (NTCIP) 1203 Dynamic Message Signs (DMS) v2.0
2. NTCIP 1204 Environmental Sensor Systems (ESS) v3.0
3. NTCIP 1209 Transportation Sensor Systems (TSS)
4. NTCIP 1210 Field Master Stations (FMS), Part I SSM (v1.46)
5. NTCIP 1211 Signal Control and Prioritization (SCP) v2.0
6. NTCIP 1213 Electrical and Lighting Management Systems (ELMS) v2.0

C2C Standards Approved by SDOs

7. Traffic Management Data Dictionary (TMDD) v3.0
8. NTCIP 2306 C2C XML

 

Slide 27:

Learning Objective #3

Structure of Standards with SEP Content (C2C)

 

Slide 28:

Learning Objective #3

Example

TMDD v3.0 Standard

 

Slide 29:

Learning Objective #3

TMDD v3.0

Where do I find it?

http://www.ite.org/standards/tmdd/

Traffic Management Data Dictionary (TMDD} and Message Sets for External Traffic Management Center Communications (MS/ETMCC) v3.0

Table. See extended text description below.

(Extended Text Description: " Traffic Management Data Directory (TMDD) and Message Sets for External Traffic Management Center Communications (MS/ETMCC) v3.0." A table with two columns and three rows. The first row is darker gray and is the header row, with the words “Title” and “Order Now.” The first data row includes “Volume 1” and a shopping cart icon in the second cell. The second data row includes “Volume 2” and a shopping cart icon in the second cell.)

 

Slide 30:

TMDD Volume I - Table of Contents

2 CONCEPT OF OPERATIONS FOR TRAFFIC MANAGEMENT CENTER-TO-CENTER COMMUNICATIONS 9

2.1 Scope 9

2.2 User Classes 11

2.2.1 Data User 11

2.2.2 Operations User 12

2.3 Needs 12

2.3.1 Need for Connection Management 12

2.3.1.1 Verity Connection Active 12

2.3.1.2 Need to Support Requests 12

2.3.1.3 Need to Support Subscriptions 12

2.3.1.4 Need to Support Error Handling 12

3 REQUIREMENTS 34

3.1 Introduction 34

3.2 Mandatory and Optional Data 34

3.3 Detailed Requirements 34

3.3.1 Connection Management 34

3.3.1.1 Exchange Center Active Verification 34

3.3.1.1.1 Send Center Active Verification Upon Request 34

 

Slide 31: TMDD Volume I - Table of Contents

4 TRACEABILITY TO THE NATIONAL ITS ARCHITECTURE 156

4.1 TMDD Trace to Market Packages 156

4.1.1 Network Surveillance (ATMS01 157

4.1.2 Traffic Information Dissemination (ATMS06) 158

4.1.3 Regional Traffic Operations (ATMS07) 159

4.1.4 Traffic Incident Management (ATMS08) 160

4.1.5 Road Weather Data Collection (MC03) 161

5 NEEDS TO REQUIREMENTS TRACEABILITY MATRIX 171

5.1 User Need ID and User Needs Columns 171

5.2 User Need Selected? 171

5.3 Requirements ID and Requirements Columns 171

5.4 Conformance Column 171

5.4.1 Status Symbols 171

5.4.2 Conditional Status Notation 172

5.5 Support 173

5.6 Other Requirements Column 173

 

Slide 32:

Learning Objective #3

Example of TMDD User Need(s)

2.3.6.4.4 Need to Display a Message on a Remote DMS

Centers need to request that a specific message be displayed on a DMS controlled by another center. Messages may be either freeform text messages, in MULTI-string format, or from a library associated with the DMS.

When a control request is received, the center that controls the DMS needs to make a determination if the message will be implemented, queued, or rejected. Then, the center that controls the DMS needs to send a response to the center that originated the request describing the status (action taken) on the control request.

 

Slide 33:

Learning Objective #3

Needs to Requirements Traceability Matrix (NRTM)

TMDD Standard for Traffic Management Center-to-Center Communications Volume I: Concept of Operations and Requirements

Balloted Standard November 12,2008

UN ID

User Need

UN Selected

Requirement ID

Requirement

Conformance

Support

Other Requirements

2.3.6.4.4

Need to Display a Message on a Remote DMS

Yes/ No

3.3.6.1.4.1

Contents of Device Control Request Header

M

Yes

3.3.6.1.4.1.1

Required Device Control Reguest Header Content

M

Yes

3.3.6.1.4.1.2.1

Operator Identifier

0

Yes /No

3.3.6.1.4.1.2.2

Request Priority

0

Yes/No

3.3.6.1.4.1.2.3

Request Expiration Date and Time

0

Yes/No

3.3.6.1.4.1.2.4

Event Identifier

0

Yes /No

3.3.6.1.4.1.2.5

Event Response Plan

0

Yes/No

3.3.6.1.4.1.2.6

External Center Organization

0

Yes/No

3.3.6.1.4.1.2.7

Request Date and Time Information

0

Yes/No

3.3.6.1.4.2

Contents of Device Control Request Response

M

Yes

3.3.6.1.4.2.1

Required Device Control Response Content

M

Yes

3.3.6.1.4.2.2.1

Operator Identifier

0

Yes/No

3.3.6.1.4.2.2.2

Operator Lock Identifier

0

Yes/No

3.3.6.1.4.2.2.3

Owner Center Organization

0

Yes/No

3.3.6.1.4.2.2.4

Operator Last Revised Date and Time

0

Yes/No

3.3.6.5.3.1

Send DMS Control Response Upon Reguest

M

Yes

3.3.6.5.3.2

Contents of DMS Control Request

M

Yes

3.3.6.5.3.2.1

Required DMS Control Request Content

M

Yes

3.3.6.5.3.2.2.1

Beacon Control

0

Yes/No

3.3.6.5.3.3

Contents of DMS Control Response

M

Yes

 

Slide 34:

Learning Objective #3

TMDD v3.0

Additional training available:

Module A321a: Understanding User Needs for Traffic Management Systems Based on TMDD V3 Standard

This module will provide participants with information on how to identify the appropriate use of the TMDD V3 standard and acquire a Traffic Management system based on what the user is seeking to accomplish with support from tools and resources such as Needs to Requirements Traceability Matrix (NRTM) in following a systems engineering process.

 

Slide 35:

Learning Objective #3

NTCIP 1203 Example

Overview of NTCIP 1203 DMS

 

Slide 36:

Learning Objective #3

Organization of NTCIP 1203 DMS

 

Slide 37:

Learning Objective #3

NTCIP 1203 DMS

www.ntcip.org/library/documents/

Table. See extended text description below.

(Extended Text Description: Two tables of four columns. The first is a single row of data: Cell 1 -- "1203"; Cell 2 -- "Device Data Dictionary"; Cell 3 -- "NTCIP Object Definitions for Dynamic Message Signs (DMS)"; Cell 4 -- shopping cart icon. The second is two rows of data: Row 1, Cell 1: "9002"; Cell 2 -- "Information Report"; Cell 3 -- "NTCIP VDOT Case Study on VMS"; Cell 4 -- empty. Row 2, Cell 1: "9003"; Cell 2 -- "Information Report"; Cell 3 -- "NTCIP WashDOT Case Study on VMS"; Cell 4 -- empty.)

 

Slide 38:

Learning Objective #3

NTCIP 1203 DMS

 

Slide 39:

Learning Objective #3

Example User Needs from NTCIP 1203 DMS v02

2.5.3.1 Perform Diagnostics

This feature enables the operator to test the operational status of system components. It consists of the following sub-features:

a) Determine Sign Error Conditions (High-Level Diagnostics)

b) Monitor Sign Subsystem Failures (Mid-Level Diagnostics)

2.5.3.1.13 Monitor Fuel Level

This feature enables the operator to monitor the level of fuel within the tank of a generator that is being used to operate the DMS. This feature is typically used in portable signs.

 

Slide 40:

Learning Objective #3

3.3.8 Protocol Requirements List (PRL)

UN Section Number

User Need (UN)

FR Section Number

Functional Requirem ent (FR)

Conformance

Support / Project Requirem ent

Additional Project Requirements

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 Fiber:M

Yes / NA

3.5.3.1.1.2 (Pixel Test)

Activate Pixel Testing

Matrix: M

Yes / NA

3.5.3.1.1.3 (ClimateTest)

Execute Climate-Control Equipment Testing

0

Yes/No

3.5.3.1.2

Provide General DMS Error Status Information

M

Yes

 

Slide 41:

Learning Objective #3

Project User Needs

Table with four columns: 1) "UN ID#" 2) "UN Title" 3) "User Need" 4) "Remark". There are three rows: 1) purple with subheads mentioned; 2) Medium blue with all cells blank; 3) lighter blue with all cells blank.

Two examples follow...

 

Slide 42:

VDOT/VTTI Early Deployment

 

Slide 43:

Learning Objective #3

NTCIP 1203 DMS

Additional training to be available:

Module A311a-Understanding User Needs for DMS Systems Based on NTCIP 1203 Standard

This module will provide participants with information on how to identify the appropriate use of the NTCIP 1203 standard and acquire a Dynamic Message Sign system based on what the user is seeking to accomplish with support from tools and resources such as a Protocol Requirements List (PRL) in following a systems engineering process.

 

Slide 44:

Additional Examples of Standards with SEP Content

NTCIP 1204 ESS v3.0

2.5.2.1.1 Monitor Atmospheric Pressure

A transportation system operator may need to monitor the atmospheric pressure in the vicinity of the ESS.

2.5.2.1.2 Monitor Winds

A transportation system operator may need to monitor the current wind conditions in the vicinity of the ESS.

 

Slide 45:

NTCIP 1209 TSS v02

2.5.4 Collect Data from TSS

The various sub-features for collecting data from the TSS include:

a) Retrieve In-Progress Sample Data

b) Retrieve Most Recently Completed Sample Data

c) Retrieve Historical Sample Data

 

Slide 46:

NTCIP 1210 FMS Part I SSM v1.46

2.5.1.2.5.1 Configure Traffic Responsive Mode

To operate in an traffic responsive mode, a system owner needs to configure the SSM to assign which system detectors to obtain data from, configure the pattern selection frequency, and to select which traffic-responsive algorithm (Threshold or Signature) to use. Once these selections are made, the SSM directs the SSL to engage the plan that contains these elements.

 

Slide 47:

NTCIP 1211 Signal Control and Prioritization (SCP) v01 vs. v02

2.5.1.1.3 Configure Reservice Period

A management station needs to define the reservice period between when servicing one priority request is completed and when a subsequent priority request is serviced. This feature allows an operator to prevent the Priority Request Server (PRS) from constantly servicing priority requests, therefore disrupting traffic flow. This feature also helps maintain headways to prevent bunching of transit vehicles.

 

Slide 48:

NTCIP 1213 Electrical and Lighting Management Systems (ELMS) v2.0

2.4.1.2.9 Provide Periodic Power Meter Measurement Logging

The management station may need to configure the ELMS device to keep a local log of periodic measurements of the voltage, current, power, and energy.

 

Slide 49:

NTCIP 2306 C2C XML v2.0

2.1 Profile Need (PN 2.1) Message Encoding Privacy

Privacy. This profile needs a mechanism to allow messages to be privately transmitted over the Internet and other shared networks.

 

Slide 50:

Learning Objective #2

Standards without SEP Content (as of Oct-27-2010)

C2F Device Approved Standards

1. NTCIP 1202 Actuated Traffic Signal Controller (ASC)
2. NTCIP 1205 Closed Circuit Television (CCTV)
3. NTCIP 1206 Data Collection
4. NTCIP 1207 Ramp Meters
5. NTCIP 1208 Video Switches
6. NTCIP 1214 Signal Monitor Unit (SMU) Conflict Monitoring

Domain Standards (includes C2C communication protocols)

7. IEEE 1512 Incident Management
8. IEEE 1609.X DSRC
9. SAE J2354 ATIS
10. SAE LRMS Series
11. SAE J2735 DSRC Message Sets
12. ITS Cabinet
13. ITE ITS Advanced Traffic Controller v5.2

Equipment Standards

14. ITS Cabinet v1
15. ATC Controller Standard v5.2b

 

Slide 51:

Extracting User Needs from Standards without SEP Content

 

Slide 52:

What did we Learn Today?

1) User Needs describe the major capability provided by a system.

2) Criteria for a well-written User Need:

a) Uniquely Identifiable

b) Describe Major Desired Capability (MDC)

c) Are Solution Free

d) Capture Rationale or Intent

3) Identified eight (8) ITS standards that contain Systems Engineering Process (SEP) content

4) How to select User Needs from the Concept of Operations section

 

Slide 53:

Conclusion

 

Slide 54:

Module A201

Next Module:

Details on Acquiring Standards-based ITS Systems

The module will provide guidance on selecting the appropriate standard for acquiring standards based systems that take into account the specifications, processes, and roles of users and staff.

 

Slide 55:

Where to Learn More

 

Slide 56:

“Questions?” A placeholder graphic of a light bulb indicating questions. DOT logo, RITA, Department of Transportation, Research and Innovative Technologies Administration in lower left corner and “Standards ITS Training” logo in lower right corner.