Module 29 - A207b

A207b: Building an ITS Infrastructure Based on the Advanced Transportation Controller (ATC) 5201 Standard (Part 2 of 2)

HTML of the PowerPoint Presentation

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

Slide 1:

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

Ken Leonard, Director

ITS Joint Program Office

Ken.Leonard@dot.gov

(Extended Text Description: Intro Slide: Screen capture snapshot of RITA website - for illustration only. Below this image is a link to the current website: https://www.its.dot.gov/pcb - this screen capture snapshot shows an example from the RITA website from April 2013. At the top of the page it shows the RITA logo with the text U.S. Department of Transportation Research and Innovative Technology Administration - 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 sections entitled Available E-Training (free), Free ITS Training and T3 Webinars. Again, this image serves for illustration only. The current website link is: https://www.its.dot.gov/pcb)

ITS PCB Home

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

"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 Ken Leonard, 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 yourself.

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 ITS PCB Home

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

Slide 3:

Slide 4:

A207b:

Building an ITS Infrastructure Based on the Advanced Transportation Controller (ATC) 5201 Standard Part 2 of 2

Slide 5:

Instructor

Ralph W. Boaz

President

Pillar Consulting, Inc.

San Diego, CA, USA

Slide 6:

Target Audience

• Engineering staff
• Traffic management center/operations staff
• Traffic signal maintenance staff
• System developers
• Software developers
• Manufacturers
• Private and public sector users

Slide 7:

Recommended Prerequisite(s)

• 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

Slide 8:

Recommended Prerequisite(s) (cont.)

• A203 Writing Requirements When ITS Standards Do Not Have SEP Content
• C101: Introduction to the Communications Protocols and Their Uses in ITS Applications
• A207a: Building an ITS Infrastructure Based on the ATC 5201 Standard Part 1 of 2

Slide 9:

Curriculum Path (Non-SEP)

(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 of the modules. There are 7 boxes in total; two rows of 3 boxes and a row with 1 box. The first box is labeled "I101 Using ITS Standards: An Overview." An arrow from this box connects it to a box labeled "A101 Introduction to Acquiring Standards-Based ITS Systems." 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 row labeled "A201 Details on Acquiring Standards-based ITS Systems." An arrow from this box connects it to a box labeled "A202 Identifying and Writing User Needs When ITS Standards Do Not Have SEP Content." An arrow from this box connects it to a box labeled "A103 Introduction to ITS Standards Requirements Development." An arrow from this box connects it to a box located at the start of the next row labeled "A203 Writing Requirements When ITS Standards Do Not Have SEP Content." An arrow from this box connects it to a box labeled "C101 Intro. To Comm. Protocols and Their Use in ITS Applications." An arrow from this box connects it to a box labeled "A207a Building an ITS Infrastructure Based on the ATC 5201 Standard Part 1 of 2." An arrow from this box connects it to a box located at the start of the next row labeled "A207b Building an ITS Infrastructure Based on the ATC 5201 Standard Part 2 of 2." The last two boxes are highlighted indicating that they represent the current modules in the series.)

Slide 10:

Learning Objectives

1. Explain the purpose of the ATC Family of Standards
2. Identify the basic components and operation of iransportation Field Cabinet Systems
3. Identify the features of the ATC 5201 Standard
4. Describe the ATC 5201 architecture
5. Describe how the ATC 5201 Standard works with other ITS standards
6. Specify ATC equipment for system and equipment procurements

Slide 11:

Learning Objective #3 - Identify the Features of the ATC 5201 Advanced Transportation Controller Standard

• Problem with traditional transportation controller architectures
• Structure of the ATC 5201 Standard
• Features for ATC controller units

Slide 12:

Learning Objective #3

Problem with Traditional Transportation Controller Architectures

(Extended Text Description: This slide, titled "Problem with Traditional Controller Architectures," contains an X/Y type of graph. The X axis is an arrow that begins at the bottom left of the slide and extends horizontally to the bottom right of the slide. The Y axis is an arrow that begins at the bottom left of the slide and extends upward to the upper left of the slide. Below the X axis are evenly distributed labels "1980," "1990," "2000," "2010" and "2020." To the left of the Y axis is the label "INCREASING CAPABILITY" which runs from the lower part of the Y axis towards the top of the Y axis. There is curving arrow that begins about 15% of the way up the Y axis extending to the right with a gradual slope upwards until it reaches the 2020 point of the X axis at about the 20% of the height of the Y axis. At the end of this curved arrow is a label "Traditional Capability Curve." There are three traffic signal heads on the curve at about the 1975, 1995 and 2005 points of the X axis.

There is a second curving arrow that begins about 15% of the way up the Y axis extending to the right with a radical slope upwards until it reaches nearly the 2020 point of the X axis at about the 100% of the height of the Y axis. At the end of this curved arrow is a label "Application Demand Curve." Along this curve are three rectangular graphics. The first two rectangles are larger than the third. The second rectangle slightly hides the upper right corner of the first rectangle. The third rectangle is about 20% of the size of the first two and is located towards the top right of the slide. The contents of these graphics are as follows:

• The first rectangular graphic is centered about the 1995 point of the X axis. It contains a graphic of a building next to a grid of streets. The grid is made up of four north-south streets and four west-east streets. Near most of the intersections of the streets is a small aluminum cabinet. There are dotted lines going from the building to the cabinets. The graphic is labeled "NTCIP."
• The second rectangular graphic is centered about the 2010 point of the X axis. It contains a small X/Y type of graph. Below the X axis are evenly distributed labels "16:00," "17:00," "18:00," "19:00" and "20:00." To the left of the Y axis are evenly spaced labels (starting from the bottom upward) "500," "1000," "1500," and "2000." There is an irregular line starting about the 500 point on the Y axis and extending to the right. The high point is at the 2000 mark of the Y axis about at the 18:30 point of the X axis. The line ends at a height approximately 150 on Y axis at the 20:00 point on the X axis. The graphic is labeled "ADAPTIVE CONTROL."
• The third rectangular graphic is located at the 2015 point of the X axis. It contains a graphic of a car next to an aluminum cabinet. The graphic is labeled "CONNECTED VEHICLE / V2I."

At the middle right of the slide is a label "Technology Gap." It has lines from the label to the end of the first line and to the end of the second line.)

Graphics: Ralph W. Boaz

Slide 13:

Learning Objective #3

Transportation Controller Comparative Performance

(Extended Text Description: This slide, titled "Transportation Controller Comparative Performance," contains a bar graph. The vertical axis has values "0," "50," "100," "150," "200," "250," "300," "350," "400," "450" and "500." There are thin lines extending from the numerical points on the vertical axis across the chart. To the left of the numbers is a label "MIPS*." The horizontal axis has labels beneath it for three vertical bars as follows: "Model 170 (1982)," "Model 2070 (1998)" and "ATC v5/6 (2013) Minimum/Available." The vertical bar on the left is barely visible above the 0 point on the vertical axis. It has a label, "0.2 MIPS*," centered on top of the bar. The center bar can be seen slightly higher than the previous but still new the 0 point on the vertical axis. It has a label "4.5 MIPS*," centered on top of the bar. The bar to the right extends the entire height of the chart to the 500 point of the vertical axis. It has a label "500 MIPS*," centered on top of the bar. There is an additional label, "60 MIPS*," identifying a point on the right bar just above the 50 point of the vertical axis. There is text below the entire chart as follows: "* Millions of Instructions Per Second.")

Graphics: Ralph W. Boaz

Slide 14:

Learning Objective #3

Uses for ATC Controller Units Identified

• 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
  • Safety
  • Eco Driving

Slide 15:

Learning Objective #3

Purpose of the ATC Family of Standards

• Provide a general purpose field computing platform for transportation applications that is:
  • Open Architecture
  • Modular
  • Multi-Process/Multi-Application
  • Can Grow with Technology
  • Upgrade for Legacy Transportation Field Cabinet Systems (TFCSs)

Slide 16:

Learning Objective #3

Structure of the ATC 5201 Standard

Section 1 Introduction

Section 2 Overall Description

Section 3 Functional Requirements

Section 4 Engine Board Details

Section 5 Communication Interface Details

Section 6 Physical and User Interface Details

Section 7 Parallel and Serial I/O Details

Section 8 Environmental and Test Procedures

Slide 17:

Learning Objective #3

Structure of the ATC 5201 Standard (cont.)

Section 9 Performance and Material Requirements

Section 10 Quality Control

Appendix A Linux Operating System and Minimum Kernel Configuration

Appendix B Required Device Driver Interfaces

Appendix C Historical Background of Traffic Controllers

Slide 18:

Learning Objective #3

Major Transportation Field Cabinet Systems (TFCSs)

(Extended Text Description: This slide, titled "Major Transportation Field Cabinet Systems (TFCSs) (cont.)," consists of large pictures of two different TFCS architectures. The intent of the slide is to highlight some of the major TFCS architectures in use today. The first image is a picture of a TFCS that is about 4 feet tall and 2 ½ feet wide with the door open and out of view. It has two shelves approximately 1/3 and 2/3 down from the top of the cabinet. On the top shelf sit two cuboid electronic devices. The cuboid device on the left of the shelf is wider that it is tall and appears to be an assembly of other thinner devices that sit inside it. The devices inside each have small lights going down the middle of them. The device on the right of the shelf is taller than it is wide. It has lights along the lower left side of the device. On the second shelf, there is a single larger device that appears to be about 1 foot tall and 1 3/4 feet wide. It has a small screen on its upper face and keys below and to the right of the screen. Below the upper face is a row of four thick round cables attached. There is also a thinner cable attached to a D-type connector to the right. The lower internal back area of the cabinet has an electrical panel with numerous wires attached to it. There is cabling and wiring going throughout the cabinet. The label below this picture says "NEMA TS 1.")

NEMA TS 1

(Extended Text Description: The second images is a picture of a TFCS that is about 5 1/2 feet tall and 2 feet wide with the door open and out of view. The interior of the cabinet contains a 19 inch wide standard electronic equipment rack. The side metal rails of the rack 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 with screws.

• The first (top) section is a single rectangular device that takes up approximately 11 inches of vertical cabinet space. The device has a handwritten piece of paper (writing is illegible) covering about 4 inches of the left side of the device. There is a key pad approximately 3 inches by 3 inches with 16 equidistant square keys just right of the paper. The remainder of the front of this device has assorted small switches and electronic connectors in various locations on the right side of the device.
• The second section takes up approximately 11 inches of vertical cabinet space. It consists of two rows of similar horizontal assemblies about 5 1/2 inches tall each. The assemblies are horizontal racks that hold devices that sit in groves of the rack. The devices are rectangular approximately 5 1/2 inches tall and 1 inch wide and fit vertically within the assemblies. There is one rectangular device that is twice the width of the others but the same height. The rectangular devices have small lights and switches on them and there are wires of various sizes connecting them to other points in the cabinet. There are 9 rectangular devices in the upper assembly. There are 7 rectangular devices in the lower assembly including the one with the double width. The rectangular devices are unevenly spaced within the assemblies.
• The third section takes up approximately 11 inches of vertical cabinet space and is made up of three assemblies distributed horizontally across the section. The first assembly on the left is approximately 9 inches wide. It consists of 8 light switches and two three-pronged electrical outlets. There are assorted mounting screws and a toggle switch on the assembly. The middle assembly takes up approximately 4 inches wide and contains two rectangular devices approximately 4 inches tall and 1 3/4 inches wide. The assembly on the right side of the section is approximately 6 inches wide. It contains two small lights, two small knobs, and a thin handle that is about three inches tall in the center of the assembly.
• The fourth section takes up approximately 18 inches of vertical cabinet space. Aligned down the left side of the section there are 6 evenly spaced glass covered components approximately 2 inches tall and 3 inches wide. To the right of the glass covered components there are three similar horizontal assemblies that are about 5 1/2 inches tall each. The assemblies are horizontal racks that hold devices that sit in groves of the rack. The devices are rectangular approximately 4 inches tall and 2 inches wide and fit vertically within the assemblies. These devices are different than those in the racks described for the second section. The top two racks are slightly shorter than the third rack which connects to the right rail of the cabinet. There are 6 devices in the first assembly, 6 devices in the second assembly and 2 in the third assembly. On the right edge of the section there is a taller rectangular device that is approximately 9 1/2 inches tall and 1 1/2 inches wide. This device fits on top of the third rack and between the upper two racks and the right rail of the cabinet.

)

Model 33X

Photos: Econolite and Ralph W. Boaz

Slide 19:

Learning Objective #3

Major Transportation Field Cabinet Systems (TFCSs) (cont.)

(Extended Text Description: This slide, titled "Major Transportation Field Cabinet Systems (TFCSs) (cont.)," consists of large pictures of two different TFCS architectures. The intent of the slide is to highlight the major TFCS architectures in use today. The first image is a picture of a TFCS that is about 4 ½ feet tall and 3 ½ feet wide with the door open and out of view. It has two shelves approximately 1/6 and 2/5 down from the top of the cabinet. On the top shelf sit two cuboid electronic assemblies that appear to be racks for holding for other devices. On the middle shelf are two larger cuboid devices with one being about 1 1/2 feet long and 1 foot high and the other about 1/2 feet wide and 1 foot tall. The former is sitting in the middle of the shelf. The latter is sitting on the right of the shelf. The device sitting in the middle of the shelf has a Liquid Crystal Display (LCD) screen and an assortment of keys to the right of the screen. The device on the right of the shelf has lights running down the left front side of the unit. There are cables running between all of the devices and assemblies. The lower remainder of the cabinet has numerous smaller devices with lights on them that appear to be plugged into an electrical panel in the back of the cabinet interior. The label below this picture says "NEMA TS 2 Cabinet.")

NEMA TS 2 Type 1

(Extended Text Description: The second image is a picture of a TFCS that is about 5 1/2 feet tall and 2 feet wide with the door open and out of view. The interior of the cabinet contains a 19 inch wide standard electronic equipment rack. The side metal rails of the rack run along the left and right sides of the front of the cabinet interior. There are six sections of equipment that extend edge to edge of the cabinet interior attaching to the side rails of the rack with screws. The top section is a single device about 4 inches tall with lights. The second section contains a large single device about 7 inches high. It has a Liquid Crystal Display (LCD) screen and two key pads below the screen. The third section is an assembly of devices. There appears to be common light switches running from the left side to about 2/3 of the way across the assembly. There are three smaller and separate devices on the right 1/3 of the assembly about 2 inches wide each. Two of them are identical. The third device has a handle running down the middle of it. The forth section is an assembly about 10 1/2 inches high and has two rows. The top row has 6 slender devices (about 1 inch wide) that appear to be plugged into the assembly. The right side each row of this assembly contains device that is about 2 inches wide. Most of this assembly appears empty. The fifth section is an assembly that has two rows. It contains fourteen smaller devices with lights on them about two inches wide. There are 6 on the top row and 8 on the lower row. There are two additional devices on the right side of the first row that look to be 3 inches wide. The sixth section appears to be storage and wiring. The label below this picture says "ITS Cabinet v01.")

ITS Cabinet v01

Photos: Ralph W. Boaz

Slide 20:

Learning Objective #3

Features for ATC Controller Units

Major Operational Features

• Manage/Configure Applications
• Manage External Devices
• Facilitate Ease of Maintenance and Future Hardware/Software Updates

Slide 21:

Learning Objective #3

Manage/Configure Controller Applications

2.3.1.1 Install/Update Applications Software Quickly and Efficiently

2.3.1.2 Install/Upgrade Operating System (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

Slide 22:

Learning Objective #3

Manage/Configure Controller Applications (cont.)

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

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 23:

Learning Objective #3

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

Slide 24:

Learning Objective #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 25:

Slide 26:

Learning Objective #3

Which of the following is NOT a purpose of the ATC standards program?

Answer Choices

1. General purpose field computing platform
2. Grow with technology
3. Open architecture
4. Compact

Slide 27:

Learning Objective #3

Review of answers

a) General purpose field computing platform
Incorrect. Defining a general purpose field computing platform for the transportation community is the primary purpose of the ATC standards program.

b) Grow with technology
Incorrect. Being able to grow with technology is a purpose of the ATC standards program mitigating obsolescence.

