CSDM

CSDM attribution & coverage

The upper layers of CSDM — capabilities, business services, ownership — cannot be discovered; they can only be declared by people who run the business. ServiceMatch builds the service model from evidence-backed stakeholder claims, then attributes devices to it with a discipline designed around one rule: never fake a business placement.

Two-layer attribution

Multi-signal scoring places hosting infrastructure at business-service granularity across a dozen signal types, with frequency-based damping so a signal shared by a fifth of the fleet contributes nothing.
Evidence matching upgrades placements to named offering leaves when device-content evidence supports it, with the full evidence trail on the assignment.

The confirm bar

A placement is confirmed only when evidence found on the device itself supports it — installed applications, registered services. Corroborating context (mappings, naming, department) can support a confirmation but can never anchor one, and structural defaults can never confirm anything. Everything below the bar stays pending, visible, and waiting for a person. No engine release ships unless validation demonstrates zero false confirmations against the evaluation corpus; the calibration gate that enforces this must stay green for any change to ship.

Endpoints park honestly

End-user devices are not force-attributed to business services on soft signals like department or location. They attach to the technology management service that actually operates them, with the departmental context preserved as an overlay for the day real evidence arrives. Per-offering opt-in exists for the cases where endpoint placement is genuinely right.

Coverage is a three-way split

Design Principle

Coverage is always reported as business-attributed / management-service / unassigned — computed by one shared predicate, so the dashboard, the exports, and the emitted relationships can never disagree. A single flattering percentage is banned vocabulary.

CSDM 5.0-conformant output

Emitted entities target the CSDM 5.0 table mapping, pinned by conformance tests — including the details that trip implementations up, like the legacy service_classification value that survives the Technology Management Service rename. The CSDM 5.0 workbook is generated from the governed model on demand; it is a view of the model, never a source edited by hand.