IP Library Granted Patent US 7,725,429
Granted Patent B2
US 7,725,429 · App. 10/847,037 · Granted May 25, 2010

Master data management system for centrally managing core reference data associated with an enterprise

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,725,429
App. No.
10/847,037
Granted
May 25, 2010
Kind
B2
Abstract

In one embodiment, a system is provided for centrally managing core enterprise reference data associated with an enterprise. A centralized master repository contains the core enterprise reference data. An internal services framework coupled to the centralized master repository provides internal services for managing the core enterprise reference data within the centralized master repository, one or more of the internal services having direct access to the core enterprise reference data stored in the centralized master repository for management purposes. An infrastructure services layer coupled to the centralized master repository includes: (1) a back side data access layer that (a) provides bulk data transfers of core enterprise reference data between the centralized master repository and one or more external operational systems according to one or more enterprise-level business workflows, and (b) provides the external operational systems with indirect access, for operational purposes, to associated external operation services within the system that indirectly access the core enterprise reference data stored in the centralized master repository; and (2) a front side data access layer that (a) transfers control data from the external operational systems to the system to control operations of the system, and (b) provides the external operational systems with direct access to certain of the internal services that directly access the core enterprise reference data within the centralized core repository.

Claims (87)

1. A computer-implemented system, comprising:

a storage medium stored therein a centralized master repository comprising core enterprise reference data;

a storage medium stored therein an internal services framework coupled with the centralized master repository and providing internal services for managing the core enterprise reference data within the centralized master repository, one or more of the internal services having direct access to the core enterprise reference data stored in the centralized master repository for management purposes;

a storage medium stored therein an infrastructure services layer coupled with the centralized master repository, comprising:

a back side data access layer having an object-based control layer configured to:

provide bulk data transfers of core enterprise reference data between the centralized master repository and one or more external operational systems having one or more enterprise solution components, according to one or more enterprise-level business workflows;

provide the external operational systems with indirect access, for operational purposes, to associated external operation services within the system that indirectly access the core enterprise reference data stored in the centralized master repository; and

map between the centralized master repository and the one or more enterprise solution components of the one or more external operation systems, the mapping having fixed transformations; and

a front side data access layer configured to:

transfer control data from the external operational systems to the system to control operations of the system; and

provide the external operational systems with direct access to certain of the internal services that directly access the core enterprise reference data within the centralized core repository; and

a database coupled with the centralized master repository storing the core enterprise reference data.

2. The system of claim 1 , wherein the external operational system is modified without modifying the core enterprise reference data within the centralized master repository.

3. The system of claim 1 , wherein the external operational system is integrated when the external operational system is introduced, modified, or replaced.

4. The system of claim 1 , wherein another enterprise is integrated into the enterprise.

5. The system of claim 1 , wherein the centralized master repository incorporates a multi-dimensional database construct in which all the core enterprise reference data stored within the centralized master repository is represented as an attribute associated with a point in n-dimensional entity space.

6. The system of claim 1 , wherein the centralized master repository comprises multiple master repositories residing at multiple physical locations, the centralized master repository appearing to internal services and external operational systems as a single master repository at a single physical location.

7. The system of claim 1 , comprising a database containing at least some of the core enterprise reference data in the centralized master repository, any core enterprise reference data that is not physically contained in the database appearing to internal services and external operational systems as if it was physically contained in the database.

8. The system of claim 1 , wherein the infrastructure services layer is configured to facilitate application integration with the external operational systems.

9. The system of claim 1 , wherein the infrastructure services layer further provides enterprise messaging between one or more of the internal services and the external operational systems according to operation of one or more enterprise-level business workflows.

10. The system of claim 1 , wherein the back side data access layer is configured to provide the external operational systems with indirect access to associated external operation services within the system that indirectly access the core enterprise reference data within the centralized core repository through one or more staging areas associated with the centralized core repository.

11. The system of claim 1 , wherein the front side data access layer is embodied using an object-based services layer residing on an application server within an application server layer.