c) Open architecture
Incorrect. Being an open architecture so that anyone can build products for it is a purpose of the ATC standards program.

d) Compact
Correct. Being compact is not a purpose of the ATC standards program, however, the modular architecture is conducive to creating units of various sizes.

Slide 28:

Learning Objective #3

Which of the following is NOT a major feature of ATC controller units?

Answer Choices

1. Manage/Configure applications
2. Windows operating system
3. Manage external devices
4. Facilitate ease of maintenance and future hardware/software updates

Slide 29:

Learning Objective #3

Review of answers

a) Manage/Configure applications
Incorrect. Managing and configuring application programs are major features of ATC controller units.

b) Windows operating system
Correct. A Windows operating system is not a major feature of the ATC controller. A Linux O/S is used.

c) Manage external devices
Incorrect. Being able to manage external devices is a major feature of ATC controller units.

d) Facilitate ease of maintenance and future hardware/software updates
Incorrect. Making it easy to maintain controller units and make updates are major features of ATC controllers.

Slide 30:

Summary of Learning Objective #3

Identify the Features of the ATC 5201 Advanced Transportation Controller Standard

• Problem with traditional transportation controller architectures
• Structure of the ATC 5201 standard
• Features for ATC controller units

Slide 31:

Learning Objective #4 - Describe the ATC 5201 Architecture

