Worked example: assessing DCAM 5.0 Data QualityContoh pengisian: menilai DCAM 5.0 Kualitas Data

Follow a first-time assessor through one DCAM component, from planning to roadmap. Every score comes with the evidence behind it and the reason it is not one point higher.Ikuti asesor pemula menilai satu komponen DCAM, dari perencanaan sampai roadmap. Setiap skor disertai bukti di baliknya dan alasan mengapa tidak satu poin lebih tinggi.

DCAM 5.011 sub-capabilities11 sub-kapabilitasFictional companyPerusahaan fiktif~25 min

The situationSituasinya

PT Contoh Sejahtera Finance (fictional)PT Contoh Sejahtera Finance (fiktif)

A consumer finance company with 1.2 million customers and 140 branches. This year it had to resubmit two regulatory reports, 4% of new loan files arrive without a valid phone number or address, and internal audit flagged "recurring data errors" twice.Perusahaan pembiayaan konsumen dengan 1,2 juta nasabah dan 140 cabang. Tahun ini perusahaan harus mengirim ulang dua laporan regulator, 4% berkas kredit baru masuk tanpa nomor telepon atau alamat yang valid, dan audit internal dua kali menandai "kesalahan data berulang".

SponsorSponsor: Director of RiskDirektur Risiko
ScopeCakupan: Component 5.0 only, retail lending unitKomponen 5.0 saja, unit kredit ritel
DepthKedalaman: Full: all 11 sub-capabilitiesLengkap: ke-11 sub-kapabilitas
DurationDurasi: 3 weeks3 minggu
Why 5.0 first?Mengapa 5.0 dulu?: The pain is visible in quality; a focused start builds credibility for a full assessment later.Masalahnya terlihat di kualitas; awal yang terfokus membangun kredibilitas untuk asesmen penuh nanti.

Step 1Langkah 1

Plan: people and scheduleRencana: orang dan jadwal

Pick people who do the work, use the data and check it, not only managers.Pilih orang yang mengerjakan, memakai, dan memeriksa data, bukan hanya manajer.

ParticipantNarasumber	Why they are neededMengapa dibutuhkan
Head of Data OfficeKepala Kantor Data	Owns the DQ approach; main interviewee for 5.1Pemilik pendekatan DQ; narasumber utama untuk 5.1
Retail lending data steward (acting)Steward data kredit ritel (pelaksana tugas)	Knows where errors come from in daily workTahu dari mana kesalahan muncul dalam pekerjaan sehari-hari
Data engineer, ITData engineer, TI	Owns ETL checks and clean-up scriptsPemilik pemeriksaan ETL dan skrip pembersihan
Regulatory reporting lead, FinancePimpinan pelaporan regulator, Keuangan	Consumer of the data; signed off the CDE listPengguna data; mengesahkan daftar CDE
Risk analystAnalis risiko	Tracks data issues in the risk registerMelacak isu data di register risiko
Internal audit (observer)Audit internal (pengamat)	Raised the "recurring errors" findingsMengangkat temuan "kesalahan berulang"

Week 1Minggu 1Kick-off with the sponsor; send the evidence request (use the evidence log template).Kick-off dengan sponsor; kirim permintaan bukti (pakai templat log bukti).
Week 2Minggu 2Five 60-minute interviews, using the DCAM interview guide for 5.0.Lima wawancara 60 menit, memakai panduan wawancara DCAM untuk 5.0.
Week 3Minggu 3Calibration session to agree scores, then a one-page report to the sponsor.Sesi kalibrasi untuk menyepakati skor, lalu laporan satu halaman ke sponsor.

Step 2Langkah 2

Evidence: what was asked for, what arrivedBukti: apa yang diminta, apa yang diterima

Request evidence before interviews. Gaps here predict low scores.Minta bukti sebelum wawancara. Kekosongan di sini memprediksi skor rendah.

