Module 39 - A307a

A307a: Understanding User Needs for Advanced Transportation Controllers Based on ATC 5201 Standard v06

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 image of introductory slide. Please see the Extended Text Description below.

(Extended Text 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" 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 Transportation, Office of the Assistant Secretary for Research and Technology.)

Slide 2:

Welcome slide with Ken Leonard and screen capture of home webpage. Please see the Extended Text Description below.

(Extended Text 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:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

Slide 4:

A307a:

Understanding User Needs for Advanced Transportation Controllers Based on ATC 5201 Standard v06

Slide 5:

Instructor

Headshot photo of Ralph W. Boaz, President, Pillar Consulting, Inc., San Diego, CA, USA.

Ralph W. Boaz President

Pillar Consulting, Inc.

San Diego, CA, USA

Slide 6:

Target Audience

Slide 7:

Recommended Prerequisites

SEP Content

Slide 8:

Recommended Prerequisites (cont.)

Standard Part 2 of 2

Slide 9:

Curriculum Path

This slide contains a graphic illustration indicating the sequence of training modules that lead up to this course. Please see the Extended Text Description below.

(Extended Text Description: This slide contains a graphic illustration indicating the sequence of training modules that lead up to this course. Each module is represented by a box with the name of the module in it and arrows showing the logical flow between the modules. There are 12 boxes in total; three rows of 4 boxes. The sequence goes from left to right with the fourth box on the first and second rows having arrows which connect to the first box on the second and third rows respectively. The module titles are as follows: I101: Using ITS Standards: An Overview, A101: Introduction to Acquiring Standards -based ITS Systems, A102: Introduction to User Needs Identification, A201: Details on Acquiring Standards-based ITS Systems, A202: Identifying and Writing User Needs When ITS Standards, Do Not Have SEP Content, A103: Introduction to ITS Standards Requirements Development, A203: Writing Requirements When ITS Standards Do Not Have SEP Content, C101: Intro. to Comm. Protocols and Their Uses in ITS Applications, A207a: Building an ITS Infrastructure Based on the ATC 5201 Standard (Part 1), A207b: Building an ITS Infrastructure Based on the ATC 5201 Standard (Part 2), A208: Using the ATC 5401 Application Programming Interface Standard to Leverage ITS Infrastructures, A307a: Understanding User Needs for Advanced Transportation Controllers (ATC) Based on 5201 Standard v06. The last box is highlighted indicating that it represents the current module in the series.)

Slide 10:

Learning Objectives

  1. Identify the advantages of transportation controllers based on ATC 5201 Standard v06
  2. Describe a systems engineering-based ATC specification development process
  3. Identify and write user needs for ATCs
  4. Create a concept of operations (ConOps)

Slide 11:

Learning Objective #1: Identify the Advantages of Transportation Controllers Based on ATC 5201 Standard v06

Slide 12:

Learning Objective #1

Discuss the Purpose of the ATC 5201 Standard v06

This slide, entitled Discuss the Purpose the ATC 5201 Standard v06, contains a graphic used to highlight bulleted text in the slide.Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "Discuss the Purpose the ATC 5201 Standard v06," contains a graphic used to highlight bulleted text in the slide. There is a blue box in the lower right of the slide that appears with an arrow pointing to the slide text "Multi-tasking/multi-application." The box contains the text "When using ATC Application Programming Interface (API) Software." The bulleted text in the slide is as follows:

)

Slide 13:

Learning Objective #1

Discuss the Purpose of the ATC 5201 Standard v06 (cont.)

Slide 14:

Learning Objective #1

Traditional Controllers Run a Single Application Program at a Time

Traditional Controllers Run a Single Application Program at a Time. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "Traditional Controllers Run a Single Application Program at a Time," has a graphic of a transportation controller on the left side of the slide, a list of three applications used in transportation controllers on the right side of the slide and a left brace that is used to indicate that the applications on the right may run within the controller on the left. The text to the right reads, Traditional Applications, Data collection application OR Traffic signal application OR Ramp meter application. The controller on the left is rectangular and about 2.5 times as wide as it is tall. There is a small rectangular screen in the upper center of the controller. There are two rectangular key pads (side by side) beneath the screen. To the left of the keypad is an LED with the word "ACTIVE" underneath it. To the left of the LED at mid-height of the controller is a rectangular latch. The upper left portion of the controller has the words "MODEL 2070 UNIT." To the right of the keypads is a toggle switch with the word "AUX" to the left of it and the words "ON" and OFF" above and below it respectively. To the right of the switch and slightly higher is a round knob that has the word "CONTRAST" beneath it. Below the Contrast Knob are two small rectangular connectors arranged vertically. Above the first connector is the word "C50S" below the second connector is the word "C50J." Near the right edge of the controller are two large screws with one located near the top controller and the other located near the bottom of the controller. To the right of the screws is a narrow hinge that runs down the entire height of the controller.)

Graphics: Ralph W. Boaz

Slide 15:

Learning Objective #1

Any ATC Can Run Multiple Application Programs Simultaneously

Any ATC Can Run Multiple Application Programs Simultaneously. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "Any ATC Can Run Multiple Application Programs Simultaneously," has two graphics of transportation controllers and a text box on the left side of the slide, and a list of 10 applications that could be used in transportation controllers on the right side of the slide. There is a large left brace in the center of the slide indicating that the applications on the right may run within the controllers on the left. The two controllers and the text box are aligned by their centers vertically. The text on the right reads, Example Applications for ATCs, Traffic signal control/traffic management, Transit/light rail priority, Emergency management, Lane use, Red light enforcement, Speed monitoring/enforcement, Access control, Advanced traveler information systems (ATIS), Data collection systems, Connected vehicle (CV) applications. The first controller is twice as wide as it is tall. It has a display centered within the controller, two keypads aligned vertically on the right, and four large circular connectors along the bottom. There are two rectangular expansion slots that are nearly the height of the controller that are next to each other along the left side of the controller. The left most slot has several D-Sub connectors in it. The other slot is empty. It has the word "ATC" at the top center of the controller. The second controller is 2.5 times has wide as it is tall. It is about 10% shorter that the first controller. It has a display on the left side of the controller, two keypads aligned horizontally in the center of the controller, and the word "ATC" at the top right of the controller. Below the display and the keypads there are various connectors. The text box is about the same width as the second controller but approximately 15% shorter. It contains the words "When using ATC API Software." The bulleted text to the right contains the following:

Example Applications for ATCs

)

