1. 1 Configuration Management 101 ITS Professional Capacity Building Program T3 Webinar February 21, 2008

2. 2 Configuration Management Planning CM Planning and Management Configuration Identification Change Management Configuration Audits Status Accounting Application Environment

3. 3 What is a CM Plan The CM plan provides the framework for all CM Activities Provides the definition of how the CM process will be implemented and who will be responsible for CM activities Should be tailored to the needs of the specific project The CM Plan provides the infrastructure for the CM Process

4. 4 Agencies & Developer Share CM Responsibilities Agency Developer Project product definition Quality level Audit process Life cycle processes Multiple projects Multiple teams Audit activities Internal CM processes & tools Working Together Requires Tailoring Processes and Consensus

5. 5 Agencies Define CM Requirements for RFP’s Define the contractors responsibilities Establish the basis for the CM process Identify the CM deliverables Define generic requirements for use in multiple RFP’s

6. 6 Scope the CM Responsibilities to the Size of the Project On a small project, one person may support multiple CM activities Others may support CM activities part time Responsibilities can be divided between individuals Responsibilities can be shared between stakeholder groups CM Needs

7. 7 Configuration Identification CM Planning and Management Configuration Identification Change Management Configuration Audits Status Accounting Application Environment

8. 8 What Is Placed Under Configuration Management End Products: The transportation system hardware, software, and firmware that performs the needed function Enabling Products: The supporting documentation, hardware, software, and firmware that enables the end products to be developed and maintained

9. 9 End Product Examples Hardware –Closed Circuit Television (CCTV) Camera –Smart Loop –Signal –Microwave Sensor Software –CCTV Control Software –Signal control Software –Toll Management Software –Violations Processing Software

10. 10 What are Enabling Products? Requirements Design (As-built’s) User Manuals Test Procedures, Software, Jigs Test Procedures Maintenance Manuals Production Equipment

11. 11 Typical Activities of Configuration Identification Select configuration items (CI) Establish and maintain CI Identifiers Identify documentation for each CI –Location info –Version info –Vendor info –Licensing/warrantee info –etc.

12. 12 Change Management CM Planning and Management Configuration Identification Change Management Configuration Audits Status Accounting Application Environment

13. 13 Caution: Changes Ahead! Developing systems undergo constant change Changes impact cost and schedule A change in one area will often cause changes in other areas The current state of all system elements must be considered when making changes

14. 14 Change Management is a Key Tool in the System Lifecycle Provides a defined process for managing change Starts early in the development lifecycle and continues until system is replaced Supports on-time delivery since the impact of cost and schedule are considered Results in documented, agreed upon changes

15. 15 Mind set of Change Management Definition Phase Implementation Phase Integration/Verification Changes are controlled but allowable Changes possible but more costly in dollars & schedule impact Changes are extremely costly & often cause late delivery Changes

16. 16 Change Management Process Model Change Identification Evaluation & Coordination Implementation & Verification Need for Change Current Baseline New Current Baseline Documented Change Request Approved Change Adapted from EIA 649

17. 17 Change Decisions Require a Baseline Change management begins with a stable point in system development A baseline is a well-defined, well- documented reference point for change management Changed system products must be placed under CM Next baseline incorporates the changed products

18. 18 Status Accounting in CM CM Planning and Management Configuration Identification Change Management Configuration Audits Status Accounting Application Environment

19. 19 Status Accounting Activities Record the currently approved configuration documentation Record proposed changes and status Record results of proposed changes Provide access to reports Safeguard the records through-out the life cycle Ω

20. 20 Role of Audits in CM Application Environment CM Planning and Management Configuration Identification Change Management Configuration Audits Status Accounting

21. 21 Configuration Audits Audits are verifications carried out by the agency or by an independent third party Audits verify that the product baseline matches the documentation Audits validate that the information placed under CM is complete Independent audits assure a non- biased evaluation

22. 22 Thank You Presentation By: Ron Ice R. C. Ice and Associates ronice@ronice.com