Artefact requestedArtefak yang diminta	StatusStatus	NoteCatatan
DQ approach and plan	PartialSebagian	Draft v0.3 only, not approvedHanya draf v0.3, belum disetujui
RACI / DQ role descriptions	MissingTidak ada	Does not existTidak ada
DQ process designs and procedures	MissingTidak ada	Fixes requested by e-mailPerbaikan diminta lewat e-mail
Critical data element inventory	ReceivedDiterima	48 CDEs, signed off by Finance and Risk48 CDE, disahkan Keuangan dan Risiko
Profiling results and procedure	PartialSebagian	One-off results from migration; procedure in draftHasil sekali dari migrasi; prosedur masih draf
DQ rule repository	PartialSebagian	Rules in ETL code; catalogue spreadsheet in progressAturan di kode ETL; spreadsheet katalog sedang dibuat
Control point documentation	MissingTidak ada	NoneTidak ada
Issue log and dashboards	PartialSebagian	Spreadsheet log, no dashboardLog di spreadsheet, tanpa dashboard
Root cause analysis records	MissingTidak ada	None; only audit findingsTidak ada; hanya temuan audit
Remediation plan and log	PartialSebagian	Draft plan for top 5 issues; clean-up scriptsDraf rencana untuk 5 isu teratas; skrip pembersihan

Step 3Langkah 3

Interviews: listening for evidenceWawancara: mendengarkan bukti

Three excerpts showing how an answer turns into a score.Tiga cuplikan yang menunjukkan bagaimana jawaban berubah menjadi skor.

5.1.1

AssessorAsesor: Is there an approved approach for data quality?Apakah ada pendekatan kualitas data yang disetujui?

IntervieweeNarasumber: "We wrote a strategy last quarter. It is still with us; we have not presented it to the Risk Committee yet.""Kami menulis strategi kuartal lalu. Masih di tim kami; belum kami presentasikan ke Komite Risiko."

ConclusionKesimpulan: A document exists and work is active, but nobody outside the team has validated it. That is Developmental (3), not Defined (4).Dokumen ada dan pekerjaan berjalan, tetapi belum ada pihak di luar tim yang memvalidasinya. Itu Developmental (3), bukan Defined (4).

5.3.2

AssessorAsesor: How do data issues get raised and closed?Bagaimana isu data dilaporkan dan ditutup?

IntervieweeNarasumber: "Anyone can add a row to the shared sheet. We added a severity column last month, but who fixes what still depends on who notices.""Siapa pun bisa menambah baris di spreadsheet bersama. Bulan lalu kami menambah kolom keparahan, tetapi siapa yang memperbaiki apa masih tergantung siapa yang menyadarinya."

ConclusionKesimpulan: Logging happens and the process is being built (3). Without agreed owners and escalation it cannot be Defined (4).Pencatatan berjalan dan prosesnya sedang dibangun (3). Tanpa pemilik dan eskalasi yang disepakati, belum bisa Defined (4).

5.2.1

AssessorAsesor: Which data is treated as critical?Data mana yang dianggap kritis?

IntervieweeNarasumber: "Finance and Risk signed off 48 elements used in regulatory reports. Lending operations has not adopted the list yet.""Keuangan dan Risiko mengesahkan 48 elemen yang dipakai di laporan regulator. Operasional kredit belum mengadopsi daftar itu."

ConclusionKesimpulan: Defined and validated by the stakeholders directly involved (4). Achieved (5) would need it maintained and used across the organisation.Sudah didefinisikan dan divalidasi stakeholder yang terlibat langsung (4). Achieved (5) membutuhkan daftar itu dipelihara dan dipakai di seluruh organisasi.

Step 4Langkah 4

Scoring all 11 sub-capabilitiesMenilai ke-11 sub-kapabilitas

Scale: 1 Not Initiated · 2 Conceptual · 3 Developmental · 4 Defined · 5 Achieved · 6 Enhanced. The grey line under each rationale explains why the score is not one point higher.Skala: 1 Not Initiated · 2 Conceptual · 3 Developmental · 4 Defined · 5 Achieved · 6 Enhanced. Baris abu-abu di bawah setiap alasan menjelaskan mengapa skornya tidak satu poin lebih tinggi.

Sub-capabilitySub-kapabilitas	NowKini	Target	EvidenceBukti	RationaleAlasan

Step 5Langkah 5

ResultsHasil

Simple averages, as in the self-assessment tool. The chart shows each gap from the current score (filled dot) to the target (ring).Rata-rata sederhana, seperti di alat asesmen mandiri. Grafik menunjukkan setiap selisih dari skor saat ini (titik penuh) ke target (cincin).

Gap per sub-capabilitySelisih per sub-kapabilitas

NowKiniTarget

CapabilityKapabilitas	NowKini	Target	GapSelisih

