1 / 22

Configuration Management 101

This webinar provides an introduction to configuration management planning, identification, status accounting, change management, audits, and application environment for IT professionals. Learn how to develop a CM plan and implement CM activities tailored to your project's needs.

seifert
Download Presentation

Configuration Management 101

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  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. Agencies & DeveloperShare CM Responsibilities Working Together Requires Tailoring Processes and Consensus Agency Developer Life cycle processes Multiple projects Multiple teams Audit activities Project product definition Quality level Audit process Internal CM processes & tools

  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. CM Needs 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

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

  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. 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. What are Enabling Products? Design (As-built’s) Requirements Production Equipment Test Procedures Test Procedures, Software, Jigs User Manuals Maintenance Manuals

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

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

  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. Changes 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. Mind set of Change Management Changes Definition Phase ImplementationPhase Integration/Verification Changes possible but more costly in dollars & schedule impact Changes are extremely costly & often cause late delivery Changes are controlled but allowable

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

  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. Status Accounting in CM Configuration Identification Status Accounting CM Planning and Management Change Management Configuration Audits Application Environment

  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. Role of Audits in CM Configuration Identification Status Accounting CM Planning and Management Change Management Configuration Audits Application Environment

  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. Thank You Presentation By: Ron Ice R. C. Ice and Associates ronice@ronice.com

More Related