US20060184570A1 - Value impact risk transfer products - Google Patents

Value impact risk transfer products Download PDF

Info

Publication number
US20060184570A1
US20060184570A1 US11/278,423 US27842306A US2006184570A1 US 20060184570 A1 US20060184570 A1 US 20060184570A1 US 27842306 A US27842306 A US 27842306A US 2006184570 A1 US2006184570 A1 US 2006184570A1
Authority
US
United States
Prior art keywords
risk
data
value
swap
risks
Prior art date
Legal status (The legal status 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 status listed.)
Abandoned
Application number
US11/278,423
Inventor
Jeff Eder
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Eder Jeffrey
Original Assignee
Individual
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 Individual filed Critical Individual
Priority to US11/278,423 priority Critical patent/US20060184570A1/en
Assigned to ASSET RELIANCE, INC. reassignment ASSET RELIANCE, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: EDER, JEFF S.
Publication of US20060184570A1 publication Critical patent/US20060184570A1/en
Assigned to ASSET RELIANCE, INC. reassignment ASSET RELIANCE, INC. NUNC PRO TUNC ASSIGNMENT (SEE DOCUMENT FOR DETAILS). Assignors: EDER, JEFF
Assigned to EDER, JEFFREY reassignment EDER, JEFFREY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ASSET RELIANCE INC
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06NCOMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N5/00Computing arrangements using knowledge-based models
    • G06N5/02Knowledge representation; Symbolic representation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063Operations research, analysis or management
    • G06Q10/0637Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
    • G06Q10/06375Prediction of business process outcome or impact based on a proposed change
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/03Credit; Loans; Processing thereof
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08Insurance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06NCOMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N20/00Machine learning
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q10/00Administration; Management
    • G06Q10/04Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"

Definitions

  • This invention relates to the development and delivery of products and programs that transfer the value impact of a plurality of risks for one or more customers.
  • the information regarding the risk transfer needs for each customer using the system is continuously developed and communicated to the operator of the system described herein (such as an insurance company or bank) that analyzes the information for each customer in order to:
  • the system described herein goes on to analyze the information provided by each enterprise and the financial status of firm operating the system (hereinafter, the system operator) to determine if standby credit lines and/or re-insurance are required. If either of these “back-up” (aka contingent) facilities for capital are required, then the appropriate amount of standby credit and/or reinsurance is determined by the system described herein.
  • the system described herein enables the just-in-time provision of financial service products and services such as risk transfer that are tailored to the exact needs of the enterprise.
  • the electronic linkage also eliminates the time lag that prevents many from companies from obtaining the risk reduction products they need
  • FIG. 1 is a block diagram showing the major processing steps described herein;
  • FIG. 2 is a diagram showing the files or tables in the application database ( 50 ) described herein that are utilized for data storage and retrieval during the processing in the innovative risk transfer system;
  • FIG. 3 is a block diagram of an implementation described herein;
  • FIG. 4 is a diagram showing the data windows that are used for receiving information from and transmitting information to the customer ( 20 ) during system processing;
  • FIG. 5 is block diagrams showing the sequence of steps in the present invention used for specifying system settings and for initializing and operating the data bots that extract, aggregate, store and manipulate information utilized in system processing from: the basic financial system, advanced financial system, customers and external databases; and
  • FIG. 6 is a block diagram showing the sequence in steps in the present invention used in the collaborative, on-line development and delivery of customized risk transfer programs.
  • FIG. 1 provides an overview of the processing completed by the system for the collaborative, on-line development and delivery of customized risk transfer programs.
  • an automated method of and system ( 100 ) for collaborative, on-line development and delivery of customized risk transfer programs is provided. Processing starts in this system ( 100 ) with the specification of system settings and the initialization and activation of software data “bots” ( 200 ) that extract, aggregate, manipulate and store the internal data, external data and customer data used for completing system processing. The data from external databases is used to analyze generic event risks and prices on investments for the asset classes and contingent liabilities specified by the system operator ( 21 ).
  • a customer financial model is created in order to identify the impact of the different elements of value, external factors and risks on customer financial performance and value.
  • All data used in processing is extracted via a network ( 45 ) from a basic financial system database ( 5 ), an external database ( 25 ), an advanced finance system database ( 30 ) and a customer database ( 35 ).
  • These information extractions and aggregations may be influenced by a system operator ( 21 ) through interaction with a user-interface portion of the application software ( 700 ) that mediates the display, transmission and receipt of all information to and from browser software ( 800 ) such as the Microsoft Internet Explorer or Netscape Navigator in an access device ( 90 ) such as a phone or personal computer that the customer ( 20 ) or system operator interact with.
  • the application database ( 50 ) contains tables for storing input, extracted information and system calculations including an xml profile table ( 140 ), a bot date table ( 141 ), a customer table ( 142 ), a risk products table ( 143 ), a swaps table ( 144 ), a customer profile table ( 145 ), an exchange payout history table ( 146 ), an generic risk table ( 147 ), a liability scenario table ( 148 ), an asset position table ( 149 ), an external database table ( 150 ), an asset forecasts table ( 151 ), an asset correlation table ( 152 ), an scenario table ( 153 ), an exchange simulation table ( 154 ), a contingent capital table ( 155 ), an optimal exchange mix table ( 156 ) and an exchange premium history table ( 157 ) a system settings table ( 158 ), a metadata mapping table ( 159 ), a conversion rules table ( 160 ), a metadata mapping table ( 159 ), a conversion rules table ( 160 ), a metadata mapping table ( 159 ), a conversion
  • the application database ( 50 ) can optionally exist on a hard drive, a datamart, data warehouse or departmental warehouse.
  • the system described herein has the ability to accept and store supplemental or primary data directly from user input, a data warehouse or other electronic files in addition to receiving data from the customer databases described previously.
  • a computer system ( 100 ) illustratively comprised of a user-interface personal computer ( 110 ) connected to an application-server personal computer ( 120 ) via a network ( 45 ).
  • the application server personal computer ( 120 ) is in turn connected via the network ( 45 ) to a database-server personal computer ( 130 ).
  • the user interface personal computer ( 110 ) is also connected via the network ( 45 ) to an internet browser appliance ( 90 ) that contains browser software ( 800 ) such as Microsoft Internet Explorer or Netscape Navigator.
  • the database-server personal computer ( 130 ) has a read/write random access memory ( 131 ), a hard drive ( 132 ) for storage of the application database ( 50 ), a keyboard ( 133 ), a communications bus card containing all required adapters and bridges ( 134 ), a display ( 135 ), a mouse ( 136 ) and a CPU ( 137 ).
  • the application-server personal computer ( 120 ) has a read/write random access memory ( 121 ), a hard drive ( 122 ) for storage of the non-user-interface portion of the enterprise portion of the application software ( 200 and 300 ) described herein, a keyboard ( 123 ), a communications bus containing all required adapters and bridges ( 124 ), a display ( 125 ), a mouse ( 126 ), a CPU ( 127 ) and a printer ( 128 ). While only one client personal computer is shown in FIG. 3 , it is to be understood that the application-server personal computer ( 120 ) can be networked to fifty or more client personal computers ( 110 ) via the network ( 45 ).
  • the application-server personal computer ( 120 ) can also be networked to fifty or more server, personal computers ( 130 ) via the network ( 45 ). It is to be understood that the diagram of FIG. 3 is merely illustrative of one embodiment described herein as the system ( 100 ) and application software ( 200 , 300 and 700 ) could reside on a single computer or any number of computers that are linked together using a network. In a similar manner the system operator ( 21 ) and/or the customer ( 20 ) could interface directly with one or more of the computers in the system ( 100 ) instead of using an access device ( 90 ) with a browser ( 800 ) as described in this embodiment.
  • the user-interface personal computer ( 110 ) has a read/write random access memory ( 111 ), a hard drive ( 112 ) for storage of a client data-base ( 49 ) and the user-interface portion of the application software ( 700 ), a keyboard ( 113 ), a communications bus containing all required adapters and bridges ( 114 ), a display ( 115 ), a mouse ( 116 ), a CPU ( 117 ) and a printer ( 118 ).
  • the application software ( 200 , 300 and 700 ) controls the performance of the central processing unit ( 127 ) as it completes the calculations used to support the collaborative development and implementation of a risk transfer program.
  • the application software program ( 200 , 300 and 700 ) is written in a combination of C++ and Visual Basic® although other languages can be used to the same effect.
  • the application software ( 200 , 300 and 700 ) can use Structured Query Language (SQL) for extracting data from the different databases ( 5 , 25 , 30 and 35 ).
  • SQL Structured Query Language
  • the customer ( 20 ) and system operator ( 21 ) can optionally interact with the user-interface portion of the application software ( 700 ) using the browser software ( 800 ) in the browser appliance ( 90 ) to provide information to the application software ( 200 , 300 and 700 ) for use in determining which data will be extracted and transferred to the application database ( 50 ) by the data bots.
  • User input is initially saved to the client database ( 49 ) before being transmitted to the communication bus card ( 124 ) and on to the hard drive ( 122 ) of the application-server computer via the network ( 45 ).
  • the central processing unit ( 127 ) accesses the extracted data and user input by retrieving it from the hard drive ( 122 ) using the random access memory ( 121 ) as computation workspace in a manner that is well known.
  • the computers ( 110 , 120 and 130 ) shown in FIG. 3 illustratively are IBM PCs or clones or any of the more powerful computers (such as mainframe computers) or workstations that are widely available.
  • Typical memory configurations for client personal computers ( 110 ) used with the present invention should include at least 512 megabytes of semiconductor random access memory ( 111 ) and at least a 100 gigabyte hard drive ( 112 ).
  • Typical memory configurations for the application-server personal computer ( 120 ) used with the present invention should include at least 2056 megabytes of semiconductor random access memory ( 121 ) and at least a 250 gigabyte hard drive ( 122 ).
  • Typical memory configurations for the database-server personal computer ( 130 ) used with the present invention should include at least 4112 megabytes of semiconductor random access memory ( 131 ) and at least a 500 gigabyte hard drive ( 132 ).
  • the risk reduction program development is completed in two stages.
  • the first stage of processing programs bots to continually extract, aggregate, manipulate and store the data from user input, external databases ( 25 ) and customer databases ( 30 ). Bots are independent components of the application that have specific tasks to perform.
  • the second stage of processing (block 300 from FIG. 1 ) analyzes customer risk profiles, determines the optimal risk transfer program for each customer, sets prices and communicates with each customer as in order to complete risk reduction program development and implementation.
  • the processing described in this application for identifying the optimal risk transfer program for each customer can optionally be completed at the enterprise level (as shown in the parent application Ser. No. 09/688,983) before data is transmitted to the system of the present invention.
  • the flow diagrams in FIG. 5 details the processing that is completed by the portion of the application software ( 200 ) that obtains systems settings from the system operator ( 21 ) before extracting, aggregating and storing the information used for system operation from a basic financial system database, an external database ( 25 ), and advanced finance system database ( 30 ) and a customer database ( 35 ).
  • System processing starts in a block 201 , FIG. 5A , which immediately passes processing to a software block 202 .
  • the software in block 202 prompts the system operator ( 21 ) via the system settings data window ( 701 ) to provide system setting information.
  • the system setting information entered by the system operator ( 21 ) is transmitted via the network ( 45 ) back to the application server ( 120 ) where it is stored in the system settings table ( 158 ) in the application database ( 50 ) in a manner that is well known.
  • the specific inputs the system operator ( 21 ) is asked to provide at this point in processing are shown in Table 1. TABLE 1 1. Continuous run, if yes, frequency? (hourly, daily, weekly, monthly or quarterly) 2. Account structure hierarchy 3.
  • Metadata standard (XML, MS OIM, MDC) 4. Location of account structure 5. Location of basic financial system database and metadata 6. Location of advanced finance system database and metadata 7. Location of customer database(s) and metadata 8. Location of external database(s) and metadata 9. Base currency 10. Asset classes of interest 11. Contingent capital alternatives 12. Default missing data procedure 13. Maximum time to wait for user input 14. Confidence interval for risk reduction programs
  • the software in block 202 uses the current system date to determine the time periods (months) that require data to complete the development of risk transfer programs. After the date range is calculated, it is stored in the system settings table ( 158 ). In one embodiment data is obtained for the three year period before and the three year forecast period after the current date.
  • the system operator ( 21 ) also has the option of specifying the data periods that will be used for completing system calculations.
  • the software in block 203 prompts the system operator ( 21 ) via the metadata and conversion rules window ( 702 ) to map metadata using the standard previously specified by the system operator ( 21 ) (XML, Microsoft Open Information Model or the Metadata Coalitions specification) from the basic financial system database ( 5 ), the external database ( 25 ), the advanced financial system database ( 30 ) and the customer database ( 35 ) to the enterprise hierarchy stored in the system settings table ( 158 ) and to the pre-specified fields in the metadata mapping table ( 159 ).
  • Pre-specified fields in the metadata mapping table include, the revenue, expense and capital components and sub-components for the exchange and pre-specified fields for expected value drivers.
  • the metadata mapping often takes the form of specifying the account number ranges that correspond to the different fields in the metadata mapping table ( 159 ).
  • Table 2 shows the base account number structure that the account numbers in the other systems must align with. For example, using the structure shown below, the revenue component for the enterprise could be specified as enterprise 01, any department number, accounts 400 to 499 (the revenue account range) with any sub-account.
  • any database fields that are not mapped to pre-specified fields are defined by the system operator ( 21 ) as component of value, elements of value or non-relevant attributes and “mapped” in the metadata mapping table ( 159 ) to the corresponding fields in each database in a manner identical to that described above for the pre-specified fields.
  • the software in block 203 prompts the system operator ( 21 ) via the metadata and conversion rules window ( 702 ) to provide conversion rules for each metadata field for each data source.
  • Conversion rules will include information regarding currency conversions and conversion for units of measure that may be required to accurately and consistently analyze the data.
  • the inputs from the system operator ( 21 ) regarding conversion rules are stored in the conversion rules table ( 160 ) in the application database ( 50 ).
  • conversion rules have been stored for all fields from every data source, then processing advances to a software block 204 .
  • the software in block 204 checks the bot date table ( 141 ) and deactivates any basic financial system data bots with creation dates before the current system date and retrieves information from the system settings table ( 158 ), metadata mapping table ( 159 ), conversion rules table ( 160 ), the asset position table ( 149 ) and the basic financial system table ( 161 ).
  • the software in block 204 then initializes data bots for each field in the metadata mapping table ( 159 ) that mapped to the basic financial system database ( 5 ) in accordance with the frequency specified by system operator ( 21 ) in the system settings table ( 158 ). Bots are independent components of the application that have specific tasks to perform.
  • Each data bot initialized by software block 204 will store its data in the asset position table ( 149 ) or the basic financial system table ( 161 ). Every data acquisition bot for every data source contains the information shown in Table 3. TABLE 3 1. Unique ID number (based on date, hour, minute, second of creation) 2. The data source location 3. Mapping information 4. Timing of extraction 5. Conversion rules (if any) 6. Storage Location (to allow for tracking of source and destination events) 7.
  • the bots After the software in block 204 initializes all the bots for the basic financial system database, the bots extract and convert data in accordance with their preprogrammed instructions in accordance with the frequency specified by system operator ( 21 ) in the system settings table ( 158 ). As each bot extracts and converts data from the basic financial system database ( 5 ), processing advances to a software block 209 before the bot completes data storage. The software in block 209 checks the basic financial system metadata to see if all data for all fields have been extracted and that there are metadata assignments for all extracted data. If the software in block 209 finds no unmapped data fields, then the extracted, converted data are stored in the asset position table ( 149 ) or the basic financial system table ( 161 ).
  • processing advances to a block 211 .
  • the software in block 211 prompts the system operator ( 21 ) via the metadata and conversion rules window ( 702 ) to provide metadata and conversion rules for each new field.
  • the information regarding the new metadata and conversion rules is stored in the metadata mapping table ( 159 ) and conversion rules table ( 160 ) while the extracted, converted data are stored in the asset position table ( 149 ) or the basic financial system table ( 161 ). It is worth noting at this point that the activation and operation of bots where all the fields have been mapped to the application database ( 50 ) continues. Only bots with unmapped fields “wait” for user input before completing data storage. The new metadata and conversion rule information will be used the next time bots are initialized in accordance with the frequency established by the system operator ( 21 ). In either event, system processing passes on to a software block 221 .
  • the software in block 221 checks the bot date table ( 141 ) and deactivates any external database data bots with creation dates before the current system date and retrieves information from the generic risk table ( 147 ), external database table ( 150 ), system settings table ( 158 ), metadata mapping table ( 159 ) and conversion rules table ( 160 ).
  • the software in block 221 then initializes data bots for each field in the metadata mapping table ( 159 ) that mapped to the external database ( 25 ) in accordance with the frequency specified by system operator ( 21 ) in the system settings table ( 158 ).
  • Bots are independent components of the application that have specific tasks to perform. In the case of data acquisition bots, their tasks are to extract and convert data from a specified source and then store it in a specified location.
  • Each data bot initialized by software block 221 will store its data in the generic risk table ( 147 ) or the external database table ( 150 ).
  • the bots extract and convert data in accordance with their preprogrammed instructions in accordance with the frequency specified by system operator ( 21 ) in the system settings table ( 158 ).
  • processing advances to a software block 209 before the bot completes data storage.
  • the software in block 209 checks the advanced finance system metadata to see if all data for all fields have been extracted and that there are metadata assignments for all extracted data.
  • the software in block 209 finds no unmapped data fields, then the extracted, converted data are stored in the generic risk table ( 147 ) or external database table ( 150 ). Alternatively, if there are unmapped data fields, then processing advances to a block 211 .
  • the software in block 211 prompts the system operator ( 21 ) via the metadata and conversion rules window ( 702 ) to provide metadata and conversion rules for each new field.
  • the information regarding the new metadata and conversion rules is stored in the metadata mapping table ( 159 ) and conversion rules table ( 160 ) while the extracted, converted data are stored in the generic risk table ( 147 ) or external database table ( 150 ). It is worth noting at this point that the activation and operation of bots where all the fields have been mapped to the application database ( 50 ) continues.
  • the software in block 225 checks the bot date table ( 141 ) and deactivates any advanced finance system data bots with creation dates before the current system date and retrieves information from the system settings table ( 158 ), metadata mapping table ( 159 ), conversion rules table ( 160 ) and advanced finance system table ( 162 ).
  • the software in block 225 then initializes data bots for each field in the metadata mapping table ( 159 ) that mapped to the advanced finance system database ( 30 ) in accordance with the frequency specified by system operator ( 21 ) in the system settings table ( 158 ).
  • Bots are independent components of the application that have specific tasks to perform. In the case of data acquisition bots, their tasks are to extract and convert data from a specified source and then store it in a specified location.
  • Each data bot initialized by software block 225 will store its data in the asset position table ( 149 ) or the advanced finance system table ( 162 ).
  • the bots extract and convert data in accordance with their preprogrammed instructions in accordance with the frequency specified by system operator ( 21 ) in the system settings table ( 158 ).
  • processing advances to a software block 209 before the bot completes data storage.
  • the software in block 209 checks the advanced finance system metadata to see if all data for all fields have been extracted and that there are metadata assignments for all extracted data.
  • the software in block 209 finds no unmapped data fields, then the extracted, converted data are stored in the asset position table ( 149 ) or the advanced finance system table ( 162 ). Alternatively, if there are unmapped data fields, then processing advances to a block 211 .
  • the software in block 211 prompts the system operator ( 21 ) via the metadata and conversion rules window ( 702 ) to provide metadata and conversion rules for each new field.
  • the information regarding the new metadata and conversion rules is stored in the metadata mapping table ( 159 ) and conversion rules table ( 160 ) while the extracted, converted data are stored in asset position table ( 149 ) or the advanced finance system table ( 162 ).
  • bots where all the fields have been mapped to the application database ( 50 ) continues. Only bots with unmapped fields “wait” for user input before completing data storage. The new metadata and conversion rule information will be used the next time bots are initialized in accordance with the frequency established by the system operator ( 21 ). In either event, system processing passes on to a software block 226 .
  • the software in block 226 checks the bot date table ( 141 ) and deactivates any customer database data bots with creation dates before the current system date and retrieves information from the system settings table ( 158 ), metadata mapping table ( 159 ), conversion rules table ( 160 ) and customer table ( 142 ).
  • the software in block 226 then initializes data bots for each field in the metadata mapping table ( 159 ) that mapped to the customer database ( 35 ) in accordance with the frequency specified by system operator ( 21 ) in the system settings table ( 158 ).
  • Bots are independent components of the application that have specific tasks to perform. In the case of data acquisition bots, their tasks are to extract and convert data from a specified source and then store it in a specified location.
  • Each data bot initialized by software block 226 will extract the model of customer financial performance by element of value, factor and risk and the confidence interval for risk reduction programs specified by the customer. The bot will then store this data in the customer profile table ( 145 ).
  • the software in block 226 initializes all the bots for the advanced finance system database, the bots extract and convert data in accordance with their preprogrammed instructions in accordance with the frequency specified by system operator ( 21 ) in the system settings table ( 158 ).
  • processing advances to a software block 209 before the bot completes data storage.
  • the software in block 209 checks the advanced finance system metadata to see if all data for all fields have been extracted and that there are metadata assignments for all extracted data.
  • the software in block 209 finds no unmapped data fields, then the extracted, converted data are stored in the customer profile table ( 145 ). Alternatively, if there are unmapped data fields, then processing advances to a block 211 .
  • the software in block 211 prompts the system operator ( 21 ) via the metadata and conversion rules window ( 702 ) to provide metadata and conversion rules for each new field.
  • the information regarding the new metadata and conversion rules is stored in the metadata mapping table ( 159 ) and conversion rules table ( 160 ) while the extracted, converted data are stored in the customer profile table ( 145 ). It is worth noting at this point that the activation and operation of bots where all the fields have been mapped to the application database ( 50 ) continues.
  • the flow diagram in FIG. 6 details the processing that is completed by the portion of the application software ( 300 ) that analyzes information from a number of customers and arranges for risk “swaps” and/or the sale of risk transfer products to each customer at a price that meets the profit goals and reserve requirements of the company operating the risk exchange.
  • the description below will follow the processing and activities of the system described herein when one new customer profile is transmitted to the exchange.
  • System processing in this portion of the application software ( 300 ) begins in a block 302 .
  • the software in block 302 checks the bot date table ( 141 ) and deactivates any transfer bots with creation dates before the current system date for the customer transmitting data to the exchange.
  • the software in block 302 then retrieves the information from the xml profile table ( 140 ), the customer table ( 142 ), the risk products table ( 143 ), the swaps table ( 144 ) and the customer profile table ( 145 ) in order to initialize transfer bots for the customer transmitting a summary profile to the exchange.
  • Bots are independent components of the application that have specific tasks to perform.
  • their primary tasks are to identify swaps, existing product and new products that can be used to satisfy the risk transfer needs of the customer transmitting data to the exchange. For example, if one customer has a significant risk from oil prices dropping (a heating oil company, for example) and another customer faces a significant risk when oil prices rise (a trucking company, for example), then the transfer bot will identify the offsetting risk factors and record a swap. If the risk transfer can be completed by both an existing risk transfer product and a swap, then preference is given to the swap. Every transfer bot contains the information shown in Table 4. TABLE 4 1. Unique ID number (based on date, hour, minute, second of creation) 2. Creation date (date, hour, minute, second) 3.
  • Mapping information 4. Storage location 5. Risk factor 6. Type: Swap, existing product or (potential) new product 7. Amount(s) 8. Date(s) 9. Customer 1 (for swaps only) . . . to 9 + n. Customer n (for swaps only)
  • the transfer bot identifies the swaps, existing products and new products that will satisfy the needs of the enterprise for risk transfer the results are saved to the application database ( 50 ).
  • Information on swaps is saved on the swaps table ( 144 ) and the customer profile table ( 145 ) and information on new products is saved in the risk products table ( 143 ) without a price. The price for new products will be established later in the processing.
  • processing advances to a software block 305 .
  • the software in block 305 checks the bot date table ( 141 ) and deactivates any liability scenario bots with creation dates before the current system date.
  • the software in block 305 then retrieves the information from the xml profile table ( 140 ), the customer table ( 142 ), the risk products table ( 143 ), the swaps table ( 144 ), the customer profile table ( 145 ), the exchange payout history table ( 146 ), the generic risk table ( 147 ) and the exchange premium history table ( 156 ) in order to initialize new liability scenario bots.
  • Bots are independent components of the application that have specific tasks to perform.
  • Every liability scenario bot activated in this block contains the information shown in Table 5.
  • TABLE 5 1. Unique ID number (based on date, hour, minute, second of creation) 2. Creation date (date, hour, minute, second) 3. Mapping information 4. Storage location 5. Type: extreme or normal
  • the liability scenario bots After the liability scenario bots are initialized, they retrieve the required information from the xml profile table ( 140 ), the customer table ( 142 ), the risk products table ( 143 ), the swaps table ( 144 ), the customer profile table ( 145 ), the exchange payout history table ( 146 ), the generic risk table ( 147 ), the external database table ( 150 ), the basic financial system table ( 161 ), the advanced finance system table ( 162 ) and the exchange premium history ( 156 ) before generating a series of net payout scenarios that are appropriate for the type of analysis being completed—extreme or normal.
  • the bot saves the scenarios in the liability scenario table ( 148 ) in the application database ( 50 ) and processing advances to a block 309 .
  • the software in block 309 continually completes analyses similar to those completed by the analysis bots in the enterprise portion of the parent application Ser. No. 09/688,983.
  • the software in this block uses the publicly available information stored in the external database table ( 150 ) to complete the analyses shown in Table 6 for each equity investment listed in the asset position table ( 149 ) and described in data obtained from the external database ( 25 ).
  • TABLE 6 1. Identify market value factors causing changes in the equity market price; 2. Forecast the value of the current operation for the company as a function of the causal factors identified in 1 and prior performance using forecasting method for revenue, expense and capital change similar to that described in related U.S. Pat. No. 5,615,109; 3.
  • the results of the first three forecasts (items 2, 3 and 4 from Table 6) are saved in the asset forecasts table ( 151 ) in the application database ( 50 ) and the market value factors (item 1 from Table 6) are saved with the appropriate equity in the asset position table ( 149 ).
  • the software in this block uses the publicly available information stored in the external database table ( 150 ) to complete the analyses shown in Table 6 for each income generating investments (i.e.
  • the software in block 309 then analyzes the covariance between the causal factors for each of the assets to determine the covariance between these assets under both normal and extreme conditions. The results of these analyses are then stored in the asset correlation table ( 152 ) before processing advances to a block 310 .
  • the software in block 310 checks the bot date table ( 141 ) and deactivates any scenario bots with creation dates before the current system date.
  • the software in block 310 then retrieves the information from the asset position table ( 149 ), the external database table ( 150 ) and the asset correlation table ( 152 ) in order to initialize the scenario bots.
  • Bots are independent components of the application that have specific tasks to perform. In the case of scenario bots, their primary task is to identify likely scenarios for the evolution of the causal market value factors.
  • the scenario bots use information from the external databases to obtain forecasts for individual causal factors before using the covariance information stored in the asset correlation table ( 152 ) to develop scenarios for the other causal factors under normal and extreme conditions. Every scenario bot activated in this block contains the information shown in Table 7. TABLE 7 1.
  • the software in block 311 checks the bot date table ( 141 ) and deactivates any net capital scenario bots with creation dates before the current system date.
  • the software in block 311 then retrieves the information from the liability scenario table ( 148 ), and the scenario table ( 153 ) in order to initialize net capital scenarios bots.
  • Bots are independent components of the application that have specific tasks to perform. In the case of net capital scenario bots, their primary task is to run four different types of simulations for the exchange.
  • the net capital scenario bots run Monte Carlo simulations of the exchange financial performance using the two types of scenarios generated by the asset and liability scenario bots—normal and extreme.
  • the net capital scenario bots also run an unconstrained genetic algorithm simulation that evolves to the most negative scenario and simulations specified by regulatory agencies.
  • Every net capital scenario bot activated in this block contains the information shown in Table 8.
  • TABLE 8 1. Unique ID number (based on date, hour, minute, second of creation) 2. Creation date (date, hour, minute, second) 3. Mapping information 4. Storage location 5. Type: Normal, extreme, genetic algorithm or compliance
  • the software in block 312 checks the bot date table ( 141 ) and deactivates any asset optimization bots with creation dates before the current system date.
  • the software in block 312 then retrieves the information from the asset position table ( 149 ), the external database table ( 150 ), the asset forecasts table ( 151 ), the asset correlation table ( 152 ), the scenario table ( 153 ), the exchange simulation table ( 154 ) and the advanced finance systems table ( 162 ) in order to initialize asset optimization bots.
  • Bots are independent components of the application that have specific tasks to perform.
  • asset optimization bots their primary task is to determine the optimal mix of assets and contingent capital purchases (purchase reinsurance and/or other contingent capital purchases, etc.) for the exchange under each scenario using a linear programming optimization algorithm that is constrained by any limitations imposed by regulatory requirements. A multi-criteria optimization is also run at this stage to determine the best mix for maximizing value under combined normal and extreme scenarios. A penalty function for asset liability mismatch can be added in order to minimize the difference between asset and liability lives. Other optimization algorithms can be used at this point to achieve the same result. Every asset optimization bot activated in this block contains the information shown in Table 9. TABLE 9 1. Unique ID number (based on date, hour, minute, second of creation) 2. Creation date (date, hour, minute, second) 3. Mapping information 4. Storage location 5.
  • the software in block 313 prepares and displays the optimal mix of asset purchases, asset sales and contingent capital purchases for the normal, extreme and combined scenario analysis using the optimal mix review window ( 703 ).
  • the optimal mix for the normal and extreme scenarios are determined by calculating the weighted average sum of the different scenarios where the weighting is determined by the relative likelihood of the scenario.
  • the display identifies the optimal mix from the combined analysis as the recommended solution for exchange value maximization.
  • the system operator ( 21 ) is given the option of:
  • any changes are saved in the optimal exchange mix table ( 156 ) in the application database ( 50 ) before processing advances to a software block 314 .
  • the software in block 314 compares the new optimal mix to the existing asset position stored in the asset position table ( 149 ) and orders are generated to purchase assets, sell assets and/or purchase contingent capital in order to bring the current asset position in line with the new optimal mix. These orders are then transmitted via a network ( 45 ) to other institutions and exchanges on the Internet ( 40 ). When the order confirmations are received, the asset position table ( 149 ) is updated with the new information and processing advances to a block 315 . It is worth noting at this point that the processing described for the previous blocks in this section ( 302 , 305 , 109 , 310 , 311 , 312 , 313 and 314 ) could also be used to manage an investment portfolio on a stand alone basis.
  • the software in block 315 prepares and displays the proposed prices for the risk transfer products and the swaps that are going to be offered to the customer using the price review window ( 704 ).
  • the list prices from the risk products table ( 143 ) are used for the existing risk products.
  • Pricing for swaps are calculated by marking up the cost of the swap by a standard percentage.
  • the software in block 315 marks up the calculated breakeven price for any new risk transfer products that were proposed by the bots in block 302 .
  • the system operator ( 21 ) is given the option of:
  • the software in block 316 continually runs an analysis to define the optimal risk reduction strategy for the normal and extreme scenarios for each customer. It does this by first retrieving data from the xml profile table ( 140 ), the customer table ( 142 ), the risk products table ( 143 ), the swaps table ( 144 ), the customer profile table ( 145 ), the exchange payout history table ( 146 ), the generic risk table ( 147 ), the external database table ( 150 ) and the scenario table ( 153 )—the information required to initialize the optimization algorithm.
  • the software in the block uses a linear program that uses the financial model for each customer under the range of conditions expected for each scenario to determine the optimal risk transfer program (swaps, derivative purchases, insurance purchases, etc.) within the specified confidence interval (the confidence interval specified by the system operator ( 21 ) is used if the customer has not specified a confidence interval).
  • a multi criteria optimization determines the best mix for reducing the risk under a combined normal and extreme scenario. Other optimization algorithms and simulations can be used at this point to the same effect. The optimizations consider the effect of changes in the cost of capital on the optimal risk transfer solution.
  • the resulting mix of product purchases and swaps for each scenario (normal and extreme) and the combined analysis is saved in the customer profile table ( 145 ) in the application database ( 50 ) before processing passes to a software block 317 .
  • the shadow prices from these optimizations are also stored in the risk products table ( 143 ) for use in identifying new risk reduction products that the system operator ( 21 ) may choose to offer at a later date. This information can also be used to modify pricing by customer.
  • the software in block 317 uses the customer interface window ( 705 ) to display the information regarding the optimal risk transfer program for the customer and the pricing for the products and swaps that will be used to transfer the risks identified in the optimal risk transfer program. This information could optionally be transmitted to the customer in a summary xml format that is similar to the one initially transmitted to the exchange by the customer.
  • the customer ( 20 ) can reject, edit and/or accept the proposed mix of products and swaps that are displayed.
  • the software in block 317 accepts and confirms orders, updates the information contained in the risk products table ( 143 ), the swaps table ( 144 ), the customer profile table ( 145 ) and the exchange premium history table ( 157 ) to reflect the accepted and confirmed orders.
  • the software in block 317 also accepts input from the customer ( 20 ) regarding any new losses that the customer may have experienced.
  • the software in block 317 verifies the loss is for an insured risk, updates the customer profile table ( 145 ), updates the exchange payout history table ( 146 ) and arranges for payment of the claim in a manner that is well known. This processing is continues until the customer ( 20 ) indicates that the session is complete. System processing advances to a software block 318 .
  • the software in block 318 checks the system settings table ( 158 ) to determine if the system ( 100 ) is operating in continuous mode. If the system is operating in a continuous mode, then processing returns to block 205 and the processing described above is repeated. Alternatively, if the system is not operating in continuous mode, then processing advances to a software block 320 and stops.
  • the system described herein could be used to manage transfers of ownership rights alone or in combination with foreign exchange, liquidity and risk.

Abstract

An automated method and system (100) for the development and delivery of value impact risk transfer products and programs.

Description

    CONTINUATION, CONTINUATION IN PART AND CROSS REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation of application Ser. No. 10/329,172 filed Dec. 23, 2002 the disclosure of which is incorporated herein by reference and a continuation in part of application Ser. No. 09/688,983 filed Oct. 17, 2000 the disclosure of which is incorporated herein by reference. The subject matter of this application is also related to the subject matter of U.S. patent application Ser. No. 09/994,740 filed Nov. 28, 2001, U.S. patent application Ser. No. 10/012,374 filed Dec. 12, 2001, U.S. patent application Ser. No. 10/036,522 filed Jan. 7, 2002, U.S. patent application Ser. No. 10/747,471 filed Dec. 29, 2003, U.S. patent application Ser. No. 10/821,504 filed Apr. 9, 2004 and U.S. patent application Ser. No. 11/142,785 filed May 31, 2005 the disclosures of which are incorporated herein by reference.
  • BACKGROUND OF THE INVENTION
  • This invention relates to the development and delivery of products and programs that transfer the value impact of a plurality of risks for one or more customers.
  • Insurance and most financial services are generally delivered in a manner that is very cumbersome. A system that would enable financial service firms to provide financial “products” like insurance, derivatives, foreign exchange, capital and credit tailored to the specific situation on a “just-in-time” would clearly be beneficial.
  • One of the biggest problems with achieving this goal has been that there has been no agreed upon method for analyzing risk, liquidity and foreign exchange requirements and for communicating that information to financial service firms. It is worth noting at this point that while XML is widely touted as a panacea for inter-firm communication it is only useful in establishing the language for the communication—not the substance of what is being communicated. To satisfy all the potential providers of financial services, the substance of the communication regarding risk, liquidity and foreign exchange requirements would have to overcome the limitations of traditional systems and xml.
  • In light of the preceding discussion, it is clear that it would be desirable to have an automated, real time system that could identify the full spectrum of risk transfer (and liquidity) needs for an security portfolio in a way that that would allow financial service firms to provide “just in time” and/or real time financial products and services in a manner that is customized to the exact needs of the customers using the system.
  • SUMMARY OF THE INVENTION
  • It is a general object described herein to provide a novel and useful system for the identification, measurement and management of the risk associated with a portfolio of securities and the automated development and delivery of products and programs that help transfer said risk.
  • The information regarding the risk transfer needs for each customer using the system is continuously developed and communicated to the operator of the system described herein (such as an insurance company or bank) that analyzes the information for each customer in order to:
  • 1) Arrange swaps of risk, between customers with complementary, offsetting needs (for a fee);
  • 2) Arrange for risk transfers for a larger fee in order to meet the needs of each customer using the system and the profit goals (and reserve requirements) of the firm operating the system; and
  • 3) Complete the swaps and risk transfers that have been arranged in accordance with customer instructions.
  • To provide an integrated system for transferring risk, the system described herein goes on to analyze the information provided by each enterprise and the financial status of firm operating the system (hereinafter, the system operator) to determine if standby credit lines and/or re-insurance are required. If either of these “back-up” (aka contingent) facilities for capital are required, then the appropriate amount of standby credit and/or reinsurance is determined by the system described herein.
  • By eliminating many of the gaps in information available to personnel in the enterprise and the system, the system described herein enables the just-in-time provision of financial service products and services such as risk transfer that are tailored to the exact needs of the enterprise. The electronic linkage also eliminates the time lag that prevents many from companies from obtaining the risk reduction products they need
  • BRIEF DESCRIPTION OF DRAWINGS
  • These and other objects, features and advantages described herein will be more readily apparent from the following description of one embodiment of the invention in which:
  • FIG. 1 is a block diagram showing the major processing steps described herein;
  • FIG. 2 is a diagram showing the files or tables in the application database (50) described herein that are utilized for data storage and retrieval during the processing in the innovative risk transfer system;
  • FIG. 3 is a block diagram of an implementation described herein;
  • FIG. 4 is a diagram showing the data windows that are used for receiving information from and transmitting information to the customer (20) during system processing;
  • FIG. 5, is block diagrams showing the sequence of steps in the present invention used for specifying system settings and for initializing and operating the data bots that extract, aggregate, store and manipulate information utilized in system processing from: the basic financial system, advanced financial system, customers and external databases; and
  • FIG. 6 is a block diagram showing the sequence in steps in the present invention used in the collaborative, on-line development and delivery of customized risk transfer programs.
  • DETAILED DESCRIPTION OF ONE EMBODIMENT
  • FIG. 1 provides an overview of the processing completed by the system for the collaborative, on-line development and delivery of customized risk transfer programs. In accordance with the present invention, an automated method of and system (100) for collaborative, on-line development and delivery of customized risk transfer programs is provided. Processing starts in this system (100) with the specification of system settings and the initialization and activation of software data “bots” (200) that extract, aggregate, manipulate and store the internal data, external data and customer data used for completing system processing. The data from external databases is used to analyze generic event risks and prices on investments for the asset classes and contingent liabilities specified by the system operator (21). In one embodiment, a customer financial model is created in order to identify the impact of the different elements of value, external factors and risks on customer financial performance and value. However, any other method or system for developing this data could be used to the same effect. All data used in processing is extracted via a network (45) from a basic financial system database (5), an external database (25), an advanced finance system database (30) and a customer database (35). These information extractions and aggregations may be influenced by a system operator (21) through interaction with a user-interface portion of the application software (700) that mediates the display, transmission and receipt of all information to and from browser software (800) such as the Microsoft Internet Explorer or Netscape Navigator in an access device (90) such as a phone or personal computer that the customer (20) or system operator interact with. While only one basic financial system database (5), external database (25), advanced finance system database (30) and customer database (35) is shown in FIG. 1, it is to be understood that the system (100) can extract data from an unlimited number of databases and customers via the network (45). It also to be understood that the customer (20) and the system operator (21) can operate separate access devices (90). It should also be understood that it is possible to complete a bulk extraction of data from each database (5, 25, 30 and 35) via the network (45) using data extraction applications before initializing the data bots. The data extracted in bulk could be stored in a single datamart or data warehouse where the data bots could operate on the aggregated data.
  • All extracted information is stored in a file or table (hereinafter, table) within an application database (50) as shown in FIG. 2. The application database (50) contains tables for storing input, extracted information and system calculations including an xml profile table (140), a bot date table (141), a customer table (142), a risk products table (143), a swaps table (144), a customer profile table (145), an exchange payout history table (146), an generic risk table (147), a liability scenario table (148), an asset position table (149), an external database table (150), an asset forecasts table (151), an asset correlation table (152), an scenario table (153), an exchange simulation table (154), a contingent capital table (155), an optimal exchange mix table (156) and an exchange premium history table (157) a system settings table (158), a metadata mapping table (159), a conversion rules table (160), a basic financial system table (161) and an advanced finance system table (162). Other combinations of tables and files can be used to the same effect. The application database (50) can optionally exist on a hard drive, a datamart, data warehouse or departmental warehouse. The system described herein has the ability to accept and store supplemental or primary data directly from user input, a data warehouse or other electronic files in addition to receiving data from the customer databases described previously.
  • As shown in FIG. 3, one embodiment described herein is a computer system (100) illustratively comprised of a user-interface personal computer (110) connected to an application-server personal computer (120) via a network (45). The application server personal computer (120) is in turn connected via the network (45) to a database-server personal computer (130). The user interface personal computer (110) is also connected via the network (45) to an internet browser appliance (90) that contains browser software (800) such as Microsoft Internet Explorer or Netscape Navigator.
  • The database-server personal computer (130) has a read/write random access memory (131), a hard drive (132) for storage of the application database (50), a keyboard (133), a communications bus card containing all required adapters and bridges (134), a display (135), a mouse (136) and a CPU (137).
  • The application-server personal computer (120) has a read/write random access memory (121), a hard drive (122) for storage of the non-user-interface portion of the enterprise portion of the application software (200 and 300) described herein, a keyboard (123), a communications bus containing all required adapters and bridges (124), a display (125), a mouse (126), a CPU (127) and a printer (128). While only one client personal computer is shown in FIG. 3, it is to be understood that the application-server personal computer (120) can be networked to fifty or more client personal computers (110) via the network (45). The application-server personal computer (120) can also be networked to fifty or more server, personal computers (130) via the network (45). It is to be understood that the diagram of FIG. 3 is merely illustrative of one embodiment described herein as the system (100) and application software (200, 300 and 700) could reside on a single computer or any number of computers that are linked together using a network. In a similar manner the system operator (21) and/or the customer (20) could interface directly with one or more of the computers in the system (100) instead of using an access device (90) with a browser (800) as described in this embodiment.
  • The user-interface personal computer (110) has a read/write random access memory (111), a hard drive (112) for storage of a client data-base (49) and the user-interface portion of the application software (700), a keyboard (113), a communications bus containing all required adapters and bridges (114), a display (115), a mouse (116), a CPU (117) and a printer (118).
  • The application software (200, 300 and 700) controls the performance of the central processing unit (127) as it completes the calculations used to support the collaborative development and implementation of a risk transfer program. In the embodiment illustrated herein, the application software program (200, 300 and 700) is written in a combination of C++ and Visual Basic® although other languages can be used to the same effect. The application software (200, 300 and 700) can use Structured Query Language (SQL) for extracting data from the different databases (5, 25, 30 and 35). The customer (20) and system operator (21) can optionally interact with the user-interface portion of the application software (700) using the browser software (800) in the browser appliance (90) to provide information to the application software (200, 300 and 700) for use in determining which data will be extracted and transferred to the application database (50) by the data bots.
  • User input is initially saved to the client database (49) before being transmitted to the communication bus card (124) and on to the hard drive (122) of the application-server computer via the network (45). Following the program instructions of the application software, the central processing unit (127) accesses the extracted data and user input by retrieving it from the hard drive (122) using the random access memory (121) as computation workspace in a manner that is well known.
  • The computers (110, 120 and 130) shown in FIG. 3 illustratively are IBM PCs or clones or any of the more powerful computers (such as mainframe computers) or workstations that are widely available. Typical memory configurations for client personal computers (110) used with the present invention should include at least 512 megabytes of semiconductor random access memory (111) and at least a 100 gigabyte hard drive (112). Typical memory configurations for the application-server personal computer (120) used with the present invention should include at least 2056 megabytes of semiconductor random access memory (121) and at least a 250 gigabyte hard drive (122). Typical memory configurations for the database-server personal computer (130) used with the present invention should include at least 4112 megabytes of semiconductor random access memory (131) and at least a 500 gigabyte hard drive (132).
  • Using the system described above, customer financial data is analyzed before a comprehensive risk management program is developed and implemented for each customer. The risk reduction program development is completed in two stages. As shown in FIG. 5 the first stage of processing (block 200 from FIG. 1) programs bots to continually extract, aggregate, manipulate and store the data from user input, external databases (25) and customer databases (30). Bots are independent components of the application that have specific tasks to perform. As shown in FIG. 6 the second stage of processing (block 300 from FIG. 1) analyzes customer risk profiles, determines the optimal risk transfer program for each customer, sets prices and communicates with each customer as in order to complete risk reduction program development and implementation. The processing described in this application for identifying the optimal risk transfer program for each customer can optionally be completed at the enterprise level (as shown in the parent application Ser. No. 09/688,983) before data is transmitted to the system of the present invention.
  • System Settings and Data Bots
  • The flow diagrams in FIG. 5 details the processing that is completed by the portion of the application software (200) that obtains systems settings from the system operator (21) before extracting, aggregating and storing the information used for system operation from a basic financial system database, an external database (25), and advanced finance system database (30) and a customer database (35).
  • System processing starts in a block 201, FIG. 5A, which immediately passes processing to a software block 202. The software in block 202 prompts the system operator (21) via the system settings data window (701) to provide system setting information. The system setting information entered by the system operator (21) is transmitted via the network (45) back to the application server (120) where it is stored in the system settings table (158) in the application database (50) in a manner that is well known. The specific inputs the system operator (21) is asked to provide at this point in processing are shown in Table 1.
    TABLE 1
    1. Continuous run, if yes, frequency? (hourly, daily, weekly, monthly
    or quarterly)
    2. Account structure hierarchy
    3. Metadata standard (XML, MS OIM, MDC)
    4. Location of account structure
    5. Location of basic financial system database and metadata
    6. Location of advanced finance system database and metadata
    7. Location of customer database(s) and metadata
    8. Location of external database(s) and metadata
    9. Base currency
    10. Asset classes of interest
    11. Contingent capital alternatives
    12. Default missing data procedure
    13. Maximum time to wait for user input
    14. Confidence interval for risk reduction programs

    The software in block 202 uses the current system date to determine the time periods (months) that require data to complete the development of risk transfer programs. After the date range is calculated, it is stored in the system settings table (158). In one embodiment data is obtained for the three year period before and the three year forecast period after the current date. The system operator (21) also has the option of specifying the data periods that will be used for completing system calculations.
  • After the storage of system setting data is complete, processing advances to a software block 203. The software in block 203 prompts the system operator (21) via the metadata and conversion rules window (702) to map metadata using the standard previously specified by the system operator (21) (XML, Microsoft Open Information Model or the Metadata Coalitions specification) from the basic financial system database (5), the external database (25), the advanced financial system database (30) and the customer database (35) to the enterprise hierarchy stored in the system settings table (158) and to the pre-specified fields in the metadata mapping table (159). Pre-specified fields in the metadata mapping table include, the revenue, expense and capital components and sub-components for the exchange and pre-specified fields for expected value drivers. Because the bulk of the information being extracted is financial information, the metadata mapping often takes the form of specifying the account number ranges that correspond to the different fields in the metadata mapping table (159). Table 2 shows the base account number structure that the account numbers in the other systems must align with. For example, using the structure shown below, the revenue component for the enterprise could be specified as enterprise 01, any department number, accounts 400 to 499 (the revenue account range) with any sub-account.
    TABLE 2
    Account Number
    01 - 902 (any) - 477- 86 (any)
    Segment Enterprise Department Account Sub-account
    Subgroup Workstation Marketing Revenue Singapore
    Position 4 3 2 1

    As part of the metadata mapping process, any database fields that are not mapped to pre-specified fields are defined by the system operator (21) as component of value, elements of value or non-relevant attributes and “mapped” in the metadata mapping table (159) to the corresponding fields in each database in a manner identical to that described above for the pre-specified fields. After all fields have been mapped to the metadata mapping table (159), the software in block 203 prompts the system operator (21) via the metadata and conversion rules window (702) to provide conversion rules for each metadata field for each data source. Conversion rules will include information regarding currency conversions and conversion for units of measure that may be required to accurately and consistently analyze the data. The inputs from the system operator (21) regarding conversion rules are stored in the conversion rules table (160) in the application database (50). When conversion rules have been stored for all fields from every data source, then processing advances to a software block 204.
  • The software in block 204 checks the bot date table (141) and deactivates any basic financial system data bots with creation dates before the current system date and retrieves information from the system settings table (158), metadata mapping table (159), conversion rules table (160), the asset position table (149) and the basic financial system table (161). The software in block 204 then initializes data bots for each field in the metadata mapping table (159) that mapped to the basic financial system database (5) in accordance with the frequency specified by system operator (21) in the system settings table (158). Bots are independent components of the application that have specific tasks to perform. In the case of data acquisition bots, their tasks are to extract and convert data from a specified source and then store it in a specified location. Each data bot initialized by software block 204 will store its data in the asset position table (149) or the basic financial system table (161). Every data acquisition bot for every data source contains the information shown in Table 3.
    TABLE 3
    1. Unique ID number (based on date, hour, minute, second of creation)
    2. The data source location
    3. Mapping information
    4. Timing of extraction
    5. Conversion rules (if any)
    6. Storage Location (to allow for tracking of source and destination events)
    7. Creation date (date, hour, minute, second)

    After the software in block 204 initializes all the bots for the basic financial system database, the bots extract and convert data in accordance with their preprogrammed instructions in accordance with the frequency specified by system operator (21) in the system settings table (158). As each bot extracts and converts data from the basic financial system database (5), processing advances to a software block 209 before the bot completes data storage. The software in block 209 checks the basic financial system metadata to see if all data for all fields have been extracted and that there are metadata assignments for all extracted data. If the software in block 209 finds no unmapped data fields, then the extracted, converted data are stored in the asset position table (149) or the basic financial system table (161). Alternatively, if there are unmapped data fields, then processing advances to a block 211. The software in block 211 prompts the system operator (21) via the metadata and conversion rules window (702) to provide metadata and conversion rules for each new field. The information regarding the new metadata and conversion rules is stored in the metadata mapping table (159) and conversion rules table (160) while the extracted, converted data are stored in the asset position table (149) or the basic financial system table (161). It is worth noting at this point that the activation and operation of bots where all the fields have been mapped to the application database (50) continues. Only bots with unmapped fields “wait” for user input before completing data storage. The new metadata and conversion rule information will be used the next time bots are initialized in accordance with the frequency established by the system operator (21). In either event, system processing passes on to a software block 221.
  • The software in block 221 checks the bot date table (141) and deactivates any external database data bots with creation dates before the current system date and retrieves information from the generic risk table (147), external database table (150), system settings table (158), metadata mapping table (159) and conversion rules table (160). The software in block 221 then initializes data bots for each field in the metadata mapping table (159) that mapped to the external database (25) in accordance with the frequency specified by system operator (21) in the system settings table (158). Bots are independent components of the application that have specific tasks to perform. In the case of data acquisition bots, their tasks are to extract and convert data from a specified source and then store it in a specified location. Each data bot initialized by software block 221 will store its data in the generic risk table (147) or the external database table (150). After the software in block 221 initializes all the bots for the advanced finance system database, the bots extract and convert data in accordance with their preprogrammed instructions in accordance with the frequency specified by system operator (21) in the system settings table (158). As each bot extracts and converts data from the external database (25), processing advances to a software block 209 before the bot completes data storage. The software in block 209 checks the advanced finance system metadata to see if all data for all fields have been extracted and that there are metadata assignments for all extracted data. If the software in block 209 finds no unmapped data fields, then the extracted, converted data are stored in the generic risk table (147) or external database table (150). Alternatively, if there are unmapped data fields, then processing advances to a block 211. The software in block 211 prompts the system operator (21) via the metadata and conversion rules window (702) to provide metadata and conversion rules for each new field. The information regarding the new metadata and conversion rules is stored in the metadata mapping table (159) and conversion rules table (160) while the extracted, converted data are stored in the generic risk table (147) or external database table (150). It is worth noting at this point that the activation and operation of bots where all the fields have been mapped to the application database (50) continues. Only bots with unmapped fields “wait” for user input before completing data storage. The new metadata and conversion rule information will be used the next time bots are initialized in accordance with the frequency established by the system operator (21). In either event, system processing passes on to a software block 225.
  • The software in block 225 checks the bot date table (141) and deactivates any advanced finance system data bots with creation dates before the current system date and retrieves information from the system settings table (158), metadata mapping table (159), conversion rules table (160) and advanced finance system table (162). The software in block 225 then initializes data bots for each field in the metadata mapping table (159) that mapped to the advanced finance system database (30) in accordance with the frequency specified by system operator (21) in the system settings table (158). Bots are independent components of the application that have specific tasks to perform. In the case of data acquisition bots, their tasks are to extract and convert data from a specified source and then store it in a specified location. Each data bot initialized by software block 225 will store its data in the asset position table (149) or the advanced finance system table (162). After the software in block 225 initializes all the bots for the advanced finance system database, the bots extract and convert data in accordance with their preprogrammed instructions in accordance with the frequency specified by system operator (21) in the system settings table (158). As each bot extracts and converts data from the basic financial system database (5), processing advances to a software block 209 before the bot completes data storage. The software in block 209 checks the advanced finance system metadata to see if all data for all fields have been extracted and that there are metadata assignments for all extracted data. If the software in block 209 finds no unmapped data fields, then the extracted, converted data are stored in the asset position table (149) or the advanced finance system table (162). Alternatively, if there are unmapped data fields, then processing advances to a block 211. The software in block 211 prompts the system operator (21) via the metadata and conversion rules window (702) to provide metadata and conversion rules for each new field. The information regarding the new metadata and conversion rules is stored in the metadata mapping table (159) and conversion rules table (160) while the extracted, converted data are stored in asset position table (149) or the advanced finance system table (162). It is worth noting at this point that the activation and operation of bots where all the fields have been mapped to the application database (50) continues. Only bots with unmapped fields “wait” for user input before completing data storage. The new metadata and conversion rule information will be used the next time bots are initialized in accordance with the frequency established by the system operator (21). In either event, system processing passes on to a software block 226.
  • The software in block 226 checks the bot date table (141) and deactivates any customer database data bots with creation dates before the current system date and retrieves information from the system settings table (158), metadata mapping table (159), conversion rules table (160) and customer table (142). The software in block 226 then initializes data bots for each field in the metadata mapping table (159) that mapped to the customer database (35) in accordance with the frequency specified by system operator (21) in the system settings table (158). Bots are independent components of the application that have specific tasks to perform. In the case of data acquisition bots, their tasks are to extract and convert data from a specified source and then store it in a specified location. Each data bot initialized by software block 226 will extract the model of customer financial performance by element of value, factor and risk and the confidence interval for risk reduction programs specified by the customer. The bot will then store this data in the customer profile table (145). After the software in block 226 initializes all the bots for the advanced finance system database, the bots extract and convert data in accordance with their preprogrammed instructions in accordance with the frequency specified by system operator (21) in the system settings table (158). As each bot extracts and converts data from the customer database (25), processing advances to a software block 209 before the bot completes data storage. The software in block 209 checks the advanced finance system metadata to see if all data for all fields have been extracted and that there are metadata assignments for all extracted data. If the software in block 209 finds no unmapped data fields, then the extracted, converted data are stored in the customer profile table (145). Alternatively, if there are unmapped data fields, then processing advances to a block 211. The software in block 211 prompts the system operator (21) via the metadata and conversion rules window (702) to provide metadata and conversion rules for each new field. The information regarding the new metadata and conversion rules is stored in the metadata mapping table (159) and conversion rules table (160) while the extracted, converted data are stored in the customer profile table (145). It is worth noting at this point that the activation and operation of bots where all the fields have been mapped to the application database (50) continues. Only bots with unmapped fields “wait” for user input before completing data storage. The new metadata and conversion rule information will be used the next time bots are initialized in accordance with the frequency established by the system operator (21). In either event, system processing passes on to software block 301.
  • Risk Exchange
  • The flow diagram in FIG. 6 details the processing that is completed by the portion of the application software (300) that analyzes information from a number of customers and arranges for risk “swaps” and/or the sale of risk transfer products to each customer at a price that meets the profit goals and reserve requirements of the company operating the risk exchange. The description below will follow the processing and activities of the system described herein when one new customer profile is transmitted to the exchange.
  • System processing in this portion of the application software (300) begins in a block 302. The software in block 302 checks the bot date table (141) and deactivates any transfer bots with creation dates before the current system date for the customer transmitting data to the exchange. The software in block 302 then retrieves the information from the xml profile table (140), the customer table (142), the risk products table (143), the swaps table (144) and the customer profile table (145) in order to initialize transfer bots for the customer transmitting a summary profile to the exchange.
  • Bots are independent components of the application that have specific tasks to perform. In the case of transfer bots, their primary tasks are to identify swaps, existing product and new products that can be used to satisfy the risk transfer needs of the customer transmitting data to the exchange. For example, if one customer has a significant risk from oil prices dropping (a heating oil company, for example) and another customer faces a significant risk when oil prices rise (a trucking company, for example), then the transfer bot will identify the offsetting risk factors and record a swap. If the risk transfer can be completed by both an existing risk transfer product and a swap, then preference is given to the swap. Every transfer bot contains the information shown in Table 4.
    TABLE 4
    1. Unique ID number (based on date, hour, minute, second of creation)
    2. Creation date (date, hour, minute, second)
    3. Mapping information
    4. Storage location
    5. Risk factor
    6. Type: Swap, existing product or (potential) new product
    7. Amount(s)
    8. Date(s)
    9. Customer 1 (for swaps only)
    . . . to
    9 + n. Customer n (for swaps only)

    After the transfer bot identifies the swaps, existing products and new products that will satisfy the needs of the enterprise for risk transfer the results are saved to the application database (50). Information on swaps is saved on the swaps table (144) and the customer profile table (145) and information on new products is saved in the risk products table (143) without a price. The price for new products will be established later in the processing. After data storage is complete, processing advances to a software block 305.
  • The software in block 305 checks the bot date table (141) and deactivates any liability scenario bots with creation dates before the current system date. The software in block 305 then retrieves the information from the xml profile table (140), the customer table (142), the risk products table (143), the swaps table (144), the customer profile table (145), the exchange payout history table (146), the generic risk table (147) and the exchange premium history table (156) in order to initialize new liability scenario bots. Bots are independent components of the application that have specific tasks to perform. In the case of liability scenario bots, their primary tasks are to create a series of scenarios estimating the net payout (premiums minus payout=net payout) associated the risks that may be transferred via swaps or insurance from all customers. There are two types of scenarios developed at this stage of processing, normal scenarios and extreme scenarios. The scenarios are developed by combining the information and statistics from summary profiles transmitted by the customers of the exchange with the exchange payout history, the exchange premium history and generic risk information obtained from the external database (25). Every liability scenario bot activated in this block contains the information shown in Table 5.
    TABLE 5
    1. Unique ID number (based on date, hour, minute, second of creation)
    2. Creation date (date, hour, minute, second)
    3. Mapping information
    4. Storage location
    5. Type: extreme or normal
  • After the liability scenario bots are initialized, they retrieve the required information from the xml profile table (140), the customer table (142), the risk products table (143), the swaps table (144), the customer profile table (145), the exchange payout history table (146), the generic risk table (147), the external database table (150), the basic financial system table (161), the advanced finance system table (162) and the exchange premium history (156) before generating a series of net payout scenarios that are appropriate for the type of analysis being completed—extreme or normal. The bot saves the scenarios in the liability scenario table (148) in the application database (50) and processing advances to a block 309.
  • The software in block 309 continually completes analyses similar to those completed by the analysis bots in the enterprise portion of the parent application Ser. No. 09/688,983. The software in this block uses the publicly available information stored in the external database table (150) to complete the analyses shown in Table 6 for each equity investment listed in the asset position table (149) and described in data obtained from the external database (25).
    TABLE 6
    1. Identify market value factors causing changes in the equity market
    price;
    2. Forecast the value of the current operation for the company as a
    function of the causal factors identified in 1 and prior performance
    using forecasting method for revenue, expense and capital change
    similar to that described in related U.S. Pat. No. 5,615,109;
    3. Forecast the allocation of industry real options to the company on
    the basis of relative causal intangible element of value strength using
    forecasting method similar to that described in related U.S. Pat. No.
    5,615,109; and
    4. Forecast the income (dividends) provided by the equity as a function
    of the causal factors identified in 1 and prior performance

    The results of the first three forecasts (items 2, 3 and 4 from Table 6) are saved in the asset forecasts table (151) in the application database (50) and the market value factors (item 1 from Table 6) are saved with the appropriate equity in the asset position table (149). The software in this block uses the publicly available information stored in the external database table (150) to complete the analyses shown in Table 6 for each income generating investments (i.e. bonds or real estate) listed in the asset position table (149) and described in data obtained from the external database (25). The software in block 309 then analyzes the covariance between the causal factors for each of the assets to determine the covariance between these assets under both normal and extreme conditions. The results of these analyses are then stored in the asset correlation table (152) before processing advances to a block 310.
  • The software in block 310 checks the bot date table (141) and deactivates any scenario bots with creation dates before the current system date. The software in block 310 then retrieves the information from the asset position table (149), the external database table (150) and the asset correlation table (152) in order to initialize the scenario bots. Bots are independent components of the application that have specific tasks to perform. In the case of scenario bots, their primary task is to identify likely scenarios for the evolution of the causal market value factors. The scenario bots use information from the external databases to obtain forecasts for individual causal factors before using the covariance information stored in the asset correlation table (152) to develop scenarios for the other causal factors under normal and extreme conditions. Every scenario bot activated in this block contains the information shown in Table 7.
    TABLE 7
    1. Unique ID number (based on date, hour, minute, second of creation)
    2. Creation date (date, hour, minute, second)
    3. Mapping information
    4. Storage location
    5. Type: Normal or extreme

    After the scenario bots are initialized, they retrieve the required information and develop a variety of normal and extreme scenarios as described previously. After the scenario bots complete their calculations they save the resulting scenarios in the scenario table (153) in the application database (50) and processing advances to a block 311.
  • The software in block 311 checks the bot date table (141) and deactivates any net capital scenario bots with creation dates before the current system date. The software in block 311 then retrieves the information from the liability scenario table (148), and the scenario table (153) in order to initialize net capital scenarios bots. Bots are independent components of the application that have specific tasks to perform. In the case of net capital scenario bots, their primary task is to run four different types of simulations for the exchange. The net capital scenario bots run Monte Carlo simulations of the exchange financial performance using the two types of scenarios generated by the asset and liability scenario bots—normal and extreme. The net capital scenario bots also run an unconstrained genetic algorithm simulation that evolves to the most negative scenario and simulations specified by regulatory agencies. Every net capital scenario bot activated in this block contains the information shown in Table 8.
    TABLE 8
    1. Unique ID number (based on date, hour, minute, second of creation)
    2. Creation date (date, hour, minute, second)
    3. Mapping information
    4. Storage location
    5. Type: Normal, extreme, genetic algorithm or compliance

    After the net capital scenario bots are initialized, they retrieve the required information and simulate the financial performance of the risk exchange under the different scenarios. After the net capital scenarios complete their calculations, the resulting forecasts are saved in the exchange simulation table (154) in the application database (50) and processing advances to a block 312.
  • The software in block 312 checks the bot date table (141) and deactivates any asset optimization bots with creation dates before the current system date. The software in block 312 then retrieves the information from the asset position table (149), the external database table (150), the asset forecasts table (151), the asset correlation table (152), the scenario table (153), the exchange simulation table (154) and the advanced finance systems table (162) in order to initialize asset optimization bots. Bots are independent components of the application that have specific tasks to perform. In the case of asset optimization bots, their primary task is to determine the optimal mix of assets and contingent capital purchases (purchase reinsurance and/or other contingent capital purchases, etc.) for the exchange under each scenario using a linear programming optimization algorithm that is constrained by any limitations imposed by regulatory requirements. A multi-criteria optimization is also run at this stage to determine the best mix for maximizing value under combined normal and extreme scenarios. A penalty function for asset liability mismatch can be added in order to minimize the difference between asset and liability lives. Other optimization algorithms can be used at this point to achieve the same result. Every asset optimization bot activated in this block contains the information shown in Table 9.
    TABLE 9
    1. Unique ID number (based on date, hour, minute, second of creation)
    2. Creation date (date, hour, minute, second)
    3. Mapping information
    4. Storage location
    5. Type: Normal, extreme or combined

    After the asset optimization bots complete their analyses, the resulting asset and contingent capital mix for each set of scenarios and the combined analysis is saved in the optimal exchange mix table (156) in the application database (50) and the revised simulations are saved in the exchange simulation table (154) before processing passes to a software block 313.
  • The software in block 313 prepares and displays the optimal mix of asset purchases, asset sales and contingent capital purchases for the normal, extreme and combined scenario analysis using the optimal mix review window (703). The optimal mix for the normal and extreme scenarios are determined by calculating the weighted average sum of the different scenarios where the weighting is determined by the relative likelihood of the scenario. The display identifies the optimal mix from the combined analysis as the recommended solution for exchange value maximization. At this point, the system operator (21) is given the option of:
  • 1) Editing (adding or deleting products and activities) from the recommended solution;
  • 2) Selecting the optimal mix from the normal scenarios;
  • 3) Selecting and then editing the optimal mix from the normal scenarios;
  • 4) Selecting the optimal mix from the extreme scenarios;
  • 5) Selecting and then editing the optimal mix from the extreme scenarios; or
  • 6) Leaving the default choice in place.
  • After the system operator (21) has finished the review and the optional edit of the selected mix, any changes are saved in the optimal exchange mix table (156) in the application database (50) before processing advances to a software block 314.
  • The software in block 314 compares the new optimal mix to the existing asset position stored in the asset position table (149) and orders are generated to purchase assets, sell assets and/or purchase contingent capital in order to bring the current asset position in line with the new optimal mix. These orders are then transmitted via a network (45) to other institutions and exchanges on the Internet (40). When the order confirmations are received, the asset position table (149) is updated with the new information and processing advances to a block 315. It is worth noting at this point that the processing described for the previous blocks in this section (302, 305, 109, 310, 311, 312, 313 and 314) could also be used to manage an investment portfolio on a stand alone basis.
  • The software in block 315 prepares and displays the proposed prices for the risk transfer products and the swaps that are going to be offered to the customer using the price review window (704). The list prices from the risk products table (143) are used for the existing risk products. Pricing for swaps are calculated by marking up the cost of the swap by a standard percentage. The software in block 315 marks up the calculated breakeven price for any new risk transfer products that were proposed by the bots in block 302. At this point, the system operator (21) is given the option of:
  • 1) Editing the recommended prices for any and all of the risk transfers—swaps, existing products and new products;
  • 2) Accepting the recommended prices; or
  • 3) Removing some of swaps and/or risk transfer products from the list.
  • After the system operator (21) completes the review, all price changes and the prices for any new risk transfer products are saved in the risk products table (143) before processing advances to a block 316.
  • The software in block 316 continually runs an analysis to define the optimal risk reduction strategy for the normal and extreme scenarios for each customer. It does this by first retrieving data from the xml profile table (140), the customer table (142), the risk products table (143), the swaps table (144), the customer profile table (145), the exchange payout history table (146), the generic risk table (147), the external database table (150) and the scenario table (153)—the information required to initialize the optimization algorithm. The software in the block uses a linear program that uses the financial model for each customer under the range of conditions expected for each scenario to determine the optimal risk transfer program (swaps, derivative purchases, insurance purchases, etc.) within the specified confidence interval (the confidence interval specified by the system operator (21) is used if the customer has not specified a confidence interval). A multi criteria optimization determines the best mix for reducing the risk under a combined normal and extreme scenario. Other optimization algorithms and simulations can be used at this point to the same effect. The optimizations consider the effect of changes in the cost of capital on the optimal risk transfer solution. The resulting mix of product purchases and swaps for each scenario (normal and extreme) and the combined analysis is saved in the customer profile table (145) in the application database (50) before processing passes to a software block 317. The shadow prices from these optimizations are also stored in the risk products table (143) for use in identifying new risk reduction products that the system operator (21) may choose to offer at a later date. This information can also be used to modify pricing by customer.
  • The software in block 317 uses the customer interface window (705) to display the information regarding the optimal risk transfer program for the customer and the pricing for the products and swaps that will be used to transfer the risks identified in the optimal risk transfer program. This information could optionally be transmitted to the customer in a summary xml format that is similar to the one initially transmitted to the exchange by the customer. The customer (20) can reject, edit and/or accept the proposed mix of products and swaps that are displayed. The software in block 317 accepts and confirms orders, updates the information contained in the risk products table (143), the swaps table (144), the customer profile table (145) and the exchange premium history table (157) to reflect the accepted and confirmed orders. The software in block 317 also accepts input from the customer (20) regarding any new losses that the customer may have experienced. The software in block 317 verifies the loss is for an insured risk, updates the customer profile table (145), updates the exchange payout history table (146) and arranges for payment of the claim in a manner that is well known. This processing is continues until the customer (20) indicates that the session is complete. System processing advances to a software block 318.
  • The software in block 318 checks the system settings table (158) to determine if the system (100) is operating in continuous mode. If the system is operating in a continuous mode, then processing returns to block 205 and the processing described above is repeated. Alternatively, if the system is not operating in continuous mode, then processing advances to a software block 320 and stops.
  • Thus, the reader will see that the system and method described above transforms extracted transaction data, corporate information, information from external databases and information from the internet into detailed risk analyses and risk transfer programs specifically tailored to each customer using the system. The level of detail, breadth and speed of the risk analysis allows customers and managers of the system to manage their risks in an fashion that is superior to the method currently available to users of existing risk analysis systems and traditional insurance products.
  • Because the profiles used in the system (100) provide a comprehensive picture of the financial status of the companies transferring risk through the exchange, the system and method described herein can be used with essentially no modifications to provide an on-line transfer system for:
  • 1. Foreign exchange;
  • 2. Capital (aka liquidity);
  • 3. Any combination of foreign exchange, capital and risk.
  • The system described herein could be used to manage transfers of ownership rights alone or in combination with foreign exchange, liquidity and risk.
  • While the above description contains many specificities, these should not be construed as limitations on the scope of the invention, but rather as an exemplification of one embodiment thereof. Accordingly, the scope of the invention should be determined not by the embodiment illustrated, but by the appended claims and their legal equivalents.

