Skip to main content

BIAN Mapping

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

Mapping file: triodian-bian.context.jsonld
Mapping Version: 1.0.0
Context URI: https://triodian.com/context/triodian-bian.jsonld
Format: JSON-LD context

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?​

BenefitDescription
Industry alignmentSpeak the same language as banking ecosystem
API interoperabilityEnable service-oriented integration
Vendor compatibilityAlign with BIAN-compliant solutions
Regulatory communicationUse recognized terminology with regulators

Domain Mappings​

Core Domain Mappings​

Triodian DomainContext TermMaps ToBIAN Service Domain Examples
Capabilitiescapabilitybian:BusinessCapabilityCredit Administration, Customer Management
Servicesservicebian:ServiceDomainSavings Account, Current Account, Card Case
Stakeholderstakeholderfoaf:AgentCustomer, Employee, Third Party
Value StreamvalueStreambian:ValueStreamCustomer Onboarding, Loan Origination
Initiativesinitiativebian:InitiativeProgramDigital Transformation, Regulatory Change
Policypolicybian:PolicyRuleCredit Policy, KYC Policy
Performanceperformancebian:PerformanceAssessmentService Level, Quality Metrics

The context has no term for the Information or Products domains: BIAN service domains cover the information and products they manage, so those are aligned through the service domain rather than mapped directly.

Strategic Response Model Mappings​

SRM ComponentContext TermMaps ToDescription
Triggertriggerbian:TriggerEventEvent prompting business response
Rationalerationalebian:RationaleForChangeJustification for strategic action
Strategic ResponsestrategicResponsebian:ResponseStrategyPlanned organizational response

JSON-LD Context​

The mapping is a JSON-LD context: reference it from Triodian JSON to interpret the records as linked data. Terms it does not list fall into the Triodian namespace https://triodian.com/ontology# through @vocab. This is the complete file:

interoperability/triodian-bian.context.jsonld
{
  "@context": {
    "@vocab": "https://triodian.com/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",
    "cost": "schema:cost",
    "risks": "bian:Risk",
    "toolsAndTechnologies": "bian:SupportingTool",
    "improvementOpportunities": "bian:EnhancementOpportunity",
    "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​

Each term in the context maps a Triodian attribute or element to a BIAN, schema.org or FOAF concept.

Common Attributes​

Triodian TermMaps To
titleschema:name
descriptionschema:description
purposebian:FunctionalPurpose
ownerschema:accountablePerson
orgUnitTitleschema:department

Capability Elements​

Triodian TermMaps To
capabilitybian:BusinessCapability
capabilityFunctionbian:FunctionalComponent
capabilityComponentbian:CapabilityComponent
capabilityProcessbian:ProcessComponent

Capability and Value Stream Attributes​

Triodian TermMaps To
inputsbian:InputSpecification
outputsbian:OutputSpecification
processesbian:ProcessSpecification
performanceIndicatorsbian:PerformanceIndicator
dependenciesbian:Dependency
complianceAndStandardsbian:ComplianceGuideline
strategicAlignmentbian:StrategicGoalAlignment
costschema:cost
risksbian:Risk
toolsAndTechnologiesbian:SupportingTool
improvementOpportunitiesbian:EnhancementOpportunity

Domains and SRM Components​

Triodian TermMaps To
stakeholderfoaf:Agent
valueStreambian:ValueStream
servicebian:ServiceDomain
policybian:PolicyRule
initiativebian:InitiativeProgram
performancebian:PerformanceAssessment
triggerbian:TriggerEvent
rationalebian:RationaleForChange
strategicResponsebian:ResponseStrategy

Example: Capability in JSON-LD​

{
  "@context": "https://triodian.com/context/triodian-bian.jsonld",
  "@type": "capability",
  "@id": "https://example.com/capabilities/CAP-001",
  "capabilityID": "CAP-001",
  "title": "Customer Onboarding",
  "description": "Capability to register and verify new customers across all channels",
  "purpose": "Enable compliant customer acquisition",
  "owner": "Head of Customer Operations",
  "bian:serviceDomain": [
    "bian:PartyReferenceDataDirectory",
    "bian:CustomerWorkbench",
    "bian:PartyAuthentication"
  ],
  "performanceIndicators": "Onboarding completion rate (target 95%)",
  "strategicAlignment": "Digital-first customer acquisition"
}

BIAN Service Domain Coverage​

Mapped Service Domains​

The following BIAN service domains have established mappings:

BIAN Service DomainTriodian DomainCoverage
Customer ManagementCustomerFull
Current AccountProducts, ServicesFull
Savings AccountProducts, ServicesFull
Credit AdministrationFinance, Risk ManagementFull
Payment ExecutionValue StreamPartial
Regulatory CompliancePolicy, Risk ManagementFull
Party AuthenticationCapabilitiesFull
Customer WorkbenchValue StreamFull

Implementation Considerations​

When implementing BIAN mappings:

  1. Service granularity — BIAN service domains are finer-grained than Triodian capabilities
  2. Control records — BIAN's lifecycle patterns map to Triodian 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-Triodian-Context: bian-mapping

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

{
  "@context": "https://triodian.com/context/triodian-bian.jsonld",
  "@type": "capability",
  "capabilityID": "CAP-001",
  "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 — Reference triodian-bian.context.jsonld 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.

Last updated on