• Key elements of the ATC 5201 architecture
• Describe how the ATC 5201 Standard and ATC 5401 Standard work together
• ATC software portability, compatibility, and interchangeability

Slide 32:

Learning Objective #4

Key Elements of the ATC 5201 Architecture

• Based on an "Engine Board" concept
• Computational capability can grow with technology
• Uses Linux operating system
  • Open source, multi-process, multi-application
• Mechanical requirements only for physical interfaces
• Works with all major transportation field cabinet system standards and specifications
• Source code portability for application software
  • Single application program only unless ATC 5401 Application Programming Interface is specified

Slide 33:

Learning Objective #4

ATC Engine Board Concept

(Extended Text Description: This slide, titled "ATC Engine Board Concept," is an enlarged graphic representation of a circuit board. It is 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 34:

Learning Objective #4

Engine Board Interfaces

(Extended Text Description: This slide, titled "Engine Board Interfaces," is an enlarged graphic representation of a circuit board. It is twice as tall as it is wide. In the bottom left of the board is the label "ENGINE BOARD." There are eleven identically shaped smaller rectangles representative of electronic interfaces for an Engine Board. These rectangles are about 5% of the engine board in height and about 5 times as wide as they are tall. There are five rectangles centered on the left edge of the engine board and six rectangles centered on the right edge of the engine board. The rectangles on the right are distributed evenly along the right edge of the Engine Board. The five rectangles on the left are distributed so that they are at the same heights as the first five rectangles on the right. All of the rectangles have a short line extending out of the left side, for the rectangles on the left, and out of the right side for the rectangles on the right. The five rectangles on the left are labeled "CONSOLE," "SERIAL PORT 1," "SERIAL PORT 2," "SERIAL PORT 3," and "FRONT PANEL" (top to bottom). The six rectangles on the right are labeled "FIELD I/O DEV 1," "FIELD I/O DEV 2," "USB MEM DEV," "DATAKEY," "ETHERNET 1," and "ETHERNET 2" (top to bottom). To the left of the graphic is a label "TO HOST MODULE" running vertically bottom to top. To the right of the graphic is a label "TO HOST MODULE" running vertically top to bottom.)

Graphics: Ralph W. Boaz

Slide 35:

Learning Objective #4

Example Engine Board

(Extended Text Description: This slide, titled "Example Engine Board," is photograph of an actual 5"W X 4"H Engine Board. There are various electronic chips on the board that have a rounded rectangle graphics surrounding them. The rounded rectangles have curved lines extending outside the picture with labels to identify the chips on the Engine Board. Just left of center of the board is a large chip that is approximately 1"W X 1"H. It is labeled "CPU." To the left and slightly higher than the CPU are two chips that are approximately .33"W X .67"H. The chips are aligned side by side. They are labeled "DRAM." Below the DRAM are two other chips approximately .5"W X .5"H each. The chips are side by side. They are labeled "Flash Memory." Below the left Flash Memory chip is a chip approximately .25"W X .25"H. The chip is labeled "SRAM." Below the right Flash Memory chip is a chip approximately .25"W X .25"H. The chip is labeled "USB." To the right of the CPU is a chip approximately .5"W X .5"H. The chip is labeled "ENET 1&2." Right of the ENET 1&2 chip, near the right edge of the Engine Board, is a chip approximately .25"W X .25"H. It is labeled "RTC." Near the right lower corner of the Engine Board is a chip approximately .33"W X .67"H. It is labeled "Serial I/O.")

Graphics: Ralph W. Boaz Photo: Intelight

Slide 36:

Learning Objective #4

Linux Board Support Package (BSP) and Layered Architecture Allows Any Qualified Processors to be Used on an Engine Board

(Extended Text Description: This slide, titled "Linux Board Support Package (BSP) and Layered Architecture Allows Any Qualified Processors to be Used on an Engine Board," is a graphic. At the bottom of the graphic centered on the slide it appears to be the side view of an Engine Board graphic as described in Slide 32 (no labels shown). The Engine Board is about 60% the width of the slide. Above the Engine Board is a large rectangle that is as wide as the Engine Board and twice the height. It is labeled "LINUX OS & DEVICE DRIVERS." Above the large rectangle is a smaller rectangle that is approximately 1/3 the width and 1/2 the height of the large rectangle. It is labeled "APPLICATION SW." Above this smaller rectangle is a slightly smaller rounded rectangle. It is approximately 1/3 the width and the same height as the rectangle below it. It is labeled "OPERATIONAL USER." All of the rectangles are centered above the Engine Board. Between the Engine Board and the large rectangle and between each of the rectangles above them are single heavy dashed lines running in parallel horizontally from a point just beyond the left side of the engine board to nearly the right side of the slide (total of three lines). Between the Engine Board and the large rectangle and between each of the rectangles above them are heavy solid double arrows pointing upwards and downwards. Below each dashed line, to the right of the Engine Board and rectangles, are the labels "APPLICATION LAYER," "ATC BOARD SUPPORT PACKAGE LAYER" and "HARDWARE LAYER" (top to bottom). To the left of the Engine Board and large rectangle is a label "HARDWARE & OS DEFINED BY ATC 5201 STANDARD" set in a rounded rectangle. Adjacent to the right of the rounded rectangle and left of the Engine Board is a large left bracket indicating that the label in the rounded rectangle applies to the Engine Board and large rectangle.)

Graphics: Ralph W. Boaz

Slide 37:

Learning Objective #4

Controllers Meeting Other Standards Built Using the Engine Board

(Extended Text Description: This slide, titled "Controllers Meeting Other Standards Built Using the Engine Board," is a graphic illustrating how the Engine Board can be used to build controller units that are of different designs. The Engine Board shown in Slide 32 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 Engine Board 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 38:

Learning Objective #4

Engine Board Hardware Upgrade Capability

• Engine boards have identical pinout - future boards may plug into existing host boards
• Computational capability can grow with technology
• No hardware changes required to the rest of the controller unit or changes to the TFCS

Slide 39:

Learning Objective #4

Examples of ATC Controller Units

(Extended Text Description: This slide, titled "Examples of ATC Controller Units," contains five 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 three units on the top half of the slide and two units on the bottom half. They are described below going from the top left in a clockwise fashion.

• Controller 1 is facing forward. The unit is 14.84" W X 6.13" D X 8.50" H. On the left 1/8 of the controller there are electronic cable connectors rotated 90 degrees so they are shown taller than wider. These include two USB ports, four RJ45 jacks, a 25 pin Sub D connector, a 9 pin Sub D connector and a 15 pin Sub D connector. On the lower 1/3 of the controller and to the right of the electronic cable connectors are four circular connectors evenly spaced across the remaining width of the controller. They are labeled left to right "D," "C," "B" and "A." To the right of the A connector is a plastic screw about .25" in diameter. Above the D and C connectors is a LCD screen that takes up about 50% of the height and 40% of the width of the controller. To the right of the screen above the B and A connectors is a keypad with 24 keys. One of the keys is a large diamond shape which appears to have arrows on its corners.
• Controller 2 is angled to the right. The unit is 10.75" W X 7.75" D X 10.5" H. On the lower 1/3 of the controller are four circular connectors evenly spaced across the width of the controller. They are labeled left to right "A," "B," "C" and "D." To the left of the A connector are two small knobs. Above the circular connectors, on the left 1/8 of the controller are electronic cable connectors rotated 90 degrees so they are shown taller than wider. These include four RJ45 jacks, two 25 pin Sub D connectors, a 9 pin Sub D connector and a 15 pin Sub D connector. There are numerous small LEDs adjacent to the RJ45 jacks. Centered in the upper 1/3 area of the controller is an LCD screen. Below the screen are additional electronic connectors including four USB ports, six RJ45 jacks. To the right of the LCD screen is a keypad with 28 keys. Below the keypad and above the D connector is a knob. Facing the left side of the controller are two panels (1.5" W X 7" H each) which are held in place by two round thumbscrews (each).
• Controller 3 is angled to the left. The unit is 10" W X 10.5" D X 7" H. There is an LCD screen on the upper left portion of the controller. It is about 30% of the height and 40% of the width of the controller. To the right of the LCD screen is a keypad with 28 keys four of which appear to be arrows. Below the LCD screen is a knob and four RJ45 jacks. Below the knob is a circular connector. To the left of the circular connector is knob and a small rectangular toggle switch. Beneath the RJ45 jacks are a 15 pin Sub D connector and three 9 pin Sub D connectors. To the right of the 9 pin Sub D connector and aligned with the right edge of the key pad are four USB ports. To the right of the keypad and USB ports is a panel (1.5" W X 7" H) which is held in place by two round thumbscrews.
• Controller 4 is facing forward. The unit is 17.04" W x 11.09" D x 10.03" H. There is an LCD screen on the upper left portion of the controller. It is about 25% of the width and height of the controller. To the right of the LCD screen is a keypad with 30 keys four of which appear to be arrows. Below the LCD screen are four RJ45 jacks and a USB port. Below the key pad are a 9 pin Sub D connector, a 15 pin Sub D connector and a 25 pin Sub D connector. To the right of the keypad are two panels (1.5" W X 7" H each) which are held in place by two round thumbscrews (each). Below the RJ45 jacks and Sub D connectors are four circular connectors evenly spaced across 75% if the width of the controller. They are labeled left to right "A," "B," "C" and "D." To the right of the D connector and below the two panels are a rectangular toggle switch, two plastic screws about .25" in diameter, a group of four LEDs and a plastic key.
• Controller 5 is angled to the right. The unit is 19" W x 10.5" D x 7" H. There is an LCD screen on the upper left portion of the controller. It is about 25% of the width and 50% of the height of the controller. To the right of the LCD screen is a keypad with 32 keys. In the lower left front of the controller are two plastic screws about .25" in diameter. To the right of the screws below the left side of the LCD screen are two RJ45 jacks. To the right of the RJ45 jacks aligned with the right side of the LCD screen is a USB port. Below the key pad is a 15 pin Sub D connector, two 9 pin Sub D connectors, and a 25 pin Sub D connector. To the right of the 25 pin Sub D connector is a metal posted toggle switch. On the left and right sides of the controller are wire pull handles that are about 50% of the height of the controller aligned and centered vertically.

)

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

Slide 40:

Slide 41:

Learning Objective #4

Which of the following is critical to being able to replace an Engine Board with a more powerful Engine Board in the future?

Answer Choices

1. Identical pinout
2. New host module
3. Same processor family
4. Same Engine Board manufacturer

Slide 42:

Learning Objective #4

Review of Answers

a) Identical pinout
Correct. Identical pinout is essential to allow a new Engine Board to replace a previous one.

b) New host module
Incorrect. Generally, the Host Module of the existing controller can remain the same although, over time, it is conceivable that a new Host Module may be necessary.