What the numbers sayArti angka-angka iniMeasurement (5.2) is the strongest because regulatory pressure forced a CDE list. Maintenance (5.3) is the weakest: there are no control points and no monitoring, so errors are found only after reports go out.Pengukuran (5.2) paling kuat karena tekanan regulator memaksa adanya daftar CDE. Pemeliharaan (5.3) paling lemah: tidak ada titik kontrol dan pemantauan, sehingga kesalahan baru ditemukan setelah laporan terkirim.

Step 6Langkah 6

Findings and a 12-month roadmapTemuan dan roadmap 12 bulan

Foundation first: approval and roles (5.1) unblock everything else. One quick win keeps momentum.Fondasi lebih dulu: persetujuan dan peran (5.1) membuka jalan bagi yang lain. Satu quick win menjaga momentum.

WhenKapan	InitiativeInisiatif	Closes gap inMenutup selisih di	OwnerPemilik	Success measureUkuran keberhasilan
Q1	Approve the DQ approach at the Risk CommitteeSahkan pendekatan DQ di Komite Risiko	5.1.1	Head of Data OfficeKepala Kantor Data	Approved documentDokumen disahkan
Q1	Appoint stewards for retail lending and publish a DQ RACITunjuk steward kredit ritel dan terbitkan RACI DQ	5.1.2	Director of Risk (sponsor)Direktur Risiko (sponsor)	Named stewards, RACI signedSteward ditunjuk, RACI disahkan
Q1	Quick win: move the issue log to a shared tool with owners and SLAsQuick win: pindahkan log isu ke alat bersama dengan pemilik dan SLA	5.3.2	Acting stewardSteward pelaksana tugas	All 63 open issues have an ownerKe-63 isu terbuka punya pemilik
Q2	Document DQ processes and turn ETL checks into a business-validated rule catalogueDokumentasikan proses DQ dan ubah pemeriksaan ETL menjadi katalog aturan yang divalidasi bisnis	5.1.3 · 5.2.3	DQ lead + data engineerPimpinan DQ + data engineer	Rules validated for all 48 CDEsAturan tervalidasi untuk ke-48 CDE
Q2	Put control points at branch loan entry and the regulatory report feedPasang titik kontrol di entri kredit cabang dan aliran laporan regulator	5.3.1	IT + operationsTI + operasional	Missing phone/address below 1%Telepon/alamat kosong di bawah 1%
Q3	Root cause analysis on the top 10 recurring issues; fix at sourceAnalisis akar masalah untuk 10 isu berulang teratas; perbaiki di sumber	5.4.1 · 5.4.2	DQ leadPimpinan DQ	Repeat issues down 50%Isu berulang turun 50%
Q4	Pilot automated monitoring for the 48 CDEs, then reassess 5.0Uji coba pemantauan otomatis untuk 48 CDE, lalu nilai ulang 5.0	5.3.3	Data engineerData engineer	Daily DQ dashboard liveDashboard DQ harian berjalan

Avoid theseHindari ini

Common beginner mistakesKesalahan umum pemula

Scoring without evidenceMemberi skor tanpa bukti"We do that" is not proof. No artefact usually means 3 or lower."Kami sudah melakukannya" bukan bukti. Tanpa artefak, skor biasanya 3 atau lebih rendah.

Confusing Defined with AchievedTertukar antara Defined dan AchievedDefined (4) is approved on paper; Achieved (5) is running and followed.Defined (4) berarti disetujui di atas kertas; Achieved (5) berarti berjalan dan dipatuhi.

Scoring the plan, not the presentMenilai rencana, bukan kondisi kiniNext quarter's project belongs in the target score, not the current one.Proyek kuartal depan masuk ke skor target, bukan skor saat ini.

Setting every target to 6Menetapkan semua target ke 6Targets should be realistic for 12–18 months. Here monitoring aims for 3, not 6.Target harus realistis untuk 12–18 bulan. Di sini pemantauan ditargetkan 3, bukan 6.

Trusting the averagePercaya pada rata-rataAn average of 2.5 hides a 1 in monitoring. Always read the gaps item by item.Rata-rata 2,5 menyembunyikan skor 1 di pemantauan. Selalu baca selisih per item.

Your turnGiliran Anda

Explore the case in the self-assessmentJelajahi kasus ini di asesmen mandiri

Load these scores into the self-assessment (DCAM, Full depth) to see the radar, gap list and exports, then change scores to see what moves.Muat skor ini ke asesmen mandiri (DCAM, kedalaman Lengkap) untuk melihat radar, daftar selisih, dan ekspor, lalu ubah skornya untuk melihat apa yang berubah.