Federation of multi-level master data management systems

• US 8,635,249 B2
• Filed: 05/27/2011
• Issued: 01/21/2014
• Est. Priority Date: 05/27/2011
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Anand, Rangachari, Hobson, Stacy F., Lee, Juhnyoung, Liu, Xuan, Wang, Yuan, Yang, Jeaha
• Primary Examiner(s): NGUYEN, KIM T
• Application Number:
  US13/117,370
• Publication Number:
  US 20120303672A1
• Time in Patent Office: 970 Days
• Field of Search: 707/220, 707/224
• US Class Current: 707/790
• CPC Class Codes: G06F 16/20 of structured data, e.g. relational data
• CPC Class Codes: G06F 16/256 in federated or virtual databases

Abstract

Federating multiple-level master data management systems may include a first set of master data management nodes having one or more common characteristics. A first group master data management node may be assigned to centrally manage the first set of master data management nodes, the first group master data management node maintaining master data management functionalities at a group level and providing a single logical view of master data to the first set of master data management nodes. Each master data management node in the first set has data access link with the first group master data management node based on implementation style of said each master data management node.

Claims

1. A system for federating multiple-level master data management systems, comprising:

one or more processors;

a first set of master data management nodes, executable on the one or more processors, having one or more common characteristics; and

a first group master data management node assigned to centrally manage the first set of master data management nodes, the first group master data management node maintaining master data management functionalities at a group level and providing a single logical view of master data to the first set of master data management nodes,

each master data management node in the first set having data access link with the first group master data management node based on implementation style of said each master data management node,

said each master data management node comprising a plurality of applications that link to said each master data management node for management of data objects used by the plurality of applications,

wherein the first group master data management node supports a plurality of implementation styles associated with the data objects for providing a consolidated view of data used in said first set of master data management nodes and the plurality of applications,

the implementation styles comprising at least registry architecture style, consolidation architecture style, transaction architecture style, and coexistence architecture style,

wherein in the registry architecture style, said each master data management node maintains it own data within said each master data management node, and the first group master data management node maintains references to the data wherein the consolidated view of data is provided as a virtual consolidated view,

wherein in the consolidation architecture style, each of said plurality of applications stores its own data, periodically replicating to said each master data management node, and the data replicated to said each master data management node is not published to said plurality of applications,

wherein in the coexistence architecture style, said each master data management node maintains it own data within said each master data management node, periodically replicating to said first group master data management node, and the data replicated to said first group master data management node is published to said plurality of applications,

wherein in the transaction architecture style, the data used in said first set of master data management nodes are maintained in said first group master data management node, wherein said first set of master data management nodes subscribe to updates published from the first group master data management node.

2. The system of claim 1, further including:

a root master data management node assigned to centrally manage the first group master data management node, the first group master data management node directly linked with the root master data management node, root master data management node maintaining master data management functionalities at a root level and providing a single logical hierarchy view of all master management nodes based on organization information.

3. The system of claim 2, further including:

a second set of master data management nodes having one or more common characteristics; and

a second group master data management node assigned to centrally manage the second set of master data management nodes, the second group master data management node maintaining master data management functionalities at a group level and providing a single logical view of master data to the second set of master data management nodes,

each master data management node in the second set having data access link with the second group master data management node based on implementation style of said each master data management node.

4. The system of claim 3, wherein the second group master data management node links directly to the root master data management node, and the root master data management node centrally manages the second group master data management node.

5. The system of claim 4, wherein each of the master data management nodes in the first set is enabled to communicate with each of the master data management nodes in the second set by communicating via the first group master data management node, the second group master data management node and the root master data management node.

6. The system of claim 5, wherein the root master data management node holds as the master data, aggregated data which the first group master data management node and the second group master data management node share.

7. The system of claim 6, wherein the first group master data management node and the second group master data management node each has associated rules of visibility, and the root master data management node provides view of the master data according to the associated rules of visibility to the first group master data management node and the second group master data management node.

8. The system of claim 1, wherein the first group master data management node holds as the master data, aggregated data which the first set of master data management nodes share.

9. The system of claim 8, wherein each master data management node in the first set has associated rules of visibility, and the first group master data management node provides view of the master data according to the associated rules of visibility to said each master data management node.

10. The system of claim 1, wherein if a master data management node in the first set is implemented in registry style, a bi-direction reference link is established as the data access link between the master data management node and the first group master data management node.

11. The system of claim 1, wherein if a master data management node in the first set is implemented in transaction style, an operational link is established as the data access link between the master data management node and the first group master data management node.

12. A method of federating multiple-level master data management systems, comprising:

grouping a first set of master data management nodes according to one or more common characteristics and collecting information associated with the first set of master data management nodes;

