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 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. 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 userEvery effort should be made to prevent duplication of CI names even across different classes. For example, the name of an application software package often becomes synonymous with the business service supported by the software, as in the following examples:
| Application Software | Business Service |
|---|---|
| ServiceNow | ITSM Services |
| Cognos | Business Intelligence |
| Xerox DocuShare | Electronic Document Management |
Naming both an application software CI and a business service CI "ServiceNow," even though they are in different configuration classes, would lead to confusion when referring to one or the other.
Contents
| Table of Contents |
|---|
...
- 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.
- Make every attempt to avoid abbreviations, jargon, and slang in CI names. Keep in mind that everyone from end users on the business side to the technical staff called on to provide support will need to understand the name.
- Use appropriate capitalization in the name. In general, use the guidelines outlined in the Modern Language Association (MLA) Formatting & Style Guide. Pay Pay particular attention to acronyms, application software names, and other words that have unusual letter casing. (See Capitalization Conventions for more information.)
- Under no circumstances should a person’s name be included in a CI name. If, for some reason, a person's name must be included then use the person's home department rather than the person’s name.
...
{common_name} [({nickname})] [{version}] [ - (owner)]Where:
{common_name} | The name of the software as it referred to by the majority those who will reference the CI. Whether a commercial product or something developed in-house, this should be the full, formal name of the product (e.g., "Office Suite 2016" or "Graduate Applicant Tracking System") rather than a nickname, abbreviation, or acronym ("Office 16" or "GATS"). While nicknames and abbreviations may be meaningful to frequent users of the CI, they are not so apparent to others who are not as familiar with the application. |
|---|---|
{nickname} | Nickname, abbreviation, or acronym for the CI. The nickname should always be enclosed in parentheses to separate it from the full name. |
{version} | A version is used to identify a specific baseline of a CI. This information should only be included if the CI is being defined to track a specific version or release of the applicaiton. |
{owner} | The name of the primary end user of the CI. This is optional and should only be used to eliminate any confusion about the owner of the CI or to eliminate duplication of CI names. For example, if several departments are using the same same application software but there are separate instances of the software for each department, include the department name as the owner. For example: Office Suite 2016 - (DUE), Office Suite 2016 - (Graduate Division), etc. The owner should always be enclosed in parentheses and separated from the rest of the CI name by a hyphen. |
...
NetBios names are limited to a maximum of 15 characters as described in the following articles:
...
...