Interface is CIs, too (CSDM v5)

[seungchulkim]

One question comes up on almost every ServiceNow project:

"How do we get our I/F inventory into the CMDB?"

The usual answer has been a custom table, or forcing interfaces into cmdb_ci_appl. Either way, when an incident or change hits, nobody can quickly answer:

"If we take this server down, which integrations break?"

CSDM v5 introduces a class built for exactly this, so I modeled it end to end on a PDI

(simple scenario: SAP S/4HANA → MES production order sync).

CSDM v4 → v5

▪ Model: Application Service-centric → Service Instance as the parent, split into purpose-based sub-types

▪ New: Data Service Instance (cmdb_ci_data_service_instance)

▪ Integrations: from a relationship line only → a standalone CI with its own owner, attributes and lifecycle

▪ ITSM: interfaces become selectable on Incidents/Changes, with real impact analysis

Why a cmdb_ci subclass instead of a custom table

• It's selectable in the standard CI field on Incident and Change

• It doesn't consume your custom table license quota : )

• Service Graph Connector (e.g MulSoft) loads into this same class, so you're aligned with the vendor's direction

• Structured relationship data is what Now Assist needs for AI-driven RCA

Interfaces break and get changed just like servers do. Treat them as first-class CIs, not rows in a spreadsheet.

Is your Interface inventory still living in Excel?

How does your team manage integration inventory today?