What’s Going Wrong?
Your CMDB has it under one naming convention, procurement has it under another, and the monitoring tool discovered it independently and gave it an ID of its own. None of them know they are describing the same thing. So the count is wrong, the licence position is wrong, and every report built on top inherits both.
What’s Going Wrong?
Equipment gets decommissioned but the record stays live. Licences renew against assets that no longer exist, support contracts cover hardware that left the building, and nobody notices because the invoice looks the same as last year. Each one is small. There are hundreds of them.
Client
Assets on Record
9 Active
3 Decommissioned
Retired 2022 - 2024
Client
Support Contract
12 Services Covered
$17,800 a year
Automatic Renew
What’s Going Wrong?
The change was approved because the impact assessment said nothing downstream would break. It listed three services and it was right about all three. What it did not know was that a daily revenue report has been reading the same data since someone in finance built it years ago.
That relationship was never entered into the CMDB. It was explained in a wiki page, agreed in a Slack thread and demonstrated on a call, none of which an assessment can read.
Yes, 3 Services Affected
Impact Assessment Complete
How We Close the gap
Asset & Service Intelligence resolves duplicate records into one asset, retires equipment and software that no longer exists, and rebuilds the dependencies your change process depends on. Impact assessments then cover the whole estate, not just the part somebody wrote down.
Master Data Management holds the canonical record underneath, matching at the point of write so duplicates are stopped as they arrive rather than cleaned up at the next audit. Every source key is preserved, so a match can be traced back and reversed if it turns out to be wrong.
No,
4 Services Affected
3 Known, 1 Flagged
!Impact Assessment Complete.
Daily Revenue Report
Not previously recorded.
