Method and system for interfacing with a shipping service

• US 20030009361A1
• Filed: 01/25/2001
• Published: 01/09/2003
• Est. Priority Date: 10/23/2000
• Status: Active Grant

• Current Assignee: Schneider Logistics Incorporated (Schneider National Carriers Incorporated)
• Original Assignee: Schneider Logistics Incorporated (Schneider National Carriers Incorporated)
• Inventors: Hancock, Brian D., Schommer, Robert J., Olson, Douglas S.
• Granted Patent: US 6,785,718 B2
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/06312 Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: G06Q 10/0875 Itemisation or classification of parts, supplies or services, e.g. bill of materials

Abstract

A logistics node receives a purchase order from a customer. The logistics node selects an appropriate carrier to transport products specified in the purchase order and conveys shipping instructions to the selected carrier. The logistics node also coordinates the shipment by interacting with a source node (associated with a supplier of the products) and a destination node (associated with the recipient of the products). According to one exemplary feature, the logistics node provides an interface that permits users involved in the distribution chain to track the status of the shipments without having to enter tracking codes that are unique to individual carriers. According to another exemplary feature, the interface allows a user to access multiple “levels” of information regarding a shipment, including information pertaining to an individual product within a shipment containing multiple products. According to another exemplary feature, the interface allows a user to change the priority status associated with particular products that have already been presented for shipment. According to another exemplary feature, the interface provides different “views” for use by different respective users. Each of the views provides a corresponding different set of tools for use in interacting with the freight managing service.

Claims

1. A logistics node for administering the shipment of a product from a source node to a destination node, comprising:

an interface unit for coupling the logistics node with at least one remote entity;

a processing unit coupled to the interface unit for controlling the operation of the logistics node;

a database coupled to the processing unit for storing information pertaining to the shipment of a product from the source node to the destination node;

interface administration logic for permitting a first class of users to interact with the logistics node using a first interface, the first interface providing access to a first set of functions, and for permitting a second class of users to interact with the logistics node using a second interface, the second interface providing access to a second set of functions, and

wherein the first set of functions differs from the second set of functions, and wherein the first set of users are affiliated with the source node and the second set of users are affiliated the destination node.

2. A logistics node according to claim 1, wherein the first set of functions includes a function that permits the users belonging to the first class of users to view an unconfirmed product order.

3. A logistics node according to claim 1, wherein the second set of functions includes a function that permits users in the second class of users to view a shipped load which has arrived at the destination node.

4. A logistics node according to claim 3, wherein the function that permits the users to view the shipped load permits the users in the second class of users to view a list of products in the load.

5. A logistics node according to claim 4, wherein at least two of the products identified in the list originated from separate source nodes.

6. A logistics node according to claim 1, wherein the interface administration logic further permits a third class of users to interact with the logistics node using a third interface, the third interface providing access to a third set of functions.

7. A logistics node according to claim 1, wherein the third set of functions includes a function that permits the users to change a priority level associated with at least one product, wherein the first, second and third interfaces present priority information that reflects the change in the priority level.

8. A method for administering the shipment of a product from a source node to a destination node, comprising:

providing a freight management tool to users belonging to a first and second class of users;

providing users of the first class a first interface with which to interact with the freight management tool, the first interface providing access to a first set of functions;

providing users of the second class a second interface with which to interact with the freight management tool, the second interface providing access to a second set of functions,

wherein the first set of functions differs from the second set of functions, and wherein the first class of users are affiliated with the source node and the second class of users are affiliated the destination node.

9. A method according to claim 8, wherein the first set of functions includes a function that permits the users belonging to the first class of users to view an unconfirmed product order.

10. A method according to claim 8, wherein the second set of functions includes a function that permits users in the second class of users to view a shipped load which has arrived at the destination node.

11. A method according to claim 10, wherein the function that permits the users to view the shipped load permits the users in the second class of users to view a list of products in the load.

