US20160350732A1 - Automated system for adapting market data and evaluating the market value of items - Google Patents

Automated system for adapting market data and evaluating the market value of items Download PDF

Info

Publication number
US20160350732A1
US20160350732A1 US15/237,518 US201615237518A US2016350732A1 US 20160350732 A1 US20160350732 A1 US 20160350732A1 US 201615237518 A US201615237518 A US 201615237518A US 2016350732 A1 US2016350732 A1 US 2016350732A1
Authority
US
United States
Prior art keywords
item
metric
data
price data
data set
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.)
Granted
Application number
US15/237,518
Other versions
US9524495B1 (en
Inventor
Valerie Hansen
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.)
BuyMetrics Inc
Original Assignee
BuyMetrics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US15/237,518 priority Critical patent/US9524495B1/en
Application filed by BuyMetrics Inc filed Critical BuyMetrics Inc
Priority to US15/257,765 priority patent/US9576296B2/en
Publication of US20160350732A1 publication Critical patent/US20160350732A1/en
Priority to US15/368,266 priority patent/US9754244B2/en
Application granted granted Critical
Publication of US9524495B1 publication Critical patent/US9524495B1/en
Priority to US15/445,641 priority patent/US9710856B2/en
Priority to US15/604,533 priority patent/US9904913B2/en
Priority to US15/641,083 priority patent/US10055719B2/en
Priority to US16/105,653 priority patent/US10262307B2/en
Priority to US16/116,175 priority patent/US10290008B2/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • 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
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2457Query processing with adaptation to user needs
    • G06F16/24575Query processing with adaptation to user needs using context
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2457Query processing with adaptation to user needs
    • G06F16/24578Query processing with adaptation to user needs using ranking
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/248Presentation of query results
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/951Indexing; Web crawling techniques
    • G06F17/30528
    • G06F17/3053
    • G06F17/30554
    • G06F17/30864
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F7/00Methods or arrangements for processing data by operating upon the order or content of the data handled
    • G06F7/06Arrangements for sorting, selecting, merging, or comparing data on individual record carriers
    • G06F7/08Sorting, i.e. grouping record carriers in numerical or other ordered sequence according to the classification of at least some of the information they carry
    • 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/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • 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
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • 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
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/20Point-of-sale [POS] network systems
    • G06Q20/201Price look-up processing, e.g. updating
    • 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
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201Market modelling; Market analysis; Collecting market data
    • 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
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201Market modelling; Market analysis; Collecting market data
    • G06Q30/0204Market segmentation
    • G06Q30/0205Location or geographical consideration
    • 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
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201Market modelling; Market analysis; Collecting market data
    • G06Q30/0206Price or cost determination based on market factors
    • 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
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0283Price estimation or determination
    • 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
    • G06Q30/00Commerce
    • G06Q30/04Billing or invoicing
    • 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
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0603Catalogue ordering
    • 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
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0611Request for offers or quotes
    • 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
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0623Item investigation
    • 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
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0623Item investigation
    • G06Q30/0625Directed, with specific intent or strategy
    • G06Q30/0629Directed, with specific intent or strategy for generating comparisons
    • 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/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • 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/06Asset management; Financial planning or analysis
    • 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
    • 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/12Accounting
    • 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
    • G06Q50/00Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10Services
    • G06Q50/16Real estate
    • 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
    • G06Q50/00Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10Services
    • G06Q50/18Legal services; Handling legal documents
    • G06Q50/188Electronic negotiation

Definitions

  • This present disclosure generally relates to electronic commerce software applications and, more particularly, to evaluating prices and transactions for purchasing.
  • Commodity items such as lumber, agricultural products, metals, and livestock/meat are usually traded in the open market between a number of buyers and sellers.
  • the sales transactions of most commodity items involve a number of parameters.
  • a buyer usually orders materials by specifying parameters such as lumber species, grade, size (i.e., 2 ⁇ 4, 2 ⁇ 10, etc.), and length, as well as the “tally” or mix of units of various lengths within the shipment, method of transportation (i.e., rail or truck), shipping terms (i.e., FOB or delivered), and desired date of receipt, with each parameter influencing the value of the commodity purchase.
  • a commodity buyer often finds it difficult to objectively compare similar but unequal offerings among competing vendors.
  • spruce SPF 2 ⁇ 4's of #2 & Better grade
  • the buyer would query vendors offering matching species and grade carloads seeking the best match for the buyer's need or tally preference at the lowest market price.
  • Lumber carloads are quoted at a price per thousand board feet for all material on the railcar. When the quoted parameters are not identical, it is very difficult for buyers to determine the comparative value of unequal offerings.
  • a lumber buyer will find multiple vendors each having different offerings available. For example, a railcar of SPF 2 ⁇ 4's may be quoted at a rate of $300/MBF (thousand board feet) by multiple vendors. Even though the MBF price is equal, one vendor's carload may represent significantly greater marketplace value because it contains the more desirable lengths of 2 ⁇ 4's, such as market-preferred 16-foot 2 ⁇ 4's.
  • MBF gigad boll
  • the system comprises a remotely-located server that includes a network interface, a non-transitory computer-readable medium having computer-executable instructions stored thereon, and a processor in communication with the network interface and the computer-readable medium.
  • the processor is configured to execute the computer-executable instructions stored in the computer-readable medium.
  • the computer-executable instructions implement a plurality of applications including a metric server adapter, a metrics application, and at least one communication application.
  • the metric server adapter is a governing logic application programmed to manage at least one evaluation service and a plurality of predefined instructions for managing metric data, including industry-specific instructions or a buyer-agent's customized instructions, to dynamically define transaction-specific instructions for adapting metric data.
  • the metrics application is a production application programmed to manage one or more purchase and/or analysis processes and to invoke and execute the at least one evaluation service in coordination with the governing logic application.
  • the metrics application is further programmed to manage one or more user interfaces that, in operation, facilitate interactions with the remotely-located server.
  • the at least one communication application is programmed to manage one or more protocols that facilitate communications between one or more computing devices and the remotely-located server via the network interface.
  • a triggering request received from a buyer-agent computing device initiating the at least one evaluation service causes the at least one communication application to identify an applicable protocol for communicating with the buyer-agent computing device and triggers the metrics application to receive one or more product specification data sets from the buyer-agent computing device.
  • Each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or a plurality of items having a plurality of attributes that differ in accordance with at least one parameter value.
  • the metrics application receives or retrieves a plurality of price data sets responsive to at least one item identified in the one or more product specification data sets.
  • Each received or retrieved price data set represents an offer to sell and includes price data for at least one item possessing a plurality of attributes having attribute data that includes at least one parameter value.
  • Receipt or retrieval of at least one price data set triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each price data set, to obtain metric data from at least one data source accessible to the remotely-located server.
  • the obtained metric data represents market reference data for at least one responsive item having attributes corresponding to attributes of a respective item as identified in the price data set and includes market reference price data of a current time or current period of time.
  • Each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value, and wherein at least one responsive item in the obtained metric data differs by at least one parameter value from the respective item as identified in the price data set.
  • the metrics application is further caused to evaluate the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the price data set to dynamically discover a difference in the attribute data.
  • the difference in the attribute data is disclosed to the metric server adapter and enables the metric server adapter to contextually determine which of the predefined instructions for managing metric data are applicable to the responsive item in the metric data.
  • the metric server adapter uses the attributes and one or more parameter values as identified for the respective item in the price data set with the predefined instructions determined to be applicable to the responsive item in the metric data to dynamically define transaction-specific instructions for adapting the metric data for the respective item.
  • the metrics application normalizes the metric data by executing, in coordination with the metric server adapter, the transaction-specific instructions for adapting the metric data for the respective item. Execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item as identified in the price data set, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item as identified in the price data set.
  • the metrics application generates one or more evaluation metrics that pertain to the at least one evaluation service for the respective item as identified in the price data set.
  • Each evaluation metric is based, at least in part, on the one or more transaction-specific market reference price data values produced for the respective item as identified in the price data set.
  • the metrics application sorts and/or ranks the plurality of price data sets using one or more of the evaluation metrics generated for the at least one item as identified in each price data set.
  • the metrics application is further programmed to communicate, in cooperation with the at least one communication application, at least a subset of the sorted and/or ranked price data sets and the one or more evaluation metrics generated for the at least one item as identified in each communicated price data set to at least the buyer-agent computing device from which the one or more product specification data sets were received.
  • a triggering request received from a user-agent computing device initiating the at least one evaluation service causes the at least one communication application to identify an applicable protocol for communicating with the user-agent computing device and triggers the metrics application to receive at least one product specification data set from the user-agent computing device.
  • Each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or a plurality of items having a plurality of attributes that differ in accordance with at least one parameter value.
  • the metrics application receives or retrieves at least one price data set responsive to at least one item identified in the at least one product specification data set.
  • the at least one price data set represents an offer to sell and includes price data for at least one item possessing a plurality of attributes having attribute data that includes at least one parameter value.
  • Receipt of at least one product specification data set and receipt or retrieval at least one price data set responsive to at least one item identified in the at least one product specification data set triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each received product specification data set and for each received or retrieved price data set, to obtain metric data from at least one data source accessible to the remotely-located server.
  • the obtained metric data represents market reference data for at least one responsive item having attributes that correspond to attributes of a respective item as identified in the product specification data set or the price data set and includes market reference price data of a current time or current period of time.
  • Each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value, and at least one responsive item in the obtained metric data differs by at least one parameter value from the respective item as identified in the product specification data set or the price data set.
  • the metrics application is further causes to evaluate the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the product specification data set or the price data set to dynamically discover a difference in the attribute data.
  • the difference in the attribute data is disclosed to the metric server adapter and enables the metric server adapter to contextually determine which of the predefined instructions for managing metric data are applicable to the responsive item in the metric data.
  • the metric server adapter uses the attributes and one or more parameter values as identified for the respective item in the product specification data set or the price data set with the predefined instructions determined to be applicable to the responsive item in the metric data to dynamically define transaction-specific instructions for adapting the metric data for the respective item.
  • the metrics application normalizes the metric data by executing, in coordination with the metric server adapter, the transaction-specific instructions for adapting the metric data for the respective item in the product specification data set or the price data set.
  • Execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item as identified in the product specification data set or the price data set, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item as identified in the product specification data set or the price data set.
  • the metrics application generates one or more evaluation metrics that pertain to the at least one evaluation service for the respective item as identified in the product specification data set and as identified in the received or retrieved price data set.
  • Each evaluation metric is based, at least in part, on the one or more transaction-specific market reference data values produced for the respective item.
  • the metrics application is further programmed to communicate, in cooperation with the at least one communication application, the one or more evaluation metrics generated for the at least one item as identified in each product specification data set and each price data set, via the network interface, to at least the user-agent computing device from which the one or more product specification data sets were received.
  • a triggering request received from a buyer-agent computing device initiating the at least one evaluation service causes the at least one communication application to identify an applicable protocol for communicating with the buyer-agent computing device and triggers the metrics application to receive one or more product specification data sets from a buyer-agent computing device.
  • Each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or a plurality of items having a plurality of attributes that differ in accordance with at least one parameter value.
  • the metrics application receives or retrieves at least one price data set responsive to at least one item identified in the one or more product specification data sets.
  • Each price data set comprises an offer to sell that includes price data for at least one item possessing a plurality of attributes having attribute data that includes at least one parameter value.
  • Receipt or retrieval of at least one price data set triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each price data set, to obtain metric data from at least one data source accessible to the remotely-located server.
  • the obtained metric data represents market reference data for at least one responsive item having attributes corresponding to attributes of a respective item as identified in the price data set and includes market reference price data of a current time or current period of time.
  • Each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value, and wherein at least one responsive item in the obtained metric data differs by at least one parameter value from the respective item as identified in the price data set.
  • the metrics application is further caused to evaluate the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the price data set to dynamically discover a difference in the attribute data.
  • the difference in the attribute data is disclosed to the metric server adapter and enables the metric server adapter to contextually determine which of the predefined instructions for managing metric data are applicable to the responsive item in the metric data.
  • the metric server adapter uses the attributes and one or more parameter values as identified for the respective item in the price data set with the predefined instructions determined to be applicable to the responsive item in the metric data to dynamically define transaction-specific instructions for adapting the metric data for the respective item.
  • the metrics application normalizes the metric data by executing, in coordination with the metric server adapter, the transaction-specific instructions for adapting the metric data for the respective item. Execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item identified in the price data set, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item as identified in the price data set.
  • the metrics application generates one or more evaluation metrics that pertain to the at least one evaluation service for the respective item as identified in the price data set received or retrieved via the first purchase process.
  • Each evaluation metric is based, at least in part, on the one or more transaction-specific market reference data values produced for the respective item as identified in the price data set.
  • At least one evaluation metric comprises a ratio or index value, wherein price data for the respective item in the price data set is divided by one or a combination of transaction-specific market reference price data values produced for the respective item, to generate a relative value metric.
  • the metrics application is programmed to retrieve or receive at least one price data set having an item that is responsive to at least one item identified in the one or more product specification data sets using a second, different purchase process.
  • the metrics application is further programmed to produce, in coordination with the metric server adapter, one or more transaction-specific market reference price data values for the respective item as identified in each price data set received or retrieved via the second purchase process and to generate the one or more evaluation metrics, including a relative value metric, for the at least one item as identified in each price data set received or retrieved via the second purchase process.
  • the metrics application compares the price data sets received or retrieved via each purchase process, wherein the relative value metric generated for the respective item as identified in each price data set provides an objective measure to compare the first and second purchase processes.
  • the metrics application is further programmed to communicate, in cooperation with the at least one communication application, a result of the comparison, via the network interface, to at least the buyer-agent computing device from which the one or more product specification data sets were received.
  • a triggering request received from a buyer-agent computing device initiating the at least one evaluation service causes the at least one communication application to identify an applicable protocol for communicating with the buyer-agent computing device and triggers the metrics application to receive at least one evaluation scenario from the buyer-agent computing device for analysis.
  • the at least one scenario identifies two or more different purchase processes, at least one product specification data set, and at least one particular period of time.
  • Each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or identifies a plurality of items having a plurality of attributes that differ in accordance with at least one parameter value.
  • Receipt of at least one evaluation scenario triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each purchase process identified in the at least one evaluation scenario, to retrieve the buyer-agent's historical purchase data associated with the purchase process from one or more memories accessible to the remotely-located server.
  • the retrieved purchase data includes one or more price data sets responsive to at least one item identified in the at least one product specification data set over the at least one period of time identified in the evaluation scenario.
  • Each retrieved price data set includes price data for at least one item possessing a plurality of attributes having attribute data that includes at least one parameter value.
  • the metrics application is further caused to obtain metric data from at least one data source accessible to the remotely-located server.
  • the obtained metric data represents market reference data for at least one responsive item having attributes corresponding to attributes of a respective item as identified in the price data set and includes market reference price data of the at least one period of time identified in the evaluation scenario.
  • Each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value.
  • At least one responsive item in the obtained metric data differs by at least one parameter value from the respective item as identified in the price data set.
  • the metrics application evaluates the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the price data set to dynamically discover a difference in the attribute data.
  • the difference in the attribute data is disclosed to the metric server adapter and enables the metric server adapter to contextually determine which of the predefined instructions for managing metric data are applicable to the responsive item in the metric data.
  • the metric server adapter uses the attributes and one or more parameter values as identified for the respective item the price data set with the predefined instructions determined to be applicable to the responsive item in the metric data to dynamically define transaction-specific instructions for adapting the metric data for the respective item.
  • the metrics application normalizes the metric data by executing, in coordination with the metric server adapter, the transaction-specific instructions for adapting metric data for the respective item. Execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item as identified in the price data set, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item as identified in the price data set.
  • the metrics application For each of the two or more purchase processes identified in the evaluation scenario, the metrics application generates one or more evaluation metrics that pertain to the at least one evaluation service for the at least one item identified in the at least one product specification data set over the at least one period of time identified in the evaluation scenario.
  • Each evaluation metric is based, at least in part, on the transaction-specific market reference price data values produced for the respective item as identified in the price data sets associated with each purchase process.
  • the metrics application compares the two or more identified purchase processes using one or more of the evaluation metrics generated for each purchase process.
  • the metrics application is further programmed to communicate, in coordination with the at least one communication application, a result of the comparison, via the network interface, to at least the buyer-agent controlled computing device from which the at least one evaluation scenario was received.
  • FIG. 1 is a block diagram of a prior art representative portion of the Internet
  • FIG. 2 is a pictorial diagram of a system of devices connected to the Internet, which depict the travel route of data;
  • FIG. 3 is a block diagram of the several components of the buyer's computer shown in FIG. 2 that is used to request information on a particular route;
  • FIG. 4 is a block diagram of the several components of an information server shown in FIG. 2 that is used to supply information on a particular route;
  • FIG. 5 is a flow diagram illustrating the logic of a routine used by the information server to receive and process the buyer's actions
  • FIGS. 6A-6B are flow diagrams illustrating another embodiment of the logic used by the information server to receive and process the quotes and quote requests of both buyers and vendors;
  • FIG. 7 is a flow diagram illustrating another embodiment of the logic used by the information server to execute the process of a catalog purchase
  • FIGS. 8A-8D are images of windows produced by a Web browser application installed on a client computer accessing a server illustrating one embodiment of the present disclosure.
  • FIG. 9 is a flow diagram illustrating one embodiment of the normalization process described herein.
  • Internet refers to the collection of networks and routers that use the Internet Protocol (IP) to communicate with one another.
  • IP Internet Protocol
  • FIG. 1 A representative section of the Internet 100 as known in the prior art is shown in FIG. 1 in which a plurality of local area networks (LANs) 120 and a wide area network (WAN) 110 are interconnected by routers 125 .
  • the routers 125 are generally special-purpose computers used to interface one LAN or WAN to another.
  • Communication links within the LANs may be twisted wire pair, or coaxial cable, while communication links between networks may utilize 56 Kbps analog telephone lines, or 1 Mbps digital T ⁇ 1 lines, and/or 45 Mbps T ⁇ 3 lines.
  • computers and other related electronic devices can be remotely connected to either the LANs 120 or the WAN 110 via a modem and temporary telephone link.
  • Such computers and electronic devices 130 are shown in FIG. 1 as connected to one of the LANs 120 via dotted lines.
  • the Internet comprises a vast number of such interconnected networks, computers, and routers and that only a small representative section of the Internet 100 is shown in FIG. 1 .
  • the World Wide Web is a vast collection of interconnected, electronically stored information located on servers connected throughout the Internet 100 . Many companies are now providing services and access to their content over the Internet 100 using the WWW.
  • FIG. 2 generally shows a system 200 of computers and devices to which an information server 230 is connected and to which the buyers' computers 235 are also connected.
  • Also connected to the Internet 100 is a plurality of computing devices 250 associated with a plurality of sellers.
  • the system 200 also includes a communications program, referred to as CEA, which is used on the sellers' computing devices 250 to create a communication means between the sellers' backend office software and the server applications.
  • CEA communications program
  • the buyers of a market commodity may, through their computers 235 , request information about a plurality of items or order over the Internet 100 via a Web browser installed on the buyers' computers. Responsive to such requests, the information server 230 , also referred to as a server 230 , may combine the first buyer's information with information from other buyers on other computing devices 235 . The server 230 then transmits the combined buyer data to the respective computing devices 250 associated with the plurality of sellers. Details of this process are described in more detail below in association with FIGS. 5-7 .
  • the capabilities of the server 230 and/or the client computing devices 235 and 250 may all be embodied in the other configurations. Consequently, it would be appreciated that in these embodiments, the server 230 could be located on any computing device associated with the buyers' or sellers' computing devices. Additionally, those of ordinary skill in the art will recognize that while only four buyer computing devices 235 , four seller computing devices 250 , and one server 230 are depicted in FIG. 2 , numerous configurations involving a vast number of buyer and seller computing devices and a plurality of servers 230 , equipped with the hardware and software components described below, may be connected to the Internet 100 .
  • FIG. 3 depicts several of the key components of the buyer's client computing device 235 .
  • client computing devices 235 are also referred to as “clients” or “devices,” and client computing devices 235 also include other devices such as palm computing devices, cellular telephones, or other like forms of electronics.
  • a client computing device can also be the same computing device as the server 230 .
  • An “agent” can be a person, server, or a client computing device 235 having software configured to assist the buyer in making purchasing decisions based on one or more buyer-determined parameters.
  • the buyer's computer 235 in actual practice will include many more components than those shown in FIG. 3 .
  • the buyer's computer includes a network interface 315 for connecting to the Internet 100 .
  • the network interface 315 includes the necessary circuitry for such a connection and is also constructed for use with TCP/IP protocol.
  • the buyer's computer 235 also includes a processing unit 305 , a display 310 , and a memory 300 , all interconnected along with the network interface 315 via a bus 360 .
  • the memory 300 generally comprises a random access memory (RAM), a read-only memory (ROM), and a permanent mass storage device, such as a disk drive.
  • the memory 300 stores the program code necessary for requesting and/or depicting a desired route over the Internet 100 in accordance with the present disclosure. More specifically, the memory 300 stores a Web browser 330 , such as Netscape's NAVIGATOR® or Microsoft's INTERNET EXPLORER® browsers, used in accordance with the present disclosure for depicting a desired route over the Internet 100 .
  • memory 300 also stores an operating system 320 and a communications application 325 . It will be appreciated that these software components may be stored on a computer-readable medium and loaded into memory 300 of the buyers' computer 235 using a drive mechanism associated with the computer-readable medium, such as a floppy, tape, or CD-ROM drive.
  • FIG. 4 depicts several of the key components of the information server 230 .
  • the information server 230 includes many more components than shown in FIG. 4 . However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention.
  • the information server 230 is connected to the Internet 100 via a network interface 410 .
  • the network interface 410 includes the necessary circuitry for connecting the information server 230 to the Internet 100 , and is constructed for use with TCP/IP protocol.
  • the information server 230 also includes a processing unit 415 , a display 440 , and a mass memory 450 , all interconnected along with the network interface 410 via a bus 460 .
  • the mass memory 450 generally comprises a random access memory (RAM), read-only memory (ROM), and a permanent mass storage device, such as a hard disk drive, tape drive, optical drive, floppy disk drive, or combination thereof.
  • the mass memory 450 stores the program code and data necessary for incident and route analysis as well as supplying the results of that analysis to consumers in accordance with the present disclosure. More specifically, the mass memory 450 stores a metrics application 425 formed in accordance with the present disclosure for managing the purchase forums of commodities products, and a metric server adapter 435 for managing metric data.
  • mass memory 450 stores a database 445 of buyer information continuously logged by the information server 230 for statistical market analysis. It will be appreciated by those of ordinary skill in the art that the database 445 of product and buyer information may also be stored on other servers or storage devices connected to either the information server 230 or the Internet 100 .
  • mass memory 450 stores Web server software 430 for handling requests for stored information received via the Internet 100 and the WWW, and an operating system 420 . It will be appreciated that the aforementioned software components may be stored on a computer-readable medium and loaded into mass memory 450 of the information server 230 using a drive mechanism associated with the computer-readable medium, such as floppy, tape, or CD-ROM drive.
  • the data stored in the mass memory 450 and other memory can be “exposed” to other computers or persons for purposes of communicating data.
  • “exposing” data from a computing device could mean transmitting data to another device or person, transferring XML data packets, transferring data within the same computer, or other like forms of data communications.
  • FIG. 5 is a flow chart illustrating the logic implemented for the creation of a Request for Quote (RFQ) by a singular buyer or a pool of buyers.
  • RFQ Request for Quote
  • a buyer or a pool of buyers generate an RFQ which is displayed or transmitted to a plurality of sellers. Responsive to receiving the RFQ, the sellers then send quotes to the buyers.
  • the creation of the RFQ consists of at least one buyer initially entering general user identification information to initiate the process.
  • the buyer would then define a Line Item on a Web page displaying an RFQ form.
  • the Line Item is defined per industry specification and units of product are grouped as a “tally” per industry practice.
  • the pooling process 500 allows buyers to combine RFQ Line Items with other buyers with like needs.
  • the pool buy feature is created by a graphical user interface where the RFQ Line Items from a plurality of buyers are displayed on a Web page to one of the pool buyers, referred to as the pool administrator.
  • the server 230 also provides a Web-based feature allowing the pool administrator to selectively add each RFQ Line Item to one combined RFQ.
  • the combined RFQ is then sent to at least one vendor or seller.
  • This feature provides a forum for pooling the orders of many buyers, which allows individual entities or divisions of larger companies to advantageously bid for larger orders, thus providing them with more bidding power and the possibility of gaining a lower price.
  • the pooling process 500 begins in step 501 where a buyer initiates the process by providing buyer purchase data.
  • the buyer accesses a Web page transmitted from the server 230 configured to receive the buyer purchase data, also referred to as the product specification data set or the Line Item data.
  • a Web page for the logic of step 501 is depicted in FIG. 8A .
  • the buyer enters the Line Item data specifications in the fields of the Web page.
  • the Line Item data consists of lumber species and grade 803 , number of pieces per unit 804 , quantities of the various units comprising the preferred assortment in the tally 805 A-E, delivery method 806 , delivery date 807 , delivery location 808 , and the overall quantity 809 .
  • the buyer must define the delivery date as either contemporaneous “on-or-before” delivery date or specify a delivery date in the future for a “Forward Price” RFQ.
  • the buyer selects a metric or multiple metrics in a field 810 per RFQ Line Item (tally). As described in more detail below, the metric provides pricing data that is used as a reference point for the buyer to compare the various quotes returned from the sellers.
  • the buyer RFQ Line Item data is then stored in the memory of the server 230 .
  • the server 230 determines if the buyer is going to participate in a pool buy.
  • the server 230 provides an option in a Web page that allows the buyer to post their Line Item data to a vendor or post their Line Item data to a buyer pool.
  • the window illustrated in FIG. 8A is one exemplary Web page illustrating these options for a buyer. As shown in FIG. 8A , the links “Post Buyer Pool” 812 and “Post to Vendors” 814 are provided on the RFQ Web page.
  • step 503 if the buyer does not elect to participate in a pool buy, the process continues to step 513 where the server 230 generates a request for a quote (RFQ) from the buyer's Line Item data.
  • RFQ request for a quote
  • step 505 the system notifies other buyers logged into the server 230 that an RFQ is available in a pool, allowing other buyers to add additional Line Items (tallies) to the RFQ.
  • the Line Items from each buyer are received by and stored in the server memory.
  • the Line Items provided by each buyer in the pool are received by the server 230 using the same process as described above with reference to block 501 and the Web page of FIG. 8A . All of the Line Items stored on the server 230 are then displayed to a pool administrator via a Web page or an e-mail message.
  • the pool administrator is one of the buyers in a pool where the pool administrator has the capability to select all of the Line Item data to generate a combined RFQ.
  • the server 230 provides the pool administrator with this capability by the use of any Web-based communicative device, such as e-mail or HTML forms.
  • the pool may be left open for a predetermined period of time to allow additional buyers to add purchase data to the current RFQ.
  • the server 230 determines if the pool administrator has closed the pool. The logic of this step 509 is executed when the server 230 receives the combined RFQ data from the pool administrator.
  • the pool administrator can send the combined RFQ data to the server 230 via an HTML form or by other electronic messaging means such as e-mail or URL strings.
  • the process continues to block 510 where the Line Items from each buyer (the combined RFQ) are sent to all of the buyers in the pool.
  • the process then continues to step 513 where the server 230 sends the combined RFQ to the vendors or sellers.
  • the purchase-negotiation process 600 is also referred to as a solicited offer process or the market purchase process.
  • the purchase-negotiation process 600 allows at least one buyer to submit an RFQ and then view quotes from a plurality of vendors and purchase items from selected vendor(s).
  • the logic of FIG. 6A provides buyers with a forum that automatically manages, collects, and normalizes the price of desired commodity items.
  • the purchase-negotiation process 600 calculates a normalized price data set that is based on a predefined metric(s). The calculation of the normalized price data set in combination with the format of the Web pages described herein create an integrated forum where quotes for a plurality of inherently dissimilar products can be easily obtained and compared.
  • the purchase-negotiation process 600 begins at step 601 where the RFQ, as generated by one buyer or a pool of buyers in the process depicted in FIG. 5 , is sent to a plurality of computing devices 250 associated with a plurality of sellers or vendors.
  • the vendors receive the RFQ via a Web page transmitted by the server 230 .
  • the vendors receive an e-mail message having a hypertext link to the RFQ Web page to provide notice to the vendor.
  • the process then continues to step 603 where at least one vendor sends their quote information to the server 230 .
  • the vendors respond to the RFQ by sending their price quote to the server 230 for display via a Web page to the buyer or buyer pool.
  • the vendors send an HTML form or an e-mail message with a price and description of the order.
  • the description of the order in the quote message contains the same order information as the RFQ.
  • FIG. 8B illustrates one exemplary Web page of a vendor quote that is displayed to the buyer.
  • the vendor quote includes the vendor's price 813 , the lumber species and grade 803 , number of pieces per unit 804 , quantities of the various units comprising the preferred assortment in the tally 805 A-E, delivery method 806 , delivery date 807 , and delivery location 808 .
  • the vendor has the capability to modify any of the information that was submitted in the RFQ. For example, the vendor may edit the quantity values for the various units comprising the preferred assortment in the tally 805 A-E. This allows the vendor to adjust the buyer's request according to the vendor's inventory, best means of transportation, etc. All of the vendor's quote information is referred to as price data set or the RFQ Line Item (tally) quote.
  • step 605 the server 230 normalizes the price of each RFQ Line Item (tally) quote from each vendor.
  • the normalization of the vendor's price is a computation that evaluates the vendor's price utilizing data from a metric.
  • the normalization process is carried out because each vendor may respond to the Line Items of an RFQ by quoting products that are different from a buyer's RFQ and/or have a different tally configuration.
  • the normalization of the pricing allows the buyers to objectively compare the relative value of the different products offered by the plurality of vendors.
  • one vendor may produce a quote for an RFQ of one unit of 2 ⁇ 4 ⁇ 10, two units of 2 ⁇ 4 ⁇ 12, and three units of 2 ⁇ 4 ⁇ 16.
  • another vendor may submit a quote for three units of 2 ⁇ 4 ⁇ 10, one unit of 2 ⁇ 4 ⁇ 12, and two units of 2 ⁇ 4 ⁇ 16.
  • the price normalization process provides a means for the buyer to effectively compare and evaluate the different quotes even though there are variations in the products.
  • the price normalization process 900 is described in more detail below in conjunction with the flow diagram of FIG. 9 .
  • the vendor's quote information is communicated to the buyer's computer for display.
  • the vendor's quote is displayed via a Web page that communicates the vendor's quote price 813 and other purchase information.
  • the vendor's quote page contains a metric price 815 and a quote price versus metric price ratio 816 .
  • the metric price 815 and the quote price versus metric price ratio 816 are also referred to as a normalized price data value.
  • a ratio higher than one (1) indicates a quote price that is above the metric price, and a lower ratio indicates a quote price that is below the metric price.
  • the buyer or the administrator of the buyer pool compares the various products and prices quoted by the vendors along with the normalized price for each Line Item on the RFQ.
  • the buyer may decide to purchase one of the products from a particular vendor and sends a notification to the selected vendor indicating the same.
  • the buyer notifies the selected vendor by the use of an electronic means via the server 230 , such as an HTML form, a chat window, e-mail, etc.
  • the quote Web page depicted in FIG. 8B shows two different quotes with two different tallies, the first quote price 813 of $360, and the second quote price 813 A of $320. If the buyer determines that they prefer to purchase the materials listed in the first quote, the buyer selects the “Buy!” hyperlink 820 or 820 A associated with the desired tally.
  • the server 230 allows the buyer to further negotiate with one or more of the vendors to obtain a new quote. This step is shown in decision block 611 , where the buyer makes the determination to either accept a quoted price or proceed to step 613 where they negotiate with the vendor to obtain another quote or present a counter-offer.
  • the server 230 provides a graphical user interface configured to allow the buyer and one vendor to electronically communicate, using, e.g., a chat window, streaming voice communications, or other standard methods of communication. There are many forms of electronic communications known in the art that can be used to allow the buyer and vendors to communicate.
  • the buyer and seller negotiate various quotes and iterate through several steps 603 - 613 directed by the server 230 , where each quote is normalized, compared, and further negotiated until a quote is accepted by the buyer or negotiations cease. While the buyer and seller negotiate the various quotes, the server 230 stores each quote until the two parties agree on a price. At any step during the negotiation process, the system always presents the buyer with an option to terminate the negotiation if dissatisfied with the quote(s).
  • step 615 when a buyer agrees on a quoted price, the process then continues to step 615 where the buyer sends a notification message to the vendor indicating they have accepted a quote.
  • the buyer notification message of step 615 may be in the form of a message on a chat window, e-mail, by an HTML form, or the like.
  • the buyer notification must be transmitted in a format that allows the system to record the transaction.
  • the buyer notification may include all of the information regarding the specifications by RFQ Line Item, such as, but not limited to, the buy price, date, and method of shipment, and payment terms.
  • the purchase-negotiation process 600 is then finalized when the system, as shown in step 617 , sends a confirmation message to a tracking system.
  • the confirmation message includes all of the information related to the agreed sales transaction.
  • the process includes step 619 , where the server 230 stores all of the information related to RFQ, offers, and the final sales transaction in a historical database.
  • the server 230 stores all of the information related to RFQ, offers, and the final sales transaction in a historical database. This would allow the server 230 to use all of the transaction information in an analysis process for providing an improved method of obtaining a lower market price in future transactions and in identifying optimum purchasing strategy.
  • the analysis process is described in further detail below.
  • the illustrated embodiment is configured to store the data related to the sales transactions, the system can also be configured to store all of the iterative quote information exchanged between the buyer and vendor.
  • the unsolicited offer process 650 also referred to as the unsolicited market purchase process, allows at least one buyer to view unsolicited offers from a plurality of vendors and purchase items from a plurality of vendors from the offers.
  • the logic of FIG. 6B provides buyers with a forum that automatically manages, collects, and normalizes price quotes based on metric data.
  • the server 230 creates an integrated forum where offers from a plurality of inherently dissimilar products can be obtained and normalized for determination of purchase.
  • the unsolicited offer process 650 begins at step 651 where the plurality of vendors is able to submit offers to the server 230 . This part of the process is executed in a manner similar to step 603 of FIG. 6A , where the vendor submits a quote to the server 230 . However, in the Web page of step 651 , the server 230 generates a Web page containing several tallies from many different vendors. In addition, at step 651 , the server 230 stores all of the unsolicited offer data provided by the vendors.
  • a buyer views the offers stored on the server 230 .
  • This part of the process is carried out in a manner similar to the process of step 603 or 607 where the server 230 displays a plurality of offers similar to the tallies depicted in FIG. 8A .
  • metric data may come from publicly available information, i.e., price of futures contracts traded on the Chicago Mercantile Exchange, subscription services such as CrowesTM or Random LengthsTM accessed via the metric server adapter 435 (shown in FIG. 4 ), or internally generated metrics derived from the data stored in the server 230 .
  • the normalization calculation otherwise referred to as the normalization process, occurs each time the buyer views a different offer, and the normalization calculation uses the most current metric data for each calculation.
  • the normalization process is carried out because each vendor will most likely offer products that may vary from products of other vendors and have a different tally configuration from those supplied by other vendors.
  • the normalization of the pricing allows the buyers to compare the relative value of the different products offered by the number of vendors.
  • the metric price for each selected offer is displayed in a similar manner as the metric price 815 and 816 shown in the Web page of FIG. 8B .
  • the buyer selects at least one offer for purchase. This is similar to the process of FIG. 6A in that the buyer selects the “Buy!” hyperlink 820 associated with the desired tally to purchase an order.
  • the process then continues to steps 659 - 663 , where, at step 659 , the process transmits a buy notice to the vendor, then, at step 661 , sends a purchase confirmation to the tracking system, and then, at step 663 , saves the transaction data in the server database.
  • the steps 659 - 663 are carried out in the same manner as the steps 615 - 619 of FIG. 6A .
  • the buyer notification may include all of the information regarding the specifications by RFQ Line Item, and data such as, but not limited to, the buy price, date, and method of shipment, and the payment terms.
  • FIG. 7 a flow diagram illustrating yet another embodiment of the present disclosure is shown.
  • FIG. 7 illustrates the catalog purchase process 700 .
  • This embodiment allows buyers to search for a catalog price of desired commerce items, enter their purchase data based on the pre-negotiated catalog prices, and to compare those catalog prices with a selected metric price and the current market price, wherein the current market price is determined by the purchase-negotiation process 600 .
  • the process starts at step 701 where the buyer selects a program buy catalog 443 .
  • the program buy catalog 443 provides buyers with the published or pre-negotiated price of the desired products.
  • step 703 based on the catalog information, the buyer then enters their purchase data. Similar to step 501 of FIG. 5 and the tally shown in FIG. 8A , the buyer sends purchase data to the server 230 , such as the desired quantity of each item and the lumber species, grade, etc.
  • the process then proceeds to decision block 707 where the buyer makes a determination of whether to purchase the items using the catalog price or purchase the desired product in the open market.
  • the server 230 allows the user to make this determination by displaying the metric price of each catalog price. This format is similar to the metric price 815 and 816 displayed in FIG. 8B .
  • step 707 if the buyer determines that the catalog price is better than a selected metric price, the process then proceeds to steps 709 , 711 , and 713 , where a program buy from the catalog is executed, and the buyer's purchase information is stored on the server 230 and sent to the vendor's system to confirm the sale. These steps 711 - 713 are carried out in the same manner as the confirmation and save steps 617 and 619 as shown in FIG. 6A .
  • step 707 if the buyer determines that the metric price is better than the catalog price, the process continues to step 717 where the buyer's purchase data is entered into an RFQ. At this step, the process carries out the first five steps 601 - 609 of the method of FIG. 6A to provide buyers with the price data from the open market, as well as provide the normalized prices for each open market quote.
  • the server 230 displays a Web page that allows the user to select from a purchase option of a catalog or spot (market) purchase.
  • decision block 721 based on the displayed information, the buyer will then have an opportunity to make a determination of whether they will proceed with a catalog purchase or an open market purchase.
  • step 709 if the buyer proceeds with the catalog purchase, the process continues to step 709 where the catalog purchase is executed. Steps 709 - 713 used to carry out the catalog purchase are the same as if the buyer had selected the catalog purchase in step 707 . However, if at decision block 721 the buyer selects the option to proceed with the market purchase, the process continues to step 723 where the RFQ generated in step 717 is sent to the vendor. Here, the process carries out the steps of FIG. 6 to complete the open market purchase. More specifically, the process continues to step 609 where the buyer compares the normalized prices from each vendor. Once a vendor is selected, the negotiation process of steps 603 - 613 is carried out until the buyer decides to execute the purchase. Next, the transaction steps 615 - 619 are carried out to confirm the purchase, notify the tracking system, and save the transactional data on the historical database.
  • the process can include a step where the server 230 stores all of the information related to program buy and metric comparisons and the final sales transaction in a historical database. This would allow the server 230 to use all of the transaction information in an analysis process for providing an improved method of obtaining the value of the program.
  • the illustrated embodiment is configured to store the data related to the sales transactions, the system can also be configured to store all of the iterative quote information exchanged between the buyer and vendor.
  • the analysis process allows the server 230 to utilize the sales history records stored in steps 619 and 711 to generate price reports for communication to various third parties as well as provide a means of calculating current market prices for products sold in the above-described methods.
  • the sales history records are also used as the source for a metric, such as those used in the process of FIGS. 6A, 6B, and 7 .
  • the server 230 continually updates the historical database for each sales transaction.
  • the analysis reporting process allows a buyer or manager of buyers to conduct analysis on the historical information. This analysis would include multi-value cross compilation for purposes of determining purchasing strategies, buyer effectiveness, program performance, vendor performance, and measuring effectiveness of forward pricing as a risk management strategy.
  • FIG. 9 a flow diagram illustrating the logic of the normalization process 900 is shown.
  • the logic of the normalization process 900 resides on the server 230 and processes the quotes received from commodity sellers.
  • the logic begins at step 905 where quote data is obtained from the seller in response to the buyer's RFQ as described above.
  • routine 900 iteratively calculates the board footage (BF) of each type of lumber. Once all the totals are calculated for each type, routine 900 continues to step 915 where the server 230 calculates the total type price.
  • BF board footage
  • routine 900 iteratively calculates the total type price for the amount of each type of lumber specified in the quote. This is accomplished by taking the total board footage (BF) calculated in block 910 and multiplying the total BF by the price per MBF specified in the quote. Once all the prices are calculated for each type, routine 900 continues to step 920 where the server 230 calculates the total quoted price. At step 920 , the routine 900 calculates the total price for the quote by summing all of the total type prices calculated at step 915 .
  • BF total board footage
  • routine 900 iteratively retrieves the most current price for each type of lumber specified in the quote from a predefined metric source(s).
  • Metric data may come from publicly available information, i.e., price of futures contracts traded on the Chicago Mercantile Exchange, subscription service publications such as CrowesTM or Random LengthsTM accessed via the metric server adapter 435 (shown in FIG. 4 ), or internally generated metrics derived from the server database.
  • the routine 900 then iteratively calculates the market price for the quantity of each type of lumber in the quote.
  • routine 900 continues to step 935 where the routine 900 calculates the total market price for the quote by summing all the most current prices calculated in step 930 .
  • steps 910 - 920 are executed before steps 925 - 935
  • these two groups of steps can be executed in any order, or in parallel, so long as they are both executed before a comparison step 940 .
  • routine 900 compares the total quoted to the metric price to arrive at a comparative value.
  • the comparative value is a “percent of metric” value. A value higher than one hundred (100) percent indicates a price that is above the metric rate, and a lower percent indicates a price that is below the metric rate.
  • routine 900 can be further illustrated through an example utilizing specific exemplary data.
  • a buyer sends out a request for a quote (RFQ) requesting a lot of 2 ⁇ 4 S&B lumber consisting of five units of 2′′ ⁇ 4′′ ⁇ 8′, two units of 2′′ ⁇ 4′′ ⁇ 14′, and five units of 2′′ ⁇ 4′′ ⁇ 16′.
  • the buyer then receives quotes from three sellers.
  • Seller A responds with a tally of six units of 2′′ ⁇ 4′′ ⁇ 8′, four units of 2′′ ⁇ 4′′ ⁇ 14′, and three units of 2′′ ⁇ 4′′ ⁇ 16′ for $287 per thousand board feet.
  • Seller B responds with a lot of five units of 2′′ ⁇ 4′′ ⁇ 8′, one unit of 2′′ ⁇ 4′′ ⁇ 14′, and six units of 2′′ ⁇ 4′′ ⁇ 16′ for $283 per thousand board feet.
  • Seller C responds with a lot of one unit of 2′′ ⁇ 4′′ ⁇ 8′, five units of 2′′ ⁇ 4′′ ⁇ 14′, and five units of 2′′ ⁇ 4′′ ⁇ 16′ for $282 per thousand board feet.
  • the typical unit size is 294 pieces/unit, and the metric or reported market price for 2′′ ⁇ 4′′ ⁇ 8's is $287.50, for 2′′ ⁇ 4′′ ⁇ 14's is $278.50, and for 2′′ ⁇ 4′′ ⁇ 16′ is $288.
  • additional exemplary data is used to demonstrate the analysis of a transaction having one RFQ from a buyer and two different quotes from a seller, normalized to comparable product of another species.
  • the buyer produces an RFQ listing the following items: one carload of Eastern SPF (ESPF) lumber having four units of 2′′ ⁇ 4′′ ⁇ 8′, four units of 2′′ ⁇ 4′′ ⁇ 10′, six units of 2′′ ⁇ 4′′ ⁇ 12′, two units of 2′′ ⁇ 4′′ ⁇ 14′, and six units of 2′′ ⁇ 4′′ ⁇ 16′.
  • EPF Eastern SPF
  • the first response lists a quote price of $320 per thousand board feet, and a slight modification of the tally provides four units of 2′′ ⁇ 4′′ ⁇ 8′, four units of 2′′ ⁇ 4′′ ⁇ 10′, six units of 2′′ ⁇ 4′′ ⁇ 12′, three units of 2′′ ⁇ 4′′ ⁇ 14′, and five units of 2′′x4′′x16′.
  • the second response quotes per the requested tally at a price of $322 per thousand board feet. Both quotes list the delivery location as “Chicago.”
  • the server 230 produces a Web page similar to that displayed in FIG. 8C , where the vendor's modified tally is displayed in highlighted text.
  • the buyer can then view summary metric comparison or select the hypertext link “View Calculation Detail,” which then invokes the server 230 to produce a Web page as shown in FIG. 8D .
  • the data produced by server 230 compares the response to a selected metric of a different species, Western SPF (WSPF), for items of the same size, grade, and tally.
  • WSPF Western SPF
  • the market price for the same 2 ⁇ 4 tally of ESPF and WSPF are thus simultaneously compared.
  • the buyer In review of the normalization process, the buyer must select a metric source for price information for a defined item given a set of attributes, i.e., grade, species, and size.
  • the metric may then be mapped to the RFQ item for comparison and does not have to be the equivalent of the item. For instance, as explained in the above-described example, it may be desirable to map the market relationship of one commodity item to another.
  • the most current pricing data for the metric is electronically moved from the selected source to the server 230 .
  • metric data may come from publicly available information, (i.e., price of futures contracts traded on the Chicago Mercantile Exchange), or subscription services, (i.e., CrowesTM or Random LengthsTM publications), or be an internal metric generated by the server 230 .
  • This metric data is used in the normalization process for all calculations, as described with reference to the above-described methods.
  • the above system and method can be used to purchase other commodity items, such as in the trade of livestock.
  • order information such as a lumber tally would be substituted for a meat type, grade, and cut.
  • Other examples of commodity items include agricultural products, metals, or any other items of commerce having several order parameters.

