ServiceNow Asset and Configuration Record Data Standard
Define what is recorded and how it stays accurate.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a data standard for configuration and asset records. Types of items we manage (laptops, servers, applications, licences): [ITEM_TYPES]. Fields we need for support and audit: [REQUIRED_FIELDS]. Sources of data (discovery tools, purchase records, manual entry): [DATA_SOURCES]. Problems: [PROBLEMS]. Provide a table for each item type: mandatory fields, naming convention, allowed values, owner, relationships (what depends on what), lifecycle statuses and who may change them, and the process for adding, changing and retiring. Do not record fields nobody will maintain. Example record for a laptop with invented values, including its relationship to the user and the services it supports. Data quality measures with an example calculation: completeness is mandatory fields filled divided by all mandatory fields, accuracy is the share matching physical checks in a sample, and freshness is the share updated within the agreed period. Plan the reconciliation of discovery data with purchase records and a rule for who resolves differences. Configuration differs between instances, so label any field name or process step you are unsure of [VERIFY] and ask the administrator to confirm it.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.