Intelligent Transportation Systems

T3 Webinar:

Approaches for Integrating Configuration Management into Your ITS Project Development Processes

February 21, 2008

Text version of Webinar presentation:

"Approaches for Integrating Configuration Management into Your ITS Project Development Processes"

Description of image or images on a slide contained in brackets.

Back to Webinar Files

Slide 1: Configuration Management T3 Webinar

Mark Morse
Washington State
Department of Transportation

Slide 2: Outline

[Map of Interstate and State Route network in metropolitan Seattle.]

Slide 3: CM Policy at WSDOT

  • IT vs. TMS
    • No policy for CM in TMS
    • Need-driven
    • Ad hoc

Slide 4: WSDOT CM Efforts

  • Software - Source, EXEs, Testing, Release
    • Client / Server
  • Hardware - what it is & where it is
  • Communication - how its all connected

Slide 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

back to top

Slide 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

Slide 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

Slide 8: CM Tools

  • Individual workstations
  • Compiler - Project Utilities
  • Weekly Backup

Slide 9: Hardware Management

  • Device definitions
  • Communication infrastructure
  • Circuit layout
  • Field changes coordinated with DB change
  • Design & planning for circuits

Slide 10: Hardware Devices

  • 350 Cameras
  • 380 Data Stations / Ramp Meters
  • 60 VMS Signs
  • 30 HAR Signs
  • 6 HAR Transmitters
  • 110 Serial circuits

Slide 11: Device Information

  • Device ID
  • Comm. Port
  • Comm. Address
  • Roadway Location

Slide 12: Database CM

  • Definition of the device
    • System
  • Common reference to device
    • Maintenance
    • Operations
  • Troubleshooting

back to top

Slide 13: Camera Information

  • Pan/Tilt Type
  • Switch Port

Slide 14: Data Station Information

  • # of Detectors
  • # Speed Traps
  • Data Analysis Equations

Slide 15: VMS Information

  • # of Rows & Columns
  • Controller Type
  • Display Type
  • Message Library

Slide 16: Device CM

  • Verify definition matches hardware
  • Coordinate changes to hardware
  • Troubleshooting

Slide 17: Device Report Example

[Example of Device Report (Ramp Meter). Image is title "TMS Ramp Meter/Data Collector List." It lists the following columns: RM/DC; VAXPort; Adr; Road; S; MPost; Location; Vrs; Lp; Mt, and; Status. ]

back to top

Slide 18: Communication Infrastructure

  • 96 Fiber Main Trunk lines
  • 32,000 Fiber Optic circuits
  • 20 Communication Hubs

Slide 19: Fiber Trunk Information

  • Link ID
  • Fiber Count & Length
    • Fiber Number
    • Purpose / Usage
    • Comments

Slide 20: Example Fiber Trunk Report

[Example of Fiber Trunk Report. Data grouped by Hub 1 and 2; Fiber Count; Length; Fiber #; Purpose, and; Comments.]

Slide 21: Fiber Channel Information

  • Hub ID -Location of each end
  • Channel ID
    • Circuit Type
    • Purpose / Usage

Slide 22: Example Fiber Channel Report

Channel Bank 6Mt Baker Tunnel
ChannelCard TypeCircuit Description
14w E&MAM/FM Rebroadcast circuit
2FXMBT Ring down phone
3AsyncCOHU CCTV control
4SRDUHoneywell fire control terminal
52w E&MLocal tunnel radio
6 Future
7AsyncReserved
8 Future

Slide 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

Slide 24: Example Circuit Information

[Example of Circuit Information Report. Report has the following columns: Circuit Name; Vax Port; Location; #; Chnl Modem; Cable; Main Pair; Lateral Pair; Term Cabinet. ]

Slide 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

Slide 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

back to top