Abstract

A system includes a remotely-located server implementing a metric server adapter, a metrics application, and a communication application. The metric server adapter includes governing logic that manages at least one evaluation service and a plurality of predefined instructions for managing metric data. The metrics application is a production application that operates in coordination with the metric server adapter. Receipt or retrieval of at least one price data set triggers the metrics application to obtain metric data that includes market reference price data, evaluate attributes of each responsive item in the metric data to dynamically discover a difference in the attribute data, and dynamically define transaction-specific instructions for adapting the metric data for a respective item in the price data set. One or more adjustment values transform the market reference price data, and one or more evaluation metrics are communicated to the buyer-agent computing device.

Description

    BACKGROUND
  • Technical Field
  • This present disclosure generally relates to electronic commerce software applications and, more particularly, to evaluating prices and transactions for purchasing.
  • Description of the Related Art
  • Commodity items such as lumber, agricultural products, metals, and livestock/meat are usually traded in the open market between a number of buyers and sellers. The sales transactions of most commodity items involve a number of parameters. For instance, in the trade of commodity lumber, a buyer usually orders materials by specifying parameters such as lumber species, grade, size (i.e., 2×4, 2×10, etc.), and length, as well as the “tally” or mix of units of various lengths within the shipment, method of transportation (i.e., rail or truck), shipping terms (i.e., FOB or delivered), and desired date of receipt, with each parameter influencing the value of the commodity purchase. Given the multiple possible combinations of factors, a commodity buyer often finds it difficult to objectively compare similar but unequal offerings among competing vendors.
  • For example, in a case where a lumber buyer desires to order a railcar load of spruce (SPF) 2×4's of #2 & Better grade, the buyer would query vendors offering matching species and grade carloads seeking the best match for the buyer's need or tally preference at the lowest market price. Lumber carloads are quoted at a price per thousand board feet for all material on the railcar. When the quoted parameters are not identical, it is very difficult for buyers to determine the comparative value of unequal offerings.
  • Typically, a lumber buyer will find multiple vendors each having different offerings available. For example, a railcar of SPF 2×4's may be quoted at a rate of $300/MBF (thousand board feet) by multiple vendors. Even though the MBF price is equal, one vendor's carload may represent significantly greater marketplace value because it contains the more desirable lengths of 2×4's, such as market-preferred 16-foot 2×4's. When the offering price varies in addition to the mix of lengths, it becomes increasingly difficult to compare quotes from various vendors. Further, because construction projects often require long lead times, the lumber product may need to be priced now, but not delivered until a time in the future. Alternately, another species of lumber (i.e., southern pine) may represent an acceptable substitute.
  • Therefore, from the foregoing, there is a need for a method and system that allows buyers to evaluate the price of commodity offerings possessing varying shipping parameters.
  • BRIEF SUMMARY
  • Described herein is a system that operates in a networked environment. In at least one aspect, the system comprises a remotely-located server that includes a network interface, a non-transitory computer-readable medium having computer-executable instructions stored thereon, and a processor in communication with the network interface and the computer-readable medium. The processor is configured to execute the computer-executable instructions stored in the computer-readable medium. When executed, the computer-executable instructions implement a plurality of applications including a metric server adapter, a metrics application, and at least one communication application.
  • The metric server adapter is a governing logic application programmed to manage at least one evaluation service and a plurality of predefined instructions for managing metric data, including industry-specific instructions or a buyer-agent's customized instructions, to dynamically define transaction-specific instructions for adapting metric data.
  • The metrics application is a production application programmed to manage one or more purchase and/or analysis processes and to invoke and execute the at least one evaluation service in coordination with the governing logic application. The metrics application is further programmed to manage one or more user interfaces that, in operation, facilitate interactions with the remotely-located server.
  • The at least one communication application is programmed to manage one or more protocols that facilitate communications between one or more computing devices and the remotely-located server via the network interface. In operation, a triggering request received from a buyer-agent computing device initiating the at least one evaluation service causes the at least one communication application to identify an applicable protocol for communicating with the buyer-agent computing device and triggers the metrics application to receive one or more product specification data sets from the buyer-agent computing device. Each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or a plurality of items having a plurality of attributes that differ in accordance with at least one parameter value.
  • Using one or more purchase processes, the metrics application receives or retrieves a plurality of price data sets responsive to at least one item identified in the one or more product specification data sets. Each received or retrieved price data set represents an offer to sell and includes price data for at least one item possessing a plurality of attributes having attribute data that includes at least one parameter value.
  • Receipt or retrieval of at least one price data set triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each price data set, to obtain metric data from at least one data source accessible to the remotely-located server. The obtained metric data represents market reference data for at least one responsive item having attributes corresponding to attributes of a respective item as identified in the price data set and includes market reference price data of a current time or current period of time. Each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value, and wherein at least one responsive item in the obtained metric data differs by at least one parameter value from the respective item as identified in the price data set.
  • The metrics application is further caused to evaluate the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the price data set to dynamically discover a difference in the attribute data. The difference in the attribute data is disclosed to the metric server adapter and enables the metric server adapter to contextually determine which of the predefined instructions for managing metric data are applicable to the responsive item in the metric data. The metric server adapter uses the attributes and one or more parameter values as identified for the respective item in the price data set with the predefined instructions determined to be applicable to the responsive item in the metric data to dynamically define transaction-specific instructions for adapting the metric data for the respective item.
  • The metrics application normalizes the metric data by executing, in coordination with the metric server adapter, the transaction-specific instructions for adapting the metric data for the respective item. Execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item as identified in the price data set, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item as identified in the price data set.
  • The metrics application generates one or more evaluation metrics that pertain to the at least one evaluation service for the respective item as identified in the price data set. Each evaluation metric is based, at least in part, on the one or more transaction-specific market reference price data values produced for the respective item as identified in the price data set. The metrics application sorts and/or ranks the plurality of price data sets using one or more of the evaluation metrics generated for the at least one item as identified in each price data set.
  • The metrics application is further programmed to communicate, in cooperation with the at least one communication application, at least a subset of the sorted and/or ranked price data sets and the one or more evaluation metrics generated for the at least one item as identified in each communicated price data set to at least the buyer-agent computing device from which the one or more product specification data sets were received.
  • In another aspect of the present disclosure, a triggering request received from a user-agent computing device initiating the at least one evaluation service causes the at least one communication application to identify an applicable protocol for communicating with the user-agent computing device and triggers the metrics application to receive at least one product specification data set from the user-agent computing device. Each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or a plurality of items having a plurality of attributes that differ in accordance with at least one parameter value. Using one or more purchase processes, the metrics application receives or retrieves at least one price data set responsive to at least one item identified in the at least one product specification data set. The at least one price data set represents an offer to sell and includes price data for at least one item possessing a plurality of attributes having attribute data that includes at least one parameter value.
  • Receipt of at least one product specification data set and receipt or retrieval at least one price data set responsive to at least one item identified in the at least one product specification data set triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each received product specification data set and for each received or retrieved price data set, to obtain metric data from at least one data source accessible to the remotely-located server. The obtained metric data represents market reference data for at least one responsive item having attributes that correspond to attributes of a respective item as identified in the product specification data set or the price data set and includes market reference price data of a current time or current period of time. Each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value, and at least one responsive item in the obtained metric data differs by at least one parameter value from the respective item as identified in the product specification data set or the price data set.
  • The metrics application is further causes to evaluate the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the product specification data set or the price data set to dynamically discover a difference in the attribute data. The difference in the attribute data is disclosed to the metric server adapter and enables the metric server adapter to contextually determine which of the predefined instructions for managing metric data are applicable to the responsive item in the metric data. The metric server adapter uses the attributes and one or more parameter values as identified for the respective item in the product specification data set or the price data set with the predefined instructions determined to be applicable to the responsive item in the metric data to dynamically define transaction-specific instructions for adapting the metric data for the respective item.
  • The metrics application normalizes the metric data by executing, in coordination with the metric server adapter, the transaction-specific instructions for adapting the metric data for the respective item in the product specification data set or the price data set. Execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item as identified in the product specification data set or the price data set, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item as identified in the product specification data set or the price data set.
  • The metrics application generates one or more evaluation metrics that pertain to the at least one evaluation service for the respective item as identified in the product specification data set and as identified in the received or retrieved price data set. Each evaluation metric is based, at least in part, on the one or more transaction-specific market reference data values produced for the respective item.
  • The metrics application is further programmed to communicate, in cooperation with the at least one communication application, the one or more evaluation metrics generated for the at least one item as identified in each product specification data set and each price data set, via the network interface, to at least the user-agent computing device from which the one or more product specification data sets were received.
  • In yet another aspect of the present disclosure, a triggering request received from a buyer-agent computing device initiating the at least one evaluation service causes the at least one communication application to identify an applicable protocol for communicating with the buyer-agent computing device and triggers the metrics application to receive one or more product specification data sets from a buyer-agent computing device. Each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or a plurality of items having a plurality of attributes that differ in accordance with at least one parameter value.
  • Using a first purchase process, the metrics application receives or retrieves at least one price data set responsive to at least one item identified in the one or more product specification data sets. Each price data set comprises an offer to sell that includes price data for at least one item possessing a plurality of attributes having attribute data that includes at least one parameter value.
  • Receipt or retrieval of at least one price data set triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each price data set, to obtain metric data from at least one data source accessible to the remotely-located server. The obtained metric data represents market reference data for at least one responsive item having attributes corresponding to attributes of a respective item as identified in the price data set and includes market reference price data of a current time or current period of time. Each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value, and wherein at least one responsive item in the obtained metric data differs by at least one parameter value from the respective item as identified in the price data set.
  • The metrics application is further caused to evaluate the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the price data set to dynamically discover a difference in the attribute data. The difference in the attribute data is disclosed to the metric server adapter and enables the metric server adapter to contextually determine which of the predefined instructions for managing metric data are applicable to the responsive item in the metric data. The metric server adapter uses the attributes and one or more parameter values as identified for the respective item in the price data set with the predefined instructions determined to be applicable to the responsive item in the metric data to dynamically define transaction-specific instructions for adapting the metric data for the respective item.
  • The metrics application normalizes the metric data by executing, in coordination with the metric server adapter, the transaction-specific instructions for adapting the metric data for the respective item. Execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item identified in the price data set, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item as identified in the price data set.
  • The metrics application generates one or more evaluation metrics that pertain to the at least one evaluation service for the respective item as identified in the price data set received or retrieved via the first purchase process. Each evaluation metric is based, at least in part, on the one or more transaction-specific market reference data values produced for the respective item as identified in the price data set. At least one evaluation metric comprises a ratio or index value, wherein price data for the respective item in the price data set is divided by one or a combination of transaction-specific market reference price data values produced for the respective item, to generate a relative value metric.
  • If no price data set received or retrieved via the first purchase process has a relative value metric of less than one, the metrics application is programmed to retrieve or receive at least one price data set having an item that is responsive to at least one item identified in the one or more product specification data sets using a second, different purchase process. The metrics application is further programmed to produce, in coordination with the metric server adapter, one or more transaction-specific market reference price data values for the respective item as identified in each price data set received or retrieved via the second purchase process and to generate the one or more evaluation metrics, including a relative value metric, for the at least one item as identified in each price data set received or retrieved via the second purchase process.
  • The metrics application compares the price data sets received or retrieved via each purchase process, wherein the relative value metric generated for the respective item as identified in each price data set provides an objective measure to compare the first and second purchase processes. The metrics application is further programmed to communicate, in cooperation with the at least one communication application, a result of the comparison, via the network interface, to at least the buyer-agent computing device from which the one or more product specification data sets were received.
  • In still another aspect of the present disclosure, a triggering request received from a buyer-agent computing device initiating the at least one evaluation service causes the at least one communication application to identify an applicable protocol for communicating with the buyer-agent computing device and triggers the metrics application to receive at least one evaluation scenario from the buyer-agent computing device for analysis. The at least one scenario identifies two or more different purchase processes, at least one product specification data set, and at least one particular period of time. Each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or identifies a plurality of items having a plurality of attributes that differ in accordance with at least one parameter value.
  • Receipt of at least one evaluation scenario triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each purchase process identified in the at least one evaluation scenario, to retrieve the buyer-agent's historical purchase data associated with the purchase process from one or more memories accessible to the remotely-located server. The retrieved purchase data includes one or more price data sets responsive to at least one item identified in the at least one product specification data set over the at least one period of time identified in the evaluation scenario. Each retrieved price data set includes price data for at least one item possessing a plurality of attributes having attribute data that includes at least one parameter value.
  • The metrics application is further caused to obtain metric data from at least one data source accessible to the remotely-located server. The obtained metric data represents market reference data for at least one responsive item having attributes corresponding to attributes of a respective item as identified in the price data set and includes market reference price data of the at least one period of time identified in the evaluation scenario. Each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value. At least one responsive item in the obtained metric data differs by at least one parameter value from the respective item as identified in the price data set.
  • The metrics application evaluates the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the price data set to dynamically discover a difference in the attribute data. The difference in the attribute data is disclosed to the metric server adapter and enables the metric server adapter to contextually determine which of the predefined instructions for managing metric data are applicable to the responsive item in the metric data. The metric server adapter uses the attributes and one or more parameter values as identified for the respective item the price data set with the predefined instructions determined to be applicable to the responsive item in the metric data to dynamically define transaction-specific instructions for adapting the metric data for the respective item.
  • The metrics application normalizes the metric data by executing, in coordination with the metric server adapter, the transaction-specific instructions for adapting metric data for the respective item. Execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item as identified in the price data set, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item as identified in the price data set.
  • For each of the two or more purchase processes identified in the evaluation scenario, the metrics application generates one or more evaluation metrics that pertain to the at least one evaluation service for the at least one item identified in the at least one product specification data set over the at least one period of time identified in the evaluation scenario. Each evaluation metric is based, at least in part, on the transaction-specific market reference price data values produced for the respective item as identified in the price data sets associated with each purchase process.
  • The metrics application compares the two or more identified purchase processes using one or more of the evaluation metrics generated for each purchase process. The metrics application is further programmed to communicate, in coordination with the at least one communication application, a result of the comparison, via the network interface, to at least the buyer-agent controlled computing device from which the at least one evaluation scenario was received.
  • BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
  • The foregoing aspects and many of the attendant advantages of the present disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
  • FIG. 1 is a block diagram of a prior art representative portion of the Internet;
  • FIG. 2 is a pictorial diagram of a system of devices connected to the Internet, which depict the travel route of data;
  • FIG. 3 is a block diagram of the several components of the buyer's computer shown in FIG. 2 that is used to request information on a particular route;
  • FIG. 4 is a block diagram of the several components of an information server shown in FIG. 2 that is used to supply information on a particular route;
  • FIG. 5 is a flow diagram illustrating the logic of a routine used by the information server to receive and process the buyer's actions;
  • FIGS. 6A-6B are flow diagrams illustrating another embodiment of the logic used by the information server to receive and process the quotes and quote requests of both buyers and vendors;
  • FIG. 7 is a flow diagram illustrating another embodiment of the logic used by the information server to execute the process of a catalog purchase;
  • FIGS. 8A-8D are images of windows produced by a Web browser application installed on a client computer accessing a server illustrating one embodiment of the present disclosure; and
  • FIG. 9 is a flow diagram illustrating one embodiment of the normalization process described herein.
  • DETAILED DESCRIPTION
  • The term “Internet” refers to the collection of networks and routers that use the Internet Protocol (IP) to communicate with one another. A representative section of the Internet 100 as known in the prior art is shown in FIG. 1 in which a plurality of local area networks (LANs) 120 and a wide area network (WAN) 110 are interconnected by routers 125. The routers 125 are generally special-purpose computers used to interface one LAN or WAN to another. Communication links within the LANs may be twisted wire pair, or coaxial cable, while communication links between networks may utilize 56 Kbps analog telephone lines, or 1 Mbps digital T−1 lines, and/or 45 Mbps T−3 lines. Further, computers and other related electronic devices can be remotely connected to either the LANs 120 or the WAN 110 via a modem and temporary telephone link. Such computers and electronic devices 130 are shown in FIG. 1 as connected to one of the LANs 120 via dotted lines. It will be appreciated that the Internet comprises a vast number of such interconnected networks, computers, and routers and that only a small representative section of the Internet 100 is shown in FIG. 1.
  • The World Wide Web (WWW), on the other hand, is a vast collection of interconnected, electronically stored information located on servers connected throughout the Internet 100. Many companies are now providing services and access to their content over the Internet 100 using the WWW. In accordance with the present disclosure, and as shown in FIG. 2, there may be a plurality of buyers operating a plurality of client computing devices 235. FIG. 2 generally shows a system 200 of computers and devices to which an information server 230 is connected and to which the buyers' computers 235 are also connected. Also connected to the Internet 100 is a plurality of computing devices 250 associated with a plurality of sellers. The system 200 also includes a communications program, referred to as CEA, which is used on the sellers' computing devices 250 to create a communication means between the sellers' backend office software and the server applications.
  • The buyers of a market commodity may, through their computers 235, request information about a plurality of items or order over the Internet 100 via a Web browser installed on the buyers' computers. Responsive to such requests, the information server 230, also referred to as a server 230, may combine the first buyer's information with information from other buyers on other computing devices 235. The server 230 then transmits the combined buyer data to the respective computing devices 250 associated with the plurality of sellers. Details of this process are described in more detail below in association with FIGS. 5-7.
  • Those of ordinary skill in the art will appreciate that in other embodiments of the present disclosure, the capabilities of the server 230 and/or the client computing devices 235 and 250 may all be embodied in the other configurations. Consequently, it would be appreciated that in these embodiments, the server 230 could be located on any computing device associated with the buyers' or sellers' computing devices. Additionally, those of ordinary skill in the art will recognize that while only four buyer computing devices 235, four seller computing devices 250, and one server 230 are depicted in FIG. 2, numerous configurations involving a vast number of buyer and seller computing devices and a plurality of servers 230, equipped with the hardware and software components described below, may be connected to the Internet 100.
  • FIG. 3 depicts several of the key components of the buyer's client computing device 235. As known in the art, client computing devices 235 are also referred to as “clients” or “devices,” and client computing devices 235 also include other devices such as palm computing devices, cellular telephones, or other like forms of electronics. A client computing device can also be the same computing device as the server 230. An “agent” can be a person, server, or a client computing device 235 having software configured to assist the buyer in making purchasing decisions based on one or more buyer-determined parameters. Those of ordinary skill in the art will appreciate that the buyer's computer 235 in actual practice will include many more components than those shown in FIG. 3. However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention. As shown in FIG. 3, the buyer's computer includes a network interface 315 for connecting to the Internet 100. Those of ordinary skill in the art will appreciate that the network interface 315 includes the necessary circuitry for such a connection and is also constructed for use with TCP/IP protocol.
  • The buyer's computer 235 also includes a processing unit 305, a display 310, and a memory 300, all interconnected along with the network interface 315 via a bus 360. The memory 300 generally comprises a random access memory (RAM), a read-only memory (ROM), and a permanent mass storage device, such as a disk drive. The memory 300 stores the program code necessary for requesting and/or depicting a desired route over the Internet 100 in accordance with the present disclosure. More specifically, the memory 300 stores a Web browser 330, such as Netscape's NAVIGATOR® or Microsoft's INTERNET EXPLORER® browsers, used in accordance with the present disclosure for depicting a desired route over the Internet 100. In addition, memory 300 also stores an operating system 320 and a communications application 325. It will be appreciated that these software components may be stored on a computer-readable medium and loaded into memory 300 of the buyers' computer 235 using a drive mechanism associated with the computer-readable medium, such as a floppy, tape, or CD-ROM drive.
  • As will be described in more detail below, the user interface which allows products to be ordered by the buyers are supplied by a remote server, i.e., the information server 230 located elsewhere on the Internet, as illustrated in FIG. 2. FIG. 4 depicts several of the key components of the information server 230. Those of ordinary skill in the art will appreciate that the information server 230 includes many more components than shown in FIG. 4. However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the present invention. As shown in FIG. 4, the information server 230 is connected to the Internet 100 via a network interface 410. Those of ordinary skill in the art will appreciate that the network interface 410 includes the necessary circuitry for connecting the information server 230 to the Internet 100, and is constructed for use with TCP/IP protocol.
  • The information server 230 also includes a processing unit 415, a display 440, and a mass memory 450, all interconnected along with the network interface 410 via a bus 460. The mass memory 450 generally comprises a random access memory (RAM), read-only memory (ROM), and a permanent mass storage device, such as a hard disk drive, tape drive, optical drive, floppy disk drive, or combination thereof. The mass memory 450 stores the program code and data necessary for incident and route analysis as well as supplying the results of that analysis to consumers in accordance with the present disclosure. More specifically, the mass memory 450 stores a metrics application 425 formed in accordance with the present disclosure for managing the purchase forums of commodities products, and a metric server adapter 435 for managing metric data. In addition, mass memory 450 stores a database 445 of buyer information continuously logged by the information server 230 for statistical market analysis. It will be appreciated by those of ordinary skill in the art that the database 445 of product and buyer information may also be stored on other servers or storage devices connected to either the information server 230 or the Internet 100. Finally, mass memory 450 stores Web server software 430 for handling requests for stored information received via the Internet 100 and the WWW, and an operating system 420. It will be appreciated that the aforementioned software components may be stored on a computer-readable medium and loaded into mass memory 450 of the information server 230 using a drive mechanism associated with the computer-readable medium, such as floppy, tape, or CD-ROM drive. In addition, the data stored in the mass memory 450 and other memory can be “exposed” to other computers or persons for purposes of communicating data. Thus, “exposing” data from a computing device could mean transmitting data to another device or person, transferring XML data packets, transferring data within the same computer, or other like forms of data communications.
  • In accordance with one embodiment of the present disclosure, FIG. 5 is a flow chart illustrating the logic implemented for the creation of a Request for Quote (RFQ) by a singular buyer or a pool of buyers. In process of FIG. 5, also referred to as the pooling process 500, a buyer or a pool of buyers generate an RFQ which is displayed or transmitted to a plurality of sellers. Responsive to receiving the RFQ, the sellers then send quotes to the buyers.
  • In summary, the creation of the RFQ consists of at least one buyer initially entering general user identification information to initiate the process. The buyer would then define a Line Item on a Web page displaying an RFQ form. The Line Item is defined per industry specification and units of product are grouped as a “tally” per industry practice. The pooling process 500 allows buyers to combine RFQ Line Items with other buyers with like needs. In one embodiment, the pool buy feature is created by a graphical user interface where the RFQ Line Items from a plurality of buyers are displayed on a Web page to one of the pool buyers, referred to as the pool administrator. The server 230 also provides a Web-based feature allowing the pool administrator to selectively add each RFQ Line Item to one combined RFQ. The combined RFQ is then sent to at least one vendor or seller. This feature provides a forum for pooling the orders of many buyers, which allows individual entities or divisions of larger companies to advantageously bid for larger orders, thus providing them with more bidding power and the possibility of gaining a lower price.
  • The pooling process 500 begins in step 501 where a buyer initiates the process by providing buyer purchase data. In step 501, the buyer accesses a Web page transmitted from the server 230 configured to receive the buyer purchase data, also referred to as the product specification data set or the Line Item data. One exemplary Web page for the logic of step 501 is depicted in FIG. 8A. As shown in FIG. 8A, the buyer enters the Line Item data specifications in the fields of the Web page. The Line Item data consists of lumber species and grade 803, number of pieces per unit 804, quantities of the various units comprising the preferred assortment in the tally 805A-E, delivery method 806, delivery date 807, delivery location 808, and the overall quantity 809. In one embodiment, the buyer must define the delivery date as either contemporaneous “on-or-before” delivery date or specify a delivery date in the future for a “Forward Price” RFQ. In addition, the buyer selects a metric or multiple metrics in a field 810 per RFQ Line Item (tally). As described in more detail below, the metric provides pricing data that is used as a reference point for the buyer to compare the various quotes returned from the sellers. The buyer RFQ Line Item data is then stored in the memory of the server 230.
  • Returning to FIG. 5, at a next step 503, the server 230 determines if the buyer is going to participate in a pool buy. In the process of decision block 503, the server 230 provides an option in a Web page that allows the buyer to post their Line Item data to a vendor or post their Line Item data to a buyer pool. The window illustrated in FIG. 8A is one exemplary Web page illustrating these options for a buyer. As shown in FIG. 8A, the links “Post Buyer Pool” 812 and “Post to Vendors” 814 are provided on the RFQ Web page.
  • At step 503, if the buyer does not elect to participate in a pool buy, the process continues to step 513 where the server 230 generates a request for a quote (RFQ) from the buyer's Line Item data. A detailed description of how the server 230 generates a request for a quote (RFQ) is summarized below and referred to as the purchase order process 600A depicted in FIG. 6A.
  • Alternatively, at decision block 503, if the buyer elects to participate in a pool buy, the process continues to step 505 where the system notifies other buyers logged into the server 230 that an RFQ is available in a pool, allowing other buyers to add additional Line Items (tallies) to the RFQ. In this part of the process, the Line Items from each buyer are received by and stored in the server memory. The Line Items provided by each buyer in the pool are received by the server 230 using the same process as described above with reference to block 501 and the Web page of FIG. 8A. All of the Line Items stored on the server 230 are then displayed to a pool administrator via a Web page or an e-mail message. In one embodiment, the pool administrator is one of the buyers in a pool where the pool administrator has the capability to select all of the Line Item data to generate a combined RFQ. The server 230 provides the pool administrator with this capability by the use of any Web-based communicative device, such as e-mail or HTML forms. As part of the process, as shown in steps 507 and 509, the pool may be left open for a predetermined period of time to allow additional buyers to add purchase data to the current RFQ.
  • At decision block 509, the server 230 determines if the pool administrator has closed the pool. The logic of this step 509 is executed when the server 230 receives the combined RFQ data from the pool administrator. The pool administrator can send the combined RFQ data to the server 230 via an HTML form or by other electronic messaging means such as e-mail or URL strings. Once the server 230 has determined that the pool is closed, the process continues to block 510 where the Line Items from each buyer (the combined RFQ) are sent to all of the buyers in the pool. The process then continues to step 513 where the server 230 sends the combined RFQ to the vendors or sellers.
  • Referring now to FIG. 6A, one embodiment of the purchase-negotiation process 600 is disclosed. The purchase-negotiation process 600 is also referred to as a solicited offer process or the market purchase process. In summary, the purchase-negotiation process 600 allows at least one buyer to submit an RFQ and then view quotes from a plurality of vendors and purchase items from selected vendor(s). The logic of FIG. 6A provides buyers with a forum that automatically manages, collects, and normalizes the price of desired commodity items. The purchase-negotiation process 600 calculates a normalized price data set that is based on a predefined metric(s). The calculation of the normalized price data set in combination with the format of the Web pages described herein create an integrated forum where quotes for a plurality of inherently dissimilar products can be easily obtained and compared.
  • The purchase-negotiation process 600 begins at step 601 where the RFQ, as generated by one buyer or a pool of buyers in the process depicted in FIG. 5, is sent to a plurality of computing devices 250 associated with a plurality of sellers or vendors. The vendors receive the RFQ via a Web page transmitted by the server 230. In one embodiment, the vendors receive an e-mail message having a hypertext link to the RFQ Web page to provide notice to the vendor. Responsive to the information in the buyers' RFQ, the process then continues to step 603 where at least one vendor sends their quote information to the server 230.
  • In the process of step 603, the vendors respond to the RFQ by sending their price quote to the server 230 for display via a Web page to the buyer or buyer pool. Generally described, the vendors send an HTML form or an e-mail message with a price and description of the order. The description of the order in the quote message contains the same order information as the RFQ.
  • FIG. 8B illustrates one exemplary Web page of a vendor quote that is displayed to the buyer. As shown in FIG. 8B, the vendor quote includes the vendor's price 813, the lumber species and grade 803, number of pieces per unit 804, quantities of the various units comprising the preferred assortment in the tally 805A-E, delivery method 806, delivery date 807, and delivery location 808. In the quote response message, the vendor has the capability to modify any of the information that was submitted in the RFQ. For example, the vendor may edit the quantity values for the various units comprising the preferred assortment in the tally 805A-E. This allows the vendor to adjust the buyer's request according to the vendor's inventory, best means of transportation, etc. All of the vendor's quote information is referred to as price data set or the RFQ Line Item (tally) quote.
  • Returning to FIG. 6A, the process continues to step 605, where the server 230 normalizes the price of each RFQ Line Item (tally) quote from each vendor. The normalization of the vendor's price is a computation that evaluates the vendor's price utilizing data from a metric. The normalization process is carried out because each vendor may respond to the Line Items of an RFQ by quoting products that are different from a buyer's RFQ and/or have a different tally configuration. The normalization of the pricing allows the buyers to objectively compare the relative value of the different products offered by the plurality of vendors. For example, one vendor may produce a quote for an RFQ of one unit of 2×4×10, two units of 2×4×12, and three units of 2×4×16. At the same time, another vendor may submit a quote for three units of 2×4×10, one unit of 2×4×12, and two units of 2×4×16. Even though there is some difference between these two offerings, the price normalization process provides a means for the buyer to effectively compare and evaluate the different quotes even though there are variations in the products. The price normalization process 900 is described in more detail below in conjunction with the flow diagram of FIG. 9.
  • Returning again to FIG. 6A, at step 607 the vendor's quote information is communicated to the buyer's computer for display. As shown in FIG. 8B and described in detail above, the vendor's quote is displayed via a Web page that communicates the vendor's quote price 813 and other purchase information. In addition, the vendor's quote page contains a metric price 815 and a quote price versus metric price ratio 816. The metric price 815 and the quote price versus metric price ratio 816 are also referred to as a normalized price data value. A ratio higher than one (1) indicates a quote price that is above the metric price, and a lower ratio indicates a quote price that is below the metric price.
  • Next, at step 609, the buyer or the administrator of the buyer pool compares the various products and prices quoted by the vendors along with the normalized price for each Line Item on the RFQ. In this part of the process, the buyer may decide to purchase one of the products from a particular vendor and sends a notification to the selected vendor indicating the same. The buyer notifies the selected vendor by the use of an electronic means via the server 230, such as an HTML form, a chat window, e-mail, etc. For example, the quote Web page depicted in FIG. 8B shows two different quotes with two different tallies, the first quote price 813 of $360, and the second quote price 813A of $320. If the buyer determines that they prefer to purchase the materials listed in the first quote, the buyer selects the “Buy!” hyperlink 820 or 820A associated with the desired tally.
  • If the buyer is not satisfied with any of the listed vendor quotes, the server 230 allows the buyer to further negotiate with one or more of the vendors to obtain a new quote. This step is shown in decision block 611, where the buyer makes the determination to either accept a quoted price or proceed to step 613 where they negotiate with the vendor to obtain another quote or present a counter-offer. Here, the server 230 provides a graphical user interface configured to allow the buyer and one vendor to electronically communicate, using, e.g., a chat window, streaming voice communications, or other standard methods of communication. There are many forms of electronic communications known in the art that can be used to allow the buyer and vendors to communicate.
  • The buyer and seller negotiate various quotes and iterate through several steps 603-613 directed by the server 230, where each quote is normalized, compared, and further negotiated until a quote is accepted by the buyer or negotiations cease. While the buyer and seller negotiate the various quotes, the server 230 stores each quote until the two parties agree on a price. At any step during the negotiation process, the system always presents the buyer with an option to terminate the negotiation if dissatisfied with the quote(s).
  • At decision block 611, when a buyer agrees on a quoted price, the process then continues to step 615 where the buyer sends a notification message to the vendor indicating they have accepted a quote. As described above with reference to steps 603-613, the buyer notification message of step 615 may be in the form of a message on a chat window, e-mail, by an HTML form, or the like. However, the buyer notification must be transmitted in a format that allows the system to record the transaction. The buyer notification may include all of the information regarding the specifications by RFQ Line Item, such as, but not limited to, the buy price, date, and method of shipment, and payment terms.
  • The purchase-negotiation process 600 is then finalized when the system, as shown in step 617, sends a confirmation message to a tracking system. The confirmation message includes all of the information related to the agreed sales transaction.
  • Optionally, the process includes step 619, where the server 230 stores all of the information related to RFQ, offers, and the final sales transaction in a historical database. This would allow the server 230 to use all of the transaction information in an analysis process for providing an improved method of obtaining a lower market price in future transactions and in identifying optimum purchasing strategy. The analysis process is described in further detail below. Although the illustrated embodiment is configured to store the data related to the sales transactions, the system can also be configured to store all of the iterative quote information exchanged between the buyer and vendor.
  • Referring now to FIG. 6B, an embodiment of the unsolicited offer process 650 is disclosed. In summary, the unsolicited offer process 650, also referred to as the unsolicited market purchase process, allows at least one buyer to view unsolicited offers from a plurality of vendors and purchase items from a plurality of vendors from the offers. The logic of FIG. 6B provides buyers with a forum that automatically manages, collects, and normalizes price quotes based on metric data. By the price normalization method of FIG. 6B, the server 230 creates an integrated forum where offers from a plurality of inherently dissimilar products can be obtained and normalized for determination of purchase.
  • The unsolicited offer process 650 begins at step 651 where the plurality of vendors is able to submit offers to the server 230. This part of the process is executed in a manner similar to step 603 of FIG. 6A, where the vendor submits a quote to the server 230. However, in the Web page of step 651, the server 230 generates a Web page containing several tallies from many different vendors. In addition, at step 651, the server 230 stores all of the unsolicited offer data provided by the vendors.
  • Next, at step 653, a buyer views the offers stored on the server 230. This part of the process is carried out in a manner similar to the process of step 603 or 607 where the server 230 displays a plurality of offers similar to the tallies depicted in FIG. 8A.
  • Next, at step 655, the buyer selects a metric for the calculation of the normalized price associated with the selected offer. As described in more detail below, metric data may come from publicly available information, i.e., price of futures contracts traded on the Chicago Mercantile Exchange, subscription services such as Crowes™ or Random Lengths™ accessed via the metric server adapter 435 (shown in FIG. 4), or internally generated metrics derived from the data stored in the server 230. The normalization calculation, otherwise referred to as the normalization process, occurs each time the buyer views a different offer, and the normalization calculation uses the most current metric data for each calculation. The normalization process is carried out because each vendor will most likely offer products that may vary from products of other vendors and have a different tally configuration from those supplied by other vendors. The normalization of the pricing allows the buyers to compare the relative value of the different products offered by the number of vendors. The metric price for each selected offer is displayed in a similar manner as the metric price 815 and 816 shown in the Web page of FIG. 8B.
  • Next, at decision block 657, the buyer selects at least one offer for purchase. This is similar to the process of FIG. 6A in that the buyer selects the “Buy!” hyperlink 820 associated with the desired tally to purchase an order. The process then continues to steps 659-663, where, at step 659, the process transmits a buy notice to the vendor, then, at step 661, sends a purchase confirmation to the tracking system, and then, at step 663, saves the transaction data in the server database. The steps 659-663 are carried out in the same manner as the steps 615-619 of FIG. 6A. In the above-described process, the buyer notification may include all of the information regarding the specifications by RFQ Line Item, and data such as, but not limited to, the buy price, date, and method of shipment, and the payment terms.
  • Referring now to FIG. 7, a flow diagram illustrating yet another embodiment of the present disclosure is shown. FIG. 7 illustrates the catalog purchase process 700. This embodiment allows buyers to search for a catalog price of desired commerce items, enter their purchase data based on the pre-negotiated catalog prices, and to compare those catalog prices with a selected metric price and the current market price, wherein the current market price is determined by the purchase-negotiation process 600.
  • The process starts at step 701 where the buyer selects a program buy catalog 443. The program buy catalog 443 provides buyers with the published or pre-negotiated price of the desired products. Next, at step 703, based on the catalog information, the buyer then enters their purchase data. Similar to step 501 of FIG. 5 and the tally shown in FIG. 8A, the buyer sends purchase data to the server 230, such as the desired quantity of each item and the lumber species, grade, etc.
  • The process then proceeds to decision block 707 where the buyer makes a determination of whether to purchase the items using the catalog price or purchase the desired product in the open market. Here, the server 230 allows the user to make this determination by displaying the metric price of each catalog price. This format is similar to the metric price 815 and 816 displayed in FIG. 8B.
  • At decision block 707, if the buyer determines that the catalog price is better than a selected metric price, the process then proceeds to steps 709, 711, and 713, where a program buy from the catalog is executed, and the buyer's purchase information is stored on the server 230 and sent to the vendor's system to confirm the sale. These steps 711-713 are carried out in the same manner as the confirmation and save steps 617 and 619 as shown in FIG. 6A.
  • At decision block 707, if the buyer determines that the metric price is better than the catalog price, the process continues to step 717 where the buyer's purchase data is entered into an RFQ. At this step, the process carries out the first five steps 601-609 of the method of FIG. 6A to provide buyers with the price data from the open market, as well as provide the normalized prices for each open market quote. At step 719, the server 230 then displays a Web page that allows the user to select from a purchase option of a catalog or spot (market) purchase. At decision block 721, based on the displayed information, the buyer will then have an opportunity to make a determination of whether they will proceed with a catalog purchase or an open market purchase.
  • At decision block 721, if the buyer proceeds with the catalog purchase, the process continues to step 709 where the catalog purchase is executed. Steps 709-713 used to carry out the catalog purchase are the same as if the buyer had selected the catalog purchase in step 707. However, if at decision block 721 the buyer selects the option to proceed with the market purchase, the process continues to step 723 where the RFQ generated in step 717 is sent to the vendor. Here, the process carries out the steps of FIG. 6 to complete the open market purchase. More specifically, the process continues to step 609 where the buyer compares the normalized prices from each vendor. Once a vendor is selected, the negotiation process of steps 603-613 is carried out until the buyer decides to execute the purchase. Next, the transaction steps 615-619 are carried out to confirm the purchase, notify the tracking system, and save the transactional data on the historical database.
  • Optionally, the process can include a step where the server 230 stores all of the information related to program buy and metric comparisons and the final sales transaction in a historical database. This would allow the server 230 to use all of the transaction information in an analysis process for providing an improved method of obtaining the value of the program. Although the illustrated embodiment is configured to store the data related to the sales transactions, the system can also be configured to store all of the iterative quote information exchanged between the buyer and vendor.
  • The analysis process allows the server 230 to utilize the sales history records stored in steps 619 and 711 to generate price reports for communication to various third parties as well as provide a means of calculating current market prices for products sold in the above-described methods. The sales history records are also used as the source for a metric, such as those used in the process of FIGS. 6A, 6B, and 7. As shown in steps 619, 663, and 711, the server 230 continually updates the historical database for each sales transaction. The analysis reporting process allows a buyer or manager of buyers to conduct analysis on the historical information. This analysis would include multi-value cross compilation for purposes of determining purchasing strategies, buyer effectiveness, program performance, vendor performance, and measuring effectiveness of forward pricing as a risk management strategy.
  • Referring now to FIG. 9, a flow diagram illustrating the logic of the normalization process 900 is shown. The logic of the normalization process 900 resides on the server 230 and processes the quotes received from commodity sellers. The logic begins at step 905 where quote data is obtained from the seller in response to the buyer's RFQ as described above.
  • Next, at step 910, routine 900 iteratively calculates the board footage (BF) of each type of lumber. Once all the totals are calculated for each type, routine 900 continues to step 915 where the server 230 calculates the total type price.
  • At step 915, routine 900 iteratively calculates the total type price for the amount of each type of lumber specified in the quote. This is accomplished by taking the total board footage (BF) calculated in block 910 and multiplying the total BF by the price per MBF specified in the quote. Once all the prices are calculated for each type, routine 900 continues to step 920 where the server 230 calculates the total quoted price. At step 920, the routine 900 calculates the total price for the quote by summing all of the total type prices calculated at step 915.
  • At step 925, routine 900 iteratively retrieves the most current price for each type of lumber specified in the quote from a predefined metric source(s). Metric data may come from publicly available information, i.e., price of futures contracts traded on the Chicago Mercantile Exchange, subscription service publications such as Crowes™ or Random Lengths™ accessed via the metric server adapter 435 (shown in FIG. 4), or internally generated metrics derived from the server database. Once all the prices are retrieved for each type, at step 930, the routine 900 then iteratively calculates the market price for the quantity of each type of lumber in the quote. Once the totals for all types are calculated, routine 900 continues to step 935 where the routine 900 calculates the total market price for the quote by summing all the most current prices calculated in step 930. Although this example illustrates that steps 910-920 are executed before steps 925-935, these two groups of steps can be executed in any order, or in parallel, so long as they are both executed before a comparison step 940.
  • At step 940, routine 900 compares the total quoted to the metric price to arrive at a comparative value. In one exemplary embodiment of the current invention, the comparative value is a “percent of metric” value. A value higher than one hundred (100) percent indicates a price that is above the metric rate, and a lower percent indicates a price that is below the metric rate.
  • The operation of routine 900 can be further illustrated through an example utilizing specific exemplary data. In the example, a buyer sends out a request for a quote (RFQ) requesting a lot of 2×4 S&B lumber consisting of five units of 2″×4″×8′, two units of 2″×4″×14′, and five units of 2″×4″×16′. The buyer then receives quotes from three sellers. Seller A responds with a tally of six units of 2″×4″×8′, four units of 2″×4″×14′, and three units of 2″×4″×16′ for $287 per thousand board feet. Seller B responds with a lot of five units of 2″×4″×8′, one unit of 2″×4″×14′, and six units of 2″×4″×16′ for $283 per thousand board feet. Seller C responds with a lot of one unit of 2″×4″×8′, five units of 2″×4″×14′, and five units of 2″×4″×16′ for $282 per thousand board feet. Suppose also that the typical unit size is 294 pieces/unit, and the metric or reported market price for 2″×4″×8's is $287.50, for 2″×4″×14's is $278.50, and for 2″×4″×16′ is $288.
  • Viewing the MBF prices for the respective quotes is not particularly informative, given that certain lengths of lumber are more desirable and priced accordingly in the marketplace. By processing the quote from Seller A using routine 900, we arrive at a total MBF of 29.792, giving a total quoted price of $8,550.30. The selected metric price for the same types and quantities of lumber would be $8,471.12; therefore, the quoted price would have a percent of market value of 100.93%. Processing the quote from Seller B using routine 900, we arrive at a total MBF of 29.400, giving a total quoted price of $8,320.20. The selected metric price for the same types and quantities of lumber, however, would be $8,437.21; therefore, the quoted price would have a percent of market value of 98.61%. Finally, processing the quote from Seller C using routine 900, we arrive at a total MBF of 30.968, giving a total quoted price of $8,732.98. The selected metric price for the same types and quantities of lumber, however, would be $8,767.66; therefore, the quoted price would have a percent of market value of 99.38%. By looking at the percent of selected metric value, it is apparent that the price from Seller B is a better value. As shown in the methods of FIGS. 5-7, this price normalization process allows users to compare inherently different offers having different quality and quantity values.
  • In yet another example of an application of the normalization process, additional exemplary data is used to demonstrate the analysis of a transaction having one RFQ from a buyer and two different quotes from a seller, normalized to comparable product of another species. In this example, the buyer produces an RFQ listing the following items: one carload of Eastern SPF (ESPF) lumber having four units of 2″×4″×8′, four units of 2″×4″×10′, six units of 2″×4″×12′, two units of 2″×4″×14′, and six units of 2″×4″×16′. The vendor then responds with two different quotes with two different unit tallies and two different prices. The first response lists a quote price of $320 per thousand board feet, and a slight modification of the tally provides four units of 2″×4″×8′, four units of 2″×4″×10′, six units of 2″×4″×12′, three units of 2″×4″×14′, and five units of 2″x4″x16′. The second response quotes per the requested tally at a price of $322 per thousand board feet. Both quotes list the delivery location as “Chicago.”
  • To display the quotes, the server 230 produces a Web page similar to that displayed in FIG. 8C, where the vendor's modified tally is displayed in highlighted text. The buyer can then view summary metric comparison or select the hypertext link “View Calculation Detail,” which then invokes the server 230 to produce a Web page as shown in FIG. 8D. Referring now to the Web page illustrated in FIG. 8D, the data produced by server 230 compares the response to a selected metric of a different species, Western SPF (WSPF), for items of the same size, grade, and tally. The market price for the same 2×4 tally of ESPF and WSPF are thus simultaneously compared. In an example, Eastern quoted at $322 per thousand board feet, Western metric (Random Lengths™ Jun. 26, 2000 print price plus freight of $80 as defined in Metric Manager) for the same tally being $331.791. This metric comparison is also represented as Quote/Metric Value or Eastern price representing 0.970490, or 97% of comparable Western product.
  • In review of the normalization process, the buyer must select a metric source for price information for a defined item given a set of attributes, i.e., grade, species, and size. The metric may then be mapped to the RFQ item for comparison and does not have to be the equivalent of the item. For instance, as explained in the above-described example, it may be desirable to map the market relationship of one commodity item to another. The most current pricing data for the metric is electronically moved from the selected source to the server 230. As mentioned above, metric data may come from publicly available information, (i.e., price of futures contracts traded on the Chicago Mercantile Exchange), or subscription services, (i.e., Crowes™ or Random Lengths™ publications), or be an internal metric generated by the server 230. This metric data is used in the normalization process for all calculations, as described with reference to the above-described methods.
  • While various embodiments of the invention have been illustrated and described, it will be appreciated that within the scope of the appended claims, various changes can be made therein without departing from the spirit of the invention. For example, in an agricultural commodity, an order for Wheat U.S. #2 HRW could be compared to a selected metric of Wheat U.S. #2 Soft White, similar to how different species are analyzed in the above-described example.
  • The above system and method can be used to purchase other commodity items, such as in the trade of livestock. In such a variation, order information such as a lumber tally would be substituted for a meat type, grade, and cut. Other examples of commodity items include agricultural products, metals, or any other items of commerce having several order parameters.

Claims (109)

1. In a networked environment, a system comprising:
a remotely-located server comprising:
a network interface;
a non-transitory computer-readable medium having computer-executable instructions stored thereon, wherein the computer-executable instructions, when executed, implement a plurality of components including:
a metric server adapter;
a metrics application; and
at least one communication application; and
a processor in communication with the network interface and the computer-readable medium, wherein the processor is configured to execute the computer-executable instructions stored in the computer-readable medium;
wherein:
the metric server adapter includes governing logic programmed to manage at least one evaluation service and a plurality of predefined instructions for managing metric data, including industry-specific instructions or a buyer-agent's customized instructions, and to dynamically define transaction-specific instructions for adapting metric data;
the metrics application is a production application programmed to manage one or more purchase and/or analysis processes and to invoke and execute the at least one evaluation service in coordination with the metric server adapter, and to manage one or more user interfaces that, in operation, facilitate interactions with the remotely-located server;
the at least one communication application is programmed to manage one or more protocols that facilitate communications between one or more computing devices and the remotely-located server via the network interface;
in operation, in response to receipt of a triggering request from a buyer-agent computing device, the at least one communication application identifies an applicable protocol for communicating with the buyer-agent computing device and the metrics application receives from the buyer-agent computing device one or more product specification data sets, wherein each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or a plurality of items having a plurality of attributes that differ by at least one parameter value; and
using one or more purchase processes, the metrics application receives or retrieves a plurality of price data sets responsive to at least one item identified in the one or more product specification data sets, each received or retrieved price data set representing an offer to sell that includes price data for at least one item possessing a plurality of attributes having attribute data that includes at least one parameter value;
wherein receipt or retrieval of at least one price data set triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each price data set, to:
obtain metric data from at least one data source accessible to the remotely-located server, wherein the obtained metric data represents market reference data for at least one responsive item having attributes corresponding to attributes of a respective item as identified in the price data set and includes market reference price data of a current time or current period of time, wherein each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value;
evaluate the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the price data set to dynamically discover a difference in the attribute data, wherein a discovered difference is disclosed to the metric server adapter which enables the metric server adapter to contextually define transaction-specific instructions for adapting the metric data for the respective item;
normalize the metric data by executing the transaction-specific instructions for adapting the metric data for the respective item, wherein execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item; and
generate one or more evaluation metrics that pertain to the at least one evaluation service for the respective item as identified in each price data set, wherein each evaluation metric is based, at least in part, on one or a combination of the transaction-specific market reference price data values produced for the respective item as identified in the price data set; and
sort and/or rank the plurality of price data sets using one or more of the evaluation metrics generated for the respective item as identified in each price data set;
wherein the metrics application is further programmed to communicate, in cooperation with the at least one communication application, at least a subset of the sorted and/or ranked price data sets and the one or more evaluation metrics generated for the at least one item in each communicated price data set to at least the buyer-agent computing device.
2. The system of claim 1, wherein the coordinated operation of the metrics application and the metric server adapter provides a common platform that, in operation, enables the metric server adapter to consistently define transaction-specific instructions for adapting metric data without regard to the one or more purchase processes being managed by the metrics application.
3. The system of claim 1, wherein the metrics application is separate from the metric server adapter, and wherein coordinated operation of the metrics application with the metric server adapter enables the metrics application to algorithmically process the attribute data to dynamically identify at least one relationship comprising a difference in the attribute data, wherein the at least one relationship may include a new or previously unknown relationship.
4. The system of claim 1, wherein the coordinated operation of the metrics application and the metric server adapter enables the metric server adapter to autonomously manage the at least one evaluation service and the plurality of predefined instructions for managing metric data to define transaction-specific instructions for adapting metric data, and wherein execution of the transaction-specific instructions by the metrics application provides an evaluation service that is customized for the buyer-agent or the industry without custom-coding the computer-executable instructions that comprise the metrics application.
5. The system of claim 1, wherein execution of a predefined buy link preassociated with at least one item in at least one price data set communicated to the buyer-agent computing device further causes the metrics application, in cooperation with the at least one communication application, to automatically transmit a purchase notice or purchase order to a seller-agent computing device associated with the at least one price data set.
6. The system of claim 1, wherein at least one of the one or more evaluation metrics generated for the at least one item in each price data set is a relative value metric, wherein price data associated with the at least one item in the price data set is divided by one or a combination of the transaction-specific market reference price data values produced for the respective item in the price data set, to generate a ratio or index value.
7. The system of claim 6, wherein a price data set with a lowest relative value metric for the at least one item represents an optimal market value among the plurality of price data sets.
8. The system of claim 6, wherein at least one received or retrieved price data set identifies at least one item that is not a perfect substitute for an item as identified in another received or retrieved price data set in that the at least one item is an alternate item or an item that differs by one or more parameter values from the item as identified in the other received or retrieved price data set, wherein the at least one relative value metric generated for the at least one item as identified in each of the plurality of price data sets provides an objective measure with which to sort and/or rank the plurality of price data sets, including the at least one price data set that identifies an alternate item or an item that differs by one or more parameter values.
9. The system of claim 1, wherein the one or more parameter values represent attributes or conditions that are variable for a specific item or transaction.
10. The system of claim 9, wherein the one or more parameter values include at least one of a grade, a rating measure, a species, an item type, a brand, a quantity, a size, a unit of measure, a tally, a shipping or delivery location, a method of delivery, a delivery date, a time of service, a warranty, a payment term, or a transaction type.
11. The system of claim 10, wherein delivery comprises a financial delivery.
12. The system of claim 10, wherein the delivery date or time of service specifies one or more fulfillment dates in the future, and comprises a forward price transaction type.
13. The system of claim 10, wherein delivery comprises an exchange of at least one item for at least one other item, wherein the at least one other item differs by at least one parameter value from the at least one item.
14. The system of claim 1, wherein a current time or current period of time includes a continuously sliding interval of time that represents a most current period of time.
15. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to generate at least one evaluation metric that encompasses a series of times, periods of time, and/or delivery dates, wherein the series of times, periods of time, and/or delivery dates can include one or more times in the future.
16. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to manage, in cooperation with the at least one communication application, one or more user interfaces that, in operation, expose the at least one product specification data sets to additional buyer-agent computing devices, wherein the one or more user interfaces enable the additional buyer-agents to identify one or more items to be added to the product specification data set, wherein the collaboratively-generated product specification data set identifies a plurality of items, possessing a plurality of attributes having attribute data that differs by at least one parameter value.
17. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to manage, in cooperation with the at least one communication application, one or more user interfaces that, in operation, expose at least one item as identified in the one or more product specification data sets to one or more trading venues, and to receive, from at least one seller-agent computing device, via the network interface, one or more price data sets responsive to the at least one item as identified in the product specification data set.
18. The system of claim 1, wherein the metrics application is further programmed to manage, in cooperation with the at least one communication application, one or more user interfaces that, in operation, communicate a request for quotation (RFQ) for at least one item identified in the one or more product specification data sets to at least one seller-agent computing device on behalf of the buyer-agent, and to receive, from the at least one seller-agent computing device, via the network interface, one or more price data sets responsive to the at least one item as identified in the RFQ.
19. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to manage, in cooperation with the at least one communication application, one or more user interfaces that, in operation, query one or more databases or data sources accessible to the remotely-located server or to monitor one or more data streams for at least one price data set that is responsive to at least one item identified in the one or more product specification data sets.
20. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to manage, in cooperation with the at least one communication application, one or more user interfaces that, in operation, enable the metrics application to filter price data sets exposed to the remotely-located server without prompting by the remotely-located server and to receive at least one exposed price data set that is responsive to at least one item identified in the one or more product specification data sets.
21. The system of claim 1, wherein the metrics application is further programmed to manage, in cooperation with the at least one communication application, one or more user interfaces that, in operation, enable the remotely-located server to receive, from at least one seller-agent, an unsolicited offer to sell at least one item to the buyer-agent.
22. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to retrieve at least one price data set from one or more catalogs, price lists, or one or more programs pre-negotiated with a seller-agent.
23. The system of claim 1, wherein the metrics application is further programmed to manage one or more user interfaces that, in operation, control at least one preprogrammed application, utility, or function that is running on the remotely-located server, the buyer-agent computing device, or another computing device in communication with the remotely-located server, and to execute movement of data in an integrated data exchange between the remotely-located server and the at least one preprogrammed application, utility, or function.
24. The system of claim 1, wherein the metrics application is further programmed to manage one or more user interfaces that, in operation, enable a buyer-agent to predefine an item by a plurality of attributes including one or more parameter values and to preassociate the item with one or more evaluation services.
25. The system of claim 24, wherein execution of at least one predefined instruction that pertains to the buyer-agent and the at least one evaluation service causes the metrics application to use the one or more purchase processes continuously or at a predefined time to receive or retrieve one or more price data sets responsive to at least one item predefined by the buyer-agent and to automatically generate, in coordination with the metric server adapter, one or more evaluation metrics for the at least one predefined item, wherein the metrics application is further caused to manage one or more user interfaces that, in operation, communicate at least a subset of the price data sets and the evaluation metrics generated for the at least one predefined item, continuously or at the predefined time, via the network interface, to the buyer-agent computing-device of the buyer-agent that predefined the at least one item.
26. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of one or more predefined instructions that pertain to the buyer-agent and the at least one evaluation service further causes the metrics application to limit the number of price data sets communicated to the buyer-agent computing device to a predefined number or a predefined portion of the sorted or ranked price data sets.
27. The system of claim 1, wherein at least one item identified in at least one product specification data set or in a received or retrieved price data set is a bundled or combined item that represents a plurality of items in a packaged product or transaction, a tally, or an assembly of component parts, wherein each item or component part possesses a plurality of attributes having attribute data that differs by at least one parameter value.
28. The system of claim 27, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to subdivide the plurality of items or component parts of the bundled or combined item into a plurality of segments, wherein the metrics application selectively uses a different purchase process to receive or retrieve one or more price data sets for at least one segment of the bundled or combined item.
29. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metric server adapter to define at least one transaction-specific instruction that causes the metrics application to produce at least one composite market reference price data value for the respective item, wherein two or more transaction specific market reference price data values produced for the respective item are combined using at least one function or algorithm preassociated with the at least one evaluation service to produce the at least one composite market reference price data value.
30. The system of claim 1, wherein the metric server adapter is programmed to coordinate a conditional execution of transaction-specific instructions for adapting metric data by the metrics application, including:
one or more formulas operationally combining data values and using variables relating to a plurality of items, attributes, parameters, events, or metric data sources; or
a combination of instructions, including validation rules and/or statistical criteria, relating to a plurality of items, attributes, parameters, vendors, events, metric data sources or obtained metric data, the conditional execution of which is priority weighted, sequential, recursive, or subject to another method of control defined by the metric server adapter; or
a combined evaluation service that includes a plurality of transaction-specific instructions for adapting metric data, wherein at least one transaction-specific instruction is further combined with at least one other transaction-specific instruction that specifies employing a process step, action, function, utility, or subroutine, or wherein at least one evaluation service is combined with at least one other evaluation service, wherein the conditional execution of the transaction-specific instructions of the combined evaluation service is priority weighted, sequential, recursive, or subject to another method of control defined by the metric server adapter.
31. The system of claim 1, wherein the transformation of the market reference price data occurs independent of unit-of-measure conversion of data in the metric data for responsive items that are defined by a unit-of-measure.
32. The system of claim 1, wherein the buyer-agent computing device from which the one or more product specification data sets are received is a mobile computing device, and wherein at least one predefined instruction that pertains to the buyer-agent and the at least one evaluation service causes the metric server adapter to define at least one transaction-specific instruction that causes the metrics application to limit the number of price data sets communicated to the mobile computing device for visual display in a constrained display space to a predefined number or a predefined portion of the sorted and/or ranked price data sets.
33. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to compare a plurality of seller-agents using at least one evaluation metric generated for the respective item as identified in one or more of the price data sets associated with each seller-agent.
34. The system of claim 1, wherein the metrics application is further programmed to manage at least one user interface that, in operation, configures the remotely-located server to facilitate data communication in XML format, enabling the metrics application to dynamically change, dynamically route, and/or pre-configure data for movement of the data in an integrated data exchange.
35. The system of claim 1, wherein the price data for at least one item identified in a received or retrieved price data set is specified as a formula, wherein the price of the at least one item is to be determined at one or more specified times in the future using, at least in part, one or more evaluation metrics generated by the remotely-located server or one or more market-reference prices reported by a specified data source, wherein, at the one or more specified times, the metrics application automatically obtains the one or more reported market-reference prices or generates the one or more evaluation metrics for the at least one item, wherein the metrics application automatically derives the price data for the at the least one item in accordance with the specified formula, and wherein the metrics application is further programmed to communicate the price data derived for the at least one item as identified in the received or retrieved data set, via the network interface, to at least the buyer-agent computing device from which the one or more product specification data sets were received.
36. The system of claim 1, wherein the metrics application is further programmed to manage one or more user interfaces that, in operation, enable the remotely-located server to prompt the buyer-agent computing device to identify or select at least one data element or function to be added to or removed from a currently in-progress evaluation service, to identify or select at least one different parameter value for the at least one item identified in the product specification data set, or to provide additional information required by a currently in-progress evaluation service.
37. The system of claim 36, wherein identification or selection of at least one different parameter value for the at least one item identified in the product specification data set causes the metrics application to automatically generate one or more evaluation metrics for the respective item using the at least one different parameter value.
38. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metric server adapter to define at least one transaction-specific instruction that, when executed, causes the metrics application to obtain metric data for an alternate item, wherein the alternate item is a substitute item and/or differs by at least one parameter value from the at least one item as identified in a received or retrieved price data set, and further causes the metrics application, in coordination with the metric server adapter, to produce the one or more transaction-specific market reference price data values for the at least one item identified in the price data set using, at least in part, metric data obtained for the alternate item.
39. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to automatically query one or more databases or data sources accessible to the remotely-located server or to monitor one or more data streams to obtain market reference data for one or more responsive items having attributes corresponding to the attributes of at least one item identified in a received or retrieved price data set.
40. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metric server adapter to define at least one transaction-specific instruction that causes the metrics application to limit the metric data to market-reference data associated with at least one predefined seller-agent or metric data source, or to filter, for inclusion or exclusion, the one or more responsive items in the metric data using one or more predefined control values, criteria, or parameters, and to use only a limited or filtered segment of the metric data to produce the one or more transaction-specific market reference price data values for the at least one item identified in the price data set.
41. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to obtain only metric data resulting from a computer-based interaction and/or to use only electronically-created metric data to produce the one or more transaction-specific market reference price data values for the at least one item identified in the price data set, wherein the electronically-created metric data does not include human-reported transaction data or transaction data that was manually transcribed into a digital format, wherein the electronically-created metric data includes data comprising a timestamp that identifies a particular time or period of time.
42. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to evaluate each responsive item in the metric data for satisfaction of one or more predefined validation rules and/or statistical criteria and to only produce the one or more transaction-specific market reference price data values for the at least one item identified in the product specification data set using metric data that satisfies the predefined validation rules and/or statistical criteria.
43. The system of claim 1, wherein the at least one communication application automatically identifies the buyer-agent computing device initiating the at least evaluation service, wherein upon identification of the buyer-agent computing device initiating the at least one evaluation service, the metrics application is caused to manage one or more user interfaces customized for the buyer-agent, wherein the one or more customized user interfaces include one or more preconfigured dropdown menus preloaded with one or more items and/or one or more parameter values predefined by the buyer-agent.
44. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instructions that pertain to the at least one evaluation service causes the metrics application to manage one or more user interfaces that incorporate predefined industry-specific terminology, industry-specific standards, and/or industry-specific practices.
45. The system of claim 1, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to, continuously or over a predetermined period of time, obtain more current metric data for at least one item as identified in a received or retrieved price data set, wherein the more current metric data represents market reference data for one or more items having attributes that are responsive to attributes of the at least one item as identified in the price data set and includes more-current market reference price data for the at least one item or excludes previously-obtained metric data that is no longer responsive to the at least one item or no longer represents market reference price data associated with the at least one item at the current time or period of time, and further causes the metrics application, in coordination with the metric server adapter, to produce one or more more-current transaction-specific market reference price data values for the at least one item and to generate one or more more-current evaluation metrics for the at least one item as identified in the price data set, and wherein the metrics application is further programmed to communicate at least one of the one or more more-current evaluation metrics generated for the at least one item identified in at least one price data set, via the network interface, to at least to the buyer-agent computing device from which the one or more product specification data sets were previously received.
46. In a networked environment, a system comprising:
a remotely-located server comprising:
a network interface;
a non-transitory computer-readable medium having computer-executable instructions stored thereon, wherein the computer-executable instructions, when executed, implement a plurality of components including:
a metric server adapter;
a metrics application; and
at least one communication application; and
a processor in communication with the network interface and the computer-readable medium, wherein the processor is configured to execute the computer-executable instructions stored in the computer-readable medium;
wherein:
the metric server adapter includes governing logic programmed to manage at least one evaluation service and a plurality of predefined instructions for managing metric data, and to dynamically define transaction-specific instructions for adapting metric data;
the metrics application is a production application programmed to manage one or more purchase and/or analysis processes and to invoke and execute the at least one evaluation service in coordination with the metric server adapter, and to manage one or more user interfaces that, in operation, facilitate interactions with the remotely located server;
the at least one communication application is programmed to manage one or more protocols that facilitate communications between one or more computing devices and the remotely-located server via the network interface; and
in operation, in response to receipt of a triggering request from a user-agent computing device, the at least one communication application identifies an applicable protocol for communicating with the user-agent computing device and the metrics application receives from the user-agent computing device at least one product specification data set, wherein each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or a plurality of items having a plurality of attributes that differ by at least one parameter value; and
using one or more purchase processes, the metrics application receives or retrieves at least one price data set that is responsive to at least one item identified in the at least one product specification data set, wherein the at least one price data set represents an offer to sell that includes price data for at least one item possessing a plurality of attributes having attribute data that includes at least one parameter value;
wherein receipt of at least one product specification data set and receipt or retrieval at least one responsive price data set triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each received product specification data set and for each received or retrieved price data set, to:
obtain metric data from at least one data source accessible to the remotely-located server, wherein the obtained metric data represents market reference data for at least one responsive item having attributes that correspond to attributes of a respective item as identified in the product specification data set or the price data set and includes market reference price data of a current time or current period of time, wherein each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value;
evaluate the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the product specification data set or the price data set to dynamically discover a difference in the attribute data, wherein a discovered difference is disclosed to the metric server adapter which enables the metric server adapter to contextually define transaction-specific instructions for adapting the metric data for the respective item;
normalize the metric data by executing the transaction-specific instructions for adapting the metric data for the respective item, wherein execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item; and
generate one or more evaluation metrics that pertain to the at least one evaluation service for the respective item as identified in the product specification data set or the price data set, wherein each evaluation metric is based, at least in part, on one or a combination of the transaction-specific market reference data values produced for the respective item;
wherein the metrics application is further programmed to communicate, in cooperation with the at least one communication application, the one or more evaluation metrics generated for the at least one item as identified in the at least one product specification data set and the at least one price data set to at least the user-agent computing device.
47. The system of claim 46, wherein the metrics application is separate from the metric server adapter, and wherein coordinated operation of the metrics application with the metric server adapter enables the metrics application to algorithmically process the attribute data to dynamically identify at least one relationship comprising a difference within the attribute data, wherein the at least one relationship may include a new or previously unknown relationship.
48. The system of claim 46, wherein the plurality of predefined instructions for managing metric data includes one or more industry-specific instructions or one or more instructions predefined by a user-agent, and wherein the plurality of predefined instructions for managing metric data are stored in a memory accessible to the remotely-located server.
49. The system of claim 46, wherein the one or more parameter values represent attributes or conditions that are variable for a specific item or transaction.
50. The system of claim 49, wherein the one or more parameter values include at least one of a grade, a rating measure, a species, an item type, a brand, a quantity, a size, a unit of measure, a tally, a location, a method of delivery, a delivery date, a time of service, a warranty, a payment term, or a transaction type.
51. The system of claim 50, wherein delivery comprises a financial delivery.
52. The system of claim 50, wherein the delivery date or time of service specifies one or more fulfillment dates in the future, and comprises a forward price transaction type.
53. The system of claim 50, wherein delivery comprises an exchange of at least one item for at least one other item, wherein the at least one other item differs by at least one parameter value from the at least one item.
54. The system of claim 46, wherein invocation of the at least one evaluation service and/or execution of at least one transaction specific instruction that pertains to the at least one evaluation service causes the metrics application to compare at least one evaluation metric generated for the respective item as identified in at least one product specification data set with price data associated with the respective item as identified in at least one received or retrieved price data set.
55. The system of claim 54, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service further causes the metrics application to use the comparison to identify one or more seller-agents associated with price data sets that include at least one item with price data that is below one or more of the evaluation metrics generated for the at least one item identified in the product specification data set or the corresponding price data set.
56. The system of claim 46, wherein invocation of the at least one evaluation service and/or execution of at least one transaction specific instruction that pertains to the at least one evaluation service causes the metrics application to compare price data associated with the respective item in a price data set with one or more of the evaluation metrics generated for the respective item as identified in the price data set.
57. The system of claim 46, wherein invocation of the at least one evaluation service and/or execution of at least one transaction specific instruction that pertains to the at least one evaluation service causes the metrics application to compare one or more of the evaluation metrics generated for the respective item as identified in the product specification data set to one or more of the evaluation metrics generated for the respective item as identified in at least one received or retrieved price data set.
58. The system of claim 46, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to produce a composite market reference price data value for the respective item, wherein two or more transaction specific market reference price data values produced for the respective item as identified in the product specification data set or the price data set are combined using a function or algorithm preassociated with the at least one evaluation service.
59. The system of claim 46, wherein invocation of the at least one evaluation service and/or execution of at least one transaction specific instruction that pertains to the at least one evaluation service causes the metrics application to generate at least one relative value metric, wherein price data associated with the respective item in a product specification data set or a price data set is divided by one or a combination of the transaction-specific market reference price data values produced for the respective item, to generate a ratio or index value.
60. The system of claim 46, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to compare two or more purchase processes using one or more of the evaluation metrics generated for the respective item as identified in one or more of the price data sets received or retrieved via each purchase process.
61. The system of claim 46, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metric server adapter to define at least one transaction-specific instruction that, when executed by the metrics application, causes data expressed in units of measure to be consistently converted into standardized or common units of measure, or units of measure as specified for the at least one item identified in the product specification data set, and further causes the metrics application to only produce the one or more transaction-specific market reference price data values for the at least one item as identified in the product specification data set or the price data set using data possessing consistent units of measure.
62. The system of claim 46, wherein execution of a predefined buy link preassociated with at least one price data set communicated to the user-agent computing device causes the metrics application, in cooperation with the at least one communication application, to automatically transmit a purchase notice or purchase order to a seller-agent computing device associated with the at least one price data set.
63. The system of claim 46, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to automatically update one or more of the evaluation metrics generated for the at least one item in the price data set and/or the product specification data set, continuously, at a predefined time or interval of time, upon the occurrence of a predefined event, or upon user-agent instruction.
64. In a networked environment, a system comprising:
a remotely-located server comprising:
a network interface;
a non-transitory computer-readable medium having computer-executable instructions stored thereon, wherein the computer-executable instructions, when executed, implement a plurality of components including:
a metric server adapter;
a metrics application; and
at least one communication application; and
a processor in communication with the network interface and the computer-readable medium, wherein the processor is configured to execute the computer-executable instructions stored in the computer-readable medium;
wherein:
the metric server adapter includes governing logic programmed to manage at least one evaluation service and a plurality of predefined instructions for managing metric data, and to dynamically define transaction-specific instructions for adapting metric data;
the metrics application is a production application programmed to manage one or more purchase and/or analysis processes and to invoke and execute the at least one evaluation service in coordination with the metric server adapter, and to manage one or more user interfaces that, in operation, facilitate interactions with the remotely located server;
the at least one communication application is programmed to manage one or more protocols that facilitate communications between one or more computing devices and the remotely-located server via the network interface; and
in operation, in response to receipt of a triggering request from a buyer-agent computing device, the at least one communication application identifies an applicable protocol for communicating with the buyer-agent computing device and the metrics application receives from the buyer-agent computing device one or more product specification data sets, wherein each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or a plurality of items having a plurality of attributes that differ by at least one parameter value; and
using a first purchase process, the metrics application receives or retrieves at least one price data set responsive to at least one item identified in the one or more product specification data sets, wherein each price data set comprises an offer to sell that includes price data for at least one item possessing a plurality of attributes having attribute data that includes at least one parameter value;
wherein receipt or retrieval of at least one price data set triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each price data set, to:
obtain metric data from at least one data source accessible to the remotely-located server, wherein the obtained metric data represents market reference data for at least one responsive item having attributes corresponding to attributes of a respective item as identified in the price data set and includes market reference price data of a current time or current period of time, wherein each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value;
evaluate the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the price data set to dynamically discover a difference in the attribute data, wherein a discovered difference is disclosed to the metric server adapter which enables the metric server adapter to contextually define transaction-specific instructions for adapting the metric data for the respective item;
normalize the metric data by executing the transaction-specific instructions for adapting the metric data for the respective item, wherein execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item; and
generate one or more evaluation metrics that pertain to the at least one evaluation service for the respective item as identified in each price data set received or retrieved via the first purchase process, wherein each evaluation metric is based, at least in part, on one or a combination of the transaction-specific market reference data values produced for the respective item as identified in the price data set, wherein at least one evaluation metric comprises a ratio or index value in which price data for the respective item is divided by one or a combination of the transaction-specific market reference price data values produced for the respective item, to generate a relative value metric;
wherein if no price data set has a relative value metric of less than one, the metrics application is programmed to retrieve or receive at least one price data set having a respective item responsive to the same at least one item using a second, different purchase process, and to produce, in coordination with the metric server adapter, one or more transaction-specific market reference price data values and generate one or more evaluation metrics, including a relative value metric, for the respective item as identified in each price data set received or retrieved via the second purchase process; and
compare the price data sets received or retrieved via the first and second purchase processes using at least the relative value metric generated for the respective item as identified in each price data set;
wherein the metrics application is further programmed to communicate, in cooperation with the at least one communication application, a result of the comparison to at least the buyer-agent computing device.
65. The system of claim 64, wherein the coordinated operation of the metrics application and the metric server adapter provides a common platform that, in operation, enables the metric server adapter to consistently define transaction-specific instructions for adapting metric data without regard to the purchase process used by the metrics application.
66. The system of claim 64, wherein the metrics application is separate from the metric server adapter, and wherein coordinated operation of the metrics application with the metric server adapter enables the metrics application to algorithmically process the attribute data to dynamically identify at least one relationship comprising a difference within the attribute data, wherein the at least one relationship may include a new or previously unknown relationship.
67. The system of claim 64, wherein the plurality of predefined instructions for managing metric data include one or more industry-specific instructions or one or more instructions predefined by a buyer-agent, and wherein the plurality of predefined instructions for managing metric data are stored in a memory accessible to the remotely-located server.
68. The system of claim 67, wherein the coordinated operation of the metrics application and the metric server adapter enables the metric server adapter to autonomously manage the at least one evaluation service and the plurality of predefined instructions for managing metric data, to define transaction-specific instructions for adapting metric data, and wherein execution of the transaction-specific instructions by the metrics application provides an evaluation service that is customized for the buyer-agent or the industry without custom-coding the computer-executable instructions that comprise the metrics application.
69. The system of claim 64, wherein the one or more parameter values represent attributes or conditions that are variable for a specific item or transaction.
70. The system of claim 64, wherein the comparison provides an objective measure that enables a buyer-agent to identify an optimal purchase process with which to procure the at least one item identified in the one or more product specification data sets.
71. The system of claim 64, wherein a price data set with a lowest relative value metric represents an optimal market value for the at least one item among the plurality of price data sets.
72. The system of claim 64, wherein at least one received or retrieved price data set identifies at least one item that is not a perfect substitute for an item as identified in another received or retrieved price data set in that the at least one item is an alternate item or an item that differs by one or more parameter values from the item as identified in the other received or retrieved price data set, and wherein the at least one relative value metric generated for the at least one item as identified in each of the plurality of price data sets provides an objective measure with which to compare the item or items across the plurality of received or retrieved price data sets, including the at least one price data set that identifies an alternate item or an item that differs by one or more parameter values.
73. The system of claim 64, wherein the metrics application is further programmed to manage, in cooperation with the at least one communication application, one or more user interfaces that, in operation, communicate the result of the comparison for visual display on at least the buyer-agent computing device, wherein the one or more user interfaces facilitate interactions that enable the buyer-agent to expose underlying data in one or more layers of detail, to display additional data in one or more simultaneously displayed pop-up windows, to display linked information, or to display the same data in a different form or representing one or more different purchase processes or from one or more different sources of metric data or as determined at a different period of time.
74. The system of claim 64, wherein execution of a predefined buy link preassociated with at least one price data set in the comparison communicated to the buyer-agent computing device causes the metrics application, in cooperation with the at least one communication application, to automatically transmit a purchase notice or purchase order to a seller-agent computing device associated with the at least one price data set.
75. The system of claim 64, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to manage, in cooperation with the at least one communication application, one or more user interfaces that, in operation, expose at least one item identified in the one or more product specification data sets to one or more trading venues, and to receive, from at least one seller-agent computing device, via the network interface, one or more price data sets responsive to at least one item identified in the one or more product specification data sets.
76. The system of claim 64, wherein the metrics application is further programmed to manage, in cooperation with the at least one communication application, one or more user interfaces that, in operation, communicate a request for quotation (RFQ) for at least one item identified in the one or more product specification data sets to at least one seller-agent computing device on behalf of the buyer-agent, and to receive, from the at least one seller-agent computing device, via the network interface, one or more price data sets responsive to at least one item as identified in the RFQ.
77. The system of claim 64, wherein at least one purchase process causes the metrics application to query one or more databases or data sources accessible to the service provider server or to monitor one or more data streams for at least one exposed price data set that is responsive to at least one item identified in the one or more product specification data sets.
78. The system of claim 64, wherein the metrics application is further programmed to manage, in cooperation with the at least one communication application, one or more user interfaces that, in operation, enable the remotely-located server to receive, from at least one seller-agent, an unsolicited offer to sell at least one item to the buyer-agent.
79. The system of claim 64, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to retrieve at least one price data set from one or more catalogs, price lists, or one or more programs pre-negotiated with a seller-agent.
80. The system of claim 64, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to compare a catalog purchase process to a market purchase process, wherein at least one relative value metric generated for the respective item as identified in each price data set retrieved via the catalog process is compared to at least one relative value metric generated for the respective item as identified in each price data set received via the market purchase process.
81. The system of claim 64, wherein at least one price data set identifies a bundle of items defined by a plurality of attributes having attribute data that differs by at least one parameter value or wherein at least one item identified in at least one received or retrieved price data set is a combined item that represents a packaged product or transaction, a tally, or an assembly of one or more component parts, wherein each component part is defined by a plurality of attributes having attribute data that differs by at least one parameter value, wherein at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to subdivide the plurality of items or component parts of the bundle or combined item into a plurality of segments, wherein the metrics application selectively uses a different purchase process to receive or retrieve one or more price data sets for at least one segment of the bundle or combined item.
82. The system of claim 64, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metric server adapter to define at least one transaction-specific instruction that causes the metrics application to limit the metric data to market-reference data associated with at least one predefined seller-agent or metric data source or to filter, for inclusion or exclusion, the one or more responsive items in the metric data using one or more predefined control values, criteria, or parameters, and to use only a limited or filtered segment of the metric data to produce the one or more transaction-specific market reference price data values for the at least one item identified in the price data set.
83. In a networked environment, a system comprising:
a remotely-located server comprising:
a network interface;
a non-transitory computer-readable medium having computer-executable instructions stored thereon, wherein the computer-executable instructions, when executed, implement a plurality of components including:
a metric server adapter;
a metrics application; and
at least one communication application; and
a processor in communication with the network interface and the computer-readable medium, wherein the processor is configured to execute the computer-executable instructions stored in the computer-readable medium;
wherein:
the metric server adapter includes governing logic programmed to manage at least one evaluation service and a plurality of predefined instructions for managing metric data, including industry-specific instructions or a buyer-agent's customized instructions, and to dynamically define transaction-specific instructions for adapting metric data;
the metrics application is a production application programmed to manage one or more purchase and/or analysis processes and to invoke and execute the at least one evaluation service in coordination with the metric server adapter, and to manage one or more user interfaces that, in operation, facilitate interactions with the remotely located server;
the at least one communication application is programmed to manage one or more protocols that facilitate communications between one or more computing devices and the remotely-located server via the network interface; and
in operation, in response to receipt of a triggering request from a buyer-agent computing device, the at least one communication application identifies an applicable protocol for communicating with the buyer-agent computing device and the metrics application receives from the buyer-agent computing device at least one evaluation scenario for analysis, the at least one evaluation scenario identifying two or more different purchase processes, at least one product specification data set, and at least one particular time or period of time, wherein each product specification data set identifies at least one item that is defined by a plurality of attributes having attribute data that includes two or more parameter values, or a plurality of items having a plurality of attributes that differ by at least one parameter value;
wherein receipt of at least one evaluation scenario triggers the metrics application to invoke the at least one evaluation service which causes the metrics application, for each purchase process identified in the at least one evaluation scenario, to:
retrieve the buyer-agent's historical purchase data associated with the purchase process for the at least one particular time or period of time, wherein the retrieved purchase data includes one or more price data sets responsive to at least one item identified in the at least one product specification data set, each price data set including price data for at least one item, and each item possessing a plurality of attributes having attribute data that includes at least one parameter value;
for each price data set, obtain metric data from at least one data source accessible to the remotely-located server, wherein the obtained metric data represents market reference data for at least one responsive item having attributes corresponding to attributes of a respective item as identified in the price data set and includes market reference price data for the at least one particular time or period of time, wherein each responsive item in the metric data possesses a plurality of attributes having attribute data that includes at least one parameter value;
evaluate the plurality of attributes of each responsive item in the metric data relative to the plurality of attributes for the respective item as identified in the price data set to dynamically discover a difference in the attribute data, wherein a discovered difference is disclosed to the metric server adapter which enables the metric server adapter to contextually define transaction-specific instructions for adapting the metric data for the respective item;
normalize the metric data by executing the transaction-specific instructions for adapting metric data for the respective item, wherein execution of at least one transaction-specific instruction causes one or more adjustment values to be generated and applied to the market reference price data for at least one responsive item that differs by at least one parameter value from the respective item, transforming the market reference price data for the at least one responsive item and automatically producing one or more transaction-specific market reference price data values for the respective item;
generate one or more evaluation metrics that pertain to the at least one evaluation service for at least one item identified in the at least one product specification data set for the at least one particular time or period of time, wherein each evaluation metric is based, at least in part, on one or a combination of the transaction-specific market reference price data values produced for the respective item as identified in the price data sets associated with each purchase process; and
compare the two or more purchase processes identified in the at least one evaluation scenario using one or more of the evaluation metrics generated for the respective item as identified in the price data sets associated with each purchase process;
wherein the metrics application is further programmed to communicate, in coordination with the at least one communication application, a result of the comparison to at least the buyer-agent controlled computing device.
84. The system of claim 83, wherein the coordinated operation of the metrics application and the metric server adapter provides a common platform that, in operation, enables the metric server adapter to consistently define transaction-specific instructions for adapting metric data without regard to the one or more purchase processes being analyzed by the metrics application.
85. The system of claim 83, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to generate a relative value metric for each of the two or more purchase processes identified in the evaluation scenario, wherein price data associated with the respective item as identified in each of the price data set associated with a particular purchase process is combined to determine an average price paid by the buyer-agent for the at least one item over the identified at least one period of time using the particular purchase process and further to combine the corresponding transaction-specific market reference price data values produced for the respective item as identified in each retrieved price data set to determine an average market-reference price data value for the at least one item over the same period of time, wherein the average price paid by the buyer-agent is divided by the average market-reference price data value produced for the at least one item in the price data sets to generate the relative value metric, comprising a ratio or index value, for each of the two or more identified purchase processes.
86. The system of claim 83, wherein a purchase process with a lowest relative value metric represents an optimal purchase process with which to procure the at least one item identified in the at least one product specification data set over the at least one period of time identified in the evaluation scenario.
87. The system of claim 86, wherein the metrics application is programmed to manage, in cooperation with the at least one communications application, at least one interface that enables the buyer-agent to predefine at least one instruction that preassociates the optimal purchase process with the at least one item, wherein upon receiving a product specification data set from a computing device under the control of the buyer-agent that identifies the at least one item, the metrics application is caused to automatically use the preassociated purchase process to receive or retrieve at least one price data set responsive to the at least one item as identified in the product specification data set.
88. The system of claim 83, wherein the metrics application is separate from the metric server adapter, and wherein coordinated operation of the metrics application with the metric server adapter enables the metrics application to algorithmically process the attribute data to dynamically identify at least one relationship comprising a difference within the attribute data, wherein the at least one relationship may include a new or previously unknown relationship.
89. The system of claim 83, wherein the coordinated operation of the metrics application and the metric server adapter enables the metric server adapter to autonomously manage the at least one evaluation service and the plurality of predefined instructions for managing metric data to define transaction-specific instructions for adapting metric data, and wherein execution of the transaction-specific instructions by the metrics application provides an evaluation service that is customized for the buyer-agent or the industry without custom-coding the computer-executable instructions that comprise the metrics application.
90. The system of claim 83, wherein the metrics application is further programmed to manage, in coordination with the at least one communication application, one or more user interfaces that, in operation, communicate, via the network interface, a result of the comparison for display on at least the buyer-agent computing device which identified the at least one evaluation scenario, wherein the one or more user interfaces facilitate interactions that enable the buyer-agent to expose underlying data in one or more layers of detail, to display additional data in one or more simultaneously displayed pop-up windows, to display linked information, or to display the same data in a different form or representing one or more different purchase processes or from one or more different sources of metric data or as determined at a different period of time.
91. The system of claim 83, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to obtain metric data for an alternate item, wherein the alternate item is a substitute item and/or differs by at least one parameter value from the at least one item as identified in the at least one product specification data set, and further causes the metrics application, in coordination with the metric server adapter, to produce the one or more transaction-specific market reference price data values using, at least in part, metric data obtained for the alternate item.
92. The system of claim 83, wherein a plurality of evaluation scenarios are received from the buyer-agent computing device for analysis, wherein at least one evaluation scenario specifies the use of an alternate item, alternate parameter, alternate time or period of time, alternate metric data source, or combination thereof.
93. The system of claim 83, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to generate at least one evaluation metric that comprises a range of values for each purchase process, wherein each value in the range of values is based, at least in part, on one or a combination of transaction-specific market reference price data values produced for the respective item as identified in the at least one price data set retrieved from the historical purchase data for each of the two or more different purchase processes identified in the at least one evaluation scenario.
94. The system of claim 83, wherein the one or more parameter values represent attributes or conditions that are variable for a specific item or transaction.
95. The system of claim 83, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instructions that pertains to the at least one evaluation service causes the metric server adapter to define at least one transaction-specific instruction that causes the metrics application to filter the buyer-agent's historic purchase data using one or more predefined control values, criteria, or parameters, and to only retrieve price data sets that satisfy the specified control values, criteria, or parameters.
96. The system of claim 83, wherein at least one evaluation scenario identified by the buyer-agent causes the metrics application to filter the buyer-agent's historic purchase data and to only retrieve price data sets associated with a particular seller-agent, type of seller-agent, a particular transaction type, or purchase data resulting from an executed purchase or contract.
97. The system of claim 83, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to automatically query one or more databases or data sources accessible to the remotely-located server or to monitor one or more data streams to obtain metric data for one or more items responsive to the attributes of at least one item identified in at least one retrieved price data set.
98. The system of claim 83, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to evaluate each responsive item in the metric data for satisfaction of one or more predefined validation rules and/or statistical criteria and to only produce the one or more transaction-specific market reference price data values for the respective item using metric data that satisfies the predefined validation rules and/or statistical criteria.
99. The system of claim 83, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metric server adapter to define at least one transaction-specific instruction that causes the metrics application to limit the metric data to market-reference data associated with at least one predefined seller-agent or metric data source, or to filter, for inclusion or exclusion, the one or more responsive items in the metric data using one or more predefined control values, criteria, or parameters, and to use only a limited or filtered segment of the metric data to produce the one or more transaction-specific market reference price data values for the respective item.
100. The system of claim 83, wherein invocation of the at least one evaluation service and/or execution of at least one predefined instruction that pertains to the at least one evaluation service causes the metrics application to limit the obtained metric data to market-reference price data representing the same time or period of time as that of the price data set.
101. The system of claim 83, wherein the transformation of the market reference price data occurs independent of unit-of-measure conversion of data in the metric data for responsive items that are defined by a unit-of-measure.
102. The system of claim 3, wherein the metric server adapter uses the at least one relationship comprising a difference to ascertain which of the predefined instructions for adapting metric data are applicable to the responsive item, wherein the metric server adapter uses the attributes and one or more parameter values of the respective item, in combination with the predefined instructions for adapting metric data ascertained to be applicable to the responsive item, to contextually define transaction-specific instructions for adapting the metric data for the respective item.
103. The system of claim 1, wherein the governing logic comprises a module or application or a separate application layer, wherein the governing logic cohesively manages a plurality of predefined instructions that pertain to the at least one evaluation service, wherein the predefined instructions identify rules or variables or criteria that were predefined for and preassociated with the at least one evaluation service, and wherein the predefined instructions serve to identify or modify features or elements that pertain to the at least one evaluation service or to limit at least one functionality of the at least one evaluation service or a feature or element identified therein.
104. The system of claim 47, wherein the metric server adapter uses the at least one relationship comprising a difference to ascertain which of the predefined instructions for adapting metric data are applicable to the responsive item, wherein the metric server adapter uses the attributes and one or more parameter values of the respective item, in combination with the predefined instructions for adapting metric data ascertained to be applicable to the responsive item, to contextually define transaction-specific instructions for adapting the metric data for the respective item.
105. The system of claim 46, wherein the governing logic comprises a module or application or a separate application layer, wherein the governing logic cohesively manages a plurality of predefined instructions that pertain to the at least one evaluation service, wherein the predefined instructions identify rules or variables or criteria that were predefined and preassociated with the at least one evaluation service, and wherein the predefined instructions serve to identify or modify features or elements that pertain to the at least one evaluation service or to limit at least one functionality of the at least one evaluation service or a feature or element identified therein.
106. The system of claim 66, wherein the metric server adapter uses the at least one relationship comprising a difference to ascertain which of the predefined instructions for adapting metric data are applicable to the responsive item, wherein the metric server adapter uses the attributes and one or more parameter values of the respective item, in combination with the predefined instructions for adapting metric data ascertained to be applicable to the responsive item, to contextually define transaction-specific instructions for adapting the metric data for the respective item.
107. The system of claim 64, wherein the governing logic comprises a module or application or a separate application layer, wherein the governing logic cohesively manages a plurality of predefined instructions that pertain to the at least one evaluation service, wherein the predefined instructions identify rules or variables or criteria that were predefined and preassociated with the at least one evaluation service, and wherein the predefined instructions serve to identify or modify features or elements that pertain to the at least one evaluation service or to limit at least one functionality of the at least one evaluation service or a feature or element identified therein.
108. The system of claim 88, wherein the metric server adapter uses the at least one relationship comprising a difference to ascertain which of the predefined instructions for adapting metric data are applicable to the responsive item, wherein the metric server adapter uses the attributes and one or more parameter values of the respective item, in combination with the predefined instructions for adapting metric data ascertained to be applicable to the responsive item, to contextually define transaction-specific instructions for adapting the metric data for the respective item.
109. The system of claim 83, wherein the governing logic comprises a module or application or a separate application layer, wherein the governing logic cohesively manages a plurality of predefined instructions that pertain to the at least one evaluation service, wherein the predefined instructions identify rules or variables or criteria that were predefined and preassociated with the at least one evaluation service, and wherein the predefined instructions serve to identify or modify features or elements that pertain to the at least one evaluation service or to limit at least one functionality of the at least one evaluation service or a feature or element identified therein.
US15/237,518 2000-06-28 2016-08-15 Automated system for adapting market data and evaluating the market value of items Expired - Fee Related US9524495B1 (en)

