CSDM practitioners — how are you thinking about the architecture side of this work?

[DebanshR]

Hi all — I work in ServiceNow talent advisory and I'm curious how people here are approaching CSDM in their day-to-day — whether that's refining service mapping models, working on governance/data quality, or moving into architect-level ownership of the data model itself.

If anyone's open to a quick chat about what's happening in the market right now, happy to connect and share what I'm seeing on the hiring side for CMDB/CSDM architecture roles. Feel free to DM.

[Vikram Reddy]

Hello @DebanshR,

I'll answer this from the practitioner side, since that's what I can speak to with certainty: assuming most people reading this are working architecture on an instance that's already live rather than a greenfield build, the CSDM work has quietly shifted from a modeling problem to a governance problem.

The modeling part is mostly solved on paper. ServiceNow's own CSDM 5.0 white paper lays out seven domains now: Ideation & Strategy, Design & Planning, Build & Integration, Foundation, Service Delivery, Service Consumption, and Manage Portfolios, the last two being new in 5.0. What's actually hard, and where architect-level ownership lives, is deciding which parts of that model your org genuinely needs to populate versus which are aspirational, and then holding that line once delivery teams start populating cmdb_ci_business_app, cmdb_ci_service, and service_offering with whatever gets a CSM or ITOM go-live out the door fastest.

Day to day, that looks like owning class model extensions (new CI class versus reusing an existing one with attributes), setting reconciliation identification rules so Discovery and Service Mapping stop creating duplicate CIs across horizontal discovery runs, and running the CMDB Workspace health scorecards, Completeness, Correctness, Compliance, and Relationship Health, as a recurring ritual rather than a one-time cleanup before an audit. Compliance is the one that trips people up because it checks actual field values against expected values you have to define yourself, it doesn't mean anything until someone documents what "correct" looks like per class.

Worth knowing if you're mid-migration: Application Service is being renamed to Service Instance under the newer CMDB CI class models, with new subclasses for data, network, connection, and facility service instances. That kind of change is exactly why CSDM version upgrades need to be treated as a planned migration with an architect signing off, not something that just happens quietly during a platform upgrade.

Thank you,
Vikram Karety
Octigo Solutions INC