Asset management
Every asset gets its own file.
An asset is anything with a unique number: a printer, a boiler, a laptop or a case file. Everything that happens to it lands on one timeline: requests, visits, meter readings, contracts and costs.
- Email: “boiler shows F28, serial 21K-48812”today 08:12Ticket linked
- Work order: annual service, signedSep 12
- Service contract invoice Q3Jul 1
- Installed by technician NandoMar 4, 2023
What you record per asset
The number customers and technicians know it by.
Asset types with their own fields, which can inherit from each other.
Customer, location, floor, department and who to call.
Active, in the warehouse, in maintenance or retired.
Every change with who and when, ready to read back.
Which parts and products belong to the asset.
Parts and labour added up per asset.
Attach a task to the asset so nothing is left lying around.
Mention the serial number and onecloud.works knows what it's about.
When an email or ticket contains a serial number, onecloud.works looks up the asset. If the match is certain, the ticket is linked straight away. If not, you get a suggestion.
- Recognises “serial number”, “S/N” and Dutch “serienummer”
- Link automatically or suggest
- Several assets on one ticket
Good morning, the boiler in the basement of block B (serial 21K-48812) has been showing fault F28 since last night…
Printers, boilers or case files: you choose the fields.
Create asset types with the fields your trade needs. A heat pump gets a capacity and an inspection date, a printer a meter reading. The words change too: if your team calls an asset an installation, that is what it is called everywhere.
- Asset types with inheritance
- Fields that only show when relevant
- Your own terms throughout the system
Counters and running hours without retyping.
Meter readings come in from the technician, from the customer portal or straight from MPS Monitor and Printanista. onecloud.works queues unusual readings for review before anything is invoiced.
- Fetched per serial number
- Reviewed before billing
- Usage per asset over time
Works for anything with a number on it
onecloud.works started with printer and copier companies, where every device has a serial number, a contract and a meter reading. You see the same pattern wherever unique assets are managed, serviced or rented out.
Printers and multifunction devices
Meter readings, toner and click rates per device. This is where onecloud.works started.
Boilers and heat pumps
Every boiler, heat pump and air conditioner with fault history and service contract.
Elevators and escalators
Scheduled maintenance, inspections and faults per elevator, with the history attached.
Laptops, servers and network
Hardware per customer and per user, with warranty, lease contract and tickets.
Rental equipment
Who has what, until when, and in what state it comes back.
Buildings, units and installations
Buildings and units with resident requests, contracts and maintenance.
Production machinery
Delivered machines with parts, running hours and service history at your customer.
Case files with their own number
Anything with a file number, its own timeline and a next step.
Call it what you call it. If an asset is an installation, a machine or a case file in your company, that is what it is called throughout the system.
Every industry and exampleFrequently asked questions about asset management
Also part of it
Bring a serial number. We'll show you what happens.
In a demo we show onecloud.works with examples from your daily work: your kind of assets, your contracts and the way you work.