Configuration Management for Transportation Management Systems Final Report September 2003 Notice This document is disseminated under the sponsorship of the Department of Transportation in the interest of information exchange. The United States Government assumes no liability for its contents or use thereof. This report does not constitute a standard, specification, or regulation. The United States Government does not endorse products or manufacturers. Trade and manufacturers’ names appear in this report only because they are considered essential to the object of the document. Technical Report Documentation Page 1. Report No. 2. Government Accession No. 3. Recipient's Catalog No. FHWA-OP-04-013 4. Title and Subtitle 5. Report Date Configuration Management for Transportation Management Systems September 2003 6. Performing Organization Code 7. Author(s) 8. Performing Organization Report No. Dr. Brian Smith, Smart Travel Laboratory – University of Virginia 9. Performing Organization Name and Address 10. Work Unit No. (TRAIS) University of Virginia Department of Civil Engineering Thornton Hall; B-227 11. Contract or Grant No. 351 McCormick Road DTFH61-01-C-00180 P.O. Box 400742 Charlottesville, VA 22904-4742 12. Sponsoring Agency Name and Address 13. Type of Report and Period Covered Operations Office of Transportation Management Final Report Federal Highway Administration May – September 2003 400 Seventh Street, SW Washington, DC 20590 14. Sponsoring Agency Code 15. Supplementary Notes Jon Obenberger, FHWA Operations Office of Transportation Management, Contracting Officer’s Technical Representative (COTR) 16. Abstract Configuration Management for Transportation Management Systems is intended to provide guidance for transportation professionals who are either (a) seeking to improve change management in a traffic management system or regionally integrated intelligent transportation system by introducing formal CM or (b) using CM currently and require a technical reference to support their activities. 17. Key Word 18. Distribution Statement configuration management, traffic management system, No restrictions transportation management system, intelligent transportation system 19. Security Classif. (of this report) 20. Security Classif. (of this page) 21. No. of Pages 22. Price Unclassified Unclassified 210 Form DOT F 1700.7 (8-72) Reproduction of completed page authorized This page intentionally left blank. Configuration Management for Transportation Management Systems TABLE OF CONTENTS CHAPTER 1 – Introduction to Configuration Management and Transportation Management Systems.....................1-1 CHAPTER 2 – Configuration Management and Transportation Management Systems – Current Practices.............2-1 CHAPTER 3 – Configuration Management Processes................................................................................................3-1 CHAPTER 4 – Configuration Management Plan...........................................................................................................4-1 CHAPTER 5 – Configuration Management Baselines ..................................................................................................5-1 CHAPTER 6 – Configuration Management Program Making it Work in Your Agency.................................................6-1 CHAPTER 7 – Configuration Management and the System Life Cycle .......................................................................7-1 CHAPTER 8 – Configuration Management Tools .........................................................................................................8-1 CHAPTER 9 – Resources to Support Configuration Management Programs..............................................................9-1 CHAPTER 10 – Conclusion..........................................................................................................................................10-1 APPENDIX A – Description/Summary of EIA 649........................................................................................................ A-1 APPENDIX B – Annotated Bibliography ....................................................................................................................... B-1 APPENDIX C – Summary of CM Plans ........................................................................................................................C-1 APPENDIX D – System Descriptions............................................................................................................................D-1 APPENDIX E – List of References................................................................................................................................E-1 APPENDIX F – List of Acronyms................................................................................................................................... F-1 LIST OF FIGURES Figure 1.1 – Configuration Management Process..........................................................................................................1-5 Figure 2.1 – Functional Classes of Systems...................................................................................................................2-2 Figure 2.2 – CM Use by System Size .............................................................................................................................2-3 Figure 2.3 – Core System Software ................................................................................................................................2-3 Figure 2.4 – Use of CM Based on Software Class .........................................................................................................2-4 Figure 2.5 – Percent of Agencies Using CM that Have a Formal CM Plan...................................................................2-5 Figure 2.6 – CM Tools Used by Agencies.......................................................................................................................2-7 Figure 2.7 – Lead Organization During Planning Phase................................................................................................2-8 Figure 2.8 – Lead Organization During Design Phase...................................................................................................2-8 Figure 2.9 – Lead Organization During Development Phase.........................................................................................2-9 Figure 2.10 – Lead Organization During Operations & Maintenance Phase.................................................................2-9 Figure 2.11 – Subsystems Covered by CM ..................................................................................................................2-10 Figure 2.12 – Agencies Including CM Elements...........................................................................................................2-11 Figure 3.1 – Levels of Hardware Configuration Identification .......................................................................................3-7 iii Configuration Management for Transportation Management Systems Figure 3.2 – NaviGAtor CCB Organization ..................................................................................................................3-23 Figure 3.3 – Configuration Control Board Organization ..............................................................................................3-26 Figure 3.4 – SCPC CM Subcommittee Organization ..................................................................................................3-27 Figure 3.5 – Georgia NaviGAtor SCR Flow ..................................................................................................................3-30 Figure 3.6 – CHART II Change Priorities......................................................................................................................3-32 Figure 3.7 – CHART II Change Control Process..........................................................................................................3-33 Figure 3.8 – Richmond Trouble Report Form ...............................................................................................................3-35 Figure 4.1 – Southern California Priority Corridor Identification Structure...................................................................4-11 Figure 4.2 – Southern California Priority Corridor Change Control Process ...............................................................4-11 Figure 4.3 – Southern California Priority Corridor CM Program Organization.............................................................4-12 Figure 5.1 – Baselines in the System Life Cycle (Control gate letters refer to table 5.1)..............................................5-4 Figure 6.1 – Project Office Organization.......................................................................................................................6-12 Figure 7.1 – Configuration Items and Supporting Elements...........................................................................................7-2 Figure 7.2 – The Systems Engineering Life Cycle and Configuration Items .................................................................7-3 Figure 7.3 – NaviGAtor Software Development Cycle ................................................................................................7-10 Figure C.1 – SCR Flow...................................................................................................................................................C-9 LIST OF TABLES Table 1.1 – Handbook Usage Recommendations........................................................................................................1-10