c) Same processor family
Incorrect. Generally, the Linux BSP allows any qualified processor to be used on an Engine Board.

d) Same Engine Board manufacturer
Incorrect. Any manufacturer that adheres to the ATC 5201 Standard can produce replacement Engine Boards.

Slide 43:

Learning Objective #4

Describe How the ATC 5201 Standard and ATC 5401 Standard Work Together

ATC 5401 Application Programming Interface (API) Standard

• Provides a "window-like" interface to support the use of multiple application programs running concurrently on a single controller
• Allows application software to be written that can operate in any ATC controller unit in any major TFCS
• Multiple application programs can share the resources of the controller and transportation field cabinet system
  • Front Panel, Field Inputs/Outputs, Real-Time Clock

Slide 44:

Learning Objective #4

Application Programming Interface

(Extended Text Description: This slide, titled "Application Programming Interface," is a graphic illustrating how application programs can share the field outputs (load switches) of a TFCS. The lower left of the slide is a graphic representation of the ITS Cabinet v02 architecture. It shows 6 rectangles about 20% the width of the slide and stacked vertically so that together they are about 50% of the height of the slide. The first (top) rectangle is labeled "CONTROLLER." The second rectangle is labeled "INPUT CAGE." The right 10% of the INPUT CAGE is sectioned and labeled SIU. The third rectangle is identical to the second. The fourth rectangle is labeled "PWR DISTRIBUTION ASSEMBLY." The right 10% of the PWR DISTRIBUTION ASSEMBLY is sectioned and labeled CMU. The fifth rectangle is labeled "OUTPUT CAGE." The right 20% of the OUTPUT CAGE is sectioned into two parts with each part representing 10% of the OUTPUT CAGE. These subsections are labeled "AMU" and "SIU." The sixth rectangle is identical to the fifth. There is a heavy arrow extending out the left side of the CONTROLLER and then points upward to a large graphic representation of an LCD screen of a controller. This 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:

• "FRONT PANEL MANAGER VER 1.00"
• "SELECT WINDOW: 0-F SET DEFAULT: *,0-F"
• "0 Ramp Meter Prgrm 1*Signal Program"
• "2 Emergency Mngmnt 3 Data Distributor"
• "4 System Checker     5"
• "6                               7"
• "8                               9"
• "[MORE - UP/DN ARROW] [CONFIG INFO-NEXT]"

There is a heavy arrow extending out the right side of the OUTPUT CAGE and then points upward to an enlargement of the OUTPUT CAGE which is about 60% the length of the slide. This enlargement shows that the majority of the OUTPUT CAGE is made up of load switches which are represented as sections of the OUTPUT CAGE with three LEDs aligned vertically and centered within the load switch. Seven load switches are shown followed by the AMU and SIU. There is an oval highlighting the first two load switches. There is an oval highlighting the third load switch. There is an oval highlighting the last four load switches. There is an arrow extending from the "Ramp Meter Prgrm" text in the LCD graphic to the first oval. There is an arrow extending from the "Emergency Mngmnt" text in the LCD graphic to the second oval. There is an arrow extending from the "Signal Program" text in the LCD graphic to the third oval.)

