WO2004092898A2 - Data structure and system for information sharing - Google Patents

Abstract

A data management system (100) including a database (102) adapted to contain data associated with a unique identifier (402) and a server (502) connected to the database adapted to provide access the data to at least one user (114).

Description

Data Structure and System for Global Sharing of Information

Cross Reference to Related Applications [0001] This application claims the benefit of the following U.S. Provisional Patent Application: Provisional Patent Application Serial Number 60/462,812, entitled "Data Structure and System for Global Sharing of Information," filed on April 14, 2003, having attorney docket number 28552.08.02. Provisional Patent Application Serial Number 60/462,812 is herein incorporated by reference in its entirety.

[0002] This application claims the benefit of the following U.S. Provisional Patent Application: Provisional Patent Application Serial Number 60/462,032, entitled "Data Structure and System for Global Sharing of Information," filed on April 10, 2003, having attorney docket number 28552.08.01. Provisional Patent Application Serial Number 60/462,032 is herein incorporated by reference in its entirety.

Field of Invention [0003] This invention relates generally to data management systems, databases, database structures, and their methods of use.

Summary of the Invention [0004] In one embodiment, a data management system and method are disclosed that include a database adapted to contain data associated with a unique identifier and a server connected to the database adapted to provide access to the data by to at least two users. The disclosed data management system and method may be used to manage any type of data, including logistics data.

[0005] In another embodiment, a logistics data management system is disclosed that includes a database adapted to contain logistics data and a web server connected to the database adapted to transmit the logistics data to at least one user.

[0006] In another embodiment, a method of managing logistics information is disclosed for creating a plurality of data tables, linking each data table with at least one other data table, populating the plurality of data tables with logistics data, and providing access to the logistics data.

[0007] In another embodiment, a system adapted to manage logistics data associated with a unique identifier is disclosed for moving a package from a supplier to a customer, including a means to receive a purchase order from the customer, a means to receive the package from the supplier, a means to match the purchase order with the package, a means to group the package with other packages for shipping, and a means to ship the package. The package associated with the unique identifier may be handled by several transporting entities. [0008] In another embodiment, a method is disclosed of managing logistics data from a plurality of suppliers to a customer, including a first supplier assigning a unique first supplier number to a unique identifier, the unique identifier applied to each package shipped from the first supplier to the customer, and a second supplier assigning a unique second supplier number to a unique identifier, the unique identifier applied to each package shipped from the second supplier to the customer.

[0009] In another embodiment, a system adapted to manage logistics data involving one or more uniquely identified transporting entities, which may be any entity that transports product, such as for example, a supplier, the shipper, the customer, or a freight forwarder, is disclosed for moving a product from one or more sources to a customer, including a means to receive a purchase order from the customer, a means to receive the product from the one or more sources, a means to match the purchase order with the product, a means to group the product with other products for shipping, and a means to ship the product.

Brief Description of the Drawings