Graphics: Ralph W. Boaz

Slide 16

Learning Objective #1

Identify Key Elements of the ATC 5201 Standard v06 Architecture

Slide 17:

Learning Objective #1

ATC Engine Board Concept

ATC Engine Board Concept. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "ATC Engine Board Concept," is a graphic representation of a circuit board. It is approximately 40% of the height of the slide twice as wide as it is tall. There are seven variously shaped labeled rectangles representative of electronic components on the board. They are labeled "ENET 1," "ENET 2," "USB," "RTC," "CPU + LINUX O/S," "MEMORY" and "SERIAL I/O." There are two additional rectangles, identical in shape, representative of electronic connectors at the top and bottom of the board.)

Graphics: Ralph W. Boaz

Slide 18:

Learning Objective #1

Engine Boards Used to Create Different Types of Transportation Controllers

Engine Boards Used to Create Different Types of Transportation Controllers. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "Engine Boards Used to Create Different Types of Transportation Controllers," is agraphic illustrating how the Engine Board can be used to build controller units that are of different designs. The Engine Board shown in Slide 17 is shown in the lower center of the slide. Its width is about 40% the width of the slide. To the upper left and upper right of the Engine Board are graphics of other electronic boards about equal in size to the Engine Board. They have labels above them "2070 Host Module" and "NEMA Host Module," respectively. The Host Boards are rectangular but angled inward towards the Engine Board. The 2070 Host Module has a slender metallic plate perpendicular to the board on the left side. There is a slender connector running along the right edge of the board. In the center of the board is an Engine Board that takes up approximately 75% the width of the Host Module. The Engine Board is outlined by a heavy dashed line. The NEMA Host Module has a small rectangular connector and four circular connectors running along the bottom of the board. They are all approximately 25% of Host Board in height. There is a slender connector running along the right side of the Host Board but not quite to the edge. There are metallic circles in each of the corners of the board. In the center of the board is an Engine Board that takes up approximately 50% the width of the Host Module. The EngineBoard is outlined by a heavy dashed line. There are four heavy dashed lines connecting the corners of the large Engine Board to the four corners of the Engine Board on the 2070 Host Module. There are four heavy dashed lines connecting the corners of the large Engine Board to the four corners of the Engine Board on the NEMA Host Module.)

Graphics: Ralph W. Boaz

Slide 19:

Learning Objective #1

