IT Asset Management
One notebook, seven states: the asset lifecycle in OpsCloud365
From purchase order to disposal: how we model the path a device takes through IT, why goods receipt is the most important click, and what an audit has to do with trust.
“Where is Maria’s notebook, actually?” It sounds like a harmless question, and in many IT departments it still triggers a small search party. The answer lives in a spreadsheet that was correct at some point, or in an email from two years ago. When we built the asset side of OpsCloud365, this was the situation we had in mind. Our starting point: an inventory is not a list, it is a sequence of events. Record the events and the list takes care of itself.
Seven states, one path
Every asset in OpsCloud365 follows the same lifecycle. That sounds like a textbook, but it is mostly practical: a state tells you who is responsible right now and what is allowed to happen next.
“Requested” is a wish, “Ordered” a commitment, “In stock” a responsibility. The distinction is not academic. A device that has been “Ordered” for three months deserves a call to the vendor. A device that has been “In stock” for three months deserves the question why it was bought.
Goods receipt is the most important click
The moment we spent the most care on is goods receipt. Purchase orders in OpsCloud365 have lines: item, quantity, unit price. When the goods receipt is posted, the application creates the assets in stock for every hardware line automatically, with model, manufacturer, vendor, purchase date and purchase cost.
Why this mattered so much to us: whatever is not captured at goods receipt is never captured later. The purchase cost is the basis of depreciation, the vendor is the basis of warranty handling. Both are known on the day of delivery and forgotten a year later.
Check-out, check-in, maintenance
From “Deployed” onwards, the real life of a device begins. Check-out, transfer to another person and check-in are recorded with a date in the assignment history. Maintenance records carry vendor, cost and, if you want, the incident that triggered them. Later on you can see that the notebook which visited the repair shop three times this year might be better replaced.
The financials sit on the device record: purchase cost, depreciation method (straight-line or declining-balance), current book value. Add your own fields without development. In our demo data these are things like “disk encryption active” and “last patch date”, both questions that become very concrete during a security incident.
The audit as a matter of trust
An audit is often read as distrust. We see it differently: it is the moment when the list and reality meet. In OpsCloud365 you create an audit for a location or for all active assets, scan or type asset tags and serial numbers, and the application marks the devices found. Whatever is missing at the end can be marked as lost, with a date, so that the discussion does not start over next year.
At the end: retire and dispose
The end is an event too. “Retire” takes the device out of use, “Dispose” closes the lifecycle with a disposal type and a note. The history stays. Whoever asks later what happened to the hard disk finds the answer on the asset, not in a binder.
Two hints work for you along the way: the home page shows devices whose warranty expires in the coming weeks and contracts that would need to be cancelled. Both follow from the data captured at goods receipt and on the contract. Same record, seen from the other side.
What we deliberately did not build
OpsCloud365 has no discovery agent of its own that hunts for devices on the network. That data already exists in most environments, in Configuration Manager, Intune or a third-party product. On request we import existing inventories from those systems and set up a regular synchronisation, instead of putting yet another agent on your devices.
If your inventory lives in a spreadsheet today: the way to a lifecycle is shorter than it looks. The first step is a goods receipt that creates assets. The rest follows from events that happen anyway.
All images show the real application with fictitious demo data.