How an Indonesian Digital Bank Cut Incident Resolution Time by 55%

Financial Services (Digital Banking)

Indonesia

By achieving 95% column-level lineage coverage, the bank strengthened governance, accelerated root cause analysis, and streamlined compliance reporting with Decube.

Key outcome
55% less MTTR

Mean time to resolution down 55% in four months, with 95% column-level lineage coverage

Decube modules
Column-level Lineage
Data Quality
Business Glossary
Metadata Management
Regulatory driver

OJK SLIK Reporting & Regulatory Compliance

The challenge

The bank runs on a modern but fragmented stack: dbt for transformation, Snowflake as the core warehouse, Tableau for reporting, and S3 for raw storage. Data moved cleanly through the pipeline, but visibility into how it moved did not. Tracing a single field from a dbt model through Snowflake into a Tableau dashboard meant manually cross-referencing dbt docs, Snowflake query history, and Tableau workbook metadata, three separate systems with no shared source of truth.

This became a compliance problem, not just an engineering inconvenience. OJK SLIK reporting requires the bank to demonstrate exactly where regulated fields originate and how they are transformed before submission. Without column-level lineage spanning the full stack, every reporting cycle involved reconstructing that trail by hand. On top of that, the bank had no standing data quality scorecard: errors surfaced downstream, often in a report or dashboard, with no clear way to trace them back to the responsible data owner.

The solution

The team's priority was consolidation. Rather than stitching together a lineage tool, a separate glossary product, and a bolt-on quality monitor, they wanted one platform that covered metadata management, lineage, and data quality together across their existing stack. Decube was evaluated against that requirement and chosen for exactly this reason: a single connected layer across dbt, Snowflake, Tableau, and S3, instead of multiple point solutions that each needed their own integration and upkeep.

Adoption was a second deciding factor. The platform needed to be approachable enough for compliance and governance stakeholders who are not engineers, while still being technical enough that the data engineering team would actually use it day to day rather than treat it as a reporting afterthought. Decube was rolled out across all four systems, with column-level lineage, a business glossary, and data quality scorecards tied to named data owners deployed as the core workflow.

Results in practice

End-to-end lineage for OJK SLIK reporting

Column-level lineage now spans the full path from dbt models through Snowflake into Tableau, with 95% coverage across the bank's data estate. What used to require manually reconstructing a field's history across three tools is now a direct lookup, giving compliance a defensible, auditable trail for every regulated field going into SLIK submissions.

Ownership-driven data quality

Every business term used across reporting is now mapped in a shared glossary, and data quality scorecards attribute error rates directly to the data owner responsible for that source. Instead of quality issues surfacing anonymously downstream, they route back to a named owner automatically.

Faster incident response

With lineage and ownership already mapped, the team no longer starts incident response by figuring out what broke and whose problem it is. Mean time to resolution dropped 55% over four months as investigations moved straight from symptom to root cause instead of starting with a manual trace.

The outcome

Four months in, the bank has cut incident resolution time by more than half, reached 95% column-level lineage coverage across dbt, Snowflake, and Tableau, and fully mapped its business glossary with data quality scorecards tied to accountable owners. Compliance reporting for OJK SLIK now draws on a lineage trail that exists by default, rather than one rebuilt from scratch each cycle.

“Kami sangat bangga bisa mengubah proses lineage dan pelaporan kepatuhan yang dulu tersebar di banyak sistem menjadi satu alur yang jelas dan bisa diandalkan.”

(“We are very proud to have turned lineage and compliance reporting that used to be scattered across many systems into one clear, reliable flow.”)

— Head of Data Governance

Ready for simpler compliance reporting?

Digital banks across Southeast Asia are under growing pressure from regulators like OJK to prove exactly where their data comes from and who owns it, without slowing down engineering. See how Decube's unified metadata, lineage, and quality layer can shorten your next reporting cycle.