BIAN

Introduction

With the BIAN integration in place in Orthogramic—enabled through a semantic mapping between the Orthogramic Metamodel and the BIAN Service Landscape—several types of business and IT artefacts can be parsed to automatically generate output in the BIAN schema. These include files that contain structured or semi-structured representations of organisational functions, capabilities, services, and operational models. Specifically:

Business architecture documents

These often contain the foundational content needed to map to BIAN Service Domains and Control Records:

• Capability maps → Mapped to BIAN Functional Patterns and Service Domains

• Value streams → Mapped to BIAN Business Scenarios

• Organisation structure and role definitions → Mapped to BIAN Party/Role models

• Policy and compliance documents → Parsed into BIAN Governance or Regulatory Service Domains

Process documentation

Operational and service process documents can be translated into BIAN’s layered service model:

• BPMN process models (XML) → Converted into BIAN Service Operations

• Standard operating procedures (Word, PDF) → Segmented and aligned to BIAN Functional Pattern interactions

• Customer journey maps → Mapped to BIAN Business Scenarios and channel usage

IT architecture artefacts

Files that describe systems and integration points:

• Application catalogues → Used to assign applications to BIAN Service Domains

• Interface definitions (Swagger/OpenAPI, RAML) → Mapped to BIAN Service Operation APIs

• Data flow diagrams → Interpreted for Control Record lifecycles and dependencies

Strategic planning documents

Strategy documents are essential for aligning BIAN domains to enterprise strategy:

• Business strategy plans and roadmaps → Provide linkage to required BIAN capabilities

• Investment portfolio documents → Indicate targeted or upcoming BIAN Service Domains for enablement

Data models

For integration with BIAN's semantic data layer:

• ERDs or Logical Data Models (e.g. in ERwin or Sparx EA) → Mapped to BIAN Information Concepts

• Data dictionaries and glossaries → Used to populate metadata aligned to BIAN Common Reference Data Models

Regulatory and compliance submissions

Documents that articulate obligations or governance:

• APRA or Basel reporting formats → Align with BIAN Risk & Compliance Service Domains

• Operational Resilience or CPS230 documents → Mapped to BIAN Business Continuity or Risk Management services

Supported File Types for Parsing

• Structured: .json, .xml, .csv, .xlsx, .yaml

• Semi-structured: .docx, .pdf, .pptx (with section parsing)

• Visual models: .bpmn, .archimate, .drawio (with semantic layer)

• API specifications: .json (OpenAPI/Swagger), .raml

Example Output Formats

• BIAN-aligned JSON-LD (semantic API output)

• OpenAPI definitions of BIAN Service Operations

• BIAN Business Scenario mappings in RDF/Turtle

• BIAN control record and behaviour qualifier instantiations