ATC 5401 Standard Defines API Software Which Allows Concurrent Application Programs

Slide 20:

Learning Objective #1

ATC 5401 Standard Defines API Software Which

Allows Concurrent Application Programs (cont.)

Slide 21:

Learning Objective #1

Front Panel Manager Window

Front Panel Manager Window. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "Front Panel Manager Window," is a graphic illustrating how multiple concurrently running programs can operate on a single ATC controller unit. In the upper part of the slide is a square about 1/8 the height of the slide representing a LCD screen and keypads (see Slide #25) portion of a transportation controller. Below the square is an enlargement of the LCD screen. There are dotted lines extending from the LCD in the square to the edges of the enlargement. The enlarged LCD screen is about 25% of the height of the slide and extends almost the entire width of the slide. There are 8 lines x 40 fixed width characters across shown in the LCD as follows: Line 1. "FRONT PANEL MANAGER VER 1.00" Line 2. "SELECT WINDOW: 0-F SET DEFAULT: *,0-F" Line 3. "0 Ramp Meter Prgrm 1*Signal Program" Line 4. "2 Emergency Mngmnt 3 Data Distributor" Line 5. "4 System Checker 5" Line 6. "6 7" Line 7. "8 9" Line 8. "[MORE - UP/DN ARROW] [CONFIG INFO-NEXT]" )

[Application programs shown are for example purposes only and not included in API Software]

Graphics: Ralph W. Boaz

Slide 22:

Learning Objective #1

Examples of ATC Units

Examples of ATC Units. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "Examples of ATC Controller Units," contains six photographs of controllers of various shapes, sizes and designs. All of the controllers have a Liquid Crystal Display (LCD) screen and a key pad with differing arrangements of keys. All of the controllers have various electronic cable connectors including RJ45 jacks typical of Ethernet connections (appear as small dark squares approximately 1/2 " W X 1/2" H), 9 pin Sub D connectors (1" W X 1/2" H) typically used for serial connections, 15 pin Sub D connectors (1.5" W X 1/2" H) typically used for serial connections, 25 pin Sub D connectors (2" W X 1/2" H) typically used for serial connections, and USB ports (1/2" W X 1/4" H) common to computers. Some of the units have round circular connectors about 1.5 inches in diameter. The controllers are arranged in a staggered fashion with two controllers on the left side of the slide, one controller in the middle and three controllers to the right side.

Photos: Econolite, Intelight, McCain, Peek, Siemens, and Trafficware

Slide 23:

Learning Objective #1

Describe How ATC 5201 Standard v06 Works

With Other ITS Standards

Slide 24:

Learning Objective #1

ATC Units in Different TFCSs

ATC Units in Different TFCSs. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "ATC Controller Units in Different TFCSs," illustrates that ATC 5201 conforming controller units can be designed to be used in existing TFCSs. The left of the slide is a graphic of the interior Model 332 Cabinet. The graphic is about 65% of the height of the slide and 25% of the width. There are side rails of an equipment rack which run along the left and right sides of the front of the cabinet interior. There are four sections of the equipment that extend edge to edge of the cabinet interior attaching to the side rails of the rack.

The second row consists of an assembly of devices that take up about the width of the lower section and 20% of the height. Starting from the left of the assembly is a rectangular device that is about twice as tall as it is wide. It has three connectors (two round connector and one rectangular connector) on the left side of the device. It has the letters "BIU" at the top center of the device. To the right of the BIU are eight evenly spaced nine rectangular devices. These devices consist of a smaller rectangle with three lights (except for the far right one has two lights) attached to a thick line that extends to the same height of the BIU. – The third row consists of four squares about 5% of the lower section height. The four squares are evenly spaced and take up the left half of the row. – The fourth row has a single long rectangular rack of 54 round connectors arranged in in 2 rows and evenly spaced. – The fifth row is the same as the fourth.

)

Graphics: Ralph W. Boaz

Slide 25:

Learning Objective #1

ATC 5201 Working With Other ITS Standards

