Академический Документы
Профессиональный Документы
Культура Документы
Presentation Overview
Purpose of project Intended audience Brief overview of configuration management Overview of guidance document Phase 2 completion of outreach materials Contact information and channels for questions and feedback
2003 TMC PFS Annual Meeting
Project Purpose
Configuration Management for Transportation Management Systems is intended to provide guidance for transportation professionals who are either
seeking to improve change management in a traffic management system or regionally integrated intelligent transportation system by introducing formal CM, or using CM currently and require a technical reference to support their activities.
2003 TMC PFS Annual Meeting
Intended Audience
Configuration Management for Transportation Management Systems is intended to be guidance material for any individual who is engaged with or responsible for the planning, design, implementation, management, operation or maintenance of transportation management systems. Supports both
Project Status
Current effort
Complete document formatting Complete related outreach materials
Overview of CM
Before providing an overview of the guidance document, important to briefly review the fundamentals of configuration management This overview is included in Chapter 1 of the document.
Configuration Management
A management process for establishing and maintaining consistency of a products performance, functional, and physical attributes with its requirements, design, and operational information throughout its life. -EIA Standard 649
2003 TMC PFS Annual Meeting
CM Process
Configuration Management
Configuration Identification
Define the product and its configuration documentation Identification
Change Management
Control changes to a Product and its configuration documentation
Configuration Audits
Verify consistency of configuration documentation against the product
CM Plan
CM Plan describes how configuration management is accomplished and how consistency between systems configuration and the configuration records is achieved and maintained
Configuration Identification
Configuration Identification is the basis from which the configuration of items are defined and verified products and documents are labeled and changes are managed.
Change Control
Change Control is a process for managing product configuration changes and variances in order to assure system integrity
Configuration Status Accounting is a set of activities associated with periodic reporting on the status of a configuration and the changes to that configuration
Configuration Audits
Configuration Audits ensure that the performance and functional requirements defined in the configuration documentation have been achieved and that the design itself has been accurately documented.
Philosophy
Generic CM guidance is available There is a need to relate this available guidance to TMCs through concrete examples
EIA Standard 649 was used as the foundation for the document. Basic definitions and guidance were derived from the standard.
Following the discussion of implementation guidance, a summary box is presented for quick access and review
Best transportation practices are presented. These are based on concrete examples included in the document.
Numerous navigation boxes are included to help readers gain further information on context-sensitive items.
Chapter 1 - Introduction
Fundamentals of CM Resources How to Use this Document
Chapter 3 CM Processes
Covers every component of the CM process. Heavy emphasis on
Describing & presenting transportation best practices Highlighting key aspects of CM standards
Chapter 4 CM Plan
This chapter is devoted to CM planning Example CM Plan outline presented Extensive transportation best practices.
Chapter 5 CM Baselines
What is a baseline?
Chapter 6 CM Program
The theme of this chapter is making it work in your agency Specific topics
Chapter 8 CM Tools
Presents software tools available to support a CM program Includes a link to a website providing an inventory of available tools Examples of DOTs selection and usage of tools
Chapter 10 - Conclusion
Focus on key guiding principles Nine principles that were selected from EIA 649
1. Identify the context and environment in which CM is to be implemented and develop an appropriate CM Plan accordingly.
Best Transportation Practices 2. Define procedures describing how each CM process will be
accomplished. 3. Conduct training a number of examples of Configuration Identification This section will present so that all responsible individuals understand their roles and responsibilities and the procedures for implementing configuration management processes. 4. All items are assigned unique identifiers so that one item can be distinguished from other items. 5. Configuration documentation defines the functional, performance, and physical attributes of a system. 6. A baseline identifies an agreed-to description of the attributes of an item at a point in time and provides a known configuration to which changes are addressed. 7. Each change is uniquely identified. 8. Consider the technical, support, schedule, and cost impacts of a requested change before making a judgment as to whether or not it should be approved for implementation and incorporation in the item and its documentation. 9. Implement a change in accordance with documented direction approved by the appropriate level of authority.
Appendices
A Description/Summary of EIA 649 B Annotated Bibliography C Summary of CM Plans D System Descriptions (used in Transportation Best Practices) E List of References F List of Acronyms
Outreach Materials
Presentation Fact sheet Tri-fold brochure Communications plan CM Primer CM Research & Development Needs White Paper Final publication of guidance document
2003 TMC PFS Annual Meeting
2003 Task Name Start Finish Apr May 5/2 Jun Jul Aug Sep Oct
Configuration Management for TMCs: Phase 2 Contract Aw ard A. Outreach Material and Communication Plan A1. Project Fact Sheet and Presentation Develop Presentation Submit Draft Presentation to FHWA Review Period Comments Due from FHWA Incorporate Comments Develop 508-Compliant/Publication Ready Version of Presentation Submit Final Presentation to FHWA Develop Project Fact Sheet Submit Draft Fact Sheet to FHWA Review Period Comments Due from FHWA Incorporate Comments Develop 508-Compliant/Publication Ready Version of Fact Sheet Submit Final Fact Sheet to FHWA A2. Tri-Fold Brochure Develop Tri-Fold Brochure Submit Draft Tri-Fold Brochure to FHWA Review Period Comments Due from FHWA Incorporate Comments Develop 508-Compliant/Publication Ready Version of Tri-Fold Brochure Submit Final Tri-Fold Brochure to FHWA A3. Communications Plan Develop Communications Plan Submit Draft Communications Plan to FHWA Review Period Comments Due from FHWA Incorporate Comments Submit Final Comm unications Plan to FHWA
Fri 5/2/03 Fri 5/2/03 Fri 5/2/03 Fri 5/2/03 Fri 5/2/03 Tue 7/1/03 Wed 7/2/03 Tue 7/22/03 Wed 7/23/03 Mon 8/4/03 Tue 8/12/03 Fri 5/2/03 Tue 7/1/03 Wed 7/2/03 Tue 7/22/03 Wed 7/23/03 Mon 8/4/03 Tue 8/12/03 Fri 5/2/03 Fri 5/2/03 Wed 7/16/03 Thu 7/17/03 Wed 7/30/03 Wed 7/30/03 Mon 8/11/03 Wed 8/20/03 Fri 5/2/03 Fri 5/2/03 Tue 7/1/03 Fri 7/4/03 Tue 7/15/03 Tue 7/15/03 Tue 7/29/03
Thu 10/2/03 Fri 5/2/03 Wed 9/10/03 Tue 8/12/03 Tue 7/1/03 Tue 7/1/03 Tue 7/22/03 Tue 7/22/03 Fri 8/1/03 Tue 8/12/03 Tue 8/12/03 Tue 7/1/03 Tue 7/1/03 Tue 7/22/03 Tue 7/22/03 Fri 8/1/03 Tue 8/12/03 Tue 8/12/03 Wed 8/20/03 Wed 7/16/03 Wed 7/16/03 Wed 7/30/03 Wed 7/30/03 Fri 8/8/03 Tue 8/19/03 Wed 8/20/03 Tue 7/29/03 Thu 7/3/03 Tue 7/1/03 Tue 7/15/03 Tue 7/15/03 Tue 7/29/03 Tue 7/29/03
7/1
7/22
8/12
7/1
7/22
8/12
7/16
7/30
8/20
7/1
7/15
7/29
2003 Task Name Start Finish Apr May Jun Jul Aug Sep Oct
A4. Configuration Management Primer Develop CM Primer Develop 508-Compliant/Publication Ready Version of CM Primer Submit Draft CM Primer Review Period Comments Due from FHWA Incorporate Comments Submit Revised CM Primer to FHWA Review Period Comments Due from FHWA Incorporate Comments Revise 508-Com pliant/Publication Ready Version of CM Primer Submit Final CM Primer to FHWA B. Future Research, Training, or Technical Transfer B1. Draft White Paper Develop Draft White Paper Submit Draft White Paper Review Period Comments Due from FHWA B2. Final White Paper Develop Revised White Paper Submit Revised White Paper Review Period Comments Due from FHWA Incorporate Comments Develop 508-Compliant/Publication Ready Version of Final White Paper Submit Final White Paper C. Completion of Final Technical Reference Document Develop Revised Technical Reference Document Develop 508-Compliant/Publication Ready Version of Technical Reference Document Submit Revised Technical Reference Document Review Period Comments Due from FHWA Incorporate Comments Submit Final Technical Reference Document
Fri 5/2/03 Fri 5/2/03 Fri 7/4/03 Wed 7/16/03 Thu 7/17/03 Wed 7/30/03 Thu 7/31/03 Wed 8/13/03 Thu 8/14/03 Wed 8/27/03 Thu 8/28/03 Mon 9/8/03 Wed 9/10/03 Fri 5/2/03 Fri 5/2/03 Fri 5/2/03 Thu 7/31/03 Fri 8/1/03 Thu 8/21/03 Fri 8/22/03 Fri 8/22/03 Thu 9/4/03 Fri 9/5/03 Thu 9/18/03 Fri 9/19/03 Mon 9/29/03 Thu 10/2/03 Tue 5/6/03 Tue 5/6/03 Mon 5/26/03 Mon 6/2/03 Mon 6/2/03 Mon 6/23/03 Tue 6/24/03 Fri 7/11/03
Wed 9/10/03 Thu 7/3/03 Wed 7/16/03 Wed 7/16/03 Wed 7/30/03 Wed 7/30/03 Wed 8/13/03 Wed 8/13/03 Wed 8/27/03 Wed 8/27/03 Fri 9/5/03 Wed 9/10/03 Wed 9/10/03 Thu 10/2/03 Thu 8/21/03 Thu 7/31/03 Thu 7/31/03 Thu 8/21/03 Thu 8/21/03 Thu 10/2/03 Thu 9/4/03 Thu 9/4/03 Thu 9/18/03 Thu 9/18/03 Fri 9/26/03 Thu 10/2/03 Thu 10/2/03 Fri 7/11/03 Fri 5/23/03 Mon 6/2/03 Mon 6/2/03 Fri 6/20/03 Mon 6/23/03 Fri 7/11/03 Fri 7/11/03
7/16
7/30
8/13
8/27
9/10
7/31
8/21
9/4
9/18
10/2
6/2
6/23
7/11