Extensible infrastructure for managing workflow on a plurality of installed application components that interact with a central hosted component

• US 9,489,695 B1
• Filed: 03/15/2013
• Issued: 11/08/2016
• Est. Priority Date: 12/03/2012
• Status: Active Grant

• Current Assignee: Guidewire Software Incorporated
• Original Assignee: Guidewire Software Incorporated
• Inventors: Kreisel, Raymond Timothy, Branson, Kenneth William, Tran, Mui Thu
• Primary Examiner(s): Wathen, Brian W
• Application Number:
  US13/835,198
• Time in Patent Office: 1,334 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/0633 Workflow analysis
• CPC Class Codes: G06Q 10/0635 Risk analysis of enterprise or organisation activities
• CPC Class Codes: G06Q 10/103 Workflow collaboration or project management
• CPC Class Codes: G06Q 40/08 Insurance

Abstract

Managing workflow on a plurality of installed application components that interact with a central hosted component is disclosed. A new rule is defined on the central hosted component. The new rule is applied, based on data provided by an installed application component and information that is managed by the central hosted component, to generate a new action item to be executed on the installed application component. The new action item to be executed by the installed application component is sent. The new action item modifies a workflow on the installed application component without modifying application code on the installed application component.

Claims

1. A method, comprising:

defining, on a central hosted component, a new rule for determining an action item that is usable to modify insurance related processing workflows on a plurality of remote, installed application components that interact with the central hosted component, wherein the plurality of remote, installed application components are associated with different insurance carriers;

obtaining, from a remote, installed application component included in the plurality of remote, installed application components, insurance related data associated with an insurance entity on which a workflow on the remote, installed application component is operating;

determining, based at least in part on the defined new rule and data aggregated from at least some of the other remote, installed application components included in the plurality of remote, installed application components that are associated with different insurance carriers, that a new action item to be executed on the remote, installed application component should be generated;

generating, at the central hosted component, the new action item based at least in part on the determination; and

communicating, to the remote, installed application component, the generated new action item to be executed by the remote, installed application component, wherein the new action item, when executed by the remote, installed application component, modifies the workflow on the remote, installed application component without modifying application code on the remote, installed application component.

2. The method of claim 1, further comprising storing the new rule on the central hosted component.

3. The method of claim 1, wherein the new action item includes one or more of an insurance related activity, underwriting issue, alert, notification, hold, trouble ticket, or block.

4. The method of claim 1, further comprising identifying the insurance entity that is associated with the workflow.

5. The method of claim 4, wherein identifying the insurance entity is based at least in part on geographical bounds.

6. The method of claim 4, further comprising identifying the workflow on the remote, installed application component to be modified using the generated new action item based at least in part on characteristics of the insurance entity.

7. The method of claim 4, wherein the insurance entity includes at least one of a claim, policy, or account.

8. The method of claim 1, further comprising obtaining data from an external third-party source that is unavailable to the remote, installed application component.

9. The method of claim 1, further comprising anonymizing at least a portion of the data received from the at least some of the other remote, installed application components included in the plurality of remote, installed application components that are associated with different insurance carriers.

10. The method of claim 1, wherein aggregating the data received from the at least some of the remote, installed application components includes deriving aggregate statistics from at least a portion of the data received from the at least some of the remote, installed application components.

11. The method of claim 1, wherein the insurance entity comprises a claim, wherein the defined new rule and the data aggregated from at least some of the other remote, installed application components are used to detect fraud associated with the claim, and wherein the new action item to be executed on the remote, installed application component comprises a fraud detection notification alert.

12. A system, comprising:

a set of one or more processors configured to;

define, on a central hosted component, a new rule for determining an action item that is usable to modify insurance related processing workflows on a plurality of remote, installed application components that interact with the central hosted component, wherein the plurality of remote, installed application components are associated with different insurance carriers;

obtain, from a remote, installed application component included in the plurality of remote, installed application components, insurance related data associated with an insurance entity on which a workflow on the remote, installed application component is operating;

determine, based at least in part on the defined new rule and data aggregated from at least some of the other remote, installed application components included in the plurality of remote, installed application components that are associated with different insurance carriers, that a new action item to be executed on the remote, installed application component should be generated;

generate, at the central hosted component, the new action item based at least in part on the determination; and

communicate, to the remote, installed application component, the generated new action item to be executed by the remote, installed application component, wherein the new action item, when executed by the remote, installed application component modifies the workflow on the remote, installed application component without modifying application code on the remote, installed application component; and

a memory coupled to the set of one or more processors and configured to provide the set of one or more processors with instructions.

13. The system recited in claim 12, wherein the set of one or more processors is further configured to store the new rule on the central hosted component.

14. The system recited in claim 12, wherein the new action item includes or more of an insurance related activity, underwriting issue, alert, notification, hold, trouble ticket, or block.

15. The system of claim 12, wherein the set of one or more processors is further configured to identify the insurance entity that is associated with the workflow.

16. The system of claim 15, wherein identifying the insurance entity is based at least in part on geographical bounds.

17. The system of claim 15, wherein the set of one or more processors is further configured to identify the workflow on the remote, installed application component to be modified using the generated new action item based at least in part on characteristics of the insurance entity.

18. The system of claim 15, wherein the insurance entity includes at least one of a claim, policy, or account.

19. The system of claim 12, wherein the set of one or more processors is further configured to obtain data from an external third-party source that is unavailable to the remote, installed application component.

20. A computer program product embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

defining, on a central hosted component, a new rule for determining an action item that is usable to modify insurance related processing workflows on a plurality of remote, installed application components that interact with the central hosted component, wherein the plurality of remote, installed application components are associated with different insurance carriers;

obtaining, from a remote, installed application component, insurance related data associated with an insurance entity on which a workflow on the remote, installed application component is operating;

determining, based at least in part on the defined new rule and data aggregated from at least some of the other remote, installed application components included in the plurality of remote, installed application components that are associated with different insurance carriers, that a new action item to be executed on the remote, installed application component should be generated;

generating, at the central hosted component, the new action item based at least in part on the determination; and

communicating, to the remote, installed application component, the generated new action item to be executed by the remote, installed application component, wherein the new action item, when executed by the remote, installed application component, modifies a workflow on the remote, installed application component without modifying application code on the remote, installed application component.

21. The computer program product recited in claim 20, further comprising storing the new rule on the central hosted component.

22. The computer program product recited in claim 20, wherein the new action item includes one or more of an insurance related activity, underwriting issue, alert, notification, hold, trouble ticket, or block.

23. The computer program product of claim 20, further comprising obtaining data from an external third-party source that is unavailable to the remote, installed application component.