Claims (12)

1. A swap for transferring an element of value risk
where an element of value is selected from the group consisting of alliances, brands, channels, customers, customer relationships, employees, equipment, information technology, intellectual property, partnerships, processes, supply chains, vendors, vendor relationships and combinations thereof.
2. The swap of claim 1 wherein an element of value risk is selected from the group consisting event risks, contingent liabilities, variability risks, strategic risks, volatility risks and combinations thereof.
3. The swap of claim 1 that further comprises a swap transaction completed in accordance with the applicable provisions of an International Swaps and Derivatives Association Master Agreement.
4. The swap of claim 1 wherein a swap for transfering an element of value risk further comprises a swap that reduces an overall risk of both parties to the swap transaction.
5. A swap for transferring a value impact of an element of value risk
where an element of value is selected from the group consisting of alliances, brands, channels, customers, customer relationships, employees, equipment, information technology, intellectual property, partnerships, processes, supply chains, vendors, vendor relationships and combinations thereof.
6. The swap of claim 5 wherein an element of value risk is selected from the group consisting event risks, contingent liabilities, variability risks, strategic risks, volatility risks and combinations thereof.
7. The swap of claim 5 that further comprises a swap transaction completed in accordance with the applicable provisions of an International Swaps and Derivatives Association Master Agreement.
8. The swap of claim 5 wherein a swap for transfering a value impact of an element of value risk further comprises a swap that reduces an overall risk of both parties to the swap transaction.
9. An insurance policy for transferring a value impact of an element of value risk or external factor risk
where an element of value is selected from the group consisting of alliances, brands, channels, customers, customer relationships, employees, equipment, information technology, intellectual property, partnerships, processes, supply chains, vendors, vendor relationships and combinations thereof.
10. The insurance policy of claim 9 wherein an element of value risk is selected from the group consisting event risks, contingent liabilities, variability risks, strategic risks, volatility risks and combinations thereof.
11. The insurance policy of claim 9 wherein an external factor is selected from the group consisting of a commodity price, an inflation rate, a gross domestic product, an interest rate, an insider trading level, a consumer confidence measure, a measure of organization performance against expectations, an unemployment rate and combinations thereof.
12. The insurance policy of claim 9 that is underwritten by a method comprising
aggregating data from a plurality of management systems for each of a plurality of customers,
analyzing said data as required to determine available cash, expected magnitude, expected frequency and probable value impact for a plurality of risks for each of a plurality of customers by element of value and external factor from said data,
combining the customer risk and value impact data with a plurality of data regarding a risk transfer operation, and
analyzing the combined customer and risk transfer operation data as required to determine a price for a plurality of insurance policies for transferring risk by element of value or external factor, and
offering said insurance policies for sale.
US11/278,423 2000-10-17 2006-04-01 Value impact risk transfer products Abandoned US20060184570A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/278,423 US20060184570A1 (en) 2000-10-17 2006-04-01 Value impact risk transfer products

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US68898300A 2000-10-17 2000-10-17
US10/329,172 US20040236673A1 (en) 2000-10-17 2002-12-23 Collaborative risk transfer system
US11/278,423 US20060184570A1 (en) 2000-10-17 2006-04-01 Value impact risk transfer products

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/329,172 Continuation US20040236673A1 (en) 2000-10-17 2002-12-23 Collaborative risk transfer system

Publications (1)

Publication Number Publication Date
US20060184570A1 true US20060184570A1 (en) 2006-08-17

Family

ID=33098506

Family Applications (10)

Application Number Title Priority Date Filing Date
US10/329,172 Pending US20040236673A1 (en) 2000-10-17 2002-12-23 Collaborative risk transfer system
US10/821,504 Abandoned US20040199445A1 (en) 2000-10-17 2004-04-09 Business activity management system
US11/360,087 Abandoned US20060143115A1 (en) 2000-10-17 2006-02-23 Enterprise risk management system
US11/278,423 Abandoned US20060184570A1 (en) 2000-10-17 2006-04-01 Value impact risk transfer products
US11/278,419 Abandoned US20060184449A1 (en) 2000-10-17 2006-04-01 A risk management system for securities
US12/185,093 Abandoned US20080288394A1 (en) 2000-10-17 2008-08-03 Risk management system
US12/271,846 Abandoned US20090070182A1 (en) 2000-10-17 2008-11-15 Organization activity management system
US12/356,505 Expired - Fee Related US8185486B2 (en) 2000-10-17 2009-01-20 Segmented predictive model system
US13/548,095 Expired - Fee Related US8694455B2 (en) 2000-10-17 2012-07-12 Automated risk transfer system
US13/740,223 Abandoned US20130132163A1 (en) 2000-10-17 2013-01-13 Automated risk transfer system

Family Applications Before (3)

Application Number Title Priority Date Filing Date
US10/329,172 Pending US20040236673A1 (en) 2000-10-17 2002-12-23 Collaborative risk transfer system
US10/821,504 Abandoned US20040199445A1 (en) 2000-10-17 2004-04-09 Business activity management system
US11/360,087 Abandoned US20060143115A1 (en) 2000-10-17 2006-02-23 Enterprise risk management system

Family Applications After (6)

Application Number Title Priority Date Filing Date
US11/278,419 Abandoned US20060184449A1 (en) 2000-10-17 2006-04-01 A risk management system for securities
US12/185,093 Abandoned US20080288394A1 (en) 2000-10-17 2008-08-03 Risk management system
US12/271,846 Abandoned US20090070182A1 (en) 2000-10-17 2008-11-15 Organization activity management system
US12/356,505 Expired - Fee Related US8185486B2 (en) 2000-10-17 2009-01-20 Segmented predictive model system
US13/548,095 Expired - Fee Related US8694455B2 (en) 2000-10-17 2012-07-12 Automated risk transfer system
US13/740,223 Abandoned US20130132163A1 (en) 2000-10-17 2013-01-13 Automated risk transfer system

Country Status (1)

Country Link
US (10) US20040236673A1 (en)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040078328A1 (en) * 2002-02-07 2004-04-22 Talbert Vincent W. Method and system for completing a transaction between a customer and a merchant
US20060229996A1 (en) * 2005-04-11 2006-10-12 I4 Licensing Llc Consumer processing system and method
US20060226216A1 (en) * 2005-04-11 2006-10-12 I4 Licensing Llc Method and system for risk management in a transaction
US20060229974A1 (en) * 2005-04-11 2006-10-12 I4 Licensing Llc Method of extending credit to at least one consumer and method of processing a transaction between a consumer and a merchant
US20070288375A1 (en) * 2004-02-23 2007-12-13 I4 Licensing Llc Computer-Implemented Method, System and Apparatus for the Dynamic Verification of a Consumer Engaged in a Transaction with a Merchant and Authorization of the Transaction
US20080167956A1 (en) * 2007-01-09 2008-07-10 I4 Commerce Inc. Method and system for offering a credit product by a credit issuer to a consumer at a point-of sale
US20080203153A1 (en) * 2007-02-26 2008-08-28 I4 Commerce Inc. Method and system for engaging in a transaction between a consumer and a merchant
US20090043637A1 (en) * 2004-06-01 2009-02-12 Eder Jeffrey Scott Extended value and risk management system
US20090187610A1 (en) * 2008-01-22 2009-07-23 Oracle International Corporation Persistent multimedia content versioning
US8001040B2 (en) 2005-01-25 2011-08-16 Ebay Inc. Computer-implemented method and system for dynamic consumer rating in a transaction
US8719164B2 (en) 2008-06-19 2014-05-06 Bill Me Later, Inc. Method and system for engaging in a transaction between a business entity and a merchant
US10580070B2 (en) 2007-05-02 2020-03-03 Paypal, Inc. Distributed system for commerce

Families Citing this family (178)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020046143A1 (en) * 1995-10-03 2002-04-18 Eder Jeffrey Scott Method of and system for evaluating cash flow and elements of a business enterprise
US10839321B2 (en) * 1997-01-06 2020-11-17 Jeffrey Eder Automated data storage system
US20050119922A1 (en) * 1997-01-06 2005-06-02 Eder Jeff S. Method of and system for analyzing, modeling and valuing elements of a business enterprise
US20020038217A1 (en) * 2000-04-07 2002-03-28 Alan Young System and method for integrated data analysis and management
US20040193503A1 (en) * 2000-10-04 2004-09-30 Eder Jeff Scott Interactive sales performance management system
US20040236673A1 (en) * 2000-10-17 2004-11-25 Eder Jeff Scott Collaborative risk transfer system
US7415432B1 (en) * 2000-11-17 2008-08-19 D.E. Shaw & Co., Inc. Method and apparatus for the receipt, combination, and evaluation of equity portfolios for execution by a sponsor at passively determined prices
US7720703B1 (en) * 2001-02-05 2010-05-18 Trimble Navigation Limited System and method for tracking and managing construction projects
US7283975B2 (en) * 2001-02-05 2007-10-16 Broughton W Curtis System and method for tracking and managing construction projects
US7398271B1 (en) * 2001-04-16 2008-07-08 Yahoo! Inc. Using network traffic logs for search enhancement
US7246080B2 (en) * 2001-06-08 2007-07-17 International Business Machines Corporation Apparatus, system and method for measuring and monitoring supply chain risk
US20020198750A1 (en) * 2001-06-21 2002-12-26 Innes Bruce Donald Risk management application and method
US7739176B2 (en) * 2001-07-10 2010-06-15 The Boeing Company System, method and computer program product for performing a contingent claim valuation of an early-launch option
US7747504B2 (en) * 2001-07-10 2010-06-29 The Boeing Company System, method and computer program product for determining a minimum asset value for exercising a contingent claim of an option
US7676413B2 (en) * 2001-07-10 2010-03-09 The Boeing Company System, method and computer program product for determining a minimum asset value for exercising a contingent claim of an option
US7747503B2 (en) 2001-07-10 2010-06-29 The Boeing Company System, method and computer program product for determining a minimum asset value for exercising a contingent claim of an option
US7676412B2 (en) * 2001-07-10 2010-03-09 The Boeing Company System, method and computer program product for determining a minimum asset value for exercising a contingent claim of an option
US20040249642A1 (en) 2003-06-03 2004-12-09 The Boeing Company Systems, methods and computer program products for modeling uncertain future benefits
US7752113B2 (en) * 2001-07-10 2010-07-06 The Boeing Company System, method and computer program product for performing a contingent claim valuation of a multi-stage option
US7698189B2 (en) * 2001-07-10 2010-04-13 The Boeing Company System, method and computer program product for determining a minimum asset value for exercising a contingent claim of an option
US6862579B2 (en) * 2001-07-10 2005-03-01 The Boeing Company Systems, methods and computer program products for performing a generalized contingent claim valuation
US20080027769A1 (en) 2002-09-09 2008-01-31 Jeff Scott Eder Knowledge based performance management system
US7386528B2 (en) * 2002-05-31 2008-06-10 American Express Travel Related Services Company, Inc. System and method for acquisition, assimilation and storage of information
US7711539B1 (en) * 2002-08-12 2010-05-04 Netapp, Inc. System and method for emulating SCSI reservations using network file access protocols
US20050097065A1 (en) * 2002-10-11 2005-05-05 Vivecon Corporation System and method for analyzing relationships between sourcing variables
US20040098300A1 (en) * 2002-11-19 2004-05-20 International Business Machines Corporation Method, system, and storage medium for optimizing project management and quality assurance processes for a project
US20040177335A1 (en) * 2003-03-04 2004-09-09 International Business Machines Corporation Enterprise services application program development model
US7769628B2 (en) * 2003-06-03 2010-08-03 The Boeing Company Systems, methods and computer program products for modeling uncertain future demand, supply and associated profitability of a good
US7739166B2 (en) * 2003-06-03 2010-06-15 The Boeing Company Systems, methods and computer program products for modeling demand, supply and associated profitability of a good in a differentiated market
US7627494B2 (en) 2003-06-03 2009-12-01 The Boeing Company Systems, methods and computer program products for modeling a monetary measure for a good based upon technology maturity levels
US7627495B2 (en) * 2003-06-03 2009-12-01 The Boeing Company Systems, methods and computer program products for modeling demand, supply and associated profitability of a good
US20050021380A1 (en) * 2003-07-25 2005-01-27 Taylor Stephen W. Strategic level quality assurance system for business development
US20050108080A1 (en) * 2003-11-18 2005-05-19 Peterson Gary E. Interactive risk management system and method
US7707511B2 (en) * 2003-11-18 2010-04-27 Gary Edward Peterson Interactive risk management system and method
US7756790B2 (en) 2004-02-23 2010-07-13 Coventry First Llc Life settlement/settlement with paid-up policy system and method
US7996462B2 (en) * 2004-07-30 2011-08-09 Sap Ag Collaborative agent for a work environment
US8639604B1 (en) 2004-10-26 2014-01-28 Invest N Retire, LLC System and method for managing tax-deferred retirement accounts
US7533092B2 (en) * 2004-10-28 2009-05-12 Yahoo! Inc. Link-based spam detection
US7680752B1 (en) * 2005-01-06 2010-03-16 Parasoft Corporation System and method for predictive process management
US8103565B2 (en) * 2005-02-10 2012-01-24 Coventry First Llc Method and system for enabling a life insurance premium loan
US20060206405A1 (en) * 2005-03-11 2006-09-14 Scott Gambill Gambill stock oscillator
US8713025B2 (en) 2005-03-31 2014-04-29 Square Halt Solutions, Limited Liability Company Complete context search system
US20060229921A1 (en) * 2005-04-08 2006-10-12 Mr. Patrick Colbeck Business Control System
US20060247943A1 (en) * 2005-04-29 2006-11-02 Millennium Ventures Group System and method for generating and evaluating an innovation
US7624054B2 (en) * 2005-08-25 2009-11-24 Sas Institute Inc. Financial risk mitigation optimization systems and methods
US7698188B2 (en) * 2005-11-03 2010-04-13 Beta-Rubicon Technologies, Llc Electronic enterprise capital marketplace and monitoring apparatus and method
US10083481B2 (en) * 2006-02-02 2018-09-25 Oracle America, Inc. IT risk management framework and methods
US8429177B2 (en) * 2006-02-08 2013-04-23 Yahoo! Inc. Using exceptional changes in webgraph snapshots over time for internet entity marking
US9129290B2 (en) * 2006-02-22 2015-09-08 24/7 Customer, Inc. Apparatus and method for predicting customer behavior
US8275637B1 (en) * 2006-05-02 2012-09-25 Allstate Insurance Company Earnings at risk method and system
US7792731B2 (en) * 2006-05-16 2010-09-07 Financial Industry Regulatory Authority, Inc. Capital-adequacy filing and assessment system and method
US20080052211A1 (en) * 2006-06-14 2008-02-28 Buerger Alan H Method and system for protecting an investment of a life insurance policy
US7844530B2 (en) 2006-07-31 2010-11-30 Insight Catastrophe Solutions Apparatuses, methods, and systems for providing a risk scoring engine user interface
US8090600B2 (en) 2006-07-31 2012-01-03 Insight Catastrophe Solutions Apparatuses, methods, and systems for building a risk evaluation product
US7844529B2 (en) 2006-07-31 2010-11-30 Insight Catastrophe Solutions Apparatuses, methods, and systems for providing a reconfigurable insurance quote generator user interface
US20080154700A1 (en) * 2006-12-19 2008-06-26 Celeritasworks, Llc Campaign awareness management systems and methods
US10339539B2 (en) 2006-12-19 2019-07-02 Celeritasworks, Llc Campaign awareness management systems and methods
US10783526B2 (en) 2006-12-19 2020-09-22 Celeritasworks, Llc Campaign awareness management systems and methods
US7930290B2 (en) * 2007-01-12 2011-04-19 Microsoft Corporation Providing virtual really simple syndication (RSS) feeds
US7840468B2 (en) * 2007-02-05 2010-11-23 Jpmorgan Chase Bank, N.A. System and method for a risk management framework for hedging mortality risk in portfolios having mortality-based exposure
WO2008101004A1 (en) * 2007-02-13 2008-08-21 Sohail Jaffar Zarawani System and method for just-in-time capital investment and controlled cost insurance
US8290986B2 (en) * 2007-06-27 2012-10-16 Yahoo! Inc. Determining quality measures for web objects based on searcher behavior
US20090013033A1 (en) * 2007-07-06 2009-01-08 Yahoo! Inc. Identifying excessively reciprocal links among web entities
US20090030761A1 (en) * 2007-07-09 2009-01-29 Infosys Technologies Ltd. Predicting financial impact of business framework
US9064284B1 (en) 2007-09-27 2015-06-23 United Services Automobile Association (Usaa) System and method of providing a financial investment recommendation using a portfolio planner
WO2009065222A1 (en) * 2007-11-20 2009-05-28 Loyaltymatch Inc. Trading platform for rewards earned from multiple loyalty programs
US20090222415A1 (en) * 2008-03-03 2009-09-03 Hitachi, Ltd. Evaluating risk of information mismanagement in computer storage
US8407118B1 (en) * 2008-03-31 2013-03-26 Intuit Inc. Method and system for generating an economic indicator using aggregated financial data
US20090292546A1 (en) * 2008-05-20 2009-11-26 Aleixo Jeffrey A Human Resources Employment Method
US8788247B2 (en) * 2008-08-20 2014-07-22 International Business Machines Corporation System and method for analyzing effectiveness of distributing emergency supplies in the event of disasters
US9047575B2 (en) * 2009-05-04 2015-06-02 Oracle International Corporation Creative process modeling and tracking system
WO2010141558A2 (en) * 2009-06-03 2010-12-09 Ten-Sixty Asset Management System for modeling investment performance
US20110016058A1 (en) * 2009-07-14 2011-01-20 Pinchuk Steven G Method of predicting a plurality of behavioral events and method of displaying information
US20110196808A1 (en) * 2009-08-03 2011-08-11 Kamal Mustafa System and Method for Directors and Officers Risk Assessment
WO2011017366A1 (en) * 2009-08-03 2011-02-10 Invictus Consulting Group Llc System and method for risk assessment
US20120059750A1 (en) * 2009-08-03 2012-03-08 Kamal Mustafa System and Method for Regulatory Assessment of Financial Institutions
US8768930B2 (en) 2009-10-10 2014-07-01 Oracle International Corporation Product classification in procurement systems
US8688501B2 (en) * 2010-01-20 2014-04-01 International Business Machines Corporation Method and system enabling dynamic composition of heterogenous risk models
US8473431B1 (en) 2010-05-14 2013-06-25 Google Inc. Predictive analytic modeling platform
US8438122B1 (en) 2010-05-14 2013-05-07 Google Inc. Predictive analytic modeling platform
US20120004946A1 (en) * 2010-07-01 2012-01-05 Bank Of America Corporation Integrated Operational Risk Management
US8719207B2 (en) * 2010-07-27 2014-05-06 Oracle International Corporation Method and system for providing decision making based on sense and respond
US20120046989A1 (en) * 2010-08-17 2012-02-23 Bank Of America Corporation Systems and methods for determining risk outliers and performing associated risk reviews
US8566745B2 (en) * 2010-10-29 2013-10-22 Hewlett-Packard Development Company, L.P. Method and system for project and portfolio management
US10360527B2 (en) * 2010-11-10 2019-07-23 International Business Machines Corporation Casual modeling of multi-dimensional hierarchical metric cubes
WO2012102749A1 (en) * 2011-01-24 2012-08-02 Axioma, Inc. Methods and apparatus for improving factor risk model responsiveness
US8533222B2 (en) * 2011-01-26 2013-09-10 Google Inc. Updateable predictive analytical modeling
US8595154B2 (en) 2011-01-26 2013-11-26 Google Inc. Dynamic predictive modeling platform
KR101339800B1 (en) * 2011-02-25 2013-12-10 성균관대학교산학협력단 Apparatus and method for pss activity modeling
US8768812B2 (en) 2011-05-02 2014-07-01 The Boeing Company System, method and computer-readable storage medium for valuing a performance option
US8533224B2 (en) 2011-05-04 2013-09-10 Google Inc. Assessing accuracy of trained predictive models
US9268828B2 (en) * 2011-06-15 2016-02-23 Sas Institute Inc. Computer-implemented systems and methods for extract, transform, and load user interface processing
US20130024395A1 (en) * 2011-07-22 2013-01-24 Thomson Reuters (Markets) Llc System and method for constructing outperforming portfolios relative to target benchmarks
US9092821B2 (en) 2011-10-20 2015-07-28 Ashbury Heights Capital, Llc Method for estimating flows between economic entities
US10803028B2 (en) * 2011-12-21 2020-10-13 Sybase, Inc. Multiphase approach to data availability
US20130297627A1 (en) * 2012-05-07 2013-11-07 Sandeep J. Shah Business intelligence engine
US9779260B1 (en) 2012-06-11 2017-10-03 Dell Software Inc. Aggregation and classification of secure data
CN102855524A (en) * 2012-08-14 2013-01-02 贵州乌江水电开发有限责任公司 Carry-over storage year-end fluctuating level prediction method and system
US8788439B2 (en) * 2012-12-21 2014-07-22 InsideSales.com, Inc. Instance weighted learning machine learning model
US9460401B2 (en) 2012-08-20 2016-10-04 InsideSales.com, Inc. Using machine learning to predict behavior based on local conditions
US10127292B2 (en) * 2012-12-03 2018-11-13 Ut-Battelle, Llc Knowledge catalysts
US20140244343A1 (en) * 2013-02-22 2014-08-28 Bank Of America Corporation Metric management tool for determining organizational health
US9231979B2 (en) * 2013-03-14 2016-01-05 Sas Institute Inc. Rule optimization for classification and detection
US9594907B2 (en) 2013-03-14 2017-03-14 Sas Institute Inc. Unauthorized activity detection and classification
US10643276B1 (en) * 2013-03-15 2020-05-05 Capital One Services, Llc Systems and computer-implemented processes for model-based underwriting
CA2853346A1 (en) * 2013-06-04 2014-12-04 Robert Russell Lunan Automated accounting method
US9892178B2 (en) 2013-09-19 2018-02-13 Workday, Inc. Systems and methods for interest-driven business intelligence systems including event-oriented data
US10242407B1 (en) 2013-09-24 2019-03-26 Innovative Market Analysis, LLC Financial instrument analysis and forecast
US9407676B2 (en) 2013-11-25 2016-08-02 At&T Intellectual Property I, Lp Method and apparatus for distributing media content
GB2534806A (en) * 2013-12-02 2016-08-03 Finmason Inc Systems and methods for financial asset analysis
US20150154695A1 (en) * 2013-12-03 2015-06-04 Mastercard International Corporation Forecasting lagged current transactions based on prior transactions
US9558490B2 (en) * 2014-02-21 2017-01-31 Mastercard International Incorporated Systems and methods for predicting a merchant's change of acquirer
US10810671B2 (en) * 2014-06-27 2020-10-20 Chicago Mercantile Exchange Inc. Interest rate swap compression
US10565647B1 (en) * 2014-08-19 2020-02-18 Next Level Derivatives Llc Secure multi-server interest rate based instrument trading system and methods of increasing efficiency thereof
US20160086278A1 (en) * 2014-09-24 2016-03-24 Axioma, Inc. Risk Factor Splitting
US9720939B1 (en) 2014-09-26 2017-08-01 Jpmorgan Chase Bank, N.A. Method and system for implementing categorically organized relationship effects
US9540118B2 (en) 2014-11-10 2017-01-10 Federal Express Corporation Risk assessment framework
US20160180262A1 (en) * 2014-12-22 2016-06-23 Tom Brauer System and method for testing enterprise transactions
US10326748B1 (en) 2015-02-25 2019-06-18 Quest Software Inc. Systems and methods for event-based authentication
US10460275B2 (en) 2015-02-27 2019-10-29 International Business Machines Corporation Predictive model search by communicating comparative strength
US10417613B1 (en) 2015-03-17 2019-09-17 Quest Software Inc. Systems and methods of patternizing logged user-initiated events for scheduling functions
US9990506B1 (en) 2015-03-30 2018-06-05 Quest Software Inc. Systems and methods of securing network-accessible peripheral devices
US9842220B1 (en) 2015-04-10 2017-12-12 Dell Software Inc. Systems and methods of secure self-service access to content
US20190114549A1 (en) * 2015-05-11 2019-04-18 Daniel Joseph Olsher Systems and Methods for a Universal Task Independent Simulation and Control Platform for Generating Controlled Actions Using Nuanced Artificial Intelligence
US10536352B1 (en) 2015-08-05 2020-01-14 Quest Software Inc. Systems and methods for tuning cross-platform data collection
US9946879B1 (en) * 2015-08-27 2018-04-17 Amazon Technologies, Inc. Establishing risk profiles for software packages
US10218588B1 (en) 2015-10-05 2019-02-26 Quest Software Inc. Systems and methods for multi-stream performance patternization and optimization of virtual meetings
US10157358B1 (en) 2015-10-05 2018-12-18 Quest Software Inc. Systems and methods for multi-stream performance patternization and interval-based prediction
US20170111245A1 (en) * 2015-10-14 2017-04-20 International Business Machines Corporation Process traces clustering: a heterogeneous information network approach
US10142391B1 (en) 2016-03-25 2018-11-27 Quest Software Inc. Systems and methods of diagnosing down-layer performance problems via multi-stream performance patternization
US10656979B2 (en) 2016-03-31 2020-05-19 International Business Machines Corporation Structural and temporal semantics heterogeneous information network (HIN) for process trace clustering
US10373267B2 (en) 2016-04-29 2019-08-06 Intuit Inc. User data augmented propensity model for determining a future financial requirement
US10445839B2 (en) 2016-04-29 2019-10-15 Intuit Inc. Propensity model for determining a future financial requirement
US10855625B1 (en) * 2016-05-11 2020-12-01 Workato, Inc. Intelligent, adaptable, and trainable bot that orchestrates automation and workflows across multiple applications
US11107027B1 (en) 2016-05-31 2021-08-31 Intuit Inc. Externally augmented propensity model for determining a future financial requirement
US10671952B1 (en) 2016-06-01 2020-06-02 Intuit Inc. Transmission of a message based on the occurrence of a workflow event and the output of an externally augmented propensity model identifying a future financial requirement
US10600748B2 (en) * 2016-06-20 2020-03-24 Samsung Electronics Co., Ltd. Fan-out semiconductor package
WO2017220140A1 (en) * 2016-06-22 2017-12-28 Swiss Reinsurance Company Ltd. Life insurance system with fully automated underwriting process for real-time underwriting and risk adjustment, and corresponding method thereof
US20180040064A1 (en) * 2016-08-04 2018-02-08 Xero Limited Network-based automated prediction modeling
US10540155B1 (en) * 2016-08-11 2020-01-21 Tibco Software Inc. Platform-agnostic predictive models based on database management system instructions
WO2018046102A1 (en) * 2016-09-10 2018-03-15 Swiss Reinsurance Company Ltd. Automated, telematics-based system with score-driven triggering and operation of automated sharing economy risk-transfer systems and corresponding method thereof
US20180260903A1 (en) * 2017-03-10 2018-09-13 Brian Callery Computerized machine learning based recommendations
US10558769B2 (en) 2017-05-01 2020-02-11 Goldman Sachs & Co. LLC Systems and methods for scenario simulation
US20190294633A1 (en) * 2017-05-01 2019-09-26 Goldman Sachs & Co. LLC Systems and methods for scenario simulation
TWI664598B (en) * 2017-05-23 2019-07-01 第一商業銀行股份有限公司 Financial service method with point of sale terminal
US10997672B2 (en) * 2017-05-31 2021-05-04 Intuit Inc. Method for predicting business income from user transaction data
US10417039B2 (en) 2017-06-12 2019-09-17 Microsoft Technology Licensing, Llc Event processing using a scorable tree
US10902533B2 (en) 2017-06-12 2021-01-26 Microsoft Technology Licensing, Llc Dynamic event processing
US11393045B2 (en) * 2017-06-27 2022-07-19 Fin Box Technologies, Inc. Methods and systems for efficient delivery of accounting and corporate planning services
US10803533B2 (en) * 2017-06-27 2020-10-13 Fin Box Technologies, Inc. Methods and systems for efficient delivery of accounting and corporate planning services
CN109697282B (en) 2017-10-20 2023-06-06 阿里巴巴集团控股有限公司 Sentence user intention recognition method and device
US11861024B1 (en) 2018-01-26 2024-01-02 Wells Fargo Bank, N.A. Systems and methods for data risk assessment
US20200242700A1 (en) * 2018-02-08 2020-07-30 2Bc Innovations, Llc Riving longevity-contingent instruments
US20200402167A1 (en) * 2018-02-08 2020-12-24 2Bc Innovations, Llc Updating a portfolio of blockchain-encoded rived longevity-contingent instruments
US20200364708A1 (en) * 2018-02-08 2020-11-19 2Bc Innovations, Llc Generating a portfolio of blockchain-encoded rived longevity-contingent instruments
US11468339B2 (en) * 2018-06-29 2022-10-11 Sap Se Agnostic data structure for debriefing predictive software
US11156995B2 (en) 2018-08-22 2021-10-26 Ohio State Innovation Foundation Systems and methods for real-time data processing and for emergency planning
US11727020B2 (en) 2018-10-11 2023-08-15 International Business Machines Corporation Artificial intelligence based problem descriptions
US10997553B2 (en) 2018-10-29 2021-05-04 DIGIBILT, Inc. Method and system for automatically creating a bill of materials
US11030709B2 (en) 2018-10-29 2021-06-08 DIGIBILT, Inc. Method and system for automatically creating and assigning assembly labor activities (ALAs) to a bill of materials (BOM)
TWI699727B (en) * 2018-12-25 2020-07-21 財團法人商業發展研究院 Apparatus and method for estimate fund risk
US11461726B2 (en) * 2019-01-21 2022-10-04 Adp, Inc. Business insight generation system
US11216742B2 (en) 2019-03-04 2022-01-04 Iocurrents, Inc. Data compression and communication using machine learning
CN109919767B (en) * 2019-03-07 2023-01-06 腾讯科技(深圳)有限公司 Transaction risk management method, device and equipment
US11661195B2 (en) 2019-03-13 2023-05-30 Federal Express Corporation Mitigating operational risk in aircraft
JP6675721B1 (en) * 2019-05-06 2020-04-01 Assest株式会社 Loan credit evaluation program and system
US11308428B2 (en) * 2019-07-09 2022-04-19 International Business Machines Corporation Machine learning-based resource customization to increase user satisfaction
CN110909992A (en) * 2019-11-11 2020-03-24 北京明略软件系统有限公司 Risk prediction method, device and equipment
US11830291B2 (en) * 2020-02-10 2023-11-28 University Of Maryland, College Park System and method for multimodal emotion recognition
US11615366B2 (en) * 2020-04-15 2023-03-28 EMC IP Holding Company LLC Evaluation of product-related data structures using machine-learning techniques
CN111414999B (en) * 2020-04-27 2023-08-22 新奥新智科技有限公司 Method and device for monitoring running state of equipment
US20220092534A1 (en) * 2020-09-18 2022-03-24 International Business Machines Corporation Event-based risk assessment
US11816451B2 (en) * 2021-02-16 2023-11-14 Hcl Technologies Limited Method and system for identifying common requirements from applications
CN113516333B (en) * 2021-03-10 2023-11-14 福建省农村信用社联合社 Performance test method and system based on accurate business model
US11669898B2 (en) * 2021-03-16 2023-06-06 S&P Global Inc. System for estimating distance-to-default credit risk
EP4075352A1 (en) * 2021-04-16 2022-10-19 Tata Consultancy Services Limited Method and system for providing intellectual property adoption recommendations to an enterprise
US20230004538A1 (en) * 2021-06-30 2023-01-05 Dell Products L.P. Database gateway with machine learning model
US11695839B1 (en) 2022-05-31 2023-07-04 Bank Of America Corporation Real-time, intelligent pairing and prioritizing of client and server data queues using ultra-wide band

Citations (78)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3749892A (en) * 1971-02-16 1973-07-31 Qeleg Ltd Accountancy system
US3933305A (en) * 1974-08-23 1976-01-20 John Michael Murphy Asset value calculators
US4839304A (en) * 1986-12-18 1989-06-13 Nec Corporation Method of making a field effect transistor with overlay gate structure
US4989141A (en) * 1987-06-01 1991-01-29 Corporate Class Software Computer system for financial analyses and reporting
US5128861A (en) * 1988-12-07 1992-07-07 Hitachi, Ltd. Inventory control method and system
US5191522A (en) * 1990-01-18 1993-03-02 Itt Corporation Integrated group insurance information processing and reporting system based upon an enterprise-wide data structure
US5193055A (en) * 1987-03-03 1993-03-09 Brown Gordon T Accounting system
US5224034A (en) * 1990-12-21 1993-06-29 Bell Communications Research, Inc. Automated system for generating procurement lists
US5237495A (en) * 1990-05-23 1993-08-17 Fujitsu Limited Production/purchase management processing system and method
US5237946A (en) * 1989-01-23 1993-08-24 Copson Alex G Apparatus and method for transferring material to subaqueous levels
US5317504A (en) * 1991-10-23 1994-05-31 T.A.S. & Trading Co., Ltd. Computer implemented process for executing accounting theory systems
US5361201A (en) * 1992-10-19 1994-11-01 Hnc, Inc. Real estate appraisal using predictive modeling
US5406477A (en) * 1991-08-30 1995-04-11 Digital Equipment Corporation Multiple reasoning and result reconciliation for enterprise analysis
US5414621A (en) * 1992-03-06 1995-05-09 Hough; John R. System and method for computing a comparative value of real estate
US5435565A (en) * 1994-07-18 1995-07-25 Benaderet; David M. Board game relating to stress
US5471611A (en) * 1991-03-13 1995-11-28 University Of Strathclyde Computerised information-retrieval database systems
US5542420A (en) * 1993-04-30 1996-08-06 Goldman; Arnold J. Personalized method and system for storage, communication, analysis, and processing of health-related data
US5644727A (en) * 1987-04-15 1997-07-01 Proprietary Financial Products, Inc. System for the operation and management of one or more financial accounts through the use of a digital communication and computation system for exchange, investment and borrowing
US5649181A (en) * 1993-04-16 1997-07-15 Sybase, Inc. Method and apparatus for indexing database columns with bit vectors
US5668591A (en) * 1994-03-30 1997-09-16 Sony Corporation Information terminal apparatus that is remotely programmed by radio waves and that displays input keys of program functions on a display
US5680305A (en) * 1995-02-16 1997-10-21 Apgar, Iv; Mahlon System and method for evaluating real estate
US5704055A (en) * 1993-06-01 1997-12-30 International Business Machines Corporation Dynamic Reconfiguration of main storage and expanded storage by means of a service call logical processor
US5704045A (en) * 1995-01-09 1997-12-30 King; Douglas L. System and method of risk transfer and risk diversification including means to assure with assurance of timely payment and segregation of the interests of capital
US5706495A (en) * 1996-05-07 1998-01-06 International Business Machines Corporation Encoded-vector indices for decision support and warehousing
US5737581A (en) * 1995-08-30 1998-04-07 Keane; John A. Quality system implementation simulator
US5742775A (en) * 1995-01-18 1998-04-21 King; Douglas L. Method and apparatus of creating financial instrument and administering an adjustable rate loan system
US5774873A (en) * 1996-03-29 1998-06-30 Adt Automotive, Inc. Electronic on-line motor vehicle auction and information system
US5794219A (en) * 1996-02-20 1998-08-11 Health Hero Network, Inc. Method of conducting an on-line auction with bid pooling
US5802501A (en) * 1992-10-28 1998-09-01 Graff/Ross Holdings System and methods for computing to support decomposing property into separately valued components
US5809282A (en) * 1995-06-07 1998-09-15 Grc International, Inc. Automated network simulation and optimization system
US5812988A (en) * 1993-12-06 1998-09-22 Investments Analytic, Inc. Method and system for jointly estimating cash flows, simulated returns, risk measures and present values for a plurality of assets
US5812987A (en) * 1993-08-18 1998-09-22 Barclays Global Investors, National Association Investment fund management method and system with dynamic risk adjusted allocation of assets
US5819237A (en) * 1996-02-13 1998-10-06 Financial Engineering Associates, Inc. System and method for determination of incremental value at risk for securities trading
US5875431A (en) * 1996-03-15 1999-02-23 Heckman; Frank Legal strategic analysis planning and evaluation control system and method
US5951300A (en) * 1997-03-10 1999-09-14 Health Hero Network Online system and method for providing composite entertainment and health information
US5985559A (en) * 1997-04-30 1999-11-16 Health Hero Network System and method for preventing, diagnosing, and treating genetic and pathogen-caused disease
US6014629A (en) * 1998-01-13 2000-01-11 Moore U.S.A. Inc. Personalized health care provider directory
US6032119A (en) * 1997-01-16 2000-02-29 Health Hero Network, Inc. Personalized display of health information
US6064972A (en) * 1997-09-17 2000-05-16 At&T Corp Risk management technique for network access
US6064971A (en) * 1992-10-30 2000-05-16 Hartnett; William J. Adaptive knowledge base
US6078901A (en) * 1997-04-03 2000-06-20 Ching; Hugh Quantitative supply and demand model based on infinite spreadsheet
US6092056A (en) * 1994-04-06 2000-07-18 Morgan Stanley Dean Witter Data processing system and method for financial debt instruments
US6112188A (en) * 1992-10-30 2000-08-29 Hartnett; William J. Privatization marketplace
US6125355A (en) * 1997-12-02 2000-09-26 Financial Engines, Inc. Pricing module for financial advisory system
US6134536A (en) * 1992-05-29 2000-10-17 Swychco Infrastructure Services Pty Ltd. Methods and apparatus relating to the formulation and trading of risk management contracts
US6173276B1 (en) * 1997-08-21 2001-01-09 Scicomp, Inc. System and method for financial instrument modeling and valuation
US6189011B1 (en) * 1996-03-19 2001-02-13 Siebel Systems, Inc. Method of maintaining a network of partially replicated database system
US6209124B1 (en) * 1999-08-30 2001-03-27 Touchnet Information Systems, Inc. Method of markup language accessing of host systems and data using a constructed intermediary
US6221009B1 (en) * 1996-07-16 2001-04-24 Kyoto Daiichi Kagaku Co., Ltd. Dispersed-type testing measuring system and dispersed-type care system
US6263314B1 (en) * 1993-12-06 2001-07-17 Irah H. Donner Method of performing intellectual property (IP) audit optionally over network architecture
US6278981B1 (en) * 1997-05-29 2001-08-21 Algorithmics International Corporation Computer-implemented method and apparatus for portfolio compression
US6282531B1 (en) * 1998-06-12 2001-08-28 Cognimed, Llc System for managing applied knowledge and workflow in multiple dimensions and contexts
US6301584B1 (en) * 1997-08-21 2001-10-09 Home Information Services, Inc. System and method for retrieving entities and integrating data
US6332163B1 (en) * 1999-09-01 2001-12-18 Accenture, Llp Method for providing communication services over a computer network system
US20020002520A1 (en) * 1998-04-24 2002-01-03 Gatto Joseph G. Security analyst estimates performance viewing system and method
US20020016758A1 (en) * 2000-06-28 2002-02-07 Grigsby Calvin B. Method and apparatus for offering, pricing, and selling securities over a network
US20020023034A1 (en) * 2000-03-31 2002-02-21 Brown Roger G. Method and system for a digital automated exchange
US6366934B1 (en) * 1998-10-08 2002-04-02 International Business Machines Corporation Method and apparatus for querying structured documents using a database extender
US20020052820A1 (en) * 1998-04-24 2002-05-02 Gatto Joseph G. Security analyst estimates performance viewing system and method
US6418448B1 (en) * 1999-12-06 2002-07-09 Shyam Sundar Sarkar Method and apparatus for processing markup language specifications for data and metadata used inside multiple related internet documents to navigate, query and manipulate information from a plurality of object relational databases over the web
US6499843B1 (en) * 2000-09-13 2002-12-31 Bausch & Lomb Incorporated Customized vision correction method and business
US6510430B1 (en) * 1999-02-24 2003-01-21 Acumins, Inc. Diagnosis and interpretation methods and apparatus for a personal nutrition program
US6518069B1 (en) * 1999-04-22 2003-02-11 Liposcience, Inc. Methods and computer program products for determining risk of developing type 2 diabetes and other insulin resistance related disorders
US6518430B1 (en) * 2001-09-21 2003-02-11 Abbott Laboratories Process for the preparation of 5-(substituted)-10-methoxy-2,2,4-trimethyl-2,5-dihydro-1H-chromeno[3,4-F]quinolines and derivatives thereof
US20030083973A1 (en) * 2001-08-29 2003-05-01 Horsfall Peter R. Electronic trading system
US6576471B2 (en) * 1999-02-26 2003-06-10 Liposcience, Inc. Methods, systems, and computer program products for analyzing and presenting NMR lipoprotein-based risk assessment results
US6584507B1 (en) * 1999-03-02 2003-06-24 Cisco Technology, Inc. Linking external applications to a network management system
US6645124B1 (en) * 1998-09-18 2003-11-11 Athlon Llc Interactive programmable fitness interface system
US6654289B2 (en) * 2001-03-09 2003-11-25 Micron Technology, Inc. Non-volatile memory device with erase address register
US6671773B2 (en) * 2000-12-07 2003-12-30 Spinnaker Networks, Llc Method and system for responding to file system requests
US6684204B1 (en) * 2000-06-19 2004-01-27 International Business Machines Corporation Method for conducting a search on a network which includes documents having a plurality of tags
US6695795B2 (en) * 1999-12-27 2004-02-24 Medireha Gmbh Therapeutic device
US6732095B1 (en) * 2001-04-13 2004-05-04 Siebel Systems, Inc. Method and apparatus for mapping between XML and relational representations
US6738753B1 (en) * 2000-08-21 2004-05-18 Michael Andrew Hogan Modular, hierarchically organized artificial intelligence entity
US6757898B1 (en) * 2000-01-18 2004-06-29 Mckesson Information Solutions, Inc. Electronic provider—patient interface system
US6836773B2 (en) * 2000-09-28 2004-12-28 Oracle International Corporation Enterprise web mining system and method
US6876992B1 (en) * 2000-11-28 2005-04-05 Willis North America Inc. Method and system for risk control optimization
US7006992B1 (en) * 2000-04-06 2006-02-28 Union State Bank Risk assessment and management system

