Execute thorough configuration management from the start of an ITS project to help prioritize implementation activities.
A Utah experience in technical integration.
CM formalizes the process of making changes to a system under development so that the system’s builders maintain an appropriate configuration record and can always ensure that they know what the correct version of the system consists of. It is intended to establish and maintain the consistency of a system’s performance, functional, and physical attributes with its requirements, design, and operational information throughout the system’s life and is considered a "best practice" within the system engineering discipline. Managing changes to requirements is essential to minimizing cost and schedule overruns on transportation system projects. CM’s ability to control changes to requirements is a major reason for employing it on ITS projects.
In the case of the UDOT deployment, there were other lessons that stemmed from the need for a mature CM process, including:
- Use configuration management to help manage multiple contractors working on a single, complex, deployment. The CommuterLink system was deployed through a series of contracts that included the Highway Construction, the System Manager, the TOC construction, and the Systems Integrator contracts. There were additional subcontractors associated with these deployments and improved communication between the prime and subcontractors was warranted as well. Poor coordination between the Systems Integration contractor and their subcontractor eventually affected the delivery of the ramp metering system. Had configuration management been in place from the start of the project, miscommunication could have been avoided and schedule slippages avoided or at least acknowledged and adjusted for.
- Consider the urgency for operation of the systems being deployed within the configuration management process. UDOT required that components be brought online as soon as possible for their use in operation. Given that much of the CommuterLink system was being concurrently developed, components were often brought on line prior to the final communications infrastructure being in place. This required interim solutions to be developed and resulted in frequent configuration changes between the methods in which data / control were brought back from field elements to the operations staff.
A CM approach should have been in place from the start that identified naming conventions, interfaces, and required protocols. This would have ensured consistency between the Highway Construction integration work and that of the Systems Integration contractor. It would have also allowed for the development of test apparatus (simulators) to effectively test the functionality of the deployed components without the need of having an operating ATMS system.
 Gonzalez, P.J. A Guide to Configuration Management for Intelligent Transportation Systems United States Department of Transportation (DTFH61-00-C-00001) Washington, DC. April 2002
Author: Mark Nuaimi (Iteris)
Published By: Utah DOT
Source Date: 4/1/2003
EDL Number: 13851URL: http://ntl.bts.gov/lib/jpodocs/repts_te/13851.html
Average User Rating