Priority Applications (8)

Application Number Priority Date Filing Date Title
US15/237,518 US9524495B1 (en) 2000-06-28 2016-08-15 Automated system for adapting market data and evaluating the market value of items
US15/257,765 US9576296B2 (en) 2000-06-28 2016-09-06 Automated system for adapting market data and evaluating performance in transactions
US15/368,266 US9754244B2 (en) 2000-06-28 2016-12-02 System and method for adapting market data and evaluating the market value of transactions
US15/445,641 US9710856B2 (en) 2000-06-28 2017-02-28 System and method for adapting market data and evaluating unequal offers
US15/604,533 US9904913B2 (en) 2000-06-28 2017-05-24 Automated system for adapting metric data for use in a transaction-specific analysis or evaluation
US15/641,083 US10055719B2 (en) 2000-06-28 2017-07-03 Automated system and method for adapting market data and evaluating user-specified configurations
US16/105,653 US10262307B2 (en) 2000-06-28 2018-08-20 Automated system for adapting market data for transaction cost analysis
US16/116,175 US10290008B2 (en) 2000-06-28 2018-08-29 Automated system for adapting market data and producing metric values

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
US09/607,502 US7043457B1 (en) 2000-06-28 2000-06-28 System and method for managing and evaluating network commodities purchasing
US11/394,540 US7840462B2 (en) 2000-06-28 2006-03-31 System and method for managing and evaluating network commodities purchasing
US12/952,083 US7966240B2 (en) 2000-06-28 2010-11-22 System and method for managing and evaluating network commodities purchasing
US13/118,351 US8224729B2 (en) 2000-06-28 2011-05-27 System and method for managing and evaluating network commodities purchasing
US13/475,900 US8321317B2 (en) 2000-06-28 2012-05-18 System and method for managing and evaluating network commodities purchasing
US13/597,200 US8442888B2 (en) 2000-06-28 2012-08-28 Managing and evaluating price data for purchasing
US13/869,942 US8762258B2 (en) 2000-06-28 2013-04-24 System and method for managing and evaluating network commodities purchasing
US14/262,682 US9092825B2 (en) 2000-06-28 2014-04-25 Automated system for adapting market data and evaluating the market value of items
US14/740,630 US9418371B2 (en) 2000-06-28 2015-06-16 Automated system for adapting market data and evaluating the market value of items
US15/237,518 US9524495B1 (en) 2000-06-28 2016-08-15 Automated system for adapting market data and evaluating the market value of items

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US14/740,630 Continuation US9418371B2 (en) 2000-06-28 2015-06-16 Automated system for adapting market data and evaluating the market value of items

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/257,765 Continuation US9576296B2 (en) 2000-06-28 2016-09-06 Automated system for adapting market data and evaluating performance in transactions