Family Cites Families (236)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4750121A (en) 1985-10-03 1988-06-07 Halley Gustavo M Pension benefits system
US4839804A (en) 1986-12-30 1989-06-13 College Savings Bank Method and apparatus for insuring the funding of a future liability of uncertain cost
US5852811A (en) * 1987-04-15 1998-12-22 Proprietary Financial Products, Inc. Method for managing financial accounts by a preferred allocation of funds among accounts
US5377327A (en) * 1988-04-22 1994-12-27 Digital Equipment Corporation Congestion avoidance scheme for computer networks
US5237496A (en) 1988-12-07 1993-08-17 Hitachi, Ltd. Inventory control method and system
US6336103B1 (en) 1989-08-02 2002-01-01 Nardin L. Baker Rapid method of analysis for correlation of asset return to future financial liabilities
US5148365A (en) * 1989-08-15 1992-09-15 Dembo Ron S Scenario optimization
CA2031765C (en) * 1989-12-08 1996-02-20 Masahide Nomura Method and system for performing control conforming with characteristics of controlled system
JPH04264957A (en) 1991-02-20 1992-09-21 Toshiba Corp Security sales decision making supporting device
US7142307B1 (en) * 1991-03-01 2006-11-28 Stark Edward W Method and apparatus for optical interactance and transmittance measurements
US5377116A (en) * 1991-07-01 1994-12-27 Valenite Inc. Method and system for designing a cutting tool
DE69327691D1 (en) 1992-07-30 2000-03-02 Teknekron Infowitch Corp Method and system for monitoring and / or controlling the performance of an organization
US5388116A (en) * 1992-09-25 1995-02-07 The Furukawa Electric Co., Ltd. Semiconductor laser device
US5675746A (en) * 1992-09-30 1997-10-07 Marshall; Paul S. Virtual reality generator for use with financial information
EP0686926A3 (en) * 1994-05-24 1996-06-12 Ron S Dembo Method and apparatus for optimal portfolio replication
US5761442A (en) * 1994-08-31 1998-06-02 Advanced Investment Technology, Inc. Predictive neural network means and method for selecting a portfolio of securities wherein each network has been trained using data relating to a corresponding security
US5768475A (en) * 1995-05-25 1998-06-16 Pavilion Technologies, Inc. Method and apparatus for automatically constructing a data flow architecture
US5887120A (en) * 1995-05-31 1999-03-23 Oracle Corporation Method and apparatus for determining theme for discourse
US5806047A (en) 1995-09-25 1998-09-08 Metlife Life Insurance Company System for combined pool portfolio
US7243081B2 (en) * 1995-10-30 2007-07-10 Efi Actuaries Method of determining optimal asset allocation utilizing asset cash flow simulation
US5774881A (en) 1995-10-30 1998-06-30 Efi Actuaries Method of determining optimal asset allocation utilizing asset cash flow simulation
US5889823A (en) * 1995-12-13 1999-03-30 Lucent Technologies Inc. Method and apparatus for compensation of linear or nonlinear intersymbol interference and noise correlation in magnetic recording channels
JP3956057B2 (en) * 1996-01-31 2007-08-08 エイエスエム アメリカ インコーポレイテッド Model reference predictive control of heat treatment
US5812404A (en) * 1996-04-18 1998-09-22 Valmet Corporation Method for overall regulation of the headbox of a paper machine or equivalent
US5825653A (en) * 1997-03-14 1998-10-20 Valmet Corporation Method for overall regulation of a former of a paper machine or equivalent
US5933345A (en) * 1996-05-06 1999-08-03 Pavilion Technologies, Inc. Method and apparatus for dynamic and steady state modeling over a desired path between two end points
US6278899B1 (en) * 1996-05-06 2001-08-21 Pavilion Technologies, Inc. Method for on-line optimization of a plant
US6493596B1 (en) * 1996-05-06 2002-12-10 Pavilion Technologies, Inc. Method and apparatus for controlling a non-linear mill
US5792062A (en) * 1996-05-14 1998-08-11 Massachusetts Institute Of Technology Method and apparatus for detecting nonlinearity in an electrocardiographic signal
US6026397A (en) * 1996-05-22 2000-02-15 Electronic Data Systems Corporation Data analysis system and method
US6909708B1 (en) * 1996-11-18 2005-06-21 Mci Communications Corporation System, method and article of manufacture for a communication system architecture including video conferencing
ATE296898T1 (en) * 1997-03-20 2005-06-15 Affymetrix Inc ITERATIVE REQUENCING
US6249315B1 (en) * 1997-03-24 2001-06-19 Jack M. Holm Strategy for pictorial digital image processing
WO1998053416A1 (en) * 1997-05-21 1998-11-26 Khimetrics, Inc. Method for controlled optimization of enterprise planning models
US5991758A (en) * 1997-06-06 1999-11-23 Madison Information Technologies, Inc. System and method for indexing information about entities from different information sources
US6012053A (en) * 1997-06-23 2000-01-04 Lycos, Inc. Computer system with user-controlled relevance ranking of search results
WO1999006935A1 (en) * 1997-08-01 1999-02-11 Monks Robert A G Entreprise simulation module
US5774761A (en) * 1997-10-14 1998-06-30 Xerox Corporation Machine set up procedure using multivariate modeling and multiobjective optimization
US6324553B1 (en) * 1997-11-26 2001-11-27 International Business Machines Corporation Apparatus and method for the manual selective blocking of images
US6029139A (en) * 1998-01-28 2000-02-22 Ncr Corporation Method and apparatus for optimizing promotional sale of products based upon historical data
US6996539B1 (en) * 1998-03-11 2006-02-07 Foliofn, Inc. Method and apparatus for enabling smaller investors or others to create and manage a portfolio of securities or other assets or liabilities on a cost effective basis
US6131089A (en) * 1998-05-04 2000-10-10 Motorola, Inc. Pattern classifier with training system and methods of operation therefor
US6347306B1 (en) * 1998-07-21 2002-02-12 Cybershift.Com, Inc. Method and system for direct payroll processing
US6317787B1 (en) * 1998-08-11 2001-11-13 Webtrends Corporation System and method for analyzing web-server log files
US6249768B1 (en) * 1998-10-29 2001-06-19 International Business Machines Corporation Strategic capability networks
US6546381B1 (en) * 1998-11-02 2003-04-08 International Business Machines Corporation Query optimization system and method
US7031963B1 (en) * 1998-11-09 2006-04-18 Unisys Corporation Green ice printout sorting and delivery program
US6381586B1 (en) * 1998-12-10 2002-04-30 International Business Machines Corporation Pricing of options using importance sampling and stratification/ Quasi-Monte Carlo
US6700923B1 (en) * 1999-01-04 2004-03-02 Board Of Regents The University Of Texas System Adaptive multiple access interference suppression
US6219649B1 (en) * 1999-01-21 2001-04-17 Joel Jameson Methods and apparatus for allocating resources in the presence of uncertainty
US6411936B1 (en) * 1999-02-05 2002-06-25 Nval Solutions, Inc. Enterprise value enhancement system and method
US6330564B1 (en) * 1999-02-10 2001-12-11 International Business Machines Corporation System and method for automated problem isolation in systems with measurements structured as a multidimensional database
US6513019B2 (en) * 1999-02-16 2003-01-28 Financial Technologies International, Inc. Financial consolidation and communication platform
US6315735B1 (en) * 1999-03-31 2001-11-13 Pulsion Medical Systems Ag Devices for in-vivo determination of the compliance function and the systemic blood flow of a living being
US7299080B2 (en) * 1999-10-08 2007-11-20 Sensys Medical, Inc. Compact apparatus for noninvasive measurement of glucose through near-infrared spectroscopy
US6411939B1 (en) 1999-05-17 2002-06-25 Offshore Benefits, Llc Computer-aided method, machine, and products produced thereby, for illustrating a replacement of a benefit plan that is viable at one location but not viable at the location of the replacement
AU5377900A (en) * 1999-06-02 2000-12-28 Algorithmics International Corp. Risk management system, distributed framework and method
WO2000075819A2 (en) * 1999-06-03 2000-12-14 Algorithmics International Corp. Risk management system and method providing rule-based evolution of a portfolio of instruments
US6591232B1 (en) * 1999-06-08 2003-07-08 Sikorsky Aircraft Corporation Method of selecting an optimum mix of resources to maximize an outcome while minimizing risk
US6654469B1 (en) * 1999-06-28 2003-11-25 Lucent Technologies Inc. Methods and devices for reducing sampling noise in analog signals using linear interpolation
US8577778B2 (en) * 1999-07-21 2013-11-05 Longitude Llc Derivatives having demand-based, adjustable returns, and trading exchange therefor
WO2001008073A1 (en) * 1999-07-23 2001-02-01 Netfolio, Inc. System and method for selecting and purchasing stocks via a global computer network
US7162427B1 (en) * 1999-08-20 2007-01-09 Electronic Data Systems Corporation Structure and method of modeling integrated business and information technology frameworks and architecture in support of a business
US6567786B1 (en) * 1999-09-16 2003-05-20 International Business Machines Corporation System and method for increasing the effectiveness of customer contact strategies
US6684193B1 (en) * 1999-10-05 2004-01-27 Rapt Technologies Corporation Method and apparatus for multivariate allocation of resources
US6654389B1 (en) 1999-11-23 2003-11-25 International Business Machines Corporation System and method for searching patterns in real-time over a shared media
CA2290888A1 (en) * 1999-11-26 2001-05-26 Algorithmics International Corp. Risk management, pricing and portfolio makeup system and method
US6654649B2 (en) * 1999-12-22 2003-11-25 Aspen Technology, Inc. Computer method and apparatus for optimized controller in a non-linear process
US7003484B2 (en) * 1999-12-30 2006-02-21 Ge Capital Commercial Finance, Inc. Methods and systems for efficiently sampling portfolios for optimal underwriting
US7346518B1 (en) * 1999-12-30 2008-03-18 At&T Bls Intellectual Property, Inc. System and method for determining the marketability of intellectual property assets
US7028005B2 (en) * 1999-12-30 2006-04-11 Ge Capital Commercial Finance, Inc. Methods and systems for finding value and reducing risk
US7039608B2 (en) * 1999-12-30 2006-05-02 Ge Capital Commercial Finance, Inc. Rapid valuation of portfolios of assets such as financial instruments
US7469227B2 (en) * 2000-02-22 2008-12-23 Strategic Analytics, Inc. Retail lending risk related scenario generation
US6671673B1 (en) 2000-03-24 2003-12-30 International Business Machines Corporation Method for integrated supply chain and financial management
US8170935B2 (en) * 2000-03-27 2012-05-01 Nyse Amex Llc Systems and methods for evaluating the integrity of a model portfolio of a financial instrument
JP4054507B2 (en) * 2000-03-31 2008-02-27 キヤノン株式会社 Voice information processing method and apparatus, and storage medium
EP1323059A2 (en) * 2000-04-05 2003-07-02 Pavilion Technologies, Inc. System and method for enterprise modelling, optimization and control
US6826521B1 (en) * 2000-04-06 2004-11-30 Abb Automation Inc. System and methodology and adaptive, linear model predictive control based on rigorous, nonlinear process model
US7006939B2 (en) * 2000-04-19 2006-02-28 Georgia Tech Research Corporation Method and apparatus for low cost signature testing for analog and RF circuits
US7212996B1 (en) * 2000-04-20 2007-05-01 Jpmorgan Chase Bank, N.A. System and method for dynamic, multivariable comparison of financial products
US6795811B1 (en) * 2000-04-26 2004-09-21 Lee Epstein Method for investing working capital
US7356504B2 (en) * 2000-05-01 2008-04-08 The Olsen Group Methods for determining value at risk
US20030069986A1 (en) * 2000-05-23 2003-04-10 Lori Petrone Electronic marketplace system and method using optimization techniques
GB0013011D0 (en) * 2000-05-26 2000-07-19 Ncr Int Inc Method and apparatus for determining one or more statistical estimators of customer behaviour
US7177822B2 (en) * 2000-08-08 2007-02-13 Daimlerchrysler Corporation Common database system for sales and marketing process
US7328183B1 (en) 2000-08-15 2008-02-05 Ltcia, Llc Computer program and method for determining the economic impact of long-term care
US20040236673A1 (en) * 2000-10-17 2004-11-25 Eder Jeff Scott Collaborative risk transfer system
KR20020054245A (en) * 2000-12-27 2002-07-06 오길록 Sensor fusion apparatus and method for optical and magnetic motion capture system
US7249089B2 (en) * 2000-12-29 2007-07-24 Hartford Fire Insurance Company Method and system for auctioning bankruptcy assets and valuing same
JP2002215423A (en) * 2001-01-22 2002-08-02 Hitachi Ltd Method of preparing software model
US6757689B2 (en) * 2001-02-02 2004-06-29 Hewlett-Packard Development Company, L.P. Enabling a zero latency enterprise
US7536332B2 (en) * 2001-02-02 2009-05-19 Rhee Thomas A Real life implementation of modern portfolio theory (MPT) for financial planning and portfolio management
WO2002071308A1 (en) * 2001-03-05 2002-09-12 The Ohio State University Engine control using torque estimation
US7496534B2 (en) 2001-03-08 2009-02-24 Olsen Richard B Methods for trade decision making
US7155510B1 (en) 2001-03-28 2006-12-26 Predictwallstreet, Inc. System and method for forecasting information using collective intelligence from diverse sources
US7167837B1 (en) * 2001-04-16 2007-01-23 Ft Interactive Data Corporation Fair-value pricing of a financial asset
US7031955B1 (en) * 2001-04-27 2006-04-18 I2 Technologies Us, Inc. Optimization using a multi-dimensional data model
US20040015906A1 (en) * 2001-04-30 2004-01-22 Goraya Tanvir Y. Adaptive dynamic personal modeling system and method
US7236940B2 (en) * 2001-05-16 2007-06-26 Perot Systems Corporation Method and system for assessing and planning business operations utilizing rule-based statistical modeling
US7246080B2 (en) * 2001-06-08 2007-07-17 International Business Machines Corporation Apparatus, system and method for measuring and monitoring supply chain risk
US20020198811A1 (en) * 2001-06-12 2002-12-26 Adam Wizon System and method for monitoring the status of analyses performed on a portfolio of financial instruments
US7376610B2 (en) * 2001-06-14 2008-05-20 International Business Machines Corporation Computerized method and system for score based evaluation of capital market investment decisions and strategies
US7222095B2 (en) 2001-07-06 2007-05-22 Buyside Research Llc Method and system for comparison and evaluation of investment portfolios
US7318038B2 (en) * 2001-07-30 2008-01-08 International Business Machines Corporation Project risk assessment
US20030028267A1 (en) * 2001-08-06 2003-02-06 Hales Michael L. Method and system for controlling setpoints of manipulated variables for process optimization under constraint of process-limiting variables
US7386496B1 (en) * 2001-08-15 2008-06-10 Jones Lang Lasalle Ip, Inc. System and method for evaluating real estate financing structures
US20030046130A1 (en) * 2001-08-24 2003-03-06 Golightly Robert S. System and method for real-time enterprise optimization
US20030074291A1 (en) * 2001-09-19 2003-04-17 Christine Hartung Integrated program for team-based project evaluation
AU2002349976A1 (en) * 2001-10-17 2003-04-28 Advanced Research And Technology Institute Methods for predicting transcription levels
FR2831301B1 (en) * 2001-10-18 2004-02-13 Eurocopter France METHOD AND DEVICE FOR DETERMINING IN REAL TIME THE BEHAVIOR OF A MOBILE, IN PARTICULAR AN AIRCRAFT
SE520728C2 (en) * 2001-11-12 2003-08-19 Ericsson Telefon Ab L M Non-linear modeling procedure
EP1461688A4 (en) * 2001-11-27 2006-02-08 Accenture Llp Service control architecture
US7272617B1 (en) * 2001-11-30 2007-09-18 Ncr Corp. Analytic data set creation for modeling in a customer relationship management system
JP3736442B2 (en) * 2001-11-30 2006-01-18 ソニー株式会社 Display device and display method
CA2364425A1 (en) * 2001-12-05 2003-06-05 Algorithmics International Corp. A system for calculation of operational risk capital
US7395219B2 (en) 2001-12-08 2008-07-01 Kenneth Ray Strech Insurance on demand transaction management system
US7523065B2 (en) * 2001-12-12 2009-04-21 Asset Trust, Inc. Risk transfer supply chain system
US20030115090A1 (en) * 2001-12-17 2003-06-19 Shahid Mujtaba Method to define an optimal integrated action plan for procurement, manufacturing, and marketing
US7158967B1 (en) * 2001-12-21 2007-01-02 Unisys Corporation XML output definition table for transferring internal data into XML document
US7249007B1 (en) * 2002-01-15 2007-07-24 Dutton John A Weather and climate variable prediction for management of weather and climate risk
US7451065B2 (en) * 2002-03-11 2008-11-11 International Business Machines Corporation Method for constructing segmentation-based predictive models
CA2381689A1 (en) * 2002-04-12 2003-10-12 Algorithmics International Corp. System, method and framework for generating scenarios
US7080207B2 (en) * 2002-04-30 2006-07-18 Lsi Logic Corporation Data storage apparatus, system and method including a cache descriptor having a field defining data in a cache block
GB0210397D0 (en) * 2002-05-07 2002-06-12 Ferring Bv Pharmaceutical formulations
AU2003230405A1 (en) * 2002-05-07 2003-11-11 Markov Processes International, Llc A method and system to solve dynamic multi-factor models in finance
US7395235B2 (en) * 2002-06-13 2008-07-01 Centre For Development Of Advanced Computing Strategy independent optimization of multi objective functions
US20030233310A1 (en) * 2002-06-17 2003-12-18 Boris Stavrovski Method and system for implementing a business transaction over the internet with use and consecutive transformation of information from publicly available databases, actual preferences of potential customers and statistical models of the market situation
US7596523B2 (en) * 2002-09-09 2009-09-29 Barra, Inc. Method and apparatus for network-based portfolio management and risk-analysis
US7747339B2 (en) * 2002-10-03 2010-06-29 Hewlett-Packard Development Company, L.P. Managing procurement risk
JP2004129458A (en) * 2002-10-07 2004-04-22 Canon Inc Controller for vibratory actuator, vibratory actuator system, and control method for vibratory actuator
US7752099B2 (en) * 2002-10-17 2010-07-06 Itg Software Solutions, Inc. Factor risk model based system, method, and computer program product for generating risk forecasts
US7219040B2 (en) * 2002-11-05 2007-05-15 General Electric Company Method and system for model based control of heavy duty gas turbine
US6892155B2 (en) * 2002-11-19 2005-05-10 Agilent Technologies, Inc. Method for the rapid estimation of figures of merit for multiple devices based on nonlinear modeling
US6823253B2 (en) * 2002-11-27 2004-11-23 General Electric Company Methods and apparatus for model predictive control of aircraft gas turbine engines
WO2004099899A2 (en) * 2002-12-09 2004-11-18 Pavilion Technologies, Inc. A system and method of adaptive control of processes with varying dynamics
US7272820B2 (en) * 2002-12-12 2007-09-18 Extrapoles Pty Limited Graphical development of fully executable transactional workflow applications with adaptive high-performance capacity
DE10353868B4 (en) * 2002-12-12 2014-07-24 Heidelberger Druckmaschinen Ag Representation of data in a substrate processing machine
AU2003303250A1 (en) * 2002-12-20 2004-07-14 Accenture Global Services Gmbh Quantification of operational risks
GB0301707D0 (en) * 2003-01-24 2003-02-26 Rolls Royce Plc Fault diagnosis
US7337137B2 (en) * 2003-02-20 2008-02-26 Itg, Inc. Investment portfolio optimization system, method and computer program product
US7249004B2 (en) * 2003-02-28 2007-07-24 3M Innovative Properties Company Mill roll analysis system
US7640201B2 (en) * 2003-03-19 2009-12-29 General Electric Company Methods and systems for analytical-based multifactor Multiobjective portfolio risk optimization
US7347365B2 (en) * 2003-04-04 2008-03-25 Lumidigm, Inc. Combined total-internal-reflectance and tissue imaging systems and methods
US7716073B1 (en) 2003-04-15 2010-05-11 Pension Benefit Insurance Services, Inc. Methods for administering claims in a pension insurance program
US7848939B1 (en) 2003-04-15 2010-12-07 Pentech, Llc Methods for validating participants in a pension insurance program
US7912738B1 (en) 2003-04-15 2011-03-22 Pentech, Llc Methods for administering loan premiums in a pension insurance program
US7080027B2 (en) 2003-04-17 2006-07-18 Targetrx, Inc. Method and system for analyzing the effectiveness of marketing strategies
WO2004099890A1 (en) * 2003-05-01 2004-11-18 Aspen Technology, Inc. Methods, systems, and articles for controlling a fluid blending system
US7617141B2 (en) * 2003-05-08 2009-11-10 International Business Machines Corporation Software application portfolio management for a client
US8108920B2 (en) * 2003-05-12 2012-01-31 Microsoft Corporation Passive client single sign-on for web applications
US20040243461A1 (en) * 2003-05-16 2004-12-02 Riggle Mark Spencer Integration of causal models, business process models and dimensional reports for enhancing problem solving
BRPI0410656A (en) * 2003-05-28 2006-07-18 Pioneer Hi Bred Int plant breeding method and plant obtained
US7426423B2 (en) * 2003-05-30 2008-09-16 Liebherr-Werk Nenzing—GmbH Crane or excavator for handling a cable-suspended load provided with optimised motion guidance
US8010387B2 (en) * 2003-06-04 2011-08-30 California Institute Of Technology Method, computer program product, and system for risk management
US7606727B1 (en) * 2003-06-16 2009-10-20 Jpmorgan Chase Bank, N.A. System and method for identifying optimal marketing offers
US7912769B2 (en) * 2003-07-01 2011-03-22 Accenture Global Services Limited Shareholder value tool
US7899723B2 (en) * 2003-07-01 2011-03-01 Accenture Global Services Gmbh Shareholder value tool
US7711617B2 (en) * 2003-07-11 2010-05-04 Finanalytica, Inc. System and method for providing optimization of a financial portfolio using a parametric leptokurtic distribution
US7146353B2 (en) * 2003-07-22 2006-12-05 Hewlett-Packard Development Company, L.P. Resource allocation for multiple applications
JP2007500379A (en) * 2003-07-25 2007-01-11 ヤマハ発動機株式会社 Software optimization device for intelligent control system
US8175908B1 (en) * 2003-09-04 2012-05-08 Jpmorgan Chase Bank, N.A. Systems and methods for constructing and utilizing a merchant database derived from customer purchase transactions data
WO2005038582A2 (en) * 2003-10-10 2005-04-28 Julian Van Erlach Asset analysis according to the required yield method
US7283982B2 (en) * 2003-12-05 2007-10-16 International Business Machines Corporation Method and structure for transform regression
US7657475B1 (en) * 2003-12-31 2010-02-02 Fannie Mae Property investment rating system and method
US20050228730A1 (en) * 2004-01-07 2005-10-13 Thomas Henderson Targeted dividend reinvestment plans and methods of establishing same
US7542932B2 (en) * 2004-02-20 2009-06-02 General Electric Company Systems and methods for multi-objective portfolio optimization
US20050193739A1 (en) * 2004-03-02 2005-09-08 General Electric Company Model-based control systems and methods for gas turbine engines
US7778910B2 (en) * 2004-03-02 2010-08-17 Accenture Global Services Gmbh Future value drivers
US7251638B2 (en) * 2004-03-03 2007-07-31 Yamaha Hatsudoki Kabushiki Kaisha Intelligent robust control system for motorcycle using soft computing optimizer
US7827557B2 (en) * 2004-03-24 2010-11-02 Hewlett-Packard Development Company, L.P. Method and apparatus for allocating resources to applications using a linearized objective function
US7296734B2 (en) 2004-06-02 2007-11-20 Robert Kenneth Pliha Systems and methods for scoring bank customers direct deposit account transaction activity to match financial behavior to specific acquisition, performance and risk events defined by the bank using a decision tree and stochastic process
US8082207B2 (en) 2004-06-17 2011-12-20 Certegy Check Services, Inc. Scored negative file system and method
US7877321B2 (en) * 2004-06-29 2011-01-25 Textura Corporation Method of and system for evaluating financial risk associated with a construction project
US7672889B2 (en) * 2004-07-15 2010-03-02 Brooks Kent F System and method for providing customizable investment tools
US7490356B2 (en) * 2004-07-20 2009-02-10 Reflectent Software, Inc. End user risk management
EP1628492A1 (en) * 2004-08-17 2006-02-22 Dialog Semiconductor GmbH A camera test system
US7711623B2 (en) * 2004-08-20 2010-05-04 Consulting Services Support Corporation Decision assistance platform configured for facilitating financial consulting services
US8160956B2 (en) * 2004-08-31 2012-04-17 Thomas Franklin Comstock Insurance system and method for a high-risk asset purchaser or lessee
US7509275B2 (en) 2004-09-10 2009-03-24 Chicago Mercantile Exchange Inc. System and method for asymmetric offsets in a risk management system
US7426487B2 (en) * 2004-09-10 2008-09-16 Chicago Mercantile Exchange, Inc. System and method for efficiently using collateral for risk offset
US7996339B2 (en) * 2004-09-17 2011-08-09 International Business Machines Corporation Method and system for generating object classification models
US7224761B2 (en) * 2004-11-19 2007-05-29 Westinghouse Electric Co. Llc Method and algorithm for searching and optimizing nuclear reactor core loading patterns
US7693765B2 (en) * 2004-11-30 2010-04-06 Michael Dell Orfano System and method for creating electronic real estate registration
US7877283B2 (en) * 2004-12-30 2011-01-25 Sap Ag Multi-perspective business process configuration
US7774293B2 (en) * 2005-03-17 2010-08-10 University Of Maryland System and methods for assessing risk using hybrid causal logic
US7624054B2 (en) * 2005-08-25 2009-11-24 Sas Institute Inc. Financial risk mitigation optimization systems and methods
US7698188B2 (en) * 2005-11-03 2010-04-13 Beta-Rubicon Technologies, Llc Electronic enterprise capital marketplace and monitoring apparatus and method
US7702615B1 (en) * 2005-11-04 2010-04-20 M-Factor, Inc. Creation and aggregation of predicted data
US7561158B2 (en) * 2006-01-11 2009-07-14 International Business Machines Corporation Method and apparatus for presenting feature importance in predictive modeling
US7433809B1 (en) * 2006-01-25 2008-10-07 Sas Institute Inc. System and method for non-linear modeling
EP1999711A4 (en) * 2006-03-01 2009-11-04 Townsend Analytics Ltd Methods and systems for risk management
US7689494B2 (en) 2006-03-23 2010-03-30 Advisor Software Inc. Simulation of portfolios and risk budget analysis
US7853509B2 (en) 2006-03-23 2010-12-14 Hartford Fire Insurance Company Lifetime income
US7788195B1 (en) * 2006-03-24 2010-08-31 Sas Institute Inc. Computer-implemented predictive model generation systems and methods
US8392240B2 (en) * 2006-09-01 2013-03-05 Oracle Financial Services Software Limited System and method for determining outsourcing suitability of a business process in an enterprise
US8589190B1 (en) 2006-10-06 2013-11-19 Liberty Mutual Insurance Company System and method for underwriting a prepackaged business owners insurance policy
US7940899B2 (en) * 2006-10-06 2011-05-10 Pricewaterhousecoopers Llp Fraud detection, risk analysis and compliance assessment
US7949597B2 (en) 2007-02-02 2011-05-24 Zadoorian James A Method of collecting delinquent specialized debt
US7840468B2 (en) 2007-02-05 2010-11-23 Jpmorgan Chase Bank, N.A. System and method for a risk management framework for hedging mortality risk in portfolios having mortality-based exposure
US8108290B2 (en) 2007-02-15 2012-01-31 Chicago Board Options Exchange, Incorporated Market sentiment indicator
US7900259B2 (en) * 2007-03-16 2011-03-01 Prevari Predictive assessment of network risks
JP5405720B2 (en) * 2007-03-30 2014-02-05 株式会社ニデック Eyeglass lens processing equipment
US7877308B1 (en) 2007-04-26 2011-01-25 Klein Decisions, Inc. Method and system for using risk tolerance and life goal preferences and rankings to enhance financial projections
US8566206B2 (en) 2007-05-10 2013-10-22 Pensions First Analytics Limited Pension fund systems
US8005739B1 (en) 2007-06-22 2011-08-23 Stephen David Reddy Pension alternative retirement income system
US7908237B2 (en) * 2007-06-29 2011-03-15 International Business Machines Corporation Method and apparatus for identifying unexpected behavior of a customer in a retail environment using detected location data, temperature, humidity, lighting conditions, music, and odors
US7962321B2 (en) * 2007-07-10 2011-06-14 Palo Alto Research Center Incorporated Modeling when connections are the problem
US7870061B2 (en) 2007-08-13 2011-01-11 Mott Antony R System and method for transferring longevity risk
US7921061B2 (en) * 2007-09-05 2011-04-05 Oracle International Corporation System and method for simultaneous price optimization and asset allocation to maximize manufacturing profits
US8566128B2 (en) 2007-10-24 2013-10-22 Joseph D. Koziol Insurance transaction system and method
US8065209B1 (en) 2007-11-12 2011-11-22 United Services Automobile Association (Usaa) System and method for bundling financial services products with a mortgage in connection with a move event
US8645259B1 (en) * 2008-02-14 2014-02-04 Tyche Technologies LLC Mitigating risk associated with executing limit orders for trading securities
US8041580B1 (en) 2008-02-28 2011-10-18 Intuit Inc. Forecasting consequences of healthcare utilization choices
US7849004B2 (en) 2008-02-29 2010-12-07 American Express Travel Related Services Company, Inc. Total structural risk model
US8095396B1 (en) * 2008-03-27 2012-01-10 Asterisk Financial Group, Inc. Computer system for underwriting a personal guaranty liability by utilizing a risk apportionment system
US8156030B2 (en) * 2008-04-03 2012-04-10 Gravity Investments Llc Diversification measurement and analysis system
US8577712B2 (en) 2008-05-02 2013-11-05 Hewlett-Packard Development Company, L.P. Assessing risk
US8200573B2 (en) 2008-06-05 2012-06-12 Skopos Financial Group, Llc Multi-variable transaction system and method
US8255972B2 (en) 2008-06-06 2012-08-28 International Business Machines Corporation Method to automatically map business function level policies to it management policies
FR2933396B1 (en) * 2008-07-02 2011-07-22 Air Liquide PROCESS FOR MANUFACTURING A TRAPPING STRUCTURE WITH CONTROL OF THE DRYING STEP
US8650108B1 (en) * 2008-07-29 2014-02-11 Bank Of America Corporation User interface for investment decisioning process model
US8332305B1 (en) 2008-09-22 2012-12-11 Optionmonster Holdings, Inc. Automatic strategy grouping for a trading system
US8560359B2 (en) 2008-10-31 2013-10-15 Hewlett-Packard Development Company, L.P. System and methods for modeling consequences of events
US8566219B2 (en) 2009-03-24 2013-10-22 Trading Technologeis International, Inc. System and method for a risk check
US8335732B2 (en) 2009-05-27 2012-12-18 Joshua Farzad Dayanim Security pricing method and system
US8442908B2 (en) * 2009-06-12 2013-05-14 MCMCAP Partners, LLC Systems and methods for asset valuation
US8131571B2 (en) * 2009-09-23 2012-03-06 Watson Wyatt & Company Method and system for evaluating insurance liabilities using stochastic modeling and sampling techniques
US8255346B2 (en) 2009-11-11 2012-08-28 International Business Machines Corporation Methods and systems for variable group selection and temporal causal modeling
US8548934B2 (en) 2009-11-17 2013-10-01 Infozen, Inc. System and method for assessing risk
US8401950B2 (en) * 2010-01-25 2013-03-19 Fair Isaac Corporation Optimizing portfolios of financial instruments
US8473431B1 (en) 2010-05-14 2013-06-25 Google Inc. Predictive analytic modeling platform
US8306849B2 (en) * 2010-09-16 2012-11-06 International Business Machines Corporation Predicting success of a proposed project
US8566222B2 (en) 2010-12-20 2013-10-22 Risconsulting Group Llc, The Platform for valuation of financial instruments
US8626558B2 (en) * 2011-09-07 2014-01-07 Dow Corning Corporation Supply chain risk management method and device
US8583533B2 (en) 2011-09-29 2013-11-12 Direct Swap Inc. System, method, article for facilitating derivatives transactions
US8595845B2 (en) 2012-01-19 2013-11-26 Mcafee, Inc. Calculating quantitative asset risk