ATC 5201 Working With Other ITS Standards. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "ATC 5201 Working With Other ITS Standards," illustrates how ATC 5201 and ATC 5401 Standard enables the use of other ITS standards. There is a graphic on the left 2/3 of the slide. On the right 1/3 of the slide are labels that identify the standards that are used at each level. Level 1 of the graphic shows the top portions of the graphic illustrations of the Caltrans 332 and the NEMA TS 2 cabinets from the previous slide aligned side by side. In the Caltrans 332 cabinet, the ATC controller is shown. In the NEMA TS 2 Type 1 Cabinet the ATC controller and the MMU are shown. To the right of the cabinets is the label "TFCS Standards & Specifications." Level 2 of the graphic shows two Engine Board graphics as described in Slide 55 except they are about 1/8 the width and 1/10 the height of the slide. They are aligned side by side and centered above the cabinet graphics (one over each cabinet). There are thick curved arrows extending out of the left side of each Engine Board and pointing to the left side of the controller in the cabinets below them. To the right of the cabinets is the label "ATC 5201 Standard." Level 3 of the graphic shows a rectangle labeled "API Software" above each of the two Engine Boards. They are aligned side by side and centered above the Engine Board graphics (one over each Engine Board). There are thick curved arrows extending out of the left side of the API Software Pillar Consulting, Inc.rectangles and pointing to the left side of the Engine Boards below them. To the right of the API Software rectangles is the label "ATC 5401 Standard." Level 4 is a large rounded rectangle that is about 25% of the height of the slide and 40% of the width of the slide. It is aligned so that it is centered above the two API Software rectangles. At the top of the rounded rectangle is the label "Example Applications." The remainder of the large rounded rectangle is made up of four identically sized rounded rectangles. The upper left rounded rectangle is labeled "Single Control App w/ASC." The upper right rounded rectangle is labeled "Field Master App w/FMS." The lower left rounded rectangle is labeled "Ramp Meter App w/RMC." The lower right rounded rectangle is labeled "SPAT Message Service." There is a thick curved arrow extending out of the left side of the large rounded rectangle and pointing to the left side of the API Software rectangle to the lower left. There is a thick curved arrow extending out of the right side of the large rounded rectangle and pointing to the right side of the API Software rectangle to the lower right. To the right of the large rounded rectangle is the label "NTCIP, Other Standards.")

Graphics: Ralph W. Boaz

Slide 26:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

Slide 27:

Learning Objective #1

Which of the following features of ATC units allows them to run concurrent application programs?

Answer Choices

  1. Has a computational capability that can grow with technology
  2. Works with all major transportation field cabinet systems
  3. Works with NTCIP standards
  4. Runs API software

Slide 28:

Learning Objective #1

Review of Answers

A small graphical red and yellow X representing incorrect.a) Has a computational capability that can grow with technology
Incorrect. Being able to grow with technology is a feature of ATCs which mitigates obsolescence.

A small graphical red and yellow X representing incorrect.b) Works with all major transportation field cabinet systems
Incorrect. This feature allows ATC units with contemporary processing power to be used to upgrade older cabinet systems.

A small graphical red and yellow X representing incorrect.c) Works with NTCIP standards
Incorrect. ATC units provide the computing resources for NTCIP communications but the applications determine their use.

A small graphical green and yellow check mark representing correct.d) Runs API software
Correct! The API software, defined by the ATC 5401 Standard, runs on ATC units and allows application programs to share the resources of the controller.

Slide 29:

Summary of Learning Objective #1

Identify the Advantages of Transportation Controllers Based on ATC 5201 Standard v06

Slide 30:

Learning Objective #2: Describe a Systems Engineering-Based ATC Specification Development Process

Slide 31:

Learning Objective #2

Traditional Approaches to Developing Transportation Controller Procurement Specification

Slide 32:

Learning Objective #2

Systems Engineering Approach to Developing an ATC Procurement Specification

Slide 33:

Learning Objective #2

Systems Engineering Processes Used in Standards Development

IEEE - Systems Engineering

An interdisciplinary collaborative approach to derive, evolve, and verify a life cycle balanced system solution that satisfies customer expectations and meets public acceptability.

Systems Engineering Processes Used in Standards Development. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "Systems Engineering Processes Used in Standards Development," uses a graphic that illustrates the systems engineering process used in standards development. This graphic introduces three circles evenly spaced in a descending fashion from left to right. They contain the text "User Needs," "Requirements" and "Design," respectively. There is a curved arrow leading from the "User Needs" circle to the "Requirements" circle. There is a curved arrow leading from the "Requirements" circle to the "User Needs" circle. This same arrange of arrows occurs between the "Requirements" circle and the "Design" circle.)

Graphics: Ralph W. Boaz

Slide 34:

Learning Objective #2

Systems Engineering Specification Development Process

