Asset context

An asset carries an asset tag, serial number, location, status and service. Incident responders can use that link when a failure appears to involve a particular device or host. An incident itself can reference both the service and the asset, so the team can work from the service impact toward the affected equipment. The asset’s status tells whether it is in stock, assigned, under maintenance or retired.

Asset service links hold a separate dependency type and verification time. That record is useful when an asset supports a service in a way that needs explicit confirmation. An assigned asset and a verified link answer related but different questions: the asset’s current operating state, and when a stated service dependency was checked.

• Register. Assets identify the equipment, location and linked service.
• Assign. Asset assignments record the custodian, assignment time and return time.
• Verify. Asset service links capture dependency type and verification date.

Agree the asset tag convention and the level of detail needed in location. Decide who can update an asset’s service link and what evidence is sufficient to set a verification time. An asset may move between people while its service association remains relevant, so assignment history should be read alongside the current asset record. Keep retired assets visible for the incidents and changes that referred to them earlier.

For a release affecting a service, the release manager can look at the service’s assets before setting the change window. For an incident, the responder can see whether the implicated asset is already in maintenance. The service desk manager can also read the verified link when deciding whether a new request affects a shared dependency.

Use an assigned asset with a recorded custodian and a service link. Verify that the tag and serial number distinguish it from another device at the same location. Record a verified dependency and then open an incident that names the asset and service. At handoff, another responder should be able to follow the incident to the asset and from the asset to its service without relying on an unrecorded explanation.

If the asset is returned, record the return time on the assignment. If it is retired, change the asset state while retaining the historical incident link. The asset service coverage report can help a manager inspect which services have recorded assets and verified dependencies.

• Assigned Assets — Equipment currently marked assigned, with its service and location.
• Verified Asset Service Links — Dependencies with a recorded verification time.
• Open Incidents — Current response work that can reference affected equipment.

Read the incident response process to see how asset context enters triage. The release change process places service dependencies in a planned delivery window.