Asset data model for recurring revenue asset management
First Claim
1. A computer program product comprising a non-transitory machine-readable medium storing instructions that, when executed by at least one programmable processor, cause the at least one programmable processor to perform operations comprising:
- mapping a unit of data received from an external data source at a recurring revenue management system implemented on one or more programmable processors, the mapping comprising integrating an inbound record type of the received unit of data to one of a set of predefined data object types supporting functions of the recurring revenue management system, the integrating comprising;
constructing, at a data source layer, a skeletal object from partial data loaded through a data ingestion pipeline comprising a service bus connecting a plurality of external data sources, the skeletal objects each comprising at least one annotation added at a load time of the skeletal object; and
combining, at the service bus, the skeletal object with existing skeletal objects by matching one of the at least one annotations of the skeletal object to similar existing annotations of existing skeletal objects, the combining of the skeletal objects resulting in the received unit of data being at least one of the set of predefined data object types;
extracting data relevant to a predefined data object type of the set of predefined data object types from the received unit of data;
populating a data object instance of the predefined data object type with the extracted data;
defining one or more relationships between the data object instance and at least one other data object instance of the predefined data object type and/or a second predefined data object type of the set of predefined data objects, the defining occurring based on a set of parameters associated with the predefined data object type and on content of the extracted data, the defining further comprising inferring at least one of the one or more relationships based on a transitivity analysis by the recurring revenue management system between the data object instance and the at least one other data object instance;
generating an opportunity for a sale or renewal of a recurring revenue asset based at least in part on the one or more relationships; and
providing user interface data to a client machine for presenting the opportunity to a user via a user interface shown on a display device of the client machine.
7 Assignments
0 Petitions
Accused Products
Abstract
Data relevant to a predefined data object of a set of predefined data objects can be extracted from a unit of date received at a recurring revenue management system. The extracted relevant data can be populated to an instance of the predefined data object. One or more relationships between the instance of the predefined data object and at least one other instance of the predefined data object or a second predefined data object. The defining occurs based on a set of parameters associated with the predefined data object and content of the extracted data. An opportunity can be generated for a sale or renewal of a recurring revenue asset based at least in part on the one or more relationships, and the generated opportunity can be presented to a user. Related methods, systems, and computer program products are also described.
85 Citations
20 Claims
-
1. A computer program product comprising a non-transitory machine-readable medium storing instructions that, when executed by at least one programmable processor, cause the at least one programmable processor to perform operations comprising:
-
mapping a unit of data received from an external data source at a recurring revenue management system implemented on one or more programmable processors, the mapping comprising integrating an inbound record type of the received unit of data to one of a set of predefined data object types supporting functions of the recurring revenue management system, the integrating comprising; constructing, at a data source layer, a skeletal object from partial data loaded through a data ingestion pipeline comprising a service bus connecting a plurality of external data sources, the skeletal objects each comprising at least one annotation added at a load time of the skeletal object; and combining, at the service bus, the skeletal object with existing skeletal objects by matching one of the at least one annotations of the skeletal object to similar existing annotations of existing skeletal objects, the combining of the skeletal objects resulting in the received unit of data being at least one of the set of predefined data object types; extracting data relevant to a predefined data object type of the set of predefined data object types from the received unit of data; populating a data object instance of the predefined data object type with the extracted data; defining one or more relationships between the data object instance and at least one other data object instance of the predefined data object type and/or a second predefined data object type of the set of predefined data objects, the defining occurring based on a set of parameters associated with the predefined data object type and on content of the extracted data, the defining further comprising inferring at least one of the one or more relationships based on a transitivity analysis by the recurring revenue management system between the data object instance and the at least one other data object instance; generating an opportunity for a sale or renewal of a recurring revenue asset based at least in part on the one or more relationships; and providing user interface data to a client machine for presenting the opportunity to a user via a user interface shown on a display device of the client machine. - View Dependent Claims (2, 3, 4, 5, 18)
-
-
6. A recurring revenue management system comprising:
-
at least one programmable processor; and a non-transient machine-readable medium storing instructions that, when executed by the at least one processor, cause the at least one programmable processor to perform operations comprising; mapping a unit of data received from an external data source at a recurring revenue management system implemented on one or more programmable processors, the mapping comprising integrating an inbound record type of the received unit of data to one of a set of predefined data object types supporting functions of the recurring revenue management system, the integrating comprising; constructing, at a data source layer, a skeletal object from partial data loaded through a data ingestion pipeline comprising a service bus connecting a plurality of external data sources, the skeletal objects each comprising at least one annotation added at a load time of the skeletal object; and combining, at the service bus, the skeletal object with existing skeletal objects by matching one of the at least one annotations of the skeletal object to similar existing annotations of existing skeletal objects, the combining of the skeletal objects resulting in the received unit of data being at least one of the set of predefined data object types; extracting data relevant to a predefined data object type of the set of predefined data object types from the received unit of data; populating a data object instance of the predefined data object type with the extracted data; defining one or more relationships between the data object instance and at least one other data object instance of the predefined data object type and/or a second predefined data object type of the set of predefined data objects, the defining occurring based on a set of parameters associated with the predefined data object type and on content of the extracted data, the defining further comprising inferring at least one of the one or more relationships based on a transitivity analysis by the recurring revenue management system between the data object instance and the at least one other data object instance; generating an opportunity for a sale or renewal of a recurring revenue asset based at least in part on the one or more relationships; and providing user interface data to a client machine for presenting the opportunity to a user via a user interface shown on a display device of the client machine. - View Dependent Claims (7, 8, 9, 10, 19)
-
-
11. A method comprising:
-
mapping a unit of data received from an external data source at a recurring revenue management system implemented on one or more programmable processors, the mapping comprising integrating an inbound record type of the received unit of data to one of a set of predefined data object types supporting functions of the recurring revenue management system, the integrating comprising; constructing, at a data source layer, a skeletal object from partial data loaded through a data ingestion pipeline comprising a service bus connecting a plurality of external data sources, the skeletal objects each comprising at least one annotation added at a load time of the skeletal object; and combining, at the service bus, the skeletal object with existing skeletal objects by matching one of the at least one annotations of the skeletal object to similar existing annotations of existing skeletal objects, the combining of the skeletal objects resulting in the received unit of data being at least one of the set of predefined data object types; extracting data relevant to a predefined data object type of the set of predefined data object types from the received unit of data; populating a data object instance of the predefined data object type with the extracted data; defining one or more relationships between the data object instance and at least one other data object instance of the predefined data object type and/or a second predefined data object type of the set of predefined data objects, the defining occurring based on a set of parameters associated with the predefined data object type and on content of the extracted data, the defining further comprising inferring at least one of the one or more relationships based on a transitivity analysis by the recurring revenue management system between the data object instance and the at least one other data object instance; generating an opportunity for a sale or renewal of a recurring revenue asset based at least in part on the one or more relationships; and providing user interface data to a client machine for presenting the opportunity to a user via a user interface shown on a display device of the client machine. - View Dependent Claims (12, 13, 14, 15, 16, 17, 20)
-
Specification