Talking Technology and Transportation (T3) Webinar
presents
Configuration Management @ WSDOT
Mark Morse
Washington State Department of Transportation
21 February, 2008
WSDOT 2
Center line Miles
I-5 – 65I-90 – 20
I-405 – 30SR 520 – 10SR 167 – 10
Et Al. – 10Total ~ 150
WSDOT 3
CM Policy at WSDOT
IT vs. TMS No policy for CM in TMS
Need-driven Ad hoc
WSDOT 4
WSDOT CM Efforts
Software - Source, EXEs, Testing, Release
Client / Server
Hardware - what it is & where it is Communication - how its all
connected
WSDOT 5
Software Development
3 Software Developers 2 Testers 1 System Administrator
Functional division of labor Each module the
responsibility of 1 person Client done by 1 person
WSDOT 6
Software Development Software developers sit side by side Discuss changes to common
elements Coordinate who makes changes to
the common files Monthly coordination meetings Developers are the Change Control
Board
WSDOT 7
In House Development
Users and developers on the same team Instant access More intimate knowledge of the end
use Users involved in the process
Beta testing Prototyping
WSDOT 8
CM Tools
Individual workstations Compiler - Project Utilities Weekly Backup
WSDOT 9
Hardware Management
Device definitions Communication infrastructure Circuit layout
Field changes coordinated with DB change
Design & planning for circuits
WSDOT 10
Hardware Devices
350 Cameras 380 Data Stations / Ramp Meters 60 VMS Signs 30 HAR Signs 6 HAR Transmitters 110 Serial circuits
WSDOT 11
Device Information
Device ID Comm. Port Comm. Address Roadway Location
WSDOT 12
Database CM
Definition of the device System
Common reference to device Maintenance Operations
Troubleshooting
WSDOT 13
Camera Information
Pan/Tilt Type Switch Port
WSDOT 14
Data Station Information
# of Detectors # Speed Traps Data Analysis Equations
WSDOT 15
VMS Information
# of Rows & Columns Controller Type Display Type Message Library
WSDOT 16
Device CM
Verify definition matches hardware
Coordinate changes to hardware
Troubleshooting
WSDOT 17
Device Report Example
TMS Ramp Meter/Data Collector List - 09/19/2001 11:37:28
RM/DC VAXPort Adr Road S MPost Location Vrs Lp Sp Mt Status ES-055D _TXB8: 1 I-5 W 152.82 S 184th St 40 24 8 0 ACTV|OFF ES-057D _TXB8: 2 I-5 W 153.16 S 178th St 40 11 0 0 ACTV|
OFF ES-061R _TXB8: 4 I-5 W 154.14 518/Klickitat-SB 45 18 1 2 ACTV|OFF ES-222D _TXD12: 6 I-5 W 89.41 SR 526 40 20 7 0 MARG|OFF ES-265D _TXF7: 6 SR-522 S 6.61 61st Ave NE 40 5 0 0 ACTV|
OFF ES-616R _TXD7: 8 I-405 N 0.86 Interurban-SB 45 12 0 1 ACTV|USE ES-810D _TXA10: 2 I-90 S 02.49 NB I-5 – EB 40 4 0 1 ACTV|
OFF
WSDOT 18
Communication Infrastructure
96 Fiber Main Trunk lines 32,000 Fiber Optic circuits 20 Communication Hubs
WSDOT 19
Fiber Trunk Information
Link ID Fiber Count & Length Fiber Number
Purpose / Usage Comments
WSDOT 20
ExampleFiber Trunk Report
Fiber Count: 96 SMHub 1: Dayton
Terminated with SC-APC connecters
T1 - Roanoke5
Future…
Terminated with SC-APC connectersVideo to UW4
KNT1Kent Video3
Dayton to RoanokeOC-482
Roanoke to DaytonOC-481
CommentsPurposeFiber #
Length = 15.03 km (9.32mi)Hub 2: Roanoke
WSDOT 21
Fiber Channel Information
Hub ID -Location of each end Channel ID
Circuit Type Purpose / Usage
WSDOT 22
ExampleFiber Channel Report
Future6
ReservedAsync7
Local tunnel radio2w E&M5
Future…
Honeywell fire control terminalSRDU4
COHU CCTV controlAsync3
MBT Ring down phoneFX2
AM/FM Rebroadcast circuit4w E&M1
Circuit DescriptionCard TypeChannel
Mt Baker TunnelChannel Bank 6
WSDOT 23
Circuit Information
Circuit Name Comm. Port, & Comm. Address Device ID, Location Hub Name Channel & Modem ID Cable ID & Pair ID Terminal Cabinet & Lateral Pair ID
WSDOT 24
Example Circuit Information
n / acc-708
6 / 2n / a
9/109/10
East
TermCabinet
Lateral
Pair
MainPairCable
Chnl modemHub#NameLocation
Vax Port
Circuit Name
nor hubnor hubnor hubnor hub
n / a n / a n / a n / a
n / an / an / an / a
Optelcb4/cb2
Ren99989776
c-634c-642c-646c-649
Sunset BNE ParkNE 24th
NE 72nd
txh9
CCTVRenton
tc-118tc-122
1 / 25 / 6
9/109/10Southcb2/
ch1C-5
Fac6895
v-532v-124v-708v-021
wb 124th sb SE 20th nb 10th NEeb Denny
txa5
VMSCentral
tc-081cc-086es-079tc-083
n / a3 / 41 / 23 / 4
3 / 43 / 43 / 43 / 4
Northcb3/ch6G-4
Tuk1234
079D081D082R084D
Norfolk StThistle StHolden StS 129th St
txb1
170BoeingField
WSDOT 25
Benefits of CM Efforts
Troubleshooting - test points identified Knowledge available to all players Transfer of knowledge to new
players Resource Management - can we fill
requests Future Planning – expansion: need,
capacity
WSDOT 26
Conclusions
C M - system user’s survival kit
Match the tools to the need The better the CM effort, the
better prepared you will be for the future of your system
WSDOT 27
Contact Information
Mark Morse, TMS Software EngineerWashington State Department of
TransportationPO Box 330310Shoreline, WA 98133
(206) 440-4479 6:30 am - 5:00 pm, M - Th.