[ooι o; FIG. 1 is a view of a logistics data management system.

[0011 FIG. 2 is a view of a database. [0012 FIG. 3 is a view of a middleware component.

[0013; FIG. 4 is a view of a logistics supply chain. [0014; FIG. 5 is a view of a method of creating a database. [0015; FIG. 6 is a view of a method of using a shipper's destination profile. [0016; FIG. 7 is a view of a logistics supply chain. [0017; FIG. 8a is a view of a process of managing logistics data. [0018; FIG. 8b is an alternate view of a process of managing logistics data. [0019; FIG. 9 is a view of a purchase order. [0020; FIG.10 s a view of a purchase order,

[0021 FIG.11 s a view of a purchase order item, [0022 FIG.12 s a view of a receiving entry, [0023; FIG.13 s a view of a receiving item entry, [0024; FIG.14 s a view of a material receipt, [0025; FIG.15 s a view of a material receipt, [0026; FIG.16 s a view of a material receipt, [0027; FIG.17 s a view of a material receipt item, [0028 FIG.18 s a view of a release to pack item, [0029; FIG.19 s a view of a release to pack item. [0030 FIG.20 s a view of a packing list entry. [0031 FIG.21 s a view of a packing list entry. [0032] FIG. 22 i s a view o a box entry.

[0033] FIG. 23 i s a view o a box entry.

[0034] FIG. 24 i s a view o a box entry.

[0035] FIG. 25 i s a view o a box entry.

[0036] FIG. 26 i s a view o' a delivery ticket entry.

[0037] FIG. 27 i s a view ©^■ a delivery ticket entry.

[0038] FIG. 28 i s a view o a delivery ticket entry.

[0039] FIG. 29 i s a view o' a shipper's destination profile entry.

[0040] FIG. 30 i s a view o- a shipper's destination profile entry.

[0041] FIG. 31 i s a view o' a shipper's destination profile entry.

[0042] FIG. 32 i s a view o customer update flags.

[0043] FIG. 33 i s a view o ^: a logistics supply chain.

[0044] FIG. 34 i s a view o ^: a logistics supply chain.

[0045] FIG. 35 i s a view o' a logistics supply chain.

[0046] FIG. 36 i s a view o a logistics supply chain.

[0047] FIG. 37 i s a view o ^: a logistics supply chain. Detailed Description of the Drawings [0048] This invention relates generally to data management systems, databases, database structures, and their methods of use. It is understood, however, that the following disclosure provides many different embodiments or examples. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting. In addition, the present disclosure may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed. [0049] Referring now to FIG. 1 , an exemplary embodiment of data management system 100 is shown, which includes database 102, coupled to middleware 104, coupled to a server, such as for example a web server 106. In this embodiment, data management system 100 is designed to manage logistics data. Database 102 is adapted to contain logistics data. User 108, user 110, user 112, and user 14 are able to access system 100 and logistics data through web server 106 and/or through electronic data interchange 116. Web server 106 is adapted to host one or more web pages containing logistics data from database 102.

[0050] In operation, users 108, 110, 112, and/or 114 can access the database 102 through web server 106 and middleware 104 to read and/or write to database 102. User 114, and optionally, users 108, 110, and 112, are also able to access logistics data through electronic data interchange 116, through middleware 104 to database 102, or input logistics data to database 102 through electronic data interchange 116 and middleware 104. [0051] Referring now to FIG. 2, one embodiment of database 102 is illustrated in more detail. Database 102 includes a number of data tables, for example at least 100 tables to 200 tables, or for example, 197 tables. For purposes of illustration, database 102 includes Table 1 201, Table 2 202, Table 3 203, Table 4 204, Table 5 205, Table 6 206, Table 7 207, Table 8 208, Table 9 209, and Tables 10-197 210-397. Table 1 201 includes Data Record 1 400 to Data Record N 401 which each have Company Code 402, Location Code 404, Data Field 3 406, Data Field 4 408, Data Field 5 410, Data Field 6 412, and Data Field 7 414. Table 2 202 to Table 197 397 may also have Company Code 402 and/or Location Code 404. [0052] In one embodiment, a unique identifier, such as for example, Company Code 402 may be used to identify data incorporated into database 102 as coming from a source of the data. For example, before data is incorporated into database 102, a unique identifier is applied to the data to identify the source of the data within database 102. The unique identifier may remain associated with the data so long as the data is stored in database 102. [0053] Referring now to FIG. 3, one embodiment of middleware 104 is illustrated in more detail. Middleware 104 includes application server 502, report generator 504, program components 506, and print servers 508. Application server 502 is connected to report generator 504, program components 506, and print servers 508. Report generator 504 is connected to print servers 508.

[0054] Referring now to FIG. 4, in another embodiment, a data management system, such as for example, logistics supply chain 600, is illustrated. Logistics supply chain 600 includes Supplier A 602, which gives product to Trucking Company A 604, which delivers product to Rail Company A 606, which delivers product to Trucking Company B 608, which delivers product to Customer A 610. The product may be associated with a unique identifier representing the source of the product provided by Supplier A and such association is maintained throughout the delivery process until the product is delivered to Customer A 610. [0055] Information on the movement of the product may be delivered to, stored, and/or accessed from System A 612, for example system 100. Information on the movement of the product may also be delivered to, stored, and/or accessed from System B 616, for example system 100.

[0056] Supplier A 602 is connected to System A 612 by Connection A 614. Trucking Company A 604 is connected to Internet 614 by Connection 620. Trucking Company A 604 may access System A 612 by Connection 628 and/or System B 616 by Connection 630. Rail Company A 606 is connected to Internet 614 by Connection 622. Rail Company A 606 may access System A 612 by Connection 628 and/or System B 616 by Connection 630. Trucking Company B 608 is connected to Internet 614 by Connection 624. Trucking Company B 608 may access System A 612 by Connection 628 and/or System B 616 by Connection 630. Customer A 610 is connected to System B 616 by Connection 626. [0057] System A 612 is able to synchronize with System B 616 and vice versa through Internet 614 by Connections 628 and 630, for example daily, hourly, each minute, or a "put and get" synchronization. One or more of connections 618, 620, 622, 624, 626, 628, and/or 630 may be made over the Internet.

[0058] Using System A 612, Supplier A 602 is able to track the movements of packages, each associated with a unique identifier representing the source of the package, to Customer A 610 and to other customers (not shown). Supplier A 602 may only make the movements of packages to Customer A 610 available to Trucking Company A 604, Rail Company A 606, Trucking Company B 608, and Customer A 610, and not make the movements of packages to other customers available.

[0059] Similarly, Customer A 610 is able to track the movements of packages from Supplier A 602 and from other suppliers (not shown) using System B 616. Customer A 610 may only make the movements of packages from Supplier A 602 available to Supplier A 602, Trucking Company A 604, Rail Company A 606, and Trucking Company B 608, and not make the movements of packages from other suppliers available.

[0060] Referring now to FIG. 5, one embodiment of method 700 of creating a database, for example database 102 is illustrated. At step 702, a plurality of data tables are created, for example Table 1 201 - Table 197 397 (from FIG. 2). At step 704, one or more common data fields between the tables are linked to each other to create a relational database, for example data fields 402 and/or 404 (from FIG. 2). At step 706, the tables are populated with data, for example record 1 400 to record N 401. At step 708, database 102 may be used to access the data from the tables.

[0061] Referring now to FIG. 6, one embodiment of method 800 of using a shipper's destination profile is illustrated. At step 801 , a shipper's destination profile number is defined. At step 803, the shipper's destination profile is populated with information regarding the delivery location, for example manually or by electronic data interchange. At step 805, a purchase order may be entered into one or more tables of database 102. At step 807, the shipper's destination profile number is linked to the purchase order (P/O) At step 809, items on the P/O may be linked to the shipper's destination profile. A shipper's destination profile is a unique combination of a shipper/customer's delivery location and packing specifications. In one embodiment, a shipper's destination profile may be provided for each logical grouping of materials per delivery location. For example, for a construction project, all of the cement, steel, and bricks may be grouped into a single shipper's destination profile to be delivered to the construction site, a second shipper's destination profile may be created for the delivery of all of the wiring, electrical, and electronic equipment, and a third shipper's destination profile may be created for the chemicals, and other hazardous materials. [0062] In one embodiment, shipper's destination profile 644 may be used to control the first level of packing, for example where shipments are supposed to go. Shipper's destination profile 644 may include one or more functional flags.

[0063] In another embodiment, shipper's destination profile 644 includes a company code, customer number, an associated purchase order or purchase order prefix, an associated purchase order suffix, a request for quotation prefix/suffix, port of discharge/ destination, one or more special codes, associated rate charge, and/or ship to/notify. [0064] Referring back to FIG. 1 , in one embodiment, web server 106 may be a conventional web server, for example a J2E application server commercially available from BEA Systems, Inc., under the trade name WebLogic Application Server, at http://www.bea.com. In another embodiment, web server 106 may be an Tomcat web server, commercially available from The Apache Software Foundation, at Apache.org, Project Jakarta. In one embodiment, electronic data interchange 116 may be a conventional electronic data interchange adapted to handle different formats of incoming data, such as for example, data received in system 100 format or data received in a non-system 100 format. The system 100 formatted data may be passed through to middleware 104 without reformatting. Whereas the non-system 100 formatted data may require reformatting prior to being transferred to the middleware for storing in database 102. In addition, electronic data interchange 116 may be adapted to convert data received from database 102 to any format other than system 100 format to accommodate any type of data source interfacing with system 100.

[0065] In one embodiment, if electronic data interchange 116 is used to transfer data from a system that has already assigned a unique identifier associated with the source of the data, to the data, the unique identifier may also be transferred into system 100. In another embodiment, if electronic data interchange 116 is used to transfer data from a system that has not already assigned a source unique identifier to the data, the unique identifier may be assigned by system 100.

[0066] In one embodiment, users 108-114 may connect to web server 106 using a computer, an internet connection, and a commercially available web browser, for example Microsoft Internet Explorer or Netscape Navigator, commercially available from Netscape Communications Corp.

[0067] In one embodiment, database 102 may be any conventional database or storage medium. In another embodiment, database 102 is created and/or maintained on a SQL Server, for example SQL Server 2000 commercially available from Microsoft Corporation at http://www.microsoft.com/. In another embodiment, database 102 may be created and/or maintained on a Oracle Database Server, for example Oracle 9i commercially available from

Oracle Corp. at http://www.oracle.com/.

[0068] In one embodiment, application server 502 of middleware 104 may be a conventional application server, for example an application server commercially available from BEA Systems, under the trade name WebLogic Application Server, at http://www.bea.com/.

[0069] In one embodiment, report generator 504 of middleware 104 may be a conventional report generator, for example a Java-based report generator commercially available from Jinfonet Software, under the trade name JReports, at http://jinfonet.com. In another embodiment, report generator 504 may include one or more templates for reports.

[0070] In one embodiment program components 506 of middleware 104 are developed in Java to the J2EE 1.4 Specification, commercially available from Sun Microsystems at http://www.sun.com/. In one embodiment, program components 506 provide for interaction between different parts of system 100 and/or the users. For example, one program component could be an RF scanning interface to input data scanned from a barcode by a handheld scanning device into system 100 or a purchase order entry function to enter information from a purchase order in to system 100.

[0071] In one embodiment, print servers 508 of middleware 104 may be conventional print servers, for example print servers commercially available from Loftware, under the trade name Loftware Enterprise Print Server, at http://www.loftware.com.

[0072] Referring to Figure 2, in one embodiment, company code 402 is a three digit unique identifier made up of three letters and/or numbers selected from 0-9 and A-Z, for

46,656 unique combinations. In another embodiment, company code 402 is a four digit unique identifier made up of four letters and/or numbers selected from 0-9 and A-Z, for greater than 1.6 million unique combinations.

[0073] In one embodiment, location code 404 is a two digit unique identifier made up of two letters and/or numbers selected from 0-9 and A-Z, for 1296 unique combinations, which may be used to identify different locations within each company.

[0074] In another embodiment, one or more other tables 202-397 may also include a company code and a location code, for example company code 402 and location code 404, and also include at least one other data field.

[0075] Referring now to FIGS. 7-32, in another embodiment, a system and a method are illustrated for managing data in a logistics process. Referring first to FIG. 7, an example of system 100, system 900 is provided to manage information on the flow of products from supplier/vendor 902 to a transportation entity 904, such as for example, a third-party logistics provider/freight forwarder, carrier, or freight handler, by ship 906 to shipper/customer 908. As illustrated, supplier/vendor 902 and third-party logistics provider/freight forwarder 904 are located in country A 910, while shipper/customer 908 are located in country B 912, and ship 906 traverses ocean 914 to deliver products to shipper/customer 908. In another embodiment, system 900 could also be used to manage information on the domestic flow of products, or for any number of international variations.

[0076] In one embodiment, shipper/customer 908 hires third-party logistics provider/freight forwarder 904 to manage the logistics of supply movements, for example to expedite materials, group materials, send materials to the desired locations, pack materials, arrange for shipments, and track shipments.

[0077] Referring now to FIG. 8a, process 1000 using system 900 is illustrated. At step 1002, shipper/customer 908 issues a purchase order (P/O) which is received by supplier/vendor 902 and third-party logistics provider/freight forwarder 904. In one embodiment, shipper/customer 908 may issue the purchase order directly to third-party logistics provider/freight forwarder 904 by electronic data interchange ("EDI"), and in another embodiment the purchase order may be issued on paper. After receiving the P/O, third- party logistics provider/freight forwarder 904 creates a record in system 900 including the P/O information. In one embodiment, shipper/customer 908 may be working on a project which has a master requisition or bill of materials to cover all of the materials needed for the project. From this "master" multiple purchase orders may be issued to various suppliers and third-party logistics providers to ship all the materials to the desired location. [0078] Also at step 1002, third-party logistics provider/freight forwarder 904 assigns the purchase order to a shipper's destination profile within relevant P/O record within system 900. A shipper's destination profile is a unique combination of shipper/customer's 908 delivery location and packing specifications. In one embodiment, a shipper's destination profile may be provided for each logical grouping of materials per delivery location. For example, for a construction project, all of the cement, steel, and bricks may be grouped into a single shipper's destination profile to be delivered to the construction site, a second shipper's destination profile may be created for the delivery of all of the wiring, electrical, and electronic equipment, and a third shipper's destination profile may be created for the chemicals, and other hazardous materials.

[0079] At step 1004, third-party logistics provider/freight forwarder 904 receives freight shipped from supplier/vendor 902. Third-party logistics provider/freight forwarder 904 supplies a unique identifier to the freight, for example a barcode. In one embodiment, a barcode including a unique identifier is applied to the smallest identifiable unit received as a part of the shipment. The barcode may include the following: a unique company code of the company that applied the barcode; a location code to identify the location of the company applying the barcode; and a package identifier to identify which package at the company location received the barcode.

[0080] At step 1006, the freight is checked by verifying the product received at step 1004 with the purchase order received at step 1002 by accessing purchase order within system 900. In one embodiment, the boxes received and/or the documents associated with the shipment received may be labeled with the unique identifier and a purchase order or requisition number, which can be used to associate each box received with a purchase order.

[0081] At step 1006, the purchase order product line items and quantities within system 900 are compared to the contents of the boxes received that are associated with the purchase order, by accessing purchase order within system 900.

[0082] At step 1008, a material receipt (MR) is issued from system 900. The material receipt is an official statement of what was received in the shipment. In one embodiment, steps 1006 and 1008 are done at the same time. For each shipment, the associated purchase order is pulled up on a computer (not shown) from system 900, and available items in the purchase order that have not yet been received are highlighted. The highlighted items are identified in the shipment, then the barcode of the shipment item is scanned to identify that one or more of the highlighted items has been received in the shipment, and the item is no longer highlighted on the purchase order. During this process, as a received product is associated with the purchase order, the shipper's destination profile of the purchase order is associated within system 900 with each product that is received on that purchase order. [0083] After all of the received items have been associated within system 900 with highlighted items on the purchase order, the quantities are compared between the items received and the purchase order items. If the received items match the quantities for the purchase order items, then there are no problems. If there were too many items received as compared to the purchase order, then an overage error is generated for that purchase order by system 900, for example to the worker who is receiving the shipment. If there were too few items received as compared to the purchase order, then an underage or shortage error is generated for the purchase order by system 900. If some of the items were damaged as received, then a damage error is generated for the purchase order by system 900. Any such errors within system 900 must be resolved prior to proceeding to 1010, for example by removing the excess items from the purchase order, receiving additional items to add to the purchase order, or by receiving replacement items to replace damaged items. [0084] At step 1010, one or more products are grouped together and associated within system 900 and released to pack (RTP). At step 1010, a pick ticket and/or a packing list are generated from system 900.

[0085] At step 1012, all of the products on each pick ticket and/or packing list from 1010 are marshaled together into one area at third-party logistics provider/freight forwarder's 904 warehouse, for example a pull to pack step (PTP).

[0086] At step 1014, all of the marshaled products from 1012 are overpacked, for example, boxed together. During this procedure, the warehouse worker scans or otherwise inputs the release to pack job (RTP) or pick ticket from 1010, then places a barcode with a unique identifier on the box or other container in which the products will be placed, to associate this pick ticket with the appropriate box in system 900. As each item is placed into the box, the barcode is scanned to ensure that the product belongs on the appropriate pick ticket with the other products being placed in the box, and system 900 is updated with each barcode is scanned, for example by a batch update or a continuous update. If the warehouse worker scans a product not on the pick ticket to place in the box, an error code is generated on the worker's scanner to let him know that that product does not belong. At the end of the packing, all of the materials on the pick ticket must have been scanned and placed in boxes, otherwise an error message is generated.

[0087] Referring to figure 8b, in another embodiment, at step 1015, a forwarder reference is provided by system 900, including, for example, a file number, a shipment number, or a house or consolidator number. Alternatively, for example, all the routing and route information, and/or the documentation for a route to move the product from third-party logistics provider 904 to shipper/customer 908 may be provided.

[0088] At step 1016, the containers are released to deliver and a delivery ticket is printed from system 900. The delivery ticket may contain such information as: supplier/vendor 902, third-party logistics provider/freight forwarder 904, shipment method, shipper/customer 908, shipper's destination profile (where the products are to be delivered), how many containers there are in the shipment, identification of the smaller packages within the containers, and items contained in each of the smaller packages. This information allows an employee at shipper/customer 908 to easily locate a specific item out of all of the containers and packages.

[0089] At step 1018, the delivery ticket from 1016 is verified as the containers to be shipped are loaded onto ship 906. First, the delivery ticket is scanned, then as each container is loaded, the container is scanned to associate the container with the delivery ticket and to verify that the container has been shipped, within delivery ticket record in system 900. The delivery ticket is verified when all of the containers on the ticket have been scanned and placed on ship 906.

[0090] At step 1020, the containers on the delivery ticket are in transit on ship 906 crossing ocean 914 from third-party logistics provider/freight forwarder 904 to shipper/customer 908.

[0091] At step 1022, shipper/customer 908 takes delivery of the containers. Shipper/customer 908 may then unpackage the containers as desired to get the items, overpack the containers into larger containers to be shipped somewhere else, and/or repackage the containers to be shipped somewhere else. In one embodiment, shipper/customer 908 scans the containers as they arrive, and updates system 900 to show that the containers are now at shipper/customer's 908 location.

[0092] In other embodiments, different types of barcodes including the unique identifier may be utilized in the logistics process. For example, barcodes may be used in the following labels: a unique box ID label; an inventory location label; markings label; or a delivery ticket label.

[0093] Referring now to FIGS. 9-11 , different views of a purchase order record that may be stored in system 900 and/or system 100, accessed by a web browser, for example Internet Explorer, and received by third-party logistics provider/freight forwarder 904 at step 1002 are illustrated. Referring first to FIG. 9, the details screen of purchase order 1100 includes the following: unique purchase order number 1101 assigned by system 900 as purchase order 1100 is received, in this case be BU030804B; company code field 1102 referring to the third-party logistics provider/freight forwarder 904, in this case Dragon; destination 1104 for the products, in this case Rio de Janeiro; transportation method 1106 for the products, in this case air freight; supplier/vendor 1108 for the products, in this case Abco; customer name 1110 of shipper/customer 908 who will receive the products, in this case Excel; and products 1112 that will be shipped. Several different view tabs 1114 may be provided to allow a user to toggle between the screens details, such as, for example, haz/other, xref/rem/ship via, and SDP/expedite.

[0094] Referring now to FIG. 10, the SDP/expedite screen of purchase order 1100 includes the following: unique purchase order number 1101 assigned by system 900 as purchase order 1100 is received, in this case be BU030804B; company code field 1102 referring to the third-party logistics provider/freight forwarder 904, in this case Dragon; destination 1104 for the products, in this case Rio de Janeiro; customer name 1110 of shipper/customer 908 who will receive the products, in this case Excel; products 1112 that will be shipped; and shipper's destination profile 1116, a unique product grouping, destination, transportation type combination for products 1112, in this case Rio 182-D. [0095] Referring now to FIG. 11, purchase order item 1120 detail is presented. Purchase order item 1120 includes purchase order number 1101 , company code field 1102, transportation method 1106, vendor 1108, products 1112, purchase order item number 1122, product quantity 1124, and product price 1126. Purchase order item 1120 provides additional detail concerning one of products 1112 from purchase order 1100. [0096] Referring now to FIGS. 12-13, different views of a receiving entry record that may be stored in system 900 and/or system 100, accessed by a web browser, for example Internet Explorer, and generated by third-party logistics provider/freight forwarder 904 at step 1004 are illustrated. Referring first to FIG. 12, receiving entry record 1200 includes unique receiving entry information 1202 assigned by system 900 as receiving entry record 1200 is received. For example, receiving entry information 1202 is illustrated as DRG HO 2004 03 08 0007, where DRG is the three digit company code representing Dragon, HO is the two digit location code representing Dragon's Houston location, 2004 03 08 is the date March 8, 2004 identifying the date the shipment is received, and 0007 represents the number shipment of the day, in this case, the seventh shipment of the day that DRG's Houston location received.

[0097] Receiving entry information 1202 also includes the information that three packages were received in this shipment. Receiving date 1204 represents the date the shipment was received, in this case March 8, 2004. Supplier 1208 is the entity that shipped the shipment, this case Acme, Inc.

[0098] Also included on receiving entry record 1200 are customer name 1210 of shipper/customer 908 for whom the packages are received, in this case Excel and packages 1212 that were received, in this case three packages. Packages 1212 are sequentially numbered as they arrive, and are then or later associated with a purchase order, in this case purchase order number 1101. Several different view tabs 1214 are provided to allow a user to toggle between the screens details, apply to packages, intransit information, and charges. [0099] Referring now to FIG. 13, receiving item entry 1220 is illustrated, for the second package of the three package receiving entry record 1200. Receiving item entry record 1220 includes receiving entry number 1202, receiving date 1204, supplier number 1208, package type 1222, and barcode number 1224. Purchase order number 1101 is also provided to associate this package with a particular purchase order. Several different view tabs 1214 are provided to allow a user to toggle between general information, additional information, intransit information, and charges.

[00100] Referring now to FIGS. 14-17, different views of a material receipt entry record that would be stored in system 900 and/or system 100 and accessed by a web browser, for example Internet Explorer, and generated by third-party logistics provider/freight forwarder 904 at step 1008 are illustrated. Referring first to FIG. 14, a first tab of material receipt entry 1300 includes the following: material receipt number 1302, in this case 2004 030 8007; associated barcode number 1224, in this case 04000088A; carrier 1306, in this case Great Transportation Services Inc.; and material receipt items 1308, in this case nine staplers. Also part of material receipt entry 1300 are purchase order number 1101 , customer 1210, package type 1222, destination 1104, vendor 1108, supplier 1208, and transportation method 1106 (from purchase order 1100 and/or receiving entry 1200). [00101] Referring now to FIG. 15, a second tab of material receipt entry 1300 includes material receipt number 1302, in this case 2004 030 8007; associated barcode number 1224, in this case 04000088A; and material receipt items 1308, in this case nine staplers, checked date 1310, material receipt date 1312, released to pack date 1314, packed date 1316, delivered date 1318, and delivery ticket number 1320. Also part of this tab of material receipt entry 1300 are purchase order number 1101, customer 1210, and receiving date 1204 (from purchase order 1100 and/or receiving entry 1200).

[00102] Referring now to FIG. 16, a third tab of material receipt entry 1300 includes: material receipt number 1302, in this case 2004 030 8007; associated barcode number 1224, in this case 04000088A; and material receipt items 1308, in this case nine staplers. Also part of this tab of material receipt entry 1300 are purchase order number 1101, customer 1210, and shipper's destination profile 1116, in this case Rio 182 - D. [00103] Referring now to FIG. 17, material receipt item entry 1330 is illustrated. Material receipt item entry 1330 includes: material receipt number 1302, in this case 2004 030 8007; associated barcode number 1224, in this case 04000088A; material receipt items 1308, in this case nine staplers; and tabs 1332 which allow a user to switch between screens of material receipt item entry 1330. Also included are purchase order number 1101 , customer 1210, transportation method 1106, and supplier 1208.

[00104] Referring now to FIGS. 18-19, different views of a release to pack entry record that would be stored in system 900 and/or system 100 and accessed by a web browser, for example Internet Explorer, and generated by third-party logistics provider/freight forwarder 904 at step 1010 are illustrated. Referring first to FIG. 18, a first tab of release to pack item entry 1400 includes: release to pack job number 1402, in this case DRGHOHOR15 00195; packing due date on 1404, in this case March 8, 2004 at 16:00; hazardous material indicator 1406, in this case no hazardous materials; packing and handling instructions 1408, in this case "keep dry" and "do not stack"; and packing list number 1410, in this case PHO 0402683. Also part of release to pack item entry 1400 are third-party logistics provider/freight forwarder 1102, in this case Dragon's Houston location; customer 1210, in this case Excel; and transportation method 1106. [00105] Referring now to FIG. 19, a second tab of release to pack item entry 1400 includes the following: release to pack job number 1402, in this case DRGHOHOR15 00195; and assigned material receipt packages 1412. Also part of release to pack item entry 1400 are third-party logistics provider/freight forwarder 1102, in this case Dragon's Houston location; customer 1210, in this case Excel; transportation method 1106, in this case air freight A; shipper's destination profile 1116, in this case Rio 182 - D; material receipt numbers 1302, in this case 2004 0308 0007 0002 and 2004 0308 0007 0003; and associated purchase order number 1101 , in this case BU0300804B.

[00106] Referring now to FIGS. 20-21 , different views of a packing list entry record that would be stored in system 900 and/or system 100 and accessed by a web browser, for example Internet Explorer, and generated by third-party logistics provider/freight forwarder 904 at step 1012 are illustrated. Referring first to FIG. 20, a first tab of packing list entry 1500 is illustrated. Packing list entry 1500 includes packing list number 1502 and package markings 1504. Also part of packing list entry 1500 are the following: third-party logistics provider/freight forwarder 1102, in this case Dragon's Houston location; customer 1210, in this case Excel; transportation method 1106, in this case air freight (A); and destination 1104, in this case Rio de Janeiro (from purchase order 1100 and/or receiving entry 1200 and/or material receipt entry 1300 and/or release to pack item entry 1400). [00107] Referring now to FIG. 21 , a second tab of packing list entry 1500 is illustrated. Packing list entry 1500 includes the following: packing list number 1502, boxes 1510 associated with a packing list, in this case only one box; packing list box numbers 1512, in this case only box number 1 ; and box numbers 1514 associated with each packing list box number 1512. Also part of packing list entry 1500 is third-party logistics provider/freight forwarder 1102, in this case Dragon's Houston location (from purchase order 100 and/or receiving entry 1200 and/or material receipt entry 1300 and/or release to pack item entry 1400).

[00108] Referring now to FIGS. 22-25, different views of a box entry record that would be stored in system 900 and/or system 100 and accessed by a web browser, for example Internet Explorer, and generated by third-party logistics provider/freight forwarder 904 at step 1014 are illustrated. Referring first to FIG. 22, a first tab of box entry 1600 is illustrated. Box entry 1600 includes the following: package type 1602, in this case book; package markings 1604; delivery ticket number 1606, in this case DD4000009; and box weights and dimensions 1608. Also part of box entry 1600 is third-party logistics provider/freight forwarder 1102, in this case Dragon's Houston location; release to pack job number 1402, in this case 00195; packing list number 1502, in this case PHO 0402683; packing list box number 1512, in this case box number 1 ; and customer 1210, in this case Excel having customer number 781903 (from purchase order 1100 and/or receiving entry 1200 and/or material receipt entry 1300 and/or release to pack item entry 1400 and/or packing list entry 1500).

[00109] Referring now to FIG. 23, a second tab of box entry 1600 is illustrated. Box entry 1600 includes the following: delivery ticket number 1606, in this case DD4000009; hazardous material notes 1610; and customs notes 1612. Also part of box entry 1600 is third-party logistics provider/freight forwarder 1102, in this case Dragon's Houston location; release to pack job number 1402, in this case 00195; packing list number 1502, in this case PHO 0402683; packing list box number 1512, in this case box number 1 ; and customer 1210, in this case Excel having customer number 781903 (from purchase order 1100 and/or receiving entry 1200 and/or material receipt entry 1300 and/or release to pack item entry 1400 and/or packing list entry 1500).

[00110] Referring now to FIG. 24, a third tab of box entry 1600 is illustrated. Box entry 1600 includes the following: delivery ticket number 1606, in this case DD4000009; and packing hierarchy 1614, in this case packed to level 1. Also part of box entry 1600 is third- party logistics provider/freight forwarder 1102, in this case Dragon's Houston location; release to pack job number 1402, in this case 00195; packing list number 1502, in this case PHO 0402683; packing list box number 1512, in this case box number 1; and customer 1210, in this case Excel having customer number 781903 (from purchase order 1100 and/or receiving entry 1200 and/or material receipt entry 1300 and/or release to pack item entry 1400 and/or packing list entry 1500).

[00111] Referring now to FIG. 25 a fourth tab of box entry 1600 is illustrated. Box entry 1600 includes the following: delivery ticket number 1606, in this case DD4000009; and packed packages 1616 associated with this box, in this case DRGHO 2004 030 8000 7000 2 and DRGHO 2004 030 8000 7000 3. Also part of box entry 1600 is third-party logistics provider/freight forwarder 1102, in this case Dragon's Houston location; release to pack job number 1402, in this case 00195; packing list number 1502, in this case PHO 0402683; packing list box number 1512, in this case box number 1 ; and customer 1210, in this case Excel having customer number 781903 (from purchase order 1100 and/or receiving entry 1200 and/or material receipt entry 1300 and/or release to pack item entry 1400 and/or packing list entry 1500).

[00112] Referring now to FIGS. 26-28, different views of a delivery ticket entry record that would be stored in system 900 and/or system 100 and accessed by a web browser, for example Internet Explorer, and generated by third-party logistics provider/freight forwarder 904 at step 1016 are illustrated. Referring first to FIG. 26, a first tab of delivery ticket entry 1700 is illustrated. Delivery ticket entry 1700 includes the following: package details 1702; delivery ticket number 1606, in this case DD4000009; carrier 1704, in this case Varco; origin 1706, in this case Bush Intercontinental Airport in Houston; and delivery type 1708, in this case standard delivery. Also part of delivery ticket entry 1600 is the following: third-party logistics provider/freight forwarder 1102, in this case Dragon's Houston location; and customer 1210, in this case Excel having customer number 781903 (from purchase order 1100 and/or receiving entry 1200 and/or material receipt entry 1300 and/or release to pack item entry 1400 and/or packing list entry 1500 and/or box entry 1600). [00113] Referring now to FIG. 27, a second tab of delivery ticket entry 1700 is illustrated. Delivery ticket entry 1700 includes the following: delivery ticket number 1606, in this case DD4000009; delivery type 1708, in this case standard delivery; and package assignment 1710. Also part of delivery ticket entry 1600 includes the following: third-party logistics provider/freight forwarder 1102, in this case Dragon's Houston location; box number 1514, in this case DRGHOHOR 1500286; and customer 1210, in this case Excel having customer number 781903 (from purchase order 1100 and/or receiving entry 1200 and/or material receipt entry 1300 and/or release to pack item entry 1400 and/or packing list entry 1500 and/or box entry 1600).

[00114] Referring now to FIG. 28, a third tab of delivery ticket entry 1700 is illustrated. Delivery ticket entry 1700 includes the following: delivery ticket number 1606, in this case DD4000009; delivery type 1708, in this case standard delivery; and load costs 1712. Also part of delivery ticket entry 1600 includes the following: third-party logistics provider/freight forwarder 1102, in this case Dragon's Houston location; and customer 1210, in this case Excel having customer number 781903 (from purchase order 1100 and/or receiving entry 1200 and/or material receipt entry 1300 and/or release to pack item entry 1400 and/or packing list entry 1500 and/or box entry 1600).

[00115] Referring now to FIGS. 29-31 , different views of a shipper's destination profile that would be stored in system 900 and/or system 100, and generated by third-party logistics provider/freight forwarder 904 for use with process 1000, and which may be used with purchase order 1100 and/or receiving entry 1200 and/or material receipt entry 1300 and/or release to pack item entry 1400 and/or packing list entry 1500 and/or box entry 1600 and/or delivery ticket entry 1700, is illustrated. Referring first to FIG. 29, general information regarding a shipper's destination profile is illustrated. Shipper's destination profile entry 1800 includes the following: third-party logistics provider/freight forwarder 1102, in this case Dragon; customer 1210, in this case Excel having customer number 781903; shipper's destination profile 1116, in this case Rio 182 - D; and flags 1802 which may be turned on or off for this shipper's destination profile. [00116] Referring now to FIG. 30, marking information regarding a shipper's destination profile is illustrated. Shipper's destination profile entry 1800 includes the following: third- party logistics provider/freight forwarder 1102, in this case Dragon; customer 1210, in this case Excel having customer number 781903; shipper's destination profile 1116, in this case Rio 182 - D; and package markings 1504 which are provided on each package associated with this shipper's destination profile 1116.

[00117] Referring now to FIG. 31, group box identification information regarding a shipper's destination profile is illustrated. Shipper's destination profile entry 1800 includes the following: third-party logistics provider/freight forwarder 1102, in this case Dragon; customer 1210, in this case Excel having customer number 781903; shipper's destination profile 1116, in this case Rio 182 - D; and group box identification 1804, to group packages together sharing common characteristics within this shipper's destination profile 1116. [00118] Referring now to FIG. 32, a selection of customer update flags that would be stored in system 900 and/or system 100, and generated by third-party logistics provider/freight forwarder 904 for use with process 1000, is illustrated. Customer update flags 1900 includes customer 1210, in this case Excel and packing flags 1902 which may be turned on or off for shipments to this customer.

[00119] Connection between system 900 and users may be made by any appropriate mechanism, for example, in one embodiment, system 900 is available to third-party logistics provider/freight forwarder 904, and optionally supplier/vendor 902 and/or shipper/customer 908, as a web-based Java application. In another embodiment, system 900 is available to third-party logistics provider/freight forwarder 904, and optionally supplier/vendor 902 and/or shipper/customer 908, as a terminal-based mainframe application.

[00120] The barcode and/or data associated with the barcode may be in any format sufficient to identify a company. For example, in one embodiment, the barcode and/or a data entry associated with the barcode begins with a three digit company unique identifier to identify third-party logistics provider/freight forwarder 904 as receiving the freight, followed by a two digit location code, which identify the specific location of third-party logistics provider/freight forwarder 904 which received the freight. In this embodiment, there is provided 46,656 unique company combinations based on the three digit company identifier, made up of three digits chosen from 1-0 and A-Z, to provide the combinations 111 - ZZZ. In this embodiment, there is also provided 1296 unique location combinations per company based on the two digit company identifier, made up of two digits chosen from 1-0 and A-Z, to provide the combinations 11 - ZZ. [00121] An example of barcode may include, the data entry associated with the barcode such as the date, the shipment of the day, and the package of the shipment. For example, a barcode having characters "123 HO 2004 03 11 017 003" represents the information of:

Company X having company code 123; at Company X's Houston location having location code HO; on the date March 11 , 2004 represented as 2004 03 11 ; for the 17th shipment received in the morning represented as 017; and that Company X received the third box of the 17th shipment. [00122] In this embodiment, one or more barcodes having characters "123 HO 2004 03 11 017 000" representing the "zero box" of the 17th shipment, may be applied to the shipping and receiving documents to associate the boxes received and the shipment with the shipping and receiving documents. This allows the persons processing the paperwork to scan the papers, and associate all the boxes in the shipment with one or more purchase orders received at step 1002.

[00123] Referring back to Figs. 8a, 8b, and 9, in one embodiment, freight may be received at step 1004 prior to receiving a purchase order at step 1002, and in another embodiment, the purchase order may be received at step 1002 prior to receiving the freight at step 1004.

[00124] At step 1010 in one embodiment, multiple products are grouped by shipper's destination profile, transportation method, and/or hazardous or nonhazardous materials. For example, all of the hazardous materials traveling to shipper/customer 908 by ship 906 may be grouped onto one packing list/pick ticket, while the non-hazardous materials traveling to shipper/customer 908 by airfreight may be grouped onto a different packing list/pick ticket. [00125] At step 1014, in another embodiment, multiple boxes from one pick ticket may be consolidated into a single larger container. This larger container is also supplied with a barcode with a unique identifier to create an association in system 900 between the larger container, the boxes within the larger container, and the products from the pick ticket within the boxes. In another embodiment, multiple boxes from different pick tickets sharing the same shipper's destination profile may be consolidated into a single larger container. [00126] At step 1014, in another embodiment, packages may be overpacked up to eight times. For example, multiple items in a bag, multiple bags packed into a carton, multiple cartons into a case, multiple cases into a box, and multiple boxes into a container, for five times over packing.

[00127] Referring now to FIG. 33, in an embodiment, logistics supply chain 2000 is shown. Product a 2002 has Barcode a 2004 attached thereto. Product a 2002 is packed with other products, for example product b, product c, and product d (not shown), into Box 1 2006, and Box 1 2006 is closed and sealed. Box 1 2006 has Barcode 1 2008. Box 1 2006 is then packed with other boxes, for example box 2, box 3, and box 4 (not shown), into

Container A 2010, and Container A 2010 is closed and sealed. Container A 2010 has

Barcode A 2012 attached. Container A 2010 is then placed on Truck I 2014 with other containers. Barcode I 2016 is attached to Truck I 2014.

[00128] Truck I 2014 is then moved to a first desired location, where Container A 2010 is transferred to Railcar 2018 with other containers. Railcar Barcode 2020 is attached to

Railcar 2018. Railcar 2018 is then moved to a second desired location, where Container A

2010 is transferred to Truck II 2022 with other containers. Barcode II 2024 is attached to

Truck II 2022.

[00129] Truck II 2022 is then move to a third desired location where Container A 2010 is opened and unloaded. Box 1 2006 is removed from Container A 2010 along with other boxes in Container A 2010. Box 1 2006 is opened and unloaded. Product a 2002 is removed from Box 1 2006 along with other products in Box 1 2006.

[00130] In one embodiment, a scanner is directly connected, for example by wire, to a system which tracks logistical information of the products, which can be used to scan the barcodes of the products. In another embodiment, a scanner may be used which has a memory device to store the scanned barcodes, which may then transmit by radio frequency or store the data for later connection to a system which tracks logistical information of the products.

[00131] Referring now to FIG. 34, in another embodiment, logistics supply chain 2100 is illustrated. Logistics supply chain 2100 includes Supplier A 2102, which gives product to

Trucking Company A 2104, which delivers product to Rail Company A 2106, which delivers product to Trucking Company B 2108, which delivers product to Customer A 2110.

[00132] Information on the movement of the product may be delivered to, stored, and/or accessed from System A 2112, for example system 100. Supplier A 2102 is connected to

System A 2112 by Connection A 2114. Trucking Company A 2104 is connected to System

A 2112 by Connection B 2116. Rail Company A 2106 is connected to System A 2112 by

Connection C 2118. Trucking Company B 2108 is connected to System A 2112 by

Connection D 2120. Customer A 2110 is connected to System A 2112 by Connection E

2122. One or more of connections 2114, 2116, 2118, 2120, and/or 2122 may be made over the Internet, or for example with a wireless connection.

[00133] In one embodiment, Supplier A 2102 receives a purchase order (not shown) from

Customer A 2110 for Product a 2002. Supplier A 2102 then generates a packing slip (not shown) which is sent to the warehouse to pick Product a 2002 off the shelf. As Product a 2002 is picked of the shelf, Barcode a 2004 is scanned and uploaded to System 2112 to indicate that Product a 2002 has been pulled and is being prepared for shipment. [00134] Product a 2002 is then packed with other products into Box 1 2006. Barcode 1 2008 is also scanned to create a record in System A 2112 that associates Product a 2002 with Box 1 2006. This association will show the location of Product a 2002 having the same location of Box 1 2006 until such time as Box 1 2006 is unpacked at a destination. [00135] Box 1 2006 is scanned to indicate that Box 1 2006 has been assembled and is being prepared for shipment. Box 1 2006 is then packed with other boxes into Container A 2010.

[00136] Barcode A 2012 is also scanned to create a record in System A 2112 that associates Box 1 2006 with Container A 2010. This association will show the location of Product a 2002 having the same location as Box 1 2006 until such time as Box 1 2006 is unpacked at a destination, and will show the location of Box 1 2006 having the same location as Container A 2010 until such time as Container A 2010 is unpacked at a destination.

[00137] In this embodiment, the information regarding the packing of Product a 2002 into Box 1 2006, and the packing of Box 1 2006 into Container A 2010 by Supplier A 2102 is transmitted to System A 2112 by Connection A 2114. In one embodiment, the information is inputted by a scanner, for example a hand-held RF scanner. In another embodiment, information is entered by hand on a keyboard. In another embodiment, one or more of Product a 2002, Box 1 2006, and/or Container A 2010 have an identifying tag or transmitter which can be read by readers located at one or more of Supplier A 2102, Trucking Company A 2104, Rail Company A 2106, Trucking Company B 2108, and/or Customer A 2110, to provide the location of Product a 2002, Box 1 2006, and/or Container A 2010 to System A 2112.

[00138] Supplier A 2102 then delivers Container A 2010 to Trucking Company A 2104, which puts Container A 2010 onto Truck I 2014, and creates a record in System A 2112 associating Container A 2010 with Truck I 2014 until such time as Container A 2010 is unloaded from Truck I 2014. Periodically, Trucking Company A 2104 updates the loading time and information, current location, and/or estimated time of arrival of Truck I 2014 to System A 2112 by Connection B 2116, for example by scanning Barcode I 2016, or by other suitable means. This information regarding Truck I 2014 allows the other companies in logistics supply chain 2100 to plan accordingly and monitor the progress. [00139] Trucking Company A 2104 then delivers Container A 2010 to Rail Company A 2106, and creates a record in System A 2112 associating Container A 2010 with Railcar 2018 until such time as Container A 2010 is unloaded from Railcar 2018. Periodically, Rail Company A 2106 updates the loading time and information, current location, and/or estimated time of arrival of Railcar 2018 to System A 2112 by Connection C 2118, for example by scanning Railcar Barcode 2020, or by other suitable means. This information regarding Railcar 2018 allows the other companies in logistics supply chain 2100 to plan accordingly and monitor the progress.

[00140] Rail Company A 2106 then delivers Container A 2010 to Trucking Company B 2108, which puts Container A 2010 onto Truck II 2022, and creates a record in System A 2112 associating Container A 2010 with Truck II 2022 until such time as Container A 2010 is unloaded from Truck II 2022. Periodically, Trucking Company B 2108 updates the loading time and information, current location, and/or estimated time of arrival of Truck II 2022 to System A 2112 by Connection D 2120, for example by scanning Barcode II 2024, or by other suitable means. This information regarding Truck II 2022 allows the other companies in logistics supply chain 2100 to plan accordingly and monitor the progress. [00141] Trucking Company B 2108 then delivers Container A 2010 to Customer A 2110, and creates a record in System A 2112 associating Container A 2010 with Customer A 2110 until such time as Container A 2010 leaves the site of Customer A 2110. Customer A 2110 then proceeds to unpack Container A 2010 by removing Box 1 2006. Customer A 2110 scans Barcode 1 2008 while unpacking to disassociate Box 1 2006 from Container A 2010. Customer A 2110 then proceeds to unpack Box 1 2006 by removing Product a 2002. Customer A 2110 scans Barcode a 2004 while unpacking to disassociate Product a 2002 from Box 1 2006. Customer A 2110 updates System A 2112 with all this information by Connection E 2122, so that the other companies in logistics supply chain 2100 can see that Product a 2002 has successfully reached its destination.

[00142] In one embodiment, System A 2112 may be owned and/or maintained by Supplier A 2102. In another embodiment, System A 2112 may be owned and/or maintained by Trucking Company A 2104. In another embodiment, System A 2112 may be owned and/or maintained by Rail Company A 2106. In another embodiment, System A 2112 may be owned and/or maintained by Trucking Company B 2108. In another embodiment, System A 2112 may be owned and/or maintained by Customer A 2110. In another embodiment, System A 2112 may be owned and/or maintained by a third-party provider, which provides data services regarding logistics supply chain 2100 to one or more of Supplier A 2102, Trucking Company A 2104, Rail Company A 2106, Trucking Company B 2108, and/or Customer A 2110. In another embodiment, one or more other systems (not shown) may be provided and optionally connected to System A 2112 and each other; these one or more other systems may be owned and/or maintained by a third-party provider, Supplier A 2102, Trucking Company A 2104, Rail Company A 2106, Trucking Company B 2108, and/or Customer A 2110.

[00143] Referring now to FIG. 35, in another embodiment, logistics supply chain 2200 is illustrated. Logistics supply chain 2200 includes Supplier A 2202, which gives product to Trucking Company A 2204, which delivers product to Rail Company A 2206, which delivers product to Trucking Company B 2208, which delivers product to Customer A 2210. Information on the movement of the product may be delivered to, stored, and/or accessed from System A 2212, System B 2214, System C 2216, System D 2218, and/or System E 2220, each of which may be configured substantially the same as System 100. [00144] Supplier A 2202 is connected to System A 2212 by Connection 2221. Trucking Company A 2204 is connected to System B 2214 by Connection 2222. Rail Company A 2206 is connected to System C 2216 by Connection 2223. Trucking Company B is connected to System D 2218 by Connection 2224. Customer A 2210 is connected to System E 2220 by Connection 2225.

[00145] System A 2212 is connected to Internet 2260 by Connection 2251. System B 2214 is connected to Internet 2260 by Connection 2252. System C 2216 is connected to Internet 2260 by Connection 2253. System D 2218 is connected to Internet 2260 by Connection 2254. System E 2220 is connected to Internet 2260 by Connection 2255. Connections 2251-2255 allow Systems 2212-2220 to synch data with one another, for example using standard synchronization techniques known in the art. [00146] In one embodiment, Supplier A 2202 receives a purchase order (not shown) from Customer A 2210 for Product a 2002. Supplier A 2202 then generates a packing slip (not shown) which is sent to the warehouse to pick Product a 2002 off the shelf. As Product a 2002 is picked of the shelf, Barcode a 2004 is scanned to indicate that Product a 2002 has been pulled and is being prepared for shipment.

[00147] Product a 2002 is then packed with other products into Box 1 2006. Barcode 1 2008 is also scanned to create a record in System A 2212 that associates Product a 2002 with Box 1 2006. This association will show the location of Product a 2002 having the same location of Box 1 2006 until such time as Box 1 2006 is unpacked at a destination. Box 1 2006 is scanned to indicate that Box 1 2006 has been assembled and is being prepared for shipment. Box 1 2006 is then packed with other boxes into Container A 2010. [00148] Barcode A 2012 is also scanned to create a record in one or more of System A 2212, System B 2214, System C 2216, System D 2218, and/or System E 2220 that associates Box 1 2006 with Container A 2010. This association will show the location of Product a 2002 having the same location as Box 1 2006 until such time as Box 1 2006 is unpacked at a destination, and will show the location of Box 1 2006 having the same location as Container A 2010 until such time as Container A 2010 is unpacked at a destination.

[00149] In this embodiment, the information regarding the packing of Product a 2002 into Box 1 2006, and the packing of Box 1 2006 into Container A 2010 by Supplier A 2202 is transmitted to System 2212 by Connection 2221. In one embodiment, the information is nputted by a scanner, for example a hand-held RF scanner. In another embodiment, nformation is entered by hand on a keyboard. System 2212 may then transmit this nformation to Internet 2260 by Connection 2251 , which may then be transmitted to Systems 2214-2220, to provide the information to Trucking Company A 2204, Rail Company A 2206, Trucking Company B 2208, and/or Customer A 2210, for example by a daily, hourly, or put and get (continuous/real time) synchronization.

[00150] In another embodiment, one or more of Product a 2002, Box 1 2006, and/or Container A 2010 have an identifying tag or transmitter which can be read by readers located at one or more of Supplier A 2202, Trucking Company A 2204, Rail Company A 2206, Trucking Company B 2208, and/or Customer A 2210, to provide the location of Product a 2002, Box 1 2006, and/or Container A 2010 to Systems 2212-2220. [00151] Supplier A 2202 then delivers Container A 2010 to Trucking Company A 2204, which puts Container A 2010 onto Truck I 2014, and creates a record in System 2214 associating Container A 2010 with Truck I 2014 until such time as Container A 2010 is unloaded from Truck I 2014. Periodically, Trucking Company A 2204 updates the loading time and information, current location, and/or estimated time of arrival of Truck I 2014 to System 2214 by Connection 2222, for example by scanning Barcode I 2016, or by other suitable means. This information regarding Truck I 2014 is then synchronized with Systems 2212 and 2216-2220 through Internet 2216, which allows the other companies in logistics Supply Chain 2200 to plan accordingly and monitor the progress of the product movement, for example by a daily, hourly, or put and get (continuous/real time) synchronization. [00152] Trucking Company A 2204 then delivers Container A 2010 to Rail Company A 2206, and creates a record in System 2216 associating Container A 2010 with Railcar 2018 until such time as Container A 2010 is unloaded from Railcar 2018. Periodically, Rail Company A 2206 updates the loading time and information, current location, and/or estimated time of arrival of Railcar 2018 to System C 2216 by Connection C 2223, for example by scanning Railcar Barcode 2020, or by other suitable means (which may be synchronized with systems 2212-2214 and 2218-2220 as above). This information regarding Railcar 2018 allows the other companies in logistics supply chain 2200 to plan accordingly and monitor the progress of the product movement. [00153] Rail Company A 2206 then delivers Container A 2010 to Trucking Company B 2208, which puts Container A 2010 onto Truck II 2022, and creates a record in System 2218 associating Container A 2010 with Truck II 2022 until such time as Container A 2010 is unloaded from Truck II 2022. Periodically, Trucking Company B 2208 updates the loading time and information, current location, and/or estimated time of arrival of Truck II 2022 to System 2218 (which may be synchronized with systems 2212-2216 and 2220 as above), for example by scanning Barcode II 2024, or by other suitable means. This information regarding Truck II 2022 allows the other companies in logistics supply chain 2200 to plan accordingly and monitor the progress of the product movement.

[00154] Trucking Company B 2208 then delivers Container A 2010 to Customer A 2210, and creates a record in System 2220 associating Container A 2010 with Customer A 2210 until such time as Container A 2010 leaves the site of Customer A 2210. Customer A 2210 then proceeds to unpack Container A 2010 by removing Box 1 2006. Customer A 2210 scans Barcode 1 2008 while unpacking to disassociate Box 1 2006 from Container A 2010. Customer A 2210 then proceeds to unpack Box 1 2006 by removing Product a 2002. Customer A 2210 scans Barcode a 2004 while unpacking to disassociate Product a 2002 from Box 1 2006. Customer A 2210 updates System 2220 with all this information (which may be synchronized with systems 2212-2218 as above), so that the other companies in logistics supply chain 2200 can see that Product a 2002 has successfully reached its destination.

[00155] In one embodiment, Systems 2212-2220 may be owned and/or maintained by one or more of Supplier A 2202, Trucking Company A 2204, Rail Company A 2206, Trucking Company B 2208, Customer A 2210, and/or maintained by a third-party provider, which provides data services regarding logistics supply chain 2200 to one or more of Supplier A 2202, Trucking Company A 2204, Rail Company A 2206, Trucking Company B 2208, and/or Customer A 2210.

[00156] In another embodiment, Supplier A 2202 updates System A 2212 by Connection 2221 , and Systems 2212-2220 are connected to each other through Internet 2260 by Connections 2251-2255. In this embodiment, either periodically or continuously, System A 2212 is synchronized with the data in Systems 2214-2220 so that Supplier A 2202 does not need to be directly connected to Systems 2214-2220.

[00157] Referring now to FIG. 36, in another embodiment, logistics supply chain 2400 is illustrated. Logistics supply chain 2400 includes Engine Corp. 2402, Al's Engine Shop 2406, Global Logistics Company 2410, Engine Corp. Warehouse 2414, Car Corp. 2416, and Airplane Corp. 2414. Engine Corp 2402 is connected to System A 2404, for example system 100. Engine Corp Warehouse 2414 is connected to System A 2404. Global Logistics Company 2410 is connected to System B 2412, for example system 100. Airplane

Corp. 2414 is connected to System C 2418, for example system 100.

[00158] Engine Corp. 2402 sells engines to Car Corp. 2416 and Airplane Corp. 2414.

Engine Corp. 2402 contracts with Al's Engine Shop 2406 to manufacture the engines. Al's

Engine Shop 2406 is connected to Internet 2408, which enables Al's Engine Shop 2406 to access System A 2404. As Al's Engine Shop 2406 manufactures an engine, a barcode or other unique identifier is applied to the engine, which information is inputted into System A

2404.

[00159] In one embodiment, the barcode or other unique identifier is unique within logistics supply chain 2400 to Al's Engine Shop 2406, so that anyone who receives the engine and inputs the barcode or other unique identifier into one of Systems 2404, 2412, and/or 2418 will know that the engine originated from Al's Engine Shop 2406.

[00160] System A 2404 is synchronized with System B 2412 and System C 2418 so that

Engine Corp. 2402, Al's Engine Shop 2406, Global Logistics Company 2410, Engine Corp.

Warehouse 2414, Car Corp. 2416, and/or Airplane Corp. 2414 can monitor the status of the engines, for example by a daily, hourly, or put and get (continuous/real time) synchronization.

[00161] Al's Engine Shop 2406 then ships the engine to Global Logistics Company 2410, which scans the barcode or otherwise inputs the unique identifier to associate the engine with Global Logistics Company 2410. This information is then fed to System B 2412, which is synchronized with System A 2404 and System C 2418, as above.

[00162] Global Logistics Company 2410 then transfers the engines to Engine Corp.

Warehouse 2414, where they are held. The warehouse workers receive the engines and scan the barcode placed on by Al's Engine Shop 2406 to update Systems 2404, 2412, and

2418.

[00163] Engine Corp. Warehouse 2414 then ships the engines to Car Corp. 2416 and/or

Airline Corp. 2414 as needed. When Airline Corp. 2414 receives an engine, it updates

System C 2418 with the delivery information. When Car Corp. 2416 receives an engine, it accesses and updates System B 2412 through Internet 2408 with the delivery information.

[00164] Referring now to FIG. 37, in another embodiment, logistics supply chain 2500 is illustrated. Logistics supply chain 2500 includes Refinery 2502, Parts Supplier A 2506, Parts

Supplier B 2510. Refinery 2502 is connected to System A 2504, for example system 100.

System A 2504 is also connected to Internet 2508, allowing Parts Supplier A 2506 and/or

Parts Supplier B 2510 to access System A 2504.

[00165] In this embodiment, Parts Supplier A 2506 and Parts Supplier B 2510 supply some of the exact same parts to Refinery 2502. Prior to shipping parts to Refinery 2502, Parts Supplier A 2506 applies a unique identifier, for example a barcode, to the parts which identify that the parts originated from Parts Supplier A 2506. Similarly, prior to shipping parts to Refinery 2502, Parts Supplier B 2510 applies a unique identifier, for example a barcode, to the parts which identify that the parts originated from Parts Supplier B 2510. [00166] When refinery 2502 receives parts shipped from Parts Supplier A 2506 and/or Parts Supplier B 2510, refinery workers may input the unique identifier to identify where the parts originated from. As Parts Supplier A 2506 and Parts Supplier B 2510 each have unique identifiers applied to every part they ship, there will never be data collisions at refinery 2502 even though some identical parts are shipped from Parts Supplier A 2506 and Parts Supplier B 2510.

[00167] In one embodiment there is disclosed a data management system including a database adapted to contain data, and a server connected to the database adapted to transmit the logistics data to at least one user. In another embodiment, the system also includes a middleware device connected between the database and the web server. In another embodiment, the system also includes an electronic data interchange adapted to transmit data from a user to the database. In another embodiment, the system also includes a report generator. In another embodiment, the system also includes a print server. In another embodiment, at least one table of the database comprises a shipper's destination profile. In another embodiment, at least one table of the database comprises a unique company code data field. In another embodiment, the company code data fields comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters. In another embodiment, the company code data fields comprises three characters. In another embodiment, the company code data fields comprises four characters. In another embodiment, the data includes logistics data.

[00168] In one embodiment, there is disclosed a method of managing information including creating a plurality of data tables, linking each data table with at least one other data table, populating the plurality of data tables with data, and providing access to the data. In another embodiment, providing access to the data comprises generating reports. In another embodiment, providing access to the data comprises connecting a web server to at least one of the data tables. In another embodiment, providing access to the data comprises providing access to the data to selected users over the Internet. In another embodiment, at least one of the data tables comprises a shipper's destination profile data field. In another embodiment, at least one of the data tables comprises a unique company code data field. In another embodiment, each of the data tables comprises a unique company code data field. In another embodiment, the company code data field comprises about 1 to 50 characters; 2- 25 characters; or 3-10 characters. In another embodiment, the company code data field comprises three characters or four characters. In another embodiment, at least one of the data tables also comprises a company location code data field. In another embodiment, the company location code data field comprises two characters. In another embodiment, the data includes logistics data.

[00169] In one embodiment, there is disclosed a system adapted to manage logistics data for a product moving from an initial origin to a destination, including a means to receive a requirement to move the product, a means to locate or receive the product, a means to match the requirement with the product, and a means to ship the product. In another embodiment, the means to receive the requirement comprises electronic data interchange, and wherein the requirement comprises a requisition order, a purchase order, a movement order, or an asset movement order. In another embodiment, the system also includes a means to generate a pick ticket. In another embodiment, the system also includes a means to generate shipping documents. In another embodiment, the system also includes a means to verify that the product being shipped is the same as the product requested on the requirement. In another embodiment, the system also includes a means to monitor the product in transit after being shipped. In another embodiment, the system also includes a means to share the data within the system with a plurality of users. In another embodiment, the means to share the data comprises a Web browser and the Internet. In another embodiment, the system also includes a means to group the product with other products for shipping.

[00170] In one embodiment, there is disclosed a method of managing logistics data from a plurality of shippers to a receiver, including a first shipper assigning a unique first shipper number to a unique identifier, the unique identifier applied to each product shipped from the first shipper to the receiver, and a second shipper assigning a unique second shipper number to a unique identifier, the unique identifier applied to each product shipped from the second shipper to the receiver. In another embodiment, the method also includes at least one of the first shipper and the second shipper applying a barcode to a product. In another embodiment, the method also includes the receiver managing data concerning each product shipped from the first shipper to the receiver based on the unique first shipper number. In another embodiment, the method also includes the receiver managing data concerning each product shipped from the second shipper to the receiver based on the unique second shipper number. In another embodiment, the method also includes the receiver and the first shipper sharing access to a database containing logistics data concerning each product shipped from the first shipper to the receiver. In another embodiment, the method also includes the receiver and the second shipper sharing access to a database containing logistics data concerning each product shipped from the second shipper to the receiver. In another embodiment, the method also includes the first shipper shipping product to a first third-party logistics provider. In another embodiment, the method also includes assigning a unique first third-party logistics provider number to a unique identifier, the unique identifier applied to each product shipped from the first shipper to the first third-party logistics provider. In another embodiment, the method also includes the second shipper shipping product to a second third-party logistics provider. In another embodiment, the method also includes assigning a unique second third-party logistics provider number to a unique identifier, the unique identifier applied to each product shipped from the second shipper to the second third-party logistics provider. In another embodiment, the method also includes at least one of the first third-party logistics provider and the second third-party logistics provider shipper applying a barcode to a product. In another embodiment, the method also includes the receiver, the first third-party logistics provider, and the first shipper sharing access to a database containing logistics data concerning each product shipped from the first shipper to the first third-party logistics provider, to the receiver. In another embodiment, the method also includes the receiver, the second third-party logistics provider, and the second shipper sharing access to a database containing logistics data concerning each product shipped from the second shipper to the second third-party logistics provider, to the receiver. [00171] In one embodiment, there is disclosed a logistics data management system including a database adapted to contain logistics data and configured to be accessed by an internet connection. In another embodiment, the database is adapted to connect to a middleware device. In another embodiment, the database is adapted to connect to an electronic data interchange adapted to transmit data from a user to the database. In another embodiment, at least one database record comprises a shipper's destination profile. In another embodiment, at least one table of the database comprises a unique company code data field. In another embodiment, each table of the database comprises a unique company code data field. In another embodiment, the company code data fields comprises three characters. In another embodiment, the company code data fields comprises four characters. In another embodiment, the company code data fields comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters. In another embodiment, at least one table of the database comprises a company location code data field. In another embodiment, the company location code data field comprises about 1 to 10 characters. [00172] In one embodiment, there is disclosed a supply chain including at least two members of the supply-chain selected from the group consisting of shippers, receivers, customers, suppliers, vendors, third-party logistics providers, and a database containing logistics data concerning the supply-chain, wherein the at least two members of the supply- chain are each assigned a unique identifier within the database. In another embodiment, the unique identifier comprises a company code data field. In another embodiment, the company code data fields comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters. In another embodiment, at least one table of the database further comprises a company location code data field. In another embodiment, each table of the database comprises the unique identifier. In another embodiment, every member of the supply-chain is assigned a unique identifier within the database.

[00173] In one embodiment, there is disclosed a method of managing a supply chain including providing at least two members of the supply-chain selected from the group consisting of shippers, receivers, customers, suppliers, vendors, third-party logistics providers, and assigning a unique identifier to the at least two members of the supply-chain. In another embodiment, the unique identifier comprises a company code data field within a logistics management data system. In another embodiment, the company code data fields comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters. In another embodiment, the method also includes assigning a unique identifier to every member of the supply-chain.

[00174] In another embodiment, the systems 100 and/or 900 may include a single network or may be a variety of different networks, such as an intranet and the Internet, and may include both wireline and wireless communication channels to connect the various components.

[00175] In one embodiment there is disclosed a data management system including a database adapted to contain data associated with a unique identifier, and a server connected to the database adapted to transmit the data to at least two users. In another embodiment, the system also includes a middleware device connected between the database and the web server. In another embodiment, the system also includes an electronic data interchange adapted to transmit data from a user to the database. In another embodiment, the system also includes a report generator. In another embodiment, the system also includes a print server. In another embodiment, at least one table of the database comprises a shipper's destination profile. In another embodiment, at least one table of the database comprises a unique company code data field. In another embodiment, the company code data fields comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters. In another embodiment, the company code data fields comprises three characters. In another embodiment, the company code data fields comprises four characters. In another embodiment the data includes logistics data. [00176] In one embodiment, there is disclosed a method of managing information including creating a plurality of data tables each data table containing at least one field for a unique identifier, linking each data table with at least one other data table, populating the plurality of data tables with data including the unique identifiers, and providing access to the data. In another embodiment, providing access to the data comprises generating reports. In another embodiment, providing access to the data comprises connecting a web server to at least one of the data tables. In another embodiment, providing access to the data comprises providing access to the data to selected users over the Internet. In another embodiment, at least one of the data tables comprises a shipper's destination profile data field. In another embodiment, at least one of the data tables comprises a unique company code data field. In another embodiment, each of the data tables comprises a unique company code data field. In another embodiment, the company code data field comprises about 1 to 50 characters; 2- 25 characters; or 3-10 characters. In another embodiment, the company code data field comprises three characters or four characters. In another embodiment, at least one of the data tables also comprises a company location code data field. In another embodiment, the company location code data field comprises two characters. In another embodiment, the data includes logistics data.

[00177] In another embodiment, system 100 and/or system 900, and their various subparts and variations incorporate one or more elements of the technical disclosure located at http://www.hal-inc.com/. Http://www.hal-inc.com/ is herein incorporated by reference in its entirety.

[00178] In another embodiment, system 100 and/or system 900, and their various subparts and variations incorporate one or more elements of the technical disclosure located in the documentation regarding the product MEPAW®, commercially available from Hal, Inc. of Houston, Texas, at http://www.hal-inc.com. The documentation regarding the product MEPAW® is herein incorporated by reference in its entirety.

[00179] In another embodiment, system 100 and/or system 900, and their various subparts and variations incorporate one or more elements of the technical disclosure located in Appendix A. Appendix A is herein incorporated by reference in its entirety. [00180] Numerous other variations and modifications can be made without departing from the spirit of the present invention. For example, among other things, the disclosed systems and methods may be used with any type of data, such as for example, logistic data, or in any environment where data management is required, such as for example, a logistics environment, a financial data environment, or an inventory control environment. The disclosed logistics systems and methods may employ any type of transporting entities. The present invention has been described relative to a preferred embodiment. Improvements or modifications that become apparent to persons of ordinary skill in the art only after reading this disclosure are deemed within the spirit and scope of the application. It is understood that several modifications, changes and substitutions are intended in the foregoing disclosure and in some instances some features of the invention will be employed without a corresponding use of other features. Therefore, it should be clearly understood that the embodiments of the present invention described above and shown in the figures of the accompanying drawings are illustrative only and are only provided to aid in the understanding of the invention. The description above and the accompanying figures should not be used, and are not intended to limit the scope of the claims of the present invention. Accordingly, it is appropriate that the appended claims be construed broadly and in a manner consistent with the scope of the invention.

Claims

Claims What is claimed is:

1. A data management system comprising: a database adapted to contain data; and a web server coupled to the database adapted to transmit the data to at least one users.

2. The system of claim 1 , further comprising: a middleware device coupled between the database and the web server.

3. The system of any of the preceding claims, further comprising: an electronic data interchange adapted to transmit data from a user to the database.

4. The system of any the preceding claims, further comprising a report generator.

5. The system of any the preceding claims, further comprising a print server.

6. The system of any the preceding claims, wherein at least one table of the database comprises a shipper's destination profile.

7. The system of any the preceding claims, wherein at least one table of the database comprises a unique company code data field.

8. The system of claim 7, wherein the company code data fields comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters.

9. The system of claim 7, wherein the company code data fields comprises three characters or four characters.

10. The system of any the preceding claims, wherein the data comprises logistics.

11. A method of managing information comprising: creating a plurality of data tables; linking each data table with at least one other data table; populating the plurality of data tables with data; and providing access to the data.

12. The method of claim 11 , wherein providing access to the data comprises generating reports.

13. The method of claims 11 or 12, wherein providing access to the data comprises connecting a web server to at least one of the data tables.

14. The method of claims 11 , 12, or 13, wherein providing access to the data comprises providing access to the data to selected users over the Internet.

15. The method of claims 11 , 12, 13, or 14, wherein at least one of the data tables comprises a shipper's destination profile data field.

16. The method of claims 11 , 12, 13, 14, or 15, wherein at least one of the data tables comprises a unique company code data field or wherein each of the data tables comprises a unique company code data field.

17. The method of claim 16, wherein the company code data field comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters.

18. The method of claim 16, wherein the company code data field comprises three characters or four characters.

19. The method of claims 16, 17, or 18, wherein the at least one of the data tables also comprises a company location code data field.

20. The method of claim 19, wherein the data comprises logistics data.

21. A system adapted to manage logistics data for a package moving from an initial origin to a destination, comprising: a means to receive a requirement to move the package; a means to locate or receive the package; a means to match the requirement with the package; and a means to ship the package.

22. The system of claim 21 , wherein the means to receive the requirement comprises electronic data interchange, and wherein the requirement comprises a requisition order, a purchase order, a movement order, or an asset movement order.

23. The system of claims 21 or 22, further comprising a means to generate a pick ticket.

24. The system of claims 21 , 22, or 23, further comprising a means to generate shipping documents.

25. The system of claims 21 , 22, 23, or 24, further comprising a means to verify that the package being shipped is the same as the package requested on the requirement.

26. The system of claims 21 , 22, 23, 24, or 25, further comprising a means to monitor the package in transit after being shipped.

27. The system of claims 21-26, further comprising a means to share the data within the system with a plurality of users.

28. The system of claims 27, wherein the means to share the data comprises a Web browser and the Internet.

29. The system of claim 21-28, further comprising a means to group the package with other packages for shipping.

30. A method of managing logistics data from a plurality of shippers to a receiver, comprising: a first shipper assigning a unique first shipper number to a unique identifier and applying the unique identifier to each package shipped from the first shipper to the receiver; and a second shipper assigning a unique second shipper number to a unique identifier and applying the unique identifier to each package shipped from the second shipper to the receiver.

31. The method of claim 30, further comprising at least one of the first shipper and the second shipper applying a barcode to a package.

32. The method of claim 30 or 31 , further comprising the receiver managing data concerning each package shipped from the first shipper to the receiver based on the unique first shipper number.

33. The method of claim 30, 31 , or 32, further comprising the receiver managing data concerning each package shipped from the second shipper to the receiver based on the unique second shipper number.

34. The method of claims 30-33, further comprising the receiver and the first shipper sharing access to a database containing logistics data concerning each package shipped from the first shipper to the receiver.

35. The method of claims 30-34, further comprising the receiver and the second shipper sharing access to a database containing logistics data concerning each package shipped from the second shipper to the receiver.

36. The method of claims 30-35, further comprising the first shipper shipping a package to a first third-party logistics provider.

37. The method of claim 36, further comprising assigning a unique first third-party logistics provider number to a unique identifier and applying the unique identifier to each package shipped from the first shipper to the first third-party logistics provider.

38. The method of claims 30-36, further comprising the second shipper shipping a package to a second third-party logistics provider.

39. The method of claim 38, further comprising assigning a unique second third-party logistics provider number to a unique identifier and applying the unique identifier to each package shipped from the second shipper to the second third-party logistics provider.

40. The method of claims 36-39, further comprising at least one of the first third-party logistics provider and the second third-party logistics provider shipper applying a barcode to a package.

41. The method of claims 36, 37, or 40, further comprising the receiver, the first third- party logistics provider, and the first shipper sharing access to a database containing logistics data concerning each package shipped from the first shipper to the first third-party logistics provider, to the receiver.

42. The method of claims 38, 39, or 40, further comprising the receiver, the second third-party logistics provider, and the second shipper sharing access to a database containing logistics data concerning each package shipped from the second shipper to the second third-party logistics provider, to the receiver.

43. A logistics data management system comprising: a database adapted to contain logistics data and configured to be accessed by an internet connection.

44. The system of claim 43, wherein the database is adapted to connect to a middleware device.

45. The system of any of claims 43 or 44, wherein the database is adapted to connect to an electronic data interchange adapted to transmit data from a user to the database.

46. The system of any of claims 43, 44, or 45, wherein at least one database record comprises a shipper's destination profile.

47. The system of any of claims 43, 44, 45 or 46, wherein at least one table of the database comprises a unique company code data field, or wherein each table of the database comprises a unique company code data field.

48. The system of claims 47, wherein the company code data fields comprises three characters.

49. The system of claims 47, wherein the company code data fields comprises four characters.

50. The system of claims 47, wherein the company code data fields comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters.

51. The system of any of claims 47, wherein at least one table of the database comprises a company location code data field.

52. The system of claim 51 , wherein the company location code data field comprises about 1 to 10 characters.

53. A supply chain management system comprising: at least two members of the supply-chain selected from the group consisting of shippers, receivers, customers, suppliers, vendors, third-party logistics providers; and a database containing logistics data concerning the supply-chain, wherein the at least two members of the supply-chain are each assigned a unique identifier within the database.

54. The supply-chain of claim 53, wherein the unique identifier comprises a company code data field.

55. The supply-chain of claim 54, wherein the company code data fields comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters.

56. The supply-chain of any of claims 53, 54, or 55, wherein at least one table of the database further comprises a company location code data field.

57. The supply-chain of any of claims 53, 54, 55, or 56, wherein each table of the database comprises the unique identifier.

58. The supply-chain of any one of claims 53, 54, 55, 56, or 57, wherein every member of the supply-chain is assigned a unique identifier within the database.

59. A method of managing a supply chain comprising: providing at least two members of the supply-chain selected from the group consisting of shippers, receivers, customers, suppliers, vendors, third-party logistics providers; and assigning a unique identifier to the at least two members of the supply-chain.

60. The method of claim 59, wherein the unique identifier comprises a company code data field within a logistics management data system.

61. The method of claim 60, wherein the company code data fields comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters.

62. The method of any one of claims 59, 60, or 61, further comprising assigning a unique identifier to every member of the supply-chain.

63. A data management system comprising: a database adapted to contain data, associated with a unique identifier reflecting a source of the data, from at least two sources; and a server coupled to the database adapted to provide access the data to at least two users.

64. The system of claim 63, further comprising: a middleware device coupled between the database and the web server.

65. The system of any of the preceding claims, further comprising: an electronic data interchange adapted to transmit data from a user to the database.

66. The system of any the preceding claims, further comprising a report generator.

67. The system of any the preceding claims, further comprising a print server.

68. The system of any the preceding claims, wherein at least one table of the database comprises a shipper's destination profile.

69. The system of any the preceding claims, wherein at least one table of the database comprises a unique company code data field.

70. The system of claim 69, wherein the company code data fields comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters.

71. The system of claim 69, wherein the company code data fields comprises three characters or four characters.

72. The system of any the preceding claims, wherein the data comprises logistics data.

73. The system of any the preceding claims, wherein the data comprises the unique identifier, and the data and the unique identifier are accessed by the at least two users.

74. The system of any the preceding claims, wherein the server comprises a web server.

75. A method of managing data comprising: creating a plurality of data tables each data table containing at least one field for a unique identifier reflecting a source of the data; linking each data table with at least one other data table; populating the plurality of data tables with data including the unique identifier codes; and providing access to the data.

76. The method of any the preceding claims, wherein providing access to the data comprises generating reports.

77. The method of any the preceding claims, wherein providing access to the data comprises connecting a web server to at least one of the data tables.

78. The method of any the preceding claims, wherein providing access to the data comprises providing access to the data to selected users over the Internet.

79. The method of any the preceding claims, wherein at least one of the data tables comprises a shipper's destination profile data field.

80. The method of any the preceding claims, wherein the unique identifier comprises a unique company code.

81. The method of any the preceding claims, wherein the company code data field comprises about 1 to 50 characters; 2-25 characters; or 3-10 characters.

82. The method of any the preceding claims, wherein the company code data field comprises three characters or four characters.

83. The method of any the preceding claims, wherein the at least one of the data tables also comprises a company location code data field.

84. The method of any the preceding claims, wherein the data comprises logistics data.