Graphics: Ralph W. Boaz

Slide 45:

Learning Objective #4

ATC Layered S/W Architecture

(Extended Text Description: This slide, titled "ATC Layered S/W Architecture," illustrates the layered architecture defined by the ATC 5201 and ATC 5401 standards. At the bottom of the graphic and centered on the slide is a side view of an Engine Board graphic as described in Slide 32 (no labels shown). The Engine Board is about 60% the width of the slide. Above the Engine Board is a large rectangle that is as wide as the Engine Board and twice the height. It is labeled "LINUX OS & DEVICE DRIVERS." Above the LINUX OS & DEVICE DRIVERS rectangle is a smaller rectangle that is approximately 1/3 the width and 1/2 the height of the LINUX OS & DEVICE DRIVERS rectangle. It is labeled "API" and centered over the LINUX OS & DEVICE DRIVERS rectangle. Above the API rectangle is another rectangle of the same width and height. It is labeled "APPLICATION SW." The APPLICATION SW rectangle is aligned to the right so that only 25% of the APPLICATION SW rectangle is over the API rectangle. Above the APPLICATION SW rectangle is a slightly smaller rounded rectangle. It is approximately 1/3 the width and the same height as the APPLICATION SW rectangle below it. It is labeled "OPERATIONAL USER" and it is centered above the API rectangle, the LINUX OS & DEVICE DRIVERS rectangle and the Engine Board. Between the Engine Board and the LINUX OS & DEVICE DRIVERS rectangle and between each of the rectangles above them are single heavy dashed lines running in parallel horizontally from a point just beyond the left side of the engine board to nearly the right side of the slide (total of four lines). Between the Engine Board and the LINUX OS & DEVICE DRIVERS rectangle and between the LINUX OS & DEVICE DRIVERS rectangle and the API rectangle are heavy solid double arrows pointing upwards and downwards. Between the right side of the API rectangle and the left side of the APPLICATION SW rectangle is a heavy solid double arrow pointing upwards and downwards. Between the right side of the API rectangle and the left side of the APPLICATION SW rectangle is heavy solid double arrow pointing upwards and downwards. Between the right side of the LINUX OS & DEVICE DRIVERS rectangle and the right side of the APPLICATION SW rectangle is a heavy solid double arrow pointing upwards and downwards. Centered between the API rectangle and the OPERATIONAL USER rounded rectangle is a heavy solid double arrow pointing upwards and downwards. There is a heavy solid double arrow pointing to the right side of the OPERATIONAL USER rounded rectangle and making a 90 degree turn downward to the top of the APPLICATION SW rectangle. Below each dashed line, to the right of the Engine Board and rectangles, are the labels "APPLICATION LAYER," "API SOFTWARE LAYER," "ATC BOARD SUPPORT PACKAGE LAYER" and "HARDWARE LAYER" (top to bottom). To the left of the Engine Board and LINUX OS & DEVICE DRIVERS rectangle is a label "HARDWARE & OS DEFINED BY ATC 5201 STANDARD" set in a rounded rectangle. Adjacent to the right of the rounded rectangle and left of the Engine Board is a large left bracket indicating that the label in the rounded rectangle applies to the Engine Board and LINUX OS & DEVICE DRIVERS rectangle. To the left of the API rectangle is a label "INTERFACE & BEHAVIOR  DEFINED BY ATC 5401 STANDARD" set in a rounded rectangle. Adjacent to the right of the rounded rectangle and left of the Engine Board is a smaller left bracket indicating that the label in the rounded rectangle applies to the API rectangle.)

Graphics: Ralph W. Boaz

Slide 46:

Learning Objective #4

ATC Software Portability, Compatibility, and Interchangeability

Portability

• The ease with which applications software and data can be transferred from one application platform to another
• Ability to move, with minimal changes, application software between computers

Slide 47:

Learning Objective #4

Portability Achieved Through Compiling and Linking Software

(Extended Text Description: This slide, titled "Portability Achieved Through Compiling and Linking Software," illustrates the method used to make an application program portable to ATC Engine Boards built by different vendors. At the top of the graphic is a rounded rectangle about 1/4 the width and 1/10 the height of the slide. It is centered with the label "Application Software." At the bottom of the graphic are three Engine Boards as described in Slide 32 except they are about 1/8 the width and 1/10 the height of the slide. They are evenly distributed across the bottom portion of the slide. Beneath the three Engine Boards are three corresponding labels "ATC Engine Board From Vendor 1," "ATC Engine Board From Vendor 2" and "ATC Engine Board From Vendor 3." There are three solid arrows pointing downward from the bottom of the rounded rectangle to the three Engine Boards. There is an oval that overlays the middle areas of the arrows (not the points connecting to the rounded rectangles or the Engine Boards). It is about 1/2 the width of the slide and 1/5 the height. It is centered on the slide and it is outlined with a dashed line. It is labeled "Compiling and Linking Using Application Source Code and API Software Libraries.")

Graphics: Ralph W. Boaz

Slide 48:

Learning Objective #4

ATC Software Portability, Compatibility, and Interchangeability

Compatibility

• Two or more systems or components perform their required functions while sharing the same environment
• The two components (or systems) do not need to communicate with each other

Slide 49:

Learning Objective #4

Compatibility Achieved Through Linux O/S and API Software

(Extended Text Description: This slide, titled "Compatibility Achieved Through Linux O/S and API Software," illustrates how the Linux operating system and API Software allow application programs to be compatible on a single Engine Board. At the top of the graphic are three rounded rectangles about 1/8 the width and 1/10 the height of the slide. They are closely spaced and evenly distributed in the center of the slide horizontally. They are labeled "Application Software 1," "Application Software 2" and "Application Software 3," respectively. At the bottom of the graphic is an Engine Board as described in Slide 32 except they it is about 1/8 the width and 1/10 the height of the slide. It is centered horizontally. Beneath the Engine Boards is a label "ATC Engine Board From Vendor."  Centered above the Engine Board and below the three Application Software rectangles is a rounded rectangle that is about 1/8 the width and 1/10 the height of the slide. It is labeled "Linux O/S and API Software." There is a heavy double arrow from the center bottom Application Software 1 rounded rectangle to the upper left corner of the Linux O/S rounded rectangle. There is a heavy double arrow from the center bottom Application Software 2 rounded rectangle to the center top of the Linux O/S rounded rectangle. There is a heavy double arrow from the center bottom Application Software 3 rounded rectangle to the upper right corner of the Linux O/S rounded rectangle. There is a heavy double arrow from the center bottom Linux O/S rounded rectangle to the Engine Board.)

Graphics: Ralph W. Boaz

Slide 50:

Learning Objective #4

ATC Software Portability, Compatibility, and Interchangeability

Interchangeability

• Same functional and physical characteristics so as to be equivalent in performance and durability (subjective)
• Ability to exchange devices of the same type without alteration to the device or adjoining items (adjustments permitted, subjective)

Slide 51:

Learning Objective #4

Interchangeability Possible If Application Features Are Equivalent (subjective)

(Extended Text Description: This slide, titled "Interchangeability Possible If Application Features Are Equivalent (subjective)," illustrates how application program interchangeability is possible using the Linux operating system and API Software. This slide contains the graphic as described in Slide 48. The graphic is aligned slightly to left of the center of this slide. The third (rightmost) rounded rectangle at the top of the graphic (see Slide 48) is labeled "Application Software 3*." There is a fourth rounded rectangle that is the same size as Application Software 3* but it is located at the level of the Linux O/S rounded rectangle (see Slide 48). It is labeled "Application Software 4*." There is a solid curved arrow extending from the top of the Application Software 4* rounded rectangle to the right side of the Application Software 3* rounded rectangle. There is a solid curved arrow extending from the bottom of the Application Software 3* rounded rectangle to the left side of the Application Software 4* rounded rectangle. Below the Application Software 4* rectangle is a rectangle (not rounded) that is about 1/3 the width and 1/10 the height of the slide. It is located slightly higher than the Engine Board (see Slide 48). The rectangle has the label "* Indicates applications are of the same type.")

