270 likes | 401 Views
Talking Technology and Transportation (T3) Webinar presents Configuration Management @ WSDOT. Mark Morse Washington State D epartment of T ransportation 21 February, 2008. Center line Miles I-5 – 65 I-90 – 20 I-405 – 30 SR 520 – 10 SR 167 – 10 Et Al. – 10 Total ~ 150.
E N D
Talking Technology and Transportation (T3) WebinarpresentsConfiguration Management @ WSDOT Mark Morse Washington State Department of Transportation 21 February, 2008
Center line Miles I-5 – 65 I-90 – 20 I-405 – 30 SR 520 – 10 SR 167 – 10 Et Al. – 10 Total ~ 150 WSDOT
CM Policy at WSDOT • IT vs. TMS • No policy for CM in TMS • Need-driven • Ad hoc WSDOT
WSDOT CM Efforts • Software - Source, EXEs, Testing, Release • Client / Server • Hardware - what it is & where it is • Communication - how its all connected WSDOT
3 Software Developers 2 Testers 1 System Administrator Functional division of labor Each module the responsibility of 1 person Client done by 1 person Software Development WSDOT
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 Software Development WSDOT
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
Individual workstations Compiler - Project Utilities Weekly Backup CM Tools WSDOT
Hardware Management • Device definitions • Communication infrastructure • Circuit layout • Field changes coordinated with DB change • Design & planning for circuits WSDOT
Hardware Devices • 350 Cameras • 380 Data Stations / Ramp Meters • 60 VMS Signs • 30 HAR Signs • 6 HAR Transmitters • 110 Serial circuits WSDOT
Device Information • Device ID • Comm. Port • Comm. Address • Roadway Location WSDOT
Database CM • Definition of the device • System • Common reference to device • Maintenance • Operations • Troubleshooting WSDOT
Camera Information • Pan/Tilt Type • Switch Port WSDOT
Data Station Information • # of Detectors • # Speed Traps • Data Analysis Equations WSDOT
VMS Information • # of Rows & Columns • Controller Type • Display Type • Message Library WSDOT
Device CM • Verify definition matches hardware • Coordinate changes to hardware • Troubleshooting WSDOT
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
Communication Infrastructure • 96 Fiber Main Trunk lines • 32,000 Fiber Optic circuits • 20 Communication Hubs WSDOT
Fiber Trunk Information • Link ID • Fiber Count & Length • Fiber Number • Purpose / Usage • Comments WSDOT
Example Fiber Trunk Report Hub 1: Dayton Fiber Count: 96 SM Hub 2: Roanoke Length = 15.03 km (9.32mi) Fiber # Purpose Comments 1 OC-48 Roanoke to Dayton 2 OC-48 Dayton to Roanoke 3 Kent Video KNT1 4 Video to UW Terminated with SC-APC connecters 5 T1 - Roanoke Terminated with SC-APC connecters … Future WSDOT
Fiber Channel Information • Hub ID -Location of each end • Channel ID • Circuit Type • Purpose / Usage WSDOT
ExampleFiber Channel Report Channel Bank 6 Mt Baker Tunnel Channel Card Type Circuit Description 1 4w E&M AM/FM Rebroadcast circuit 2 FX MBT Ring down phone 3 Async COHU CCTV control 4 SRDU Honeywell fire control terminal 5 2w E&M Local tunnel radio 6 Future 7 Async Reserved … Future WSDOT
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
Example Circuit Information Circuit Name Vax Port Location Name # Hub Cable Main Pair Lateral Pair Term Cabinet Chnl modem 170 Boeing Field txb1 Norfolk St Thistle St Holden St S 129th St 079D 081D 082R 084D 1 2 3 4 Tuk North 3 / 4 3 / 4 3 / 4 3 / 4 n / a 3 / 4 1 / 2 3 / 4 tc-081 cc-086 es-079 tc-083 cb3/ch6 G-4 VMS Central txa5 wb 124th sb SE 20th nb 10th NE eb Denny v-532 v-124 v-708 v-021 6 8 9 5 Fac South 9/10 9/10 1 / 2 5 / 6 tc-118 tc-122 cb2/ch1 C-5 East 9/10 9/10 6 / 2 n / a n / a cc-708 CCTV Renton txh9 Sunset B NE Park NE 24th NE 72nd c-634 c-642 c-646 c-649 99 98 97 76 Ren Optel n / a n / a n / a n / a n / a n / a n / a n / a nor hub nor hub nor hub nor hub cb4/cb2 WSDOT
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
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
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