US20080027831A1 - Virtual warehouse parts distribution system and process - Google Patents
Virtual warehouse parts distribution system and process Download PDFInfo
- Publication number
- US20080027831A1 US20080027831A1 US11/867,377 US86737707A US2008027831A1 US 20080027831 A1 US20080027831 A1 US 20080027831A1 US 86737707 A US86737707 A US 86737707A US 2008027831 A1 US2008027831 A1 US 2008027831A1
- Authority
- US
- United States
- Prior art keywords
- parts
- buyer
- accordance
- inventory
- seller
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
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/0601—Electronic shopping [e-shopping]
- G06Q30/0603—Catalogue ordering
-
- 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
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- 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
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
-
- 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/0601—Electronic shopping [e-shopping]
- G06Q30/0613—Third-party assisted
- G06Q30/0617—Representative agent
-
- 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/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
Definitions
- This invention relates generally to the distribution of spare parts and more particularly to a system and method of using a computer network such as the Internet to facilitate spare part distribution.
- Aircraft are routinely subject to various maintenance operations as part of their normal operation. Aircraft engines in particular have many components that periodically need to be replaced, on a scheduled or unscheduled basis. As is the case for many types of equipment, spare parts for aircraft engines are available from a wide variety of sources. For example, newly manufactured parts can be obtained from vendors or original equipment manufacturers (OEMs) that produce the parts. Used parts can be obtained from overhaul and repair shops or engine operators such as airlines.
- OEMs original equipment manufacturers
- site excess i.e., unused parts previously obtained by a repair site or engine operator but no longer needed by that entity
- site rotables i.e., used or unused parts kept on hand by service shops to be used in place of a customer's parts while those parts are being repaired
- the above-mentioned need is met by the present invention which provides a network-based parts distribution system and process.
- the system includes a plurality of buyer computers for operation by a system participant desiring to obtain one or more parts, a plurality of seller computers for operation by a system participant desiring to sell one or more parts, and at least one server computer.
- the buyer computers, seller computers and server computer are interconnected as a computer network.
- the seller computers are used to input part related data to the server computer, and the server computer uses the data to maintain a database of all available parts.
- the buyer computers are used to transmit part requests to the server computer, and the server computer selecting one or more parts from the database in response to the requests.
- FIG. 1 is a schematic view of a virtual warehouse parts distribution system.
- FIG. 2 graphically illustrates a matrix representing one inventory category from the database of the virtual warehouse parts distribution system.
- FIG. 3 graphically illustrates a parts selection process of the present invention.
- FIG. 1 shows a virtual warehouse parts distribution system 10 .
- the system 10 includes at least one central server computer 12 , a plurality of buyer computers 14 operated by system participants interested in obtaining parts (referred to herein as buyers), and a plurality of seller computers 16 operated by system participants wishing to sell parts (referred to herein as sellers).
- buyers system participants interested in obtaining parts
- sellers system participants wishing to sell parts
- a system participant could participate as both a buyer and a seller.
- many organizations concerned with aircraft engine repair, such as overhaul shops and engine operators can experience both excesses and shortages of various parts. Such an organization would be interested in participating in the system 10 to sell excess parts and buy parts that are in short supply.
- the server computer 12 , the buyer computers 14 and the seller computers 16 are all interconnected via a computer network 18 and can thus be geographically dispersed on a regional, national or worldwide basis.
- the network 18 is preferably the Internet, although it is possible to employ other types of computer networks such as a local area network or a wide area network.
- the buyer computers 14 and the seller computers 16 which may be conventional workstations, personal computers, or the like, are client computers that include a conventional Web browser software application.
- the browser allows the computer 14 , 16 to access Hypertext Markup Language (HTML) Web pages and other data stored on the server computer 12 or any other server systems connected to the network 18 .
- HTML Hypertext Markup Language
- the present invention is not limited to the use of HTML; other suitable languages may be substituted within the scope of the present invention.
- the system 10 may also include firewall protection (not shown) to prevent non-system participants from gaining access thereto.
- the server computer 12 which could comprise a cluster of server computers, includes a Web server 20 (i.e., a computer program that serves requested HTML pages or files) for communicating with the buyer computers 14 and the seller computers 16 , and a parts inventory database 22 .
- the database 22 contains a list of all the parts that the various sellers participating in the system 10 are willing to sell, and thus represents a pool of all the parts available for purchase via the system 10 .
- the server computer 12 is programmed to receive data relating to the available parts and uses the data to maintain the database 22 .
- the server computer 12 is also programmed to receive requests for parts from prospective buyers and subsequently search the database 22 for such parts.
- the operation of the system 10 comprises two primary processes: a database creation and maintenance process and a part selection process.
- a database creation and maintenance process prospective sellers willing to sell one or more parts utilize the seller computers 16 to upload data corresponding to the parts to the server computer 12 .
- the server computer 12 processes the data and adds the parts to the database 22 in a sorted fashion.
- the database 22 is continually updated in this fashion as newly available parts are posted by the various sellers. When a part is selected by a buyer in the manner described below, it is immediately removed from the database 22 , thereby prohibiting other buyers from subsequently selecting parts that have already been purchased.
- the database 22 is constantly changing as parts are posted and sold so as to represent an accurate pool of available parts.
- the data uploaded by the buyer computers 14 to the server computer 12 must describe the corresponding parts with sufficient detail to enable the system 10 to make appropriate part selections in accordance with the buyers' requests.
- the actual data needed will vary depending on the nature of the parts contained in the system 10 . In most all applications, the minimum data requirements will generally include part numbers, serial numbers, quantity and pricing. Other data could be useful for some types of parts.
- the virtual warehouse parts distribution system 10 contained an inventory database of aircraft engine parts it would be useful to include data identifying the source of each part as well as each part's condition, namely whether it is new or used. Related information such as a part's time since new and/or cycles since new would also be helpful.
- the inputted data is used to sort the parts in a manner that will facilitate the searching of the database 22 for appropriate parts to meet buyer requests.
- the database 22 can be divided into a number of inventory categories that contain a particular type of part. These inventory categories could be limited to a single part number or a part number and its alternative part numbers.
- each inventory category can be further divided into sub-inventory categories. As shown, the inventory category is sorted as a matrix whereby the available parts are broken down by condition and seller and each box in the matrix represents a sub-inventory category.
- the first row of the matrix corresponds to new parts and the remaining rows correspond to used parts, wherein the used parts are further sorted as being repaired parts, serviceable parts (i.e., parts suitable for use as is), and parts needing repair.
- Each column in FIG. 2 corresponds to the source or seller that is offering the part. Although only four columns are depicted in the Figure, the number of columns will actually match the number of sellers participating in the system 10 . Thus, the numbers of new parts, repaired parts, serviceable parts and repairable parts available from each seller can be determined. In the inventory category depicted in FIG. 2 , for example, Seller A has 8 new parts available and Seller B has 4 serviceable parts available.
- a single system participant could be both a seller and a buyer. That is, a repair shop may have a surplus of one part that they wish to sell and also have a need to obtain other parts.
- one of the columns would represent the system participant's own available inventory. Accordingly, such a system participant would be able to use the system 10 to monitor its own inventory as well as the entire database 22 .
- the system 10 can also be programmed to include a “kanban function.”
- Kanban is a well known technique used in manufacturing operations practicing just-in-time methods. Briefly, if a manufacturing workstation needs a part, it sends a signal, such as a colored card, to the station that makes the part to send more of the parts. In accordance with just-in-time philosophy, limits are put on how many parts are sent so that an excess of the part will not occur.
- maximum and minimum kanban limits are programmed into the server computer 12 for each sub-inventory category. Then, if a particular sub-inventory category is at its maximum value, no more of that particular part will be accepted. If the sub-inventory category falls below its minimum value, then the seller is notified that more such parts are needed.
- Step 1 a prospective buyer wishing to obtain specific parts utilizes a buyer computer 14 to access the server computer 12 .
- the buyer computer 14 sends a request for the desired parts to the server computer 12 .
- the request will identify the desired parts by part number and quantity.
- the server computer 12 performs an automated search of the inventory database 22 to determine if the desired parts are available and selects the most suitable parts from the pool of available parts found in the search, if any are found.
- the server computer 12 is programmed to make the selection of parts for a buyer based on that buyer's specified picking order.
- the buyer may have certain preferences relating to what parts will be accepted. For example, a buyer may want all used parts (which are generally less expensive than newly manufactured parts), or a buyer may want all used parts except for certain part numbers. Another example could be that a buyer might be generally willing to accept used parts, but not from particular sources.
- the process will take all of these preferences into account for each participant and develop a hierarchy of preferences to establish a buyer-specific picking order. This picking order is programmed into the system 10 so that the server computer 12 will automatically use the picking order when searching the database 22 in response to a buyer request.
- Step 2 the server computer 12 sends a message to the buyer computer 14 informing it of the availability of the desired parts. If the parts are not available, then the selection process ends at this point. If desired parts are available, then server computer's message notifies the buyer computer of the availability of the selected parts and includes an instruction to the buyer computer 14 to issue a purchase order identifying the parts desired, the needed quantity and the delivery location to the appropriate seller.
- the buyer computer 14 issues the purchase order, preferably via electronic data interchange (EDI) or a similar electronic uplink means, to the server computer 12 , and the server computer 12 relays the purchase order to the appropriate seller computer 16 at Step 4 . Note that in some instances it is possible that not all of the parts needed to fulfill a given buyer's request are supplied by the same seller. In that case, multiple purchase orders would be issued, with one purchase order going to each seller for the parts provided by that seller.
- EDI electronic data interchange
- the seller ships the parts directly to the buyer. Typically, the seller will provide an invoice either with the shipment or on its regular billing cycle.
- the buyer routes the parts to the shop floor, where a determination is made whether the parts will be used. If any of the parts are not used, then these parts are returned to the buyer's inventory.
- the buyer at Step 5 , could upload data corresponding to these parts to the server computer 12 for posting in the database 22 , thereby utilizing the system 10 as a seller.
- a master agreement that controls participation in the system 10 be utilized. All system participants would be required to sign the master agreement to join the system 10 . All aspects of the transactions between buyers and sellers under the system 10 , including the terms of the blanket purchase orders, would thus be determined before participation in the system 10 commenced.
- the master agreement could also provide for an auditing function wherein the data describing the parts posted by prospective sellers would periodically be checked for accuracy.
Abstract
A parts distribution system and process uses a computer network, particularly the Internet, to efficiently distribute spare parts in a cost-effective manner. The system includes a plurality of buyer computers for operation by a system participant desiring to obtain one or more parts, a plurality of seller computers for operation by a system participant desiring to sell one or more parts, and at least one server computer. The buyer computers, seller computers and server computer are interconnected as a computer network. In operation, the seller computers are used to input part related data to the server computer, and the server computer uses the data to maintain a database of all available parts. The buyer computers are used to transmit part requests to the server computer, and the server computer selecting one or more parts from the database in response to the requests.
Description
- This application claims the benefit of U.S. Provisional Application No. 60/178,779, filed Jan. 28, 2000.
- This invention relates generally to the distribution of spare parts and more particularly to a system and method of using a computer network such as the Internet to facilitate spare part distribution.
- In many equipment-based industries, it is common to use service technicians to support and maintain the equipment. Such support and maintenance often requires a large number of spare parts. However, one problem with servicing such equipment has been obtaining the necessary spare parts in an efficient and cost-effective manner.
- An exemplary industry where this problem occurs is commercial aviation. Aircraft are routinely subject to various maintenance operations as part of their normal operation. Aircraft engines in particular have many components that periodically need to be replaced, on a scheduled or unscheduled basis. As is the case for many types of equipment, spare parts for aircraft engines are available from a wide variety of sources. For example, newly manufactured parts can be obtained from vendors or original equipment manufacturers (OEMs) that produce the parts. Used parts can be obtained from overhaul and repair shops or engine operators such as airlines. In addition, site excess (i.e., unused parts previously obtained by a repair site or engine operator but no longer needed by that entity) and site rotables (i.e., used or unused parts kept on hand by service shops to be used in place of a customer's parts while those parts are being repaired) are often available.
- While such numerous and diverse options for obtaining spare parts are available, the various sources form an unorganized network of prospective sellers that are generally independent from one another. Thus, a prospective buyer is faced with a daunting task when trying to obtain acceptable parts at the lowest price available. Currently, when an operation such as an engine service shop or an engine operator has a need for spare parts, the prospective buyer must search the unorganized network of prospective sellers on a source-by-source basis by contacting individual sources and inquiring whether they have the desired parts available and, if so, at what pricing. Given the large number of sources available, it is generally not practical to obtain a quote from every possible source. Many operations require that some minimum number of quotes (such as three) be obtained prior to issuing a purchase order to provide some comfort level that a reasonable price will be obtained. However, this is a subjective approach in that it relies heavily on guesswork as to which sources should be contacted. Furthermore, even when limiting the number of quotes required to be obtained, this approach can be a time consuming and inefficient process that does not guarantee the lowest pricing.
- Accordingly, there is a need for an easy and effective spare parts distribution system and process that enables prospective buyers to obtained desired parts at the best price possible or in accordance with other preferences.
- The above-mentioned need is met by the present invention which provides a network-based parts distribution system and process. The system includes a plurality of buyer computers for operation by a system participant desiring to obtain one or more parts, a plurality of seller computers for operation by a system participant desiring to sell one or more parts, and at least one server computer. The buyer computers, seller computers and server computer are interconnected as a computer network. In operation, the seller computers are used to input part related data to the server computer, and the server computer uses the data to maintain a database of all available parts. The buyer computers are used to transmit part requests to the server computer, and the server computer selecting one or more parts from the database in response to the requests.
- The present invention and its advantages over the prior art will become apparent upon reading the following detailed description and the appended claims with reference to the accompanying drawings.
- The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the concluding part of the specification. The invention, however, may be best understood by reference to the following description taken in conjunction with the accompanying drawing figures in which:
-
FIG. 1 is a schematic view of a virtual warehouse parts distribution system. -
FIG. 2 graphically illustrates a matrix representing one inventory category from the database of the virtual warehouse parts distribution system. -
FIG. 3 graphically illustrates a parts selection process of the present invention. - Referring to the drawings wherein identical reference numerals denote the same elements throughout the various views,
FIG. 1 shows a virtual warehouseparts distribution system 10. Thesystem 10 includes at least onecentral server computer 12, a plurality ofbuyer computers 14 operated by system participants interested in obtaining parts (referred to herein as buyers), and a plurality ofseller computers 16 operated by system participants wishing to sell parts (referred to herein as sellers). It should be noted that a system participant could participate as both a buyer and a seller. For example, many organizations concerned with aircraft engine repair, such as overhaul shops and engine operators, can experience both excesses and shortages of various parts. Such an organization would be interested in participating in thesystem 10 to sell excess parts and buy parts that are in short supply. This would also be the case in many fields other than aircraft engine repair. Accordingly, although thebuyer computers 14 and theseller computers 16 as shown inFIG. 1 as being distinct components of thesystem 10 for the purposes of illustration, it should be understood that a single computer could be configured to function as both abuyer computer 14 and aseller computer 16. - The
server computer 12, thebuyer computers 14 and theseller computers 16 are all interconnected via acomputer network 18 and can thus be geographically dispersed on a regional, national or worldwide basis. Thenetwork 18 is preferably the Internet, although it is possible to employ other types of computer networks such as a local area network or a wide area network. In general, thebuyer computers 14 and theseller computers 16, which may be conventional workstations, personal computers, or the like, are client computers that include a conventional Web browser software application. The browser allows thecomputer server computer 12 or any other server systems connected to thenetwork 18. Note that the present invention is not limited to the use of HTML; other suitable languages may be substituted within the scope of the present invention. As is known in the art, thesystem 10 may also include firewall protection (not shown) to prevent non-system participants from gaining access thereto. - The
server computer 12, which could comprise a cluster of server computers, includes a Web server 20 (i.e., a computer program that serves requested HTML pages or files) for communicating with thebuyer computers 14 and theseller computers 16, and aparts inventory database 22. Thedatabase 22 contains a list of all the parts that the various sellers participating in thesystem 10 are willing to sell, and thus represents a pool of all the parts available for purchase via thesystem 10. Theserver computer 12 is programmed to receive data relating to the available parts and uses the data to maintain thedatabase 22. Theserver computer 12 is also programmed to receive requests for parts from prospective buyers and subsequently search thedatabase 22 for such parts. - Generally, the operation of the
system 10 comprises two primary processes: a database creation and maintenance process and a part selection process. In the database creation and maintenance process, prospective sellers willing to sell one or more parts utilize theseller computers 16 to upload data corresponding to the parts to theserver computer 12. Theserver computer 12 processes the data and adds the parts to thedatabase 22 in a sorted fashion. Thedatabase 22 is continually updated in this fashion as newly available parts are posted by the various sellers. When a part is selected by a buyer in the manner described below, it is immediately removed from thedatabase 22, thereby prohibiting other buyers from subsequently selecting parts that have already been purchased. Thus, thedatabase 22 is constantly changing as parts are posted and sold so as to represent an accurate pool of available parts. - The data uploaded by the
buyer computers 14 to theserver computer 12 must describe the corresponding parts with sufficient detail to enable thesystem 10 to make appropriate part selections in accordance with the buyers' requests. The actual data needed will vary depending on the nature of the parts contained in thesystem 10. In most all applications, the minimum data requirements will generally include part numbers, serial numbers, quantity and pricing. Other data could be useful for some types of parts. By way of example, if the virtual warehouseparts distribution system 10 contained an inventory database of aircraft engine parts it would be useful to include data identifying the source of each part as well as each part's condition, namely whether it is new or used. Related information such as a part's time since new and/or cycles since new would also be helpful. As mentioned above, spare parts for aircraft engines, both new and used, are available from a wide variety of diverse sources. It should be emphasized that aircraft engine parts are only being used as an example to facilitate description of the present invention and that the present invention is in no way limited to this type of parts. - The inputted data is used to sort the parts in a manner that will facilitate the searching of the
database 22 for appropriate parts to meet buyer requests. For example, thedatabase 22 can be divided into a number of inventory categories that contain a particular type of part. These inventory categories could be limited to a single part number or a part number and its alternative part numbers. As can be seen inFIG. 2 , each inventory category can be further divided into sub-inventory categories. As shown, the inventory category is sorted as a matrix whereby the available parts are broken down by condition and seller and each box in the matrix represents a sub-inventory category. The first row of the matrix corresponds to new parts and the remaining rows correspond to used parts, wherein the used parts are further sorted as being repaired parts, serviceable parts (i.e., parts suitable for use as is), and parts needing repair. Each column inFIG. 2 corresponds to the source or seller that is offering the part. Although only four columns are depicted in the Figure, the number of columns will actually match the number of sellers participating in thesystem 10. Thus, the numbers of new parts, repaired parts, serviceable parts and repairable parts available from each seller can be determined. In the inventory category depicted inFIG. 2 , for example, Seller A has 8 new parts available and Seller B has 4 serviceable parts available. - It is again pointed out that a single system participant could be both a seller and a buyer. That is, a repair shop may have a surplus of one part that they wish to sell and also have a need to obtain other parts. In this case, one of the columns would represent the system participant's own available inventory. Accordingly, such a system participant would be able to use the
system 10 to monitor its own inventory as well as theentire database 22. - The
system 10 can also be programmed to include a “kanban function.” Kanban is a well known technique used in manufacturing operations practicing just-in-time methods. Briefly, if a manufacturing workstation needs a part, it sends a signal, such as a colored card, to the station that makes the part to send more of the parts. In accordance with just-in-time philosophy, limits are put on how many parts are sent so that an excess of the part will not occur. In the present invention, maximum and minimum kanban limits are programmed into theserver computer 12 for each sub-inventory category. Then, if a particular sub-inventory category is at its maximum value, no more of that particular part will be accepted. If the sub-inventory category falls below its minimum value, then the seller is notified that more such parts are needed. - Referring now to
FIG. 3 , the part selection process is illustrated. InStep 1, a prospective buyer wishing to obtain specific parts utilizes abuyer computer 14 to access theserver computer 12. Specifically, thebuyer computer 14 sends a request for the desired parts to theserver computer 12. Generally, the request will identify the desired parts by part number and quantity. In response, theserver computer 12 performs an automated search of theinventory database 22 to determine if the desired parts are available and selects the most suitable parts from the pool of available parts found in the search, if any are found. - The
server computer 12 is programmed to make the selection of parts for a buyer based on that buyer's specified picking order. In other words, the buyer may have certain preferences relating to what parts will be accepted. For example, a buyer may want all used parts (which are generally less expensive than newly manufactured parts), or a buyer may want all used parts except for certain part numbers. Another example could be that a buyer might be generally willing to accept used parts, but not from particular sources. The process will take all of these preferences into account for each participant and develop a hierarchy of preferences to establish a buyer-specific picking order. This picking order is programmed into thesystem 10 so that theserver computer 12 will automatically use the picking order when searching thedatabase 22 in response to a buyer request. - In
Step 2, then theserver computer 12 sends a message to thebuyer computer 14 informing it of the availability of the desired parts. If the parts are not available, then the selection process ends at this point. If desired parts are available, then server computer's message notifies the buyer computer of the availability of the selected parts and includes an instruction to thebuyer computer 14 to issue a purchase order identifying the parts desired, the needed quantity and the delivery location to the appropriate seller. InStep 3, thebuyer computer 14 issues the purchase order, preferably via electronic data interchange (EDI) or a similar electronic uplink means, to theserver computer 12, and theserver computer 12 relays the purchase order to theappropriate seller computer 16 atStep 4. Note that in some instances it is possible that not all of the parts needed to fulfill a given buyer's request are supplied by the same seller. In that case, multiple purchase orders would be issued, with one purchase order going to each seller for the parts provided by that seller. - When the purchase order is received at the
seller computer 16, the seller ships the parts directly to the buyer. Typically, the seller will provide an invoice either with the shipment or on its regular billing cycle. Upon receipt of the parts, the buyer routes the parts to the shop floor, where a determination is made whether the parts will be used. If any of the parts are not used, then these parts are returned to the buyer's inventory. At this point, the buyer, atStep 5, could upload data corresponding to these parts to theserver computer 12 for posting in thedatabase 22, thereby utilizing thesystem 10 as a seller. - In order to ensure consistent and equitable operation of the
system 10 among the multiple participants, it is preferred that a master agreement that controls participation in thesystem 10 be utilized. All system participants would be required to sign the master agreement to join thesystem 10. All aspects of the transactions between buyers and sellers under thesystem 10, including the terms of the blanket purchase orders, would thus be determined before participation in thesystem 10 commenced. The master agreement could also provide for an auditing function wherein the data describing the parts posted by prospective sellers would periodically be checked for accuracy. - The foregoing has described a network-based, automated system and process for efficiently obtaining spare parts in a cost-effective manner. The system coordinates multiple participants and can be integrated into site legacy systems. While specific embodiments of the present invention have been described, it will be apparent to those skilled in the art that various modifications thereto can be made without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1-12. (canceled)
13. A method for distributing parts between system participants, said method comprising:
obtaining agreements from system participants, including buyers and sellers, to join in a network-based, automated virtual warehouse parts distribution system, including agreements to terms of blanket purchase orders and auditing to check accuracy of data describing parts posted by sellers;
operating a server computer to receive, via a computer network, descriptions of data corresponding of parts being offered for sale by the sellers, to receive, via the computer network, requests for desired parts by the buyers, to identify suitable parts from a pool of available said parts being offered for sale by the sellers, and to issue an instruction to a computer used by the buyer to issue a purchase order consistent with the agreement of the buyer identifying the parts meeting the request.
14. A method in accordance with claim 13 further comprising operating the server computer to identify suitable parts for the buyer in accordance with a buyer's specified picking order.
15. A method in accordance with claim 13 further comprising operating the server computer to maintain a database of available parts, including descriptions of conditions of used parts offered for sale.
16. A method in accordance with claim 13 including obtaining an agreement from a system participant who is both a buyer and a seller.
17. A method in accordance with claim 13 further comprising operating the server to issue an instruction to the computer used by the buyer to issue a plurality of purchase orders, one to each seller of a part, in an instance in which not all parts needed to fulfill the buyer's request are supplied by the same seller.
18. A method in accordance with claim 13 further comprising:
operating the server to divide the parts offered for sale into a plurality of inventory categories and sub-categories; and
programming the server with maximum and minimum inventory limits for sub-inventory categories.
19. A method in accordance with claim 18 further comprising operating the server to accept no more parts in a sub-category when the sub-inventory category is at the maximum inventory limit.
20. A method in accordance with claim 18 further comprising operating the server to notify a seller that more parts in a sub-inventory category are needed when the sub-inventory category falls below the minimum inventory limit.
21. A method in accordance with claim 13 wherein the parts comprise aircraft parts, including used aircraft parts.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/867,377 US20080027831A1 (en) | 2000-01-28 | 2007-10-04 | Virtual warehouse parts distribution system and process |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17877900P | 2000-01-28 | 2000-01-28 | |
US09/523,079 US7376599B1 (en) | 2000-01-28 | 2000-03-10 | Virtual warehouse parts distribution system and process |
US11/867,377 US20080027831A1 (en) | 2000-01-28 | 2007-10-04 | Virtual warehouse parts distribution system and process |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/523,079 Division US7376599B1 (en) | 2000-01-28 | 2000-03-10 | Virtual warehouse parts distribution system and process |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080027831A1 true US20080027831A1 (en) | 2008-01-31 |
Family
ID=39387682
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/523,079 Expired - Fee Related US7376599B1 (en) | 2000-01-28 | 2000-03-10 | Virtual warehouse parts distribution system and process |
US11/867,377 Abandoned US20080027831A1 (en) | 2000-01-28 | 2007-10-04 | Virtual warehouse parts distribution system and process |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/523,079 Expired - Fee Related US7376599B1 (en) | 2000-01-28 | 2000-03-10 | Virtual warehouse parts distribution system and process |
Country Status (1)
Country | Link |
---|---|
US (2) | US7376599B1 (en) |
Cited By (54)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070156550A1 (en) * | 2005-12-30 | 2007-07-05 | Der Emde Martin V | Architectural design for cash and liquidity management application software |
US20070156475A1 (en) * | 2005-12-30 | 2007-07-05 | Arthur Berger | Architectural design for plan-driven procurement application software |
US20070156500A1 (en) * | 2005-12-30 | 2007-07-05 | Wilfried Merkel | Architectural design for sell from stock application software |
US20070156476A1 (en) * | 2005-12-30 | 2007-07-05 | Alexander Koegler | Architectural design for service request and order management application software |
US20070156489A1 (en) * | 2005-12-30 | 2007-07-05 | Arthur Berger | Architectural design for service procurement application software |
US20070156499A1 (en) * | 2005-12-30 | 2007-07-05 | Arthur Berger | Architectural design for self-service procurement application software |
US20070162893A1 (en) * | 2005-12-30 | 2007-07-12 | Gerd Moosmann | Software model process component |
US20070168240A1 (en) * | 2005-12-30 | 2007-07-19 | Shai Alfandary | Architectural design for make to stock application software |
US20070168303A1 (en) * | 2005-12-30 | 2007-07-19 | Gerd Moosmann | Software model process interaction |
US20070233541A1 (en) * | 2006-03-30 | 2007-10-04 | Martin Schorr | Providing accounting software application as enterprise services |
US20070233728A1 (en) * | 2006-03-30 | 2007-10-04 | Joachim Puteick | Foundation layer for services based enterprise software architecture |
US20070233581A1 (en) * | 2006-03-30 | 2007-10-04 | Markus Peter | Providing product catalog software application as enterprise services |
US20070234282A1 (en) * | 2006-03-31 | 2007-10-04 | Uta Prigge | Composite application modeling |
US20070233598A1 (en) * | 2006-03-30 | 2007-10-04 | Martin Von Der Emde | Providing payment software application as enterprise services |
US20070265862A1 (en) * | 2006-04-13 | 2007-11-15 | Jens Freund | Software model business process variant types |
US20070265860A1 (en) * | 2006-03-30 | 2007-11-15 | Karina Herrmann | Providing supplier relationship management software application as enterprise services |
US20090171713A1 (en) * | 2007-12-31 | 2009-07-02 | Armin Schwarz | Architectural Design for Self-Service Procurement Application Software |
US20090171758A1 (en) * | 2007-12-31 | 2009-07-02 | Shai Alfandary | Architectural design for physical inventory application software |
US20090171712A1 (en) * | 2007-12-31 | 2009-07-02 | Matthias Heinrichs | Architectural Design for Ad-Hoc Goods Movement Software |
US20090172699A1 (en) * | 2007-12-31 | 2009-07-02 | Christoph Jungkind | Architectural Design for Service Procurement Application Software |
US20090171698A1 (en) * | 2007-12-31 | 2009-07-02 | Sap Ag | Providing human capital management software application as enterprise services |
US20090177516A1 (en) * | 2000-10-26 | 2009-07-09 | I2 Technologies Us, Inc. | Redistribution of Parts in a Distribution Network |
US20100070395A1 (en) * | 2008-09-18 | 2010-03-18 | Andreas Elkeles | Architectural design for payroll processing application software |
US20100070391A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Architectural Design for Tax Declaration Application Software |
US20100070331A1 (en) * | 2008-09-18 | 2010-03-18 | Alexander Koegler | Architectural design for service request and order management application software |
US20100070330A1 (en) * | 2008-09-18 | 2010-03-18 | Peer Marschall | Architectural design for customer returns handling application software |
US20100070324A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Architectural Design for Plan-Driven Procurement Application Software |
US20100070317A1 (en) * | 2008-09-18 | 2010-03-18 | Nir Pachter | Architectural design for sell from stock application software |
US20100070318A1 (en) * | 2008-09-18 | 2010-03-18 | Achim Clemens | Providing logistics execution application as enterprise services |
US20100070555A1 (en) * | 2008-09-18 | 2010-03-18 | Jacques Duparc | Architectural design for time recording application software |
US20100070336A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Providing Customer Relationship Management Application as Enterprise Services |
US20100070289A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Architectural Design for Embedded Support Application Software |
US20100082497A1 (en) * | 2008-09-18 | 2010-04-01 | Sap Ag | Providing Foundation Application as Enterprise Services |
US20100138276A1 (en) * | 2008-12-03 | 2010-06-03 | Sap Ag | Architectural design for make-to-specification application software |
US20100138255A1 (en) * | 2008-12-03 | 2010-06-03 | Sap Ag | Architectural design for manual invoicing application software |
US20100153239A1 (en) * | 2008-12-11 | 2010-06-17 | Sap Ag | Providing accounting software application as enterprise services |
US20100153240A1 (en) * | 2008-12-11 | 2010-06-17 | Andreas Bold | Providing Payroll Software Application as Enterprise Services |
WO2012151435A2 (en) * | 2011-05-04 | 2012-11-08 | Loop Aerospace Corporation | Methods and systems for facilitating aircraft parts manufacturing |
US8311904B2 (en) | 2008-12-03 | 2012-11-13 | Sap Ag | Architectural design for intra-company stock transfer application software |
US8316344B2 (en) | 2005-12-30 | 2012-11-20 | Sap Ag | Software model deployment units |
US8321306B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for selling project-based services application software |
US8321831B2 (en) | 2005-12-30 | 2012-11-27 | Sap Ag | Architectural design for internal projects application software |
US8326703B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Architectural design for product catalog management application software |
US8374896B2 (en) | 2008-09-18 | 2013-02-12 | Sap Ag | Architectural design for opportunity management application software |
US8396749B2 (en) * | 2006-03-30 | 2013-03-12 | Sap Ag | Providing customer relationship management application as enterprise services |
US8401936B2 (en) | 2007-12-31 | 2013-03-19 | Sap Ag | Architectural design for expense reimbursement application software |
US8401928B2 (en) | 2008-09-18 | 2013-03-19 | Sap Ag | Providing supplier relationship management software application as enterprise services |
US8407664B2 (en) | 2005-12-30 | 2013-03-26 | Sap Ag | Software model business objects |
US8448137B2 (en) | 2005-12-30 | 2013-05-21 | Sap Ag | Software model integration scenarios |
US8522194B2 (en) | 2005-12-30 | 2013-08-27 | Sap Ag | Software modeling |
US8671032B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Providing payment software application as enterprise services |
US8671033B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Architectural design for personnel events application software |
US8738476B2 (en) | 2008-12-03 | 2014-05-27 | Sap Ag | Architectural design for selling standardized services application software |
US20190026691A1 (en) * | 2016-03-31 | 2019-01-24 | Cainiao Smart Logistics Holding Limited | Method, apparatus, and system for scheduling logistic resources |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100582814B1 (en) | 1999-05-25 | 2006-05-23 | 세이프페이 오스트레일리아 피티와이 리미티드 | Method and system for handling network transactions |
WO2005043425A2 (en) * | 2003-10-31 | 2005-05-12 | Siemens Aktiengesellschaft | Method and computer system for providing spare parts for a client |
AU2004202060B2 (en) * | 2004-05-14 | 2006-08-24 | Kim Gilbert Davidson | Spare part procurement method |
US20110153469A1 (en) * | 2009-12-23 | 2011-06-23 | Patricia Denise Mackenzie | System and method for managing mobile inventory within a virtual warehouse |
CN105608087B (en) * | 2014-11-19 | 2020-01-31 | 菜鸟智能物流控股有限公司 | resource scheduling method and device |
US10339496B2 (en) * | 2015-06-15 | 2019-07-02 | Milwaukee Electric Tool Corporation | Power tool communication system |
US10417595B2 (en) | 2017-05-05 | 2019-09-17 | DeHart Consulting, LLC | Time-based, demand-pull production |
US11494832B2 (en) | 2018-11-09 | 2022-11-08 | Honeywell International Inc. | Systems and methods for securely creating a listing of equipment on an equipment online marketplace platform |
US11640630B2 (en) | 2018-11-09 | 2023-05-02 | Honeywell International Inc. | Systems and methods for verifying identity of a user on an equipment online marketplace platform |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5216612A (en) * | 1990-07-16 | 1993-06-01 | R. J. Reynolds Tobacco Company | Intelligent computer integrated maintenance system and method |
US5712989A (en) * | 1993-04-02 | 1998-01-27 | Fisher Scientific Company | Just-in-time requisition and inventory management system |
US5819232A (en) * | 1996-03-22 | 1998-10-06 | E. I. Du Pont De Nemours And Company | Method and apparatus for inventory control of a manufacturing or distribution process |
US6182053B1 (en) * | 1996-03-26 | 2001-01-30 | Recovery Sales Corporation | Method and apparatus for managing inventory |
US6332135B1 (en) * | 1998-11-16 | 2001-12-18 | Tradeaccess, Inc. | System and method for ordering sample quantities over a network |
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 |
US6338050B1 (en) * | 1998-11-16 | 2002-01-08 | Trade Access, Inc. | System and method for providing and updating user supplied context for a negotiations system |
US20020065764A1 (en) * | 2000-05-05 | 2002-05-30 | Brodersen Andrew N. | Marketing and purchasing components and services |
US20020077850A1 (en) * | 2000-02-04 | 2002-06-20 | Mcmenimen James L. | Responsive manufacturing and inventory control |
US20030055753A1 (en) * | 2001-09-17 | 2003-03-20 | Eshinui Incorporated | Spare parts and consumables management system |
US20030110104A1 (en) * | 2001-10-23 | 2003-06-12 | Isuppli Corp. | Enhanced vendor managed inventory system and process |
US6671673B1 (en) * | 2000-03-24 | 2003-12-30 | International Business Machines Corporation | Method for integrated supply chain and financial management |
US20050216366A1 (en) * | 2004-03-09 | 2005-09-29 | Ford Motor Company | Method and system for controlling spare parts inventory within a manufacturing plant |
US7266518B2 (en) * | 2005-12-29 | 2007-09-04 | Kimberly-Clark Worldwide, Inc. | Spare parts inventory management |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4799156A (en) * | 1986-10-01 | 1989-01-17 | Strategic Processing Corporation | Interactive market management system |
JPH08500201A (en) * | 1993-05-20 | 1996-01-09 | ムーア.ビジネス.フォームス.インコーポレイテッド | An integrated computer network that guides customer orders to various suppliers through a centralized computer |
US5592375A (en) * | 1994-03-11 | 1997-01-07 | Eagleview, Inc. | Computer-assisted system for interactively brokering goods or services between buyers and sellers |
US6023683A (en) * | 1994-08-10 | 2000-02-08 | Fisher Scientific Company | Electronic sourcing system and method |
US5845265A (en) * | 1995-04-26 | 1998-12-01 | Mercexchange, L.L.C. | Consignment nodes |
US5758328A (en) * | 1996-02-22 | 1998-05-26 | Giovannoli; Joseph | Computerized quotation system and method |
US6016504A (en) * | 1996-08-28 | 2000-01-18 | Infospace.Com, Inc. | Method and system for tracking the purchase of a product and services over the Internet |
US6058373A (en) * | 1996-10-16 | 2000-05-02 | Microsoft Corporation | System and method for processing electronic order forms |
US6026378A (en) * | 1996-12-05 | 2000-02-15 | Cnet Co., Ltd. | Warehouse managing system |
US5895454A (en) * | 1997-04-17 | 1999-04-20 | Harrington; Juliette | Integrated interface for vendor/product oriented internet websites |
AU758001B2 (en) * | 1997-09-15 | 2003-03-13 | Mro Software, Inc. | Electronic information network for inventory control and transfer |
-
2000
- 2000-03-10 US US09/523,079 patent/US7376599B1/en not_active Expired - Fee Related
-
2007
- 2007-10-04 US US11/867,377 patent/US20080027831A1/en not_active Abandoned
Patent Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5216612A (en) * | 1990-07-16 | 1993-06-01 | R. J. Reynolds Tobacco Company | Intelligent computer integrated maintenance system and method |
US5712989A (en) * | 1993-04-02 | 1998-01-27 | Fisher Scientific Company | Just-in-time requisition and inventory management system |
US5819232A (en) * | 1996-03-22 | 1998-10-06 | E. I. Du Pont De Nemours And Company | Method and apparatus for inventory control of a manufacturing or distribution process |
US6182053B1 (en) * | 1996-03-26 | 2001-01-30 | Recovery Sales Corporation | Method and apparatus for managing inventory |
US6338050B1 (en) * | 1998-11-16 | 2002-01-08 | Trade Access, Inc. | System and method for providing and updating user supplied context for a negotiations system |
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 |
US6332135B1 (en) * | 1998-11-16 | 2001-12-18 | Tradeaccess, Inc. | System and method for ordering sample quantities over a network |
US20020077850A1 (en) * | 2000-02-04 | 2002-06-20 | Mcmenimen James L. | Responsive manufacturing and inventory control |
US6671673B1 (en) * | 2000-03-24 | 2003-12-30 | International Business Machines Corporation | Method for integrated supply chain and financial management |
US20020065764A1 (en) * | 2000-05-05 | 2002-05-30 | Brodersen Andrew N. | Marketing and purchasing components and services |
US20030055753A1 (en) * | 2001-09-17 | 2003-03-20 | Eshinui Incorporated | Spare parts and consumables management system |
US20030110104A1 (en) * | 2001-10-23 | 2003-06-12 | Isuppli Corp. | Enhanced vendor managed inventory system and process |
US20050216366A1 (en) * | 2004-03-09 | 2005-09-29 | Ford Motor Company | Method and system for controlling spare parts inventory within a manufacturing plant |
US7266518B2 (en) * | 2005-12-29 | 2007-09-04 | Kimberly-Clark Worldwide, Inc. | Spare parts inventory management |
Cited By (85)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7886960B2 (en) * | 2000-10-26 | 2011-02-15 | I2 Technologies Us, Inc. | Redistribution of parts in a distribution network |
US20090177516A1 (en) * | 2000-10-26 | 2009-07-09 | I2 Technologies Us, Inc. | Redistribution of Parts in a Distribution Network |
US8321831B2 (en) | 2005-12-30 | 2012-11-27 | Sap Ag | Architectural design for internal projects application software |
US20070156489A1 (en) * | 2005-12-30 | 2007-07-05 | Arthur Berger | Architectural design for service procurement application software |
US8326703B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Architectural design for product catalog management application software |
US20070156499A1 (en) * | 2005-12-30 | 2007-07-05 | Arthur Berger | Architectural design for self-service procurement application software |
US20070162893A1 (en) * | 2005-12-30 | 2007-07-12 | Gerd Moosmann | Software model process component |
US20070168240A1 (en) * | 2005-12-30 | 2007-07-19 | Shai Alfandary | Architectural design for make to stock application software |
US20070168303A1 (en) * | 2005-12-30 | 2007-07-19 | Gerd Moosmann | Software model process interaction |
US8316344B2 (en) | 2005-12-30 | 2012-11-20 | Sap Ag | Software model deployment units |
US8327319B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Software model process interaction |
US20070156550A1 (en) * | 2005-12-30 | 2007-07-05 | Der Emde Martin V | Architectural design for cash and liquidity management application software |
US8402426B2 (en) | 2005-12-30 | 2013-03-19 | Sap Ag | Architectural design for make to stock application software |
US20070156476A1 (en) * | 2005-12-30 | 2007-07-05 | Alexander Koegler | Architectural design for service request and order management application software |
US20070156500A1 (en) * | 2005-12-30 | 2007-07-05 | Wilfried Merkel | Architectural design for sell from stock application software |
US8370794B2 (en) | 2005-12-30 | 2013-02-05 | Sap Ag | Software model process component |
US8676617B2 (en) | 2005-12-30 | 2014-03-18 | Sap Ag | Architectural design for self-service procurement application software |
US8660904B2 (en) | 2005-12-30 | 2014-02-25 | Sap Ag | Architectural design for service request and order management application software |
US8380553B2 (en) | 2005-12-30 | 2013-02-19 | Sap Ag | Architectural design for plan-driven procurement application software |
US8522194B2 (en) | 2005-12-30 | 2013-08-27 | Sap Ag | Software modeling |
US8448137B2 (en) | 2005-12-30 | 2013-05-21 | Sap Ag | Software model integration scenarios |
US20070156475A1 (en) * | 2005-12-30 | 2007-07-05 | Arthur Berger | Architectural design for plan-driven procurement application software |
US8396731B2 (en) | 2005-12-30 | 2013-03-12 | Sap Ag | Architectural design for service procurement application software |
US8407664B2 (en) | 2005-12-30 | 2013-03-26 | Sap Ag | Software model business objects |
US20070233541A1 (en) * | 2006-03-30 | 2007-10-04 | Martin Schorr | Providing accounting software application as enterprise services |
US8326702B2 (en) | 2006-03-30 | 2012-12-04 | Sap Ag | Providing supplier relationship management software application as enterprise services |
US8396761B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing product catalog software application as enterprise services |
US8442850B2 (en) | 2006-03-30 | 2013-05-14 | Sap Ag | Providing accounting software application as enterprise services |
US8396749B2 (en) * | 2006-03-30 | 2013-03-12 | Sap Ag | Providing customer relationship management application as enterprise services |
US8538864B2 (en) | 2006-03-30 | 2013-09-17 | Sap Ag | Providing payment software application as enterprise services |
US20070265860A1 (en) * | 2006-03-30 | 2007-11-15 | Karina Herrmann | Providing supplier relationship management software application as enterprise services |
US8438119B2 (en) | 2006-03-30 | 2013-05-07 | Sap Ag | Foundation layer for services based enterprise software architecture |
US20070233728A1 (en) * | 2006-03-30 | 2007-10-04 | Joachim Puteick | Foundation layer for services based enterprise software architecture |
US20070233598A1 (en) * | 2006-03-30 | 2007-10-04 | Martin Von Der Emde | Providing payment software application as enterprise services |
US20070233581A1 (en) * | 2006-03-30 | 2007-10-04 | Markus Peter | Providing product catalog software application as enterprise services |
US20070234282A1 (en) * | 2006-03-31 | 2007-10-04 | Uta Prigge | Composite application modeling |
US8321832B2 (en) | 2006-03-31 | 2012-11-27 | Sap Ag | Composite application modeling |
US20070265862A1 (en) * | 2006-04-13 | 2007-11-15 | Jens Freund | Software model business process variant types |
US8312416B2 (en) | 2006-04-13 | 2012-11-13 | Sap Ag | Software model business process variant types |
US8315900B2 (en) | 2007-12-31 | 2012-11-20 | Sap Ag | Architectural design for self-service procurement application software |
US8401936B2 (en) | 2007-12-31 | 2013-03-19 | Sap Ag | Architectural design for expense reimbursement application software |
US20090171713A1 (en) * | 2007-12-31 | 2009-07-02 | Armin Schwarz | Architectural Design for Self-Service Procurement Application Software |
US8671033B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Architectural design for personnel events application software |
US8671034B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Providing human capital management software application as enterprise services |
US8671032B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Providing payment software application as enterprise services |
US20090171758A1 (en) * | 2007-12-31 | 2009-07-02 | Shai Alfandary | Architectural design for physical inventory application software |
US20090171712A1 (en) * | 2007-12-31 | 2009-07-02 | Matthias Heinrichs | Architectural Design for Ad-Hoc Goods Movement Software |
US20090172699A1 (en) * | 2007-12-31 | 2009-07-02 | Christoph Jungkind | Architectural Design for Service Procurement Application Software |
US8510143B2 (en) | 2007-12-31 | 2013-08-13 | Sap Ag | Architectural design for ad-hoc goods movement software |
US20090171698A1 (en) * | 2007-12-31 | 2009-07-02 | Sap Ag | Providing human capital management software application as enterprise services |
US8447657B2 (en) | 2007-12-31 | 2013-05-21 | Sap Ag | Architectural design for service procurement application software |
US20100082497A1 (en) * | 2008-09-18 | 2010-04-01 | Sap Ag | Providing Foundation Application as Enterprise Services |
US20100070395A1 (en) * | 2008-09-18 | 2010-03-18 | Andreas Elkeles | Architectural design for payroll processing application software |
US8352338B2 (en) | 2008-09-18 | 2013-01-08 | Sap Ag | Architectural design for time recording application software |
US20100070336A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Providing Customer Relationship Management Application as Enterprise Services |
US8374896B2 (en) | 2008-09-18 | 2013-02-12 | Sap Ag | Architectural design for opportunity management application software |
US20100070555A1 (en) * | 2008-09-18 | 2010-03-18 | Jacques Duparc | Architectural design for time recording application software |
US8380549B2 (en) | 2008-09-18 | 2013-02-19 | Sap Ag | Architectural design for embedded support application software |
US8386325B2 (en) | 2008-09-18 | 2013-02-26 | Sap Ag | Architectural design for plan-driven procurement application software |
US20100070318A1 (en) * | 2008-09-18 | 2010-03-18 | Achim Clemens | Providing logistics execution application as enterprise services |
US20100070317A1 (en) * | 2008-09-18 | 2010-03-18 | Nir Pachter | Architectural design for sell from stock application software |
US20100070324A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Architectural Design for Plan-Driven Procurement Application Software |
US20100070330A1 (en) * | 2008-09-18 | 2010-03-18 | Peer Marschall | Architectural design for customer returns handling application software |
US8818884B2 (en) | 2008-09-18 | 2014-08-26 | Sap Ag | Architectural design for customer returns handling application software |
US8401928B2 (en) | 2008-09-18 | 2013-03-19 | Sap Ag | Providing supplier relationship management software application as enterprise services |
US8315926B2 (en) | 2008-09-18 | 2012-11-20 | Sap Ag | Architectural design for tax declaration application software |
US20100070331A1 (en) * | 2008-09-18 | 2010-03-18 | Alexander Koegler | Architectural design for service request and order management application software |
US20100070391A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Architectural Design for Tax Declaration Application Software |
US20100070289A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Architectural Design for Embedded Support Application Software |
US8321250B2 (en) | 2008-09-18 | 2012-11-27 | Sap Ag | Architectural design for sell from stock application software |
US8326706B2 (en) | 2008-09-18 | 2012-12-04 | Sap Ag | Providing logistics execution application as enterprise services |
US8595077B2 (en) | 2008-09-18 | 2013-11-26 | Sap Ag | Architectural design for service request and order management application software |
US8401908B2 (en) | 2008-12-03 | 2013-03-19 | Sap Ag | Architectural design for make-to-specification application software |
US20100138255A1 (en) * | 2008-12-03 | 2010-06-03 | Sap Ag | Architectural design for manual invoicing application software |
US20100138276A1 (en) * | 2008-12-03 | 2010-06-03 | Sap Ag | Architectural design for make-to-specification application software |
US8321306B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for selling project-based services application software |
US8321308B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for manual invoicing application software |
US8738476B2 (en) | 2008-12-03 | 2014-05-27 | Sap Ag | Architectural design for selling standardized services application software |
US8311904B2 (en) | 2008-12-03 | 2012-11-13 | Sap Ag | Architectural design for intra-company stock transfer application software |
US20100153239A1 (en) * | 2008-12-11 | 2010-06-17 | Sap Ag | Providing accounting software application as enterprise services |
US20100153240A1 (en) * | 2008-12-11 | 2010-06-17 | Andreas Bold | Providing Payroll Software Application as Enterprise Services |
US8671035B2 (en) | 2008-12-11 | 2014-03-11 | Sap Ag | Providing payroll software application as enterprise services |
WO2012151435A2 (en) * | 2011-05-04 | 2012-11-08 | Loop Aerospace Corporation | Methods and systems for facilitating aircraft parts manufacturing |
WO2012151435A3 (en) * | 2011-05-04 | 2014-04-17 | Loop Aerospace Corporation | Methods and systems for facilitating aircraft parts manufacturing |
US20190026691A1 (en) * | 2016-03-31 | 2019-01-24 | Cainiao Smart Logistics Holding Limited | Method, apparatus, and system for scheduling logistic resources |
Also Published As
Publication number | Publication date |
---|---|
US7376599B1 (en) | 2008-05-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7376599B1 (en) | Virtual warehouse parts distribution system and process | |
US7103567B2 (en) | System and device for product valuation and associated method | |
US10475095B2 (en) | Method and apparatus for efficiently responding to electronic requests for quote | |
Da Silveira et al. | Mass customization: Literature review and research directions | |
US5842178A (en) | Computerized quotation system and method | |
US9070166B2 (en) | Centralized, online multi-seller interface system | |
KR102244568B1 (en) | Method, device and system for managing logistics through forecast of demand and supply | |
US8473365B2 (en) | Multiple-platform estimating and automatic quoting for network-based parts resale with transferable reports | |
US8738662B2 (en) | Methods and apparatus for catalog data capture, storage and distribution | |
US20020087440A1 (en) | Method for reconstructing and validating a bill of materials and creating a comprehensive bill of materials | |
US20100017273A1 (en) | Method Apparatus, and System for Grouping Transportation Services | |
US20050010491A1 (en) | Consolidated procurement management system and method | |
KR20200139561A (en) | Product information processing apparatus for multiple online shopping maill product registration and method thereof | |
WO2007133892A1 (en) | Automated product selection and management system | |
US20020111872A1 (en) | Real time method for dynamic packaging items for distribution | |
US20030018538A1 (en) | System and method of intermediating sales | |
US20040267629A1 (en) | Purchasing hub for a procurement system | |
EP1528494A1 (en) | Automatic supplier sourcing | |
US20050065858A1 (en) | System and method for improved excess inventory distribution | |
US20050222912A1 (en) | System and method of processing commercial transactions through an internet website | |
US20030101098A1 (en) | Process and device for managing automatic data flow between data processing units for operational order processing | |
US20020082950A1 (en) | Product planning, development and program management information system and method | |
KR101429115B1 (en) | Integration Material-Distribution System for Identifying | |
US20050177468A1 (en) | Request for quote system and method | |
US7640191B2 (en) | Clustered bidding and auctions in a procurement system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: GENERAL ELECTRIC COMPANY, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GERHARDT, BRIAN L.;REEL/FRAME:019922/0460 Effective date: 20000307 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |