Data problems can occur anywhere, but are often discovered at the end of a data lifecycle, for example when managers are reviewing a monthly report, or a business modeller applies some data quality checks before using the data in his or her business model.
Understanding the lineage of the data, i.e. where it was created and how it was derived, is key to understanding why the problem occurred, and how to fix it.
With Architector, you can explore the data lifecycle, and narrow down potential causes of a data problem, if not pin-point it exactly. Architector can trace the lifecycle of an individual piece of data through the labyrinth of processes and systems, back to where it was created.
In the snippet of lineage above, two problems have been discovered with the data element Exposure Amount in the Stress Scenario 1 report. We can also see from here that there are other reports using Exposure Amount which could also be impacted.
The image below shows the data lineage back to ultimate source. (If you click on the image you should be able to read it more easily, although you may need to use your browser’s Zoom function to see it properly)
Here you can see that there is a known issue connected to Exposure Amount near where the data is created, in some end-user-computing spreadsheet. This could well be causing the problem. You can also see all the intervening processes and systems, giving clear pointers for where to look for the source of the problem.
Architector provides the tools needed to trace the problem back to its source, and to start fixing problems as early as possible.
Give your root cause analysis team the tools it needs – contact us today to find out more about Architector data management.