Please enable JavaScript.
Coggle requires JavaScript to display documents.
Customizing the Configuration Management Process (The Appropriate Level of…
Customizing the Configuration Management Process
Modifying the Process to Fit Goals
The planning procedure should consider where the development cycle the architecture of applications is captured as CIs.
Consider the
linkage
between source code control systems and the CM tool.
Focus the procedure work on areas that will help make
better decisions
about business applications.
Build a general process that cover all CM equally well, the reality is that projects get funded if they meet business goals.
The Appropriate Level of Process Detail
Keep procedures at the level of business activities without getting into exactly how those activities would be accomplished.
Each procedure should get consistent output despite who is executing it.
Rewrite procedures so they are more business related with general instructions.
Document procedures to ensure that the best practices can be used by the newest members.
Procedures aren't finished if they are too costly to implement.
The Standard of ITIL Framework
Control
Fences might be dictated by regulatory, business' rules or common sense.
Defining and implementing adequate controls requires
maturity.
Is the
most important
part by putting adequate controls in place.
The most common way to tell if your controls are adequate is by using results of
audits.
Track Status
This ease the process of moving CIs from one
state
to another.
Versions
are very important in accounting for the status of CIs.
CIs
Lifecycle
: Acquisition, Testing, Installation, Operations, Maintenance, Decommissioning and Disposal.
Identify
"You can't control what hasn't been identified yet".
This will be an ongoing activity.
Identification of
CIs
and the
relationships
between them.
It could be a very complex process, depending on existing documentation
Audit
Inaccuracy is a death knell for a CMDB.
This helps to validate that the other parts of the process are working well.
Your policies dictates whether this is an inaccuracy, and if so, what the severity of the error is.
Plan
Creation of the
Configuration Management Plan
Defines
Scope, Span and Granularity
of the
CMDB
Planning is
not
a one time activity
Common Process Customizations
Top Down Process
The exercise continues until each process step at the lowest level can be accomplished by a single person in a reasonable time.
At top level, the process includes the five areas provided by ITIL.
It goes from the top level of detail down to the bottom.
You can combine control and status tracking into one top-level process.
Planning Procedures
Procedures for Control of CIs
Integration with change management.
Every CMDB update must happen as a result of an enterprise change record.
Status Tracking Procedures
CIs in a terminal status can be archived after some defined retention period and bust be defined in this category.
Document the set of statuses that are possible and define procedures for transitions from one status to another.
Procedures for CI Identification
It is critical to define how data will be collected and how disparate sources will be reconciled.
Consider carefully where each piece of data is coming from and how to match it up with other data sources.
Challenge: marry demographic data with technical data.
Audit Procedures
Procedures about how to verify the accuracy of the CMDB.