creating a first group master data management node to centrally manage the first set of master data management nodes and master data shared among the first set of master data management nodes;

establishing rules of visibility for each master data management node in the first set based on the collected information; and

establishing data access link type between the first group master data management node and said each master data management node in the first set based on implementation style of said each master data management node,

said each master data management node comprising a plurality of applications that link to said each master data management node for management of data objects used by the plurality of applications,

wherein the first group master data management node supports a plurality of implementation styles associated with the data objects for providing a consolidated view of data used in said first set of master data management nodes and the plurality of applications,

the implementation styles comprising at least registry architecture style, consolidation architecture style, transaction architecture style, and coexistence architecture style,

wherein in the registry architecture style, said each master data management node maintains it own data within said each master data management node, and the first group master data management node maintains references to the data wherein the consolidated view of data is provided as a virtual consolidated view,

wherein in the consolidation architecture style, each of said plurality of applications stores its own data, periodically replicating to said each master data management node, and the data replicated to said each master data management node is not published to said plurality of applications,

wherein in the coexistence architecture style, said each master data management node maintains it own data within said each master data management node, periodically replicating to said first group master data management node, and the data replicated to said first group master data management node is published to said plurality of applications,

wherein in the transaction architecture style, the data used in said first set of master data management nodes are maintained in said first group master data management node, wherein said first set of master data management nodes subscribe to updates published from the first group master data management node.

13. The method of claim 12, further including:

creating a root master data management node to manage the first group master data management node; and

establishing a physical link between the root master data management node and the first group master data management node.

14. The method of claim 13, further including:

grouping a second set of master data management nodes according to one or more common characteristics and collecting information associated with the second set of master data management nodes;

creating a second group master data management node to centrally manage the second set of master data management nodes and master data shared among the second set of master data management nodes;

establishing rules of visibility for each master data management node in the second set based on the collected information; and

establishing data access link type between the second group master data management node and said each master data management node in the second set based on implementation style of said each master data management node in the second set.

15. The method of claim 14, further including:

establishing a physical link between the root master data management node and the second group master data management node.

16. The method of claim 15, further including:

aggregating in the root master data management node, data which the first group master data management node and the second group master data management node share.

17. A non-transitory computer readable storage medium storing a program of instructions executable by a machine to perform a method of federating multiple-level master data management systems, comprising:

grouping a first set of master data management nodes according to one or more common characteristics and collecting information associated with the first set of master data management nodes;

creating a first group master data management node to centrally manage the first set of master data management nodes and master data shared among the first set of master data management nodes;

establishing rules of visibility for each master data management node in the first set based on the collected information; and

establishing data access link type between the first group master data management node and said each master data management node in the first set based on implementation style of said each master data management node,

said each master data management node comprising a plurality of applications that link to said each master data management node for management of data objects used by the plurality of applications,

wherein the first group master data management node supports a plurality of implementation styles associated with the data objects for providing a consolidated view of data used in said first set of master data management nodes and the plurality of applications,

the implementation styles comprising at least registry architecture style, consolidation architecture style, transaction architecture style, and coexistence architecture style,

wherein in the registry architecture style, said each master data management node maintains it own data within said each master data management node, and the first group master data management node maintains references to the data wherein the consolidated view of data is provided as a virtual consolidated view,

wherein in the consolidation architecture style, each of said plurality of applications stores its own data, periodically replicating to said each master data management node, and the data replicated to said each master data management node is not published to said plurality of applications,

wherein in the coexistence architecture style, said each master data management node maintains it own data within said each master data management node, periodically replicating to said first group master data management node, and the data replicated to said first group master data management node is published to said plurality of applications,

wherein in the transaction architecture style, the data used in said first set of master data management nodes are maintained in said first group master data management node, wherein said first set of master data management nodes subscribe to updates published from the first group master data management node.

18. The computer readable storage medium of claim 17, further including:

creating a root master data management node to manage the first group master data management node; and

establishing a physical link between the root master data management node and the first group master data management node.

19. The computer readable storage medium of claim 18, further including:

grouping a second set of master data management nodes according to one or more common characteristics and collecting information associated with the second set of master data management nodes;

creating a second group master data management node to centrally manage the second set of master data management nodes and master data shared among the second set of master data management nodes;

establishing rules of visibility for each master data management node in the second set based on the collected information; and

establishing data access link type between the second group master data management node and said each master data management node in the second set based on implementation style of said each master data management node in the second set.

20. The computer readable storage medium of claim 19, further including:

establishing a physical link between the root master data management node and the second group master data management node.

21. The computer readable storage medium of claim 20, further including:

aggregating in the root master data management node, data which the first group master data management node and the second group master data management node share.