Take your Business intelligence OUT of the hands of the I.T. department !
Once the knowledge base is published, it can be used to examine and cleanse other data. Once the user is done cleansing the data, it can be exported to Excel, to a csv file, or to a database. You can see in the screenshot below that the exported results show the source data and the output (cleansed data). In this way, the business data owner can document what has been changed and share those results with other business users.
Notice that I said this was being done by the business user or data owner. This is a key aspect of DQS: the business data owner, not the IT admin, DBA, or developer is doing the work since they know the business.
Why do you want to use DQS? You want to use it, because analyzing data from disparate sources is the heart of BI, and analyzing bad data leads to bad business decisions. So before we analyze data we want to have accurate and consistent data. One way to get that is to create a data warehouse. (Data warehouses offer other advantages such as a single source of the data, but that’s not the issue here.) It would be nice if the business users could examine their data, see the bad data, and correct it. Now they can. And you can do this without having a data warehouse, before you analyze your data.
Most of us have encountered bad data: a field that should be filled in that is blank, a filled in field with a misspelled value (Wadhington instead of Washington), a variety of values instead of the standard approved value (Washington, Washington State, WASH, and WA). DQS allows the business user with the DQS client on their desktop to examine their data for patterns.