Configuration Item Naming Standards

A Configuration Item (CI) is any component or other service asset that needs to be managed in order to deliver an IT service. Information about each configuration item is recorded in a configuration record and each is identified by a unique name. CIs are classified into any number of categories based on the purpose of the item. CI classes typically include IT or business services, hardware, software, buildings, and formal documentation such as process documentation and service level agreements.

CI names should be concise, follow a consistent format, and contain enough information that a unique name can be assigned to each individual item and the nature of the item is immediately apparent to any user.

General Principles in Naming CIs

It is unlikely that the same naming standard can be used for all CI classes. The following are general guidelines that should be considered when determining the most appropriate naming convention for a particular CI.

• A format should be chosen that eliminates the need to ever have to rename the CI throughout its life cycle. Do not include version numbers or release dates in CI names unless you are tracking that specific version of the CI through its entire life cycle.

• The name should describe the CI in a way that it is recognizable by the majority of users (including clients) who will see it.

• The name should have the more significant information at the beginning, which will make it easier for systems with autocomplete to find the name when a user searches for it.

• For hardware, consider including the asset tag ID or chassis serial number in the name. This will uniquely identify the CI and typically will not change during the CI's life cycle.

• For software, use the common industry name of the product (for commercial products) or the name by which the software is usually referenced (for software developed internally) as the basis of the name.

• For servers, printers, workstations and other network devices, consider that host names often change and care should be taken when considering them as CI names.

Application Software CI Name Elements

Application software CI names should follow the form of:

      {{common_name} [({nickname})] [{version}] [ - (owner)]

Where:

{common_name}

{noun}

{modifier}

{sponsor}

Other Considerations

• Avoid using multiple verbs. Most projects involve more than one kind of activity and it is not necessary to mention them all in the project name. For example, a software development project might involve designing, developing, testing, and deploying business application software. All this activity can be summarized simply as “implementing” since the final outcome of the project will be newly implemented software.
• In all cases, avoid abbreviations, jargon, and slang in project names. Keep in mind that everyone from the executive sponsor on the business side to the technical staff called on to implement the detailed tasks associated with the project will need to understand the name.
• Under no circumstances should a person’s name be included in a project name. If the project sponsor needs to be included, use the department name rather than the individual person’s name.
• Avoid using the words “old” and “new” since, by definition, most projects are implementing something “new” and most result in the elimination of something “old.”

Examples

The following are examples of project names that have been normalized using the conventions described above.