Bad Data is Really the Monster
- by Dain C. Hansen
Normal
0
false
false
false
EN-US
X-NONE
X-NONE
MicrosoftInternetExplorer4
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Calibri","sans-serif";
mso-bidi-font-family:"Times New Roman";}
Bad
Data is really the monster – is an article written by Bikram Sinha who I borrowed
the title and the inspiration for this blog. Sinha writes:
“Bad or missing data makes application systems fail when
they process order-level data. One of the key items in the supply-chain
industry is the product (aka SKU). Therefore, it becomes the most important
data element to tie up multiple merchandising processes including purchase order
allocation, stock movement, shipping notifications, and inventory details… Bad
data can cause huge operational failures and cost millions of dollars in terms
of time, resources, and money to clean up and validate data across multiple
participating systems.
Yes bad data really is the
monster, so what do we do about it? Close our eyes and hope it stays in the closet?
We’ve tacked this problem
for some years now at Oracle, and with our latest introduction of Oracle Enterprise Data Quality
along with our integrated Oracle
Master Data Management products provides a complete, best-in-class answer
to the bad data monster.
What’s unique about it?
Oracle Enterprise Data
Quality also combines powerful data profiling, cleansing, matching, and
monitoring capabilities while offering unparalleled ease of use. What makes it
unique is that it has dedicated capabilities to address the distinct challenges
of both customer and product data quality – [different
monsters have different needs of course!].
And the ability to profile
data is just as important to identify and measure poor quality data and
identify new rules and requirements. Included are semantic and pattern-based
recognition to accurately parse and standardize data that is poorly structured.
Finally all of the data quality components are integrated with Oracle Master
Data Management, including Oracle Customer Hub and Oracle Product Hub, as well
as Oracle Data Integrator Enterprise Edition and Oracle CRM.
Want to learn more? On Tuesday Nov 15th,
I invite you to listen to our webcast on Reduce
ERP consolidation risks with Oracle Master Data Management I’ll be joined
by our partner iGate Patni and be talking about one specific way to deal with
the bad data monster specifically around ERP consolidation. Look forward to
seeing you there!
