BIAN Mapping

The Banking Industry Architecture Network (BIAN) provides a standardized service domain model for the banking industry. This page documents how Orthogramic domains map to BIAN concepts, enabling interoperability between business architecture and banking-specific reference models.

Mapping Version: 2.1
BIAN Version: 11.0
Format: JSON-LD compatible

Overview

What is BIAN?

BIAN is a collaborative, not-for-profit ecosystem that defines a semantic banking services landscape. It provides:

• Service Domains — Discrete business capabilities in banking
• Business Objects — Core data entities
• Service Operations — Standard API patterns
• Control Records — Lifecycle management patterns

Why Map to BIAN?

Benefit	Description
Industry alignment	Speak the same language as banking ecosystem
API interoperability	Enable service-oriented integration
Vendor compatibility	Align with BIAN-compliant solutions
Regulatory communication	Use recognized terminology with regulators

Domain Mappings

Core Domain Mappings

Orthogramic Domain	BIAN Concept	BIAN Service Domain Examples
Capabilities	Business Capability	Credit Administration, Customer Management
Services	Service Domain	Savings Account, Current Account, Card Case
Stakeholder	Party	Customer, Employee, Third Party
Value Stream	Value Stream	Customer Onboarding, Loan Origination
Initiatives	Initiative Program	Digital Transformation, Regulatory Change
Policy	Policy Rule	Credit Policy, KYC Policy
Information	Information Asset	Customer Data, Transaction Data
Performance	Performance Assessment	Service Level, Quality Metrics

Strategic Response Model Mappings

SRM Component	BIAN Concept	Description
Trigger	Trigger Event	Event prompting business response
Rationale	Rationale for Change	Justification for strategic action
Response	Response Strategy	Planned organizational response

JSON-LD Context

The following JSON-LD context enables semantic interoperability:

{
  "@context": {
    "@vocab": "http://orthogramic.org/ontology#",
    "bian": "https://bian.org/ontology#",
    "schema": "http://schema.org/",
    "foaf": "http://xmlns.com/foaf/0.1/",
    "dcterms": "http://purl.org/dc/terms/",
    
    "title": "schema:name",
    "description": "schema:description",
    "purpose": "bian:FunctionalPurpose",
    "owner": "schema:accountablePerson",
    "orgUnitTitle": "schema:department",
    
    "capability": "bian:BusinessCapability",
    "capabilityFunction": "bian:FunctionalComponent",
    "capabilityComponent": "bian:CapabilityComponent",
    "capabilityProcess": "bian:ProcessComponent",
    
    "inputs": "bian:InputSpecification",
    "outputs": "bian:OutputSpecification",
    "processes": "bian:ProcessSpecification",
    "performanceIndicators": "bian:PerformanceIndicator",
    "dependencies": "bian:Dependency",
    "complianceAndStandards": "bian:ComplianceGuideline",
    "strategicAlignment": "bian:StrategicGoalAlignment",
    
    "stakeholder": "foaf:Agent",
    "valueStream": "bian:ValueStream",
    "service": "bian:ServiceDomain",
    "policy": "bian:PolicyRule",
    "initiative": "bian:InitiativeProgram",
    "performance": "bian:PerformanceAssessment",
    
    "trigger": "bian:TriggerEvent",
    "rationale": "bian:RationaleForChange",
    "strategicResponse": "bian:ResponseStrategy"
  }
}

Detailed Mappings

Capability Domain → BIAN Business Capability

Orthogramic Attribute	BIAN Property	Notes
title	bian:capabilityName	Direct mapping
description	bian:capabilityDescription	Direct mapping
purpose	bian:functionalPurpose	Semantic alignment
owner	bian:capabilityOwner	Role mapping
performanceIndicators	bian:performanceIndicator	Array mapping
dependencies	bian:capabilityDependency	Reference mapping
strategicAlignment	bian:strategicGoalAlignment	Link to strategy

