SD-13.12 — Data Platform & Integration Services

Business Domain: BD-13 Investment Data & Reporting (Cross-cutting — data) · Applies: BOTH

Purpose

Provides the data-engineering, pipeline and integration services beneath the institution’s investment data estate — the infrastructure layer the rest of BD-13 runs on. SD-13.12 moves and lands data: it operates the pipelines that carry data from source systems and vendors into the data store, integrates the institution’s investment systems with each other and with external parties, and runs the warehouse / lakehouse the data sits in. It is deliberately separated from the data-curation capabilities — it does not own a master, define a metric or interpret a figure. SD-13.12 is the substrate; the other twelve BD-13 Service Domains are capabilities that run on it. The separation keeps platform engineering and data stewardship from being conflated.

Service Operations

Data-pipeline operation — build, run and monitor the ingestion, transformation and orchestration pipelines that move data from source systems and vendor feeds into the data store on schedule and on contract.
System integration — operate the integrations between the institution’s investment systems (the order-management, accounting, risk, portfolio and analytics systems) and with external parties (custodians, administrators, brokers, data vendors), including the messaging, APIs and file transfers between them.
Data-warehouse / lakehouse management — run the central analytical data store the certified datasets and reporting are built over — storage, compute, partitioning, performance.
Data-store and environment provisioning — provision and manage the data environments — production, test, development — and the access to them.
Pipeline observability and SLA management — monitor pipeline health, freshness and throughput against the data-delivery SLAs the consuming Service Domains depend on, and manage failures and reprocessing.
Interface and contract management — maintain the data-interface contracts — the agreed schema and delivery terms — between producing and consuming systems, so an upstream change does not silently break a downstream consumer.
Platform security and resilience — apply the data-platform-level security controls and the backup, recovery and resilience arrangements, in line with the firm’s enterprise security and continuity standards (SD-14.5, SD-14.6).

Inputs and outputs

Inputs: data from source systems across BD-01 to BD-12 and from external parties; the vendor feeds SD-13.4 manages; the interface contracts and SLAs.
Outputs: the operational data platform — the pipelines, the integrations, the warehouse / lakehouse — on which every other BD-13 Service Domain runs and through which the firm’s data moves. Its direct consumers are the BD-13 Service Domains that curate, govern, define and report data; indirectly it serves the whole model.

Entities

Owns: none — SD-13.12 is an infrastructure Service Domain. It moves, lands and stores the entities other Service Domains own; it does not own business-data entities or platform-metadata entities itself. The interface contracts and pipeline definitions are operational artefacts of the Service Domain.
Consumes: the full entity model as the data it transports and stores — it is data-content-neutral by design; the vendor feeds SD-13.4 manages.
Note: OpenIM models the data platform capability. Each implementation chooses its warehouse or lakehouse, orchestration tools, pipeline tools and integration patterns.

Standards

DAMA-DMBOK — the data-integration and data-architecture knowledge areas.
Data-interface and messaging standards — used where the institution integrates with external parties; the specific standards (file formats, messaging protocols, financial-messaging standards such as ISO 20022 for the cash and settlement interfaces) are integration-point-specific.
Enterprise security and resilience standards — the platform inherits the firm’s SD-14.5 Cyber & Information Security and SD-14.6 Operational Resilience & Business Continuity requirements.
The platform layer is otherwise technology-neutral in the model by design.

Open extensions

The data-interface-contract model — making the producer / consumer contract an explicit, governed artefact.
The data-delivery-SLA model and its link to SD-13.7 data-quality timeliness rules.
Reusable mappings from this capability to implementation-specific platform choices.