Graphics: Ralph W. Boaz

Slide 52:

Slide 53:

Learning Objective #4

Which of the following ATC controller resources is NOT shared/managed by the API software?

Answer Choices

1. Real-Time Clock
2. Front Panel
3. Datakey
4. Field Input/Output

Slide 54:

Learning Objective #4

Review of answers

a) Real-Time Clock
Incorrect. API software allows multiple programs to set the Real-Time Clock of the controller.

b) Front Panel
Incorrect. The front panel is managed by the API software so that application programs can share the front panel of the controller and users can switch between programs.

c) Datakey
Correct. A Datakey is a memory device controlled by the BSP not the API Software.

d) Field Input/Output
Incorrect. Field Inputs and Outputs are managed by API software, which allows them to be shared across application programs.

Slide 55:

Summary of Learning Objective #4

Describe the ATC 5201 Architecture

• Key elements of the ATC 5201 architecture
• Describe how the ATC 5201 Standard and ATC 5401 Standard work together
• ATC software portability, compatibility, and interchangeability

Slide 56:

Learning Objective #5 - Describe How the ATC 5201 Standard Works With Other ITS Standards

• Transportation Field Cabinet Systems
• ITS Communications Standards

Slide 57:

Learning Objective #5

ATC 5201 Standard Works with all of the Major Transportation Field Cabinet Systems

• Provides internal cabinet interfaces for Model 33X Cabinets, NEMA TS 1 and TS 2 Type 2 Cabinets, NEMA TS 2 Type 1 Cabinets, and ITS Cabinets
• Generally, ATC 5201 v06 has more rigorous environmental and testing requirements than the major TFCS standards and specifications

Slide 58:

Learning Objective #5

Example ATC Controller Units in a Cabinet Architecture

(Extended Text Description: This slide, titled "Example ATC Controller Units in a Cabinet Architecture," has two photos showing how ATC controller units can be used in different types TFCSs. The first image of the slide is a picture of a TFCS that is about 4 ½ feet tall and 3 ½ feet wide with the door open and out of view. It has two shelves approximately 1/5 and 2/5 down from the top of the cabinet. On the top shelf on the left side of the cabinet is a cuboid electronic assembly that appears to be double stacked racks for holding for other devices. In the leftmost portions of the racks are devices that are approximately 2.5 inches wide and 4.5 inches high with LEDs and a connector. The remainder of the assembly (top and bottom rack) is empty but appear to be slotted for other devices. On the top shelf center is a second assembly identical to that on the left. On the top shelf right is a cuboid device about 6 inches wide and 6 inches high. It has LEDs and connectors. On the second shelf slightly to the left of center sits a controller unit as described in Slide 38 Controller 1. To the right of this device sitting on the shelf is a cuboid device about 4.5 inches wide and 10.5 inches high. It has LEDs and connectors. Below the second shelf and filling the remainder of the cabinet is a metallic and electronic backplane. In the center top of this back plane are three devices similar to those plugged into the left top shelf assembly. Below these devices are 17 smaller cuboid devices with LEDs that are plugged into the backplane. They are aligned horizontally across the width of the backplane. Below the 17 devices are rows of screws. Except for the 17 smaller cuboid devices, there are cables attached to all of the other devices. The label below this picture says "NEMA TS2 Type 1.")

NEMA TS2 Type 1

(Extended Text Description: The second image is a picture of a TFCS that is about 5 1/2 feet tall and 2 feet wide with the door open and out of view. The interior of the cabinet contains a 19 inch wide standard electronic equipment rack. The side metal rails of the rack run along the left and right sides of the front of the cabinet interior. There are five sections of the equipment that extend edge to edge of the cabinet interior attaching to the side rails of the rack with screws.

• The first (top) section is a controller unit as described in Slide 38 Controller 5. It is located about 10 inches from the top of the rack vertically.
• The second section, takes up approximately 11 inches of vertical cabinet space. It consists of two rows of identical horizontal assemblies about 5 1/2 inches tall each. The assemblies are horizontal racks that hold devices that sit in groves of the rack. This section is located about 3 inches below the first section.
• The third section takes up approximately 11 inches of vertical cabinet space and is made up of three assemblies distributed horizontally across the section. The first assembly on the left is approximately 9 inches wide. It consists of 8 light switches and two three-pronged electrical outlets. There are assorted mounting screws and a toggle switch on the assembly. The middle assembly is approximately 4 inches wide and contains two rectangular devices approximately 4 inches tall and 1 3/4 inches wide. The assembly on the right side of the section is approximately 6 inches wide. It has two small lights, two small knobs, and a thin handle that is about three inches tall located in the center of the assembly. The third section is immediately below the second section.
• The fourth section takes up approximately 11 inches of vertical cabinet space. Aligned down the left side of the section are 4 evenly spaced glass covered components approximately 2 inches tall and 3 inches wide. To the right of the glass covered components there are two identical horizontal assemblies that are about 5 1/2 inches tall each. The assemblies are horizontal racks that hold devices that plug into the back of the rack. The plug-in devices are rectangular approximately 4 inches tall and 2 inches wide and fit vertically within the assemblies. There are 6 devices in the first assembly and 6 devices in the second assembly. There are three LEDs aligned vertically on the front of these devices. There is a blank 3 inch aluminum panel between the third section and the four section.
• The fifth section appears to be a single rack assembly as described in the fourth section except that it is empty of devices. It is located approximately 2 inches below the fourth section.

)

Model 332 Cabinet

Photos: Ralph W. Boaz

Slide 59:

Learning Objective #5

ATC 5201 Standard Provides Computational Power and Interfaces for ITS Communications

• TFCSs that use 170 controller units require replacement hardware in order to utilize NTCIP Actuated Signal Control (ASC) communications
• ATC 5201 Standard provides the capability to support multiple applications using different (or same) types of NTCIP communications simultaneously
• ATC 5201 Standard provides interfaces and computational power for applications such as Adaptive Control and Connected Vehicle applications

Slide 60:

Slide 61:

Learning Objective #5

Which of the following is a TRUE statement?

Answer Choices

1. API Software provides NTCIP communications software for multiple applications
2. ATC 5201 allows multiple applications to use NTCIP communications simultaneously
3. ATC environmental requirements are generally the same as TFCS standards and specifications
4. Most 170 controllers are suitable for NTCIP ASC communications

Slide 62:

Learning Objective #5

Review of answers

a) API Software provides NTCIP communications for multiple applications
Incorrect. API software does not provide NTCIP communications directly.

b) ATC 5201 allows multiple applications on an ATC controller to use NTCIP communications simultaneously
Correct. The Linux O/S supports multiple network addressing allowing multiple applications to use NTCIP at the same time.

c) ATC environmental requirements are generally the same as TFCS standards and specifications
Incorrect. ATC environmental requirements are generally greater than TFCS standards and specifications.

d) Most 170 controllers are suitable for NTCIP ASC communications
Incorrect. Most TFCSs that use 170 controllers will require replacement controllers to perform full functioning NTCIP ASC communications.

Slide 63:

Summary of Learning Objective #5

Describe How the ATC 5201 Standard Works

With Other ITS Standards

• Transportation Field Cabinet Systems
• ITS Communications Standards

Slide 64:

Learning Objective #6 - Specify ATC Equipment for System and Equipment Procurements

• Discuss How ATC 5201 Fits in the Systems Life Cycle
• Develop Migration Strategies and Mitigate Deployment Issues
• Creating a Specification Based on the ATC 5201 Standard

Slide 65:

Learning Objective #6