Publications (2)

Publication Number Publication Date
US20160350732A1 true US20160350732A1 (en) 2016-12-01
US9524495B1 US9524495B1 (en) 2016-12-20

Family

ID=24432548

Family Applications (21)

Application Number Title Priority Date Filing Date
US09/607,502 Expired - Lifetime US7043457B1 (en) 2000-06-28 2000-06-28 System and method for managing and evaluating network commodities purchasing
US11/394,540 Expired - Lifetime US7840462B2 (en) 2000-06-28 2006-03-31 System and method for managing and evaluating network commodities purchasing
US12/952,083 Expired - Fee Related US7966240B2 (en) 2000-06-28 2010-11-22 System and method for managing and evaluating network commodities purchasing
US13/118,351 Expired - Fee Related US8224729B2 (en) 2000-06-28 2011-05-27 System and method for managing and evaluating network commodities purchasing
US13/475,900 Expired - Fee Related US8321317B2 (en) 2000-06-28 2012-05-18 System and method for managing and evaluating network commodities purchasing
US13/597,200 Expired - Fee Related US8442888B2 (en) 2000-06-28 2012-08-28 Managing and evaluating price data for purchasing
US13/744,373 Expired - Fee Related US8635139B2 (en) 2000-06-28 2013-01-17 System and method for managing and evaluating network commodities purchasing
US13/846,945 Expired - Fee Related US8700521B2 (en) 2000-06-28 2013-03-18 System and method for managing and evaluating network commodities purchasing
US13/869,942 Expired - Fee Related US8762258B2 (en) 2000-06-28 2013-04-24 System and method for managing and evaluating network commodities purchasing
US14/262,682 Expired - Fee Related US9092825B2 (en) 2000-06-28 2014-04-25 Automated system for adapting market data and evaluating the market value of items
US14/740,630 Expired - Fee Related US9418371B2 (en) 2000-06-28 2015-06-16 Automated system for adapting market data and evaluating the market value of items
US14/808,854 Expired - Fee Related US9412117B2 (en) 2000-06-28 2015-07-24 Automated system for adapting market data and evaluating the market value of items
US15/231,546 Expired - Fee Related US9542689B2 (en) 2000-06-28 2016-08-08 Automated system for adapting market data and evaluating the market value of items
US15/237,518 Expired - Fee Related US9524495B1 (en) 2000-06-28 2016-08-15 Automated system for adapting market data and evaluating the market value of items
US15/257,765 Expired - Fee Related US9576296B2 (en) 2000-06-28 2016-09-06 Automated system for adapting market data and evaluating performance in transactions
US15/368,266 Expired - Fee Related US9754244B2 (en) 2000-06-28 2016-12-02 System and method for adapting market data and evaluating the market value of transactions
US15/445,641 Expired - Fee Related US9710856B2 (en) 2000-06-28 2017-02-28 System and method for adapting market data and evaluating unequal offers
US15/604,533 Expired - Fee Related US9904913B2 (en) 2000-06-28 2017-05-24 Automated system for adapting metric data for use in a transaction-specific analysis or evaluation
US15/641,083 Expired - Fee Related US10055719B2 (en) 2000-06-28 2017-07-03 Automated system and method for adapting market data and evaluating user-specified configurations
US16/105,653 Expired - Fee Related US10262307B2 (en) 2000-06-28 2018-08-20 Automated system for adapting market data for transaction cost analysis
US16/116,175 Expired - Fee Related US10290008B2 (en) 2000-06-28 2018-08-29 Automated system for adapting market data and producing metric values

