- Version
- Download 0
- File Size 408.00 KB
- File Count 1
- Create Date September 5, 2026
- Last Updated September 5, 2026
CSDM and SSC
CSDM and SSC: Two Models, One Truth?
CSDM vs SSC is a debate playing out in almost every organisation running ServiceNow at scale. The Configuration Management team is busy populating the Common Service Data Model. Meanwhile, the SAM team is defending its Supported Software Catalogue. Both believe they own 'the list of software.' In reality, both are only half right. This free SAM Charter whitepaper explains why. It also shows how to make the two models work together instead of against each other.
What the Supported Software Catalogue Actually Governs
A Supported Software Catalogue answers a governance question: what software are we willing to let people run? It acts as a guardrail at the point of request. It also serves as a compliance boundary for Information Security, and a cost-management lever for Procurement. Crucially, entries move between approved and restricted status because a governance board decided they should. Ultimately, that decision cadence, not any single data field, is what makes an SSC valuable.
What CSDM Actually Describes
ServiceNow's Common Service Data Model, by contrast, answers a structural question: how does everything we run relate to everything else? It organises Configuration Items into Foundation, Design, Manage, Sell/Consume and Operate domains. As a result, a Software Installation can be traced through a Product Model and a Business Application. From there it links to a Business Service, all in one connected graph. In short, a spreadsheet cannot express that chain of relationships.
CSDM and SSC Should not be Competing
Treating CSDM vs SSC as a contest misses the point entirely. The SSC supplies the policy judgement that CSDM deliberately leaves out. CSDM, in turn, supplies the operational evidence the SSC cannot generate on its own. Connected properly, the two close each other's gaps. Policy status flows into the CMDB. Real installation data flows back into the catalogue's review cycle. In the end, that closed loop is worth more than either model running alone.
A Practical Migration Path
Most organisations are not starting from a blank sheet. They already have a working SSC and a ServiceNow instance somewhere on the CSDM journey. Our whitepaper sets out a seven-step method for lifting an existing catalogue into CSDM. Steps include normalising data first and mapping fields to the right domain. It finishes by automating an exception report before declaring the project done. It also covers where AI-assisted normalisation and policy-as-code are already changing what 'good' looks like.
Where SAM Charter Fits in
SAM Charter's ITAM Surgery engagement assesses 44+ Hardware and Software Asset Management processes in just two days. That includes exactly this kind of CMDB and catalogue governance gap. If your CSDM and your SSC disagree, that conversation is worth having before your next steering meeting, not after.
Download the Free Whitepaper
Get the full comparison, the seven-step migration method, and where AI-assisted normalisation is heading next. Download 'CSDM vs SSC: Two Models, One Truth?' now, free from SAM Charter.
