Practical guides on data centre asset normalisation, DCIM platform migrations, data quality, and infrastructure management — written by practitioners, for practitioners.
Get new DCIM guides in your inbox
Practical articles on normalisation, migrations, and data quality — no spam.
Every data centre team has the same problem: asset records that look different depending on who entered them. DCIM data normalisation is the process that fixes that — and it is the foundation of every successful DCIM implementation.
NetBox's CSV import is powerful but unforgiving. One mismatched manufacturer name and the whole batch fails. This guide walks you through every step — from preparing your data to completing a clean import.
dcTrack is one of the most capable DCIM platforms available — but migrating data into it requires careful preparation. Here is what experienced DC teams know before they start.
Device42 is a powerful CMDB and DCIM platform, but a successful migration requires more than just uploading a spreadsheet. Here is what the preparation actually looks like.
Before you can implement DCIM, you need accurate asset data. But most organisations discover their inventory is far messier than they thought. Here is how to build a solid foundation.
"Dell", "Dell Inc.", "Dell EMC", "Dell Technologies" — four names, one company, and a data quality problem that will break your DCIM import. Here is how to fix it.
Running out of rack space mid-project is a preventable problem. But prevention requires accurate capacity data — and most organisations discover their capacity data is wrong only when they need it most.
The NetBox Device Type Library is one of the most valuable resources in the DCIM community. Here is how to use it effectively — and how to contribute back when your devices are not in it.
Not all asset records are created equal. A quality score tells you which records you can trust and which ones need attention before they go into your DCIM platform.
NetBox, dcTrack, and Device42 are three of the most widely used DCIM platforms. They have different strengths, different data models, and different ideal use cases. Here is how to choose.