Here’s a sample DDA template/checklist tailored for a bank:
Parties
- Data Provider: [Business Unit / System of Record]
- Data Consumer: [Receiving Department / Use Case]
- Platform: [Common Data Platform (Data Lake / Warehouse / Hub)]
1. Dataset Definition
- Name: [e.g., “Daily Customer Master Data”]
- Business Purpose: [KYC, Risk Reporting, CRM, etc.]
- Owner / Steward: [Responsible data owner]
- Data Classification: Confidential / Personal / Restricted
2. Delivery Specifications
- Content: [Fields, business definitions, reference data rules]
- Format: [Parquet, CSV, Delta Table, API feed]
- Delivery Frequency: [Daily 07:00 CET, near real-time, monthly]
- Delivery Method: [S3 bucket, Kafka topic, Snowflake table]
- Retention Period: [e.g., 7 years (Basel/Finance), 5 years (AML/KYC)]
3. Data Quality & SLAs
- Accuracy: [≥ 99.5% records must be valid per business rules]
- Completeness: [All transactions after T+1 included]
- Timeliness: [Delivered no later than 07:00 CET next business day]
- Validation Reports: [Daily data quality report to consumer]
- Error Handling: [Escalation to provider + platform ops within 2 hours]
4. Responsibilities
- Provider: Ensures correctness, timeliness, and schema stability.
- Consumer: Uses data only for agreed purposes; reports anomalies.
- Platform: Enforces access control, lineage, monitoring, encryption.
5. Compliance & Risk
- Privacy Rules: [PII masked if not needed, GDPR legal basis documented]
- Auditability: Full lineage from source to consumer must be traceable.
- Access Control: Role-based, least-privilege principle, MFA required.
- Regulatory Alignment: Must support internal and external audits (e.g., ECB, DNB, ECB-TRIM).
6. Change & Version Management
- Schema Changes: Announced ≥ 30 days in advance.
- Business Meaning Changes: Announced ≥ 60 days in advance.
- Backward Compatibility: Provider ensures stable delivery.
- Versioning: Dataset version maintained in catalog.
7. Governance
- Data Catalog Registration: Mandatory entry in enterprise data catalog.
- Data Steward: Named steward for business definitions.
- Monitoring: Quality and SLA metrics logged in platform.
- Review Cycle: Agreement reviewed annually.
In practice at a bank, these DDAs are often:
- Standardized templates managed by Chief Data Office (CDO) or Data Governance Office.
- Stored in a data catalog tool (Collibra, Informatica, Alation).
- Linked to data lineage, quality dashboards, and risk controls.