Abstract: Systems, computer program products, and methods are described herein for predictive use of resources across a dispersed Internet protocol capable network connecting devices electrically attached to the network. The present invention is configured to determine a resource utilization profile associated with a first user; receive an indication from the first user to improve the resource utilization profile; initiate a first user interface, wherein the first user interface comprises one or more target resource utilization profiles associated with one or more users; receive a first user selection of a target resource utilization profile associated with the resource utilization profile that the first user wishes to change; determine one or more access paths associated with the at least one target resource utilization profile; and display on the first user computing device the one or more access paths to enable the first user to achieve the at least one target utilization profile.

Abstract: Systems, computer program products, and methods are described herein for access to a resource across a dispersed Internet protocol capable network connecting devices electrically attached to the network. The present invention is configured to receive an indication from a user to access a resource; display a first user interface on the user computing device, wherein the first user interface further comprises an option for the user to establish an authorization profile; receive a user acknowledgement to establish the authorization profile; determine one or more access paths associated with an authorization model to enable the user to establish the authorization profile; and display a second user interface on the user computing device, wherein the second user interface comprises the one or more access paths associated with the authorization model to enable the user to establish the authorization profile.

Abstract: A system for automatically filtering and aggregating plural smart device usage and diagnostic data includes a smart device, a resource management device, and a third party system, each having communication interfaces, memory devices, and processing devices. In the resource management device, one or more sets of smart device data, such as usage profiles and/or diagnostic information, is filtered to create an extracted data set, which can be communicated to a third party system to initiate communication between a device custodian, the third party system, host entity systems associated with one or more smart device, and other system participants associated with a particular smart device or multiple smart devices.

Abstract: The present invention provides for managing communication of data from Internet-connected devices, such as those devices within an IoT environment. Specifically, the invention provides automated determination of which devices are communicating to which third-party entities and, in some embodiments, the type of data being communicated to such third-party entities. Once such information is known, the third-party entity can be automatically placed into a designated third-party category, which defines the type of data that the third-party entity is authorized to receive. In addition, a user can manage the communications from such devices by selecting to prohibit (i.e., block) or limit, based on data type, which data is communicated to which third-party entities. Additionally, the identity of the third-party entities can be authenticated/verified, such that if the third-party entity cannot be verified, communication of data to that entity is blocked or limited.

Abstract: A rules engine stores customer data, a first rule comprising a first plurality of conditions, and a second rule comprising a second plurality of conditions, wherein the customer data is associated with a particular customer. The rules engine transforms a first portion of the customer data into a first code segment by applying the first rule and by satisfying a condition of the first plurality of conditions of the first rule. It also transforms a second portion of the customer data into a second code segment by applying the second rule and by satisfying a condition of the second plurality of conditions of the second rule. The rules engine further combines at least the first code segment and the second code segment to form a customer profile code. An interface engine communicatively coupled to the rules engine communicates the customer profile code to a third party.

Abstract: A system for transforming customer data includes a network interface and a processor. The network interface communicates a request for customer data associated with a particular geographical area. It also receives a customer profile code associated with the customer data, wherein the customer profile code comprises a first code segment and a second code segment. It further receives first and second rules associated with the customer profile code. The processor transforms the first and second code segments into customer data using the rules. It further analyzes the particular geographical area using the customer data.

Abstract: A system for transforming customer data includes a network interface and a processor. The network interface communicates a request for customer data associated with a determined set of customers. It also receives a customer profile code associated with the customer data, wherein the customer profile code comprises a first code segment and a second code segment. It further receives first and second rules associated with the customer profile code. The processor determines the set of customers, transforms the first and second code segments into customer data using the rules, and analyzes the customer data to determine an operations history for the set of customers.

Abstract: A system for authenticating a customer includes a network interface and a processor. The network interface communicates a request for customer data associated with a particular customer. It also receives a customer profile code associated with the customer, wherein the customer profile code comprises a first code segment and a second code segment. It further receives first and second rules associated with the customer profile code. The processor transforms the first and second code segments into customer data using the rules. It further authenticates the customer using the customer data.

Abstract: A system for encoding customer data includes a memory, a decision engine, a rules engine and an interface engine. The memory stores customer data associated with service levels and rules. The decision engine receives a request for customer data from a third party, determines that the third party is associated with a first service level, and retrieves the customer data associated with the first service level. The rules engine transforms customer data into first and second code segments by applying the rules. The rules engine combines at least the first code segment and the second code segment to form a customer profile code. An interface engine communicates the customer profile code to the third party.

Abstract: A system for transforming customer data includes a network interface and a processor. The network interface communicates a request for customer data associated with a particular geographical area. It also receives a customer profile code associated with the customer data, wherein the customer profile code comprises a first code segment and a second code segment. It further receives first and second rules associated with the customer profile code. The processor transforms the first and second code segments into customer data using the rules. It further analyzes the particular geographical area using the customer data.

Abstract: A system for authenticating a customer includes a network interface and a processor. The network interface communicates a request for customer data associated with a particular customer. It also receives a customer profile code associated with the customer, wherein the customer profile code comprises a first code segment and a second code segment. It further receives first and second rules associated with the customer profile code. The processor transforms the first and second code segments into customer data using the rules. It further authenticates the customer using the customer data.

Abstract: A system for transforming customer data includes a network interface and a processor. The network interface communicates a request for customer data associated with a determined set of customers. It also receives a customer profile code associated with the customer data, wherein the customer profile code comprises a first code segment and a second code segment. It further receives first and second rules associated with the customer profile code. The processor determines the set of customers, transforms the first and second code segments into customer data using the rules, and analyzes the customer data to determine an operations history for the set of customers.

Abstract: A system for encoding customer data includes a memory, a decision engine, a rules engine and an interface engine. The memory stores customer data associated with service levels and rules. The decision engine receives a request for customer data from a third party, determines that the third party is associated with a first service level, and retrieves the customer data associated with the first service level. The rules engine transforms customer data into first and second code segments by applying the rules. The rules engine combines at least the first code segment and the second code segment to form a customer profile code. An interface engine communicates the customer profile code to the third party.

Abstract: A rules engine stores customer data, a first rule comprising a first plurality of conditions, and a second rule comprising a second plurality of conditions, wherein the customer data is associated with a particular customer. The rules engine transforms a first portion of the customer data into a first code segment by applying the first rule and by satisfying a condition of the first plurality of conditions of the first rule. It also transforms a second portion of the customer data into a second code segment by applying the second rule and by satisfying a condition of the second plurality of conditions of the second rule. The rules engine further combines at least the first code segment and the second code segment to form a customer profile code. An interface engine communicatively coupled to the rules engine communicates the customer profile code to a third party.

Abstract: A rules engine stores a first rule, a second rule, and customer data. The rules engine transforms a portion of the customer data into a first code segment by applying the first rule and transforms a portion of the customer data into a second code segment by applying the second rule. In addition, the rules engine combines at least the first code segment and the second code segment to form a customer profile code. The generated customer profile code is associated with a customer identifier. A decision engine communicatively coupled to the rules engine matches the customer identifier of the customer profile code to third party data associated with a request for customer information. An interface engine communicatively coupled to the decision engine communicates the customer profile code to a third party if the customer identifier of the customer profile code matches the third party data.