How ATC 5201 Fits into the Systems Life Cycle

(Extended Text Description: This slide, titled "How ATC 5201 Fits into the Systems Life Cycle," illustrates how a systems life cycle may be represented as a V-like formation called the Vee Diagram. The Vee Diagram is depicted as a thick light blue graphic "V" with a short horizontal portion (same thickness as the "V" portion graphic) at the left top of the "V" extending to the left and a short horizontal portion at the right top of the "V" extending to the right. It is said that it looks like the letter "V" with wings. There is a long thin horizontal arrow which points to the right at the bottom of the slide with the words "Time Line" sitting on top of it. The arrow extends along the bottom of the slide covering the distance of most of the V-like graphic.

The thick lines of the Vee Diagram are sectioned by dark blue lines to delineate the systems life cycle activities (identified below as lifecycle processes). There is a small legend on the lower right of the slide indicating these dark blue lines indicate "Document/Approval." From left to right on the left horizontal portion, there are two sections labeled: "Regional Architecture(s)" and "Feasibility Study / Concept Exploration". Moving downward on the left side of the Vee Diagram there are four sections labeled: "Concept of Operations," "System Requirements," "High-Level Design," and "Detailed Design". There is a bottom section at the vertex of the Vee Diagram labeled: "Software/Hardware Development Field Installation." Moving upward on the right side of the Vee Diagram there are four sections labeled: "Unit/Device Testing," "Subsystem Verification," "System Verification & Deployment," and "System Validation." From left to right on the right horizontal portion there are three sections labeled: "Operations and Maintenance," "Changes and Upgrades" and "Retirement/Replacement." There is an arrow that points downward along the edge of the left side of the Vee Diagram with the label "Decomposition and Definition." At the vertex of the Vee Diagram, there is the label "Implementation." There is an arrow that points upward along the right side of the Vee Diagram with the label "Integration and Recomposition." 

In a smaller font, underneath the left horizontal portion there are the words "Lifecycle Processes" identifying the sections of the Vee Diagram as life cycle processes. In the same size font at the vertex of the Vee Diagram are the words "Development Processes." It is intended that this identify the nine lifecycle processes "Concept of Operations" through "Systems Validation" as development processes. There are dotted horizontal lines with arrows at each end indicating a relationship between the processes on the left and right sides of the "V" as follows:

• "Concept of Operations" and "System Validation" have a dotted line labeled "System Validation Plan;"
• "Systems Requirements" and "System Verification & Deployment" have a dotted line labeled "System Verification Plan (System Acceptance);"
• "High-Level Design" and "Subsystem Verification" have a dotted line labeled "Subsystem Verification Plan (Subsystem Acceptance);"
• "Detailed Design" and Unit Testing have a dotted line labeled "Unit/Device Test Plan;" and
• "Software/Hardware Development Field Installation" at the vertex has no dotted lines associated with it.

The slide has animation. As the instructor discusses each of the development processes, a circle is drawn around the process on the Vee Diagram.)

Slide 66:

Learning Objective #6

How ATC 5201 Fits in the Systems Life Cycle

• ATC 5201 Standard defines a general purpose computing platform for TFCSs
• ATC controller units can be deployed as part of a Center-to-Field (C2F) system project
• ATC controller units may be used for multiple C2F systems and for generations of C2F systems
• ATC controller units may extend the life of a system
• Procurements may be made in relation to a system deployment but it is more of a strategic decision to use the ATC standards

Slide 67:

Learning Objective #6

How ATC 5201 Fits in the Systems Life Cycle

(Extended Text Description: This slide, titled "How ATC 5201 Fits into the Systems Life Cycle," illustrates how deployments of ATC controller units may occur at any point in the life of a system. This graphic is based on the identical graphic use in Slide 65 for the Vee Diagram. There is an oval encompassing the Software/Hardware Development Field Installation section at vertex (bottom) of the Vee Diagram. There is a single oval encompassing the subsequent four sections of the diagram including: Unit/Device Testing, Subsystem Verification, System Verification & Deployment, and System Validation. There is a single oval encompassing the subsequent two sections: Operations and Maintenance and Changes and Upgrades. There is an oval encompassing the final section, Retirement/Replacement. The entire diagram and ovals are encompassed by a rounded rectangle. The slide has animation. As the instructor discusses each of the development encompassed sections and then the entire diagram, the ovals and rounded rectangle appear.)

Slide 68:

Learning Objective #6

Develop Migration Strategies

• Have a written plan and policy for deploying ATC equipment as part of a strategic plan
• Factors that may influence the plan:
  • Working with Existing TFCS
  • Moving to new TFCS architectures
  • New Projects
  • Scheduled Maintenance
  • Upgrading to ATC hardware while using an agency's current application software
  • Upgrading to new operational software

Slide 69:

Learning Objective #6

Develop Migration Strategies (cont.)

• Factors that may influence the plan: (cont.)
  • Compatibility with existing or planned system software
  • Training operational staff

Slide 70:

Learning Objective #6

ATC Standards Update

• ATC 5201 v06 is currently being developed with publication projected second quarter 2014
• Although the API 5401 v02 has been published, complete API software meeting the standard is not yet available
• USDOT starting a project to create a reference implementation of API software (APIRI) for public use (2014/2015)
• APIRI project includes a validation suite that can be used to test API software on an Engine Board

Slide 71:

Learning Objective #6

Mitigating Deployment Issues

• Reference User Comment Draft ATC 5201 v06.10 or later in specifications
• Establish a contractual commitment from Engine Board suppliers to provide operational API software for their Engine Boards once the API RI is available
• Establish a contractual commitment from application software providers to supply software compatible with the API once the API RI is available
• Identify the tool chain (compiler and C libraries) used to create application programs for the Engine Board

Slide 72:

Learning Objective #6

Mitigating Deployment Issues (cont.)

• Determine access to source code for the Linux environment (Board Support Package) used on the Engine Board
• Require a test program from manufacturers demonstrating that each of the interfaces is operational
• Have a certification from manufacturer that the ATC being purchased passed testing "under load"
• Prior to purchase, have application providers demonstrate their software on the agency's current ATC units
• Buy support services with software in the case that the software becomes inoperable due to changes in the configuration of the Controller

Slide 73:

Slide 74:

Learning Objective #6

What is the best way to migrate to ATC equipment?

Answer Choices

1. Use existing TFCSs and replace older controllers with ATC controller units
2. Use existing operational software that has a version suitable for ATC controller units
3. Replace controller units as part of regular scheduled maintenance
4. All equally good and it depends on the needs of the agency

Slide 75:

Learning Objective #6

Review of answers

a) Use existing TFCSs and replace older controllers with ATC controller units
Incorrect. This is a good option for migrating to ATC equipment but agencies must define their needs and goals to assess what is best.

b) Use existing operational software that has a version suitable for ATC controller units
Incorrect. This is a good option for migrating to ATC equipment but agencies must define their needs and goals to assess what is best.

c) Replace controller units as part of regular scheduled maintenance
Incorrect. This is a good option for migrating to ATC equipment but agencies must define their needs and goals to assess what is best.

d) All equally good and it depends on the needs of the agency
Correct. All of the items listed can be part of a migration strategy. Agency must define their needs and goals to assess what is best.

Slide 76:

Learning Objective #6

Creating a Specification Based on the ATC 5201 Standard

• Agency specifications written based on how the agency will be purchasing equipment
• Agencies create standing specifications to insure consistency and expediency in procuring equipment
• Agencies may have a prequalified vendors list or a single vendor selected through a bid process
• Recommended that agencies separate specifications for ATC 5201 equipment from that of any application programs

Slide 77:

Learning Objective #6

Creating a Specification Based on the ATC 5201 Standard

• Develop a Concept of Operations (ConOps) for the TFCS based on your strategic plan
  • Describe characteristics of the TFCS equipment from the user's perspective
  • Cover the operational scenarios in which the equipment will be used
  • ConOps may or may not be part of the specification

