Is CSDM intended as a model for all service types, or is it IT-centric in practice?

[SwarnadeepNandy]

Hi All,
I've been working through the CSDM domains and I keep coming back to a conceptual question I can't fully resolve from the docs. Would appreciate perspectives from architects who have modelled non-IT or customer-facing services.

My reasoning so far

CSDM stands for Common Service Data Model — not Common IT Service Data Model. And the Service Consumption domain is described as serving internal or external consumers, with tables used by both Service Portfolio Management and CSM. The business service examples in the docs are non-IT anyway (Manage HR, procurement, shipping, finance).

That pushes me toward reading CSDM as a model for service in the general sense — IT service, HR service, Customer service, Workplace service — where a service can be provided by any persona and consumed by anyone, and a catalog is simply the menu through which it's consumed (restaurant menu, service catalog, product catalog — same concept, different context).

Where I see the structural parallel

On the ITSM side: Business Service → Business Service Offering → published in a Service Catalog, with the offering carrying commitments/SLAs.

On the CRM side: Product → Product Offering → published in a Product Catalog.

The shapes look isomorphic to me. And the CSM/CSDM documentation seems to confirm they're not entirely separate worlds: Sold Product references Product Model [cmdb_model] or Service Model [cmdb_service_product_model], a Service Model references Service Offering [service_offering], Sold Product itself references Service Offering to identify subscribers, and catalog items are tied back via [sn_prod_cat_rel_m2m_product_catalog_item].

So the documented meeting point between CRM and CSDM appears to be Service Offering, rather than a parallel product hierarchy.

My questions

1. Is CSDM intended to cater to all service types, with the IT-heavy content simply reflecting where adoption started — or is the scope genuinely bounded to what lives in the CMDB?
2. Given that Product Model is a model/specification record while Business Service is an operational CI, is treating "Product : Product Offering" as analogous to "Business Service : Service Offering" sound, or is that a false analogy?
3. Does the Sold Product → Service Model → Service Offering chain still hold for the newer CRM capabilities (Sales, CPQ, Order Management, product offerings), or is that guidance scoped to classic CSM Install Base
4. For a non-IT service line (HR, Workplace, Legal), what's the recommended pattern — model it as [cmdb_ci_service_business] + [service_offering] in the Service Consumption domain, or keep it in the application's own taxonomy (e.g. HR Services) and only bridge where needed?
5. Is there any stated direction for future CSDM versions to formally bring CRM entities into the conceptual diagram, or is the intent that CRM stays adjacent and connects only at the offering/sold-product boundary?

Not looking for a single right answer — more interested in how others have reasoned about the boundary.

Thanks in advance.