12. A method according to claim 11, wherein at least two of the products identified in the list originated from separate source nodes.

13. A method according to claim 8, further including the step of providing users of a third class a third interface with which to interact with the freight management tool, the third interface providing access to a third set of functions offered by the freight management tool.

14. A method according to claim 13, wherein the third set of functions includes a function that permits the users to change a priority level associated with at least one product, wherein the first, second and third interfaces present priority information that reflects the change in the priority level.

16. The logistics node of claim 15, wherein the first level of detail provides information concerning a shipment load, and the second level of detail provides information pertaining to an individual product on the shipment load.

18. The method of claim 17, wherein the first level of detail provides information concerning a shipment load, and the second level of detail provides information pertaining to an individual product on the shipment load.

15. A logistics node for administering the shipment of a product from a source node to a destination node, comprising:

an interface unit for coupling the logistics node with at least one remote entity;

a processing unit coupled to the interface unit for controlling the operation of the logistics node;

a database coupled to the processing unit for storing information pertaining to the shipment of a product from the source node to the destination node;

logic for providing a user with an option to examine shipment information using first and second levels of detail, wherein the second level of detail is more refined compared to the first level of detail;

logic for allowing a user to select the first or second level of detail; and

logic for providing shipping information to the user corresponding to the selected level of detail.

17. A method for administering the shipment of a product from a source node to a destination node, comprising:

providing a freight management tool to a user;

providing the user an interface with which to interact with the freight management tool;

providing the user with an option to examine shipment information using a first level of detail;

providing the user with an option to examine shipment information using a second level of detail, wherein the second level of detail is more refined compared to the first level of detail;

allowing a user to select the first or second level of detail; and

providing shipping information to the user corresponding to the selected level of detail.

19. A logistics node for administering the shipment of a product from a source node to a destination node, comprising:

an interface unit for coupling the logistics node with at least one remote entity;

a processing unit coupled to the interface unit for controlling the operation of the logistics node;

a database coupled to the processing unit for storing information pertaining to the shipment of a product from the source node to the destination node; and

logic for permitting at least one user to change a priority level associated with at least one product.

20. A method for administering the shipment of a product from a source node to a destination node, comprising:

providing a freight management tool to a user;

providing the user an interface with which to interact with the freight management tool;

providing the user, through the interface, with information that identifies a priority level associated with at least one product;

providing the user, through the interface, with an opportunity to change the priority level; and

modifying the priority level in response to a user'"'"'s change in the priority level to produce a modified priority level.

21. A logistics node for administering the shipment of a product from a source node to a destination node:

an interface unit for coupling the logistics node with at least one remote entity;

a processing unit coupled to the interface unit for controlling the operation of the logistics node;

a database coupled to the processing unit for storing information pertaining to the shipment of a product from the source node to the destination node; and

tracking logic for receiving an inquiry from a user regarding a shipment being made by at least one of a plurality of possible carrier candidates, and in response thereto, providing information pertaining to the shipment,

wherein the inquiry does not require a user to specify carrier-specific information to successfully retrieve information regarding the shipment.

22. The logistics node according to claim 21, wherein the inquiry identifies a product being shipped in the shipment.

23. The logistics node according to claim 21, wherein the shipment involves transferring a load from a first carrier to a second carrier at a cross dock node.

25. The method according to claim 24, wherein the inquiry identifies a product being shipped in the shipment.

26. The method according to claim 24, wherein the shipment involves transferring a load from a first carrier to a second carrier at a cross dock node.

24. A method for administering the shipment of a product from a source node to a destination node:

providing a freight management tool to a user;

providing the user an interface with which to interact with the freight management tool; and

receiving an inquiry from a user regarding a shipment being made by at least one of a plurality of possible carrier candidates, and in response thereto, providing information pertaining to the shipment,

wherein the inquiry does not require a user to specify carrier-specific information to successfully retrieve information regarding the shipment.