Features of Master Index Applications (Repository)

The components of the master index applications you create are highly configurable, allowing each master index application to be customized for your specific data processing needs. Primary features of a master index application include the following:

• Centralized Information – A master index application maintains a centralized database, enabling the integration of data records throughout the enterprise while allowing local systems to continue operating independently. The index stores copies of local system records and the single best record (SBR), which represents the most accurate and complete data for each object. This database is the central location of all object information and identifiers, and is accessible throughout the enterprise. Records from various systems are cross-referenced using the EUID assigned by a master index application to each object profile.

• Configurability – Before deploying a master index application, you can customize the components and processing capabilities of the system. The configurable components include:

  • The types of objects to index

  • The types of data stored

  • The standardization and match engines to use

  • Matching, standardization, and phonetic conversion rules

  • Survivorship and weighting rules for determining the SBR

  • The types of queries available

  • How queries are blocked, or grouped, for match processing

  • EDM appearance

  • Searches available to the EDM

  • Local ID validation rules

  Cross-referencing – A master index application serves as a global cross-reference, matching profiles across disparate source systems and simplifying the process of sharing data between systems. A master index application uses the local identifiers assigned by your existing systems as a reference, allowing you to maintain your current systems and practices.

• Data Cleansing – A master index application uses configurable matching algorithm logic to uniquely identify object profiles and to identify duplicate and potential duplicate profiles. A master index application provides the ability to easily merge or resolve duplicates, and can be configured to automatically match profiles that are found to be duplicates of one another.

• Data Updates – A master index application provides the ability to add, update, deactivate, merge, and delete data in the database tables through messages received from external systems or the EDM. Messages received from external systems and the EDM are checked for potential duplicates during processing.

• Updates to External Systems – The Sun Enterprise Service Bus provides a master index application with the ability to publish updated information to external systems, provided the external systems can accept incoming messages. This is handled through a JMS Topic to which a master index application publishes XML messages that contain the updates.

• Identification – A master index application employs configurable probabilistic matching technology. This technology uses a matching algorithm to formulate an effective statistical measure of how closely profiles match. Using a state-of-the-art algorithm in real-time mode and establishing a common method of locating profiles, a master index application consistently and precisely identifies objects within an enterprise.

• Integration – Relying on the Sun Enterprise Service Bus, a master index application provides the power and flexibility to identify, route, and transform data to and from any system or application throughout your business enterprise. It can accept incoming transactions and distribute updates to any external system, providing seamless integration with the systems in your enterprise.

• Matching Algorithm – A master index application is designed to use the Sun Match Engine or a custom matching algorithm to provide a matching probability weight between object profiles. You define matching thresholds, which control how potential duplicates and automatic merges are determined.

• Unique Identifier – A master index application assigns an enterprise-wide unique identifier (EUID) to each object added to the database. The index uses the EUID to cross-reference the local IDs assigned to each object by the various computer systems throughout the enterprise.