IT Asset Management Done Right: Lessons From 1,500+ Devices Across 3 Offices
Asset management is the IT discipline that separates mature operations from reactive ones. When it's working, it's invisible — procurement runs on time, audits pass, devices are where they should be, and nobody loses sleep over warranty expiry. When it's broken, everything downstream breaks with it.
I've managed 1,500–2,000 active IT assets across three offices in Saudi Arabia for 15 years. These are the practices that work.
Syed Waqas Tayyab
Senior IT System Engineer · SAP Saudi Arabia · 15+ Years
Azure Security Certified · SAP AI Hub · MBA · MENA IT Expert
1. The Serial Number Is the Source of Truth — Protect It
Every asset management failure I've seen starts with a serial number problem. Duplicate entries. Typos. Fields left blank because "we'll fill it in later."
The rule: Serial number is mandatory, unique, verified at time of entry. No exceptions.
In a database-backed system, enforce this at the schema level with a UNIQUE constraint. In our enterprise asset management system, every equipment record has a mandatory serial number field validated against the asset tag.
When a device arrives from a vendor, the serial number goes into the system before the device leaves the receiving area. Not later. Not "when we get a chance." Before it moves.
The cost of fixing a duplicate serial number six months later — when that asset is sitting in three different records across two offices — is 10× the cost of capturing it correctly at intake.
2. MDM Compliance Is Your Asset Inventory
Every managed device enrolled in Jamf (macOS/iOS) or Microsoft Intune (Windows/Android) is visible in the MDM console with its serial number, last check-in time, compliance status, and location.
This is your real-time asset inventory. Use it.
Cross-reference your ERP asset register against MDM every quarter. Devices that appear in ERP but not in MDM have likely been lost, reimaged, or reallocated without a ticket. Devices in MDM but not ERP are shadow assets — someone enrolled a device that was never formally tracked.
Set up an automated Intune compliance report in Power BI. One dashboard showing asset count by category, compliance status by device type, and devices not seen in 30+ days. This makes your quarterly inventory audit a 20-minute review rather than a week-long spreadsheet exercise.
3. The 21-Day Offboarding Rule
When an employee's contract ends, their devices need to come back. This sounds obvious. It requires a process.
The rule we enforce: devices not returned within 21 days of the employee's last day are escalated to HR for recovery. The escalation is automatic — triggered by the offboarding ticket in ServiceNow.
The sequence:
- HR confirms last day → IT ticket auto-raised at T-14 days
- Manager notified to collect device before last day
- If not returned by last day: HR escalation + account disability
- T+7 days: Legal/HR formal recovery notice
- T+21 days: Asset marked as "unrecovered" in ERP, insurance/replacement claim initiated
The 21-day rule creates urgency without being punitive. Most devices come back in the first 7 days once the process is clearly communicated.
4. Inactivity Monitoring Is Cheaper Than Replacement
Devices sitting in a drawer, not enrolled in MDM, accumulate warranty expiry. Someone finds them a year later, they're out of warranty, and now you're paying for a replacement device you already owned.
Set up an MDM compliance dashboard showing devices not checked in for 30+ days. These are the candidates for:
- Recovery from ex-employees who kept a device "just in case"
- Devices in storage that should be redeployed
- Devices assigned to roles that no longer exist
We flag every device inactive for 6 months as "review required" in our enterprise asset management system. Every quarter, the IT team does a physical sweep of flagged devices. We consistently find 3–5% of our fleet sitting unused — that's 45–100 devices that could be redeployed instead of procured new.
At an average laptop cost of ~4,000 SAR, this is a meaningful budget saving.
5. Asset Categories Need Real Definitions
"Laptop" is not an asset category. "Windows Laptop," "MacBook," "iPad," "iPhone," "Monitor," "Printer," "Meeting Room AV" are asset categories.
The granularity matters because lifecycle, warranty, procurement lead time, and disposal processes differ per category. A MacBook managed through Jamf has a different support model than a Windows laptop managed through SCCM/Intune. An iPhone has a different warranty process than a desktop monitor.
Define your categories before you start adding records. Changing categories mid-flight is painful — every existing record needs updating, and reports that span the transition period are unreliable.
Our categories:
- Lenovo Laptop (Windows)
- MacBook (macOS)
- iPhone (corporate)
- iPad (corporate)
- Android Device (corporate/BYOD)
- Monitor
- Printer/MFP
- Meeting Room AV (Teams MTR unit)
- Server Room Equipment
- Network Device (switch, AP, router)
6. The LPA Scan: Don't Trust the Database Alone
LPA = Local Physical Audit. Once a year, someone physically scans every device in the office. Serial number on the device must match the record in ERP.
It always surfaces discrepancies. Devices that were "transferred" but not updated in the system. Devices that show as assigned to an employee who left 18 months ago. Assets in the server room that have no record at all.
The LPA is not an indictment of your asset management process — it's the corrective mechanism that keeps it honest.
We do it in October/November annually, timed with the hardware budget planning cycle. Knowing exactly what we have informs exactly what we need to buy.
7. Warranty Tracking Is Risk Management
Warranty expiry on an enterprise laptop means the next hardware failure results in a procurement cycle — which takes weeks — instead of a service call. For a device used by an executive or a critical operations role, that's unacceptable.
Track warranty expiry dates in your asset system. Generate a monthly report of devices expiring in the next 90 days. For devices under active daily use, initiate the replacement procurement 60 days before expiry.
In SAP Ariba, this means raising the Purchase Request at T-60. Vendor delivery is typically T+14 to T+21. Configuration and user setup is T+5. You hand over a new device with 30 days of warranty overlap on the old one.
Devices expiring that are assigned to light users (meeting room shared PCs, occasional-use workstations) can often be kept in service for 12–18 months post-warranty with careful risk management. Track which devices are in this "extended life" category and don't assign them to high-criticality roles.
8. The Procurement → Asset Record Pipeline
Every procurement request should automatically create a draft asset record. Every delivery should trigger a serial number capture workflow.
In our setup:
- Device request raised in SAP Ariba
- PO approved and sent to vendor
- Delivery confirmation triggers an IT intake ticket in ServiceNow
- IT engineer receives device, scans serial number into enterprise asset management system
- Asset record linked to PO number and delivery date
- Device enrolled in MDM and assigned to user
- IT ticket closed — record complete
The link between the PO and the asset record is critical. Auditors want to trace a device from procurement through assignment to disposal. If you can't show that chain, the audit finding is yours.
The Compounding Value of Clean Data
Asset management data compound. One accurate record this year means:
- Accurate warranty tracking next year
- Clean audit trail the year after
- Accurate replacement forecasting in year three
- Reliable procurement budgeting in year four
The organisations that struggle with asset management are the ones that treat accuracy as optional until an audit or an incident forces them to care. By then, reconstructing 3 years of device history from email chains and memory is a weeks-long project.
Build the discipline now. The cost of maintaining accurate records daily is trivial. The cost of rebuilding them from scratch is not.
Waqas Syed is a Senior IT System Engineer at SAP Saudi Arabia, managing 1,500–2,000+ IT assets across three offices in MENA. He built the IT Asset Manager web application to replace Excel-based tracking with a validated, auditable system.