Data lineage
Answering "where did this number come from" without a three-week investigation.
Data lineage is a foundation capability of metadata management. Almost everything else you want to do with data governance depends on having it, and most organizations running legacy systems do not.
We determine where data comes from, how it is transformed and where it is going, tracing the lifecycle of information between systems including every operation performed on it in transit.
What it is used for
- Meeting compliance targets, with an auditable answer rather than an assurance
- In-depth data analysis
- Authorization management
- Impact assessment, before a change rather than after it
- Risk assessment
- Ensuring data governance principles are actually observed
- Enabling reuse and standardization
Why legacy makes this hard
In a modern stack, lineage tooling can often read the pipeline definitions. On a mainframe there are no pipeline definitions. The transformation is distributed across programs, copybooks, job steps and datasets, and reconstructing it means understanding the code. That is what the model is for.
Trace lineage across your systems
A short conversation is usually enough for us to say honestly whether we can help, and roughly what it would take. No obligation either way.