Page 15 -

xvi Enterprise Data Governance

goal. They have enabled me understand just how potentially
wide ranging and valuable MDM is.”

Graham Chapman
Senior Enterprise Domain Architect: Information Enterprise
Architecture at Inland Revenue, New Zealand

“Time (or money) to market a solution seems to shorten
as we age. Should we waste in modeling? Think of the data
silos “galaxy” accumulated in less than 20 or 30 years of data
processing within your own organization, and ask why? It
has been disorganized to such extent because nobody wanted
to pay the bill for modeling upfront...so, everybody had to
pay anyway, but afterwards (data transformation, data
migration, data redesign etc.).

Data (and even more master data) is your asset. It is like
your money in the bank. You may not have plenty initially
but you most probably want it there for as long as possible. If
you leave your safe on weak foundations, you will keep
rebuilding and soon discover that everyone around preferred
to use the bank as a service instead. Can you still afford to
remain alone in your data mastering? Standards bodies like
OASIS and others progressively deliver prebuilt vertical
models like UBL, CIQ, ACORD, HL7 etc. However, those are
intended for data flows and do not fit for data
implementation. Packaged solutions (like SAP, Oracle
Application, etc.) also provide out-of-the-box configurable
data implementation schemas.

However those implementations tend to embed most of
your master data (from the package prospective only), thus
preventing us from keeping an homogeneous level on data
quality, control and governance in the overall IT eco-
systems. The same pitfalls apply if your try Corporate
Services in SOA before data mastering. This book is a great
opportunity for re-using from past experiences and