Systems Engineering Specification Development Process. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "Systems Engineering Specification Development Process," uses a graphic that illustrates the systems engineering process used to develop a specification. There are two circles evenly spaced in a descending fashion from left to right representing processes. They contain the text "User Needs" and "Requirements," respectively. There is a curved arrow extending from the User Needs process to the Requirements process. There is a curved arrow extending from the Requirements process to the User Needs process. There are three rectangular graphics with lines across them representing documents. The first document is located at the top of the slide and is labeled "Strategic or Regional Plans." It has a curved arrow extending from the document to the User Needs process. There is a curved arrow extending from the User Needs process two the second document located in the lower left of the slide that is labeled "Concept of Operations." There is a curved arrow extending from the Requirements process to the third document located in the lower right of the slide that is labeled "Agency Specification." There is a dotted double arrow extending between the second and third documents. The double arrow is labeled "Traceability.)

Graphics: Ralph W. Boaz

Slide 35:

Learning Objective #2

Relationships of User Needs and Requirements

Relationships of User Needs and Requirements. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "Relationships of User Needs and Requirements," uses graphics to highlight the relationships between a user needs and requirements. User needs are represented by green boxes on the left side of the slide labeled "Need #1," "Need #2," "Need #3," and "Need #4." Requirements are represented by green boxes on the right side of the slide labeled "Requirement #1," "Requirement #2," "Requirement #3," and "Requirement #4." Three relationships between the user needs and the requirements are represented using solid blue lines with arrows on each end connecting the needs and requirements as follows: One-to-One – Need #1 is connected to Requirement #1; One-to-Many – Need #2 is connected to Requirement #2 and Requirement #3; and Many-to-One – Need #3 and Need #4 are connected to Requirement #4.)

Graphics: Ralph W. Boaz

Slide 36:

Learning Objective #2

Benefits of the Systems Engineering Specification Development Process

Slide 37:

Learning Objective #2

Challenges to Preparing a Good ATC Specification

Slide 38:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

Slide 39:

Learning Objective #2

Which of the following is NOT a good source for discovering user needs?

Answer Choices

  1. Regional plans
  2. Integration testing
  3. Stakeholders
  4. Strategic plans

Slide 40:

Learning Objective #2

Review of Answers

A small graphical red and yellow X representing incorrect. a) Regional plans
Incorrect. Regional plans provide insight into the future and are a good source for discovering user needs.

A small graphical red and yellow check representing correct. b) Integration testing
Correct! It is not a good practice to depend on integration testing to discover user needs.

A small graphical red and yellow X representing incorrect. c) Stakeholders
Incorrect. Stakeholders are a good source (essential source) for discovering user needs.

A small graphical red and yellow X representing incorrect. d) Strategic plans
Incorrect. Strategic plans provide insight into the future and are a good source for discovering user needs.

Slide 41:

Summary of Learning Objective #2

Describe a Systems Engineering-Based ATC Specification Development Process

Slide 42:

Learning Objective #3: Identify and Write User Needs for ATCs

Slide 43:

Learning Objective #3

Sources of User Needs for ATCs

Slide 44:

Learning Objective #3

Sources of User Needs - Stakeholders

Sources of User Needs – Stakeholders. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "Sources of User Needs – Stakeholders" illustrates the broad base of stakeholders that could contribute user needs for an ATC project. It uses a graphic of four concentric circles arranged in a fashion similar to an archery target. The innermost circle is a reddish tan. The three bands of colors that are further from the center are in lighter shades of tan. This is called an "onion diagram" as onions are made up of multiple layers. The inner circle is labeled "Physical System." The next layer outward is labeled "Operational System." The next layer outward is labeled "Containing System." The outermost layer is labeled "Wider Environment." There are smaller black representations of people positioned in the different layers of the diagram. Each person has a project role next to it as follows: Inner Circle has no people – It represents the system; Next Layer Outward has three people labeled "TMC Operator", "Field Maintenance" and "Operational Support" respectively; Next Layer Outward has two people labeled "Interfacing System Owner" and "Purchaser" respectively; and Outermost Layer has four people labeled "Sponsor," "Regulator," "The Public" and "Politician" respectively. The picture demonstrates while they are all stakeholders, different stakeholders have different levels of influence on the physical system to be defined. The most influence coming from those closest to the center.)

© Ian Alexander 2006 (adapted with permission)

Slide 45:

Learning Objective #3

Characteristics of Well-Written User Needs

Slide 46:

Learning Objective #3

An Example User Need

7.8.2.1 Traffic Signal Control

