WO2003012718A1 - Outil de gestion de soumissions - Google Patents

Outil de gestion de soumissions Download PDF

Info

Publication number
WO2003012718A1
WO2003012718A1 PCT/US2001/026967 US0126967W WO03012718A1 WO 2003012718 A1 WO2003012718 A1 WO 2003012718A1 US 0126967 W US0126967 W US 0126967W WO 03012718 A1 WO03012718 A1 WO 03012718A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
bid
classification
level
response
Prior art date
Application number
PCT/US2001/026967
Other languages
English (en)
Inventor
Karl F. Almstead
Lars Lindberg
Lars Ersmarker
Original Assignee
Hochtief Ag
Skanska Ab
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hochtief Ag, Skanska Ab filed Critical Hochtief Ag
Priority to US10/484,372 priority Critical patent/US20040210490A1/en
Publication of WO2003012718A1 publication Critical patent/WO2003012718A1/fr

Links

Classifications

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

Definitions

  • the present invention relates to the field of software tools, and more particularly to a tool that facilitates the management of requests to submit bids and the responses to those requests.
  • the general contractor may issue a request to bid on a particular scope of work containing items that need to be completed to other entities, e.g., sub-contractors, in order to select the best entity to perform the particular scope of work.
  • the general contractor may then select one of the sub-contractors to complete the particular scope of work.
  • the entity responsible for the project may issue a request to bid, commonly referred to as a "bid request," containing a list of line items that need to be provided in order to complete the project.
  • the entity responsible for the project may need to provide documentation, e.g., drawings, diagrams, specifications, in order to assist the recipient of the bid request in understanding the bid request.
  • the line items provide the detail for the scope of work as stated above. If an entity receiving such a request decides to respond, it may need to include at least an estimate of the costs for completing such line item(s). Such costs may include, for example, material costs, labor costs, insurance costs, and the like. Once these costs are determined, the recipient may add a profit margin to the estimated costs and then submit its response back to the issuer of the request.
  • the recipient may need to solicit bids for some or all of those line items from other entities. That is, the recipient of the bid request may need to then issue a bid request itself on a portion of those items in the request received.
  • a recipient may receive multiple bid requests from the same or different requesters relating to the same or different projects. These multiple requests may include line items and accompanying documentation, e.g., agreements, drawings, that need to be procured by the recipient. To obtain better pricing or terms, the recipient may want to combine line items found in multiple requests into a new request to solicit bids from sub-contractors, material suppliers, manufacturers or other types of vendors or suppliers.
  • Traditional methodologies for issuing requests and preparing responses are both time and labor intensive, and therefore, costly.
  • the traditional methodologies are vulnerable to human error and have proven ill suited for projects of increasing magnitude and complexity where the bidding process has expanded geometrically.
  • a tool that allows a recipient of a bid request to become a bid requester thereby being able to submit one or more bid requests to other entities
  • the tool may allow a user to import data related to one or more line items contained in one or more responses to one or more bid requests into one or more new responses to be submitted to the appropriate entity
  • the tool may allow a user to aggregate the line items and the accompanying documentation, e g , agreements, drawings, if any, in the received requests, into one or more new requests to be submitted to other entities
  • the tool may allow a user to select and import data related to particular line items from one or more responses to an aggregated request into one or more new responses to be submitted to the appropriate entity
  • a method for managing bids may comprise the step of one or more requesters, e g , owners, operating at a particular level of classification, e g , first level of classification, issuing one or more bid requests to one or more users, e g , general contractors, operating at the next lower level of classification
  • Levels of classifications may refer to stages at which the user(s) may be involved in the process of bidding on a particular project
  • the bid request may comprise a plurality of line items as well as any accompanying documentation, e g , agreements, drawings, if any
  • the user may issue a new bid request to one or more users operating at a next lower level of classification, e g , third level of classification corresponding to sub-contractors
  • the new bid request issued by the user may include one or more of the plurality of line items as well as any accompanying documentation, if any, in the received bid request into the new bid
  • the recipient of one or more responses to bid requests previously submitted may import data, e g , description of goods, price quotes, related to one or more selected line items in the received responses into a new response to be submitted to a user operating at a next higher level of classification, e.g., general contractor.
  • a next higher level of classification e.g., general contractor.
  • the user may select particular data, if any, from any one of those responses related to a line item with more than one response. That data related to the line item may then be imported into one or more responses to be submitted to one or more users operating at a next higher level of classification.
  • the user may further select particular data, if any, related to a line item that does not have more than one response. That data related to the line item may then be imported into one or more responses to be submitted to one or more users operating at a next higher level of classification. If the received responses are not responses to the same line items then the user may import data related to one or more line items in one or more responses into one or more responses to be submitted to one or more users operating at a next higher level of classification. The received responses that are imported into the new response may be hidden to the user operating at a next higher level of classification that receives the new response. That is, these bid responses may not be separately accessible by the user operating at a next higher level of classification that receives the new response.
  • Figure 1 illustrates an embodiment of a network system configured in accordance with the present invention
  • Figure 2 illustrates an embodiment of a server configured in accordance with the present invention
  • Figure 3 illustrates an embodiment of a client configured in accordance with the present invention
  • Figure 4 illustrates a hierarchical diagram of an overall process for transmitting bid requests in accordance with the present invention
  • Figure 5 illustrates a hierarchical diagram of an overall process for responding to bid requests in accordance with the present invention
  • FIG. 6 is a flowchart of a method for managing Requests For Information (RFI's) in accordance with the present invention
  • Figure 7 illustrates a hierarchical diagram illustrating aggregation in accordance with the present invention.
  • FIG. 8 is a flowchart of a method for managing bids in accordance with the present invention.
  • FIG. 1 illustrates one embodiment of the present invention of a database system 100.
  • System 100 may comprise a plurality of clients 110A-F coupled to a server 130 via a network 120.
  • Network 120 may be a Local Area Network (LAN), e.g., Ethernet, Token Ring, ARCnet, or a Wide LAN, e.g., Ethernet, Token Ring, ARCnet, or a Wide LAN, e.g., Ethernet, Token Ring, ARCnet, or a Wide LAN
  • LAN Local Area Network
  • Server 130 may be configured to store and retrieve data, e.g., bid requests, responses to bid requests, to and from, respectively, a database 140.
  • Clients 110A-F may collectively or individually be referred to as clients 110 or client 110, respectively. It is noted that system 100 may comprise any number of clients 110 as well as any number of servers 130 and databases 140 and that Figure 1 is illustrative. It is further noted that the connection between client
  • client 110 and network 120 may be any medium type, e.g., wireless, wired.
  • client 110 may be any type of network access device, e.g., wireless, Personal Digital Assistant (PDA), cell phone, personal computer system, workstation, web terminal, Internet appliance, configured with the capability of connecting to network 120 by either a wired or wireless connection.
  • system 100 may be any type of system that has at least one server 130 and at least one client 110 and that Figure 1 is not to be limited in scope to any one particular embodiment.
  • FIG. 2 illustrates an embodiment of the present invention of server 130.
  • server 130 may comprise a central processing unit (CPU) 210 coupled to various other components by system bus 212.
  • An operating system 240 e.g., AIX, UNIX, runs on CPU 210 and provides control and coordinates the function of the various components of Figure 2.
  • Application 250 e.g., program for transmitting notifications as well as storing and retrieving requests and responses stored in database 140 as described in Figures 6 and 8, runs in conjunction with operating system 240 which implements the various functions to be performed by application 250.
  • Read only memory (ROM) 216 is coupled to system bus 212 and includes a basic input/output system (“BIOS”) that controls certain basic functions of server 130.
  • BIOS basic input/output system
  • RAM 214 Random access memory
  • I/O adapter 218 and communications adapter 234 are also coupled to system bus 212.
  • software components including operating system 240 and application 250 are loaded into RAM 214 which is the computer system's main memory.
  • I/O adapter 218 may be a small computer system interface ("SCSI") adapter that communicates with disk unit 220, e.g., disk drive.
  • SCSI small computer system interface
  • the program of the present invention that may transmit notifications as well as store and retrieve requests and responses in database 140 as described in Figures 6 and 8 may reside in disk unit 220 or in application 250.
  • Communications adapter 234 interconnects bus 212 with network 120 thereby enabling server 130 to communicate with client 110.
  • Implementations of the invention include implementations as a computer system programmed to execute the method or methods described herein, and as a computer program product.
  • sets of instructions for executing the method or methods are resident in the random access memory 214 of one or more computer systems configured generally as described above.
  • the set of instructions may be stored as a computer program product in another computer memory, for example, in disk drive 220 (which may include a removable memory such as an optical disk or floppy disk for eventual use in disk drive 220).
  • the computer program product can also be stored at another computer and stored or transmitted (or a portion thereof) when desired to the user's workstation or accessed by a user via a network or by an external network such as the Internet.
  • the physical storage of the sets of instructions physically changes the medium upon which it is stored so that the medium carries computer readable information. The change may be electrical, magnetic, chemical or some other physical change.
  • Figure 3 illustrates a typical hardware configuration of client 110 which is representative of a hardware environment for practicing the present invention. While the description below describes the internal connections in client 110 as hard wired it is understood by a person of ordinary skill that the connections may be wireless.
  • Client 110 has a central processing unit (CPU) 310 coupled to various other components by system bus 312.
  • An operating system 340 runs on CPU 310 and provides control and coordinates the function of the various components of Figure 3.
  • An application 350 in accordance with the principles of the present invention runs in conjunction with operating system 340 and provides output calls to operating system 340 where the output calls implement the various functions or services to be performed by application 350.
  • Application 350 may include for example, a program for managing bids, as described in Figures 4-8.
  • ROM 316 is coupled to system bus 312 and includes a basic input/output system (“BIOS”) that controls certain basic functions of client 110.
  • RAM random access memory
  • I/O adapter 318, and communications adapter 334 are also coupled to system bus 312.
  • software components including operating system 340 and application 350 are loaded into RAM 314 which is the computer system's main memory.
  • I/O adapter 318 may be an integrated drive electronics ("IDE") adapter that communicates with disk unit 320, e.g., disk drive.
  • IDE integrated drive electronics
  • Communications adapter 334 interconnects bus 312 with network 120 enabling client 110 to communicate with server 130.
  • Input/Output devices are also connected to system bus 312 via a user interface adapter 322 and display adapter 336.
  • Keyboard 324, mouse 326 and speaker 330 are all interconnected to bus 312 through user interface adapter 322.
  • Event data may be input to client 110 through any of these devices.
  • sets of instructions for executing the method or methods are resident in the random access memory 314 of one or more computer systems configured generally as described above.
  • the set of instructions may be stored as a computer program product in another computer memory, for example, in disk drive 320 (which may include a removable memory such as an optical disk or floppy disk for eventual use in the disk drive 320)
  • the computer program product can also be stored at another computer and transmitted when desired to the user's workstation by a network or by an external network such as the Internet
  • the physical storage of the sets of instructions physically changes the medium upon which it is stored so that the medium carries computer readable information The change may be electrical, magnetic, chemical, biological, or some other physical change
  • FIG. 4 is a hierarchical diagram 400 of the overall process for transmitting bids in accordance with the present invention
  • Hierarchical diagram 400 may illustrate users of clients 110, which are represented as circles, transmitting bids to users in different layers or levels of classification 411 A-D which are represented by the dashed lines
  • the levels of classification 411 A-D may refer to the stage the user(s) may be involved in the process of bidding on a particular project or portion thereof
  • level of classification 411 A may refer to the first stage in the bidding process
  • Level of classification 411 B may refer to the second stage in the bidding process
  • Level of classification 411C may refer to the third stage in the bidding process
  • Level of classification 411 D may refer to the fourth stage in the bidding process
  • Levels of classification may collectively or individually be referred to as levels of classification 411 or level of classification 411 , respectively
  • a single entity may engage in the bidding process at separate levels of classification 411 with respect to multiple bid requests relating to different projects or even the same project
  • hierarchical diagram 400 may further illustrate the flow of requests from one or more users at a next higher level of classification 411 to one or more users operating at a next lower level of classification 411 as indicated by arrows 421-434
  • hierarchical diagram 400 is illustrative and that the bidding process may comprise any number of stages, i e , any number of levels of classification 411 , involving any number of users, i e , each level of classification 411 may comprise any number of users
  • a bid request may generically refer to a request to bid on line ⁇ tem(s) but could refer to a request for proposal or quotation as those terms would be understood by a person of ordinary skill in the art
  • the bid request may include some or all of the documentation, e g , drawings, diagrams, specifications, instructions, agreements related to a specific line item or the request in general
  • the bid request may include a link, or other similar pointer to the documentation, or to portions thereof, rather than the documentation itself
  • the bid request may refer to the same or different projects where the line items in the bid request may be associated with different projects
  • hierarchical diagram 400 illustrates the transmission of bid requests from one or more users operating at a next higher level of classification 411 to one or more users operating at a next lower level of classification 411
  • the first stage of the bidding process may involve one or more users, e.g., owners, issuing one or more requests (hereinafter referred to as primary bid requests) to bid on one or more line items that need to be completed for a particular project to one or more other users.
  • a user involved in the first stage of the bidding process e.g. user 401 , may be said to be operating at a first level of classification (hereinafter referred to as the primary requester).
  • the second stage of the bidding process may involve one or more users, e.g., general contractors, receiving one or more requests to bid from a user operating at a first level of classification.
  • users 402A-B receive a request from user 401 as illustrated by arrows 421 and 422, respectively.
  • a user involved in the second stage of the bidding process may be said to be operating at a second level of classification.
  • Users, e.g., users 402A-B, operating at the second stage of the bidding process may import one or more of the line items contained in the primary bid request into one or more subsequent bid requests (hereinafter referred to as secondary bid requests) to one or more other users, e.g., subcontractors, operating at a next lower level of classification 411.
  • the one or more users that receive the secondary bid request may be said to be operating at a third level of classification as it is the third stage in the bidding process.
  • user 402A (hereinafter referred to as the secondary requester) may import one or more line items in the primary bid request into a secondary bid request to be transmitted to user 403A operating at the next lower level of classification 411C as illustrated by arrow 423.
  • user 402A may import one or more line items in the primary bid request into a secondary bid request to be transmitted to user 403B operating at the next lower level of classification 411C as illustrated by arrow 424.
  • user 402A may import one or more line items in the primary bid request into a secondary bid request to be transmitted to user 403C operating at the next lower level of classification 411C as illustrated by arrow 425.
  • user 402B may import one or more line items in the primary bid request into a secondary bid request to be transmitted to user 403B operating at the next lower level of classification 411C as illustrated by arrow 426.
  • arrows 427 and 428 represent secondary bid requests transmitted to users 403C and 403D, which may include one or more line items imported from the primary bid request.
  • users e.g., users 403A-D
  • users 403A-D operating at the third stage of the bidding process may import one or more of the line items contained in the secondary bid request into one or more subsequent bid requests (hereinafter referred to as tertiary bid requests) to one or more other users, e.g., sub-sub-contractors, operating at a next lower level of classification 411.
  • the one or more users that receive the tertiary bid request may be said to be operating at a fourth level of classification as it is the fourth stage in the bidding process.
  • user 403B may import one or more line items in the secondary request into a tertiary bid request to be transmitted to one or more of users 404A-F, e.g., 404A, 404D, operating at the next lower level of classification 411 D as illustrated by arrows 429 and 431.
  • user 403A may import one or more line items in the secondary request into a tertiary bid request to be transmitted to one or more of users 404A-F, e.g., 404B, operating at the next lower level of classification 411 D as illustrated by arrow 430.
  • user 403D may import one or more line items in the secondary request into a tertiary bid request to be transmitted to one or more of users 404A-F, e.g., 404C, 404E, 404F, operating at the next lower level of classification 411D as illustrated by arrows 432, 433 and 434, respectively.
  • hierarchical diagram 400 illustrates the flow of requests from one or more users operating at a next higher level of classification 411 to one or more users operating at a next lower level of classification 411.
  • hierarchical diagram 400 is illustrative and that the bidding process may comprise any number of stages, i.e., any number of levels of classification 411 , involving any number of users, i.e., each level of classification 411 may comprise any number of users. It is further noted that each user may issue any number of requests to bid to any number of users operating at a next lower level of classification. It is further noted that each user may issue what is commonly referred to as a Request For Information (RFI) related to a received bid request to the requester of that bid request as described in greater detail in the description of Figure 6. It is further noted that the line items in the bid requests may refer to the same or different projects. It is further noted that the line items in a particular bid request may be "aggregated" from two or more previously received bid requests that may refer to the same or different projects as described in greater detail in the description of Figure 7.
  • RFI Request For Information
  • FIG. 5 is a hierarchical diagram 500 of the overall process for responding to bid requests in accordance with the present invention.
  • Hierarchical diagram 500 has the same corresponding levels of classification 411 and users as in hierarchical diagram 400.
  • the levels of classification 411 may refer to the stage at which the user(s) may be involved in the process of bidding on a particular project or portion thereof. It is noted that a single entity may engage in the bidding process at separate levels of classification 411 with respect to multiple bid requests relating to different projects or even the same project.
  • hierarchical diagram 500 may further illustrate the flow of responses from one or more users operating at a next lower level of classification 411 to one or more users at a next higher level of classification 411 as indicated by arrows 521-534.
  • each user in a particular level of classification 411 may be a requester, i.e., transmit a request to one or more users operating at a lower level of classification 411.
  • Each requester may receive one or more responses to one or more requests transmitted.
  • the requester may then select data, e.g., price quotes, inputted by one or more users from the next lower level of classification related to one or more selected line items and import that selected data into a new response to be submitted to a requester operating at the next higher level of classification 411.
  • hierarchical diagram 500 is illustrative and that the bidding process may comprise any number of stages, i.e., any number of levels of classification 411 , involving any number of users, i.e., each level of classification 411 may comprise any number of users.
  • a bid request may generically refer to a request to bid on line item(s) but could refer to a request for proposal or quotation as those terms would be understood by a person of ordinary skill in the art.
  • the bid request may include some or all of the documentation, e.g., drawings, diagrams, specifications, instructions, agreements related to a specific line item or the request in general.
  • a request may include a link or links, or similar pointers to the documentation, or portions thereof.
  • the bid request may refer to the same or different project where the line items in the bid request may be associated with different projects.
  • Hierarchical diagram 500 illustrates the flow of responding to bid requests from one or more users operating at a next lower level of classification 411 to one or more users at a next higher level of classification 411.
  • users 404A-F at the fourth stage of the bidding process i.e., operating at a fourth level of classification 411 D, may receive a tertiary bid request from users 403A-D as illustrated by arrows 429-434 in Figure 4.
  • Users 404A-F may respond to a tertiary request by transmitting a response to one or more of the line items in a tertiary request to the tertiary requester, i.e., users 403A-D, as indicated by arrows 529-534.
  • Users may import data, e.g., price quotes, related to one or more selected line items in one or more responses to one or more tertiary bid requests submitted from one or more users operating at the next lower level of classification 411 , e.g., fourth level of classification 411 D, into one or more new responses to one or more secondary bid requests to be submitted to one or more secondary requesters operating at a next higher level of classification, e.g., second level of classification 411 B.
  • data e.g., price quotes
  • user 403B may import data, e.g., price quotes, related to one or more selected line items in the response to the tertiary bid request submitted by user 404A into one or more new responses to one or more secondary bid requests to be submitted to one or more secondary requesters, e.g., users 402A-B, operating at a next higher level of classification 411 as indicated by arrows 524 and 526.
  • users 403A, 403C and 403D may respond to one or more secondary requesters, e.g., users 402A-B, operating at a next higher level of classification as indicated by arrows 523, 525, 527 and 528, respectively.
  • users may simply respond to one or more of the one or more line items in the secondary bid request to the secondary requesters, e.g., users 402A-B, without importing any response from any user operating at the fourth level of classification.
  • Users e.g., users 402A-B, operating at the second level of classification 411 B, may import data, e.g., price quotes, related to one or more selected line items in one or more responses received from one or more users operating at the next lower level of classification 411 , e.g., third level of classification 411C, into one or more new responses to be submitted to one or more users operating at a next higher level of classification, e.g., first level of classification 411 A.
  • data e.g., price quotes
  • user 402A may receive a response from one or more of users 403A-C to its bid request, i.e., secondary bid request, on one or more line items in the secondary bid request as indicated by arrows 523, 524 and 525, respectively.
  • user 402B may receive a response from one or more users 403B-D to its bid request, i.e., secondary bid request, on one or more line items in the secondary bid request as indicated by arrows 526, 527 and 528, respectively.
  • Users 402A-B may decide to import data inputted by the sender on selected one or more line items into a response to be submitted to a primary requester operating at a next higher level of classification 411 , e.g., user 401.
  • user 402A may submit a secondary bid request comprising line item #1 from the primary bid request which corresponds to furnishing and installing one hundred windows of a particular type and size to user 403A.
  • User 402A also may submit a secondary bid request comprising line item #2 from the primary bid request which corresponds to furnishing and installing 10,000 square feet of a particular type of carpeting including the preparation of existing floor surfaces to user 403B.
  • User 402A may submit a secondary bid request comprising line item #3 from the primary bid request which corresponds to furnishing and delivering one hundred desks of a particular type and size to user 403C.
  • Users 403A, 403B and 403C may each respond by quoting a price to complete line items 1 , 2 and 3, respectively. User 402A may then import the data related to those line items in the responses received from users
  • 403A, 403B and 403C into its response to the primary bid request issued by the primary requester, operating at the next higher level of classification 411 , e.g., user 401, as indicated by arrow 521.
  • user 402B may then import data related to one or more selected line items in the responses received from users 403B, 403C and 403D into its response to the primary bid request issued by the primary requester, operating at the next higher level of classification 411 , e.g., user 401 , as indicated by arrow 522.
  • bid responses from users 403A, 403B and 403C to user 402A or from users 403B, 403C and 404D to user 402B may be "hidden.” That is, these responses may not be separately accessible to the requester operating at the next higher level of classification 411 , e.g., user 401.
  • hierarchical diagram 500 illustrates the flow of responses to bid requests from one or more users operating at a next lower level of classification 411 to one or more users operating at a next higher level of classification 411.
  • hierarchical diagram 500 is illustrative and that the bidding process may comprise any number of stages, i.e., any number of levels of classification 411 , involving any number of users, i.e., each level of classification 411 may comprise any number of users.
  • responses to bid requests may be responses related to the same or different projects.
  • a response may include data, e.g., price quotes, related to line items that may have been "aggregated" from two or more previously transmitted requests that may refer to the same or different projects as described in greater detail in the description of Figure 7.
  • each user responding may issue what is commonly referred to as a Request For Information (RFI), requesting further information related to the bid request transmitted by the requester as described in greater detail below.
  • RFI Request For Information
  • Figure 6 - Method for Managing Requests for Information Figure 6 is a flowchart of one embodiment of the present invention, which includes a method
  • an RFI may refer to a request for information related to a bid request received.
  • a particular user e.g., user 402A
  • the recipient e.g., user 403A
  • the recipient may desire further information related to the bid request in order to determine how or if to respond to the bid request.
  • the recipient e.g., user 403A, may then issue an RFI related to the received ' bid request back to the requester, e.g., user 402A, of the bid request.
  • Method 600 is a method for managing such RFIs as discussed below.
  • a determination by a particular user may be made as to whether to issue an RFI to a particular user operating at a next higher level of classification, e.g., user 402A, in connection with a request previously received from that particular requester, e.g., user 402A. If the particular user, e.g., user 403A, determines not to issue an RFI then the particular user, e.g., user 403A, does not issue an RFI at step 602.
  • the particular user e.g., user 403A
  • determines to issue an RFI to a user operating at a next higher level of classification e.g., user 402A
  • the particular user may transmit the RFI from one of the clients 110, to be stored on at least one server 130.
  • the issuer of the RFI may issue the RFI by transmitting the RFI from the client 110 that corresponds to the issuer of the RFI, via network 120, to at least one of server 130 ( Figure 1).
  • step 640 system notifies the requester corresponding to the bid request, e.g., user 402A, that the RFI is available to be accessed.
  • the requester determines whether or not to access the RFI in step 641. If the requester determines in step 641 not to access the RFI, then the process ends at step 642. Otherwise, if the requester determines in step 641 to access the RFI, then in step 604 the requester receives the RFI via network 120, from server 130.
  • the particular user may determine whether to respond to the RFI received in step 604. If the particular user, e.g., user 402A, determines not to respond, then the particular user, e.g., user 402A, does not respond in step 606. If the particular user, e.g., user 402A, determines to respond, then a determination may be made in step 607 as to whether the particular user, e.g., user 402A, prepares its response and identifies one or more users operating at a next lower level of classification 411 authorized to access the response.
  • the particular user e.g., 402A
  • the particular user e.g., user 402A
  • the particular user identifies such one or more users operating at the third level of classification who are authorized to access the response and transmits the response to the RFI from the client 110, via the network, to at least one server 130 in step 608.
  • the particular user e.g., user 402A
  • the particular user may determine whether to modify the RFI in step 609. If the particular user, e.g., user 402A, determines not to modify the RFI then the particular user, e.g., user 402A, may submit the RFI to a user operating at a next higher level of classification, e.g., user 401 , in connection with a request previously received from that user, e.g., user 401 , in step 610.
  • the particular user e.g., user 402A
  • the RFI is transmitted from the client 110 that corresponds to such user, e.g. user 402A, via network 120, to at least one of server 130.
  • the particular user e.g., user 402A
  • the particular user may modify the RFI accordingly in step 611.
  • "to modify" a RFI contemplates that a particular user, e.g., user 402A, creates a new RFI in step 601 and imports selected data from the RFI received from a user operating at a next lower level of classification, e.g., user 403A, in step 604.
  • the particular user, e.g., user 402A may add, delete or edit the imported data.
  • the database system may maintain each RFI, e.g., RFI received by user 402A, in its unaltered form so as to maintain a record of all communications between users at each level of classification 411 with respect to each bid request.
  • RFI e.g., RFI received by user 402A
  • user 403A as a recipient of a secondary bid request, may issue an RFI to user 402A as the secondary requester seeking additional information about the supports for light fixtures to be installed when the drawings included with the secondary bid request show that the air distribution system prevents a direct connection to the structure above.
  • user 402A may modify the RFI issued by user 403A to include a further inquiry related to the design of the air handling system prior to transmitting the RFI to user 401.
  • the particular user e.g., user 402A
  • step 647 system notifies the requester corresponding to the bid request, e.g., user 401 , that the RFI is available to be accessed.
  • the requester determines whether or not to access the RFI in step 648. If the requester determines in step 648 not to access the RFI, then the process ends at step 649. Otherwise, if the requester determines in step 648 to access the RFI, then in step 613 the requester receives the RFI via network 120, from a server 130.
  • the particular user may receive the modified RFI transmitted in step 612 or the unmodified RFI transmitted in step 610.
  • the particular user e.g., user 401
  • the particular user may determine whether to respond. If the particular user, e.g., user 401 , that received the RFI in step 613 determines not to respond, then the particular user, e.g., user 401 , may not respond in step 615.
  • the particular user e.g., user 401
  • the particular user may prepare its response and identify the one or more users operating at a next lower level of classification, e.g., user 402A, authorized to access the response in step 616, and the response is submitted by transmitting the response from the client 110 that corresponds to such user, e.g., user 401 , via network 120, to at least one of server 130.
  • a next lower level of classification e.g., user 402A
  • a user other than a primary requester may issue an RFI to a requester at a next higher level of classification 411 , by initiating a sub-process that performs step 601 and step 603.
  • step 650 system notifies the user submitting the RFI, e.g., user 402A, that the response to the RFI is available to be accessed.
  • the user submitting the RFI determines whether or not to access the response to the RFI in step 651. If the user submitting the
  • step 651 determines in step 651 not to access the response to the RFI, then the process ends at step 652. Otherwise, if the user submitting the RFI determines in step 651 to access the response to the RFI, then in step 617 the user submitting the RFI receives the response via network 120, from a server 130. In step 617, one or more users, e.g., user 402A, operating at a next lower level of classification 411 that are authorized to receive the response prepared and transmitted in step 616 may receive the response.
  • users e.g., user 402A, operating at a next lower level of classification 411 that are authorized to receive the response prepared and transmitted in step 616 may receive the response.
  • the one or more users operating at a next lower level of classification 411 authorized to receive the response in step 616 may or may not include the user, e.g., user 402A, that transmitted the RFI in step 610 or modified RFI in step 612.
  • the one or more users, e.g., user 402A, operating at a next lower level of classification 411 that received the response in step 617 may determine whether to forward the response. If one or more users, e.g., user 402A, operating at a next lower level of classification 411 that received the response in step 617 determined not to forward the response, then those one or more users, e.g., user 402A, may not forward the response in step 619. If one or more users, e.g., user 402A, operating at a next lower level of classification 411 that received the response in step 617 determine to forward the response, then a determination may be made as to whether to modify the response in step 620.
  • those one or more users may forward the response to one or more users, e.g., user 403A, operating at a next lower level of classification 411 in step 621.
  • the one or more users, e.g., user 402A, that determined to forward the response in step 618 determined to modify the received response may modify the received response in step 622.
  • a particular user, e.g. user 402A may create a new response as in step 611 and import selected data from the response received from a user at the next higher level of classification, e.g. user 401.
  • the particular user, 402A may then add to, delete from, or otherwise edit the imported data.
  • the database system maintains each response in its unaltered form so as to maintain a record of all communications between users at each level of classification 411 with respect to each bid request.
  • the one or more users, e.g., user 402A, that modified the response in step 622 may submit the modified response to one or more users, e.g., user 403A, operating at a next lower level of classification 411.
  • step 644 system notifies one or more users operating at the third level of classification authorized to access the response to the RFI, e.g., user 403A, that a response to an RFI is available for access.
  • the requester determines whether or not to access the RFI in step 645. If the requester determines in step 645 not to access the RFI, then the process ends at step 646. Otherwise, if the requester determines in step 645 to access the RFI, then in step 624 the requester receives the RFI via network 120 from a server 130.
  • the one or more users e.g., user 403A, operating at a next lower level of classification 411 may receive the forwarded response transmitted in step 621 or the modified response transmitted in step 623.
  • the one or more users may determine whether to issue an additional RFI. If one or more users, e.g., user 403A, operating at a next lower level of classification 411 that received the response in step 624, determine to issue an additional RFI, then those users, e.g., user 403A, may transmit an additional RFI in step 603.
  • one or more users e.g., user 403A, operating at a next lower level of classification 411 that received the response in step 624, determine not to issue an additional RFI, then those users, e.g., user 403A, may import the response received in step 624 into one or more responses to one or more requests that may be submitted to one or more users, e.g., user 404, associated at a next lower level of classification 411 in step 626.
  • FIG. 7 Hierarchical Diagram of Aggregation
  • Figure 7 illustrates an embodiment of the present invention of a hierarchical diagram 700 illustrating aggregation.
  • Hierarchical diagram 700 illustrates the flow of issuing and responding to aggregated bid requests between users of clients 110, which are represented as circles, within three levels of classification, e.g., levels of classification 411 B-D, as indicated by the dashed lines in Figure 7.
  • the transfer of requests and responses illustrating aggregation may be represented by arrows 721- 728 in Figure 7.
  • the levels of classification 411 may refer to the stage the user(s) may be involved in the process of bidding on a particular project.
  • Hierarchical diagram 700 may illustrate any three particular levels of classification 411 and that each level of classification 411 may comprise any number of users.
  • aggregated requests and responses to aggregated requests may be transmitted through one or more users operating over multiple levels of classification 411.
  • a user operating in a second level of classification 411 B may issue an aggregated request to one or more users operating in a third level of classification 411C that may further issue the aggregated request or a portion thereof to one or more users operating at the next lower level of classification, e.g., level of classification 411 D, and so forth.
  • the responses to the aggregated request(s) may be transmitted to the requester(s) through a similar process.
  • the line items aggregated as discussed below may be associated with the same or different projects.
  • Hierarchical diagram 700 illustrates transmitting an aggregated bid request to one or more users operating in a next lower level of classification 411.
  • An aggregated bid request may refer to aggregating line items in two or more received requests related to the same or different projects into one or more new requests to be transmitted to one or more users operating at a next lower level of classification. These new requests may be referred to as "aggregated bid requests.”
  • An aggregated bid request may include some or all of the documentation, e.g., drawings, diagrams, specifications, instructions, agreements, related to a specific line item or the requests in general.
  • an aggregated bid request may include links, or similar such pointers to the documentation or portions thereof.
  • hierarchical diagram 700 illustrates one or more users, e.g., users 701 A, 701 B, in a particular level of classification 411 , e.g., level of classification 411 B, issuing one or more bid requests to one or more users, e.g., user 702, operating in a next lower level of classification 411 , e.g., level of classification 411 C.
  • user 701 A operating at level of classification 411 B may submit a bid request that includes line items 1, 3 and 5 related to project #1 to user 702 operating at the next lower level of classification 411 , i.e., level of classification 411C, as indicated by arrow 721.
  • Line item #1 may correspond to furnishing and installing one hundred desk chairs of a particular type and size.
  • Line item #3 may correspond to furnishing and delivering one hundred desks of a particular type and size.
  • Line item #5 may correspond to furnishing and installing one hundred windows of a particular type and size.
  • User 701 B operating at level of classification 411 B may submit a bid request that includes line items 2, 4, 6 and 8 related to project #2 to user 702 operating at the next lower level of classification 411 , i.e., level of classification 411C, as indicated by arrow 722.
  • Line item #2 may correspond to furnishing and delivering one hundred conference room chairs of a particular type and size.
  • Line item #4 may correspond to furnishing and installing 10,000 square feet of a particular type of carpeting including the preparation of existing floor surfaces.
  • Line item #6 may correspond to furnishing and installing one hundred blinds of a particular type and size.
  • Line item #8 may correspond to furnishing and delivering fifty desks of a particular type and size.
  • Hierarchical diagram 700 further illustrates one or more users, e.g., user 702, issuing aggregated bid requests to be transmitted to one or more users operating at a next lower level of classification, i.e., aggregating line items in two or more received requests related to the same or different projects into one or more new requests to be transmitted to one or more users operating at a next lower level of classification.
  • user 702 may aggregate one or more line items in the bid requests received from users 701A and 702B as identified by arrows 721 and 722, respectively.
  • User 702 may aggregate line items 1 and 3 related to project #1 in the bid request received from user 701 A with line items 2 and 8 related to project #2 in the bid request received from user 701 B by importing selected data, e.g., description of goods, quantities, on the selected line items from such bid requests into an aggregated bid request to be transmitted to user 703A operating at a next lower level of classification 411 , i.e., level of classification 411 D, as identified by arrow 723.
  • selected data e.g., description of goods, quantities
  • User 702 may further aggregate line item 5 related to project #1 in the bid request received from user 701 A with line items 4 and 6 related to project #2 in the bid request received from user 701 B by importing selected data, e.g., description of goods, quantities, on the selected line items from such bid requests into an aggregated bid request to be transmitted to user 703B operating at a next lower level of classification 411 , i.e., level of classification 411 D, as identified by arrow 724.
  • selected data e.g., description of goods, quantities
  • Hierarchical diagram 700 further illustrates selecting and importing data, e.g., price quotes, on selected line item(s) in responses to the transmitted aggregated bid request(s) into one or more responses to be submitted to one or more requesters operating at a next higher level of classification 411.
  • user 703A may submit a response to the received aggregated bid request, e.g., bid request on line items 1 and 3 for project #1 and line items 2 and 8 for project #2, to user 702 that issued the aggregated bid request as indicated by arrow 725.
  • User 703B may submit a response to the received aggregated bid request, e.g., bid request on line item 5 for project #1 and line items 4 and
  • User 702 may import selected data, e.g., price quotes, on selected line item(s) into one or more responses to be submitted to one or more requesters operating at a next higher level of classification 411.
  • user 702 may import data, e.g., price quotes, on selected line item(s), e.g., line items 1 and 3 related to project #1 , from the response submitted by user 703A as indicated by arrow 725 and import data, e g , price quotes, on selected line ⁇ tem(s), e g , line item 5 related to project #1 , from the response submitted by user 703B as indicated by arrow 726 into a response to be submitted to user 701 A as indicated by arrow 727
  • User 702 may transmit the response that includes the response to line items 1 , 3 and 5 related to project #1 to user 701 A since user 701 A had previously transmitted a bid request that included line items 1 , 3 and 5 related to project #1 to user 702
  • User 702 may transmit the response that includes the response to
  • 702 may import selected data, e g , price quotes, on selected line ⁇ tem(s), e g , line items 2 and 8 related to project #2, from the response submitted by user 703A as indicated by arrow 725 and import selected data, e g , price quotes, on selected line ⁇ tem(s), e g , line items 4 and 6 related to project #2, from the response submitted by user 703B as indicated by arrow 726 into a response to be submitted to user 701 B as indicated by arrow 728
  • User 702 may transmit the response that includes the response to line items 2, 4, 6 and 8 related to project #2 to user 701 B since user 701 B had previously transmitted a bid request that included line items 2, 4, 6 and 8 related to project #2 to user 702
  • FIG 8 - Flowchart of a Method for Managing Bids Figure 8 is a flowchart of one embodiment of the present invention of a method 800 for managing bids
  • a recipient of a bid request may need to sub-contract some or all of those line items in the request to other entities That is, the recipient of the bid request may have to become a requester itself and issue a bid request on all or a portion of those items in the request received
  • a recipient may receive multiple bid requests
  • These multiple requests may comprise line items as well as the accompanying documentation, e g , agreements, drawings, that need to be sub-contracted
  • the recipient may desire to aggregate line items and the accompanying documentation from multiple requests into a new bid request to sub-contractors
  • requests may include links or similar such pointers to the documentation as an alternative to the documentation files themselves It would therefore be desirable to develop a tool that allows a recipient of a bid request to submit one or more bid requests
  • a requester operating at a first level of classification 411 may prepare one or more primary bid requests to be transmitted to one or more users operating at a second level of classification, e.g., general contractors, via network 120 ( Figure 1).
  • a primary bid request may comprise a plurality of line items to be accomplished and related documentation, e.g., drawings, agreements, if any.
  • Each line item may represent a particular task, e.g., installing windows, in order to complete a particular project, e.g., construction of a building.
  • a primary bid request may also identify one or more users operating at a second level of classification 411 who are authorized to access such request.
  • a primary bid request may be transmitted from one of the clients 110 and stored on at least one server 130.
  • the primary bid requester e.g., user 401 ( Figure 4)
  • step 802 system notifies one or more authorized users operating at a second level of classification to access the primary bid request that a primary bid request is available to be accessed.
  • one or more authorized users operating at a second level of classification to access the primary bid request determines whether or not to access the primary bid request in step 803. If one or more authorized users operating at a second level of classification determines in step
  • step 803 not to access the primary bid request, then the process ends at step 804. Otherwise, if one or more authorized users operating at a second level of classification determines in step 803 to access the primary bid request, then in step 805 the bid request is transmitted to the authorized user by a server 103. (For purposes herein, transmission from a server to a user may also be referred to as "downloading.") As a result of an evaluation of the bid request, in step 806, the one or more users that access the primary bid request determines whether to respond to the request. If one of the one or more users operating at the second level of classification that accessed the system in step 803 determines not to respond, then step 806 proceeds by the "NR" branch to step 807.
  • step 863 any one or more users operating at a second level of classification that determines in step 807 not to submit a response, selectively transmits a notification of its intent not to submit a response to the primary bid request.
  • step 863 may be performed asynchronously, that is, may be selectively initiated by user input 864, and may not be performed until user input is received.
  • Process 800 terminates as to that user in step 863 with no response.
  • step 806 proceeds by the "R" branch.
  • any one or more users operating at a second level of classification that determines in step 806 to submit a response selectively transmits a notification to the primary requester of its intent to submit a response to the primary bid request.
  • step 808 may be performed asynchronously, that is, may be selectively initiated by user input 860, and may not be performed until user input is received.
  • a user operating at a second level of classification e.g., user 402A ( Figure 4)
  • receiving the primary bid request may also determine whether to respond directly to the primary bid request or to issue one or more secondary bid requests to one or more users operating at a third level of classification.
  • a response may be generated to one or more of the line items of the primary bid request and transmitted to at least one server 130.
  • the recipient of the primary bid request e.g., user 402A
  • the transmission may be to a server, such as, server 130, via network 120.
  • the system transmits notification to the primary requester that one or more authorized users operating at a second level of classification have submitted a response to the primary requester, e.g., user 401.
  • the primary requester accesses the system from a client, e.g., a client 110 that corresponds to user 401 , via network 120.
  • a recipient of the primary bid request determines to issue one or more secondary bid requests
  • step 813 it determines whether or not to aggregate one or more of the one or more line items contained in primary bid requests into one or more secondary bid requests. If the recipient of the primary bid request, e.g., user 402A, determines not to aggregate in step 813, then in step 814 one or more secondary bid requests may be generated containing one or more of the one or more line items contained in the primary bid request and authorize one or more other users operating at a third level of classification, e.g., sub-contractors, to access one or more of the secondary bid requests.
  • a third level of classification e.g., sub-contractors
  • one or more secondary bid request may be prepared containing one or more of the one or more line items contained in more than one primary bid request and authorize one or more other users operating at a third level of classification, e.g., sub-contractors, to access one or more of the secondary bid requests.
  • the system notifies the one or more users operating at the third level of classification authorized by the secondary requester, e.g., user 402A, to access one or more secondary bid requests, via the network 120, that such one or more secondary bid requests are available for access.
  • a secondary bid request prepared in a corresponding one of steps 814 or step 815 may include documentation, e.g., agreements, drawings, related to the line item(s) or the secondary bid request in general, which were selected and imported from one or more primary bid requests or attached by the secondary requester.
  • One or more authorized users operating at a third level of classification determines whether or not to access the secondary bid request in step 817. If one or more authorized users in a third level of classification determines in step 817 not to access the secondary bid request, then the process ends at step 818. Otherwise, if one or more authorized users operating at a third level of classification determines in step 817 to access the secondary bid request, then in step 840 the bid request is downloaded to the authorized user by a server 130. In response to an evaluation of the bid request, in step 819, the one or more users that access the secondary bid request determines whether to respond to the request.
  • step 819 proceeds by the "NR" branch to step 820.
  • step 865 any one or more users operating at a third level of classification that determines in step 820 not to submit a response, selectively transmits a notification of its intent not to submit a response to the secondary bid request
  • step 865 may be performed asynchronously, that is, may be selectively initiated by user input 866, and may not be performed until user input is received
  • Process 800 terminates as to that user in step 865 with no response
  • step 819 proceeds by the "R" branch
  • step 821 any one or more users operating at a third level of classification that determines in step 819 to submit a response, selectively transmits a notification to the secondary requester of its intent to submit a response to the secondary bid request
  • a user operating at a third level of classification e g , user 403A ( Figure 4)
  • receiving the secondary bid request also determines whether to respond directly to the secondary bid request or to issue one or more tertiary bid requests to one or more users operating at a fourth level of classification
  • the recipient of the secondary bid request e g , user 403A
  • determines not to issue any tertiary bid request on one or more of the one or more line items contained in the secondary bid request then in step 823, a response may be generated to one or more of the line items of the secondary bid request and the response uploaded to at least one server 130
  • the recipient of the secondary bid request, e g , user 402A may submit a response by transmitting pricing, delivery, warranty, general terms and conditions, documentation and other information relating to one or more of the one or more line items contained in the secondary bid request to the secondary requester
  • the transmission may be to a server, such as, server 130, via network 120, Figure 1
  • a server such as,
  • a recipient of the secondary bid request e g , user 403A determines to issue one or more tertiary bid requests
  • step 822 it determines whether or not to aggregate one or more of the one or more line items contained in one or more secondary bid requests into one or more tertiary bid requests
  • the recipient of the secondary bid request e g , user 403A
  • step 827 one or more tertiary bid requests may be generated containing one or more of the one or more line items contained in the secondary bid request and authorize one or more other users operating at a fourth level of classification, e g , sub-contractors, to access one or more of the tertiary bid requests
  • the recipient of the secondary bid request determines to aggregate in step 822, then in step 826 it prepares one or more tertiary bid requests containing one or more of the one or more line items contained in more than one secondary bid request and authorizes one or more other users operating at a fourth level of classification, e g , sub-sub-contractors, to access one or more of the tertiary bid requests
  • the system notifies the one or more authorized users operating at the fourth level of classification authorized by the tertiary requester, e.g., user 403A, to access one or more tertiary bid requests, via the network 120, that such one or more tertiary bid requests are available for access.
  • a tertiary bid request prepared in a corresponding one of steps 826 or step 827 may include documentation, e.g., agreements, drawings, related to the line item(s) or the tertiary bid request in general, which were selected and imported from one or more secondary bid request or attached by the tertiary requester.
  • process 800 the process steps through three levels of classification have been illustrated. However, it would be recognized that corresponding process steps may be replicated through any number, n, of levels of classification in accordance with the present inventive principles. Additionally the terminology primary, secondary and tertiary are not intended to be limiting as to cardinality and other terms may be used to denote levels of classification.
  • a secondary requestor accessing the system may then respond to the primary request in view of the responses to the secondary request generated, in step 823, by one or more authorized users operating at a third level of classification.
  • a response by a secondary user may be generated in accordance with subprocess 850. Note that a particular user may have a plurality of subprocess 850, corresponding to a submission of bid responses to a plurality of bid requests which need not, necessarily, be related.
  • an analysis tool may indicate the lowest combination for all line items derived from all responses imported into the analysis tool. Additionally, the analysis tool may provide an indicator of the lowest value for each line item attribute, for example, lowest unit price, lowest aggregated price, lowest labor costs, etc.
  • step 829 responses are selected for analysis, in step 830 the responses selected in step 829 are analyzed.
  • step 831 may be a switch statement.
  • the secondary user may select to generate a secondary response to the primary bid request by importing selected data from the response from the user operating at a third level of classification. Otherwise, user, in step 831 B may selectively import selected data from a response from a user at a third level of classification into an existing secondary response. If, the secondary user selects either of these, in step 832, such user determines if the response to the primary bid request is to be submitted.
  • step 833 a notification is transmitted to the requestor of the primary bid request corresponding to the response being generated, similarly to step 811 , discussed hereinabove.
  • step 834 the response to the primary bid request generated by the user at the second level of classification is uploaded to the system. Note that once a response has been submitted, it may not be unilaterally retracted. A response submitted by a user at a particular level of classification, in accordance with the principles of the present invention, may "roll up" into bid responses at each higher level of classification. Consequently, a retraction of a response at a particular level, may affect responses at each higher level of classification. A response may be recalled only if such recall is approved by the corresponding requester at each higher level of classification. If the recall of a response is approved, the response may be maintained in the system, with a status of "Recalled.”
  • step 835 a determination is made if the current subprocess 850 is to be exited. Recall, as discussed hereinabove, that a particular user may be responding to a multiplicity of requests, and a subprocess 850 may be spawned with respect to each of these. If, in step 835, the current subprocess 850 is to be exited, step 835 proceeds by the "Yes" branch and the subprocess 850 exists, step 839. The user may subsequently re-enter to subprocess 850, step 837, to continue generating a response. Otherwise, step 835 proceeds by the "No" branch and the subprocess 850 returns to step 825 at step 836 to access additional responses, if any.
  • step 831 if, in three-way decision block 831 , the user has selected neither to generate secondary response and import a response (step 831 A), nor to import a response into an existing secondary response (step 831 B), then three-way decision block 831 proceeds to step 835, and the user may selectively exit the subprocess, or return to step 825, as previously described.
  • step 828 if it is determined not to import responses accessed in step 825 into the analysis tool, the secondary user may view the responses, step 836. Then subprocess 850 proceeds to three-way decision block 831 , and the secondary user may selectively generate a response and import, or may import a response into an existing secondary response, or neither, as previously described.
  • Process 800 including subprocess 850 has been discussed hereinabove in conjunction with the submission of bid requests and responses thereto.
  • users at any level of classification may change elements of a request any particular user initially submitted. Such changes may be referred to as an addendum or addenda and submission of such addenda and responses thereto, may performed by the analogous process steps of methodology 800.
  • method 800 may be executed in a different order presented and that the order presented in the discussion of Figure 8 is illustrative. It is further noted that certain steps may be executed almost concurrently.

Abstract

L'invention concerne un procédé, un produit-programme informatique et un système de gestion de soumissions. Une demande de soumission (421-422) peut être transmise à un destinataire (402A-B), qui peut lui-même devenir un demandeur de soumission, ce qui lui permet de soumettre une ou plusieurs demandes de soumission (423-428) à d'autres entités (403A-D). Le terme demande de soumission peut désigner l'ensemble des invitations à faire une soumission sur un ou plusieurs articles. Un destinataire d'une ou plusieurs demandes de soumission peut ensuite être autorisé à réunir un ou plusieurs articles et la documentation d'accompagnement, par exemple des accords et des figures le cas échéant, se trouvant dans la ou les demandes reçues, au sein d'une ou de plusieurs nouvelles demandes à soumettre à d'autres entités. De plus, un destinataire d'une ou plusieurs réponses à une ou plusieurs demandes de soumission peut importer des données relatives à un ou plusieurs articles se trouvant dans une ou plusieurs réponses reçues dans une ou plusieurs nouvelles réponses à soumettre à d'autres entités.
PCT/US2001/026967 2001-07-25 2001-08-30 Outil de gestion de soumissions WO2003012718A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/484,372 US20040210490A1 (en) 2001-08-30 2001-08-30 Tool for managing bids

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US30775101P 2001-07-25 2001-07-25
US60/307,751 2001-07-25

Publications (1)

Publication Number Publication Date
WO2003012718A1 true WO2003012718A1 (fr) 2003-02-13

Family

ID=23191031

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/026967 WO2003012718A1 (fr) 2001-07-25 2001-08-30 Outil de gestion de soumissions

Country Status (1)

Country Link
WO (1) WO2003012718A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5243515A (en) * 1990-10-30 1993-09-07 Lee Wayne M Secure teleprocessing bidding system
US5826244A (en) * 1995-08-23 1998-10-20 Xerox Corporation Method and system for providing a document service over a computer network using an automated brokered auction
US6014644A (en) * 1996-11-22 2000-01-11 Pp International, Inc. Centrally coordinated communication systems with multiple broadcast data objects and response tracking
WO2001040905A2 (fr) * 1999-12-06 2001-06-07 Webusiness Usa, Inc. Gestion de cotation de commerce electronique et achats automatises

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5243515A (en) * 1990-10-30 1993-09-07 Lee Wayne M Secure teleprocessing bidding system
US5826244A (en) * 1995-08-23 1998-10-20 Xerox Corporation Method and system for providing a document service over a computer network using an automated brokered auction
US6014644A (en) * 1996-11-22 2000-01-11 Pp International, Inc. Centrally coordinated communication systems with multiple broadcast data objects and response tracking
WO2001040905A2 (fr) * 1999-12-06 2001-06-07 Webusiness Usa, Inc. Gestion de cotation de commerce electronique et achats automatises

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
DATABASE GALEGROUP TRADE&INDUSTRY [online] 2 August 2000 (2000-08-02), "BuildPoint announces sharp increase in adoption and use of its online project bidding service by commercial contractors", XP002949298, Database accession no. 63814658 *
DATABASE GALEGROUP TRADE&INDUSTRY [online] 30 May 2000 (2000-05-30), "RedLadder.com improves the contractor's bid process, initiates easy online bidding with quickbid 2.0", XP002949297, Database accession no. 62446689 *

Similar Documents

Publication Publication Date Title
US8266015B2 (en) Inventory sales system and method
US20020077939A1 (en) Item specification object management system
US8103694B1 (en) System and method for managing data in multiple bills of material over a network
JP2701234B2 (ja) 電子的注文システム及び方法
US20140222495A1 (en) Dynamic workflow approvals
US20040210490A1 (en) Tool for managing bids
US20110225062A1 (en) Method and apparatus for efficiently responding to electronic requests for quote
US20120271729A1 (en) Method and System for Managing Sourcing Program Requests
JP2007536627A (ja) 電子カタログのサプライヤ・ポータルのためのシステムおよび方法
US20020107818A1 (en) System and method for expression-based pricing
WO2001067279A2 (fr) Systeme transactionnel integre de conception, execution et gestion de projets
US8914352B2 (en) Non-equijoin metadata
WO2001020530A1 (fr) Procede et systeme pour le traitement de decisions sur un reseau et pour l'adaptation des demandes de propositions aux resultats
US8249938B2 (en) Fuzzy evaluation of responses to provide degree of satisfaction
US20060041496A1 (en) Method and system for automating proposals involving direct and indirect sales
US20090063240A1 (en) Routing transactions in a multiple job environment using an approval framework
US7620575B1 (en) Locally generating price quotes using one or more pricing tools received from a seller
US20170161809A1 (en) Procurement recommendation system
US20070140222A1 (en) Facilitating the exchange of a position on a waiting list
US20230419387A1 (en) User-Specific Rule-Based Database Querying
US7792750B2 (en) Submitting requests with degrees of satisfaction to be used for fuzzy evaluation of responses
WO2003012718A1 (fr) Outil de gestion de soumissions
WO2001008067A1 (fr) Systeme et procede de transaction en reseau
Ben-Arieh et al. Web-based cost estimation of machining rotational parts
US7437314B2 (en) Method and system for referencing trading agreements

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

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

Kind code of ref document: A1

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

AL Designated countries for regional patents

Kind code of ref document: A1

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

Kind code of ref document: A1

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

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 10484372

Country of ref document: US

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP