Talking Technology and Transportation T 3 Webinar presents
Talking Technology and Transportation (T 3) Webinar presents Configuration Management @ WSDOT Mark Morse Washington State Department of Transportation 21 February, 2008 WSDOT
Center line Miles I-5 – 65 I-90 – 20 I-405 – 30 SR 520 – 10 SR 167 – 10 Et Al. – 10 Total ~ 150 WSDOT 2
CM Policy at WSDOT n n IT vs. TMS No policy for CM in TMS n n Need-driven Ad hoc WSDOT 3
WSDOT CM Efforts n Software - Source, EXEs, Testing, Release n n n Client / Server Hardware - what it is & where it is Communication - how its all connected WSDOT 4
Software Development n 3 Software Developers 2 Testers 1 System Administrator n Functional division of labor n n Each module the responsibility of 1 person Client done by 1 person WSDOT 5
Software Development n n n 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 6
In House Development n Users and developers on the same team n n n Instant access More intimate knowledge of the end use Users involved in the process n n Beta testing Prototyping WSDOT 7
CM Tools n n n Individual workstations Compiler - Project Utilities Weekly Backup WSDOT 8
Hardware Management n n n Device definitions Communication infrastructure Circuit layout Field changes coordinated with DB change Design & planning for circuits WSDOT 9
Hardware Devices n n n 350 Cameras 380 Data Stations / Ramp Meters 60 VMS Signs 30 HAR Signs 6 HAR Transmitters 110 Serial circuits WSDOT 10
Device Information n n Device ID Comm. Port Comm. Address Roadway Location WSDOT 11
Database CM n Definition of the device n n Common reference to device n n n System Maintenance Operations Troubleshooting WSDOT 12
Camera Information n n Pan/Tilt Type Switch Port WSDOT 13
Data Station Information n # of Detectors # Speed Traps Data Analysis Equations WSDOT 14
VMS Information n n # of Rows & Columns Controller Type Display Type Message Library WSDOT 15
Device CM n n n Verify definition matches hardware Coordinate changes to hardware Troubleshooting WSDOT 16
Device Report Example TMS Ramp Meter/Data Collector List - 09/19/2001 11: 37: 28 RM/DC VAXPort Adr Road S Sp Mt Status ES-055 D _TXB 8: 1 I-5 W 0 ACTV|OFF ES-057 D _TXB 8: 2 I-5 W ACTV|OFF ES-061 R _TXB 8: 4 I-5 W 2 ACTV|OFF ES-222 D _TXD 12: 6 I-5 W MARG|OFF ES-265 D _TXF 7: 6 SR-522 S ACTV|OFF ES-616 R _TXD 7: 8 I-405 N MPost Location Vrs Lp 152. 82 S 184 th St 40 24 8 153. 16 S 178 th St 40 11 0 0 154. 14 518/Klickitat-SB 45 18 1 89. 41 SR 526 6. 61 61 st Ave NE WSDOT 0. 86 Interurban-SB 40 20 7 0 40 5 0 0 45 12 0 17
Communication Infrastructure n n n 96 Fiber Main Trunk lines 32, 000 Fiber Optic circuits 20 Communication Hubs WSDOT 18
Fiber Trunk Information n Link ID Fiber Count & Length Fiber Number n n Purpose / Usage Comments WSDOT 19
Example Fiber Trunk Report Hub 1: Dayton Hub 2: Roanoke Fiber Count: 96 SM Length = 15. 03 km (9. 32 mi) Fiber # Purpose 1 OC-48 Roanoke to Dayton 2 OC-48 Dayton to Roanoke 3 Kent Video 4 Video to UW Terminated with SC-APC connecters 5 T 1 - Roanoke Terminated with SC-APC connecters … Comments KNT 1 Future WSDOT 20
Fiber Channel Information n n Hub ID -Location of each end Channel ID n n Circuit Type Purpose / Usage WSDOT 21
Example Fiber Channel Report Channel Bank 6 Channel 1 2 3 4 5 6 7 … Card Type 4 w E&M FX Async SRDU 2 w E&M Async Mt Baker Tunnel Circuit Description AM/FM Rebroadcast circuit MBT Ring down phone COHU CCTV control Honeywell fire control terminal Local tunnel radio Future Reserved Future WSDOT 22
Circuit Information n n n Circuit Name Comm. Port, & Comm. Address Device ID, Location Hub Name Channel & Modem ID Cable ID & Pair ID Terminal Cabinet & Lateral Pair ID WSDOT 23
Example Circuit Information Circuit Name Vax Port 170 Boeing Field txb 1 VMS txa 5 Central CCTV txh 9 Renton Chnl modem Cable Main Lateral Pair Term Cabinet Location Name # Hub Norfolk St Thistle St Holden St S 129 th St 079 D 081 D 082 R 084 D 1 2 3 4 Tuk cb 3/ch 6 North G-4 3 / 4 n / a 3 / 4 1 / 2 3 / 4 tc-081 cc-086 es-079 tc-083 wb 124 th sb SE 20 th nb 10 th NE eb Denny v-532 v-124 v-708 v-021 6 8 9 5 Fac cb 2/ch 1 South C-5 East 9/10 1 / 2 5 / 6 tc-118 tc-122 9/10 6 / 2 n / a cc-708 Sunset B NE Park NE 24 th NE 72 nd c-634 c-642 c-646 c-649 99 98 97 76 Ren cb 4/cb 2 Optel n / a n / a nor hub WSDOT 24
Benefits of CM Efforts n n Troubleshooting - test points identified Knowledge available to all players Transfer of knowledge to new players Resource Management - can we fill requests n Future Planning – expansion: need, capacity WSDOT 25
Conclusions n n n 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 26
Contact Information Mark Morse, TMS Software Engineer Washington State Department of Transportation PO Box 330310 Shoreline, WA 98133 (206) 440 -4479 6: 30 am - 5: 00 pm, M - Th. morsemh@wsdot. wa. gov WSDOT 27
- Slides: 27