These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Feature · Assets
Example screen with sample data
Assets
Track equipment, assignments and the service connections that explain impact.
OverviewVerified Service Asset Links×
IT Service Management · Assets
New
Verified Service Asset Links
Service asset links
| Id | Service | Asset | Dependency type | Verified at | |
|---|---|---|---|---|---|
| IDD-159 | SRV-6714 | ASS-90156 | DT-611 | 06 Oct | |
| IDD-713 | SRV-6396 | ASS-83040 | DT-121 | 05 Oct | |
| IDD-613 | SRV-4825 | ASS-95378 | DT-789 | 15 Oct | |
| IDD-336 | SRV-3664 | ASS-74860 | DT-206 | 07 Oct | |
| IDD-467 | SRV-6647 | ASS-54603 | DT-848 | 06 Oct |
6 of 6 records
IDD-159Service asset links · SAL-62108
ServiceSRV-6714
AssetASS-90156
Dependency typeDT-611
Verified at06 Oct
What you can do
Put equipment in service context
The asset register holds an asset tag, serial number, location, status and service. That lets the desk tell an in-stock device from one assigned to someone, in maintenance or retired. A separate assignment record names its custodian and dates of assignment and return. Service-asset links describe which equipment supports a service and when that link was verified.
The service connection matters during an interruption. An incident may identify the affected asset directly. The team can then follow its service, the asset’s location and its custodian without relying on an informal inventory list. A disposal record can retain the method, date, approval person and data wipe certificate when an item reaches the end of use.
How the work is organized
- Register. Keep identifying details and current status on each asset record.
- Assign. Record custody separately, with assignment and return dates.
- Relate. Verify service-asset links so responders can inspect service dependencies.
What to agree during setup
Agree what gets an asset record, how asset tags are issued, and which team maintains location and status. A device should not appear assigned in the register if its custody record says it was returned. Decide who reviews service links after equipment changes and how a link is verified. These rules make the asset view useful during an incident.
For specialized endpoints, the team may also record a department, criticality and next service due date. Patch attempts and server metric samples can refer to an asset. Use those records where the operational team actually collects the values, and name their owner before relying on them in service reviews.
Check the handoff on an actual case
A device supporting a named service moves to a new custodian. The Admin checks its tag and serial number, records the assignment date and person, and changes the asset status to assigned. The service-asset link identifies the service that depends on the device. Another person should be able to find the device from the service and find the custodian from the assignment record.
Later, an incident is raised against the device. The Incident Responder checks the asset location, related service and verified link before assessing impact. If the device is replaced, record its return date and update the register. Keep any disposal approval and wipe certificate with the disposal record so the handoff can be checked later.
What your team sees
- Assigned Assets — Equipment currently marked assigned, with its location and service.
- Verified Service Asset Links — Service dependencies with a recorded verification date.
Follow the work through
Use asset and service context to rehearse a custody change and an incident lookup. Continue to incident response when equipment affects service.
What it keeps track of
Data model- Assets
- Assets records for IT service and asset operations.
- Asset assignments
- Asset Assignments records for IT service and asset operations.
- Asset disposals
- Asset Disposals records for IT service and asset operations.
- Service asset links
- Links between a service and the assets that deliver it.
- Services
- Services records for IT service and asset operations.
- Specialty assets
- Specialty and regulated endpoints tracked alongside the main asset register.
- Patch attempts
- Patch Attempts records for IT service and asset operations.
- Server metrics
- Periodic resource samples captured from managed servers.
Who uses it
Permissions- Admin
- , Service Desk Agent, Incident Responder.
Set up IT Service Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.