12. The system of claim 1 , wherein the front side data access layer is configured to transfer core enterprise reference data between the centralized master repository and an external operational system where the external operational system requires core enterprise reference data in a particular format that the back side data access layer does not support.

13. The system of claim 1 , wherein the external operational systems comprise one or more of:

external enterprise solution components associated with the enterprise; and

external enterprises.

14. A method of centrally managing core enterprise reference data associated with an enterprise, comprising:

providing a centralized master repository containing the core enterprise reference data;

providing an internal services framework that is coupled with the centralized master repository and provides internal services for managing the core enterprise reference data within the centralized master repository, one or more of the internal services having direct access to the core enterprise reference data stored in the centralized master repository for management purposes;

providing an infrastructure services layer that is coupled with the centralized master repository and comprises:

a back side data access layer having an object-based control layer configured to:

provide bulk data transfers of core enterprise reference data between the centralized master repository and one or more external operational systems having one or more enterprise solution components, according to one or more enterprise-level business workflows;

provide the external operational systems with indirect access, for operational purposes, to associated external operation services within the system that indirectly access the core enterprise reference data stored in the centralized master repository;

map between the centralized master repository and the one or more enterprise solution components of the one or more external operation systems, the mapping having fixed transformations; and

a front side data access layer configured to:

transfer control data from the external operational systems to the system to control operations of the system; and

provide the external operational systems with direct access to certain of the internal services that directly access the core enterprise reference data within the centralized core repository; and

a database associated with the centralized master repository storing the core enterprise reference data.

15. The method of claim 14 , wherein the external operational system is modified without modifying the core enterprise reference data within the centralized master repository.

16. The method of claim 14 , wherein the external operational system is integrated when the external operational system is introduced, modified, or replaced.

17. The method of claim 14 , wherein another enterprise is integrated into the enterprise.

18. The method of claim 14 , wherein the centralized master repository incorporates a multi-dimensional database construct in which all the core enterprise reference data stored within the centralized master repository is represented as an attribute associated with a point in n-dimensional entity space.

19. The method of claim 14 , wherein the centralized master repository comprises multiple master repositories residing at multiple physical locations, the centralized master repository appearing to internal services and external operational systems as a single master repository at a single physical location.

20. The method of claim 14 , comprising providing a database containing at least some of the core enterprise reference data in the centralized master repository, any core enterprise reference data that is not physically contained in the database appearing to internal services and external operational systems as if it was physically contained in the database.

21. The method of claim 14 , wherein the infrastructure services layer is configured to facilitate application integration with the external operational systems.

22. The method of claim 14 , wherein the infrastructure services layer further provides enterprise messaging between one or more of the internal services and the external operational systems according to operation of one or more enterprise-level business workflows.

23. The method of claim 14 , wherein the back side data access layer is configured to provide the external operational systems with indirect access to associated external operation services that indirectly access the core enterprise reference data within the centralized core repository through one or more staging areas associated with the centralized core repository.

24. The method of claim 14 , wherein the front side data access layer is embodied using an object-based services layer residing on an application server within an application server layer.

25. The method of claim 14 , wherein the front side data access layer is configured to transfer core enterprise reference data between the centralized master repository and an external operational system where the external operational system requires core enterprise reference data in a particular format that the back side data access layer does not support.

26. The method of claim 14 , wherein the external operational systems comprise one or more of:

external enterprise solution components associated with the enterprise; and

external enterprises.

27. Software that centrally manages core enterprise reference data associated with an enterprise, the software embodied in one or more computer-readable media and when executed using one or more computer systems configured to:

interact with a centralized master repository containing the core enterprise reference data;

provide an internal services framework that is coupled with the centralized master repository and provides internal services for managing the core enterprise reference data within the centralized master repository, one or more of the, internal services having direct access to the core enterprise reference data stored in the centralized master repository for management purposes;

provide an infrastructure services layer that is coupled with the centralized master repository and comprises:

a back side data access layer having an object-based control layer configured to:

provide bulk data transfers of core enterprise reference data between the centralized master repository and one or more external operational systems having one or more enterprise solution components, according to one or more enterprise-level business workflows;

