Every other discipline — AI governance, security, portfolio delivery — depends on knowing what you have and trusting the data that describes it. I build the CMDB and data architecture that becomes that foundation: accurate, governed, and mapped to the services your business actually runs on.
Most CMDBs decay into a graveyard of stale, duplicated, and orphaned records — populated once, then never trusted again. Teams route around it, and every downstream decision inherits the doubt.
That's expensive, because the CMDB is load-bearing. Change management, incident response, asset and license optimization, security vulnerability prioritization, and now AI asset governance all rest on it. When the foundation is shaky, the whole estate is.
A CMDB done right is the opposite: a living, governed source of truth — discovered automatically, mapped to real business services through CSDM, and owned by people who trust it because it's accurate.
Design or rebuild the CMDB from the ground up — class structure, CI relationships, data model, and the governance that keeps it trustworthy over time.
Implement the Common Service Data Model so your data maps to real business and application services — the structure modern ServiceNow capabilities expect.
Stand up Discovery and Business Service Mapping (with MID Servers, where needed) so the CMDB populates and stays current automatically — not by hand.
Hardware and software asset management — HAM, SAM, and SAM Pro — lifecycle, license position, and the asset-to-CI alignment that drives real savings.
Bring in data from across the estate via Integration Hub and import sets — reconciled, de-duplicated, and normalized into one authoritative record.
Assess CMDB health, fix what's broken, and put data governance, ownership, and completeness/correctness controls in place to keep it that way.
This is the line I've delivered longest and deepest. From early data-center and asset-management work to enterprise CMDB architecture today, I've built and rescued the source of truth for organizations that can't operate without one.
And it's the foundation the rest of ITProjX stands on — the same discipline of knowing what you own and proving you control it is exactly what AI governance, security, and portfolio delivery require.
Audit current CMDB health, data sources, and how the estate actually uses (or avoids) it.
Design the class model, CSDM alignment, and governance the organization needs — not a generic template.
Stand up Discovery, integrations, and reconciliation so data flows in accurate and stays current.
Hand over ownership, health dashboards, and the controls that keep the source of truth trustworthy.
Whether you're starting from scratch, adopting CSDM, or rescuing a CMDB that's lost credibility, let's scope the path to a living source of truth.