Patent Citations (81)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3749892A (en) * 1971-02-16 1973-07-31 Qeleg Ltd Accountancy system
US3933305A (en) * 1974-08-23 1976-01-20 John Michael Murphy Asset value calculators
US4839304A (en) * 1986-12-18 1989-06-13 Nec Corporation Method of making a field effect transistor with overlay gate structure
US5193055A (en) * 1987-03-03 1993-03-09 Brown Gordon T Accounting system
US5644727A (en) * 1987-04-15 1997-07-01 Proprietary Financial Products, Inc. System for the operation and management of one or more financial accounts through the use of a digital communication and computation system for exchange, investment and borrowing
US4989141A (en) * 1987-06-01 1991-01-29 Corporate Class Software Computer system for financial analyses and reporting
US5128861A (en) * 1988-12-07 1992-07-07 Hitachi, Ltd. Inventory control method and system
US5237946A (en) * 1989-01-23 1993-08-24 Copson Alex G Apparatus and method for transferring material to subaqueous levels
US5191522A (en) * 1990-01-18 1993-03-02 Itt Corporation Integrated group insurance information processing and reporting system based upon an enterprise-wide data structure
US5237495A (en) * 1990-05-23 1993-08-17 Fujitsu Limited Production/purchase management processing system and method
US5224034A (en) * 1990-12-21 1993-06-29 Bell Communications Research, Inc. Automated system for generating procurement lists
US5471611A (en) * 1991-03-13 1995-11-28 University Of Strathclyde Computerised information-retrieval database systems
US5406477A (en) * 1991-08-30 1995-04-11 Digital Equipment Corporation Multiple reasoning and result reconciliation for enterprise analysis
US5317504A (en) * 1991-10-23 1994-05-31 T.A.S. & Trading Co., Ltd. Computer implemented process for executing accounting theory systems
US5414621A (en) * 1992-03-06 1995-05-09 Hough; John R. System and method for computing a comparative value of real estate
US6134536A (en) * 1992-05-29 2000-10-17 Swychco Infrastructure Services Pty Ltd. Methods and apparatus relating to the formulation and trading of risk management contracts
US5361201A (en) * 1992-10-19 1994-11-01 Hnc, Inc. Real estate appraisal using predictive modeling
US5802501A (en) * 1992-10-28 1998-09-01 Graff/Ross Holdings System and methods for computing to support decomposing property into separately valued components
US6112188A (en) * 1992-10-30 2000-08-29 Hartnett; William J. Privatization marketplace
US6064971A (en) * 1992-10-30 2000-05-16 Hartnett; William J. Adaptive knowledge base
US5649181A (en) * 1993-04-16 1997-07-15 Sybase, Inc. Method and apparatus for indexing database columns with bit vectors
US5542420A (en) * 1993-04-30 1996-08-06 Goldman; Arnold J. Personalized method and system for storage, communication, analysis, and processing of health-related data
US5704055A (en) * 1993-06-01 1997-12-30 International Business Machines Corporation Dynamic Reconfiguration of main storage and expanded storage by means of a service call logical processor
US5812987A (en) * 1993-08-18 1998-09-22 Barclays Global Investors, National Association Investment fund management method and system with dynamic risk adjusted allocation of assets
US6263314B1 (en) * 1993-12-06 2001-07-17 Irah H. Donner Method of performing intellectual property (IP) audit optionally over network architecture
US5812988A (en) * 1993-12-06 1998-09-22 Investments Analytic, Inc. Method and system for jointly estimating cash flows, simulated returns, risk measures and present values for a plurality of assets
US5668591A (en) * 1994-03-30 1997-09-16 Sony Corporation Information terminal apparatus that is remotely programmed by radio waves and that displays input keys of program functions on a display
US6092056A (en) * 1994-04-06 2000-07-18 Morgan Stanley Dean Witter Data processing system and method for financial debt instruments
US5435565A (en) * 1994-07-18 1995-07-25 Benaderet; David M. Board game relating to stress
US5704045A (en) * 1995-01-09 1997-12-30 King; Douglas L. System and method of risk transfer and risk diversification including means to assure with assurance of timely payment and segregation of the interests of capital
US6148293A (en) * 1995-01-18 2000-11-14 King; Douglas L. Method and apparatus of creating a financial instrument and administering an adjustable rate loan system
US5742775A (en) * 1995-01-18 1998-04-21 King; Douglas L. Method and apparatus of creating financial instrument and administering an adjustable rate loan system
US5680305A (en) * 1995-02-16 1997-10-21 Apgar, Iv; Mahlon System and method for evaluating real estate
US5809282A (en) * 1995-06-07 1998-09-15 Grc International, Inc. Automated network simulation and optimization system
US5737581A (en) * 1995-08-30 1998-04-07 Keane; John A. Quality system implementation simulator
US5819237A (en) * 1996-02-13 1998-10-06 Financial Engineering Associates, Inc. System and method for determination of incremental value at risk for securities trading
US5794219A (en) * 1996-02-20 1998-08-11 Health Hero Network, Inc. Method of conducting an on-line auction with bid pooling
US5875431A (en) * 1996-03-15 1999-02-23 Heckman; Frank Legal strategic analysis planning and evaluation control system and method
US6189011B1 (en) * 1996-03-19 2001-02-13 Siebel Systems, Inc. Method of maintaining a network of partially replicated database system
US5774873A (en) * 1996-03-29 1998-06-30 Adt Automotive, Inc. Electronic on-line motor vehicle auction and information system
US5706495A (en) * 1996-05-07 1998-01-06 International Business Machines Corporation Encoded-vector indices for decision support and warehousing
US6221009B1 (en) * 1996-07-16 2001-04-24 Kyoto Daiichi Kagaku Co., Ltd. Dispersed-type testing measuring system and dispersed-type care system
US6612986B2 (en) * 1996-07-16 2003-09-02 Kyoto Daiichi Kagaku Co., Ltd. Dispersed-type testing/measuring system and dispersed-type health care system
US6032119A (en) * 1997-01-16 2000-02-29 Health Hero Network, Inc. Personalized display of health information
US6375469B1 (en) * 1997-03-10 2002-04-23 Health Hero Network, Inc. Online system and method for providing composite entertainment and health information
US5951300A (en) * 1997-03-10 1999-09-14 Health Hero Network Online system and method for providing composite entertainment and health information
US6078901A (en) * 1997-04-03 2000-06-20 Ching; Hugh Quantitative supply and demand model based on infinite spreadsheet
US5985559A (en) * 1997-04-30 1999-11-16 Health Hero Network System and method for preventing, diagnosing, and treating genetic and pathogen-caused disease
US6278981B1 (en) * 1997-05-29 2001-08-21 Algorithmics International Corporation Computer-implemented method and apparatus for portfolio compression
US6173276B1 (en) * 1997-08-21 2001-01-09 Scicomp, Inc. System and method for financial instrument modeling and valuation
US6301584B1 (en) * 1997-08-21 2001-10-09 Home Information Services, Inc. System and method for retrieving entities and integrating data
US6064972A (en) * 1997-09-17 2000-05-16 At&T Corp Risk management technique for network access
US6125355A (en) * 1997-12-02 2000-09-26 Financial Engines, Inc. Pricing module for financial advisory system
US6014629A (en) * 1998-01-13 2000-01-11 Moore U.S.A. Inc. Personalized health care provider directory
US20020002520A1 (en) * 1998-04-24 2002-01-03 Gatto Joseph G. Security analyst estimates performance viewing system and method
US20020052820A1 (en) * 1998-04-24 2002-05-02 Gatto Joseph G. Security analyst estimates performance viewing system and method
US6282531B1 (en) * 1998-06-12 2001-08-28 Cognimed, Llc System for managing applied knowledge and workflow in multiple dimensions and contexts
US6645124B1 (en) * 1998-09-18 2003-11-11 Athlon Llc Interactive programmable fitness interface system
US6366934B1 (en) * 1998-10-08 2002-04-02 International Business Machines Corporation Method and apparatus for querying structured documents using a database extender
US6510430B1 (en) * 1999-02-24 2003-01-21 Acumins, Inc. Diagnosis and interpretation methods and apparatus for a personal nutrition program
US6576471B2 (en) * 1999-02-26 2003-06-10 Liposcience, Inc. Methods, systems, and computer program products for analyzing and presenting NMR lipoprotein-based risk assessment results
US6584507B1 (en) * 1999-03-02 2003-06-24 Cisco Technology, Inc. Linking external applications to a network management system
US6518069B1 (en) * 1999-04-22 2003-02-11 Liposcience, Inc. Methods and computer program products for determining risk of developing type 2 diabetes and other insulin resistance related disorders
US6209124B1 (en) * 1999-08-30 2001-03-27 Touchnet Information Systems, Inc. Method of markup language accessing of host systems and data using a constructed intermediary
US6332163B1 (en) * 1999-09-01 2001-12-18 Accenture, Llp Method for providing communication services over a computer network system
US6418448B1 (en) * 1999-12-06 2002-07-09 Shyam Sundar Sarkar Method and apparatus for processing markup language specifications for data and metadata used inside multiple related internet documents to navigate, query and manipulate information from a plurality of object relational databases over the web
US6695795B2 (en) * 1999-12-27 2004-02-24 Medireha Gmbh Therapeutic device
US6757898B1 (en) * 2000-01-18 2004-06-29 Mckesson Information Solutions, Inc. Electronic provider—patient interface system
US20020023034A1 (en) * 2000-03-31 2002-02-21 Brown Roger G. Method and system for a digital automated exchange
US7006992B1 (en) * 2000-04-06 2006-02-28 Union State Bank Risk assessment and management system
US6684204B1 (en) * 2000-06-19 2004-01-27 International Business Machines Corporation Method for conducting a search on a network which includes documents having a plurality of tags
US20020016758A1 (en) * 2000-06-28 2002-02-07 Grigsby Calvin B. Method and apparatus for offering, pricing, and selling securities over a network
US6738753B1 (en) * 2000-08-21 2004-05-18 Michael Andrew Hogan Modular, hierarchically organized artificial intelligence entity
US6499843B1 (en) * 2000-09-13 2002-12-31 Bausch & Lomb Incorporated Customized vision correction method and business
US6836773B2 (en) * 2000-09-28 2004-12-28 Oracle International Corporation Enterprise web mining system and method
US6876992B1 (en) * 2000-11-28 2005-04-05 Willis North America Inc. Method and system for risk control optimization
US6671773B2 (en) * 2000-12-07 2003-12-30 Spinnaker Networks, Llc Method and system for responding to file system requests
US6654289B2 (en) * 2001-03-09 2003-11-25 Micron Technology, Inc. Non-volatile memory device with erase address register
US6732095B1 (en) * 2001-04-13 2004-05-04 Siebel Systems, Inc. Method and apparatus for mapping between XML and relational representations
US20030083973A1 (en) * 2001-08-29 2003-05-01 Horsfall Peter R. Electronic trading system
US6518430B1 (en) * 2001-09-21 2003-02-11 Abbott Laboratories Process for the preparation of 5-(substituted)-10-methoxy-2,2,4-trimethyl-2,5-dihydro-1H-chromeno[3,4-F]quinolines and derivatives thereof

Cited By (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040078328A1 (en) * 2002-02-07 2004-04-22 Talbert Vincent W. Method and system for completing a transaction between a customer and a merchant
US7890393B2 (en) 2002-02-07 2011-02-15 Ebay, Inc. Method and system for completing a transaction between a customer and a merchant
US8095445B2 (en) 2003-07-23 2012-01-10 Ebay, Inc. Method and system for completing a transaction between a customer and a merchant
US8571972B2 (en) 2004-02-23 2013-10-29 Bill Me Later, Inc. Computer-implemented method, system and apparatus for the dynamic verification of a consumer engaged in a transaction with a merchant and authorization of the transaction
US20070288375A1 (en) * 2004-02-23 2007-12-13 I4 Licensing Llc Computer-Implemented Method, System and Apparatus for the Dynamic Verification of a Consumer Engaged in a Transaction with a Merchant and Authorization of the Transaction
US20090043637A1 (en) * 2004-06-01 2009-02-12 Eder Jeffrey Scott Extended value and risk management system
US8001040B2 (en) 2005-01-25 2011-08-16 Ebay Inc. Computer-implemented method and system for dynamic consumer rating in a transaction
US20060229996A1 (en) * 2005-04-11 2006-10-12 I4 Licensing Llc Consumer processing system and method
US7527195B2 (en) * 2005-04-11 2009-05-05 Bill Me Later, Inc. Method and system for risk management in a transaction
US20060226216A1 (en) * 2005-04-11 2006-10-12 I4 Licensing Llc Method and system for risk management in a transaction
US20060229974A1 (en) * 2005-04-11 2006-10-12 I4 Licensing Llc Method of extending credit to at least one consumer and method of processing a transaction between a consumer and a merchant
US8756099B2 (en) 2005-04-11 2014-06-17 Bill Me Later, Inc. Consumer processing system and method
US11922494B2 (en) 2007-01-09 2024-03-05 Paypal, Inc. Method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale
US20080167956A1 (en) * 2007-01-09 2008-07-10 I4 Commerce Inc. Method and system for offering a credit product by a credit issuer to a consumer at a point-of sale
US11847692B2 (en) 2007-01-09 2023-12-19 Paypal, Inc. Method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale
US8554669B2 (en) 2007-01-09 2013-10-08 Bill Me Later, Inc. Method and system for offering a credit product by a credit issuer to a consumer at a point-of sale
US9684931B2 (en) 2007-01-09 2017-06-20 Paypal, Inc. Method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale
US10949920B2 (en) 2007-01-09 2021-03-16 Paypal, Inc. Method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale
US10068289B2 (en) 2007-01-09 2018-09-04 Paypal, Inc. Method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale
US9412132B2 (en) 2007-01-09 2016-08-09 Paypal, Inc. Method and system for offering a credit product by a credit issuer to a consumer at a point-of-sale
US20080203153A1 (en) * 2007-02-26 2008-08-28 I4 Commerce Inc. Method and system for engaging in a transaction between a consumer and a merchant
US8433648B2 (en) 2007-02-26 2013-04-30 Bill Me Later, Inc. Method and system for engaging in a transaction between a consumer and a merchant
US10580070B2 (en) 2007-05-02 2020-03-03 Paypal, Inc. Distributed system for commerce
US9058407B2 (en) * 2008-01-22 2015-06-16 Oracle International Corporation Persistent multimedia content versioning
US20090187610A1 (en) * 2008-01-22 2009-07-23 Oracle International Corporation Persistent multimedia content versioning
US10424008B2 (en) 2008-06-19 2019-09-24 Paypal, Inc. Method and system for engaging in a transaction between a business entity and a merchant
US8719164B2 (en) 2008-06-19 2014-05-06 Bill Me Later, Inc. Method and system for engaging in a transaction between a business entity and a merchant

Also Published As

Publication number Publication date
US20060184449A1 (en) 2006-08-17
US20080288394A1 (en) 2008-11-20
US20120303408A1 (en) 2012-11-29
US20040199445A1 (en) 2004-10-07
US20130132163A1 (en) 2013-05-23
US20090070182A1 (en) 2009-03-12
US8185486B2 (en) 2012-05-22
US20040236673A1 (en) 2004-11-25
US20060143115A1 (en) 2006-06-29
US20090132448A1 (en) 2009-05-21
US8694455B2 (en) 2014-04-08

Similar Documents

Publication Publication Date Title
US20060184570A1 (en) Value impact risk transfer products
US20070239581A1 (en) A data processing framework for financial services
US7523065B2 (en) Risk transfer supply chain system
Mayo The human value of the enterprise
TW580627B (en) System and method for efficiently providing due diligence knowledge and a computer therefor
US10839321B2 (en) Automated data storage system
US7822654B2 (en) Business analysis tool
US7873567B2 (en) Value and risk management system
US20160239919A1 (en) Predictive model development system applied to organization management
US7197484B1 (en) Asset management advice system and recording medium containing program of the system
WO2002097701A1 (en) Methods and systems for managing a portfolio of securities
US7970640B2 (en) Purchasing optimization system
US20040236621A1 (en) Business context layer
US20140222637A1 (en) Systems and Methods for Academic Core Banking
Abu-Musa The determinates of selecting accounting software: A proposed model
KR100371407B1 (en) Investment clinic service system and method thereof
Abu-Musa The criteria for selecting accounting software: a theoretical framework
Ranjan et al. Building Data Warehouse at life insurance corporation of India: a case study
KR100918418B1 (en) System and Method for Predicting Profit and Loss, and Program Recording Medium
KR20020085194A (en) System for household financial management and method using the same
US20040215537A1 (en) Banking process and application architecture
McKinney The station never sleeps
Berke Evaluating investments in information technology: theory versus practice
Qureshi et al. Software For Nonprofit Organizations

Legal Events

Date Code Title Description
AS Assignment

Owner name: ASSET RELIANCE, INC.,WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EDER, JEFF S.;REEL/FRAME:017410/0899

Effective date: 20060403

Owner name: ASSET RELIANCE, INC., WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EDER, JEFF S.;REEL/FRAME:017410/0899

Effective date: 20060403

STCB Information on status: application discontinuation

Free format text: EXPRESSLY ABANDONED -- DURING EXAMINATION

AS Assignment

Owner name: ASSET RELIANCE, INC., WASHINGTON

Free format text: NUNC PRO TUNC ASSIGNMENT;ASSIGNOR:EDER, JEFF;REEL/FRAME:031925/0080

Effective date: 20120623

AS Assignment

Owner name: EDER, JEFFREY, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ASSET RELIANCE INC;REEL/FRAME:040639/0485

Effective date: 20161214