provide the external operational systems with indirect access, for operational purposes, to associated external operation services within the system that indirectly access the core enterprise reference data stored in the centralized master repository;

map between the centralized master repository and the one or more enterprise solution components of the one or more external operation systems, the mapping having fixed transformations; and

a front side data access layer configured to:

transfer control data from the external operational systems to the system to control operations of the system; and

provide the external operational systems with direct access to certain of the internal services that directly access the core enterprise reference data within the centralized core repository; and

a database associated with the centralized master repository storing the core enterprise reference data.

28. The software of claim 27 , wherein the external operational system is modified without modifying the core enterprise reference data within the centralized master repository.

29. The software of claim 27 , wherein the external operational system is integrated when the external operational system is introduced, modified, or replaced.

30. The software of claim 27 , wherein another enterprise is integrated into the enterprise.

31. The software of claim 27 , wherein the centralized master repository incorporates a multi-dimensional database construct in which all the core enterprise reference data stored within the centralized master repository is represented as an attribute associated with a point in n-dimensional entity space.

32. The software of claim 27 , wherein the centralized master repository comprises multiple master repositories residing at multiple physical locations, the centralized master repository appearing to internal services and external operational systems as a single master repository at a single physical location.

33. The software of claim 27 , configured to interact with a database containing at least some of the core enterprise reference data in the centralized master repository, any core enterprise reference data that is not physically contained in the database appearing to internal services and external operational systems as if it was physically contained in the database.

34. The software of claim 27 , wherein the infrastructure services layer is configured to facilitate application integration with the external operational systems.

35. The software of claim 27 , wherein the infrastructure services layer further provides enterprise messaging between one or more of the internal services and the external operational systems according to operation of one or more enterprise-level business workflows.

36. The software of claim 27 , wherein the back side data access layer is configured to provide the external operational systems with indirect access to associated external operation services that indirectly access the core enterprise reference data within the centralized core repository through one or more staging areas associated with the centralized core repository.

37. The software of claim 27 , wherein the front side data access layer is embodied using an object-based services layer residing on an application server within an application server layer.

38. The software of claim 27 , wherein the front side data access layer is configured to transfer core enterprise reference data between the centralized master repository and an external operational system where the external operational system requires core enterprise reference data in a particular format that the back side data access layer does not support.

39. The software of claim 27 , wherein the external operational systems comprise one or more of:

external enterprise solution components associated with the enterprise; and

external enterprises.

40. A system for centrally managing core enterprise reference data associated with an enterprise, comprising:

means for providing a centralized master repository comprising core enterprise reference data;

means for providing an internal services framework coupled with the centralized master repository and providing internal services for managing the core enterprise reference data within the centralized master repository, one or more of the internal services having direct access to the core enterprise reference data stored in the centralized master repository for management purposes; and

means for providing bulk data transfers of core enterprise reference data between the centralized master repository and one or more external operational systems having one or more enterprise solution components, according to one or more enterprise-level business workflows; and

means for providing the external operational systems with indirect access, for operational purposes, to associated external operation services within the system that indirectly access the core enterprise reference data stored in the centralized master repository;

means for mapping between the centralized master repository and the one or more enterprise solution components of the one or more external operation systems, the mapping having fixed transformations;

means for transferring control data from the external operational systems to the system to control operations of the system;

means for providing the external operational systems with direct access to certain of the internal services that directly access the core enterprise reference data within the centralized core repository; and

means for providing a database associated with the centralized master repository storing the core enterprise reference data.