Family Applications Before (13)

Application Number Title Priority Date Filing Date
US09/607,502 Expired - Lifetime US7043457B1 (en) 2000-06-28 2000-06-28 System and method for managing and evaluating network commodities purchasing
US11/394,540 Expired - Lifetime US7840462B2 (en) 2000-06-28 2006-03-31 System and method for managing and evaluating network commodities purchasing
US12/952,083 Expired - Fee Related US7966240B2 (en) 2000-06-28 2010-11-22 System and method for managing and evaluating network commodities purchasing
US13/118,351 Expired - Fee Related US8224729B2 (en) 2000-06-28 2011-05-27 System and method for managing and evaluating network commodities purchasing
US13/475,900 Expired - Fee Related US8321317B2 (en) 2000-06-28 2012-05-18 System and method for managing and evaluating network commodities purchasing
US13/597,200 Expired - Fee Related US8442888B2 (en) 2000-06-28 2012-08-28 Managing and evaluating price data for purchasing
US13/744,373 Expired - Fee Related US8635139B2 (en) 2000-06-28 2013-01-17 System and method for managing and evaluating network commodities purchasing
US13/846,945 Expired - Fee Related US8700521B2 (en) 2000-06-28 2013-03-18 System and method for managing and evaluating network commodities purchasing
US13/869,942 Expired - Fee Related US8762258B2 (en) 2000-06-28 2013-04-24 System and method for managing and evaluating network commodities purchasing
US14/262,682 Expired - Fee Related US9092825B2 (en) 2000-06-28 2014-04-25 Automated system for adapting market data and evaluating the market value of items
US14/740,630 Expired - Fee Related US9418371B2 (en) 2000-06-28 2015-06-16 Automated system for adapting market data and evaluating the market value of items
US14/808,854 Expired - Fee Related US9412117B2 (en) 2000-06-28 2015-07-24 Automated system for adapting market data and evaluating the market value of items
US15/231,546 Expired - Fee Related US9542689B2 (en) 2000-06-28 2016-08-08 Automated system for adapting market data and evaluating the market value of items

Family Applications After (7)

Application Number Title Priority Date Filing Date
US15/257,765 Expired - Fee Related US9576296B2 (en) 2000-06-28 2016-09-06 Automated system for adapting market data and evaluating performance in transactions
US15/368,266 Expired - Fee Related US9754244B2 (en) 2000-06-28 2016-12-02 System and method for adapting market data and evaluating the market value of transactions
US15/445,641 Expired - Fee Related US9710856B2 (en) 2000-06-28 2017-02-28 System and method for adapting market data and evaluating unequal offers
US15/604,533 Expired - Fee Related US9904913B2 (en) 2000-06-28 2017-05-24 Automated system for adapting metric data for use in a transaction-specific analysis or evaluation
US15/641,083 Expired - Fee Related US10055719B2 (en) 2000-06-28 2017-07-03 Automated system and method for adapting market data and evaluating user-specified configurations
US16/105,653 Expired - Fee Related US10262307B2 (en) 2000-06-28 2018-08-20 Automated system for adapting market data for transaction cost analysis
US16/116,175 Expired - Fee Related US10290008B2 (en) 2000-06-28 2018-08-29 Automated system for adapting market data and producing metric values

Country Status (2)

Country Link
US (21) US7043457B1 (en)
CA (1) CA2351595A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180046344A1 (en) * 2012-10-09 2018-02-15 Mastercard International Incorporated System and method for payment using a mobile device

