KY%20Statewide%20Traffic%20Signal%20System

1
KY Statewide Traffic Signal System

• ITS Mid-America 2005
• Columbus, OH

2

• 1987
• No Standardized hardware or firmware
• Low Bid Lottery
• Difficult to maintain
• Confusing to program
• Universal Manual not working
• Tighter NEMA specs not working
• 1989
• Adopted the Caltrans 170 spec and Wapiti W4IKS
  firmware
• Initial resistance from technicians
• Now the best decision we ever made
• Mid 1990s
• Field equipment changout complete

3
KY Traffic Signal Facts

• KY maintains 2500 traffic signals
• All of those signals use Model 170 equipment and
  Wapiti W4IKS firmware.
• Many of our signals are interconnected
• Wapiti does nearly everything we need it to do
• Our people are trained in maintaining the model
  170/Wapiti controllers

4
Is there something wrong in our world of Wapiti?
5
What could be wrong???

• We estimate that we have 2500 traffic signals
• We know that they are located in KY
• Somewhere on a PC, laptop or PDA is the correct
  timing for each of those signals
• We many bonus timing files out there
• Technicians never modify timing in the field
• Our signals are working correctly because the
  police have not called today
• Every coordinated signal is in-step because the
  170 controller is as good as an atomic clock

6

• Overall the W4IKS standard has served us well.
• Standards are importantthat is why there are so
  many

7
The world may be changing but we are sticking
with the Wapiti/170 standard
8
Nothing more can be added to the 170/Wapiti system
9
What we need

• A way to manage our timing data
• A way to modify signal timing (from our desks)
• An automated process to check the status of every
  signal every day

10
Kentucky is Unique just like everyone else
11
Unique Needs

• We have very limited bandwidth to our signals
• We dont need to monitor our signals
  second-by-second
• We do need to use our existing hardware and
  firmware
• We do need to use the technician/PDA as a
  communication link

12

• We decided to use COTS software
• and modify it

13
We want an easy to understand user interface
14
ATMS Map

• Platform for display of traffic status, devices,
  etc.
• Geographically accurate
• ESRI data
• Layers support
• Traffic Controllers
• Traffic Conditions (links)

15
ATMS Explorer

• Platform for Schematics
• Import Graphics
• WMF
• BMP
• Uses common drawing tools
• DXF, TIFF, JPEG
• Uses Active-X Controls
• Used to Construct Management Views of System
  Elements
• Links Directly to the Device Controls
• Supports Hyper Links

16
TransSuite TCS Users Interface

• Primary interface to TCS
• Online device configuration
• Intersection
• System Detector
• Section
• Zone
• Multiple views of system devices
• By Jurisdiction
• By Section
• By Zone
• By Device
• Scheduler View
• Device Reports
• System Log
• Links with ATMS Map and Explorer

17
KYTC System Overview

• Base KYTC System
• TransSuite Traffic Control System (TCS) Server
• Database Server
• Central Communications Server (CCS)
• Support Server
• Operator Integrated Workstations (IWS)
• ATMS Map
• ATMS Explorer
• TransSuite TCS User Interface
• Unified Controller Manager

18
KYTC System Architecture
19
Where we are at

• Inventory 97.5 complete (73.8 of all
  statistics are made up on the spot)
• Initial software installation in progress
• Field controllers coming on-line
• KY modifications being added and tested

20
Step 1 - Field Inventory

• Show signal inventory animation

21
Comments, Questions?

• Glenn Anderson
• KY Transportation Cabinet
• Division of Traffic Operations
• 200 Mero Street
• Frankfort, KY 40622
• Glenn.Anderson_at_ky.gov