Service Domain → BIAN Service Domain

Orthogramic Attribute	BIAN Property	Notes
title	bian:serviceDomainName	Direct mapping
description	bian:serviceDomainDescription	Direct mapping
serviceType	bian:serviceType	Enum mapping required
serviceChannel	bian:channelType	Enum mapping required
serviceLevelAgreement	bian:serviceLevelSpecification	SLA mapping

Stakeholder Domain → BIAN Party

Orthogramic Attribute	BIAN Property	Notes
title	bian:partyName	Direct mapping
stakeholderType	bian:partyType	Customer, Employee, etc.
influence	bian:partyRole	Role-based mapping
expectations	bian:partyExpectation	Array mapping

Example: Capability in JSON-LD

{
  "@context": "https://orthogramic.org/context/orthogramic-bian.jsonld",
  "@type": "capability",
  "@id": "cap:customer-onboarding",
  "title": "Customer Onboarding",
  "description": "Capability to register and verify new customers across all channels",
  "purpose": "Enable compliant customer acquisition",
  "owner": {
    "@type": "stakeholder",
    "title": "Head of Customer Operations"
  },
  "bian:serviceDomain": [
    "bian:PartyReferenceDataDirectory",
    "bian:CustomerWorkbench",
    "bian:PartyAuthentication"
  ],
  "performanceIndicators": [
    {
      "@type": "bian:PerformanceIndicator",
      "title": "Onboarding Completion Rate",
      "targetValue": 95,
      "unit": "percent"
    }
  ],
  "strategicAlignment": {
    "@type": "bian:StrategicGoalAlignment",
    "strategicGoal": "Digital-first customer acquisition"
  }
}

BIAN Service Domain Coverage

Mapped Service Domains

The following BIAN service domains have established mappings:

BIAN Service Domain	Orthogramic Domain	Coverage
Customer Management	Customer	Full
Current Account	Products, Services	Full
Savings Account	Products, Services	Full
Credit Administration	Finance, Risk Management	Full
Payment Execution	Value Stream	Partial
Regulatory Compliance	Policy, Risk Management	Full
Party Authentication	Capabilities	Full
Customer Workbench	Value Stream	Full

Implementation Considerations

When implementing BIAN mappings:

1. Service granularity — BIAN service domains are finer-grained than Orthogramic capabilities
2. Control records — BIAN's lifecycle patterns map to Orthogramic domain elements
3. Business objects — Map to Information domain entities
4. Service operations — Map to Value Stream activities

API Integration Pattern

REST API with BIAN Headers

GET /api/v1/capabilities/customer-onboarding
Accept: application/ld+json
X-BIAN-Version: 11.0
X-Orthogramic-Context: bian-mapping

HTTP/1.1 200 OK
Content-Type: application/ld+json

{
  "@context": "https://orthogramic.org/context/orthogramic-bian.jsonld",
  "@type": "capability",
  "title": "Customer Onboarding",
  "bian:serviceDomain": ["bian:PartyReferenceDataDirectory"]
}

Usage Guidelines

When to Use BIAN Mappings

• Banking organizations implementing BIAN-aligned architectures
• Financial services vendors building BIAN-compatible products
• Regulators requiring standardized architectural documentation
• Integration projects connecting to BIAN-compliant systems

Mapping Best Practices

1. Use JSON-LD context — Include the context for semantic interoperability
2. Reference BIAN IDs — Use official BIAN service domain identifiers
3. Document gaps — Note where mappings are partial or approximate
4. Version align — Specify which BIAN version the mapping targets

For Data Engineers

BIAN mappings enable automated population of banking-specific data catalogs. When integrating with OpenMetadata, use the BIAN service domain tags to classify data assets by their business capability alignment.

Related Documentation

• SAP EAF Mapping — Enterprise architecture framework mapping
• FIBO Mapping — Financial ontology mapping
• External Organizations — Cross-enterprise modeling