|Publication number||US20050091090 A1|
|Application number||US 10/993,355|
|Publication date||Apr 28, 2005|
|Filing date||Nov 22, 2004|
|Priority date||Oct 10, 2000|
|Also published as||CN1474985A, CN1474985B, EP1327220A1, EP2725529A1, EP2725529A9, US7752142, US7756794, US7761387, US7827119, US20020123911, US20020178023, US20050091089, US20050091091, WO2002031730A2|
|Publication number||10993355, 993355, US 2005/0091090 A1, US 2005/091090 A1, US 20050091090 A1, US 20050091090A1, US 2005091090 A1, US 2005091090A1, US-A1-20050091090, US-A1-2005091090, US2005/0091090A1, US2005/091090A1, US20050091090 A1, US20050091090A1, US2005091090 A1, US2005091090A1|
|Inventors||Poul Bjerre, Thomas Eskesen, Michael Schutt|
|Original Assignee||Inttra, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (44), Referenced by (13), Classifications (12)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims priority to provisional application U.S. Ser. No. 60/238,454, filed Oct. 10, 2000, whose contents are expressly incorporated by reference.
Today, shipping goods is a complicated business. Carriers have a finite amount of cargo space, and accordingly, shippers often negotiate with multiple carriers to coordinate the movement of just one container. Typically to limit the uncertainty and cost of moving goods, shippers contract with multiple carriers to provide a predetermined volume of business to each carrier at an agreed upon rate. This gives shippers the flexibility to choose from a number of different carriers to transport goods (for example, shipping directly from Stockholm to New York, rather than through an intermediate location) and increases the likelihood of moving a container when the shipper needs the container moved while guaranteeing individual carriers a volume of business. In practice, a shipper sequentially contacts carriers to check availability. If one carrier doesn't meet the shipper's desires, the shipper then contacts another contracted carrier. For example, refrigeration may be required and only certain carriers may handle refrigerated goods, the shipper may negotiate with only those contracted carriers that provide refrigeration. Even if the carrier may handle refrigerated cargo, they may not have the cargo space available to move the goods by a given day. Accordingly, even if the shipper and carriers have executed a contract prior to negotiations to move goods, shippers are still effectively required to negotiate with multiple carriers when securing the transport of cargo.
Since shippers typically contract with multiple carriers, the shipper is required to learn and understand a variety of different carrier idiosyncrasies. The differences between carriers is compounded as each carrier attempts automation and/or direct booking over the internet. Each carrier booking system (or platform) may be different in the look and feel as well as in the process that one requests the transport of goods. This forces each shipper to learn each carrier's platform to effectively and efficiently book a shipment of goods. The entire process is both confusing and time consuming for shippers. Carriers are then faced with incorrect or irreconcilable booking reports leading to more lost resources.
Freight forwarders add yet another level to this complicated business. Freight forwarders generally coordinate the transportation of goods on behalf of the shippers. For example, if the shipper desires goods be shipped from Chicago to Tokyo, the freight forwarder, on behalf of the shipper, negotiates and/or coordinates with the carriers to arrange for the goods to be moved. Essentially, the freight forwarders provide shippers with a service and generally do not move the goods themselves. Thus, freight forwarders provide shippers with an alternative to coordinating transportation of goods with the carriers. Although, freight forwarders provide shippers with a valuable service, they also create inefficiency and increase shipping costs for shippers as the cost for the service of the forwarders is billed to the shippers.
Biasing results in yet another inefficiency. Forwarders may receive incentives to direct business to certain carriers over others. Also, as the complexity of the shipping business creates a desire for both shippers and freight forwarders to contract with certain carriers, this desire naturally creates a bias towards the contracted carriers. For example, if a shipper wants to move goods from Detroit to Spokane, the shipper may negotiate with a contracted carrier which only moves goods directly to Seattle. A second carrier would be needed to complete the transport from Seattle to Spokane, thus, requiring an additional leg to move the goods to Spokane. However, if the shipper wasn't biased towards the contracted carriers, the goods may have been shipped directly to Spokane using a non-contracted carrier. Accordingly, shippers or freight forwarders may be creating inefficiencies by not using all available resources.
Since shippers or freight forwarders typically move goods using a variety of carriers, tracking and tracing goods across different carriers is also costly. Because shippers or freight forwarders often coordinate transportation of goods with multiple carriers, they are required to learn how to track and trace goods according the specific carrier's platform. Since shippers may have hundreds of containers being shipped by many different carriers at any given time and want to know the status and related info for their shipments, both shippers and carriers devote large amounts of resources to tracking and tracing containers. It is not uncommon for carriers to devote an entire workgroup to handling phone calls from shippers requiring information on the location of their goods. A consolidated system is needed that permits shippers to track shipments from a variety of carriers. Also, a system is needed that permits tracking of a shipment across multiple carriers.
In recent years developers have used the internet to create virtual marketplaces that bring together buyer and sellers, run negotiations and give companies and their suppliers the ability to readily share information. Some attempts have been made to reduce the cost to the shipper by using the internet. One attempt was to give carriers the ability to post published rates and discount information for land, sea and air bearing cargo vessels allowing customers to evaluate prices prior to booking. Another attempt to use the internet, give shippers the ability to receive a plurality of bids from a plurality of participating cargo transportation entities. These systems merely identify the cost of doing business with a select carrier and no more. This does not solve the problem of having to use multiple carrier platforms to submit the booking request to different carriers. This also does not permit easy exchange of goods between carriers where multiple carriers are used for a single shipment. Finally, warehousing goods, transporting goods, customs brokerage and trade finance are complicated pieces of a very complicated business. Accordingly, a need exists for a more efficient system for handling logistics and transportation of goods.
The disclosure provides a method and system that enables domestic and international transportation users to handle shipping transactions through a single common system through a neutral transportation portal. The system provides, among other things, transportation users with single point of entry for tracking cargo movements with multiple carriers. In various embodiments, the system also gives users access to scheduling, booking requests for booking cargo across several carriers and, in some embodiments, proactive event notification.
These and other benefits will become apparent as described in the drawings and related description.
The following description is divided into sub-sections to assist the reader. The sub-sections include: terms; infrastructure; booking process and user interface; track and trace; and event notification.
The following terms are used in the description.
Shipper—Any entity with goods to be transported. The entity may desire the goods be transported or may be transporting the goods for a different entity.
Freight forwarder—An entity that coordinates the transportation of goods with a carrier or carriers for a shipper.
Carrier—Any entity that transports goods from an origin to a destination. The carrier may transport goods domestically and/or internationally. For example, a carrier may transport goods for a shipper from Chicago to Seattle or the same carrier may transport goods from Chicago to Paris. The carrier may transport goods using trucks, trains, planes, ships, and/or the like.
Carrier Platform—A carrier's computer system supporting an interface that enables exchange of information with the carrier.
Common Carrier System—Infrastructure that supports the common carrier interface including data storage.
Common Carrier Interface—An interface that enables multiple users and multiple carriers to communicate.
User—Any entity that uses the common carrier system. All users may have various levels of interest in using the common carrier system. The main users of the common carrier system may be shippers, third-party logistics providers, freight forwarders, consignees, brokers, trading portals, carriers and the like.
Booking—A reservation to transport a volume of goods from a single origin to a single destination. The goods may vary in product type, may be a mix of hazardous and non-hazardous, may require refrigeration and the like. The booking may be a single booking or may be repetitive.
Routing Request—A query to the carrier to determine if the carrier supports the basic transpirations of the cargo as part of the carrier product catalog.
Booking Activity Plan—A carrier plan that encompasses the major, or milestone, activities of a shipment.
The present disclosure relates to a system and method for buyers and sellers of domestic and/or international transportation services related to the shipment of goods. The users and carriers may be linked to the system by dial-up modem to communicate to the internet, and accordingly, be disconnected from the system or off-line. For example, the user may use a dial-up modem and submit a booking request to a carrier through the internet and afterwards disconnect from the internet. After the user disconnects and is currently off-line, the common carrier system may submit the booking request to the carrier and receive confirmation of the booking request from carriers while the user is off-line. In another embodiment, the common carrier system 102 may process the information while the user is still connected with the internet. This permits the user to be notified as soon as availability is determined for various carriers or after a reservation has been made with the carriers by the common carrier system 102. The system and method offers shippers the opportunity to request and select specific service patterns offered by participating carriers in the booking of full container shipments. The system and method includes user interfaces, processes, computer systems, and computer-readable mediums having programs stored thereon. The system and method enable a user to submit booking requests to multiple carriers and/or track and trace the goods using a single common carrier system and interface. The system and method also may be used to provide event notification.
In general, when a shipper wants to move goods, the shipper submits a booking request to one or more carriers to which the carrier(s) responds by accepting, rejecting, or changing the booking request. A booking represents a shipper's intention to transport a volume of goods from a single origin to a single destination. The goods may vary in product type, may be a mix of hazardous and non-hazardous, may require refrigeration and the like. As a result, differing container types may be required. To accommodate differing cargo characteristics, a booking may contain one or more booking lines. The request may be made using a variety of different processes. The user 101 may send an email message to the common carrier system 102, who processes the email and acts in response. Alternatively, the user 101 may post information to a web site of the common carrier 102. Further, the user 101 may transmit information in the form of XML or EDI data sets for processing by the common carrier system 102. It is appreciated that a number of different transmission schemes may be used to forward requests to the common carrier system 102. The information received by the common carrier system 102 may then forward the requests to a variety of carriers 103. The common carrier system 102 may blindly forward the request to all carriers 103 to see who responds. Otherwise, the common carrier system may filter the booking request from user 101 to minimize the number of carriers 103 who receive the request In addition, the common carrier system 103 may have a routing list as specified by the user for permitting the ordering of the hierarchy in which carriers are polled for booking availability.
The transmissions between the common carrier system 102 and the carriers 103 may also be in the form used by the user. Alternatively, the common carrier system 103 may translate the user's request from one form or format into one understood by the carrier or carriers 103. If needed, common carrier system 103 may add information or subtract information as needed for each carrier 103. For example, some carriers may use one type of units while others use another type of units. The common carrier system 103 then translates the units provided by the user for submission to the carrier. Also, the user may have certain needs if goods are transported one way as opposed to another (refrigeration needed if shipped in a container ship while no refrigeration needed if shipped by truck or train). If so, the common carrier system 103 may eliminate or modify the information transmitted to each carrier 103 so as to meet the needs of each carrier's platform and/or booking system. A booking line may include a single container type, single hazardous goods indicator, single refrigeration and a single commodity description. When the common carrier system receives the first carrier booking confirmation massage, for example the confirmation from carrier 103 a, the system 102 may, upon the shippers request (any user using one of terminals 101 a-101 e or other known devices like, for example, a mobile PDA), automatically generate and submit booking cancellation to other carriers 103 b-103 e.
Alternatively, the booking request from the common carrier system 102 may request information from the carriers 103 of who has availability for handling the proposed booking. The response from the carriers 103 provides the common carrier system 102 with information of availability, shipping time frame, and other information.
In one example, an interested party, typically the shipper or freight forwarder, enters a booking draft with high-level details about the freight it desires to be shipped. Using the information entered on the booking, the user of the system may also, via terminals 101 a-101 e, issue a routing request through the common carrier system 102 to one or more carriers 103 a-103 e. One or more of carriers 103 a-103 e responds with detailed routing information. The shipper may request the carrier 103 a-103 e submit routing information based upon the data contained within the booking (place or receipt, place of delivery, etc.) The common carrier system 102 enable users (via terminals 101 a-101 e or by other known devices like, for example, a mobile PDA) to submit a booking, with or without a routing request, and it may be submitted to one or more carriers 103 a-103 e.
The actual interfaces between the user 101 and the plurality carriers 103 handling the routing request may be determined by the technical capabilities of the carriers 103. Sophisticated carriers 103 may provide direct online response through their internal systems. Other carriers 103 may use the service patterns interface to store available routings. At a minimum, all carriers may respond to routing request via using the common carrier system 102. Separate confirmation directed to each user may also be made (via email, instant messaging and the like).
If the booking party 101 chooses to so specify (for example, by checking a checkbox or similar object on the booking screen), the first carrier to respond with a valid response to the routing request may automatically be selected and the booking may be submitted to the carrier. Otherwise, the booking party may manually select the carrier and submit the booking. It is now up the carrier to determine if the actual transport of cargo may take place (based on vessel capacity, equipment availability, etc.) and either confirm the booking, decline the booking or make a counter proposal.
Finally, when a carrier confirms the booking, the carrier may return a booking activity plan as part of the booking confirmation. The plan may be stored in the common carrier system database(s) 102 a of the common carrier system 102 and subsequent track and trace messages may be used to measure performance (time to process bookings, percent on time delivery, claims, misdeliveries, etc.) against the booking activity plan.
The common carrier system enables the common carrier interface provides the users with a unified booking interface and procedure while also providing an additional source of bookings for the carriers.
Furthermore, the common carrier system and interface enables the user to create templates tailored for their specific needs. Accordingly, the user may quickly create template-driven booking requests without having to step through the entire booking process. Also, Identifying and registering a user's consignees, forwarders, shippers, et al., may facilitate the template building process and provide shipment visibility to user's partners as quickly as possible.
Booking Process and User Interface
The description of the first embodiment is organized to show process flows as taken by the user. Various user interface screens embody the process flows.
The process of creating a booking request through confirmation will now be described, with reference to
Creating a new booking request will now be described. If the user chooses to create a new booking request in step 203, then the user continues to step 206 and identifies the carrier and the commodity description details. If HAZMAT data is not desired, the user advances to step 210 of
After identifying the shipping party at step 236 and steps 227-230, the user advances to step 231 and submits the booking request to the system, wherein the system submits the booking request to the carrier at step 234. The user may also reach step 234 by entering a reference number and remarks during steps 232 and 233, respectively. Additionally, the user may reach step 234 by reusing an existing booking request or from a predetermined template as shown in
As illustrated in
Creating new booking request will now be described with reference to
Referring to cargo section 402 of
Referring to the container information section 403 of
Referring to the routing information section 404 of
Optionally, the user may search to find the common carrier system for the registered locations of the place of origin, load and discharge locations. Several locations in the booking screen may be registered (non-free text) locations. To assist the user with identify these locations, the user may link to the search screen for assistance by clicking any of the buttons 425-428. The user may enter any combination of city, state, and country in fields 814-816 and press the search button 817 of
Referring to the booking parties section 405 of
Referring to the additional information section 406 of
Once the user entered all initial data, the user may send the booking request, save the booking request as a draft or save the booking request as a template by clicking one of the appropriate buttons 436-438. If the user sends the booking request, the carrier selected by the user may then be alerted by the common carrier system and reply to the user's booking request. If the user saves the booking request as a draft, the user may at a later time complete the booking request and send it to the carrier and/or save the booking request as a template.
Creating a booking request from a template will now be described. Referring to
Reusing an existing booking request will now be described. Referring to
The common carrier system is capable of developing forms for the common carrier interface which help users capture their tradelanes, commodity and equipment requirements, routing, and booking party details. These forms enable the common carrier system to create customer specific booking request templates. In most cases, a booking template capture the majority of fields described above, and worksheets group these fields into easily understood sections.
Bookings may be made, for example, through the common carrier system user interface, Electronic Data Interchange and the like. EDI transmission pass through the common carrier system to allow common carrier system functionality to be used. For example, track and trace functionality require the booking EDI transmission pass through the common carrier system. Booking made via the common carrier system user interface may be made from scratch of facilitated by means of previously saved data in the form of templates or previous booking as described above.
Track and Trace
This embodiment enables the user to track and trace only by identifying container as opposed to tracking and tracing by identifying both carrier and container. That is, the user does not need identify which carrier is transporting their container. Accordingly, the common carrier system enables the user to track and trace containers across multiple carrier platforms from a single system, the common carrier system.
The common carrier system facilitates track and trace information within the confines of a carrier's responsibilities. The boundaries for tracking a shipment directly reflect the associated route and service patterns supporting that container's movement. Applicable common carrier system users, via terminal 101 a-101 e of
To use the track and trace function, the user request a booking with a common carrier registered carrier using the common carrier system as outlined above. The carrier confirms the booking request and submits a booking activity plan for the booking at the same time. A single booking supports a single booking activity plan. The booking may consist of multiple container movements. The booking activity plan may be used to support track and trace information at the container level. The booking activity plan may provide greater information than a service pattern, since each main leg may be broken down into actual transport modes, transshipment locations and interim arrival and departure date/times.
Once the carrier submits the booking activity plan the container may be tracked and traced. The carrier submits the track and trace events to the common carrier system either by EDI or via a common carrier system user interface. Carriers may continue to use their own coding convention when submitting events by using EDI translator. EDI translator translates carrier event codes and message formats into a common carrier system neutral format. The common carrier system may record when a shipment has departed and arrived at the various location and record when business processes or non-conformances occur. The common carrier system may also record the date and time when the common carrier system receives track and trace events. The date and time recorded by the system maintains consistency with the date and time associated with where that event occurred (e.g. from GMT to local time of the shipper, local time of the destination location, local time of the sending location, and the like). That is, the date and time may be adjusted to match the time zone of the user or other parties.
The user uses the track and trace function by using the common carrier system track and trace user interface. This enables the user to select criteria against which a search may be conducted. The user has the ability to customize how the search results are displayed. The user has the ability to customize display results on an individual container basis or on a “batched” container basis. The common carrier system may “batch” container records. When the common carrier system returns track and trace information on “batch” records, the user has the ability to drill-down to the container level detail and to drill back up. Furthermore, the user has the ability to ascertain, at glance, where the container is in relation to the activity plan and clear visibility as to what events have been successfully completed and which were not.
Event notification may be submitted to the nominated users using any of the following technologies: EDI, Email, common carrier interface pop-up dialogue box and the like. This may be based on the users technology. Furthermore, the user may define the rules with respect to event notification. Table I below shows an example of the events, event triggers and event notification as determined by the user.
The system may, upon the user demand, automatically generate notices of cargo movement according to the user specification. The event handling functionality may be employed to provide notification regarding the certain track and trace events, track and trace non-events, and certain business process decisions. The event notification component of the common carrier system may reflect the workflow environment whereby interested users are notified when an event has occurred, or when one hasn't (e.g. a shipment was expected on a certain day, but is not expected to arrive until the next day). The user may specify their tolerances for these events. For example, one user may which to know if a shipment is late more than six hours, whereas another is more tolerant and a 24 hour delay and notification is acceptable.
To notify the user when an event has not occurred, the common carrier system polls the booking activity plan information periodically to identify non-conformances against the booking activity plan, that is, when milestone events (that should have occurred) have not. Event messages may contain event code and location information. When the system identifies a non-conformance, an event notification is automatically generated and submitted to nominated entries. A non-confirmation in this case is deemed to be when the system has not received an event message prior to or at the dateltime of the event should have occurred as defined in the booking activity plan. The common carrier system also submits track and trace events notifications when certain “optional” events are notified to the system, for example customs held and customs release.
TABLE I Events Event Trigger Event Source Event Notification Empty container Empty Container Released by Carrier Carrier's system or None pick-up CC System Empty container Arrival of container at Shipper's Carrier's system or None positioned premises CC System Departure Departure of Container from a Location Carrier's system or Yes, if not notified CC System to CC System Arrival Arrival of Container at Location Carrier's system or Yes, if not notified CC System to CC System Loaded on Truck As part of an inland move, container has Carrier's system or None been loaded onto a Truck CC System Loaded on Rail As part of an inland move, container has Carrier's system or None been loaded onto a train CC System Loaded on Barge As part of an inland move, container has Carrier's system or None been loaded onto a barge CC System Loaded on Container has been loaded onto a vessel Carrier's system or None Vessel CC System Discharged from Container has been unloaded from Carrier's system or None Vessel vessel CC System Customs Container has cleared customs Carrier's System or Yes Clearance nominated agent's system or CC System Customs Hold Container has been held at Customs Carrier's System or Yes nominated agent's system or CC System Customs Release Container has been released by Customs Carrier's System or Yes after being held nominated agent's system or CC System Cargo Release Cargo has been released by the Carrier Carrier's system or None CC System Free Time to Containers from time about to expire Carrier's system or Yes Expire CC System Free Time Container free time has expired Carrier's system or Yes Expired CC System
Thus, has been described a system that enables domestic and/or international transportation users to handle shipping transactions through a single common system substantially through a neutral transportation portal. The system provides, among other things, transportation users with single point of entry for tracking cargo movements with multiple carriers. The system also gives users access to scheduling, booking requests for booking cargo across several carriers and proactive event notification. Many variation and alterations of the embodiments are of course possible.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5293310 *||May 22, 1992||Mar 8, 1994||Pitney Bowes Inc.||Flexible method for applying customized rating adjustments to transaction charges|
|US5311425 *||Nov 28, 1990||May 10, 1994||Japan Airlines, Co., Ltd.||Reservation system terminal|
|US5631827 *||Jun 6, 1995||May 20, 1997||Tandata Corporation||Logistics system for automating transportation of goods|
|US5712789 *||Aug 28, 1995||Jan 27, 1998||K&T Ltd.||Container monitoring system and method|
|US5787400 *||Dec 12, 1994||Jul 28, 1998||Pitney Bowes Inc.||Method for implementing electronic data interchange (EDI) in the processing of manifests and parcel inquiry/responses for multiple carriers in a parcel processing system|
|US5835716 *||Dec 15, 1995||Nov 10, 1998||Pitney Bowes Inc.||Method and system for brokering excess carrier capacity|
|US5910896 *||Nov 12, 1996||Jun 8, 1999||Hahn-Carlson; Dean W.||Shipment transaction system and an arrangement thereof|
|US5959568 *||Jun 26, 1996||Sep 28, 1999||Par Goverment Systems Corporation||Measuring distance|
|US5995950 *||Aug 23, 1993||Nov 30, 1999||Pitney Bowes Inc.||Carrier management system having a capability to determine discounted shipping charges for groups of parcels having the same consignee|
|US6016484 *||Apr 26, 1996||Jan 18, 2000||Verifone, Inc.||System, method and article of manufacture for network electronic payment instrument and certification of payment and credit collection utilizing a payment|
|US6018725 *||Sep 30, 1997||Jan 25, 2000||Pitney Bowes Inc.||Method and system of implementing a carrier manager registry|
|US6035289 *||Jul 14, 1998||Mar 7, 2000||International Business Machines Corporation||Method and apparatus for electronic trading of carrier cargo capacity|
|US6035291 *||May 2, 1997||Mar 7, 2000||Francotyp Postalia Gmbh||Method and arrangement for data processing in a shipping system with a postage meter machine, including automatic selection of the most beneficial carrier|
|US6047264 *||Oct 8, 1996||Apr 4, 2000||Onsale, Inc.||Method for supplying automatic status updates using electronic mail|
|US6047267 *||May 14, 1997||Apr 4, 2000||Portal Software, Inc.||Method and apparatus for tracking multiple payment resources and charging transactions to payment resources in on line transaction processing system|
|US6061667 *||Aug 4, 1997||May 9, 2000||Schneider National, Inc.||Modular rating engine, rating system and method for processing rating requests in a computerized rating system|
|US6064981 *||Jun 17, 1999||May 16, 2000||Barni; Neil A.||Method for online display and negotiation of cargo rates|
|US6078889 *||Sep 30, 1997||Jun 20, 2000||Pitney Bowes Inc.||Method and system of implementing a carrier manager librarian|
|US6088648 *||Jan 22, 1998||Jul 11, 2000||Mobile Information Systems, Inc.||Method and apparatus for tracking vehicle location|
|US6219653 *||Sep 15, 1998||Apr 17, 2001||Forest Products International Exchange, Inc.||Freight calculation system and method of operation|
|US6233568 *||Jun 29, 1998||May 15, 2001||E-Stamp Corporation||System and method for automatically providing shipping/transportation fees|
|US6240362 *||Oct 19, 2000||May 29, 2001||Iap Intermodal, Llc||Method to schedule a vehicle in real-time to transport freight and passengers|
|US6263317 *||Dec 1, 1998||Jul 17, 2001||Fogdog, Inc.||Web sales channel conflict resolution system|
|US6285916 *||Apr 28, 1997||Sep 4, 2001||United Parcel Serivce Of America, Inc.||Multi-stage parcel tracking system|
|US6321214 *||Jan 13, 2000||Nov 20, 2001||Francotyp-Postalia Ag & Co.||Method and arrangement for data processing in a shipping system with a postage meter machine, including automatic selection of the most beneficial carrier|
|US6463419 *||Mar 7, 2000||Oct 8, 2002||Chartering Solutions||Internet system for exchanging and organizing vessel transport information|
|US6463420 *||Feb 4, 2000||Oct 8, 2002||General Electric Company||Online tracking of delivery status information over a computer network|
|US6539360 *||Feb 5, 1999||Mar 25, 2003||United Parcel Service Of America, Inc.||Special handling processing in a package transportation system|
|US6625584 *||May 4, 1999||Sep 23, 2003||Jatin S. Bains||Maritime freight option|
|US6772130 *||Nov 22, 2000||Aug 3, 2004||Pitney Bowes Inc.||Method for parcel tracking on the internet with e-mail notification|
|US6865516 *||Nov 1, 1999||Mar 8, 2005||Ceebron Pty Limited||Method of recording the temperature of perishable products in cold chain distribution|
|US6970825 *||Dec 30, 1999||Nov 29, 2005||Pitney Bowes Inc.||Planning engine for a parcel shipping system|
|US6976007 *||Oct 4, 1999||Dec 13, 2005||Pitney Bowes Inc.||Method and system for multi-carrier package tracking|
|US7117170 *||Oct 6, 2000||Oct 3, 2006||Stamps.Com Inc.||Apparatus, systems and methods for applying billing options for multiple carriers for online, multi-carrier, multi-service parcel shipping management|
|US20020123911 *||Oct 10, 2001||Sep 5, 2002||Poul Bjerre||Common carrier system|
|US20020178023 *||Mar 11, 2002||Nov 28, 2002||Inttra, Inc.||Common carrier system|
|US20030236739 *||Mar 10, 2003||Dec 25, 2003||Quoteship.Com||Bid positioning system|
|US20050019090 *||May 7, 2004||Jan 27, 2005||The Pilot Ink Co., Ltd.||Water-based ballpoint pen|
|US20050091089 *||Nov 22, 2004||Apr 28, 2005||Inttra, Inc.||Common carrier system|
|US20050091090 *||Nov 22, 2004||Apr 28, 2005||Inttra, Inc.||Common carrier system|
|US20050091091 *||Nov 22, 2004||Apr 28, 2005||Inttra, Inc.||Common carrier system|
|US20050246359 *||Jun 30, 2005||Nov 3, 2005||Ronald Robbins||Delivery tracking system|
|US20070073551 *||Aug 24, 2006||Mar 29, 2007||Stamps.Com Inc.||Apparatus, systems and methods for online, multi-parcel, multi-carrier, multi-service enterprise parcel shipping management|
|US20070299686 *||Aug 27, 2007||Dec 27, 2007||Stamps.Com Inc.||Apparatus, systems and methods for interfacing with digital scales configured with remote client computer devices|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7653586 *||Mar 25, 2004||Jan 26, 2010||Future Freight Corporation||Computer-implemented trading in freight derivatives and techniques therefor|
|US7711629 *||Mar 25, 2004||May 4, 2010||Future Freight Corporation||Freight fulfillment and trading platform|
|US7752142||Nov 22, 2004||Jul 6, 2010||Inttra, Inc.||Common carrier system|
|US7756794||Oct 10, 2001||Jul 13, 2010||Inttra, Inc.||Common carrier system|
|US7761387||Mar 11, 2002||Jul 20, 2010||Inttra, Inc.||Common carrier system|
|US7783557 *||Mar 25, 2004||Aug 24, 2010||Future Freight Corporation||Computer-implemented display to facilitate trading in multi-modal freight shipment derivatives|
|US7827119||Nov 22, 2004||Nov 2, 2010||Inttra, Inc.||Common carrier system|
|US8504464||Aug 23, 2010||Aug 6, 2013||Future Freight Corporation||Trading in multi-modal freight shipment derivatives|
|US20040249699 *||Mar 25, 2004||Dec 9, 2004||Future Freight Corporation||Computer-implemented display to facilitate trading in multi-modal freight shipment derivatives|
|US20040249742 *||Mar 25, 2004||Dec 9, 2004||Future Freight Corporation||Computer-implemented trading in freight derivatives and techniques therefor|
|US20040254807 *||Mar 25, 2004||Dec 16, 2004||Future Freight Corporation||Freight fulfillment and trading platform|
|US20050091089 *||Nov 22, 2004||Apr 28, 2005||Inttra, Inc.||Common carrier system|
|US20050091090 *||Nov 22, 2004||Apr 28, 2005||Inttra, Inc.||Common carrier system|
|International Classification||B65G61/00, G06Q10/00, G06Q50/28, G06Q10/08|
|European Classification||G06Q10/08, G06Q10/0831, G06Q10/0835, G06Q10/02, G06Q10/0833, G06Q10/083|