Asset Registry
One source of truth for every asset
Every plant that grows past 20-30 machines hits the same wall: the asset list lives in three places at once — a purchase Excel with the PO numbers, a warranty folder with the AMC papers, and a supervisor's notebook with which technician actually knows how to fix the compressor. When a machine breaks down at 2 AM and the contract electrician on shift doesn't know if it's still under warranty, that gap costs real money. The Asset Registry is where AssetAI puts all of it — the machine, its paperwork, and who's allowed to touch it — on one record.
One record, not three folders
Every asset gets a company-unique code (auto-numbered as AST-000001, or your own prefix if you'd rather keep a scheme you already use — auto-numbering can also be switched off entirely) along with name, serial number, and master-linked fields for Category, Type, System type, OEM, Make, Model, Location and Owner. That last part matters more than it sounds: because these are masters, not free-text boxes, your CNC lathes all say "CNC Lathe" the same way, and a search for "Kirloskar" pulls up every pump regardless of who typed it in.
Sitting on the same record is the commercial block most CMMS tools treat as an afterthought:
- Capacity, supplier and supplier reference, year of manufacture
- PO number and date, purchase date, purchase cost, currency
- Installation date, warranty from/to with notes
- AMC applicable flag, cost, vendor, start/end and schedule
- Internal technician and supervisor, external technician contact, service vendor, remarks
This is the difference between a system that knows a machine exists and one that knows what it cost, who to call, and whether the AMC lapses next month. If your team is still asking "is this under warranty?" by digging through a supplier's email thread, this block alone justifies moving off spreadsheets — read more on what a CMMS is actually for if you're comparing options.
Skip the manual typing on the nameplate
Every machine has a rating plate riveted to it — usually in a font someone squinted at once and never again. Point a phone camera at it and AssetAI's nameplate OCR reads the serial number, year, capacity and machine name off the plate directly, appending maker and model to the description automatically. For a 150-machine plant doing a first-time registry, that's the difference between a two-week data entry project and a two-day one. It works over the web; there's no dedicated mobile app, so the flow is scan-in-browser rather than a native scanning app.
Attachments and links that work when someone else is on shift
A contract technician who's been on the floor for three weeks shouldn't need to call the plant head to find the SOP for a machine. Each asset carries:
- Machine image, PDF manual, multiple SOPs (PDF, JPG, PNG, WEBP or DWG), AMC document, and multiple compliance certificates
- Required Skills, Tools/instruments and Safety measures — the work-order screen then suggests technicians who actually hold those skills, useful when your floor has a mix of multi-lingual contract labour and permanent staff with different certifications
- A Bill of Materials — the spares fitted to that specific asset, with quantity and position, so the storekeeper knows exactly what to pull when a bearing fails
Upload limits are generous enough for real documentation — images up to 8 MB, manuals and compliance certificates up to 16 MB each — without becoming a place to dump entire ERP exports.
Statuses that match how a shift actually runs
A machine's life on the floor isn't binary. AssetAI tracks nine statuses — Draft, Active, Idle, Under Maintenance, Breakdown, Standby, Decommissioned, Retired, Scrapped — so a machine waiting on a spare part with a three-week lead time shows as Under Maintenance rather than just "not working," and a standby DG set doesn't get counted the same as an idle line. New assets start in Draft, which isn't just a status — it automatically opens an approval request carrying the purchase cost as the approval amount, so a ₹40 lakh CNC machine doesn't go live on the floor without someone signing off on the number.
Built to look like your form, not ours
No two plants record assets the same way — a foundry cares about pour weight, a pharma unit cares about qualification certificates. Rather than force every field on every plant, a company admin can switch roughly 20 optional field groups on or off, so the form matches what your plant actually fills in rather than what a generic template assumes. Pair that with list and tree views, search across name/code/serial, CSV export for whoever still wants an Excel copy, and a soft-delete Trash with restore for when someone deletes the wrong compressor by mistake.
What it deliberately doesn't do
Being direct about limits saves everyone a demo call that ends in disappointment:
- No IoT, SCADA or PLC ingestion — there's no Modbus, OPC-UA or MQTT anywhere in the product. If your registry needs to auto-populate from a live SCADA feed, this isn't that tool.
- No barcode or RFID reader integration beyond the QR code URL already used for QR-based asset tracking.
- No depreciation or book-value calculation. Purchase cost is stored exactly as entered and never amortised — finance teams needing fixed-asset accounting should keep that in their ERP; AssetAI answers "is it under warranty," not "what's its written-down value."
- No multi-currency conversion — currency is stored as a label against the cost, not converted anywhere in the system.
That makes the Asset Registry the right fit for a 20-500 machine plant moving off Excel and paper, where the real question is warranty, AMC and who supplied what — not for a finance team doing depreciation schedules, and not for a plant expecting SCADA to fill in the registry for them. Entry stays manual, via CSV, nameplate OCR, or API — a decision that keeps the record honest to what's actually on the floor.
If your registry today is a spreadsheet with three tabs and a shared drive full of AMC PDFs, it's worth seeing how one record replaces all three — check pricing against your machine count, browse industries we already work with, or book a demo and bring your worst asset spreadsheet.
The asset register as a living tree — every node with details, criticality, linked spares and history.
Every asset record in AssetAI is also a working reference for the people who maintain the machine day to day, not just a data entry for finance or audit. That connective layer — skills, tools, spares and documentation tied directly to the asset — is what separates a CMMS asset master from a spreadsheet of nameplate data.
Linking Skills, Tools and Spares to Every Asset
Each asset can carry its own list of required Skills, Tools/instruments and Safety measures. This isn't just documentation — when a work order is raised against that asset, the screen uses these links to suggest technicians who actually hold the required skills, instead of leaving a supervisor to guess who's qualified. For plants running toward TPM or formal safety programmes, this keeps competency and PPE requirements visible at the point of assignment rather than buried in a separate procedure manual.
The same asset record holds its Bill of Materials — the spares attached to it, along with fitted quantity and position. This means a technician opening a breakdown work order can see not only what skills and tools the job needs, but which spare parts belong on that specific machine and where they sit, which shortens the diagnostic step before repair rather than after it.
- Skills and safety measures are asset-specific, not generic role requirements
- Tool/instrument links flag what needs to be brought to the job before it starts
- BOM entries record fitted quantity and position, not just a parts list
What the Registry Deliberately Leaves Out
AssetAI's Asset Registry is built as a structured system of record, not a sensor platform. It does not ingest data from IoT, SCADA or PLC systems — there is no Modbus, OPC-UA or MQTT connectivity anywhere in the product, and it isn't intended to replace condition-monitoring tools. Asset identification for field use is handled through a generated QR URL rather than dedicated barcode or RFID reader integration, and the scan-and-report flow runs in a browser rather than a native mobile app.
On the commercial side, the registry stores what was paid and when — purchase cost, currency, PO details — as fixed fields. It does not calculate depreciation or book value, and currency is stored as a label rather than converted between currencies. Plants that need amortisation schedules or multi-currency consolidation should treat these as inputs to their finance system, with the registry as the source record. The full list of what's built and what isn't is on /features.
Finding and Building On Registry Data
Once assets are loaded, the registry gives you list and tree views, and search across name, code and serial — useful when a plant has thousands of similar-looking motors, pumps or panels across multiple lines. Records can be exported to CSV for reporting or reconciliation with other systems, and anything removed goes to a soft-delete Trash with restore rather than disappearing outright.
This structured, searchable asset base is also what downstream reporting depends on — reliable OEE calculations, audit trails against ISO requirements, and sector benchmarking against data such as IBEF's industry reports all start with an asset master that's complete and consistently coded. See how this plays out across sectors on /industries, or browse practical scenarios on /use-cases.
Asset Registry FAQs
How does AssetAI make sure the right technician gets called when a machine breaks down at night?
The Asset Registry stores who is authorized to work on each machine directly on the asset record, not in a supervisor's notebook. Alongside the technical and commercial fields, every asset carries an internal technician and supervisor entry, plus a field for an external technician if the job needs an outside contractor. Because this sits on the same record as the warranty and AMC details, a shift engineer opening the asset can see both who to call and whether the job is covered under contract, instead of chasing three different people or files. This is one of the core mechanics covered on the features page, where the full asset data model is laid out.
Can I keep our existing asset numbering scheme instead of switching to AssetAI's format?
Yes — asset numbering is configurable, not fixed to one pattern. By default the Asset Registry auto-numbers new assets as AST-000001, but you can set your own prefix if your plant already runs a numbering scheme on nameplates, PO records or ERP, or switch auto-numbering off entirely and enter codes manually. This matters because most plants past 20-30 machines already have asset tags in circulation, and re-tagging everything just to fit a new CMMS becomes its own project. The registry is built to sit on top of whatever identification scheme is already stuck on the machine, rather than forcing a rebuild. You can read more about how this fits the broader asset model under what is a CMMS.
How do I check if a machine is still under warranty or AMC before calling a contractor?
You check it on the same asset record, since warranty and AMC data live next to the machine's basic details rather than in a separate folder. The registry holds warranty from/to dates with notes, plus an AMC-applicable flag, AMC cost, vendor, start/end dates and schedule, all attached to that specific asset code. So when a compressor fails at 2 AM, whoever opens the record — even a contract electrician — can see coverage status without calling the purchase office or digging through an AMC folder. If you're still tracking this in spreadsheets, the resources section has downloadable templates showing how this kind of data is typically structured before it moves into a registry.
What purchase and financial details can I store against each asset — or is it just technical specs?
No — alongside technical fields the registry also captures the commercial history of the asset: what was paid, when it was installed, and which PO and supplier it came from, all stored as separate fields on the same record rather than in a purchase Excel. Because currency is one of those fields, plants that import machinery or operate across group companies can log cost in the actual transaction currency instead of converting it first. This means a finance or audit review can open one asset and see purchase cost, PO number and installation date without cross-referencing a separate spreadsheet. This commercial block is part of the full data model shown on the features page.
Does Asset Registry help with ISO audits or compliance documentation for equipment?
It helps by giving an auditor one consolidated asset record instead of three separate sources to cross-check. Because master-linked fields such as Category, Type, OEM, Make and Model are shared across the plant, and commercial and AMC data sit on the same record, someone checking equipment history or contract coverage can pull a single asset code rather than reconciling a purchase Excel, a warranty folder and a supervisor's notebook. This doesn't replace a quality management system, but it does reduce the number of places information about a machine has to live before an audit. For plants working toward ISO-aligned maintenance practices, the standards page covers how AssetAI's structure lines up with common requirements.
What happens to an asset's history if I move it to another location or plant?
The asset keeps its history because Location is a master-linked field on the record rather than something baked into the asset code itself. Moving a machine means updating the Location field, and the same asset code continues to carry its OEM, purchase, warranty, AMC and technician data forward — you're not creating a new asset or losing the paper trail that already exists. This matters for plants running more than one facility and periodically redeploying equipment between them, since the commercial and maintenance history stays attached to the physical machine rather than the site it happened to sit at when purchased. How multi-site manufacturers structure this is covered further under use-cases.
Can I track which assets belong to which production line or cost center for allocation purposes?
Yes. AssetAI lets you tag assets with cost centers, production lines, and departments. This helps you allocate maintenance spend accurately across your plant's different units. When you generate maintenance reports, you can filter by these custom groupings to see real costs per line.