IP Library Granted Patent US 9,218,387
Granted Patent B2
US 9,218,387 · App. 13/899,715 · Granted Dec 22, 2015

Cloud based master data management system and method therefor

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 9,218,387
App. No.
13/899,715
Granted
Dec 22, 2015
Kind
B2
Abstract

A source record from an enterprise is received at a registry at a master data management system at a host enterprise. The enterprise is located remotely from the host enterprise. The source record has a source identifier. A data record is generated based on the source record and the data record has a first registry identifier. The data record is stored at a data store. The registry maintains a link identifying a relationship between the registry identifier and the source identifier. A reference engine determines a value of an attribute of a field of the source record identifies a second source record, and determines whether the registry includes a second registry identifier associated with a second data record generated based on the second source record. The reference engine sets an indicator identifying the data record if the registry does not include the second registry identifier, and clears the indicator if the registry does include the second registry identifier.

Claims (72)

1. A system implemented at a host enterprise for handling information, the system comprising:

a computer memory;

a computer processor coupled to the computer memory;

a registry configured by the computer processor to:

receive a first source record from a first source enterprise located remotely from the host enterprise, the first source record having a first source identifier;

generate a first data record based on the first source record, the first data record having a first registry identifier;

store the first data record at a data store provided by the host enterprise; and

maintain a first link identifying a relationship between the first registry identifier and the first source identifier; and

a reference engine configured by the computer processor to:

determine that a value of a first attribute of a field of the first source record identifies a second source record;

determine whether the registry includes a second registry identifier associated with a second data record, the second data record generated based on the second source record;

set an indicator in the registry, the indicator identifying the first data record in response to determining that the registry does not include the second registry identifier, the indicator identifying an unresolved reference; and

clear the indicator, if the indicator is set, in response to determining that the registry does include the second registry identifier.

2. The system of claim 1 , wherein the registry is further configured to maintain a link between the first attribute value and the second data record in response to the determining that the registry includes the second registry identifier.

3. The system of claim 1 , further comprising:

a first data channel coupled to the registry, the first data channel to provide change information indicating a change to the first data record; and

a first interface process module to identify the change information at the first data channel and to initiate update of the first source record based on the first change information using an Internet protocol.

4. The system of claim 3 , wherein the first interface process module is further to:

determine that the value of the first attribute of the field of the first source record at the first source enterprise has been updated; and

provide the updated value to the first data channel, the first data channel to provide the updated value to the registry.

5. The system of claim 1 , further comprising:

a channel delivery module;

a second data channel coupled to the registry, the second data channel to selectively provide change information indicating a change to the first data record based on information provided by the channel delivery module; and

a second interface process module to identify the change information at the second data channel and to initiate update of the second source record based on the second change information using an Internet protocol.

6. The system of claim 5 , wherein the selectively providing the change information comprises:

providing the change information in response to determining that the second source record is not configured to operate in a strict mode;

not providing the change information in response to determining that the second source record is configured to operate in the strict mode and in response to determining the indicator is set; and

providing the change information in response to determining that the second source record is configured to operate in the strict mode and in response to determining the indicator is not set.

7. The system of claim 1 , wherein the first data record is associated with a first client enterprise and the data registry is further configured to provide storage at the data store of the second data record associated with a second client enterprise different from the first client enterprise.

8. The system of claim 1 , wherein the first data record is further associated with a client enterprise located remotely from the host enterprise, the client enterprise including a client interface process module to provide access by the client enterprise to the first data record and the first source record using an Internet protocol.

9. The system of claim 1 , further comprising a matching unit at the host enterprise, the matching unit to:

receive the second source record; and

determine if the second source record is to be associated with the first data record.

10. The system of claim 1 , further comprising a suggest unit at the host enterprise to provide guidance for configuring the first data record to be stored by the system based on information included at a suggestion database, the information determined based on configuration of data records provided by a plurality of users of the system.

11. A method for handling information comprising:

receiving, at a registry, at a host enterprise a first source record from a first source enterprise located remotely from the host enterprise, the first source record having a first source identifier;

generating a first data record based on the first source record, the first data record having a first registry identifier;

storing the first data record at a data store provided by the host enterprise;

maintaining a first link identifying a relationship between the first registry identifier and the first source identifier;

determining at a reference engine that a value of a first attribute of a field of the first source record identifies a second source record;

determining whether the registry includes a second registry identifier associated with a second data record, the second data record generated based on the second source record;

setting an indicator in the registry, the indicator identifying the first data record in response to determining that the registry does not include the second registry identifier, the indicator identifying, an unresolved reference; and

clearing the indicator, if the indicator is set, in response to determining that the registry does include the second registry identifier.

12. The method of claim 11 , further comprising maintaining at the registry a link between the first attribute value and the second data record in response to the determining that the registry includes the second registry identifier.

13. The method of claim 11 , further comprising:

providing change information at a first data channel, the change information indicating a change to the first data record; and

receiving the change information at a first interface process module, the first interface process module to initiate update of the first source record based on the change information using an Internet protocol.

14. The method of claim 13 , further comprising:

determining at the first interface process module that the value of the first attribute of the field of the first source record at the first source enterprise has been updated; and

providing the updated value to the first data channel, the first data channel to provide the updated value to the registry.

15. The method of claim 11 , further comprising:

selectively providing change information at a second data channel coupled to the registry based on information received from a channel delivery module, the change information indicating a change to the first data record; and

receiving the change information at a second interface process module, the second interface process module to initiate update of the second source record at a second source enterprise based on the first change information using an Internet protocol, the second source enterprise located remotely from the host enterprise and the first source enterprise.

