Patent Grant
9384198
1. Technical Field
This disclosure generally relates to data services, and particularly to system integration services.
2. Description of the Related Art
Insurance agency management systems are specialized to handle the domain of insurance business processes. Content management systems are specialized to handle content and workflow. Each of these systems is useful to an insurance agency and many agencies choose to operate both types of systems. There are many insurance business activities that would benefit from interaction with both the agency management system and the content management system (for example, printing out an insurance application for an insurance carrier and saving a copy for the agency's records). Often this involves entering information in both systems and learning to navigate in the two systems. As standalone applications, this creates a burden of work for the user who has to make sure to precisely enter information into both systems and in the correct location in both of the systems. Because of the flexibility of content management systems and complexity of agency management systems, this can be a very tedious and time consuming task that is prone to human error, resulting in a cost to the business.
The agency management and content management integration system is a system which provides easy navigation, linking, and indexing with automatic content structure creation.
When an agency has both an agency management system and a content management system, it is advantageous to integrate these programs so that the user has to copy less data by hand (which is time consuming and prone to error and omission). Integration may also allow the users to quickly navigate between the agency management system and the content management system. Integration may additionally provide for the creation of content structures before there is a need to use the content structure. This may advantageously allow a user to immediately organize content and skip the content structure creation phase of their work. This may be especially valuable if the particular workflow does not start in the agency management system. By automatically creating content structures in a hierarchical fashion, the agency can deploy a unified organization structure that is enforced automatically across the organization. By providing an external integration, the content management system and agency management systems can be developed independently, retaining the benefits of specialization, while the integration pulls the two parts together.
A computer-implemented method may be summarized as including receiving information defining entities of an insurance agency management system; receiving content structure of a content management system; receiving mapping data indicative of mappings between the entities of the insurance agency management system and the content structure; automatically generating a data structure based on the mappings; storing the content structure in the data structure corresponding to the mappings; and automatically synchronizing with changes of the entities of the insurance agency management system, the synchronizing based on information indicative of the changes of the entities of the insurance agency management system.
The synchronizing may include receiving information indicative of changes of the entities of the insurance agency management system; automatically comparing at least one of a number of current attributes of the data structure and at least one of a number of current attributes of the content structure stored in the data structure; and automatically updating, based on the comparing, at least one of the current attributes of the data structure and the current attributes of the content structure stored in the data structure to correspond to the received changes.
The receiving information indicative of changes of the entities may occur automatically on a periodic or nonperiodic (aperiodic) basis without requesting the information indicative of changes of the entities. Synchronizing with changes of the entities of the insurance agency management system may occur at an initial generation of the data structure corresponding to the mappings. The automatically generating a data structure based on the mappings may include generating a hierarchical data structure corresponding to a hierarchical business structure defined by the mapping data.
The computer-implemented method may further include, after initial generation of the data structure, displaying a number of interactive graphical user interface elements operable to trigger automatically performing at least one of: opening the content structure or the data structure for viewing or editing, linking the content structure or the data structure to other content structures or entities, indexing the content structure or the data structure, or entering at least some of the mapping data.
The insurance agency management system, after initial generation of the data structure, may automatically provide information indicative of changes of the entities upon the changes occurring or on a periodic or nonperiodic (aperiodic) basis and wherein the automatically synchronizing may include automatically comparing at least one of a number of current attributes of the data structure and at least one of a number of current attributes of the content structure stored in the data structure to the provided information indicative of the changes; and automatically updating, based on the comparing, at least one of the current attributes of the data structure and the current attributes of the content structure stored in the data structure to correspond to the provided information indicative of the changes.
The entities may include at least one of: an insurance client entity, an insurance submissions entity, an insurance policies entity, an insurance claims entity, an insurance quotes entity, an insurance vendor entity, an insurance company employee entity, an insurance carrier entity, or an insurance transactions entity. The changes of the entities may be at least one of: adding entities, changes to relationships between the entities, changes to a hierarchical structure defining the entities, or changes to attributes of the entities.
The computer-implemented method may further include automatically organizing the content structure based on entity criteria including at least one of: insurance business unit, insurance coverage type, agency number, customer line of business, policy type of business, policy type, submission type.
A system may be summarized as including a computer processor; and a non-transitory memory communicatively coupled to the computer processor having computer-executable instructions stored thereon that when executed by the computer processor cause the computer processor to perform: receiving information defining entities of an insurance agency management system; receiving content structure of a content management system; receiving mapping data indicative of mappings between the entities of the insurance agency management system and the content structure; automatically generating a data structure based on the mappings; storing the content structure in the data structure corresponding to the mappings; and automatically synchronizing with changes of the entities of the insurance agency management system, the synchronizing based on information indicative of the changes of the entities of the insurance agency management system.
The synchronizing may include receiving information indicative of changes of the entities of the insurance agency management system; automatically comparing at least one of a number of current attributes of the data structure and at least one of a number of current attributes of the content structure stored in the data structure; and automatically updating, based on the comparing, at least one of the current attributes of the data structure and the current attributes of the content structure stored in the data structure to correspond to the received changes. The receiving information indicative of changes of the entities may occur automatically on a periodic or aperiodic basis without requesting the information indicative of changes of the entities. Synchronizing with changes of the entities of the insurance agency management system may occur at an initial generation of the data structure corresponding to the mappings. The automatically generating a data structure based on the mappings may include generating a hierarchical data structure corresponding to a hierarchical business structure defined by the mapping data.
The computer-executable instructions, when executed by the computer processor, after initial generation of the data structure, may further configure the computer processor to display a number of interactive graphical user interface elements operable to trigger automatically performing at least one of: opening the content structure or the data structure for viewing or editing, linking the content structure or the data structure to other content structures or entities, indexing the content structure or the data structure, or entering at least some of the mapping data.
The insurance agency management system may be configured to, after initial generation of the data structure, automatically provide information indicative of changes of the entities upon the changes occurring or on a periodic or nonperiodic (aperiodic) basis and wherein the automatically synchronizing may include automatically comparing at least one of a number of current attributes of the data structure and at least one of a number of current attributes of the content structure stored in the data structure to the provided information indicative of the changes; and automatically updating, based on the comparing, at least one of the current attributes of the data structure and the current attributes of the content structure stored in the data structure to correspond to the provided information indicative of the changes.
The entities may include at least one of: an insurance client entity, an insurance submissions entity, an insurance policies entity, an insurance claims entity, an insurance quotes entity, an insurance vendor entity, an insurance company employee entity, an insurance carrier entity, or an insurance transactions entity. The changes of the entities may be at least one of: adding entities, changes to relationships between the entities, changes to a hierarchical structure defining the entities, or changes to attributes of the entities.
The computer-executable instructions, when executed by the computer processor, may further configure the computer processor to automatically organize the content structure based on entity criteria including at least one of: insurance business unit, insurance coverage type, agency number, customer line of business, policy type of business, policy type, submission type.
At least one non-transitory computer-readable medium may be summarized as one that stores instructions that when executed by at least one computer system cause the at least one computer system to perform: receiving information defining entities of an insurance agency management system; receiving content structure of a content management system; receiving mapping data indicative of mappings between the entities of the insurance agency management system and the content structure; automatically generating a data structure based on the mappings; storing the content structure in the data structure corresponding to the mappings; and automatically synchronizing with changes of the entities of the insurance agency management system, the synchronizing based on information indicative of the changes of the entities of the insurance agency management system.
The synchronizing may include receiving information indicative of changes of the entities of the insurance agency management system; automatically comparing at least one of a number of current attributes of the data structure and at least one of a number of current attributes of the content structure stored in the data structure; and automatically updating, based on the comparing, at least one of the current attributes of the data structure and the current attributes of the content structure stored in the data structure to correspond to the received changes.
The receiving information indicative of changes of the entities may occur automatically on a periodic basis without requesting the information indicative of changes of the entities. Synchronizing with changes of the entities of the insurance agency management system may occur at an initial generation of the data structure corresponding to the mappings. The automatically generating a data structure based on the mappings may include generating a hierarchical data structure corresponding to a hierarchical business structure defined by the mapping data. The computer-executable instructions, when executed by the at least one computer system, may further cause the at least one computer system to display a number of interactive graphical user interface elements operable to trigger automatically performing at least one of: opening the content structure or the data structure for viewing or editing, linking the content structure or the data structure to other content structures or entities, indexing the content structure or the data structure, or entering at least some of the mapping data.
The computer-executable instructions, when executed by the at least one computer system, may further cause the at least one computer system to, after initial generation of the data structure, cause the insurance agency management system to automatically provide information indicative of changes of the entities upon the changes occurring or on a periodic or nonperiodic (aperiodic) basis and wherein the automatically synchronizing includes automatically comparing at least one of a number of current attributes of the data structure and at least one of a number of current attributes of the content structure stored in the data structure to the provided information indicative of the changes; and automatically updating, based on the comparing, at least one of the current attributes of the data structure and the current attributes of the content structure stored in the data structure to correspond to the provided information indicative of the changes.
The entities may include at least one of: an insurance client entity, an insurance submissions entity, an insurance policies entity, an insurance claims entity, an insurance quotes entity, an insurance vendor entity, an insurance company employee entity, an insurance carrier entity, or an insurance transactions entity. The changes of the entities may be at least one of: adding entities, changes to relationships between the entities, changes to a hierarchical structure defining the entities, or changes to attributes of the entities. The computer-executable instructions, when executed by the at least one computer system, may further cause the at least one computer system to automatically organize the content structure based on entity criteria including at least one of: insurance business unit, insurance coverage type, agency number, customer line of business, policy type of business, policy type, submission type.
A system may be summarized as including at least one computer processor; and a non-transitory memory communicatively coupled to the computer processor having computer-executable instructions stored thereon that when executed by the computer processor cause the at least one computer processor to: link entities of an insurance agency management system to content hierarchical structures of a content management system; automatically provide information indicative of changes of an insurance agency business unit upon the changes occurring or on a periodic or nonperiodic (aperiodic) basis; and automatically synchronize a content management system content hierarchical structure related to the insurance agency business unit with the changes to the insurance agency business unit.
The computer-executable instructions may further cause the at least one computer processor to: automatically compare at least one current attribute of a data structure for the insurance agency business unit of the insurance agency management system to an attribute of content related to the insurance agency business unit stored in the content management system content hierarchical structures. The information indicative of changes may be automatically provided by the insurance agency management system. The computer-executable instructions may further cause the at least one computer processor to: automatically provide information indicative of changes to content of an insurance policy; and automatically update content management system content hierarchical structures based on the information indicative of changes to content of the insurance policy. The information indicative of changes to content of the insurance policy may be automatically provided by the content management system. The computer-executable instructions may further cause the at least one computer processor to link the entities of the insurance agency management system to the content hierarchical structures of the content management system as an initial process before any of the information indicative of changes is provided.
The computer-executable instructions may further cause the at least one computer processor to: provide a preview of changes to the content hierarchical structure; provide a testing environment to test the content hierarchical structure changes; provide troubleshooting logs resulting from testing of the content hierarchical structure changes; and link the entities of the insurance agency management system to content hierarchical structures of the content management system by providing multiple mappings between the entities of the insurance agency management system and the content hierarchical structures.
The computer-executable instructions may further cause the at least one computer processor to provide an interface for a user to manually trigger a synchronization of the content management system content hierarchical structure related to the insurance agency business unit with the changes to the insurance agency business unit.
In the drawings, identical reference numbers identify similar elements or acts. The sizes and relative positions of elements in the drawings are not necessarily drawn to scale. For example, the shapes of various elements and angles are not drawn to scale, and some of these elements are arbitrarily enlarged and positioned to improve drawing legibility. Further, the particular shapes of the elements as drawn are not intended to convey any information regarding the actual shape of the particular elements, and have been solely selected for ease of recognition in the drawings.
In the following description, certain specific details are set forth in order to provide a thorough understanding of various disclosed embodiments. However, one skilled in the relevant art will recognize that embodiments may be practiced without one or more of these specific details, or with other methods, components, materials, etc. In other instances, well-known structures associated with computing systems including client and server computing systems, as well as networks, including various types of telecommunications networks, have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the embodiments.
Unless the context requires otherwise, throughout the specification and claims which follow, the word “comprise” and variations thereof, such as “comprises” and “comprising,” are to be construed in an open, inclusive sense, that is, as “including, but not limited to.”
Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” include plural referents unless the content clearly dictates otherwise. It should also be noted that the term “or” is generally employed in its sense including “and/or” unless the content clearly dictates otherwise.
The headings and Abstract of the Disclosure provided herein are for convenience only and do not interpret the scope or meaning of the embodiments.
The networked environment 100 may include a plurality of entities (e.g., insurance entities), entity 1106, entity 2108, and entity n 110; one or more agency management systems 104; one or more content management systems 102; and an agency management and content management integration system 112. Entity 1106, entity 2108, entity n 110, the one or more agency management systems 104, the one or more content management systems 102 and the agency management and content management integration system 112 may all be communicatively coupled via a network 116. Alternatively, one or more of the systems or devices may be located on a single system and/or at a single physical location. Additional systems and devices may also be present, but are not illustrated for clarity of presentation.
The network 116 may be any computer network, telecommunications network or combination of telecommunications and computer networks that enables communication between the various systems and entities connected to the network 116 shown in
The network 116 may comprise connections to entity 1106, entity 2, 108, entity n 110, the one or more agency management systems 104, and the one or more content management systems 102 such that the agency management and content management integration system 112 may provide integration of the agency management system(s) 104 and content management system(s) 102, and may itself represent multiple interconnected networks. For instance wired and wireless enterprise-wide computer networks, intranets, extranets, and/or the Internet may be included in or comprise a part of network 116. Embodiments may include various types of communication networks including other telecommunications networks, cellular networks, paging networks, and other mobile networks. There may be any variety of computers, switching devices, routers, bridges, firewalls, edge devices, multiplexers, phone lines, cables, telecommunications equipment and other devices within network 116 and/or in the communications paths between the systems and entities of
In accordance with an aspect of the disclosure, the systems and/or systems of the entities shown in
Although the physical environment of the network 116 may have connected devices such as computers, the physical environment may alternatively have or be described as comprising various digital devices such as personal digital assistants (PDAs), televisions, MP3 players, etc., software objects such as interfaces, Component Object Model (COM) objects and the like.
There are a variety of systems, components, and network configurations that may also support distributed computing environments within the network 116. For example, computing systems may be connected together within the network 116 by wired or wireless systems, by local networks or by widely distributed networks. Currently, many networks are coupled to the Internet, which provides an infrastructure for widely distributed computing and encompasses many different networks. Any such infrastructures, whether coupled to the Internet or not, may be used in conjunction with, be connected to, or comprise part of the network 116.
The computer system 200 is suitable for implementing systems, devices and methods for agency management and content management integration, according to one illustrated embodiment. The computer system 200 will at times be referred to in the singular herein, but this is not intended to limit the embodiments to a single device since in typical embodiments, there may be more than one computer system or devices involved. Unless described otherwise, the construction and operation of the various blocks shown in
The computer system 200 may include one or more processing units 212a, 212b (collectively 212), a system memory 214 and a system bus 216 that couples various system components including the system memory 214 to the processing units 212. The processing units 212 may be any logic processing unit, such as one or more central processing units (CPUs) 212a, digital signal processors (DSPs) 212b, application-specific integrated circuits (ASICs), programmable gate arrays such as field programmable gate arrays (FPGAs), etc. The system bus 216 can employ any known bus structures or architectures, including a memory bus with memory controller, a peripheral bus, and a local bus. The system memory 214 includes read-only memory (“ROM”) 218 and random access memory (“RAM”) 220. A basic input/output system (“BIOS”) 222, which can form part of the ROM 218, contains basic routines that help transfer information between elements within the computer system 200, such as during start-up.
The computer system 200 may include a hard disk drive 224 for reading from and writing to a hard disk 226, an optical disk drive 228 for reading from and writing to removable optical disks 232, and/or a magnetic disk drive 230 for reading from and writing to magnetic disks 234. The optical disk 232 can be a CD-ROM, while the magnetic disk 234 can be a magnetic floppy disk or diskette. The hard disk drive 224, optical disk drive 228 and magnetic disk drive 230 may communicate with the processing unit 212 via the system bus 216. The hard disk drive 224, optical disk drive 228 and magnetic disk drive 230 may include interfaces or controllers (not shown) coupled between such drives and the system bus 216, as is known by those skilled in the relevant art. The drives 224, 228 and 230, and their associated computer-readable storage media 226, 232, 234, may provide nonvolatile and non-transitory storage of computer readable instructions, data structures, program modules and other data for the computer system 200. Although the depicted computer system 200 is illustrated employing a hard disk 224, optical disk 228 and magnetic disk 230, those skilled in the relevant art will appreciate that other types of computer-readable storage media that can store data accessible by a computer may be employed, such as magnetic cassettes, flash memory, digital video disks (“DVD”), Bernoulli cartridges, RAMs, ROMs, smart cards, etc. For example, computer-readable storage media may include, but is not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc ROM (CD-ROM), digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, solid state memory or any other medium which can be used to store the desired information and which may be accessed by processing unit 212a.
Program modules can be stored in the system memory 214, such as an operating system 236, one or more application programs 238, other programs or modules 240 and program data 242. Application programs 238 may include instructions that cause the processor(s) 212 to provide agency management and content management integration such as, for example, integration between agency management system(s) 104 and content management system(s) 102. Other program modules 240 may include instructions for handling security such as password or other access protection and communications encryption. The system memory 214 may also include communications programs, for example, a Web client or browser 244 for permitting the computer system 200 to access and exchange data with sources such as Web sites of the Internet, corporate intranets, extranets, or other networks and devices as described herein, as well as other server applications on server computing systems. The browser 244 in the depicted embodiment is markup language based, such as Hypertext Markup Language (HTML), Extensible Markup Language (XML) or Wireless Markup Language (WML), and operates with markup languages that use syntactically delimited characters added to the data of a document to represent the structure of the document. A number of Web clients or browsers are commercially available such as those from Mozilla, Google, and Microsoft of Redmond, Wash.
While shown in
An operator can enter commands and information into the computer system 200 through input devices such as a touch screen or keyboard 246 and/or a pointing device such as a mouse 248, and/or via a graphical user interface. Other input devices can include a microphone, joystick, game pad, tablet, scanner, etc. These and other input devices are connected to one or more of the processing units 212 through an interface 250 such as a serial port interface that couples to the system bus 216, although other interfaces such as a parallel port, a game port or a wireless interface or a universal serial bus (“USB”) can be used. A monitor 252 or other display device is coupled to the system bus 216 via a video interface 254, such as a video adapter. The computer system 200 can include other output devices, such as speakers, printers, etc.
The computer system 200 can operate in a networked environment using logical connections to one or more remote computers and/or devices as described above with reference to
Although not required, the embodiments will be described in the general context of computer-executable instructions, such as program application modules, objects, or macros stored on computer- or processor-readable storage media and executed by a computer or processor. Those skilled in the relevant art will appreciate that the illustrated embodiments as well as other embodiments can be practiced with other system configurations and/or other computing system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, personal computers (“PCs”), network PCs, mini computers, mainframe computers, and the like. The embodiments can be practiced in distributed computing environments where tasks or modules are performed by remote processing devices, which are linked through a communications network such as network 116. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Previously, attempts have been made to include “light weight” (i.e., lacking full functionality) content management systems into agency management systems to mitigate costs, but these systems cannot compete with a full content management and workflow system. It is more valuable to have the two specialized systems than to have one system and a light weight version of the other. Advantageously, the embodiments described herein integrate the two specialized systems such that the end user, which could be an insurance manager, executive, sales representative, customer service representative, account manager, or even mail indexer gains productivity and data robustness, reducing the cost to the business.
Additionally, some previous attempts have been made to include a completely user driven integration. However, sometimes a user's workflow does not originate in the agency management system, but because the content management system would require the integration to be pushed from the agency management system, the user would have to enter the agency management system, start the integration, and then move back to the content management system. Advantageously, the embodiments described herein immediately reflect changes in the agency management system in the content management system.
Using the integration layer 304, the agency management and content management integration system 112 allows automatic generation of content structure in the content management system for various agency management system domain entities, for example, insurance entities such as clients, submissions, policies, claims, quotes, vendors, employees (staff members), companies (carriers), and transactional elements (activities, tasks, notes, etc.). The agency management and content management integration system 112 provides linking between the agency management system entity to the appropriate content management system structure or structures through a well-defined mapping process (as explained in more detail with reference to
The agency management and content management integration system 112 also executes automatic data entry into the content management system 102 to assist content management system workflow processes. Specifically, agency management and content management integration system 112 provides automatic data synchronization into the content management system 102 so that data stays current in the content management system 102 even when the agency management system 104 is changing. Hierarchical content structures are automatically generated by the agency management and content management integration system 112 so that an agency can automatically deploy an organizational structure to their end users. This organizational structure is deployed by organizing content based on domain entity criteria (such as business unit, coverage type, entity type, etc.) and by supporting multiple agencies, including multiple agency management system environments.
Also, multiple content management system structure divisions for the same entities are dynamically provided. For example, one entity may exist in multiple structures in the content management system 102 based on certain domain criteria like business unit or coverage type and a flexible mapping of entities to content structures is used to support the various organizational strategies of different insurance companies.
The agency management and content management integration system 112 includes testing mechanisms and performs logging to aid implementers in troubleshooting connection problems to the agency management system 104 and the content management system 102. A testing platform is also provided for verifying that the mappings are configured per insurance company specifications as well as a hierarchical view of mapping results. This provides an implementer of the content management integration system 112 an easy way to verify the view of the content structures that will be created before actually creating the structures in the content management system 102.
Front end processes 306 include software elements that the end user directly interacts with to perform work. Primarily, this includes providing a user interface 310 or user interface elements within the agency management system 104. The user interface 310 has icons, buttons or other selectable user interface elements that a user clicks on, presses or otherwise selects within the agency management system 104 while viewing a particular domain entity. These selections perform actions such as opening 312, linking 314, and indexing 316 data structures and content in the content management system 102.
Back end processes and utilities 308 include software elements that may be automated and may run as services. The structure creation element 320 creates structures in the content management system 102 and the data synchronization element 322 synchronizes data in the content management system 102 to match entities in the agency management system 104. The various synchronization processes of the data synchronization element 322 take the entities in the agency management system 104 as input and generates corresponding structures in the content management system 102 using the structure creation element 320 based on mappings defined by the user.
There are two synchronization processes, the baseline synchronization process 324 and the delta synchronization process 326. The baseline synchronization process 324 is responsible for initial structure creation and en masse structure updates in the content management system 102. In one embodiment the baseline synchronization process 324 is manually started and runs and finishes completely. The delta synchronization process 326 performs continuous content structure creation and updating. In one embodiment, the delta synchronization process 326 runs at all times as a service and uses one of two strategies to receive changes in the agency management system. For example, the delta synchronization process either polls the agency management system for changes or receives notifications from the agency management system that a change has occurred and then updates the content management system accordingly. There are various configuration points and configuration utilities that allow an implementer of the agency management and content management integration system 112 to configure and manage configurations and the operation of the various utilities. Also, some of these utilities configure the front end processes 306.
In the content management system, the entity 410 is represented by either a file 402 or 404 or a folder 406408. Entities that are represented by a file 402 or 404 are called top level entities (such as clients and vendors of an insurance agency). Some entities are hierarchically related to other entities. In an insurance agency example, clients own policies and policies have claims submitted against them. In the content management system, the sub-entities are represented by folders 406 or 408 in the file 402 or 404 (e.g., policy or claim folders in client files) or folders in another folder (e.g., claim folders in policy folders). Also, parent folders can be configured for these sub folders based on other criteria (e.g., a claims folder to hold all claim folders or a policy term folder that holds all policies of a specific year).
Top level entities (e.g., domain entity 410) may or may not have multiple content structures (e.g., files 402 or 404 and folders 406 and 408) that match them. This duplication results from the way entities are mapped into the content management system 102. Insurance industry business rules often divide up the work that is done on a client based on specific usage criteria of the work being done. For example, a client that belongs to a certain division of a company may in some cases only be worked on by that division. A client with a policy of a certain type may in some cases only be worked on by a specific group in that company. Because of the content management system's ability to provide security features based on content structure to match the agency's work structure, it is often advantageous place a client in different file containers. All files 402404 within a file container 418 are unique, but uniqueness is not required between file containers. For example, in the ImageRight® content management system, these file containers are specified by three content structure concepts: location, drawer, and file type. A file is considered unique based on its file number within a container 418. Work for one client may be split across the organization, which may be referred to herein as a work division, in which case it is beneficial to the organization to have a separate file container 418 for each work division.
Also, some content management system content structures may require additional originations of content within that entity's structure. For example, a policy may have endorsement content or application content. By allowing the precreation of these sub structures, the agency management and content management integration system 112 allows the organization to enforce a consistent organizational scheme throughout the system, removing the burden from the end user.
Shown on the user interface 500 is example integration job information 502 for the commercial lines policy work division 504, associated entity filters 506 for the integration job 414, and an associated content structure 508 for the integration job 414. Also shown are user interface controls 510 for executing the applicable integration job 414.
Referring now to
If an entity passes the all criteria setup by the filters (indicated by the dashed “Yes” arrow), then custom data mapping component 606 may be applied to the entity 410 using other entity information 410 to further determine the final content management structure. For files, the unique entity identifier 412 is directly mapped to an associated file number 610. For all entity files and entity folders, the unique entity identifier 412 is directly mapped to one specified key attribute 612 on the file or folder. Also, additional entity information 410 may be mapped to an additional attribute 614 resulting from the output of the custom data mapping component 606. In one embodiment, the filters 602 are configured to ensure that there is only one integration job per work division so that files are not duplicated within a work division.
Some entities are hierarchically related to other entities. For example, clients own policies and policies have claims submitted against them. In the content management system, these sub-entities are represented by folders in the file. Files can contain folders and folders can contain further folders. In one embodiment, the system only has one folder representing a sub-entity across the entire content management system. This is enforced through proper creation of integration jobs.
In one embodiment, the back end processes automatically perform these jobs whenever a change is detected in the agency management system 104 and the front end processes 306 allow a user to access the entity file or folder from the agency management system object after the integration job 414 has been executed.
In one embodiment, there are integrations between AMS360®, Sagitta®, and the BenefitPoint (BP)® agency management systems and the content management system supported is ImageRight® (IR).
The agency management and content management integration system enables a user to perform content management system actions from the agency management system 104. Shown in
Selecting the applicable button within the agency management system user front end 801 calls the LaunchXX.exe program 802 with a specific command line. The command line contains information that identifies and describes the current domain entity 410, in this case an AMS360® client. A client (called a customer in the AMS360® system and an account in BenefitPoint® system) is identified by some unique string in each system called the client. For AMS360®, the client identifier is a globally unique identifier (GUID). Also, the different LaunchXX.exe programs 802 each represent an action (Open, Save, Accounting Management). The command line is reformatted by the LaunchXX.exe program 802 based on the contents of the LaunchXX.ini file 804 and based on the intended action. This reformatting results in a command line for one of the various linker programs denoted collectively as Linker.exe 806 (e.g., AMS360Link.exe for the AMS360® system, SagittaLink.exe for the Sagitta® system and BPLink.exe for the BenefitPoint® system). After this reformatting, the command line is then executed.
The Linker.exe programs 806 (e.g., AMS360Linker.exe, SagittaLinker.exe, and BPLinker.exe) have agency management system specific knowledge and are configured to match the integration jobs defined for the integrated environment. The configurations are placed in a configuration file, denoted as Link.config file 810, that is shared between all users in the environment by placing it on a network share. On the users' system, only the linker.exe.config file 808 needs to be altered to point to this shared Link.config file 810. This allows all users' configurations to be updated by changing just one file. The Linker.exe program 806 maps the entity identification 412 and information 410 to the content management system 102 and calls the content management systems exposed interoperability interface, denoted as IRLinker.exe 812, to perform the desired command on the resulting content structure or structures that will be reflected on the content management and workflow system user front end 814.
The specific actions enabled by the agency management and content management integration system 112 are Open, Save, and Account Management. Performing an Open action on a top level entity will cause the content management system 102 to navigate to structures matching the entity 410 based on the key attributes 612 placed on the structure by the back end integration process 308. It will also attempt to create the appropriate file in the content management system 102 if it does not exist, filling in the key attributes 612 at that time. Performing an Open action on a sub entity will cause the content management system 102 to navigate to the structures matching the entity 410. If no matching structures are found, nothing will be created.
Performing the Save action on an entity 410 will have a content management system context-specific result.
The process 900 starts at the Save action 902, such as when the user clicks the WorkSmart File Save button 704 shown in
At 904 a processor determines whether the entity to which the Save action pertains 902 is a top level entity.
At 906, if it was determined that the entity to which the Save action pertains 902 is a top level entity, then the processor determines whether the workflow task is locked for that entity.
At 908, if it was determined that the workflow task is locked for that entity, then the processor determines whether the current file to be saved is marked as temporary.
At 910, if it was determined that the current file to be saved is marked as temporary, then the processor indexes the selected content structures to an appropriate existing file.
At 912 if it was determined that the entity to which the Save action pertains is not a top level entity, or that the workflow task not locked for that entity or that the current file to be saved is not marked as temporary, then the processor tags the selected content structures. The tagging action marks the content management structure with the key attributes 612 of the domain entity 410. This tagging works on both top level entities and sub entities. This allows the Open action to use the key attributes to find the content management structure. On the other hand, the indexing action only works on top level entities and moves the selected content into the correct top level content structure matching the entity based on key attributes. The original top level structure is marked as temporary, and a workflow task should be locked on some structure in the original top level structure or the Save action will perform the tag option instead of the indexing action as illustrated process 900.
The Agency management and content management integration system 112 pre-creates content management system structures based on the agency management systems' entities in an automated fashion.
The agency management and content management integration system 112 provides a set of utilities to help pre-create data structures so that users do not have to manually enter data into the content management system 102. Shown on user interfaces 1000 and 1002 is a connections tab 1004 under which agency management system connections 1006 are displayed. Based on these agency management system connections 1006, content management system structures will be created in response to a user interacting with the user selectable controls 1008 shown on user interface 1000 or by subscribing to a synchronization service 1010 shown in interface 1002.
Often, an agency has insurance data before implementing the agency management and content management integration system 112. The agency management and content management integration system 112 provides a way to create the vast amount of structure for all of an agency's data. The baseline synchronization process 324 executed by one or more processors performs this function. The baseline synchronization process 324 provides on a large scale the ability to take information from an existing agency management system and apply it to the content management system 102.
Also, once the user has run the baseline synchronization process 324, the user will start to change their agency management system data. In order to keep the content management system 102 synchronized with the agency management system 104, changes in the agency management system 104 are constantly or nearly constantly reflected in content management system 102. The delta synchronization process 326 performs this function.
At 1012, the agency management and content management integration system 112 determines which entity needs to be created or updated.
At 1014, the agency management and content management integration system 112 retrieves the entity information (e.g., from the agency management system 104).
At 1016, the agency management and content management integration system 112 determines which integration jobs match the retrieved entity (e.g., integration job 414).
At 1018, the agency management and content management integration system 112 transforms or maps the entity into a content management structure (e.g., a content management system structure such as file container 418 and the related substructures).
At 1020, the agency management and content management integration system 112 creates or updates the content management structure accordingly to synchronize data between the content management system 102 and agency management system 104.
First will be described components common to both the update (delta) synchronization system architecture 1100 and a baseline synchronization system architecture 1200 of the backend integration module. There are three layers to the backend integration module. The first layer is the domain layer 1104, where the backend integration module retrieves source data from some source such as the agency management system 104. However, the source may vary depending on the integration piece. After forming a connection to this source, a data extractor 1106 creates a generic data representation for the entity and is referred to as domain objects 1108.
These domain objects 1108 are passed to the domain transformation and mapping layer 1110. The domain transformation and mapping layer 1110 converts domain objects into content management system domain objects 1112, which are structures like locations, drawers, files, and folders based on integration jobs. Finally, these content management system domain objects 1112 are passed to the file services layer 1114 of the content management system 102. This file services layer 1114 takes the representations of the content management system domain objects 1112 and actually applies changes therein to the content management system 102. This layered system allows for changes in either the agency management system 104 or content management system 102 to not affect large portions of the system.
The data extractor 1106 contains the entities that might need to be created or updated. If a sub entity is included, its parent entity is included also, so that the integration jobs can correctly process it. The data extractor 1106 can be made to connect to any agency system and in various ways.
For the baseline synchronization architecture 1200, the agency management and content management integration system 112 uses extracted files from the Agency Management System Extractor 1206 containing the information for all or a subset of entities in the agency management system 104. From these files, the latency of web service calls and database queries is avoided. Because of the large amount of data that may need to be initialized or updated, these latencies can render the baseline synchronization process unusable as millions of entities each add a few seconds of latency. For example, in the AMS360® management system, the baseline synchronization process uses comma separated value (CSV) files 12021204 containing entity data per line. For the Sagitta® agency management system, the baseline synchronization process uses XML files containing a hierarchy of data. However any file format may be used for integration of other types of systems that is capable of presenting data in an organized fashion.
For the delta synchronization architecture 1100, the connection is a web service exposed by the agency management system denoted by the notification services block 1116 in the agency management system 104. In order to know when a change has happened, the agency management and content management integration system 112 either polls the agency management system 104 on a periodic or nonperiodic (i.e., aperiodic) basis or is notified by the agency management system 104 through the notification services 1116 whenever a change occurs. This is controlled by the notification manager 1118 and the push/pull delta event manager 1120 in the domain layer 1104. For example, in the AMS360® agency management system, a delta event manager exposes a notification port that is a web service from the notification services 1116 that the agency management system 104 can call to report changes. For the Sagitta® agency management system, the Web service is polled at intervals to determine the changes. From this information, the entities are determined and domain objects 1108 are created for the entities. The agency management and content management integration system 112 may include one or both of the capabilities to poll the agency management system 104 or be notified by the agency management system 104 through the notification services 1116 to determine the changes. The domain objects 1108 contain an identifier and all additional data that the user may want mapped to the content management system 102.
The agency integration processor 1120 of the domain transformation and mapping layer 1110 takes the domain objects 1108 and turns them into content management system domain objects 1112 based on the user defined integration jobs. There is often data relationally related to the data received in the domain object 1108 that needs to be mapped to the content management system 102. For example, a customer service representative has a first and last name. The entity may represent the customer service representative as a code (for example, “CSR52” or “!!{circle around ( )}”). In the content management system 102, one may want to see “John Smith”. To do this, the agency management and content management integration system 112 connects to the agency management system 104, gathers the related data, and when an entity is encountered that has a mapping to this secondary data, the agency management and content management integration system 112 looks up the value as configured by the job and substitutes it.
The content management system file services layer 1114 takes those content management domain objects 1112 and creates or updates the actual content structures by connecting into the content management system 102 and making changes. This separation allows the file services layer 1114 to be replaced with a user interface (UI) element 1300 as shown in
The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, schematics, and examples. Insofar as such block diagrams, schematics, and examples contain one or more functions and/or operations, it will be understood by those skilled in the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, the present subject matter may be implemented via Application Specific Integrated Circuits (ASICs). However, those skilled in the art will recognize that the embodiments disclosed herein, in whole or in part, can be equivalently implemented in standard integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more controllers (e.g., microcontrollers) as one or more programs running on one or more processors (e.g., microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of ordinary skill in the art in light of this disclosure.
In addition, those skilled in the art will appreciate that the mechanisms taught herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment applies equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of signal bearing media include, but are not limited to, the following: recordable type media such as floppy disks, hard disk drives, CD ROMs, digital tape, and computer memory.
The various embodiments described above can be combined to provide further embodiments. To the extent that they are not inconsistent with the specific teachings and definitions herein, all of the U.S. patents, U.S. patent application publications, U.S. patent applications, foreign patents, foreign patent applications and non-patent publications referred to in this specification are incorporated herein by reference, in their entirety, including U.S. Provisional Patent Application No. 61/422,090, filed Dec. 10, 2010. Aspects of the embodiments can be modified, if necessary, to employ systems, circuits and concepts of the various patents, applications and publications to provide yet further embodiments.
These and other changes can be made to the embodiments in light of the above-detailed description. In general, in the following claims, the terms used should not be construed to limit the claims to the specific embodiments disclosed in the specification and the claims, but should be construed to include all possible embodiments along with the full scope of equivalents to which such claims are entitled. Accordingly, the claims are not limited by the disclosure.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3970992 | Boothroyd et al. | Jul 1976 | A |
| 4346442 | Musmanno | Aug 1982 | A |
| 4347568 | Giguere et al. | Aug 1982 | A |
| 4359631 | Lockwood et al. | Nov 1982 | A |
| 4383298 | Huff et al. | May 1983 | A |
| 4410940 | Carlson et al. | Oct 1983 | A |
| 4429360 | Hoffman et al. | Jan 1984 | A |
| 4486831 | Wheatley et al. | Dec 1984 | A |
| 4491725 | Pritchard | Jan 1985 | A |
| 4503499 | Mason et al. | Mar 1985 | A |
| 4553206 | Smutek et al. | Nov 1985 | A |
| 4567359 | Lockwood | Jan 1986 | A |
| 4591974 | Dornbush et al. | May 1986 | A |
| 4598367 | DeFrancesco et al. | Jul 1986 | A |
| 4633430 | Cooper | Dec 1986 | A |
| 4642768 | Roberts | Feb 1987 | A |
| 4646229 | Boyle | Feb 1987 | A |
| 4646231 | Green et al. | Feb 1987 | A |
| 4646250 | Childress | Feb 1987 | A |
| 4648037 | Valentino | Mar 1987 | A |
| 4658351 | Teng | Apr 1987 | A |
| 4730252 | Bradshaw | Mar 1988 | A |
| 4794515 | Hornung | Dec 1988 | A |
| 4809170 | Leblang et al. | Feb 1989 | A |
| 4819156 | DeLorme et al. | Apr 1989 | A |
| 4831526 | Luchs et al. | May 1989 | A |
| 4845644 | Anthias et al. | Jul 1989 | A |
| 4860247 | Uchida et al. | Aug 1989 | A |
| 4912628 | Briggs | Mar 1990 | A |
| 4918588 | Barrett et al. | Apr 1990 | A |
| 4928243 | Hodges et al. | May 1990 | A |
| 4928252 | Gabbe et al. | May 1990 | A |
| 4949251 | Griffin et al. | Aug 1990 | A |
| 4951194 | Bradley et al. | Aug 1990 | A |
| 4959769 | Cooper et al. | Sep 1990 | A |
| 4985831 | Dulong et al. | Jan 1991 | A |
| 5072412 | Henderson, Jr. et al. | Dec 1991 | A |
| 5086502 | Malcolm | Feb 1992 | A |
| 5159669 | Trigg et al. | Oct 1992 | A |
| 5161226 | Wainer | Nov 1992 | A |
| 5170480 | Mohan et al. | Dec 1992 | A |
| 5175853 | Kardach et al. | Dec 1992 | A |
| 5201033 | Eagen et al. | Apr 1993 | A |
| 5220665 | Coyle, Jr. et al. | Jun 1993 | A |
| 5241677 | Naganuma et al. | Aug 1993 | A |
| 5257375 | Clark et al. | Oct 1993 | A |
| 5261099 | Bigo et al. | Nov 1993 | A |
| 5263134 | Paal et al. | Nov 1993 | A |
| 5265159 | Kung | Nov 1993 | A |
| 5282052 | Johnson et al. | Jan 1994 | A |
| 5317733 | Murdock | May 1994 | A |
| 5363214 | Johnson | Nov 1994 | A |
| 5448729 | Murdock | Sep 1995 | A |
| 5517644 | Murdock | May 1996 | A |
| 5530861 | Diamant et al. | Jun 1996 | A |
| 5537315 | Mitcham | Jul 1996 | A |
| 5553282 | Parrish et al. | Sep 1996 | A |
| 5583922 | Davis et al. | Dec 1996 | A |
| 5634052 | Morris | May 1997 | A |
| 5812859 | Kamimaki et al. | Sep 1998 | A |
| 5864340 | Bertram et al. | Jan 1999 | A |
| 5880724 | Bertram et al. | Mar 1999 | A |
| 5968125 | Garrick et al. | Oct 1999 | A |
| 6044475 | Chung et al. | Mar 2000 | A |
| 6049877 | White | Apr 2000 | A |
| 6065026 | Cornelia et al. | May 2000 | A |
| 6128653 | del Val et al. | Oct 2000 | A |
| 6199079 | Gupta et al. | Mar 2001 | B1 |
| 6240416 | Immon et al. | May 2001 | B1 |
| 6247020 | Minard | Jun 2001 | B1 |
| 6271846 | Martinez et al. | Aug 2001 | B1 |
| 6272678 | Imachi et al. | Aug 2001 | B1 |
| 6301592 | Aoyama et al. | Oct 2001 | B1 |
| 6362836 | Shaw et al. | Mar 2002 | B1 |
| 6366920 | Hoose et al. | Apr 2002 | B1 |
| 6377948 | Kikuchi et al. | Apr 2002 | B2 |
| 6381744 | Nanos et al. | Apr 2002 | B2 |
| 6385642 | Chlan et al. | May 2002 | B1 |
| 6393407 | Middleton, III et al. | May 2002 | B1 |
| 6393438 | Kathrow et al. | May 2002 | B1 |
| 6405238 | Votipka | Jun 2002 | B1 |
| 6407752 | Harnett | Jun 2002 | B1 |
| 6430575 | Dourish et al. | Aug 2002 | B1 |
| 6437803 | Panasyuk et al. | Aug 2002 | B1 |
| 6463343 | Emens et al. | Oct 2002 | B1 |
| 6490601 | Markus et al. | Dec 2002 | B1 |
| 6510430 | Oberwager et al. | Jan 2003 | B1 |
| 6538667 | Duursma et al. | Mar 2003 | B1 |
| 6546405 | Gupta et al. | Apr 2003 | B2 |
| 6553419 | Ram | Apr 2003 | B1 |
| 6592629 | Cullen et al. | Jul 2003 | B1 |
| 6601047 | Wang et al. | Jul 2003 | B2 |
| 6658167 | Lee et al. | Dec 2003 | B1 |
| 6658659 | Hiller et al. | Dec 2003 | B2 |
| 6671716 | Diedrichsen et al. | Dec 2003 | B1 |
| 6766471 | Meth | Jul 2004 | B2 |
| 6795966 | Lim et al. | Sep 2004 | B1 |
| 6915435 | Merriam | Jul 2005 | B1 |
| 6918082 | Gross et al. | Jul 2005 | B1 |
| 6978376 | Giroux et al. | Dec 2005 | B2 |
| 6993529 | Basko et al. | Jan 2006 | B1 |
| 6993661 | Garfinkel | Jan 2006 | B1 |
| 7000230 | Murray et al. | Feb 2006 | B1 |
| 7010503 | Oliver et al. | Mar 2006 | B1 |
| 7020779 | Sutherland | Mar 2006 | B1 |
| 7028223 | Kolawa et al. | Apr 2006 | B1 |
| 7146495 | Baldwin et al. | Dec 2006 | B2 |
| 7178110 | Fujino | Feb 2007 | B2 |
| 7206998 | Pennell et al. | Apr 2007 | B2 |
| 7266537 | Jacobsen et al. | Sep 2007 | B2 |
| 7296193 | Goode et al. | Nov 2007 | B2 |
| 7299202 | Swanson | Nov 2007 | B2 |
| 7299502 | Schmeling et al. | Nov 2007 | B2 |
| 7318193 | Kim et al. | Jan 2008 | B2 |
| 7321539 | Ballantyne | Jan 2008 | B2 |
| 7322025 | Reddy et al. | Jan 2008 | B2 |
| 7372789 | Kuroda | May 2008 | B2 |
| 7421438 | Turski et al. | Sep 2008 | B2 |
| 7440967 | Chidlovskii | Oct 2008 | B2 |
| 7457878 | Mathiske et al. | Nov 2008 | B1 |
| 7478064 | Nacht | Jan 2009 | B1 |
| 7574048 | Shilman et al. | Aug 2009 | B2 |
| 7584196 | Reimer et al. | Sep 2009 | B2 |
| 7587327 | Jacobs et al. | Sep 2009 | B2 |
| 7593532 | Plotkin et al. | Sep 2009 | B2 |
| 7624189 | Bucher | Nov 2009 | B2 |
| 7636898 | Takahashi | Dec 2009 | B2 |
| 7650320 | Nakano | Jan 2010 | B2 |
| 7676792 | Irie et al. | Mar 2010 | B2 |
| 7698230 | Brown et al. | Apr 2010 | B1 |
| 7711703 | Smolen | May 2010 | B2 |
| 7725456 | Augustine | May 2010 | B2 |
| 7757168 | Shanahan et al. | Jul 2010 | B1 |
| 7757239 | Beck | Jul 2010 | B2 |
| 7814078 | Forman et al. | Oct 2010 | B1 |
| 7886046 | Zeitoun et al. | Feb 2011 | B1 |
| 7949711 | Chang et al. | May 2011 | B2 |
| 8112394 | Shringi et al. | Feb 2012 | B2 |
| 8146058 | Sarkar et al. | Mar 2012 | B2 |
| 8166388 | Gounares et al. | Apr 2012 | B2 |
| 8266592 | Beto et al. | Sep 2012 | B2 |
| 8285685 | Prahlad | Oct 2012 | B2 |
| 8370403 | Matsuki | Feb 2013 | B2 |
| 8375126 | Kriewall | Feb 2013 | B2 |
| 8438045 | Erlanger | May 2013 | B2 |
| 8489921 | Varadarajan et al. | Jul 2013 | B2 |
| 8650043 | Phillips | Feb 2014 | B1 |
| 8667267 | Garcia et al. | Mar 2014 | B1 |
| 8825626 | Wallace et al. | Sep 2014 | B1 |
| 20010027420 | Boublik et al. | Oct 2001 | A1 |
| 20010032092 | Calver | Oct 2001 | A1 |
| 20020065879 | Ambrose et al. | May 2002 | A1 |
| 20020087602 | Masuda et al. | Jul 2002 | A1 |
| 20020120474 | Hele et al. | Aug 2002 | A1 |
| 20020120776 | Eggebraaten et al. | Aug 2002 | A1 |
| 20020138476 | Suwa et al. | Sep 2002 | A1 |
| 20020194033 | Huff | Dec 2002 | A1 |
| 20020194578 | Irie et al. | Dec 2002 | A1 |
| 20020198743 | Ariathurai et al. | Dec 2002 | A1 |
| 20030101200 | Koyama et al. | May 2003 | A1 |
| 20030105813 | Mizutani | Jun 2003 | A1 |
| 20030144887 | Debber | Jul 2003 | A1 |
| 20030191938 | Woods et al. | Oct 2003 | A1 |
| 20030212610 | Duffy et al. | Nov 2003 | A1 |
| 20040039757 | McClure | Feb 2004 | A1 |
| 20040059740 | Hanakawa et al. | Mar 2004 | A1 |
| 20040128182 | Pepoon et al. | Jul 2004 | A1 |
| 20040133606 | Miloushev | Jul 2004 | A1 |
| 20040186750 | Surbey et al. | Sep 2004 | A1 |
| 20040193455 | Kellington | Sep 2004 | A1 |
| 20040194026 | Barrus et al. | Sep 2004 | A1 |
| 20040220975 | Carpentier et al. | Nov 2004 | A1 |
| 20040230903 | Elza et al. | Nov 2004 | A1 |
| 20040236614 | Keith | Nov 2004 | A1 |
| 20040243969 | Kamery et al. | Dec 2004 | A1 |
| 20040255275 | Czerwonka | Dec 2004 | A1 |
| 20040267578 | Pearson | Dec 2004 | A1 |
| 20050024387 | Ratnakar et al. | Feb 2005 | A1 |
| 20050033988 | Chandrashekhar et al. | Feb 2005 | A1 |
| 20050071203 | Maus | Mar 2005 | A1 |
| 20050080804 | Bradshaw, Jr. et al. | Apr 2005 | A1 |
| 20050097061 | Shapiro et al. | May 2005 | A1 |
| 20050137928 | Scholl et al. | Jun 2005 | A1 |
| 20050144195 | Hesselink et al. | Jun 2005 | A1 |
| 20050233287 | Bulatov et al. | Oct 2005 | A1 |
| 20060047540 | Hutten et al. | Mar 2006 | A1 |
| 20060059418 | Elkady | Mar 2006 | A1 |
| 20060100912 | Kumar et al. | May 2006 | A1 |
| 20060184452 | Barnes et al. | Aug 2006 | A1 |
| 20060195491 | Nieland et al. | Aug 2006 | A1 |
| 20060195494 | Dietrich | Aug 2006 | A1 |
| 20060259524 | Horton | Nov 2006 | A1 |
| 20070006222 | Maier et al. | Jan 2007 | A1 |
| 20070016465 | Schaad | Jan 2007 | A1 |
| 20070016829 | Subramanian et al. | Jan 2007 | A1 |
| 20070061154 | Markvoort et al. | Mar 2007 | A1 |
| 20070067772 | Bustamante | Mar 2007 | A1 |
| 20070130346 | Xie et al. | Jun 2007 | A1 |
| 20070146823 | Borchers et al. | Jun 2007 | A1 |
| 20070160070 | Buchhop et al. | Jul 2007 | A1 |
| 20070186066 | Desai et al. | Aug 2007 | A1 |
| 20070186214 | Morgan | Aug 2007 | A1 |
| 20070233880 | Nieh et al. | Oct 2007 | A1 |
| 20070244921 | Blair | Oct 2007 | A1 |
| 20070244935 | Cherkasov | Oct 2007 | A1 |
| 20070245230 | Cherkasov | Oct 2007 | A1 |
| 20070282927 | Polouetkov | Dec 2007 | A1 |
| 20080002830 | Cherkasov et al. | Jan 2008 | A1 |
| 20080010542 | Yamamoto et al. | Jan 2008 | A1 |
| 20080040690 | Sakai | Feb 2008 | A1 |
| 20080086499 | Wefers et al. | Apr 2008 | A1 |
| 20080091846 | Dang | Apr 2008 | A1 |
| 20080120602 | Comstock et al. | May 2008 | A1 |
| 20080243897 | Petri | Oct 2008 | A1 |
| 20090007077 | Musuvathi et al. | Jan 2009 | A1 |
| 20090055242 | Rewari et al. | Feb 2009 | A1 |
| 20090119133 | Yeransian et al. | May 2009 | A1 |
| 20090199160 | Vaitheeswaran et al. | Aug 2009 | A1 |
| 20090271779 | Clark | Oct 2009 | A1 |
| 20090287746 | Brown | Nov 2009 | A1 |
| 20090328171 | Bayus et al. | Dec 2009 | A1 |
| 20100060926 | Smith et al. | Mar 2010 | A1 |
| 20100064230 | Klawitter et al. | Mar 2010 | A1 |
| 20100064258 | Gorczowski et al. | Mar 2010 | A1 |
| 20100064375 | Gorczowski et al. | Mar 2010 | A1 |
| 20100076993 | Klawitter et al. | Mar 2010 | A1 |
| 20100091317 | Williams et al. | Apr 2010 | A1 |
| 20100161616 | Mitchell | Jun 2010 | A1 |
| 20100179883 | Devolites | Jul 2010 | A1 |
| 20100191785 | Serlet et al. | Jul 2010 | A1 |
| 20100199263 | Clee et al. | Aug 2010 | A1 |
| 20100235392 | McCreight et al. | Sep 2010 | A1 |
| 20110021250 | Ickman et al. | Jan 2011 | A1 |
| 20110088014 | Becker et al. | Apr 2011 | A1 |
| 20110119574 | Rogers et al. | May 2011 | A1 |
| 20110145037 | Domashchenko et al. | Jun 2011 | A1 |
| 20110153560 | Bryant et al. | Jun 2011 | A1 |
| 20110161375 | Tedder et al. | Jun 2011 | A1 |
| 20110173153 | Domashchenko et al. | Jul 2011 | A1 |
| 20110184689 | Awedikian et al. | Jul 2011 | A1 |
| 20110184766 | Virdhagriswaran | Jul 2011 | A1 |
| 20110270975 | Troup | Nov 2011 | A1 |
| 20110276875 | McCabe et al. | Nov 2011 | A1 |
| 20110283177 | Gates et al. | Nov 2011 | A1 |
| 20120222014 | Peretz et al. | Aug 2012 | A1 |
| 20120232934 | Zhang et al. | Sep 2012 | A1 |
| 20120271657 | Anderson et al. | Oct 2012 | A1 |
| 20130024418 | Sitrick et al. | Jan 2013 | A1 |
| 20130066901 | Marcelais et al. | Mar 2013 | A1 |
| 20130073942 | Cherkasov | Mar 2013 | A1 |
| 20130080760 | Li et al. | Mar 2013 | A1 |
| 20130152047 | Moorthi et al. | Jun 2013 | A1 |
| 20130290786 | Artzi et al. | Oct 2013 | A1 |
| 20140040867 | Wefers et al. | Feb 2014 | A1 |
| 20140358938 | Billmaier et al. | Dec 2014 | A1 |
| 20150100552 | Malis et al. | Apr 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2646167 | Oct 2007 | CA |
| 2649441 | Oct 2007 | CA |
| 2761405 | Jun 2012 | CA |
| 2733857 | Sep 2012 | CA |
| 2737734 | Oct 2012 | CA |
| 0585192 | Mar 1994 | EP |
| 60-41138 | Mar 1985 | JP |
| 3-282941 | Dec 1991 | JP |
| 4-373026 | Dec 1992 | JP |
| 11-143567 | May 1999 | JP |
| 11-296452 | Oct 1999 | JP |
| 0195093 | Dec 2001 | WO |
| 2004088543 | Oct 2004 | WO |
| 2007120771 | Oct 2007 | WO |
| 2007120772 | Oct 2007 | WO |
| 2007120773 | Oct 2007 | WO |
| 2007120774 | Oct 2007 | WO |
| 2008049871 | May 2008 | WO |
| 2010030675 | Mar 2010 | WO |
| 2010030676 | Mar 2010 | WO |
| 2010030677 | Mar 2010 | WO |
| 2010030678 | Mar 2010 | WO |
| 2010030679 | Mar 2010 | WO |
| 2010030680 | Mar 2010 | WO |
| 2013072764 | May 2013 | WO |
| Entry |
|---|
| “Update insurance template according to changes to policy” retrieved from URL=https://www.google.com/?tbm=pts on Sep. 24, 2012, 2 pages. |
| Anderson et al., “Overlaying Images in Automated Insurance Policy Form Generation,” Amendment filed Jan. 11, 2013 for U.S. Appl. No. 13/089,886, 15 pages. |
| Anderson et al., “Overlaying Images in Automated Insurance Policy Form Generation,” Office Action mailed Oct. 11, 2012 for U.S. Appl. No. 13/089,886, 9 pages. |
| Zhang et al., “Agency Management System and Content Management System Integration,” U.S. Appl. No. 61/422,090, filed Dec. 10, 2010, 54 pages. |
| Zhang et al., “Automated Insurance Policy Form Generation and Completion,” Amendment filed Oct. 2, 2012, for U.S. Appl. No. 13/046,501, 18 pages. |
| Zhang et al., “Automated Insurance Policy Form Generation and Completion,” Office Action mailed Jun. 20, 2012 for U.S. Appl. No. 13/046,501, 22 pages. |
| “Adobe Introduces Adobe Acrobat 3.0 Software,” PR Newswire, Jun. 3, 1996, 3 pages. |
| “CoreData Inc. Announces Technology and Marketing Agreement with MobileStar Network Corp.,” Business Wire, Aug. 26, 1998, 2 pages. |
| “CoreData Offers E-mail Connectivity for RemoteWorx,” Newsbytes News Network, Sep. 18, 1998, 1 page. |
| “Free Sticky Notes software—Sticky Notes program MoRUN.net Sticker Lite,” Jan. 11, 2006, retrieved from http://web.archive.org/web/20060112031435/http://www.sticky-notes.net/free/stickynotes.html, on Oct. 10, 2013, 2 pages. |
| “Internet lifts servers to 64 bits,” Electronic Engineering Times, Dec. 23, 1996, 3 pages. |
| “NotesPlusPlus,” Feb. 25, 2006, retrieved from http://web.archive.org/web/20060225020405/http://www.sharewareconnection.com/notesplusplus.htm, on Oct. 10, 2013, 2 pages. |
| “SPSS Unveils Aggressive Development Plans: 1999 Product Releases Will Focus on Scalability and Deployment Solutions for the Enterprise,” Business Wire, Feb. 18, 1999, 3 pages. |
| “Windows XP: The Complete Reference: Using Files and Folders,” Apr. 28, 2004, retrieved from http://web.archive.org/web/20040428222156/http://delltech.150m.com/XP/files/7.htm, on Oct. 10, 2013, 4 pages. |
| Extended European Search Report, dated Jul. 9, 2012, for Application No. 07755347.7, 8 pages. |
| Extended European Search Report, dated Jun. 14, 2012, for Application No. 07755348.5, 8 pages. |
| Extended European Search Report, dated Jun. 19, 2012, for Application No. 07755349.3, 8 pages. |
| Extended European Search Report, dated Jun. 14, 2012, for Application No. 07755350.1, 9 pages. |
| Fogel, “Open Source Development With CVS,” Copyright 1999, 2000, retrieved from http://web.archive.org/web/20000815211634/http://cvsbook.red-bean.com/cvsbook.ps, on Oct. 10, 2013, 218 pages. |
| Gadia, “A Homogeneous Relational Model and Query Languages for Temporal Databases,” ACM Transactions on Database Systems 13(4):418-448, Dec. 1988. |
| Gage, “Sun's ‘objective’ is to populate Java networks,” Computer Reseller News, Apr. 15, 1996, p. 69, 2 pages. |
| International Search Report and Written Opinion, mailed Aug. 5, 2008, for PCT/US2007/009040, 7 pages. |
| International Search Report and Written Opinion, mailed Jul. 18, 2008, for PCT/US2007/009041, 8 pages. |
| International Search Report and Written Opinion, mailed Jul. 14, 2008, for PCT/US2007/009042, 6 pages. |
| International Search Report and Written Opinion, mailed Jul. 18, 2008, for PCT/US2007/009043, 9 pages. |
| Murdock, “Office Automation System for Data Base Management and Forms Generation,” U.S. Appl. No. 07/471,290, filed Jan. 26, 1990, 163 pages. |
| Snodgrass et al., “Temporal Databases,” IEEE Computer, Sep. 1986, pp. 35-42. |
| “AMS Real-Time Getting Started Guide,” AMS Services, Vertafore, Inc., 16 pages, 2008. |
| “VERITAS Replication Exec version 3.1 for Windows,” Administrator's Guide, pp. i-20, 49-68, and 119-160, Dec. 2004. |
| Announcement, “Coming Attraction, AMS Invites you to a Special Sneak Preview,” AMS Services, 1 page, Aug. 1, 2008. |
| Brochure, “AMS 360—Business Growth. Productivity. Proven Technology.,” Vertafore, Inc., 8 pages, 2008. |
| Brown et al., “Agency Management System and Content Management System Integration,” U.S. Appl. No. 61/422,090, filed Dec. 10, 2010, 54 pages. |
| Bryant et al., “Apparatus, Method and Article to Manage Electronic or Digital Documents in a Networked Enviornment,” Amendment filed May 11, 2012, in U.S. Appl. No. 12/641,843, 24 pages. |
| Bryant et al., “Apparatus, Method and Article to Manage Electronic or Digital Documents in a Networked Enviornment,” Amendment filed Sep. 19, 2012, in U.S. Appl. No. 12/641,843, 23 pages. |
| Bryant et al., “Apparatus, Method and Article to Manage Electronic or Digital Documents in a Networked Enviornment,” Final Rejection mailed Jul. 19, 2012, in U.S. Appl. No. 12/641,843, 17 pages. |
| Bryant et al., “Apparatus, Method and Article to Manage Electronic or Digital Documents in a Networked Enviornment,” Non-Final Office Action mailed Feb. 14, 2012, in U.S. Appl. No. 12/641,843, 15 pages. |
| Corriveau et al., “AMS Portal Server: Bridging the Gap Between Web Presentation and the Back Office,” White Paper, AMS Services, 13 pages, 2008. |
| Snyder et al., “Apparatus, Method and Article to Automate and Manage Communications in a Networked Enviornment,” U.S. Appl. No. 13/451,139, filed Apr. 19, 2012, 70 pages. |
| Snyder et al., “Apparatus, Method and Article to Automate and Manage Communications to Multiple Entities in a Networked Enviornment,” U.S. Appl. No. 13/451,168, filed Apr. 19,2012, 82 pages. |
| Snyder et al., “Apparatus, Method and Article to Automate and Manage Electronic Documents in a Networked Enviornment,” Office Action mailed Feb. 5, 2013, for U.S. Appl. No. 13/451,136, 22 pages. |
| Snyder et al., “Apparatus, Method and Article to Automate and Manage Electronic Documents in a Networked Enviornment,” U.S. Appl. No. 13/451,136, filed Apr. 19, 2012, 80 pages. |
| Snyder et al., “Apparatus, Method and Srticle to Provide an Insurance Workflow Management System,” U.S. Appl. No. 13/598,297, filed Aug. 29, 2012, 86 pages. |
| Tedder et al., “Systems, Methods and Articles for Template Based Generation of Markup Documents to Access Back Office Systems,” Amendment filed May 3, 2012, in U.S. Appl. No. 12/647,235, 16 pages. |
| Tedder et al., “Systems, Methods and Articles for Template Based Generation of Markup Documents to Access Back Office Systems,” Amendment filed Sep. 10, 2012, in U.S. Appl. No. 12/647,235, 21 pages. |
| Tedder et al., “Systems, Methods and Articles for Template Based Generation of Markup Documents to Access Back Office Systems,” Final Office Action mailed Jul. 10, 2012, in U.S. Appl. No. 12/647,235, 20 pages. |
| Tedder et al., “Systems, Methods and Articles for Template Based Generation of Markup Documents to Access Back Office Systems,” Non-Final Office Action mailed Feb. 3, 2012, in U.S. Appl. No. 12/647,235, 20 pages. |
| Alvarez, “Bit Level Comparator Systems and Methods,” U.S. Appl. No. 14/101,905, filed Dec. 10, 2013, 57 pages. |
| Sinyagin et al., “Integration Testing Method and System for Web Services,” U.S. Appl. No. 14/104,749, filed Dec. 12, 2013, 63 pages. |
| Batrouni et al., “Method and System of Assessing Risk Associated With Users Based at Least in Part on Online Presence of the User,” U.S. Appl. No. 14/630,509, filed Feb. 24, 2015, 71 pages. |
| Srivastava et al., “Automated Software Testing Using Metahurestic Technique Based on an Ant Colony Optimization,” International Symposium on Electronic System Design, Bhubaneswar, Dec. 20-22, 2010, 7 pages. |
| Hegarty et al., “Ambient Intelligent Mobile Persistent Browsing Experience (AIMPBE): Seamless Session Browsing Experiences across Heterogeneous Devices using Sensors,” Proceedings of the 9th Annual Post-Graduate Symposium on the Convergence of Telecommunications, Networking and Broadcasting (PGNET 2008), Liverpool, UK, Jun. 2008, 6 pages. |
| McDowell, “Performance Testing of Web Application Components Using Image Differentiation,” U.S. Appl. No. 14/926,465, filed Oct. 29, 2015, 44 pages. |
| Song et al., “Browser Session Preservation and Migration,” 2002, 2 pages. |
| Song et al., “Browser State Repository Service,” Lecture Notes in Computer Science 2414—Pervasive Computing, pp. 253-266, 2002. |
| Number | Date | Country | |
|---|---|---|---|
| 20120150919 A1 | Jun 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61422090 | Dec 2010 | US |
