Configuration Identification Report

Definition

A configuration identification report is the configuration management work product that formally identifies and reports the configuration of an endeavor.

Objectives

The typical objectives of a configuration identification report is to formally document the identity of the endeavor’s:

• Baselines.
• Configuration items.

Benefits

The typical benefits of a configuration identification report are:

• It clearly identifies and communicates the baselines to be achieved.
• It clearly identifies the work products to be placed under configuration control.

Contents

The typical contents of a configuration identification report include:

• Configuration Items:
  • Documentation
  • Data Components
  • Hardware Components
  • Software Components
• Baselines
• Conclusion
• Appendices:
  • Identification Criteria
  • Naming Criteria
  • Major Issues
  • TBDs
  • Assumptions

Stakeholders

The typical stakeholders of a configuration identification report are:

• Producer:
  • Configuration Management Team
• Evaluators:
  • Architecture Team
  • Customer Organization
• Approvers:
  • Technical Leader
  • Project Manager
  • Customer Representative
• Maintainer:
  • Configuration Management Team
• Users:
  • Customer Organization, which uses it to keep track of what is being produced.

Phases

A configuration identification report is typically produced and maintained during the following phases:

• Business Strategy: Completed
• Business Optimization: Maintained
• Initiation: Completed
• Construction: Completed
• Delivery: Completed
• Usage: Maintained
• Retirement: Archived

Preconditions

A configuration identification report typically can be produced if the following preconditions hold:

• The endeavor is started.
• The configuration management team is staffed and trained in configuration identification.

Inputs

The typical inputs to a configuration identification report include:

• Work Products:
  • Configuration Management Plan
  • Statement of Work
  • Process Description Document
• Stakeholders:
  • Project Management Team
  • Technical Leader

Guidelines

• If the number of configuration items is large, the configuration item identifications should be stored in a database and the report should be automatically generated by a configuration management tool.
• Use the procedure in the associated work flow to produce this work product.
• If you tailor this work product, then tailor its associated standard, template, and inspection checklist.

Conventions

A configuration identification report is typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• MS Word Template
• XML Template
• Inspection Checklist

Examples

• Example Configuration Identification Report