ServiceNow Hardware Asset Management Process Guide
🔧
ServiceNow Hardware Asset Management Process Guide
Explore the ServiceNow Hardware Asset Management Process Guide for a comprehensive strategy in identifying, tracking, and maintaining hardware assets effectively.
1
Open hardware lifecycle event
2
Locate or create asset record
3
Classify asset and information risk
4
Verify identity and source evidence
5
Receive and inspect hardware
6
Normalize and register hardware
7
Prepare and deploy hardware
8
Transfer or recover hardware
9
Assess maintenance or repair need
10
Complete repair and restore service
11
Authorize retirement and disposition
12
Sanitize media and verify outcome
13
Transfer asset for final disposition
14
Reconcile asset and configuration records
15
Approval: Asset manager
16
Close lifecycle event and retain evidence
Open hardware lifecycle event
Open one controlled lifecycle event for one physical hardware asset. Confirm the request or source ticket, choose the event that is actually being performed, and name the accountable asset manager. Use a single run per asset and event so evidence, ownership, and approvals remain traceable; if the request covers multiple assets, split them into separate runs unless they are managed as one serialized bundle.
1
Acquire and receive
2
Deploy or reassign
3
Transfer or recover
4
Repair or maintain
5
Retire or dispose
Locate or create asset record
Search ServiceNow by asset tag and serial number before creating anything. Reuse the authoritative record when a match exists, investigate potential duplicates, and record why a new record is needed. Do not create parallel asset records for the same serialized device; unresolved access or duplicate concerns must remain visible for reconciliation.
1
Existing record confirmed
2
New record required
3
Potential duplicate found
4
Record access unavailable
5
Further investigation required
Classify asset and information risk
Classify the physical device and the information it stores or can access. Use the organization's approved classification scheme where available, and choose the closest conservative category when facts are incomplete. This classification drives handling, sanitization, and approval scrutiny; do not infer low risk merely because the device is damaged or powered off.
1
Laptop or desktop
2
Server or storage
3
Mobile device
4
Network equipment
5
Printer or peripheral
6
Audio visual equipment
7
Other trackable hardware
1
Public
2
Internal
3
Confidential
4
Restricted
5
Unknown pending assessment
1
Critical
2
High
3
Moderate
4
Low
5
Not yet determined
Verify identity and source evidence
Physically compare the manufacturer serial number and asset tag with the source request, shipping record, and ServiceNow record. Capture legible supporting evidence without exposing passwords, private user content, or security keys. Stop and investigate mismatches before moving the asset, because unique identity and record accuracy underpin every later lifecycle action.
1
All identifiers match
2
Asset tag mismatch
3
Serial number mismatch
4
Source record mismatch
5
Verification cannot complete
Receive and inspect hardware
For an acquisition event, receive the device against its shipment or procurement source, inspect it before stocking, and document shortages or damage. ServiceNow receiving expects traceable asset identity and a valid destination such as a stockroom. Quarantine damaged or unidentified equipment instead of marking it available.
1
Purchase order
2
Transfer order
3
Replacement or RMA
4
Donation or acquisition
5
Independent receipt
1
Accepted without issue
2
Accepted with minor issue
3
Damaged and quarantined
4
Incorrect item received
5
Identity or quantity exception
Normalize and register hardware
Create or complete the ServiceNow hardware asset record using normalized manufacturer and model data. Record the unique asset tag, serial number, financial source, stockroom or location, and an accurate lifecycle state. Link the asset to its configuration item where organizational policy requires it, and resolve duplicate records before making the device available.
1
In stock and available
2
In stock and reserved
3
In transit
4
Pending repair
5
Quarantined
6
Other controlled state
Prepare and deploy hardware
For deployment or reassignment, confirm the authorized recipient, destination, baseline configuration, security controls, and handoff evidence before changing the asset to an in-use state. Remove prior-user access and data when reassigning. Do not hand over a device while identity, encryption, management enrollment, or recipient authorization remains unresolved.
1
Ready and handed over
2
Ready pending collection
3
Blocked by configuration
4
Blocked by authorization
5
Blocked by hardware issue
Transfer or recover hardware
For a transfer or recovery, establish chain of custody from the prior custodian to the new custodian or stockroom. Inspect the returned device, revoke or update the prior assignment, and record its new controlled location and lifecycle state. Escalate lost, missing, or damaged devices under the organization's incident process.
1
Employee change
2
Location transfer
3
Loan return
4
Refresh or replacement
5
Repair intake
6
Contract or lease return
7
Other authorized transfer
1
Recovered in expected condition
2
Recovered with damage
3
Recovered with data concern
4
Asset not recovered
5
Custody discrepancy identified
Assess maintenance or repair need
For maintenance or repair, diagnose the reported issue, confirm warranty or vendor coverage, and consider whether the device may expose sensitive information during service. Preserve business data according to policy and record the diagnostic evidence. Route suspected security incidents separately before external repair or parts replacement.
1
Preventive maintenance
2
Hardware failure
3
Performance degradation
4
Physical damage
5
Security concern
6
Warranty or recall
1
Repair internally
2
Send to approved vendor
3
Replace device
4
No fault found
5
Security escalation required
1
No indication
2
Exposure suspected
3
Exposure confirmed
4
Unable to assess
5
Not applicable
Complete repair and restore service
Complete the authorized work, capture parts or vendor references, test the device, and decide its post-service state. Confirm that asset and configuration records reflect component or ownership changes. If testing fails, keep the asset controlled and open the correct replacement, escalation, or retirement path rather than returning it to service.
1
Cleaned and inspected
2
Applied firmware updates
3
Replaced hardware component
4
Completed vendor repair
5
Restored approved configuration
6
Performed functional testing
1
Fully serviceable
2
Serviceable with limitation
3
Further repair required
4
Replace asset
5
Retire asset
1
In use
2
In stock available
3
In stock reserved
4
Pending further repair
5
Pending retirement
Authorize retirement and disposition
For retirement, verify that the asset is eligible to leave service and select an authorized disposition channel. Confirm legal hold, lease, warranty, financial, and contract constraints before scheduling movement. Use an approved recycler or disposition vendor when required, and keep the asset in a controlled pending-disposal state until custody transfers.
1
End of useful life
2
Uneconomical repair
3
Security or compliance risk
4
Refresh program
5
Lease or contract return
6
Surplus or consolidation
1
Certified recycling
2
Secure destruction
3
Vendor return
4
Resale
5
Donation
6
Internal parts recovery
1
Authorized
2
Authorized with conditions
3
Pending evidence
4
Escalated for review
5
Not authorized
Sanitize media and verify outcome
Determine whether the asset contains storage media or sensitive configuration, then apply the organization's NIST-aligned sanitization method based on media type, information sensitivity, and intended reuse. Record the method, operator, tool or process, verification, and exception handling. Sanitization must render access infeasible at the required level; failed verification blocks disposition.
1
Magnetic storage
2
Solid state storage
3
Mobile embedded storage
4
Removable media
5
No storage media
6
Unknown media type
1
Clear
2
Purge
3
Destroy
4
Not applicable
5
Approved exception
1
Verified successful
2
Verified by certificate
3
Failed verification
4
Unable to verify
5
Exception approved
Transfer asset for final disposition
Transfer the retired asset only after authorization and sanitization controls are satisfied. Record the receiving party, pickup or shipment reference, transfer date, and final certificate or receipt. Maintain chain of custody through departure, and do not mark disposal complete while vendor confirmation or an approved exception is missing.
1
Recycled with certificate
2
Destroyed with certificate
3
Returned to vendor
4
Resold with receipt
5
Donated with receipt
6
Transfer exception unresolved
Reconcile asset and configuration records
Reconcile the completed physical action to ServiceNow. Confirm the hardware asset state, substate, custodian, location, stockroom, financial or contractual reference, work notes, and linked configuration item are accurate for the event. Review for duplicate records and unresolved exceptions; record any variance with an owner and remediation path before approval.
1
In stock
2
In use
3
In transit
4
In maintenance
5
Retired pending disposition
6
Disposed
7
Exception state
1
Fully reconciled
2
Asset record pending
3
Configuration item pending
4
Duplicate record unresolved
5
Reconciliation blocked
1
Complete
2
Not applicable
3
Pending finance update
4
Pending contract update
5
Exception requires review
Approval: Asset manager
Will be submitted for approval:
Open hardware lifecycle event
Will be submitted
Classify asset and information risk
Will be submitted
Verify identity and source evidence
Will be submitted
Reconcile asset and configuration records
Will be submitted
Close lifecycle event and retain evidence
Close the event only after the asset manager decision is recorded. Preserve the evidence bundle according to retention policy, link any follow-up work, and communicate the final state to affected service, finance, security, procurement, or user stakeholders. A rejected or conditional approval must produce an owned follow-up rather than a silent close.
Optional cookies and similar technologies support analytics, advertising and visitor identification, and embedded content. Change or withdraw consent in Cookie settings. Cookie policy.