Information Steward 4.2 Update
There was an ASUG information steward session discussing the new features in Information Steward 4.2
Below is some of the new features that caught my eye, some really nice features that will come out with Information Steward 4.2.
Figure 1 – Source: SAP
As seen below with Information Steward SAP is trying to clearly split Data Steward and Data Services roles. One of the new features is Data Quality Advisor, this guides the data stewards to rapidly develop a solution to measure and improve the quality of data. This will make it much more simple to identify rules. correction rules and implementation.
Data Quality Advisor has three high level steps in the cycle
Figure 2 – Source: SAP
Below we can see the Assess phase, but more importantly we can see two columns called Advisor and Content Type. The content Type has automatically determine what type of data it has. These names/titles in content type column matches what we usually see in Data Services data quality transforms.
Figure 3 – Source: SAP
The next step you the Data Quality Advisor recommends possible rules that you could accept or remove.
Figure 4 – Source: SAP
Part of the recommend step it will suggest data cleansing options, fuzzy matching, Parsing and Standardization.
Figure 5 – Source: SAP
The last step you can then fine tune all the recommended rules you accepted.
Figure 6 – Source: SAP
Another new feature of Information Steward is you will be able to calculate the cost of dirty data. You will be able to see this in graphs or a tabular format. Really making it possible to reduce cost by reducing BAD DATA!!
Figure 7 – Source: SAP
The below shows how we will be able to setup cost per failure for each validation to give us the cost of bad data.
Figure 8 – Source: SAP
Sybase PowerDesigner integration is also one of the new features. Allowing us to see PowerDesigner as part of the metadata.
Figure 9 – Source: SAP
Matching UI has been revamped, improved to find best record more easily.
Figure 10 – Source: SAP
Same as many tools, SAP is looking to push down as much work to HANA. So with Information Steward some rules when running off of HANA will push down to the database. This will reduce the time for the whole cycle, not all rules can be push down to HANA, but this is the first step where some will be.
Figure 11 – Source: SAP
Hope you enjoyed the read.
Follow me on twitter for more information @louisdegouveia