|
The faster you act the better chance you will have to secure a protected IT service ! Your future success is VE.
|
The goal of Service Asset and Configuration Management is to support the agreed IT service provision by managing, storing, controlling and providing information about Configuration Items (CIs) and Service Assets throughout their life cycle. Quality and timely information supplied about CIs and Service Assets will enhance the effectiveness and efficiency of other Service Management processes, and in particular, those used within Service Transition.
Other objectives include:
* To support the business and customer’s control objectives and requirements
* To minimize the number of quality and compliance issues caused by improper configuration of services and assets
* To optimize the service assets, IT configurations, capabilities and resources.
Terminology Explanations:
Configuration Item (CI):
Reference to ANY component that supports an IT service (except people).
Example: IT components or associated items such as Request for Changes, Incident Records, Service Level Agreements.
Attribute:
Specific information about CIs that are appropriate to maintain.
Example: Size of RAM, hard drive, bandwidth
CI Level:
Recording and reporting of CIs at the level that the business requires without being overly complex. It’s a trade-off balancing the value that the information will provide versus the effort and cost to manage the information over time (not too much or too little).
Status Accounting:
Reporting of all current and historical data about each CI throughout its lifecycle.
Example: Status = Under Development, live, withdrawn etc.
Configuration Baseline:
Configuration details captured at a specific point in time. This captures both the structure and details of a configuration, and is used as a reference point for later comparison (e.g. After major changes, disaster recovery etc)
