Bridging BIAN and ServiceNow CSDM — a discussion paper for financial services architects

[doug_macpherson]

Over the past eight months, a working group spanning BIAN and ServiceNow has been quietly working on a question that nobody had cleanly answered: if BIAN defines what a bank does, and CSDM describes how ServiceNow manages the systems that do it — why aren't they connected?

Today we're sharing the result.

Bridging BIAN and ServiceNow CSDM: Enterprise Architecture Integration for Financial Services Institutions (v7.6) is a discussion paper that defines a unified metamodel giving financial institutions something they've never had from a single platform: bidirectional traceability from board-level strategic intent to the APIs running in production — and back again.

Although Vinod Hariharan and I led the work, the working group brought together architecture expertise from both organisations, expert Enterprise Architecture consultancy and, critically, the voice of some key FSI EA customers, stress-testing the model assumptions and contributing throughout.

The architecture is deliberately lean. Two custom objects and some pre-existing CSDM tables. The full BIAN v14.0 Service Domain taxonomy (all 328 domains, Business Areas and Business Domains) loads into these tables with relationships established. The organisation simply requires to connect its business applications and integrations to finalise the traceability.

The key insight that unlocked the whole model: BIAN's Service Domain is the Rosetta Stone. It is canonically defined, vendor-neutral, and stable across any deployment. Once it lives in CSDM as a configuration item, it becomes the synchronisation point between BIAN's strategic framework and CSDM's operational reality. Everything else follows from that single design decision.

The paper works through four concrete business outcomes:

• Business strategy: competitive positioning and capability gap analysis, expressed in a language that technology can act on
• Investment and business planning: portfolio decisions grounded in evidence, not assembled from stakeholder opinion; capability overlap assessed in weeks
• Regulatory compliance: obligations traced to Service Domains and implementing systems, with audit evidence generated on demand rather than manually constructed
• Operational impact analysis: from CVE or outage to confirmed business impact in real time, enabling AI or human workflows to act on the business context the metamodel provides

We're publishing this to start a conversation, not to close one.

The paper is attached. The graphic summarises the traversal chain from strategic classification to customer-facing service.