Service

Every in-scope column mapped. Every competing formula flagged.

Accuracy fails when a target field can be produced more than one way — two jobs, a view and a procedure, a manual overlay. Before we move or upgrade anything in the replica, software drafts a source-to-target map and a lineage graph; a named person signs them. That is how we get more column coverage and more recon tests without skipping your sign-off.

You get a mapping workbook, a graph of sources and transformations, a list of fields with more than one producing path (and which path is authoritative), and tests tied to that map. We can run production go-live from the same map, or your team can.

What you receive

• Source-to-target mapping for in-scope columns (system, object, column, transform, grain)
• Column-level lineage — a graph, not only a table list
• Dual-origin fields called out for a decision before cutover
• Reconciliation tests (counts, checksums) generated from the map

BCBS 239

For banks and risk-data programmes, these artifacts are designed to support BCBS 239 evidence — especially accuracy and integrity, completeness, and a data architecture you can explain. We do not certify your firm as compliant. We produce the map and the lineage your control functions can use.

Mapping can ride with an upgrade, a workload move, or a data platform build — or stand on its own.

Request an assessment