The user needs to safely control the flow of traffic through the city's signalized intersections. There are over 100 signalized intersections within the city limits. The city uses pre-timed, semi-actuated and fully actuated modes of traffic signal operation. Traffic signals may be operated as a standalone intersection or in coordination with other intersections.

Uniquely Identifiable? ✓
Major Desired Capability? ✓
Captures Rationale? ✓
Solution-Free? ✓

Slide 47:

Learning Objective #3

An Example User Need

7.3.5 Keypads

The user needs the controller to have keypads as described in Section 9.4.2 of the Caltrans TEES 2009. The city has had no maintenance issues with these types of keypads on their existing controllers. The keypads work well with the city's existing signal control software.

Uniquely Identifiable? ✓
Major Desired Capability? X
Captures Rationale? X
Solution-Free? X

Slide 48:

Learning Objective #3

User Needs as a Process of Discovery

User Needs as a Process of Discovery. Please see the Extended Text Description below.

(Extended Text Description: This slide, entitled "User Needs as a Process of Discovery," shows how the development of user needs can be a process of discovery. It shows a large circle with three arrows located equidistantly around the circle pointing in a clock-wise direction. Between the arrows are three ovals with text located equidistantly around the circle. The first oval (on the left side of the circle) says "Discover." Going clockwise around the circle, the next oval says "Document." Continuing clock-wise around the circle the next oval says "Validate." In the middle of the circle are small representations of people with the word "Stakeholders" over them. There are arrows pointing out from the people to the ovals around the circle. The "Validate" oval (located on the lower right portion of the circle has an arrow pointing from the oval to text to the right that says "Next Activity.")

© Ian Alexander 2006 (adapted with permission)

Slide 49:

Learning Objective #3

User Needs from Strategic and Regional Plans

Case Study

This section uses examples from the "Orange County Intelligent Transportation Systems (ITS) Strategic Deployment Plan (SDP) - Update 2013." This SDP was developed by the Orange County Transportation Authority (OCTA), a Metropolitan Planning Organization (MPO) for Orange County, CA.

The SDP uses ITS "strategies" to provide context for the agencies and the private sector who are deploying technology today and for the following ten years. Strategies are organized as follows: Transit management and multi-modal (MM); traffic management (TM), incident management and emergency response (IM), traveler information (TI), performance monitoring (PM), communications and connectivity (CC), safety (SF), and institutional (IN).

Other strategic or regional plans may have different names and different methods of expressing desired capabilities.

Slide 50:

Learning Objective #3

Example "Strategies" from Orange County ITS Strategic Deployment Plan

MM2 - Bus Rapid Transit (BRT): Roll out BRT service in a two-step implementation process. Technology applications could include transit signal priority (TSP), real-time bus arrival information, and automated fare collection.

MM5 - Support for Pedestrian and Bicycle Travel: Local deployments of pedestrian and bicycle safety, bike-sharing, and information technologies.

Slide 51:

Learning Objective #3

Example User Needs Derived from Orange County ITS SDP "Strategies"

7.8.3.3 Increase Public Use of Transit Buses

The city needs transportation controllers that can be used to help increase ridership of transit buses. The city needs to improve customer service and ridership experience through the use of field applications that may include TSP (transit signal priority), real-time bus arrival information, automated fare collection, and others.

7.8.6.1 Non-Vehicle Modes of Transportation

The city needs transportation controllers that provide for pedestrian and bicycle applications. This is to reduce vehicle congestion, improve safety, and promote non-motorized travel.

Slide 52:

Learning Objective #3

Example "Strategies" from Orange County ITS Strategic Deployment Plan

CC1 - Countywide Communications Master Plan: Physical and logical connectivity to support multi-modal and multi-agency operations and data sharing needs.

CC3 - Provide a Connected Vehicles Platform: Allow for the future possibility of connected vehicles in order to capitalize on the robust local operational environment and further enhance the existing foundation.

Slide 53:

Learning Objective #3

Example User Needs Derived from Orange County ITS SDP "Strategies"

7.4.3.1 Multi-Network Ready

The city needs transportation controllers equipped with communications capabilities to accommodate connectivity with multiple systems and communications networks. The city has legacy center-to-field (C2F) communications to some arterials. The majority of the arterials are supported by Ethernet communications through fiber or high speed radios. It is expected that some applications will share a physical network while others will require separate networks.

Slide 54:

Learning Objective #3

Example User Needs Derived from Orange County ITS SDP "Strategies" (cont.)

7.5.1 Connected Vehicle V2I Communications

The city needs transportation controllers that have the processing power to perform connected vehicle vehicle-to-infrastructure (V2I) communications. Connected vehicle applications have the potential for a major advancement in integrated traveler information, safety, transportation management, and eco driving.

Slide 55:

Learning Objective #3

Example Architectural Constraint

6.5.1 Transportation Field Cabinet Systems

The city needs transportation controllers equipped for existing transportation field cabinet systems. The city has 70% of its TFCSs that are NEMA TS 2 Type 1 and 30% of its TFCSs are NEMA TS 2 Type 2. The transportation controllers should be suitable for these cabinet systems.

Slide 56:

Learning Objective #3

Deriving User Needs From ATC 5201 Standard v06

Slide 57:

Learning Objective #3

Features From ATC 5201 Standard v06

2.3.1 Manage/Configure Applications

2.3.1.1 Install/Update Applications Software Quickly and Efficiently

2.3.1.2 Install/Upgrade O/S Quickly and Efficiently

2.3.1.3 Manage Clock/Calendar Function and Synchronize with Reliable External Source

2.3.1.4 Configure and Verify Parameters for Particular Local Applications

2.3.1.5 Upload/Download Data Block(s) as needed to Transfer Files and Accommodate Bulk Transfers of new Application Databases

Slide 58:

Learning Objective #3

Features From ATC 5201 Standard v06

2.3.1 Manage/Configure Applications (cont.)

2.3.1.6 Monitor and Verify Present Applications Status

2.3.1.7 Allow Operator Control of Application Execution

2.3.1.8 Facilitate the Long Term Storage of Data for Logging and other Data Storage Applications

Slide 59:

Learning Objective #3

Features From ATC 5201 Standard v06

2.3.2 Manage External Devices

2.3.2.1 Manage/Control a Variety of External Field Devices

2.3.2.2 Monitor the Output and Status of a Variety of External Field Devices

2.3.3 Facilitate Ease of Maintenance and Future Hardware/Software Updates

2.3.3.1 Maintain/Update Controller Hardware

2.3.3.2 Maintain/Update Controller Software

2.3.3.3 Support Diagnostics

Slide 60:

Learning Objective #3

Converting ATC Standard v06 Features Into User Needs

Feature

2.3.1.1 Install/Update Applications Software Quickly and Efficiently

This feature allows the local operator or a remote computer to install or update the application software resident on the ATC.

User Need

7.3.8 Install/Update Applications Software Quickly and Efficiently

The user needs to be able to install or update the application software resident on the controller unit. Users may or may not use application programs from the original manufacturer. All application programs need maintenance over time. Depending on the user's organization, application updates may be performed directly on the controller unit, from computer connection, or remotely through a network.

Slide 61:

Learning Objective #3

Converting ATC Standard v06 Features Into User Needs

User Need

7.3.8 Install/Update Applications Software Quickly and Efficiently

The user needs to have the ability to install or update the application software resident on the ATC unit. Users may or may not use application programs from the original manufacturer. All application programs need maintenance over time. Depending on the user's organization they may desire the option to perform these actions directly on the ATC unit or remotely through a computer or computer network.

Uniquely Identifiable? ✓
Major Desired Capability? ✓
Captures Rationale? ✓
Solution Free? ✓

Slide 62:

Learning Objective #3

Converting ATC Standard v06 Features Into User Needs

Feature

2.3.3.1 Maintain/Update Controller Hardware

This feature addresses the need for controller unit hardware to be maintained and updated as technology changes and additional functional and performance capabilities are needed.

User Need

7.7.2 Maintain/Update Controller Hardware

The user needs the controller unit to be upgradeable. Controller units are commonly in the field for seven years or more. This leads to obsolescence. The user needs to be able to upgrade the controller unit as technology changes and additional functional and performance capabilities are needed.

Slide 63:

Learning Objective #3

Converting ATC Standard v06 Features Into User Needs

User Need

7.7.2 Maintain/Update Controller Hardware

The user needs the controller unit to be upgradeable. Controller units are commonly in the field for seven years or more. This leads to obsolescence. The user needs to be able to upgrade the controller unit as technology changes and additional functional and performance capabilities are needed.

Uniquely Identifiable? ✓
Major Desired Capability? ✓
Captures Rationale? ✓
Solution Free? ✓

Slide 64:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

Slide 65:

Learning Objective #3

Which of the following is NOT a source of user needs for the specification development process?

Answer Choices

  1. Brand of controller equipment currently used by the agency
  2. Existing type of transportation field cabinet systems
  3. Existing strategic or regional plans
  4. Stakeholders

Slide 66:

Learning Objective #3

Review of Answers

A small graphical red and yellow check representing correct. a) Brand of controller equipment currently used by the agency
Correct! The fact that an agency is using a particular brand of equipment should not become a user need. With ATCs software applications will be portable across vendors.

