WO2002025470A1 - Procede et systeme permettant l'automatisation des processus d'assurance - Google Patents

Procede et systeme permettant l'automatisation des processus d'assurance Download PDF

Info

Publication number
WO2002025470A1
WO2002025470A1 PCT/US2001/029767 US0129767W WO0225470A1 WO 2002025470 A1 WO2002025470 A1 WO 2002025470A1 US 0129767 W US0129767 W US 0129767W WO 0225470 A1 WO0225470 A1 WO 0225470A1
Authority
WO
WIPO (PCT)
Prior art keywords
computer
insurance
aided method
user
web
Prior art date
Application number
PCT/US2001/029767
Other languages
English (en)
Inventor
Gordon Surbey
Timothy Wright
Anthony Siggers
Howard Green
Adam Sandler
Original Assignee
Riskclick, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Riskclick, Inc. filed Critical Riskclick, Inc.
Priority to AU2001293000A priority Critical patent/AU2001293000A1/en
Priority to EP01973421A priority patent/EP1330731A4/fr
Priority to CA002423011A priority patent/CA2423011A1/fr
Publication of WO2002025470A1 publication Critical patent/WO2002025470A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions

Definitions

  • the present invention relates to the field of computer software specifically designed for risk management and insurance, and, more particularly, to a method and system for web-enabling the risk management and insurance process.
  • FIG. 1 is a flowchart of an embodiment of a method 100 of the present invention
  • FIG. 2 is a block diagram of an embodiment of a system 200 of the present invention.
  • FIG. 3 is a block diagram of an embodiment of an information device 300 of the present invention.
  • FIG. 4 is a flowchart of an embodiment of a method 400 of the present invention.
  • FIG. 5 is a flowchart of an embodiment of a graphical user interface 500 of the present invention.
  • FIG. 6 is a flowchart of an embodiment of a method 600 of the present invention.
  • FIG. 7 is a flowchart of an embodiment of a method 700 of the present invention.
  • FIG. 8 is a block diagram of an embodiment of a system 800 of the present invention
  • FIG. 9 is a block diagram of an embodiment of a software architecture 900 of the present invention.
  • the industry has enormous growth opportunities as the demand for risk management spreads from traditional exposures like fire, flood, and public liability to hedging financial and other specialized risks.
  • the industry is predominantly populated by four major types of participants: clients who transfer risk to insurers or sometimes manage their own risks through special purpose vehicles; insurers who accept risk in return for a premium; brokers who work as intermediaries on behalf of clients to provide risk management advice, structure transactions, and place those transactions in the market; and other risk solution providers, like accounting firms and consultants, who generally provide advice only.
  • brokers and insurers Although most brokers and insurers have "back office” computer systems that keep accounting, contract, and statistical records, there is virtually no “front end” technology to support interactions with clients, structuring the transaction, and/or placing the transaction into the market. For example, of the top global 200 brokers and insurers, only a handful have technology that systematically manages documents and interactions.
  • a business model associated with embodiments of the present invention can provide software that is tailored to the specific needs of the risk management and insurance industry to harness the efficiencies of e-business without the cost, risk, and delays of building proprietary systems.
  • the software can wrap around existing systems that have been widely deployed in the industry such as e-mail and desktop office software.
  • embodiments of the present invention can provide collaborative e- business technologies that enable more efficient and deeper customization. Such technologies can work by enhancing the traditional skills of the industry as opposed to replacing them. These technologies also can leverage the talents of key people by substantially freeing them of paperwork and can enhance the service provided to clients by promoting them from spectators to full participants.
  • Janet Smith is the risk manager of Global Inc. a rapidly growing multinational company operating in 64 countries. Janet felt that her previous insurance broker had treated her as a bystander. Although she had access to their extranet for accounting and some policy detail information, she could only get intermittent status reports on key assignments like renewals and major claims. She looked for a new broker who would make her and her team a part of the process. Vision Company was one of the first brokering firms to adopt collaborative e-business and this was a important reason they won the Global account just before the July renewal of the global property program.
  • Vision had made a big push to integrate all its files and records into the document management system that was one component of the collaborative platform.
  • Andy Stewart, Vision's account executive had set-up folders in the system mirroring the paper files he would have kept tucked away in the rows of filing cabinets that previously monopolized his floor space.
  • Andy had selected an account team and had appointed someone in each of the Vision offices to be involved in servicing the local needs of Global.
  • Andy set up a "global property renewal" folder and started uploading the documents and information that would be needed to negotiate the renewal.
  • Unlike e-mail where dozens of different versions are created, here only one version of each file is available, which everyone on the team has access to and works with collaboratively.
  • Andy now begins to assemble an electronic submission using the completed exposure templates, draft manuscript wording, and other relevant documents. He uses the tools provided by the system to select potential insurers. Andy and Janet plan to visit potential underwriters and negotiate lead positions face-to-face.
  • the electronic submission is supported by an audit trail that keeps track of exactly what documents, document versions, and messages have been exchanged with each of the potentially dozens of insurers that will be approached before this transaction is completed. This audit trail is added to potentially tens of thousands of documents and messages and Janet considers this reliable audit trail a crucial feature in replacing the certainty of paper.
  • Andy has provided Janet with access to a placement status report so she and her team can see every iteration and/or up-to-the- minute status at any time. Whenever an insurer responds with a quote or a question, this status report is updated. Janet doesn't need to see iteration in the process, she leaves this to her broker, and has agreed with Andy beforehand the level of detail required.
  • Andy and Janet can see the detail simultaneously and can discuss the issues with the full file in front of them even though Janet is traveling extensively and logging-in remotely. Andy is able to bind the insurers on-line and post a copy of the finally agreed wording in the folder.
  • Andy works with the lead insurer to create a new summary of coverages and incident reporting procedures that is posted in the client folder and instantly made available to all Global's representatives. Andy now adds the insurer's local representatives into the community so that everyone involved in the risk management (more than 400 people) can share the same information, communicate, and interact. In the background, the system automatically keeps a complete record of all of this interaction.
  • This exemplary story illustrates the opportunity to modernize risk services and solutions delivery by keeping customization yet adding collaboration, inclusion, and the efficiency of paperless processes.
  • Embodiments of the present invention can apply a new approach for accessing technology called the Application Service Provider (ASP) model and/or the Central Host model.
  • ASP Application Service Provider
  • One idea behind this technology is that instead of hundreds of participants in an industry each building their own proprietary software at great risk and expense the central hoster will develop the software once and make it available to anyone in the industry based on a rental or (user subscription) model.
  • This approach can have huge advantages for an industry like risk management and insurance. First, and most important, it can promote inter-operability. If everyone uses that same basic infrastructure, then the holy grail of inter-operability can be achieved. Second, it can remove risk and dramatically shorten timeframes. This means that things can move much more quickly.
  • centrally-hosted, collaborative e-business holds the potential for breakthrough improvements in client relationship management, thereby enabling brokers and insurers for the first time to be highly differentiated based upon their client service delivery.
  • embodiments of the present invention can provide a number of advantageous functionalities.
  • Embodiments of the present invention can include software that incorporates an electronic folder structure that is customized to the risk management and insurance process.
  • a folder structure can be uniquely rendered to each user, thereby providing an always-current view of the folders and folder contents that the user has either created or been invited to access through the collaboration feature.
  • One way of visualizing this is an electronic filing cabinet that can provide the user with instant access to any file they have created or are entitled to access. These files can be accessed anywhere/anytime through an Internet connection.
  • the folder structure can have these features:
  • the folder hierarchy can be determined by the user's role. For example, if the user is a broker, the root folders can be associated with clients, as in “client A”, “client B”, and “client C”. If the user is a client, then the root folder can be associated with one or more brokers and/or insurers as in “broker A”, “insurer B”, and/or "broker C”.
  • the folder hierarchy can include standard sub-folders determined by the user's role. This feature can place a set of standard sub-folders under each folder, and can work with other functionalities to ensure that documents and interactions used in certain parts of the process are systematically filed in the correct standard folder.
  • One purpose of this feature is to ensure that all of the documents and messages associated with a particular transaction can always be re-constituted by finding and opening a specific standard sub- folder. It also ensures that everybody in a team stores their documents and information in a consistent manner.
  • Embodiments of the present invention can include software that allows a user to initiate collaboration with any number of other users both within their own organization or externally. Once the user sets up this "virtual community", the collaborators can share documents, interact, and structure and manage transactions, subject to access rules set by the user.
  • Collaborations can be initiated at the level of a folder (for example, a client folder) or at any sub-level down to a specific document.
  • explorer By clicking on the folder ("explorer") bar, the user can select the appropriate folder and folder level, and then can utilize the collaboration dialog tool to select collaborators.
  • the software can enable the user to set "access rights" with respect to each collaborator. Those access rights can identify, specify, and/or determine whether the collaborator can "read only", “edit”, and/or "delete” documents.
  • the software can provide a verification screen. If the user proceeds, the software can automatically send an "invitation" to each of the selected collaborators.
  • This invitation can be an e- mail message that provides the URL (web address) of the unique workspace that the software has rendered for each collaborator, the workspace containing only those folders to which that collaborator has been granted access.
  • all a collaborator needs is a web browser (e.g., Microsoft's Internet Explorer 5) and Internet access.
  • the e-mail message can point the collaborator to a dialogue where they can set their own unique password to access the workspace. All collaborators can be notified every time there is an addition to a folder or a change to a document in a folder to which they have access.
  • Embodiments of the present invention can include software that systematically keeps track of every collaboration, document, message, and/or interaction, thereby providing a complete and reliable "memory".
  • a complete audit trail can be permanently maintained and can be called-up at any time.
  • "memory" is corporate, that is to say, it keeps track of every document by every member of a team and also keeps track of every interaction between every member of the team and/or third parties. Team members can be located anywhere in the world.
  • the audit trail can be achieved in five ways:
  • the software can keep track of every version of every document and can provide a dialog box stating information about each version, such as the author and date created.
  • the software can keep track of every collaborator and their access rights.
  • the software can enable the user to see if and when a collaborator has opened a specific message or document.
  • a dialog box can let the user verify the time and date a document or message was opened by a collaborator.
  • Message threads can provide a complete view of every interaction between collaborators in a given community.
  • the collaboration "owner" can grant access rights that enable a third party to view the dynamic message thread. For example, a client may be granted access to view a thread developing between a broker and several insurers negotiating a risk placement.
  • Embodiments of the present invention can include software that incorporates templates that can be used to enter structured information or data, and enable that information to be re-used by collaborators and/or counterparties (such as insurers) without re-keying.
  • the templates can use a technology that can tag data items so they can be recognized by other computers, such as XML. For example, the information contained in the data field "name of the insured" could be tagged so that any computer using XML rules would recognize this information as the insured's name.
  • XML tagged templates can enable structured information to be entered once (by, for example, the client) and "streamed" to all of the parties that need use of that information, without re- keying.
  • Templates can also advantageously provide flexibility because users can create their own templates depending on their needs. Templates can be created, for example, in a spreadsheet product, such as Excel, provided by Microsoft Corporation of Redmond, Washington.
  • the software can incorporate standard templates tagged using industry-wide standards, such as for example, those developed by ACORD (an industry standards body). These standard templates can initially embody the ACORD risk exposure standards. For example, if a user is providing a schedule of properties, property values, and business interruption values, then a standard template could be used to provide this "locations & values" schedule.
  • ACORD an industry standards body
  • a template user can publish the information entered into the template to the community of collaborators and track who enters additional information into the template, who modifies information in the template, and when those events occur.
  • Functionality #5 Process and Workflow Management
  • Embodiments of the present invention can include software that provides a user with a step-by-step process to structure transactions, such as a quote requests or claims notifications.
  • the software can use structured messages to organize the process into a series of iterative steps.
  • a "quote request" dialog can first prompt a user to select the appropriate client folder and the standard "negotiations" sub-folder.
  • a dialog screen then can prompt the user to select the insurers to receive the quote request.
  • the user can either search for appropriate insurers in the directory or can select an underwriter by entering their e-mail address.
  • the dialog then can prompt the user to create an electronic submission by assembling documents such as exposure templates, word documents, and/or spreadsheets.
  • documents such as exposure templates, word documents, and/or spreadsheets.
  • the user can access these documents from any source within their computer, their network, or the web, and can upload them into the submission.
  • the user also can add notes and instructions to the insurers.
  • the software can provide a verification screen. If the user accepts the contents of the submission, then an e-mail can automatically be sent to each of the chosen underwriters inviting them to access the electronic submission and supporting messages. Thereafter, each underwriter can access a uniquely rendered workspace, as explained in functionality #2.
  • Embodiments of the present invention can include software that provides a screen whereby all transactions being worked upon by the user are rendered as dynamically updated line items showing, for example, the client name, type of policy, and renewal date.
  • Each line item can have a flag that shows the current status of the transaction, for example "sent for quote", "quoted", and/or "declined".
  • the user can drill down to the thread of messages or documents associated with that item, such as for example, to the message or document sent by the underwriter providing details of the quote.
  • the user can set preferences for the order and structure of the information displayed within the status screen.
  • embodiments of the present invention can provide one or more software packages designed to make the risk management and insurance process more efficient by web-enabling and/or enhancing antiquated paper processes, and/or by facilitating web-based collaboration between the parties.
  • the software can be designed for use by any party to the risk management and insurance process, including clients, brokers, insurers, and/or other risk solution providers. As use of the software becomes widespread, the market can also achieve the goal of inter-operability.
  • the software can incorporate functionality for the straight-through-processing of transactions using, for example, XML tagging.
  • embodiments of the present invention can provide a computer-aided method for managing a web-enabled and/or computerized collaborative insurance process.
  • the method can include, for each of a plurality of insurance transactions, for each of a plurality of users, automatically creating a plurality of standardized computer document folders consistent with a role of the user in the collaborative insurance process, automatically hierarchically organizing the plurality of standardized computer document folders into a folder structure, and providing the user with access via a networked computer to the user's hierarchically organized folder structure and plurality of standardized computer document folders.
  • the method can also include, for each of the insurance transactions, providing an insurance data entry template having a plurality of fields that meet an insurance industry standard for the computerized submission of exposure information, and receiving the insurance data entry template with data in each of the plurality of fields.
  • the method can further include, for each of the insurance transactions, automatically creating a computer-based insurance quotation request based on the insurance data entry template and having a message and a document containing insurance requirements and exposure information, simultaneously sending the computer-based insurance quotation request to a plurality of insurers, and representing the insurance transaction as a hyperlinked line item on a computer display.
  • Fig. 1 is a flowchart of an exemplary embodiment of an exemplary method 100 of the present invention.
  • method 100 can include the initiation of collaboration, which can be performed, for example, by a broker.
  • the broker can be the initiator
  • collaborators can include the client, and the client's advisor (such as an attorney).
  • the initiator can identify, specify, indicate, and/or communicate the other collaborators.
  • a folder structure and security settings can be automatically created, as described above under Functionalities #1 and #2.
  • the folder structure is created on-the-fly, on-demand, and/or as needed, to reflect the then-current folder hierarchy and the viewer's role.
  • documents can be collaboratively prepared.
  • an electronic submission can be assembled and electronically posted to selected insurers.
  • Actions 1030 and/or 1040 can be performed as described above under Functionalities #4 and/or #5.
  • a user can select a client folder and can specify insurers to whom a submission will be posted.
  • the user can select the insurer from a directory of insurers, or can enter an e-mail address of the insurer.
  • an embodiment of a system of the present invention can prompt the user to create a submission by uploading and/or attaching documents to an "request for quotation" message.
  • the user can provide a veneer of structured information, such as when quotes are due, to whom they should be provided, etc.
  • the system can then prompt the user to verify that the entered structured information is correct.
  • the system can then provide the submission to the selected insurers.
  • the submission can be provided by sending an e-mail message to the insurers, the e-mail message including an embedded URL link that points the insurer to the submission.
  • the submission can be attached to the e-mail message.
  • At action 1050 at least some of the insurers can prepare and electronically post a quote.
  • the broker, client, and/or client advisor can collaboratively compare the quotes and/or select a quoted policy.
  • the client, client advisor, and/or broker can post a claim.
  • the client, client advisor, broker, and/or insurer can collaboratively review and/or resolve the claim.
  • actions 1010 through 1080 can be enhanced by Functionalities #3 and/or #6.
  • Fig. 2 provides a block diagram of an exemplary embodiment of an exemplary system 200 of the present invention.
  • system 200 can be viewed as illustrative, and should not be construed to limit the implementation of method 100.
  • a broker information device 2100 can be used by a broker to communicate regarding one or more insurance transactions with various other information devices (e.g., client information device 2200, insurer information device 2300, etc.) and/or with one or more data servers 2700 and/or web/application servers 2800.
  • Broker information device 2100 can also be used to collaborate with others, manage databases, query databases, enter transaction information, prepare an electronic submission, post the electronic submission, review quotes, select a policy, post a claim, review a claim, and/or resolve a claim, etc.
  • Broker information device 2100 can be connected to network 2900. Also connected to network 2900 can be various additional information devices 2200-2500, which can be used, for example, to collaborate with others, host databases, manage databases, query databases, enter transaction information, prepare an electronic submission, post the electronic submission, review the electronic submission, prepare a quote, post a quote, review quotes, select a policy, post a claim, review a claim, and/or resolve a claim, etc.
  • an insurer information device can be used by an insurer to collaborate with others, host databases, manage databases, review an electronic submission, prepare a quote, post the quote, review a claim, and/or resolve a claim, etc.
  • Web/application server 2700 and/or data server 2800 also can be connected to network 2900 and can be used to host one or more databases 2750, 2850, serve files, serve e-mail, etc.
  • Web/application server 2700 and/or data server 2800 can be one or more computing devices of any sort.
  • any of information devices 2100-2500 can be used to host one or more databases (not shown).
  • Network 2900 can electronically link physically distant information devices 2100-2500, web/application server 2700, and/or data server 2800, so that information can be transmitted and/or exchanged there between.
  • Network 2900 can have any architecture, including a direct connection, a local area network, a wide area network such as the public switched telephone network and/or the Internet, an extranet, and/or a combination thereof.
  • Network 2900 can be a packet-switched, a circuit-switched, a connectionless, or connection-oriented network or interconnected networks, or any combination thereof.
  • Network 2900 can be oriented toward voice, data, or voice and data communications.
  • a transmission media of network 2900 can take any form, including wireline, satellite, wireless, or a combination thereof.
  • any information device 2100-2500 can be, for example, a landline or wireless telephone, facsimile, personal computer, personal information manager, personal digital assistant, handheld computer, data terminal, or other similar device.
  • Fig. 3 is a block diagram of a typical information device 300, which can symbolize any information device 2100-2500, and/or any server 2700, 2800.
  • Information device 300 can include well-known components such as one or more network interfaces 3100, one or more processors 3200, one or more memories 3300 containing instructions 3400, and/or one or more input/output (I/O) devices 3500, etc..
  • network interface 3100 can be a telephone, a traditional data modem, a fax modem, a cable modem, a digital subscriber line interface, a bridge, a hub, a router, or other similar devices.
  • Each processor 3200 can be a general purpose microprocessor, such the Pentium III series of microprocessors manufactured by the Intel Corporation of Santa Clara, California.
  • the processor can be an Application Specific Integrated Circuit (ASIC) which has been designed to implement in its hardware and/or firmware at least a part of a method in accordance with an embodiment of the present invention.
  • ASIC Application Specific Integrated Circuit
  • Memory 3300 can be coupled to a processor 3200 and can store instructions 3400 adapted to be executed by processor 3200 according to one or more actions of method 100.
  • Memory 3300 can be any device capable of storing analog or digital information, such as a hard disk, Random Access Memory (RAM), Read Only Memory (ROM), flash memory, a compact disk, a magnetic tape, a floppy disk, and any combination thereof.
  • RAM Random Access Memory
  • ROM Read Only Memory
  • flash memory a compact disk, a magnetic tape, a floppy disk, and any combination thereof.
  • Instructions 3400 can be embodied in software, which can take any of numerous forms that are well-known in the art.
  • system 200 can utilize one or more databases having a flat file or a relational organization, and a centralized or distributed architecture. For instance, those of skill in the art can tailor items such as an SQL database to provide the functionality of method 100 and system 200.
  • One supplier of such database items is Oracle Corporation, of Redwood Shores, CA.
  • software tools such as EDI, FTP, HTTP, HTML, XML, cXML, XSL, and WAP can be utilized for communications between information devices.
  • system 200 can utilize platform-independent and or network-centric software tools such as, for example, Java or JavaScript.
  • Any input/output (I/O) device 3500 can be an audio and/or visual device, including, for example, a monitor, display, keyboard, keypad, touchpad, pointing device, microphone, speaker, video camera, camera, scanner, and/or printer, including a port to which an I/O device can be attached or connected.
  • I/O input/output
  • Fig. 4 is a flowchart of an exemplary embodiment of an exemplary method 400 of the present invention, and elaborates upon some of the possibilities of Functionality #1.
  • method 400 can include the selection of a client folder by a user.
  • the user can then select the applicable policy year.
  • the current calendar year can be offered as a default.
  • the user can select an action, such as for example, "negotiate renewal”.
  • a system of the present invention can render to the user a folder structure that corresponds to the user's role and security settings.
  • Fig. 5 provides an example of a folder structure and/or graphical user interface 500 that can be rendered to a user by method 400 of Fig. 4.
  • Window 5010 can contain one ore more tabs 5020.
  • One such exemplary tab, titled “Explorer” can allow a user to access a folder hierarchy 5030 directed to, for example, documents, messages, and/or templates.
  • Another such exemplary tab, titled “Search”, can provide an interface whereby a user can search for one or more documents, messages, and/or templates, within folder hierarchy 5030, and/or view the results of that search.
  • Folder hierarchy 5030 can include one or more folders 5040, which, for example, can contain information about, and be titled, as follows:
  • Client folders 5040 can be further hierarchically organized by, for example: • Client name;
  • Fig. 6 is a flowchart of an exemplary embodiment of an exemplary method 600 of the present invention, and elaborates upon some of the possibilities of Functionality #2.
  • method 600 can include the selection of a folder by a user.
  • the user can then select the collaborators for the folder.
  • the user can indicate these collaborators by any of several methods. For example, the user can search for the collaborator in a directory, and select the collaborator when found. As another example, the user can enter the collaborator's e-mail address.
  • the user can set access rights for the collaborators. These rights can be specified at any of several levels, including for all contents of the folder, for one or more sub-folders, and/or for one or more specific documents, messages, and/or templates within a given folder.
  • a system of the present invention can provide a notification to a collaborator of the change in access rights.
  • the system can send an e-mail message notifying a collaborator that they have been granted access to a particular client folder, and providing an embedded URL hyperlink, the activation of which can ultimately result in the rendering of the contents of that folder.
  • the system can send a pager message to a collaborator indicating that the collaborator has been upgraded from "read-only” to "read/write" access to a specific document.
  • the system can provide notification via any known communications method and/or technology.
  • the system can respond to an attempt by the collaborator to exercise their access rights by presenting a log-in screen, the successful completion of which can result in the rendering of the folders to which access has been granted.
  • Fig. 7 is a flowchart of an exemplary embodiment of an exemplary method 700 of the present invention, and elaborates upon some of the possibilities of Functionality #7.
  • method 700 can include the selection of a folder by a user.
  • the user can then create documents and/or messages, which an embodiment of a system of the present invention can automatically link to the selected folder.
  • an embodiment of a system of the present invention also can automatically store the created documents and/or messages in the selected folder.
  • the created documents and/or messages can be rendered to the user as being stored in the selected folder, the documents and/or messages can actually be stored on any networked media, with merely the link providing a connection to the rendered folder.
  • an embodiment of a system of the present invention can maintain a version history detailing any changes to a document or message. This version history can further describe the time and date of the changes, and the user performing the changes. Moreover, an embodiment of a system of the present invention can archive one or more earlier versions of the document or message, such that any version of the document or message can be recalled.
  • a history of the document and/or message can be provided to the user upon request. Also, the user can be notified when a collaborator has opened a message or document, and the time at which such opening occurred.
  • Fig. 8 provides a block diagram of an exemplary embodiment of an exemplary system 800 of the present invention.
  • system 800 can be viewed as illustrative, and should not be construed to limit the implementation of method 100 and/or functionalities #1 through #6.
  • a database 8100 can be stored on a shared RAID array 8120, which can be connected via dual Fiber Channel 8140 to one or more database servers 8160.
  • database servers 8160 can include a dual Intel Xeon processor with 4 gigabytes of RAM, and can be connected through a back-end sub-network 8300 to one or more firewalls 8320.
  • firewalls 8320 Also connected through a back-end sub-network 8300 to one or more firewalls 8320 can be one or more application servers 8200, which can similarly include one or more Intel Xeon processors with a substantial quantity of RAM. Also, one or more databases (not shown) can be connected to application servers 8200.
  • Firewalls 8320 can run on one or more servers, such as the Netra TI server, by Sun Microsystems Inc. of Palo Alto, California, and can utilize a secure backend network infrastructure such as those provided by Navisite of Andover, Massachusetts. Firewalls 8320 can be clustered using one or more products from the StoneBeat line by StoneSoft of Helsinki, Finland. Firewalls 8320 can be connected via sub-network 8380 to one or more web servers 8400, each of which can utilize dual Intel processors with 1 gigabyte of RAM.
  • servers such as the Netra TI server, by Sun Microsystems Inc. of Palo Alto, California, and can utilize a secure backend network infrastructure such as those provided by Navisite of Andover, Massachusetts. Firewalls 8320 can be clustered using one or more products from the StoneBeat line by StoneSoft of Helsinki, Finland. Firewalls 8320 can be connected via sub-network 8380 to one or more web servers 8400, each of which can utilize dual Intel processors with 1 gigabyte of RAM.
  • Web servers 8400 can be connected to a router/load balancer 8420 which can utilize standard EM protocol, port packet filtering, and/or access control lists.
  • Router 8420 can be connected to a front-end network 8440, which can be connected to one or more core routers 8460, each of which can utilize standard anti-spoofing, denial of service counter-measures, and access control lists.
  • each of core routers 8460 can be connected to a data network 8500, such as the Internet.
  • the connection to network 8500 can be redundant, and network 8500 itself can be a backbone provider, such as UUNET or AT&T.
  • Figure 9
  • Fig. 9 is a block diagram of an exemplary embodiment of an exemplary software architecture 900 of the present invention.
  • Software architecture 900 can have several levels, including, for example, data level 9100, document management level 9200, collaboration services level 9300, application services level 9400, and/or web services level 9500, etc..
  • data level 9100 can be numerous databases.
  • data level 9100 can include risk profile database 9110, which can include data related to exposures and/or coverages.
  • Data level 9100 can also include an entity and address management database 9120, which can include data related to entity profiles, preferences, addressing, and/or contact management.
  • Data level 9100 can also include a document indexing and management database 9130, which can include data related to audit trails, versioning, security, and/or meta-data.
  • document management level 9200 can be a document management service 9210, such as the iManage product from iManage of San Mateo, California, which can provide services such as document meta-data tagging, object permissions and access control, document version management, indexing, and/or full text searching.
  • Linked to document management service 9210 can be a collaboration file management service 9212 and/or a content engine file management service 9214, to which a content import & tagging system can be linked.
  • document management service 9210 Also linked to document management service 9210 can be fax/e-mail integration service 9216 and/or replication management service 9218.
  • application/template XML processing service 9220 can be connected to a relational database management system 9230, such as SQL Server 7.0, and to one or more third party system interfaces 9240.
  • Between document management level 9200 and collaboration services level 9300 can be a unified messaging and asynchronous rules engine 9250.
  • collaboration services level 9300 can be a security and permissions module 9310, which can include a frame-based permissions component 9312, a role- based permissions component 9314, and/or an object-based permissions component 9316. Also included in collaboration services level 9300 can be a workflow management module 9320 which can be connected to several and/or all of the components of the application services level 9400.
  • application services level 9400 can be a reporting services component 9410, a template management component 9420, a placement engine 9430, a collaboration engine 9440, and/or a knowledge and coaching dashboard 9450.
  • collaboration engine 9440 can be a messaging/threads component 9442, a document management component 9444, and/or an alerts/event manager 9446.
  • Between application services level 9400 and web services level 9500 can be a localization module 9460 and/or a brand management module 9480.
  • Web services level 9500 can include an integrated web-based risk management workspace 9510, that can include facilities for HTML, XML, XSL, JavaScript, and/or ASP, etc.
  • integrated web-based risk management workspace 9510 can be a user authentication/data encryption facility 9520, utilizing protocols such as RSA and/or SSL.
  • embodiments of the present invention can enable improved efficiency in the risk and insurance industries. Such efficiency improvements can serve to lower costs, improve quality of service, improve customer relations, and/or improve worker morale.
  • the embodiments of the computer-aided method for managing a web-enabled collaborative insurance process of the present invention can be adapted to automatically alert an insurer when a request for quotation is posted, or to automatically alert a broker (or any other designated collaborator) when a quote has been posted.
  • a computer-aided system of the present invention can provide software that compares quotes and recommends a policy based upon preselected criteria, including criteria collaboratively selected by the client, the client's advisor, and/or the broker.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne un procédé (100) permettant la création d'une structure de dossiers personnalisée pour un processus d'assurance collectif mis en oeuvre sur le Internet. Ce procédé consiste à créer automatiquement pour chaque utilisateur, une pluralité de dossiers normalisés correspondant à un rôle de l'utilisateur dans un processus d'assurance collectif mis en oeuvre sur Internet.
PCT/US2001/029767 2000-09-22 2001-09-24 Procede et systeme permettant l'automatisation des processus d'assurance WO2002025470A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU2001293000A AU2001293000A1 (en) 2000-09-22 2001-09-24 Method and system for automating insurance processes
EP01973421A EP1330731A4 (fr) 2000-09-22 2001-09-24 Procede et systeme permettant l'automatisation des processus d'assurance
CA002423011A CA2423011A1 (fr) 2000-09-22 2001-09-24 Procede et systeme permettant l'automatisation des processus d'assurance

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US23436800P 2000-09-22 2000-09-22
US60/234,368 2000-09-22

Publications (1)

Publication Number Publication Date
WO2002025470A1 true WO2002025470A1 (fr) 2002-03-28

Family

ID=22881074

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/029767 WO2002025470A1 (fr) 2000-09-22 2001-09-24 Procede et systeme permettant l'automatisation des processus d'assurance

Country Status (4)

Country Link
EP (1) EP1330731A4 (fr)
AU (1) AU2001293000A1 (fr)
CA (1) CA2423011A1 (fr)
WO (1) WO2002025470A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007147194A1 (fr) * 2006-06-23 2007-12-27 Geoffrey Miles Mansfield, John Terry, Antony John Fowler Ward And Peter John Williams, As Trustee For The Griffith Hack Unit Trust Système et procédé permettant de passer en revue des enregistrements
US8463624B2 (en) * 2003-09-19 2013-06-11 Oracle International Corporation Techniques for ensuring data security among participants in a web-centric insurance management system

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160180469A1 (en) * 2014-12-22 2016-06-23 WholeSource, LLC Workflow management system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4567359A (en) * 1984-05-24 1986-01-28 Lockwood Lawrence B Automatic information, goods and services dispensing system
US5842178A (en) * 1996-02-22 1998-11-24 Giovannoli; Joseph Computerized quotation system and method
US5845256A (en) * 1993-08-19 1998-12-01 John B. Pescitelli Interactive self-service vending system
US5873066A (en) * 1997-02-10 1999-02-16 Insurance Company Of North America System for electronically managing and documenting the underwriting of an excess casualty insurance policy
US6272528B1 (en) * 1997-08-02 2001-08-07 International Computers Limited Computer method for delivery of financial services

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5388196A (en) * 1990-09-07 1995-02-07 Xerox Corporation Hierarchical shared books with database
US5956715A (en) * 1994-12-13 1999-09-21 Microsoft Corporation Method and system for controlling user access to a resource in a networked computing environment
US5813009A (en) * 1995-07-28 1998-09-22 Univirtual Corp. Computer based records management system method
WO1998001807A1 (fr) * 1996-07-03 1998-01-15 Polydoc N.V. Systeme d'aide a la production de documents
AUPP252298A0 (en) * 1998-03-24 1998-04-23 80-20 Software Pty Limited Document management software
US6453339B1 (en) * 1999-01-20 2002-09-17 Computer Associates Think, Inc. System and method of presenting channelized data
US6687878B1 (en) * 1999-03-15 2004-02-03 Real Time Image Ltd. Synchronizing/updating local client notes with annotations previously made by other clients in a notes database
US6289460B1 (en) * 1999-09-13 2001-09-11 Astus Corporation Document management system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4567359A (en) * 1984-05-24 1986-01-28 Lockwood Lawrence B Automatic information, goods and services dispensing system
US5845256A (en) * 1993-08-19 1998-12-01 John B. Pescitelli Interactive self-service vending system
US5842178A (en) * 1996-02-22 1998-11-24 Giovannoli; Joseph Computerized quotation system and method
US5873066A (en) * 1997-02-10 1999-02-16 Insurance Company Of North America System for electronically managing and documenting the underwriting of an excess casualty insurance policy
US6272528B1 (en) * 1997-08-02 2001-08-07 International Computers Limited Computer method for delivery of financial services

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1330731A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8463624B2 (en) * 2003-09-19 2013-06-11 Oracle International Corporation Techniques for ensuring data security among participants in a web-centric insurance management system
US9916624B2 (en) 2003-09-19 2018-03-13 Oracle International Corporation Techniques for arranging views and navigating in a web-centric insurance management system
WO2007147194A1 (fr) * 2006-06-23 2007-12-27 Geoffrey Miles Mansfield, John Terry, Antony John Fowler Ward And Peter John Williams, As Trustee For The Griffith Hack Unit Trust Système et procédé permettant de passer en revue des enregistrements

Also Published As

Publication number Publication date
EP1330731A1 (fr) 2003-07-30
AU2001293000A1 (en) 2002-04-02
CA2423011A1 (fr) 2002-03-28
EP1330731A4 (fr) 2004-12-15

Similar Documents

Publication Publication Date Title
US20040186750A1 (en) Method and system for automating insurance processes
US7890405B1 (en) Method and system for enabling collaboration between advisors and clients
US7430535B2 (en) Methods and systems for identifying prospective customers and managing deals
US20080215474A1 (en) Systems and methods for management of intangible assets
US20050187866A1 (en) Method and system for executing financial transactions via a communication medium
US20050055306A1 (en) User-defined dynamic collaborative environments
US20030120578A1 (en) System and methods for electronic securities underwriting and electronic dissemination of annual financial and disclosure information from issuers to information repositories in accordance with U.S. securities laws and regulations
US20020198743A1 (en) Network architecture and management system for conducting insurance activities on a network
CN1716305A (zh) 经由分布式网络处理抵押借贷的借贷发起软件系统
MXPA02004887A (es) Sistemas y metodos para la creacion de aplicaciones de recomendaciones financieras.
US8024262B2 (en) System and method for deal management of syndicated loans by multiple bookrunners
US20030225764A1 (en) Method and system for displaying data in a collaborative work environment
US20090265279A1 (en) System and method for managing and distributing hedge fund data
US20040205010A1 (en) Report Generator for Allowing Financial Entity to Monitor Securities Class Action Lawsuits and Potential Monetary Claims Resulting Therefrom
US20110131124A1 (en) Report Generator For Allowing A Financial Entity To Monitor Securities Class Action Lawsuits And Potential Monetary Claims Resulting Therefrom
US7848984B1 (en) Method and system for collaborating advisors
US20070208638A1 (en) Consumer credit finance cashflow funding system
US8775292B2 (en) Process for creating reports of noteworthy securities class action lawsuits customized to show potential monetary claims resulting from the lawsuits for securities purchased or acquired by one or more financial entities and including loss chart selection
US8538782B2 (en) Method and system for data submission management of insurance application in a data processing system
EP1330731A1 (fr) Procede et systeme permettant l'automatisation des processus d'assurance
US20020194034A1 (en) Method and apparatus for automating structured settlements
WO2007149551A2 (fr) Système et procédé de gestion d'actifs intangibles
Reed Capturing electronic transactional evidence: the future
EP1317717A1 (fr) Systeme et procede d'acces a distance a des informations relatives a des produits d'investissement
WO2003102846A1 (fr) Systeme et procede permettant de faciliter des transactions

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 10391533

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2423011

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 2001293000

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 2001973421

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2001973421

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Ref document number: 2001973421

Country of ref document: EP