/
Configuration Item Fields
Configuration Item Fields
- Michael Anthony Waara
Owned by Michael Anthony Waara
GUIDE STATUS: DRAFT
Field Name | Description | Choices | Default | Required |
---|---|---|---|---|
Assigned to | If there is one specific person in the assignment group who should be automatically assigned to all incidents relating to the asset then provide that person's name here. It is generally not a good idea to name a person in this way since incidents will be assigned to that person whether he or she is available or not. It is recommended that this field be left blank. | Select from reference list | None | No |
Assignment group | If there is a specific support group that should be automatically assigned to all incidents relating to the asset then name that group here. Leave this field blank if the assignment group is the same as the support group. It is recommended that this field be left blank. | Select from reference list | None | No |
Client | For assets that are supported for a specific functional unit other than OIT, provide the name of the group here. Use this field only if the asset is used by a single functional unit. | Select from reference list | None | No |
Client Contact | For assets that are supported for a specific functional unit other than OIT, provide the name of the person primarily responsible for the asset. | Select from reference list | None | No |
Comments | Additional information about the asset. The Comments field is not usually shown on reports and inquiries against the CMDB table unless specifically requested. | Select from reference list | None | No |
Description | A concise description of the asset that can be used to clarify the CI name. The description should never be more than a paragraph and rarely more than a few sentences. If a more detailed description is needed then either include a link in the description or attach a document to the CI record. | None | Yes | |
Discovery source | Indicates the origin of the CI record representing the physical asset. When adding CIs manually this should be set to Manual Entry. When assets are added via an automated discovery process the field will be updated by the automated process. | Select from list | None | Yes |
DR Criticality | Disaster Recovery criticality used to prioritize the recovery of assets in the event of a major disaster. A knowledge base article that contains details of what the options mean is available Here. This field is mandatory for the Business Service and Application classes. However, it can also be used by individual support teams to document DR priority for assets supported by the team. |
| None | No |
Last Review Date | The date the CI was last reviewed for completeness and correctness. | Date | None | No |
Name | ||||
Operational status | ||||
Status(install_status) | ||||
Support group | ||||
Supported by | ||||
Tech Support 1 | ||||
Tech Support 2 |
Update Log
Updated By | Date | Notes |
---|---|---|
Initial Creation. |