Assignments (17)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053383/0117) Recorded Nov 3, 2021
From: U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: BLUE YONDER GROUP, INC.
Reel/Frame 058794/0776 →
RELEASE OF SECURITY INTEREST Recorded Sep 16, 2021
From: JPMORGAN CHASE BANK, N.A.
To: BLUE YONDER GROUP, INC.; BLUE YONDER, INC.; JDA SOFTWARE SERVICES, INC.; I2 TECHNOLOGIES INTERNATIONAL SERVICES, LLC; MANUGISTICS SERVICES, INC.; MANUGISTICS HOLDINGS DELAWARE II, INC.; REDPRAIRIE COLLABORATIVE FLOWCASTING GROUP, LLC; JDA SOFTWARE RUSSIA HOLDINGS, INC.; REDPRAIRIE SERVICES CORPORATION; BY BOND FINANCE, INC.; BY NETHERLANDS HOLDING, INC.; BY BENELUX HOLDING, INC.
Reel/Frame 057724/0593 →
CORRECTIVE ASSIGNMENT TO CORRECT THE REEL 026468 FRAME NUMBER FROM 0199 TO 0119 PREVIOUSLY RECORDED ON REEL 055136 FRAME 0623. ASSIGNOR(S) HEREBY CONFIRMS THE CORRECTION ASSIGNMENT. Recorded Apr 19, 2021
From: I2 TECHNOLOGIES US, INC.
To: JDA TECHNOLOGIES US, INC.
Reel/Frame 056813/0110 →
CORRECTIVE ASSIGNMENT TO CORRECT THE NAME OF THE CONVEYING AND RECEIVING PARTIES TO INCLUDE A PERIOD AFTER THE TERM INC PREVIOUSLY RECORDED AT REEL: 026740 FRAME: 0676. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Feb 8, 2021
From: JDA TECHNOLOGIES US, INC.
To: JDA SOFTWARE GROUP, INC.
Reel/Frame 055257/0747 →
CORRECTIVE ASSIGNMENT TO CORRECT THE NAME OF THE CONVEYING AND RECEIVING PARTIES TO INCLUDE A PERIOD AFTER THE TERM INC PREVIOUSLY RECORDED ON REEL 026468 FRAME 0199. ASSIGNOR(S) HEREBY CONFIRMS THE CHANGE OF NAME FROM I2 TECHNOLOGIES US, INC. TO JDA TECHNOLOGIES US, INC.. Recorded Dec 12, 2020
From: I2 TECHNOLOGIES US, INC.
To: JDA TECHNOLOGIES US, INC.
Reel/Frame 055136/0623 →
SECURITY AGREEMENT Recorded Aug 3, 2020
From: BLUE YONDER GROUP, INC.
To: U.S. BANK NATIONAL ASSOCIATION
Reel/Frame 053383/0117 →
CHANGE OF NAME Recorded Apr 14, 2020
From: JDA SOFTWARE GROUP, INC.
To: BLUE YONDER GROUP, INC.
Reel/Frame 052392/0496 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL/FRAME NO. 29556/0809 Recorded Oct 12, 2016
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: JDA SOFTWARE GROUP, INC.
Reel/Frame 040337/0356 →
SECURITY AGREEMENT Recorded Oct 12, 2016
From: RP CROWN PARENT, LLC; RP CROWN HOLDING LLC; JDA SOFTWARE GROUP, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 040326/0449 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL/FRAME NO. 29556/0697 Recorded Oct 12, 2016
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: JDA SOFTWARE GROUP, INC.
Reel/Frame 040337/0053 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Jan 2, 2013
From: JDA SOFTWARE GROUP, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 029556/0697 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Jan 2, 2013
From: JDA SOFTWARE GROUP, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 029556/0809 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Dec 21, 2012
From: WELLS FARGO CAPITAL FINANCE, LLC
To: JDA TECHNOLOGIES US, INC.
Reel/Frame 029529/0812 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 12, 2011
From: JDA TECHNOLOGIES US, INC.
To: JDA SOFTWARE GROUP, INC.
Reel/Frame 026740/0676 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 21, 2011
From: I2 TECHNOLOGIES US, INC
To: JDA TECHNOLOGIES US, INC
Reel/Frame 026468/0119 →
PATENT SECURITY AGREEMENT Recorded Apr 4, 2011
From: JDA TECHNOLOGIES US, INC.
To: WELLS FARGO CAPITAL FINANCE, LLC, AS AGENT
Reel/Frame 026072/0353 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 21, 2004
From: RANGADASS, MR. VASUDEV
To: I2 TECHNOLOGIES US, INC.
Reel/Frame 014874/0346 →