Slide 78:

Learning Objective #6

Concept of Operations

• Example from the FHWA Systems Engineering Guidebook V3
  • Purpose of Document
  • Scope of Project
  • Referenced Documents
  • Background
  • Concept for the Proposed System
  • User-Oriented Operational Description

Slide 79:

Learning Objective #6

Concept of Operations (con't)

• Example from the FHWA Systems Engineering Guidebook V3 (cont.)
  • Operational Needs
  • System Overview
  • Operational Environment
  • Support Environment
  • Operational Scenarios
  • Summary of Impacts

Slide 80:

Learning Objective #6

Requirements for specifications that use ATC 5201 v06

• ATC 5201 Standard generally describes a minimum level of capability for conformant ATC controller units
• ATC 5201 specifications are a composite of standards and/or other specifications (referenced documents)
• This composite may consist of:
  • Explicit requirements developed by the agency
  • Explicit requirements gleaned from referenced documents
  • Referenced requirements (or sections) in the referenced documents
  • Inherited requirements from referenced documents with an established document precedence

Slide 81:

Learning Objective #6

Proposed Organization of Requirements

• Referenced Documents and Precedence
• General Requirements
• TFCS Requirements
• User Interface Requirements
• Serial and Parallel I/O Requirements
• Engine Board CPU and Memory Requirements
• Environmental and Testing Requirements
• Warranty Requirements
• Other Requirements

Slide 82:

Learning Objective #6

Referenced Documents and Precedence

• Establish precedence between other standards documents and specifications referenced to resolve conflicts. Example:

In the case there is a conflict between the requirements in referenced documents that is not directly addressed by a stated requirement, the precedence of the referenced documents shall be as follows:

1. Agency Specific Requirements
2. ATC 5201 Standard v06 Requirements
3. TFCS Requirements (e.g. NEMA TS 2, Model 33X, ITS Cabinet v01)

Slide 83:

Learning Objective #6

General Requirements

• Apply to the overall unit. Examples:
  • Material Requirements
  • Electronic Requirements
  • Mechanical Requirements
  • Quality Requirements

Slide 84:

Learning Objective #6

TFCS Requirements

• Identify the type(s) of TFCS architectures for the ATC controller unit
• TFCS configuration requirements that may influence the controller specification
  • User Interface
  • Serial and parallel interfaces
  • Operational Voltages

Slide 85:

Learning Objective #6

User Interface Requirements - ATC Minimum

(Extended Text Description: This slide, titled "User Interface Requirements – ATC Minimum," highlights the minimum ATC user interface requirements. The graphic consists of three large text boxes that are aligned vertically and extend the width of the slide. They are outlined by heavy solid lines. The content of the text boxes is as follows: Text Box 1 (top): CPU ACTIVE LED Indicator, Ethernet Port, USB Port (for removable memory device only). Text Box 2 (middle): EIA-574, 9-pin "D" serial connector for console OR RJ45, serial connector for console. Text Box 3 (bottom): EIA-574, 9-pin "D" connector for an external front panel OR Keyboard, LCD, Bell. There is a large plus sign between Text Box 1 and Text Box 2 and between Text Box 2 and Text Box three all centered on the slide.)

Graphics: Ralph W. Boaz

Slide 86:

Learning Objective #6

User Interface Requirements - ATC Options

• User Interface Optional Features
  • Datakey
  • AUX Switch (only available for Keyboard/LCD/Bell configuration)
• Power Supply Optional Features
  • Power Switch
  • Power LEDs

Slide 87:

Learning Objective #6

User Interface Requirements

• ATC controller user interfaces may have some restrictions based on the TFCS architecture selected
• ATC 5201 allows expansion of user interface requirements to include high-resolution graphics and additional front panel keys

Agencies are cautioned to verify that these types of interfaces will also operate in a mode that supports the basic ATC 5201 and ATC 5401 Standards

Slide 88:

Learning Objective #6

Serial and Parallel I/O Requirements

• TFCS architectures may have serial and parallel I/O requirements already defined
• ATC 5201 Standard offers numerous additional general purpose ports
• Agencies should include requirements for extra ports based on their concept of operations

Agencies are cautioned to not unnecessarily require communications ports as it can drive up costs and limit choices of vendors

Slide 89:

Learning Objective #6

Engine Board CPU and Memory Requirements

• CPU - 60 MIPS Minimum
• DRAM - 64 MB Minimum
• SRAM -1 MB Minimum
• Flash Memory - 16 MB Minimum

Agencies are cautioned not to arbitrarily require the highest number of MIPS and memory available as it can drive up costs and limit choices of vendors

Slide 90:

Learning Objective #6

Environmental and Testing Requirements

• Requirements vary between TFCS documents
• Environmental requirements within ATC 5201 v06 are generally more robust than TFCS documents
• Operational Voltages for the ATC controller unit must be specified to be consistent with the TFCS architecture used

Slide 91:

Learning Objective #6

Warranty Requirements

• Long-term investment - Get as much warranty as possible
• Get software support for Linux environment

Slide 92:

Learning Objective #6

Other Requirements

• Identification of the tool chain (compiler and C libraries) used to create application programs for the Engine Board
• Access to the tool chain and source code used to produce the Linux environment for the Engine Board (requires special arrangement)
• Engine Board suppliers to provide operational API software for their Engine Boards once the API RI is available
• Packaging
• Delivery
• Manuals

Slide 93:

Slide 94:

Learning Objective #6

Which of the following is a good practice when preparing a specification using ATC 5201 v06?

Answer Choices

1. Establish a precedence of referenced standards and specifications
2. Always specify the fastest CPU available
3. Always specify several extra serial ports than you need
4. Never exceed the minimum user interface requirements of the ATC 5201 Standard

Slide 95:

Learning Objective #6

Review of Answers

a) Establish a precedence of referenced standards and specifications
Correct. This is important since an ATC 5201 based specification is a composite of other documents.

b) Always specify the fastest CPU available
Incorrect. Agencies should consider leaving themselves options and assess the entire unit proposed by vendors.

c) Always specify several more serial ports than you need
Incorrect. This may limit choices of controller units and may increase costs.

d) Never exceed the minimum user interface requirements
Incorrect. User interfaces may exceed those of ATC 5201 as long as the basic operation is still achievable.

Slide 96:

Summary of Learning Objective #6

Specify ATC Equipment for System and Equipment Procurements

• Discuss how ATC 5201 fits in the Systems Life Cycle
• Develop migration strategies and mitigate deployment issues
• Creating a specification based on the ATC 5201 Standard

Slide 97:

What We Have Learned

1. The ATC 5201 Standard provides for controller units that can grow with technology using an Engine Board concept.
2. The ATC 5201 Standard can be used to specify ATC controller units that can operate in any major TFCS architecture.
3. The ATC 5201 Standard works with the ATC 5401 Standard to provide for portable, compatible and interchangeable application programs.
4. Agencies will reference other ITS standards or specifications in preparing an ATC 5201 specification.

Slide 98:

Resources

• Caltrans Transportation Electrical Equipment Specifications (TEES), 12 March 2009
• Intelligent Transportation System (ITS) Standard Specification for Roadside Cabinets v01.02.17b
• NEMA Standards Publication TS 1-1989 Traffic Control Systems
• NEMA Standards Publication TS 2-2003 v02.06 Traffic Controller Assemblies with NTCIP Requirements
• Institute of Transportation Engineers http://www.ite.org/standards/
• ITS PCB Training ITS PCB Home

Slide 99:

Slide 100:

Next Course Module

A208: Using the ATC 5401 Application Programming Interface Standard to Leverage ITS Infrastructures

1. Identify the features of the ATC 5401 Application Programming Interface (API) Standard
2. Describe the ATC 5401 Architecture
3. Describe how the ATC 5401 Standard works with other ITS standards
4. Specify API software for system and equipment procurements