Develop > Processes and Best Practices > Configuration Management Workflows > Configuration Management Planning (process ST 3.1)

Configuration Management Planning (process ST 3.1)

Infrastructure and services should have an up-to-date Configuration Management plan, which can stand alone or form part of other planning documents. The Configuration Management plan should include or describe the following:

  • Scope, objectives, policies, standards, roles, and responsibilities
  • Configuration Management processes to provide the following services:
    • Define the Configuration Items that comprise related service(s) and infrastructure
    • Control changes to configurations
    • Record and report the status of Configuration Items
    • Verify the completeness and correctness of Configuration Items according to the requirements for accountability, traceability, and auditability
  • Configuration Control (access, protection, version, build, and release controls)
  • Interface control process for identifying, recording, and managing CIs and information at the common boundary of two or more organizations (for example, system interfaces and releases)
  • Planning and establishing the resources to bring assets and configurations under control and maintain the Configuration Management system (for example, training)
  • Management of suppliers and subcontractors performing Configuration Management

Details for this process can be seen in the following figure and table.

The Configuration Management Planning workflow is illustrated in the following figure:

Configuration Management Planning process

Process ID

Procedure or Decision

Description

Role

ST 3.1.1

Maintain Configuration Management plan

The Configuration Manager maintains the Configuration Management policies, objectives, scope, and principles. Periodically, this plan is reviewed to determine improvements. The Configuration Management plan (ACM plan) also defines the scope and level of detail of Configuration Item (CI) data to be maintained in the CMS. A Configuration Management plan provides the guidelines for documenting and modeling IT services in the CMS (identification of CIs).

Configuration Manager

ST 3.1.2

Configuration model update required?

Determine whether the Configuration model should be updated. If yes, go to ST 3.1.4. If no, go to ST 3.1.9.

Configuration Manager

ST 3.1.3

Review CMS change task

The Configuration Manager receives a task from Configuration Management to update the CMS data model (for example, when a new type of CI is introduced in the IT infrastructure as a result of a release).

Configuration Manager

ST 3.1.4

Update CMS data model

The data model defines the structure and information model of the CMS. This includes:

  • Model of IT services (breakdown of services into service components)
  • CI relationships types
  • Definition of CI types
  • Definition of CI attributes
  • Identification of data sources (such as HR-system or ERP)

The Configuration Manager determines the type of modification that is required for the CMS model.

CMS/Tools Administrator

ST 3.1.5

New CI type needed?

If a new CI type is needed, go to ST 3.1.7. If not, continue with ST 3.1.6.

CMS/Tools Administrator

ST 3.1.6

Modification of CI type required?

If a modification of the CI type is required, go to ST 3.1.8. If not, continue with ST 3.1.9.

CMS/Tools Administrator

ST 3.1.7

Create new CI type

The CMS/Tools Administrator adds a new CI type (device type). This includes the definition of CI attributes and screen design.

CMS/Tools Administrator

ST 3.1.8

Configure CI types

Create or modify the definition of the CI type. This includes:

  • CI subtypes
  • Attribute definitions
  • Screen design
  • CI relationships types
  • Naming conventions
  • Business rules on required fields

CMS/Tools Administrator

ST 3.1.9

Configuration Management policies update required?

The Configuration Administrator determines whether the Configuration Management policies must be updated (to reflect the SCAM plan). If so, go to ST 3.1.12.

Configuration Manager

ST 3.1.10

Maintain Configuration Management policies

The Configuration Manager maintains the Configuration Management policies. Policies may be applicable for specific asset types (or CI Types) or services. Policies may include business rules and requirements for specific information to be maintained in the CMS (for example, for compliance purposes or to monitor contracts). Policies determine how often a configuration audit is required. Policies also designate which data in a CI may be updated by inventory tools, as well as what actions must be performed if unauthorized software is detected. Other items covered by policies and business rules include:

  • Naming conventions
  • Labeling rules
  • Asset capitalization rules (for example, to set the depreciation start date)
  • Procedures for lost or stolen items

Configuration Manager

ST 3.1.11

Configure Configuration Management policies

Configuration Management policies and requirements are translated into tool settings (for example, required fields, schedule for automated inventory and discovery, and reconciliation rules).

CMS/Tools Administrator

ST 3.1.12

CMS update?

If yes, go to ST 3.3.1. If not, the process is finished.

Configuration Manager