16. The method of claim 15 , wherein the selectively providing the change information comprises:

providing the change information in response to determining the second source record is not configured to operate in a strict mode;

not providing the change information in response to determining that the second source record is configured to operate in the strict mode and in response to determining the indicator is set; and

providing the change information in response to determining that the second source record is configured to operate in the strict mode and in response to determining the indicator is not set.

17. The method of claim 11 , wherein the first data record is associated with a first client enterprise and the data registry is further configured to provide storage at the data store of the second data record associated with a second client enterprise different from the first client enterprise.

18. The method of claim 11 , wherein the first data record is further associated with a client enterprise located remotely from the host enterprise, the client enterprise including a client interface process module to provide access by the client enterprise to the first data record and the first source record using an Internet protocol.

19. An information handling system comprising:

a computer memory;

a microprocessor coupled to the computer memory; and

computer-readable instructions stored in the computer memory and executable by the microprocessor to:

receive at a registry at a host enterprise a first source record from a first source enterprise located remotely from the host enterprise, the first source record having a first source identifier;

generate a first data record based on the first source record, the first data record having a first registry identifier;

store the first data record at a data store provided by the host enterprise;

maintain a first link identifying a relationship between the first registry identifier and the first source identifier;

determine at a reference engine a value of a first attribute of a field of the first source record identifies a second source record;

determine whether the registry includes a second registry identifier associated with a second data record, the second data record generated based on the second source record;

set an indicator in the registry identifying the first data record in response to determining that the registry does not include the second registry identifier, the indicator identifying an unresolved reference; and

clear the indicator, if the indicator is set, in response to determining that the registry does include the second registry identifier.

20. The information handling system of claim 19 , wherein the registry is further configured to maintain a link between the first attribute value and the second data record in response to the determining that the registry includes the second registry identifier.

Assignments (13)
SECURITY INTEREST Recorded Nov 12, 2024
From: SIXTH STREET SPECIALTY LENDING, INC.
To: BLUE OWL CAPITAL CORPORATION
Reel/Frame 069342/0406 →
SECURITY INTEREST Recorded Oct 1, 2021
From: BOOMI, LLC
To: SIXTH STREET SPECIALTY LENDING, INC., AS COLLATERAL AGENT
Reel/Frame 057679/0908 →
RELEASE OF SECURITY INTEREST Recorded Sep 14, 2016
From: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: DELL MARKETING L.P.; ASAP SOFTWARE EXPRESS, INC.; APPASSURE SOFTWARE, INC.; COMPELLENT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL INC.; DELL PRODUCTS L.P.; DELL USA L.P.; DELL SOFTWARE INC.; FORCE10 NETWORKS, INC.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
Reel/Frame 040065/0618 →
RELEASE OF SECURITY INTEREST Recorded Sep 14, 2016
From: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
To: DELL MARKETING L.P.; ASAP SOFTWARE EXPRESS, INC.; APPASSURE SOFTWARE, INC.; COMPELLENT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL INC.; DELL PRODUCTS L.P.; DELL USA L.P.; DELL SOFTWARE INC.; FORCE10 NETWORKS, INC.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
Reel/Frame 040040/0001 →
RELEASE OF SECURITY INTEREST Recorded Sep 13, 2016
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: DELL MARKETING L.P.; ASAP SOFTWARE EXPRESS, INC.; APPASSURE SOFTWARE, INC.; COMPELLANT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL INC.; DELL PRODUCTS L.P.; DELL USA L.P.; DELL SOFTWARE INC.; FORCE10 NETWORKS, INC.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
Reel/Frame 040065/0216 →
RELEASE OF SECURITY INTEREST Recorded Aug 5, 2015
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: BOOMI, INC.
Reel/Frame 036262/0650 →
RELEASE OF SECURITY INTEREST Recorded Aug 5, 2015
From: BANK OF AMERICA, N.A.
To: BOOMI, INC.
Reel/Frame 036262/0642 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 5, 2015
From: DELL PRODUCTS L.P.
To: BOOMI, INC.
Reel/Frame 036262/0585 →
RELEASE OF SECURITY INTEREST Recorded Aug 5, 2015
From: BANK OF AMERICA, N.A.
To: BOOMI, INC.
Reel/Frame 036262/0627 →
PATENT SECURITY AGREEMENT (TERM LOAN) Recorded Jan 2, 2014
From: DELL INC.; APPASSURE SOFTWARE, INC.; ASAP SOFTWARE EXPRESS, INC.; BOOMI, INC.; COMPELLENT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL USA L.P.; FORCE10 NETWORKS, INC.; GALE TECHNOLOGIES, INC.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 031899/0261 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Jan 2, 2014
From: APPASSURE SOFTWARE, INC.; ASAP SOFTWARE EXPRESS, INC.; BOOMI, INC.; COMPELLENT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL INC.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL USA L.P.; FORCE10 NETWORKS, INC.; GALE TECHNOLOGIES, INC.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
To: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS FIRST LIEN COLLATERAL AGENT
Reel/Frame 031897/0348 →
PATENT SECURITY AGREEMENT (ABL) Recorded Jan 2, 2014
From: DELL INC.; APPASSURE SOFTWARE, INC.; ASAP SOFTWARE EXPRESS, INC.; BOOMI, INC.; COMPELLENT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL USA L.P.; FORCE10 NETWORKS, INC.; GALE TECHNOLOGIES, INC.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 031898/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 14, 2013
From: FENNELL, ERIC G.; AHLBORN, JAMES T.
To: DELL PRODUCTS, LP
Reel/Frame 030613/0571 →