A small graphical red and yellow X representing incorrect. b) Existing type of transportation field cabinet systems
Incorrect. The types of TFCSs being or planned to be used by the agency becomes a constraint user need for the controller equipment.

A small graphical red and yellow X representing incorrect. c) Existing strategic or regional plans
Incorrect. These higher level types of documents help provide the "vision" for the agency and are a source from which user needs can be derived.

A small graphical red and yellow X representing incorrect. d) Stakeholders
Incorrect. Stakeholders are the primary source of user needs for the transportation controller equipment (especially operational stakeholders).

Slide 67:

Summary of Learning Objective #3

Identify and Write User Needs for ATCs

Slide 68:

Learning Objective #4: Develop a Concept of Operations (ConOps)

Slide 69:

Learning Objective #4

Structure of a ConOps

Slide 70:

Learning Objective #4

Content of the ConOps

Slide 71:

Learning Objective #4

Content of the ConOps (cont.)

Slide 72:

Learning Objective #4

Content of the ConOps (cont.)

Slide 73:

Learning Objective #4

Content of the ConOps (cont.)

Slide 74:

Learning Objective #4

Content of the ConOps (cont.)

Slide 75:

Learning Objective #4

Organizing User Needs

Slide 76:

Learning Objective #4

Traceability of User Needs to Sources

