Review asset history, ticket work and reporting

Asset records bring custody, lifecycle and operational evidence together without becoming tickets themselves. Use linked work to investigate recurring equipment issues and retain an explainable history.

Before you start

Maintain reliable tags, categories, assignments and ticket links. Decide who reviews repairs, expired contracts, reconciliation exceptions and missing inventory, and how follow-up is assigned.

Steps

1. Link affected assets to Incidents, Problems, Changes or Requested Items using the supported asset picker. On an incident, the caller's assigned equipment is prioritised in the choices.
2. Open the asset's ITSM Work tab to review work grouped by ticket type and open the relevant details. Use the Problem-linking action when investigation needs an explicit Problem relationship.
3. Inspect asset activity and assignment/transfer/repair history to understand who changed what and when.
4. Review repair-without-Problem warnings and repeated work as prompts for investigation; decide whether a Problem is warranted.
5. Where Analytics is separately enabled, use asset reporting dimensions such as lifecycle, operational status, category, assigned team and location under the applicable reporting permissions.
6. Schedule an operational review of unverified inventory, ageing stock, coverage expiry and unexplained reconciliation exceptions using your team's own governance process.

Current integration and future depth

Basic cross-domain asset links, the ITSM Work view, direct Problem linking and the repair-without-Problem warning are documented as implemented in later architecture notes. The original plan's remaining advanced Problem integration should be read more narrowly: broad asset selection by model/category/manufacturer/firmware and model-level incident trends are not established by those basic links.

The proposed review cadence is an operational recommendation, not a claim that the module automatically schedules reviews or discovers recurring faults.

Expected result

Equipment investigations have explicit operational context and useful audit evidence, with reporting governed by its own module and access controls.

Important behaviour

An affected Asset link does not create a CI dependency or measure service downtime. Analytics is not enabled merely by activating Asset Management. Current cost and reporting views should not be described as full software licence compliance, predictive refresh planning or complete TCO accounting.

Related guides