Families Citing this family (129)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2882882B2 (en) 1994-10-21 1999-04-12 エヌピーエス・ファーマシューティカルズ・インコーポレイテッド Calcium receptor active compound
US7046682B2 (en) * 1997-02-12 2006-05-16 Elster Electricity, Llc. Network-enabled, extensible metering system
US8036943B2 (en) * 2000-03-30 2011-10-11 Walker Digital, Llc Systems and methods for providing transferable item prices
US7043457B1 (en) 2000-06-28 2006-05-09 Probuild, Inc. System and method for managing and evaluating network commodities purchasing
US7353188B2 (en) * 2000-06-30 2008-04-01 Lg Electronics Product selling system and method for operating the same
US6823320B1 (en) * 2000-08-28 2004-11-23 Marc Rubin Automated valuation system and method
WO2002079904A2 (en) * 2001-03-30 2002-10-10 Espeed, Inc. Request for quote (rfq) and inside markets
GB2393299A (en) * 2001-06-13 2004-03-24 Espeed Inc Systems and methods for trading in an exclusive market
US7319991B2 (en) * 2001-12-11 2008-01-15 International Business Machines Corporation Computerized cost estimate system and method
CA3080333C (en) * 2002-02-01 2021-04-06 Canadian National Railway Company System, apparatus and method for conducting an online transaction to fulfill a rail-shipment service inquiry or a rail-shipment service ordering
US20030154101A1 (en) * 2002-02-13 2003-08-14 Archibald Kevin Carl System, methods, and medium for facilitating providing a quote
US7284204B2 (en) * 2002-03-29 2007-10-16 International Business Machines Corporation System, method, and visual user interface for evaluating and selecting suppliers for enterprise procurement
US20030187716A1 (en) * 2002-03-29 2003-10-02 International Business Machines Corporation Method and visual user interface for interactive visual analysis of business expenditure
US20040044591A1 (en) * 2002-06-19 2004-03-04 Gilliland Ramelle L. Method and system for electronic procurement involving electronic requests for quotation
US8655755B2 (en) * 2003-10-22 2014-02-18 Scottrade, Inc. System and method for the automated brokerage of financial instruments
US7890412B2 (en) * 2003-11-04 2011-02-15 New York Mercantile Exchange, Inc. Distributed trading bus architecture
US20050216365A1 (en) * 2004-03-01 2005-09-29 Mainstreet Exchange Exchange system
US20060100896A1 (en) * 2004-11-10 2006-05-11 Lahey Jesse M Web based restaurant management
US20060107228A1 (en) * 2004-11-12 2006-05-18 General Electric Company Method for creating data files
US9821344B2 (en) 2004-12-10 2017-11-21 Ikan Holdings Llc Systems and methods for scanning information from storage area contents
WO2006116573A2 (en) 2005-04-23 2006-11-02 Musa John A Enhanced business and inventory management systems
US7660745B2 (en) * 2005-05-13 2010-02-09 Alcatel-Lucent Usa Inc. System and method for price analysis and negotiation
US20070171232A1 (en) * 2005-06-13 2007-07-26 Malloy Steven J System and method for collecting and distributing market information
US20070118455A1 (en) * 2005-11-18 2007-05-24 Albert William J System and method for directed request for quote
US10726479B2 (en) 2005-11-18 2020-07-28 Chicago Mercantile Exchange Inc. System and method for centralized clearing of over the counter foreign exchange instruments
EP1952335A4 (en) * 2005-11-18 2012-12-26 Chicago Mercantile Exchange Cross-currency implied spreads
US7801810B2 (en) * 2005-11-18 2010-09-21 Chicago Mercantile Exchange Inc. Hybrid cross-margining
US7774250B1 (en) 2005-11-23 2010-08-10 Bgc Partners, Inc. Systems and methods for providing valid responses to requests for quotations
US8583538B2 (en) 2005-11-23 2013-11-12 Bgc Partners, Inc. Providing valid responses to requests for quotations
US7689471B2 (en) * 2006-05-31 2010-03-30 Silvaris Corporation Medium and method providing the ability to display or hide a wood load from buyer view
WO2007140465A2 (en) * 2006-05-31 2007-12-06 Silvaris Corporation System and method for displaying wood products for purchase
US9286639B1 (en) * 2007-05-30 2016-03-15 Intuit Inc. System and method for providing price information
US8756146B2 (en) 2007-08-20 2014-06-17 Chicago Mercantile Exchange Inc. Out of band credit control
US7996301B2 (en) * 2007-08-20 2011-08-09 Chicago Mercantile Exchange, Inc. Out of band credit control
US8762252B2 (en) 2007-08-20 2014-06-24 Chicago Mercantile Exchange Inc. Out of band credit control
US7987135B2 (en) * 2007-08-20 2011-07-26 Chicago Mercantile Exchange, Inc. Out of band credit control
US8452733B2 (en) * 2008-10-17 2013-05-28 Oracle International Corporation Data decay management
US20100106545A1 (en) * 2008-10-27 2010-04-29 Noblis, Inc. Systems and methods for facilitating evaluation in an acquisition process
US8229835B2 (en) 2009-01-08 2012-07-24 New York Mercantile Exchange, Inc. Determination of implied orders in a trade matching system
US20100185489A1 (en) * 2009-01-21 2010-07-22 Satyavolu Ramakrishna V Method for determining a personalized true cost of service offerings
US20110246268A1 (en) * 2009-01-21 2011-10-06 Billshrink, Inc. System and method for providing an opportunity to assess alternative offerings related to a financial transaction
US10594870B2 (en) 2009-01-21 2020-03-17 Truaxis, Llc System and method for matching a savings opportunity using census data
US8600857B2 (en) 2009-01-21 2013-12-03 Truaxis, Inc. System and method for providing a savings opportunity in association with a financial account
US10504126B2 (en) 2009-01-21 2019-12-10 Truaxis, Llc System and method of obtaining merchant sales information for marketing or sales teams
US20110246281A1 (en) * 2009-01-21 2011-10-06 Billshrink, Inc. System and method for providing a savings opportunity in association with a financial account
US10424000B2 (en) * 2009-05-30 2019-09-24 Edmond K. Chow Methods and systems for annotation of digital information
CN101956647B (en) * 2009-07-15 2012-12-19 鸿富锦精密工业(深圳)有限公司 Tidal power generating device
US8417618B2 (en) * 2009-09-03 2013-04-09 Chicago Mercantile Exchange Inc. Utilizing a trigger order with multiple counterparties in implied market trading
US8255305B2 (en) 2009-09-15 2012-08-28 Chicago Mercantile Exchange Inc. Ratio spreads for contracts of different sizes in implied market trading
US8266030B2 (en) * 2009-09-15 2012-09-11 Chicago Mercantile Exchange Inc. Transformation of a multi-leg security definition for calculation of implied orders in an electronic trading system
US20110066537A1 (en) * 2009-09-15 2011-03-17 Andrew Milne Implied volume analyzer
US8229838B2 (en) 2009-10-14 2012-07-24 Chicago Mercantile Exchange, Inc. Leg pricer
US8271344B1 (en) * 2009-10-28 2012-09-18 Intuit Inc. Budget driven purchase monitor
US8548868B1 (en) * 2010-04-26 2013-10-01 Mark Lawrence Method and apparatus to aggregrate demand for buyer specified goods and services
US20120095829A1 (en) * 2010-10-15 2012-04-19 Joseph Bradley Harper Systems and Methods for Managing Contracts and Contract Bids
US8676739B2 (en) * 2010-11-11 2014-03-18 International Business Machines Corporation Determining a preferred node in a classification and regression tree for use in a predictive analysis
US8650051B2 (en) 2010-11-16 2014-02-11 Coral Building Knowledge, LLC Systems and methods for insurance verification
TWI464701B (en) * 2011-01-31 2014-12-11 Shao Yin Cheng Method of competitive bidding for hotel stay products
US20140207525A1 (en) * 2011-02-15 2014-07-24 Dell Products L.P. Method and Apparatus to Calculate Social Pricing Index to Determine Product Pricing in Real-Time
US10740772B2 (en) * 2011-07-25 2020-08-11 Prevedere, Inc. Systems and methods for forecasting based upon time series data
US10896388B2 (en) 2011-07-25 2021-01-19 Prevedere, Inc. Systems and methods for business analytics management and modeling
US10565629B2 (en) * 2011-10-11 2020-02-18 Carrier Services Group, Inc. Computerized valuation of electronic equipment
US20130144689A1 (en) * 2011-12-06 2013-06-06 Green Star Hub Aggregated Customer Grouping
US20130297531A1 (en) * 2012-05-02 2013-11-07 Imageworks Interactive Device for modifying various types of assets
US20130331961A1 (en) * 2012-06-11 2013-12-12 General Electric Company Data exchange system providing flexible and robust handling of units of measure
US20140019303A1 (en) * 2012-07-13 2014-01-16 Wal-Mart Stores, Inc. Comparison of Product Information
WO2014036569A1 (en) * 2012-09-03 2014-03-06 Michael Gurin Dynamic sales system and method with automated feedback negotiation
US11341749B2 (en) * 2012-09-28 2022-05-24 Avaya Inc. System and method to identify visitors and provide contextual services
WO2014087376A1 (en) * 2012-12-06 2014-06-12 Schmahl Wayne Gary Ordering system and method
US20140279175A1 (en) * 2013-03-15 2014-09-18 James C. Graf Quibl Order Process System
US9836789B2 (en) * 2013-03-15 2017-12-05 Integral Development Corporation Method and system for generating and operating hybrid markets and user-defined marketplaces
WO2015050585A1 (en) * 2013-05-24 2015-04-09 Shrimp Trader, Inc. Methods and systems for product management
US9811845B2 (en) 2013-06-11 2017-11-07 Sap Se System for accelerated price master database lookup
US10672053B1 (en) * 2013-08-19 2020-06-02 Michael J. Clemmens Systems, manufactures, and methods for comparative bid analysis and purchase order preparation
US20150120482A1 (en) * 2013-10-29 2015-04-30 Elias Kourpas Efficient Electronic Procurement Using Mathematical Optimization in an Electronic Marketplace
US20160267603A1 (en) * 2013-11-11 2016-09-15 Goldquest Refinement Services Ltd Systems and Methods for Tracking and Validating Commodities Purchases
US20150302424A1 (en) * 2014-04-18 2015-10-22 Mavatar Technologies, Inc. Systems and methods for providing content provider-driven shopping
CN105450583B (en) 2014-07-03 2019-07-05 阿里巴巴集团控股有限公司 A kind of method and device of authentification of message
CN105446992A (en) * 2014-07-08 2016-03-30 阿里巴巴集团控股有限公司 Method and device for building goods object recovery information database and determining value information
CN105450411B (en) 2014-08-14 2019-01-08 阿里巴巴集团控股有限公司 The method, apparatus and system of authentication are carried out using card feature
US11308544B2 (en) 2014-09-26 2022-04-19 Monjeri Investments, Llc System and method to generate shoppable content and increase advertising revenue in social networking using contextual advertising
US10127240B2 (en) * 2014-10-17 2018-11-13 Zestfinance, Inc. API for implementing scoring functions
CN105719183A (en) 2014-12-03 2016-06-29 阿里巴巴集团控股有限公司 Directional transfer method and apparatus
CN105869043A (en) 2015-01-19 2016-08-17 阿里巴巴集团控股有限公司 Disperse hot spot database account transfer-in and transfer-out accounting method and device
CN105989467A (en) 2015-02-03 2016-10-05 阿里巴巴集团控股有限公司 Wireless payment method, apparatus, vehicle ride fee check method and system
US10445343B2 (en) * 2015-07-16 2019-10-15 Interactive Data Pricing And Reference Data Llc Systems and methods for data exchange and conversion
US10546340B1 (en) * 2015-10-06 2020-01-28 Massachusetts Mutual Life Insurance Company Systems and methods for assessing needs
CN106570009B (en) 2015-10-09 2020-07-28 阿里巴巴集团控股有限公司 Navigation category updating method and device
US10803507B1 (en) * 2015-11-23 2020-10-13 Amazon Technologies, Inc. System for generating output comparing attributes of items
JP6788349B2 (en) * 2016-01-14 2020-11-25 三菱重工業株式会社 Plant evaluation equipment and plant evaluation method
US10311507B2 (en) * 2016-01-20 2019-06-04 Accenture Global Solutions Limited Reconfigurable user interface for product analysis
US11774944B2 (en) 2016-05-09 2023-10-03 Strong Force Iot Portfolio 2016, Llc Methods and systems for the industrial internet of things
CA3045439A1 (en) 2016-05-09 2017-11-16 Strong Force Iot Portfolio 2016, Llc Methods and systems for the industrial internet of things
US11327475B2 (en) 2016-05-09 2022-05-10 Strong Force Iot Portfolio 2016, Llc Methods and systems for intelligent collection and analysis of vehicle data
US11366455B2 (en) 2016-05-09 2022-06-21 Strong Force Iot Portfolio 2016, Llc Methods and systems for optimization of data collection and storage using 3rd party data from a data marketplace in an industrial internet of things environment
US10983507B2 (en) 2016-05-09 2021-04-20 Strong Force Iot Portfolio 2016, Llc Method for data collection and frequency analysis with self-organization functionality
US10374872B2 (en) * 2016-05-24 2019-08-06 Apstra, Inc. Configuring system resources for different reference architectures
US11237546B2 (en) 2016-06-15 2022-02-01 Strong Force loT Portfolio 2016, LLC Method and system of modifying a data collection trajectory for vehicles
US10496973B2 (en) * 2016-07-29 2019-12-03 Square, Inc. Reprogrammable point-of-sale transaction flows
US10692055B2 (en) 2016-07-29 2020-06-23 Square, Inc. Reprogrammable point-of-sale transaction flows
US10872320B2 (en) 2016-07-29 2020-12-22 Square, Inc. Reprogrammable point-of-sale transaction flows
US11443250B1 (en) * 2016-11-21 2022-09-13 Chicago Mercantile Exchange Inc. Conservation of electronic communications resources via selective publication of substantially continuously updated data over a communications network
US11182736B2 (en) 2017-05-01 2021-11-23 Wells Fargo Bank, N.A. System and method for smart inventory capture
US20180330325A1 (en) 2017-05-12 2018-11-15 Zippy Inc. Method for indicating delivery location and software for same
CN109299950B (en) * 2017-07-25 2021-10-15 中国科学院沈阳自动化研究所 Flexibly configurable quality inspection management method and system
CA3072045A1 (en) 2017-08-02 2019-02-07 Strong Force Iot Portfolio 2016, Llc Methods and systems for detection in an industrial internet of things data collection environment with large data sets
US11397428B2 (en) 2017-08-02 2022-07-26 Strong Force Iot Portfolio 2016, Llc Self-organizing systems and methods for data collection
TWI672664B (en) * 2017-12-15 2019-09-21 鄭少茵 Negotiation system and method of travel products
CN108734371A (en) 2018-02-12 2018-11-02 阿里巴巴集团控股有限公司 A kind of processing method, device and equipment for air control instruction
CN108632348B (en) 2018-03-19 2020-02-18 阿里巴巴集团控股有限公司 Service checking method and device
US20190392494A1 (en) * 2018-06-22 2019-12-26 General Electric Company System and method relating to part pricing and procurement
US11194832B2 (en) 2018-09-13 2021-12-07 Sap Se Normalization of unstructured catalog data
CN109299096A (en) * 2018-09-25 2019-02-01 阿里巴巴集团控股有限公司 A kind of processing method of pipelined data, device and equipment
US20200160244A1 (en) * 2018-11-15 2020-05-21 Simple Lobby LLC System and Method for Unsolicited Offer Management
CN109492149B (en) * 2018-11-29 2021-04-09 深圳大宇无限科技有限公司 Crawler task processing method and device
CN110035108B (en) * 2018-12-26 2022-01-28 创新先进技术有限公司 Information pushing method and system
US11423465B2 (en) * 2019-01-07 2022-08-23 Masters Choice Systems and methods for facilitating agricultural transactions
CN110009271A (en) * 2019-02-14 2019-07-12 南京中理外轮理货有限公司 A kind of intelligence tally cloud platform system
WO2020194204A1 (en) * 2019-03-26 2020-10-01 Gowda Sachin Hegdekudgi Dakappa System and method for determining grade of a product
US20220172232A1 (en) * 2019-04-12 2022-06-02 Jpmorgan Chase Bank, N.A. System and method for implementing a consolidated contributions data bridge for outbound market and reference data
CN112308720A (en) * 2019-08-02 2021-02-02 深圳前海微众银行股份有限公司 Method and device for determining participants in Federal learning alliance
CN110458669A (en) * 2019-08-15 2019-11-15 车迅联(东莞)网络科技有限公司 Based on the intelligence s ervice platform between car owner, Automobile Service shops and auto-parts supplier
US11216778B2 (en) * 2019-09-30 2022-01-04 EMC IP Holding Company LLC Automatic detection of disruptive orders for a supply chain
TWI739242B (en) * 2019-12-19 2021-09-11 財團法人工業技術研究院 System for visualized storage configuration and method thereof
US11269910B2 (en) * 2020-01-31 2022-03-08 Salesforce.Com, Inc. Methods, apparatuses and computer program products for data retrieval in a group-based communication system
JP2021157666A (en) * 2020-03-27 2021-10-07 横河電機株式会社 Information display, method for displaying information, and program
AU2021375504A1 (en) * 2020-11-09 2023-07-06 QMO IP Pty Ltd. System and methods for dynamically automating reverse auctions
US11687519B2 (en) 2021-08-11 2023-06-27 T-Mobile Usa, Inc. Ensuring availability and integrity of a database across geographical regions
US11574336B1 (en) * 2022-03-11 2023-02-07 Rx Paradigm Inc. Apparatus for secure decentralized rebate management