UN ID User Need Source(s)
7.7.2 Maintain/Update Controller Hardware ATC5201(Sec4)
7.8.2.1 Traffic Signal Control Stakeholders
7.8.3.3 Increase Public Use of Transit Buses SDP(MM2)
7.8.6.1 Non-Vehicle Modes of Transportation SDP(MM5)

Slide 77:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

Slide 78:

Learning Objective #4

Which of the following is a TRUE statement?

Answer Choices

  1. There is only one way to organize user needs in a ConOps
  2. A ConOps for an ATC is written from a vendor's point of view
  3. Consider your specification when organizing your user needs
  4. A ConOps is just "busy work"

Slide 79:

Learning Objective #4

Review of Answers

A small graphical red and yellow X representing incorrect. a) There is only one way to organize user needs in a ConOps
Incorrect. There are various ways to organize user needs in a ConOps. The method used in this module is a suggestion.

A small graphical red and yellow X representing incorrect. b) A ConOps for an ATC is written from a vendor's point of view
Incorrect. A ConOps should be written from the user's point of view.

A small graphical red and yellow check representing correct. c) Consider your specification when organizing your user needs
Correct! Organizing the user needs in a ConOps, in a similar fashion to the way you will organize requirements in your specification, facilitates traceability and understanding.

A small graphical red and yellow X representing incorrect. d) A ConOps is just "busy work"
Incorrect. A ConOps focuses users to think of what they need and express it in terms they understand.

Slide 80:

Summary of Learning Objective #4

Develop a Concept of Operations (ConOps)

  1. Structure of a ConOps
  2. Organizing user needs
  3. Traceability of user needs to sources

Slide 81:

What We Have Learned

  1. ATC 5201 Standard v06 and the ATC 5401 application programming interface_ work together so that ATC units can run multiple application programs simultaneously.
  2. A systems engineering specification development process provides traceability from user needs in a ConOps to requirements in the Agency Specification.
  3. Well-written user needs are uniquely identifiable, a major desired capability, captures the rationale, and are solution free .
  4. Showing the sources of user needs in the ConOps can demonstrate the connection of the user needs to the agency's regional and strategic plans.

Slide 82:

Resources

Slide 83:

Next Course Module

A307b: Understanding Requirements for Advanced Transportation Controllers Based on ATC 5201

Standard v06

Concepts taught in Module (Learning Objectives):

  1. Describe a systems engineering based ATC specification development process
  2. Write requirements for ATCs based on user needs
  3. Describe a specification based on ATC 5201 Standard v06
  4. Verify an ATC procurement specification

Slide 84:

Questions? A placeholder graphic image with word Questions? at the top, and an image of a lit light bulb on the lower right side.