...
- 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 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.
...