Page 97 -

58 Enterprise Data Governance

MDM system by the expression “locked MDM” which differs
from “enterprise MDM”. This latter is in agreement with the
unified approach of repositories across the whole of the
information system which is presented in this book.

At first glance, a software package which has a locked
MDM system at its disposal could be an attractive option. A
company could judge that it will save by not putting an
MDM system in place, as it seems to already be acquired
with the software package. Unfortunately, as soon as it is
necessary to leave the boundaries of the software package, it
is difficult to maintain a unified approach to repository
management. It is necessary to put in place other MDM
solutions, outside the software package, that lead to an
architecture by silos of repositories. It is rare that a software
package covers the totality of needs even though its
reference and master data must be shared across the whole
company, by all IT systems. On the other hand, a software
package must retrieve reference and master data stemming
from other IT systems, outside its own administrative scope.
In the end, accepting an MDM system locked in to the scope
of a software package, is the same as maintaining or
reinforcing the silo effect that nevertheless needs to be
corrected.

It is important to give preference to software packages
that favor IT neutrality in terms of the management of
reference and master data, i.e. that accept integration with
an MDM approach across the whole of a company, uniquely
capable of guaranteeing the following benefits :
1
– the quality of reference and master data is reinforced
since the MDM silo effect is counteracted. Only one solution
for the management of reference and master data is deployed
across the whole of the company; those that exist in software
packages are neutralized. This neutralization does not

1. See the criteria for choosing businessware in section 3.2.