Family Cites Families (252)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US1927702A (en) 1932-12-03 1933-09-19 Int Communications Lab Inc Average price computer
US3581072A (en) 1968-03-28 1971-05-25 Frederick Nymeyer Auction market computation system
US3933305A (en) 1974-08-23 1976-01-20 John Michael Murphy Asset value calculators
US4412287A (en) 1975-05-29 1983-10-25 Braddock Iii Walter D Automated stock exchange
US4486853A (en) 1981-04-01 1984-12-04 Telemet American, Inc. Apparatus for receiving and displaying continuously updated data
US4903201A (en) 1983-11-03 1990-02-20 World Energy Exchange Corporation Automated futures trading exchange
US4868866A (en) 1984-12-28 1989-09-19 Mcgraw-Hill Inc. Broadcast data distribution system
US4674044A (en) 1985-01-30 1987-06-16 Merrill Lynch, Pierce, Fenner & Smith, Inc. Automated securities trading system
JPS62139088A (en) * 1985-12-13 1987-06-22 Fujitsu Ltd Input data checking system
US4972504A (en) 1988-02-11 1990-11-20 A. C. Nielsen Company Marketing research system and method for obtaining retail data on a real time basis
US4992940A (en) * 1989-03-13 1991-02-12 H-Renee, Incorporated System and method for automated selection of equipment for purchase through input of user desired specifications
US5168446A (en) * 1989-05-23 1992-12-01 Telerate Systems Incorporated System for conducting and processing spot commodity transactions
DE69023705T2 (en) 1989-05-25 1996-07-04 Reuters Ltd Distributed system and method for establishing business relationships between buyers and sellers.
US5077665A (en) 1989-05-25 1991-12-31 Reuters Limited Distributed matching system
US5136501A (en) 1989-05-26 1992-08-04 Reuters Limited Anonymous matching system
US5101353A (en) 1989-05-31 1992-03-31 Lattice Investments, Inc. Automated system for providing liquidity to securities markets
US5063506A (en) 1989-10-23 1991-11-05 International Business Machines Corp. Cost optimization system for supplying parts
US5201047A (en) 1989-12-21 1993-04-06 International Business Machines Corporation Attribute-based classification and retrieval system
US5297031A (en) * 1990-03-06 1994-03-22 Chicago Board Of Trade Method and apparatus for order management by market brokers
GB9027249D0 (en) 1990-12-17 1991-02-06 Reuters Ltd Offer matching system
US5249120A (en) 1991-01-14 1993-09-28 The Charles Stark Draper Laboratory, Inc. Automated manufacturing costing system and method
US5172314A (en) 1991-05-03 1992-12-15 Electronic Retailing Systems International Apparatus for communicating price changes including printer and display devices
US7203661B1 (en) 1992-10-28 2007-04-10 Graff/Ross Holdings Computers making financial analysis output having property valuations
US5293479A (en) 1991-07-08 1994-03-08 Quintero Smith Incorporated Design tool and method for preparing parametric assemblies
US5418943A (en) 1991-10-23 1995-05-23 At&T Corp. Information system with knowledge base and data base
US5555403A (en) 1991-11-27 1996-09-10 Business Objects, S.A. Relational database access system using semantically dynamic objects
US5375055A (en) 1992-02-03 1994-12-20 Foreign Exchange Transaction Services, Inc. Credit management for electronic brokerage system
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
US5515524A (en) 1993-03-29 1996-05-07 Trilogy Development Group Method and apparatus for configuring systems
US6535880B1 (en) 2000-05-09 2003-03-18 Cnet Networks, Inc. Automated on-line commerce method and apparatus utilizing a shopping server verifying product information on product selection
US6714933B2 (en) 2000-05-09 2004-03-30 Cnet Networks, Inc. Content aggregation method and apparatus for on-line purchasing system
US6553346B1 (en) 1996-09-04 2003-04-22 Priceline.Com Incorporated Conditional purchase offer (CPO) management system for packages
US5794207A (en) 1996-09-04 1998-08-11 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers
US5726914A (en) 1993-09-01 1998-03-10 Gse Systems, Inc. Computer implemented process and computer architecture for performance analysis
US5500793A (en) 1993-09-02 1996-03-19 Equitrade Computerized system for developing multi-party property equity exchange scenarios
CA2112077C (en) 1993-09-15 1999-08-24 Barry Craig Smith Network architecture for allocating flight inventory segments and resources
US5446874A (en) 1993-12-23 1995-08-29 International Business Machines Corp. Automated benchmarking with self customization
US5774879A (en) 1993-12-27 1998-06-30 First Data Corporation Automated financial instrument processing system
DE69520097T2 (en) 1994-03-17 2001-07-19 Dow Benelux SYSTEM FOR REAL-TIME OPTIMIZATION AND PRESENTATION OF THE PROFIT
US5486995A (en) 1994-03-17 1996-01-23 Dow Benelux N.V. System for real time optimization
US5809483A (en) 1994-05-13 1998-09-15 Broka; S. William Online transaction processing system for bond trading
US5557514A (en) 1994-06-23 1996-09-17 Medicode, Inc. Method and system for generating statistically-based medical provider utilization profiles
US6023683A (en) * 1994-08-10 2000-02-08 Fisher Scientific Company Electronic sourcing system and method
GB9416673D0 (en) 1994-08-17 1994-10-12 Reuters Ltd Data exchange filtering system
JPH0877010A (en) * 1994-09-07 1996-03-22 Hitachi Ltd Method and device for data analysis
US5826241A (en) * 1994-09-16 1998-10-20 First Virtual Holdings Incorporated Computerized system for making payments and authenticating transactions over the internet
US5675785A (en) 1994-10-04 1997-10-07 Hewlett-Packard Company Data warehouse which is accessed by a user using a schema of virtual tables
US5909543A (en) 1994-11-30 1999-06-01 Canon Kabushiki Kaisha Communication conference system and communication conference apparatus
US5732400A (en) * 1995-01-04 1998-03-24 Citibank N.A. System and method for a risk-based purchase of goods
US5732271A (en) 1995-01-23 1998-03-24 International Business Machines Corporation Data processing system and method for processing an object oriented development environment employing property inheritance using prototypical objects
US5845266A (en) 1995-12-12 1998-12-01 Optimark Technologies, Inc. Crossing network utilizing satisfaction density profile with price discovery features
US7133835B1 (en) 1995-08-08 2006-11-07 Cxn, Inc. Online exchange market system with a buyer auction and a seller auction
US6282521B1 (en) 1995-08-28 2001-08-28 Ebs Dealing Resources, Inc. Anonymous trading system with improved quote input capabilities
US5873069A (en) 1995-10-13 1999-02-16 American Tv & Appliance Of Madison, Inc. System and method for automatic updating and display of retail prices
US5715402A (en) * 1995-11-09 1998-02-03 Spot Metals Online Method and system for matching sellers and buyers of spot metals
US6519574B1 (en) 1995-12-12 2003-02-11 Reuters Limited Electronic trading system featuring arbitrage and third-party credit opportunities
CA2193582A1 (en) 1995-12-21 1997-06-22 Aidan O'leary Order processing method
US6055518A (en) * 1996-02-01 2000-04-25 At&T Corporation Secure auction systems
US5758328A (en) 1996-02-22 1998-05-26 Giovannoli; Joseph Computerized quotation system and method
US6034652A (en) 1996-03-22 2000-03-07 Interval Research Corporation Attention manager for occupying the peripheral attention of a person in the vicinity of a display device
US5950176A (en) 1996-03-25 1999-09-07 Hsx, Inc. Computer-implemented securities trading system with a virtual specialist function
US6505174B1 (en) 1996-03-25 2003-01-07 Hsx, Inc. Computer-implemented securities trading system with a virtual specialist function
US5835896A (en) 1996-03-29 1998-11-10 Onsale, Inc. Method and system for processing and transmitting electronic auction information
US5771370A (en) 1996-05-14 1998-06-23 Mentor Graphics Corporation Method and apparatus for optimizing hardware and software co-simulation
US5924083A (en) 1996-05-29 1999-07-13 Geneva Branch Of Reuters Transaction Services Limited Distributed matching system for displaying a book of credit filtered bids and offers
US6061662A (en) 1997-08-15 2000-05-09 Options Technology Company, Inc. Simulation method and system for the valuation of derivative financial instruments
US5825651A (en) 1996-09-03 1998-10-20 Trilogy Development Group, Inc. Method and apparatus for maintaining and configuring systems
US5963910A (en) 1996-09-20 1999-10-05 Ulwick; Anthony W. Computer based process for strategy evaluation and optimization based on customer desired outcomes and predictive metrics
US5764916A (en) 1996-09-27 1998-06-09 Ichat, Inc. Method and apparatus for real time communication over a computer network
US5799300A (en) 1996-12-12 1998-08-25 International Business Machines Corporations Method and system for performing range-sum queries on a data cube
US5822751A (en) 1996-12-16 1998-10-13 Microsoft Corporation Efficient multidimensional data aggregation operator implementation
US6460020B1 (en) * 1996-12-30 2002-10-01 De Technologies, Inc. Universal shopping center for international operation
US6865524B1 (en) 1997-01-08 2005-03-08 Trilogy Development Group, Inc. Method and apparatus for attribute selection
US6038537A (en) * 1997-03-19 2000-03-14 Fujitsu Limited Intra-organization cooperation system, commodity deal management method, and storage medium
US6032158A (en) 1997-05-02 2000-02-29 Informatica Corporation Apparatus and method for capturing and propagating changes from an operational database to data marts
US5873071A (en) 1997-05-15 1999-02-16 Itg Inc. Computer method and system for intermediated exchange of commodities
US5999940A (en) 1997-05-28 1999-12-07 Home Information Services, Inc. Interactive information discovery tool and methodology
US6205447B1 (en) 1997-06-30 2001-03-20 International Business Machines Corporation Relational database management of multi-dimensional data
US7711604B1 (en) * 1997-07-08 2010-05-04 Walker Digital, Llc Retail system for selling products based on a flexible product description
US6014647A (en) 1997-07-08 2000-01-11 Nizzari; Marcia M. Customer interaction tracking
US5991696A (en) * 1997-07-11 1999-11-23 American Air Liquide Inc. Method for intelligent data acquisition in a measurement system
US6058379A (en) * 1997-07-11 2000-05-02 Auction Source, L.L.C. Real-time network exchange with seller specified exchange parameters and interactive seller participation
US6049783A (en) 1997-08-08 2000-04-11 Power Financial Group, Inc. Interactive internet analysis method
JP3753207B2 (en) 1997-08-11 2006-03-08 富士ゼロックス株式会社 Collaborative work support system and collaborative work support method
US6094651A (en) 1997-08-22 2000-07-25 International Business Machines Corporation Discovery-driven exploration of OLAP data cubes
US5960411A (en) 1997-09-12 1999-09-28 Amazon.Com, Inc. Method and system for placing a purchase order via a communications network
US6442533B1 (en) 1997-10-29 2002-08-27 William H. Hinkle Multi-processing financial transaction processing system
US5987435A (en) 1997-10-30 1999-11-16 Case Shiller Weiss, Inc. Proxy asset data processor
US6233609B1 (en) 1997-10-31 2001-05-15 Selectica, Inc Method and apparatus for remote interaction with and configuration of a wan-based knowledge base
US6535913B2 (en) 1997-10-31 2003-03-18 Selectica, Inc. Method and apparatus for use of an application state storage system in interacting with on-line services
US6049822A (en) 1997-10-31 2000-04-11 Selectica, Inc. Method for generating and updating knowledge-based configurators that are multi platform and multi language capable
US6339775B1 (en) 1997-11-07 2002-01-15 Informatica Corporation Apparatus and method for performing data transformations in data warehousing
US6064982A (en) 1997-11-12 2000-05-16 Netscape Communication Corporation Smart configurator
US7376578B1 (en) 1997-11-19 2008-05-20 I2 Technologies Us, Inc. Computer-implemented product valuation tool
EP1031105A2 (en) 1997-11-20 2000-08-30 Xacct Technologies, Inc. Network accounting and billing system and method
US5857174A (en) * 1997-11-21 1999-01-05 Dugan; John W. Real estate appraisal method and device for standardizing real property marketing analysis by using pre-adjusted appraised comparable sales
US6654747B1 (en) 1997-12-02 2003-11-25 International Business Machines Corporation Modular scalable system for managing data in a heterogeneous environment with generic structure for control repository access transactions
US6035287A (en) 1997-12-17 2000-03-07 Omega Consulting, Inc. Method and apparatus for bundled asset trading
US7124106B1 (en) * 1997-12-17 2006-10-17 Omega Consulting, Inc. Apparatus for trading of bundled assets including bundle substitution and method therefor
US6484158B1 (en) 1997-12-19 2002-11-19 A.C. Nielsen Company Dynamic rule based market research database
US6085196A (en) 1997-12-23 2000-07-04 Ricoh Company, Ltd. Object-oriented system and computer program product for mapping structured information to different structured information
US6078924A (en) 1998-01-30 2000-06-20 Aeneid Corporation Method and apparatus for performing data collection, interpretation and analysis, in an information platform
US6161103A (en) 1998-05-06 2000-12-12 Epiphany, Inc. Method and apparatus for creating aggregates for use in a datamart
US6311144B1 (en) * 1998-05-13 2001-10-30 Nabil A. Abu El Ata Method and apparatus for designing and analyzing information systems using multi-layer mathematical models
US7389211B2 (en) 1998-05-13 2008-06-17 Abu El Ata Nabil A System and method of predictive modeling for managing decisions for business enterprises
US7031901B2 (en) * 1998-05-13 2006-04-18 Abu El Ata Nabil A System and method for improving predictive modeling of an information system
US7603286B2 (en) 1998-05-21 2009-10-13 Sap Ag Demand-model based price image calculation method and computer program therefor
US6609098B1 (en) 1998-07-02 2003-08-19 Ita Software, Inc. Pricing graph representation for sets of pricing solutions for travel planning system
US6175619B1 (en) 1998-07-08 2001-01-16 At&T Corp. Anonymous voice communication using on-line controls
US6076070A (en) * 1998-07-23 2000-06-13 Cendant Publishing, Inc. Apparatus and method for on-line price comparison of competitor's goods and/or services over a computer network
US6976006B1 (en) * 1998-09-01 2005-12-13 Chhedi Lal Verma Method and apparatus for presenting price comparison to prospective buyers
AU6037699A (en) * 1998-09-15 2000-04-03 Talpx, Inc. Techniques for trading commodities on a private trading system and not regulatedby the government
US7249085B1 (en) 1999-03-31 2007-07-24 Ariba, Inc. Method and system for conducting electronic auctions with multi-parameter price equalization bidding
US7383206B2 (en) 1999-02-19 2008-06-03 Ariba, Inc. Method and apparatus for multiple variable bidding in an online auction
US6167383A (en) 1998-09-22 2000-12-26 Dell Usa, Lp Method and apparatus for providing customer configured machines at an internet site
US6317728B1 (en) 1998-10-13 2001-11-13 Richard L. Kane Securities and commodities trading system
US6125391A (en) 1998-10-16 2000-09-26 Commerce One, Inc. Market makers using documents for commerce in trading partner networks
US6618707B1 (en) 1998-11-03 2003-09-09 International Securities Exchange, Inc. Automated exchange for trading derivative securities
US6377940B2 (en) * 1998-11-05 2002-04-23 International Securities Exchange, Llc Method and apparatus for setting a price for a security on an automated exchange based on a comparison of prices on other exchanges
US6134548A (en) 1998-11-19 2000-10-17 Ac Properties B.V. System, method and article of manufacture for advanced mobile bargain shopping
US6141653A (en) 1998-11-16 2000-10-31 Tradeaccess Inc System for interative, multivariate negotiations over a network
US6285997B1 (en) 1998-11-16 2001-09-04 International Business Machines Corporation Query optimization with deferred update and autonomous sources
US6336105B1 (en) 1998-11-16 2002-01-01 Trade Access Inc. System and method for representing data and providing electronic non-repudiation in a negotiations system
US6341277B1 (en) 1998-11-17 2002-01-22 International Business Machines Corporation System and method for performance complex heterogeneous database queries using a single SQL expression
US6393605B1 (en) 1998-11-18 2002-05-21 Siebel Systems, Inc. Apparatus and system for efficient delivery and deployment of an application
US6260024B1 (en) 1998-12-02 2001-07-10 Gary Shkedy Method and apparatus for facilitating buyer-driven purchase orders on a commercial network system
US6415263B1 (en) 1998-12-14 2002-07-02 Ncr Corporation System and methods for determining and displaying product pricing
US7107226B1 (en) 1999-01-20 2006-09-12 Net32.Com, Inc. Internet-based on-line comparison shopping system and method of interactive purchase and sale of products
US6411936B1 (en) 1999-02-05 2002-06-25 Nval Solutions, Inc. Enterprise value enhancement system and method
US6408282B1 (en) 1999-03-01 2002-06-18 Wit Capital Corp. System and method for conducting securities transactions over a computer network
US6963854B1 (en) 1999-03-05 2005-11-08 Manugistics, Inc. Target pricing system
US7617144B2 (en) 1999-03-19 2009-11-10 Primex Holdings Llc Auction market with price improvement mechanism
US7742934B2 (en) 1999-03-25 2010-06-22 Travelocity.Com Lp Methods and apparatus for determining non-obvious savings in the purchase of goods and services
US6101484A (en) 1999-03-31 2000-08-08 Mercata, Inc. Dynamic market equilibrium management system, process and article of manufacture
US7840476B1 (en) * 1999-03-31 2010-11-23 Ariba, Inc. Transformation bidding with tooling requirements
US7010511B1 (en) 1999-03-31 2006-03-07 Kinney Jr Sam E Method and system for conducting electronic auctions with net present value bidding
JP3788100B2 (en) * 1999-03-31 2006-06-21 富士通株式会社 Electronic commerce system and computer-readable recording medium
US7212999B2 (en) 1999-04-09 2007-05-01 Trading Technologies International, Inc. User interface for an electronic trading system
US6993504B1 (en) 1999-04-09 2006-01-31 Trading Technologies International, Inc. User interface for semi-fungible trading
US8126779B2 (en) * 1999-04-11 2012-02-28 William Paul Wanker Machine implemented methods of ranking merchants
US6278982B1 (en) 1999-04-21 2001-08-21 Lava Trading Inc. Securities trading system for consolidation of trading on multiple ECNS and electronic exchanges
US7392214B1 (en) 1999-04-30 2008-06-24 Bgc Partners, Inc. Systems and methods for trading
US6163774A (en) 1999-05-24 2000-12-19 Platinum Technology Ip, Inc. Method and apparatus for simplified and flexible selection of aggregate and cross product levels for a data warehouse
US6381605B1 (en) 1999-05-29 2002-04-30 Oracle Corporation Heirarchical indexing of multi-attribute data by sorting, dividing and storing subsets
US7039040B1 (en) 1999-06-07 2006-05-02 At&T Corp. Voice-over-IP enabled chat
US6564192B1 (en) * 1999-06-08 2003-05-13 Freemarkets, Inc. Method and system for differential index bidding in online auctions
US6862580B1 (en) 1999-06-11 2005-03-01 Robert M. Ford System and method for managing tier-priced commodity transactions
EP1061422B1 (en) 1999-06-11 2006-01-18 IvyTeam AG Computer system for the definition, optimisation and control of processes
EP1266317A4 (en) 1999-06-14 2005-12-14 Integral Dev Corp System and method for conducting web-based financial transactions in capital markets
US6629082B1 (en) 1999-06-15 2003-09-30 W.R. Hambrecht & Co. Auction system and method for pricing and allocation during capital formation
US6477536B1 (en) 1999-06-22 2002-11-05 Microsoft Corporation Virtual cubes
US7024376B1 (en) 1999-07-02 2006-04-04 Yuen Henry C Internet-based auction method
US7330826B1 (en) 1999-07-09 2008-02-12 Perfect.Com, Inc. Method, system and business model for a buyer's auction with near perfect information using the internet
US7296001B1 (en) 1999-07-12 2007-11-13 Ariba, Inc. Electronic multilateral negotiation system
US6385604B1 (en) 1999-08-04 2002-05-07 Hyperroll, Israel Limited Relational database management system having integrated non-relational multi-dimensional data store of aggregated data elements
US6907404B1 (en) 1999-08-16 2005-06-14 Wsetport Financial Llc. Automated investment chart pattern search system for technical analysis
US20030093343A1 (en) * 1999-08-31 2003-05-15 Sidley Austin Brown & Wood Llp Dynamic order visibility system for the trading of assets
WO2001016844A1 (en) 1999-08-31 2001-03-08 Priceline.Com Incorporated System and method for facilitating the sale of a travel product
US7685048B1 (en) * 1999-09-01 2010-03-23 Bloomberg L.P. Electronic trading system for forwards spread trades
US6807565B1 (en) 1999-09-03 2004-10-19 Cisco Technology, Inc. Instant messaging system using voice enabled web based application server
US6415270B1 (en) 1999-09-03 2002-07-02 Omnihub, Inc. Multiple auction coordination method and system
US6389407B1 (en) 1999-09-13 2002-05-14 General Electric Company Method for documenting engineering rules
US6892186B1 (en) 1999-09-15 2005-05-10 Hewlett-Packard Development Company, L.P. Auction method and apparatus for electronic commerce
US6847938B1 (en) 1999-09-20 2005-01-25 Donna R. Moore Method of exchanging goods over the internet
US7577582B1 (en) * 1999-09-21 2009-08-18 Nextag, Inc. Methods and apparatus for facilitating transactions
US8407116B1 (en) 1999-09-23 2013-03-26 The Nasdaq Omx Group, Inc. Quote/order processing in electronic market system
US7181424B1 (en) 1999-09-23 2007-02-20 The Nasdaq Stock Market, Inc. Montage for automated market system
US6990238B1 (en) 1999-09-30 2006-01-24 Battelle Memorial Institute Data processing, analysis, and visualization system for use with disparate data types
US6792458B1 (en) 1999-10-04 2004-09-14 Urchin Software Corporation System and method for monitoring and analyzing internet traffic
US6339776B2 (en) 1999-10-04 2002-01-15 International Business Machines Corporation Dynamic semi-structured repository for mining software and software-related information
US6505175B1 (en) 1999-10-06 2003-01-07 Goldman, Sachs & Co. Order centric tracking system
US7171386B1 (en) 1999-10-08 2007-01-30 Rfv Holdings Real-time commodity trading method and apparatus
US7251629B1 (en) 1999-10-14 2007-07-31 Edge Capture, Llc Automated trading system in an electronic trading exchange
US6856967B1 (en) 1999-10-21 2005-02-15 Mercexchange, Llc Generating and navigating streaming dynamic pricing information
US7373317B1 (en) 1999-10-27 2008-05-13 Ebay, Inc. Method and apparatus for facilitating sales of goods by independent parties
US20020069134A1 (en) * 1999-11-01 2002-06-06 Neal Solomon System, method and apparatus for aggregation of cooperative intelligent agents for procurement in a distributed network
US20030233305A1 (en) * 1999-11-01 2003-12-18 Neal Solomon System, method and apparatus for information collaboration between intelligent agents in a distributed network
US7072857B1 (en) 1999-11-06 2006-07-04 Cynthia Calonge Method for providing online submission of requests for proposals for forwarding to identified vendors
US6556976B1 (en) 1999-11-10 2003-04-29 Gershman, Brickner And Bratton, Inc. Method and system for e-commerce and related data management, analysis and reporting
US6677963B1 (en) 1999-11-16 2004-01-13 Verizon Laboratories Inc. Computer-executable method for improving understanding of business data by interactive rule manipulation
US7386497B1 (en) 1999-11-22 2008-06-10 Gfi Group, Inc. System and method for trading an instrument
US6725257B1 (en) 1999-11-30 2004-04-20 Chrome Data Corporation Computationally efficient process and apparatus for configuring a product over a computer network
US7509261B1 (en) 1999-12-06 2009-03-24 Federal Home Loan Mortgage Corporation Method for forecasting house prices using a dynamic error correction model
US20010032163A1 (en) * 1999-12-06 2001-10-18 Michael Fertik Method and apparatus for open market trading
AU2589401A (en) 1999-12-21 2001-07-03 Net Horsepower, Inc. Method and apparatus for internet connectivity for agriculture buyers, sellers and transporters
US6510434B1 (en) * 1999-12-29 2003-01-21 Bellsouth Intellectual Property Corporation System and method for retrieving information from a database using an index of XML tags and metafiles
US7536335B1 (en) 1999-12-30 2009-05-19 Bloomberg L.P. System and method for implementing foreign exchange currency forwards
US7206756B1 (en) 2000-01-14 2007-04-17 Trilogy Development Group, Inc. System and method for facilitating commercial transactions over a data network
US7233923B1 (en) 2000-01-14 2007-06-19 Espeed, Inc. Systems and methods for matching desired purchases and sales of mis-matched items
US8554659B2 (en) 2000-01-21 2013-10-08 Tradecapture Otc Corp. System for trading commodities and the like
US7024383B1 (en) 2000-01-31 2006-04-04 Goldman, Sachs & Co. Online sales risk management system
US7835970B1 (en) * 2000-02-02 2010-11-16 Cmvt, Llc Method and system for automated auction and tender of complex multi-variable commodities
US7430531B1 (en) * 2000-02-04 2008-09-30 Verisign, Inc. System and method for assisting customers in choosing a bundled set of commodities using customer preferences
US6618714B1 (en) 2000-02-10 2003-09-09 Sony Corporation Method and system for recommending electronic component connectivity configurations and other information
US20010032116A1 (en) * 2000-02-11 2001-10-18 Geoffrey Hyatt System and method for providing information on market pricing
EP1277145A4 (en) 2000-02-16 2003-05-21 Bea Systems Inc Conversation management system for enterprise wide electronic collaboration
US20030018550A1 (en) 2000-02-22 2003-01-23 Rotman Frank Lewis Methods and systems for providing transaction data
US7113919B1 (en) 2000-02-29 2006-09-26 Chemdomain, Inc. System and method for configuring products over a communications network
US20010032171A1 (en) * 2000-03-07 2001-10-18 Brink Jerry Ten System and method for trading commodities
US7979347B1 (en) 2000-03-16 2011-07-12 Goldman Sachs & Co. Automated online sales risk management
US20050010494A1 (en) * 2000-03-21 2005-01-13 Pricegrabber.Com Method and apparatus for Internet e-commerce shopping guide
US6941280B1 (en) 2000-03-27 2005-09-06 The American Stock Exchange, Llc Determining intra-day net asset value of an actively managed exchange traded fund
WO2001077965A2 (en) * 2000-04-10 2001-10-18 Eastman Chemical Company Systems and methods for facilitating transactions in a commodity marketplace
US7472087B2 (en) 2000-04-10 2008-12-30 Stikine Technology, Llc Trading program for interacting with market programs on a platform
WO2001080131A1 (en) 2000-04-13 2001-10-25 Superderivatives, Inc. Method and system for pricing options
US7216092B1 (en) 2000-04-14 2007-05-08 Deluxe Corporation Intelligent personalization system and method
AU2001257077A1 (en) 2000-04-17 2001-10-30 Brio Technology, Inc. Analytical server including metrics engine
US7003486B1 (en) 2000-04-17 2006-02-21 Neha Net Corp. Net-value creation and allocation in an electronic trading system
US7212996B1 (en) 2000-04-20 2007-05-01 Jpmorgan Chase Bank, N.A. System and method for dynamic, multivariable comparison of financial products
US7376613B1 (en) 2000-04-21 2008-05-20 International Business Machines Corporation Business method for comparison shopping with dynamic pricing over a network
US20040015415A1 (en) * 2000-04-21 2004-01-22 International Business Machines Corporation System, program product, and method for comparison shopping with dynamic pricing over a network
US6604107B1 (en) 2000-04-24 2003-08-05 Ebay Inc. Generic attribute database system for storing items of different categories having shared attributes
US7058598B1 (en) * 2000-04-30 2006-06-06 International Business Machines Corporation Web price optimizer of multiple-item package orders for e-commerce on the internet and method of use
US7467110B2 (en) 2000-05-01 2008-12-16 The Olsen Group Method for market making
US7689495B1 (en) 2000-05-01 2010-03-30 Bloomberg L.P. System and method for processing trades using volume-weighted-average pricing techniques
US7742959B2 (en) * 2000-05-01 2010-06-22 Mueller Ulrich A Filtering of high frequency time series data
US7424452B2 (en) 2000-05-04 2008-09-09 American International Group, Inc. Method and system for initiating and clearing trades
US7970713B1 (en) * 2000-05-10 2011-06-28 OIP Technologies, Inc. Method and apparatus for automatic pricing in electronic commerce
US7246092B1 (en) 2000-05-12 2007-07-17 The Nasdaq Stock Market, Inc. Montage for an electronic market
US7908200B2 (en) 2000-05-16 2011-03-15 Versata Development Group, Inc. Method and apparatus for efficiently generating electronic requests for quote
US7653583B1 (en) * 2000-05-16 2010-01-26 Versata Development Group, Inc. Method and apparatus for filtering and/or sorting responses to electronic requests for quote
US7133848B2 (en) 2000-05-19 2006-11-07 Manugistics Inc. Dynamic pricing system
US6546402B1 (en) 2000-06-05 2003-04-08 International Business Machines Corporation System and method for asynchronous view maintenance
US7212997B1 (en) 2000-06-09 2007-05-01 Ari Pine System and method for analyzing financial market data
US20020007324A1 (en) * 2000-06-09 2002-01-17 Centner David J. System and method for effectively conducting transactions between buyers and suppliers
US6850900B1 (en) * 2000-06-19 2005-02-01 Gary W. Hare Full service secure commercial electronic marketplace
US20020152135A1 (en) * 2000-06-19 2002-10-17 Yishai Beeri System and method for e-commerce interface with controlled e-commerce interactions
US7043457B1 (en) * 2000-06-28 2006-05-09 Probuild, Inc. System and method for managing and evaluating network commodities purchasing
US8005684B1 (en) 2000-06-29 2011-08-23 Ford Global Technologies, Llc Method for estimating a used vehicle's market value
US7765140B1 (en) * 2000-08-08 2010-07-27 International Business Machines Corporation System for enhancing buyers performance in electronic commerce
US20020026630A1 (en) * 2000-08-28 2002-02-28 John Schmidt Enterprise application integration methodology
US7149717B1 (en) * 2000-10-26 2006-12-12 Kan Steven S Method and system to effectuate multiple transaction prices for a commodity
US7379898B2 (en) * 2000-12-22 2008-05-27 I2 Technologies Us, Inc. System and method for generating market pricing information for non-fungible items
US6873968B2 (en) * 2001-02-10 2005-03-29 International Business Machines Corporation System, method and computer program product for on-line real-time price comparison and adjustment within a detachable virtual shopping cart
US20020156685A1 (en) * 2001-02-10 2002-10-24 International Business Machines Corporation System and method for automating electronic commerce transactions using a virtual shopping cart
US20030065586A1 (en) * 2001-07-31 2003-04-03 Shaftel Keith L. Electronic commerce product pricing and selection system and method
SE0103642D0 (en) * 2001-11-01 2001-11-01 Om Technology Ab A method and a system for improved trading of options and futures and combinations thereof
US20060253334A1 (en) * 2002-09-13 2006-11-09 Masahiko Fukasawa Order placement and acceptance management system
US20040117291A1 (en) * 2002-12-12 2004-06-17 O'callahan Dennis M. Method of trading derivative investment products based on an index adapted to reflect the relative performance of two different investment assets
EP1618486A4 (en) * 2003-03-27 2008-10-08 Univ Washington Performing predictive pricing based on historical data
US7660738B1 (en) * 2003-04-28 2010-02-09 Amazon.Com, Inc. Collecting competitive pricing information via a merchant web site for use in setting prices on the merchant web site
US7702615B1 (en) * 2005-11-04 2010-04-20 M-Factor, Inc. Creation and aggregation of predicted data
US7725358B1 (en) * 2005-12-28 2010-05-25 United Services Automobile Association (Usaa) System and method for providing multiple real-time pricing quotes based on optional consumer variables
US8639605B2 (en) * 2006-04-21 2014-01-28 Thomson Reuters Global Resources Systems and methods for the identification and messaging of trading parties
US20080077542A1 (en) * 2006-09-22 2008-03-27 Second Rotation Inc. Systems and methods for determining market price of merchandise
WO2008077074A2 (en) * 2006-12-18 2008-06-26 Silvaris Corporation Determining and presenting product market prices
US8180710B2 (en) * 2007-09-25 2012-05-15 Strichman Adam J System, method and computer program product for an interactive business services price determination and/or comparison model
US20100023379A1 (en) * 2008-07-07 2010-01-28 HMVP Partners, LLC Method and system for determining real estate market value changes
US20100082419A1 (en) * 2008-10-01 2010-04-01 David Hsueh-Chi Au-Yeung Systems and methods of rating an offer for a products
US7684144B1 (en) 2008-10-29 2010-03-23 Quantum Corporation Multi-rate tracking with a multi-actuator servo control
US8341058B2 (en) * 2009-01-16 2012-12-25 Future Beef Partners Inc. System and method for managing a portfolio of different cuts of meat

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180046344A1 (en) * 2012-10-09 2018-02-15 Mastercard International Incorporated System and method for payment using a mobile device

Also Published As

Publication number Publication date
US20140236801A1 (en) 2014-08-21
US8224729B2 (en) 2012-07-17
US9092825B2 (en) 2015-07-28
US20190005472A1 (en) 2019-01-03
US20180357618A1 (en) 2018-12-13
US8635139B2 (en) 2014-01-21
US7043457B1 (en) 2006-05-09
US20120330725A1 (en) 2012-12-27
US20130218745A1 (en) 2013-08-22
US20170169514A1 (en) 2017-06-15
US20060173767A1 (en) 2006-08-03
CA2351595A1 (en) 2001-12-28
US8700521B2 (en) 2014-04-15
US20160371711A1 (en) 2016-12-22
US20170300878A1 (en) 2017-10-19
US8762258B2 (en) 2014-06-24
US7840462B2 (en) 2010-11-23
US20170255909A1 (en) 2017-09-07
US10290008B2 (en) 2019-05-14
US20110071918A1 (en) 2011-03-24
US9710856B2 (en) 2017-07-18
US9412117B2 (en) 2016-08-09
US20160350777A1 (en) 2016-12-01
US7966240B2 (en) 2011-06-21
US20150332300A1 (en) 2015-11-19
US8442888B2 (en) 2013-05-14
US10262307B2 (en) 2019-04-16
US20170083976A1 (en) 2017-03-23
US10055719B2 (en) 2018-08-21
US9576296B2 (en) 2017-02-21
US8321317B2 (en) 2012-11-27
US20110231339A1 (en) 2011-09-22
US9754244B2 (en) 2017-09-05
US9904913B2 (en) 2018-02-27
US20120233056A1 (en) 2012-09-13
US20150278839A1 (en) 2015-10-01
US20130132160A1 (en) 2013-05-23
US9542689B2 (en) 2017-01-10
US20130254092A1 (en) 2013-09-26
US9418371B2 (en) 2016-08-16
US9524495B1 (en) 2016-12-20

Similar Documents

Publication Publication Date Title
US9524495B1 (en) Automated system for adapting market data and evaluating the market value of items
US8046269B2 (en) Auction based procurement system
US7272579B1 (en) Auction based procurement system
WO2001033464A1 (en) Customer demand-initiated system and method for on-line information retrieval, interactive negotiation, procurement, and exchange
GB2395327A (en) Method and system for online procurement

Legal Events

Date Code Title Description
STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction
FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20201220