IMAC Asset Register and CMDB Updates

Quick answer

What is IMAC Asset Register and CMDB Updates?

An IMAC asset register update is the record change made after each install, move, add, change, or disposal so your inventory matches what is physically in the building. Deploris engineers capture serial numbers, asset tags, location, and lifecycle status at the device, and deliver the corrected records in your agreed format.

WHAT THE WORK COVERS

What IMAC Asset Register and CMDB Updates includes.

01Serial number and asset tag capture by scan or photo at the device, matched against the existing register entry

02Full location hierarchy per asset: site, building, floor, room, desk or rack unit, and patch panel port where relevant

03Lifecycle status transitions such as in stock, deployed, in repair, retired, and disposed

04User or owner assignment and cost center changes when a device moves between people or teams

05Component-level changes such as added RAM, a replaced SSD, or a new dock, linked to the parent configuration item

06CMDB relationship corrections, for example device to switch port or monitor to workstation

07Reconciliation exceptions flagged for review: untagged devices, duplicate serials, and assets found that are not in the register

HOW WE DELIVER IT

How it is delivered.

1
Agree the data model
We confirm which fields, status values, and tagging conventions your register uses, plus whether updates go in as a structured file or directly into your asset tool under the access you grant.
2
Capture at the device
The engineer records serial, tag, location, and status while the asset is in hand, using a consistent template so data is not re-keyed from memory later.
3
Validate and reconcile
The engagement manager checks each record against the existing register, resolves duplicates and mismatches where possible, and lists anything that needs a decision from your asset owner.
4
Deliver and confirm
Corrected records are delivered with a before and after change log. Your asset owner confirms receipt, and open exceptions stay tracked until closed.

INPUTS AND OUTPUTS

What you provide and what you receive.

You provide

A current register export, or read and write access to your asset management tool or CMDB if direct updates are agreed
Your field schema, mandatory fields, and status taxonomy
Your asset tagging convention and any label stock for new devices
A named data owner who resolves mismatches and approves exceptions

You receive

A before and after change log linked to each work order
A reconciled register export or direct record updates in the agreed format
A list of exceptions: untagged, duplicate, missing, and unexpected assets with locations
Photos of asset tags and serial labels attached to the relevant records

WHEN IT FITS

When this is the right deliverable.

Scenario 01

Your last audit found that a large share of desks hold devices that the register places elsewhere, and you want every future move to correct the record.

Scenario 02

A CMDB owner needs each hardware change linked to the right configuration item so change and incident records stay trustworthy.

Scenario 03

A finance or procurement team needs retired devices marked disposed with a date, so depreciation and licensing counts stop including them.

WHERE WE DELIVER

Delivered in 75+ metros across 11 countries.

Local, vetted engineers deliver this work on site across the United States and Western Europe, coordinated by one engagement manager.

United States Germany Austria Switzerland France Italy Spain Netherlands United Kingdom Ireland Portugal

View full coverage

QUESTIONS

Frequently asked questions.

Why does asset register accuracy matter after IMAC work?

Register drift after moves and swaps causes failed audits, wrong license counts, misrouted support tickets, and spare stock that cannot be found. Updating the record at the moment of the physical change is the cheapest way to prevent it, because the engineer is standing at the device with the serial in hand.

What data do engineers capture for each asset?

Typically serial number, asset tag, make and model, location down to desk or rack unit, assigned user, and lifecycle status. Added components and connected peripherals can be recorded too. The exact fields follow your schema and are listed in the written scope before the first work order is dispatched.

Can you update our CMDB directly?

It depends on the access you grant and what your tool supports. Where direct access is approved, Deploris can update records as part of closing each order. Otherwise we deliver a structured file in your format for your asset owner to import. Either route is agreed in the written scope.

What do you do with assets that are not in our register?

We record them with photos, serial, and location, tag them if you supply labels, and list them as exceptions instead of silently adding or ignoring them. Your data owner then decides whether to add, reassign, or retire each one. Nothing is deleted from the register without your approval.

MORE DELIVERABLES