WO2015177808A2

WO2015177808A2 - Freight information management system and method

Info

Publication number: WO2015177808A2
Application number: PCT/IN2015/000210
Authority: WO
Inventors: Govindan SOWMYANARAYANAN
Original assignee: Hexaware Technologies Limited
Priority date: 2014-05-19
Filing date: 2015-05-18
Publication date: 2015-11-26
Also published as: WO2015177808A3

Abstract

Disclosed is a freight information management system implemented in a freight forwarder environment. The system comprises: an application programming interface capable of being invoked by a user interface of the freight forwarder environment for submitting and extracting freight information; a freight information processing module capable of validating, formatting and translating the freight information received through the application programming interface, to form processed freight information; and a carrier communication module capable of sending processed freight information to a carrier environment, and receiving response on the freight status from the carrier environment.

Description

FR EIGHT INFORMATION MANAGEMENT SYSTEM AND METHOD

FIELD OF THE INVENTION

[0001 ] The present invention relates to freight information management system and method.

BACKGROUND OF THE INVENTION

[0002] For shipment of products, it is a common practice to engage freight forwarders. Freight forwarders generally do the shipment via truck, train, ship, aircraft and other transport mechanisms. While shipping the products, it is very important to have a well-organized consignment information exchange between the freight supply chains. Specifically, the success in effectively transporting freight via a carrier (for example, aircraft) is primarily dependent on accurate and timely information flow between the partners in the supply chain.

[0003] Few existing solutions used by freight forwarders include traditional messaging forms (teletype) and presence of web portals where information is entered manually Freight forwarders using traditional messaging forms (teletype) use International Air Transport Association (IATA) Cargo Internet Messaging Program (IMP) messages for communication between the freight supply chains. The disadvantage of this method is the higher message transmission cost. Another disadvantage is usage of private networks since teletype needs participation in private networks and does not leverage Internet based communications. A further disadvantage is that the data transmission in this mode is asynchronous.

[0004] In some cases consignment data or freight information is submitted to airlines via manual entry in airline web portals. The disadvantage of this method is the dual entry and the rework done by the freight forwarder staff to key-in the consignment data/freight information which is already present in their own IT system.

[0005] Further, the flow of information via paper documents becomes prone to failures because of inefficiencies of generation, tracking and maintenance. Using electronic communication for the flow of infonnation removes these inefficiencies but often comes with a significant technology pricing and effort.

[0006] Accordingly, there exists a need for a freight infonnation management system that provides information transfer between freight forwarders and carriers (for example, airlines) in a reliable and cost efficient manner.

SUMMARY OF THE INVENTION

[0007] In view of the foregoing disadvantages inherent in the prior-art, the general purpose of the present invention is to provide a freight information management system and method that is configured to include all advantages of the prior art and to overcome the drawbacks inherent in the prior art offering some added advantages.

[0008] In one aspect, the present invention provides a system for freight information management. The system comprises: an application programming interface (API) capable of being invoked by a user interface of the freight forwarder environment for submitting and extracting freight information; a freight information processing module capable of validating, formatting and translating the freight information received through the application programming interface, to form processed freight information; and a carrier communication module capable of sending processed freight information to a carrier environment, and receiving response on the freight status from the carrier environment.

[0009] The system can be directly plugged into the freight forwarder environment and can be invoked from a user interface of the freight forwarder environment. The system of the present invention can be used by a user to carry out one or more of the following activities: submitting consignment information; processing consignment information in a format readable by the carrier environment; sending the processed consignment information to the carrier environment; querying consignment status from the carrier environment; receiving response on consignment status from the carrier environment; submitting and receiving feedbacks; and modifying consignment information based on feedback. Overall, the system and method of the present invention provide a tool that can be directly or indirectly installed in a freight forwarder information technology (IT) environment for communicating with a carrier IT environment. [0010] The API is capable of being invoked by a user interface of the freight forwarder environment for submitting and extracting consignment infomiation. Due to presence of the API, the system serves as a software library that can be directly used by a freight forwarder for submission of information to carrier environment. Specifically, the library provided by the system can be directly invoked and used by the freight forwarder to submit freight information to the carrier.

[001 1] In another aspect, the present invention provides a method for freight information management. The method comprises: invoking an application programming interface by a user interface of a freight forwarder environment for submitting and extracting freight information; validating, formatting and translating the freight information to form processed freight information; and sending processed freight information to a carrier environment, and receiving response on freight status from the carrier environment.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The advantages and features of the present invention will become better understood with reference to the following detailed description and claims taken in conjunction with the accompanying drawing, in which:

[0013] FIG. 1 illustrates a freight information management system 100 implemented in a freight forwarder environment 200 connected to a carrier environment 300, according to an embodiment of the present invention;

[0014] FIG. 2a is a block diagram of a library deployment mode of the freight information management system, according an embodiment of the present invention;

[0015] FIG. 2b is a block diagram of a localized web deployment mode of the freight information management system, according to an embodiment of the present invention; [0016] FIG. 3 is a block diagram of a centralized web deployment mode of the freight infomiation management system, according to an embodiment of the present invention;

[0017] FIG. 4 illustrates a flow diagram of a method for freight information management, according to an embodiment of the present invention; and

[0018] FIG. 5 illustrates an implementation of the freight information management of present invention for communicating with an airline environment.

DETAILED DESCRIPTION OF THE INVENTION

[0019] The exemplary embodiments described herein detail for illustrative purposes are subject to many variations in structure and design. It should be emphasized, however, that the present invention is not limited to a particular freight information management system and method as shown and described. It is understood that various omissions and substitutions of equivalent s are contemplated as circumstances may suggest or render expedient, but these are intended to cover the application or implementation without departing from the spirit or scope of the claims of the present invention. Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting.

[0020] The use of terms "including," "comprising," or "having" and variations thereof herein are meant to encompass the items listed thereafter and equivalents thereof as well as additional items. Further, the terms, "a" and "an" herein do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item .

[0021] The present invention provides a freight information management system and method that can be directly or indirectly implemented in a freight forwarder environment. While implemented in a freight forwarder environment, the system and method can be directly used by freight forwarders and/or cargo handlers for communicating on freight consignments with a carrier. [0022] As used herein, "freight infomiation" refers to infomiation on organization and shipping of freight. Herein, freight infomiation is referred to and to be interchangeably meant as "consignment information". Particularly, consignment information is information on the freight once it takes the shape of a consignment.

[0023] Specifically, the system can be directly plugged into the freight forwarder environment and can be invoked from a user interface of the freight forwarder environment. The system of the present invention can be used by a user to carry out one or more of the following activities: submitting consignment information; processing consignment information in a format readable by the carrier environment; sending the processed consignment information to the carrier environment; querying consignment status from the carrier environment; receiving response on consignment status from the carrier environment; submitting and receiving feedbacks; and modifying consignment information based on feedback. Overall, the system and method of the present invention provide a tool that can be directly or indirectly installed in a freight forwarder info iation technology (IT) environment for communicating with a carrier IT environment.

[0024] Referring to FIG. 1, illustrated is a freight infomiation management system 100 (hereinafter referred to as system 100) implemented in a freight forwarder environment 200. The freight forwarder environment is capable of communicating with a carrier environment 300 through the system 100 for managing freight information.

[0025] As used herein, freight refers to goods and other materials transported particularly in bulk by a carrier such as, truck, train, ship, aircraft, and similar transportation means. Also, as used herein, a "freight forwarder" refers to a person or company that organizes shipments for individuals or corporations to get goods from manufacturer or producer to markets, customers and other end user destinations. Hereinafter a freight forwarder is referred to as "user" of the system and method of the present invention. Such a user of the system also includes cargo handlers and other personnel who require communication with carrier environment for freight information management.

[0026] Further, as used herein a "freight forwarder environment" refers to an environment in which freight forwarders operate. Specifically, freight forwarder environment is framework of IT and other resource platforms used by freight forwarders. The freight forwarder environment is used for organizing shipments for individuals or corporations to get goods from manufacturer or producer to markets, customers and other end user destinations. Specifically, the freight forwarder environment comprises the national / international universal computer system / network platform concept, communication utility, load arranging clearinghouse and load / equipment optimization, rate / bid, equipment availability engine for shippers in the freight transportation industry. Such freight forwarder environments work closely with business to business (B2B) environment serving shippers, third party logistics companies (3PL), brokers, broker carriers, other freight forwarders, warehouses and other related industry parties for the transportation of individual or group freight.

[0027] As used herein, carrier refers to entity that transports goods from an origin to a destination. The carrier may transport goods domestically and/or internationally. The carrier may transport goods using trucks, trains, planes, ships, and/or the like.

[0028] Further, as used herein a "carrier environment" refers to an environment or infrastructure in which carriers operate. Specifically, carrier environment is framework of IT and other resource platforms used by carriers. The carrier environment is used for maintaining the freight details and transporting the freight using tracks, trains, planes, ships, and/or the like to the end user destinations. Such destinations may be domestic or international. The earner environment comprises one or more computer systems supporting an interface that enables exchange of information with the carrier. Such interface enables multiple users and multiple carriers to communicate with each other.

[0029] The system 100 comprises: an application programming interface

(API) 102; a freight information processing module 104; and a carrier communication modulel06.

[0030] The API 102 is capable of being invoked by a user interface of the freight forwarder environment for submitting and extracting consignment information. Due to presence of the API 102, the system 100 serves as a software library that can be directly used by a freight forwarder for submission of information to carrier environment. Specifically, the library provided by. the system 100 can be directly invoked and used by the freight forwarder to submit freight information to the carrier.

[0031] Such a feature of the system 100 provides for a freight management system that is implemented at the source of data (that is, the freight forwarder environment) and exposes an API that can be invoked for submitting freight information. Also, such a feature eliminates the need for dual entry, one in the user interface of the freight forwarder environment 200 and a second one in a user interface of the system 100. Additionally, the system 100 has a native user interface that can also be used for submission and extraction of freight information. The native user interface can be used for submission of freight information by users who have not performed tighter integration with their own IT system. Submission of information via the native user interface can be done independently or in addition to submission of information via the direct invoking of API 102 by the user interface of the freight forwarder.

[0032] As used herein, the API 102 is a set of commands, pre defined functions, and protocols capable of interacting with the freight forwarder IT environment. Specifically, the API 102 can be invoked by user interface of the freight forwarder environment to perform submitting and extracting freight information. Specifically, submitting and extracting freight information includes one or more of the following activities, but not limited to, entering and submitting freight information, querying freight information, receiving and extracting freight information, entering and receiving feedbacks on freight status, and modification of freight infom ation.

[0033] As used herein, the user interface refers to human-machine interaction wherein interaction between humans and machines occurs. This interaction is effective operation and control of the machine on the user's end, and feedback from the machine, which aids the operator in making operational decisions.

[0034] The system 100 offers freight information submission via JAVA based systems or REST based systems. In one embodiment, the API 102 is a JAVA based API which uses JAVA based IT systems. The JAVA API facilitates simple program to program communication of the freight forwarder environment 200 with the system 100. In another embodiment, the API 102 is a Representative State Transfer (REST) based API. [0035] As used herein REST is a simple stateless architecture that runs over Hypertext Transfer Protocol (HTTP). REST involves reading a designated Web page that contains an Extensible Markup Language (XML) file. The XML file describes and includes the desired content. REST is used in mobile applications, social networking Web sites, mashup tools and automated business processes. REST based API 102 can be used in freight forwarder environments that do not use JAVA based IT systems. Herein, the freight forwarder environment 200 sends payload in JavaScript Object Notation (JSON) or property based formats.

[0036] As used herein, JSON refers to open standard format that uses human-readable text to transmit data objects consisting of attribute-value pairs. JSON is used primarily to transmit data between a server and web application.

[0037] The freight information processing module 104 takes the freight information from the freight forwarder environment 200 through the API 102 and processes the freight information to form processed freight information which is acceptable and understandable by the earner environment 300. Such processing is done when the system 100 is active. Specifically, the processing of freight information includes validating, formatting and translating the freight information.

[0038] The carrier communication module 106 enables connection of the system 100 with the carrier environment 300. Specifically, the carrier communication module 106 is capable of: sending the processed freight information to the carrier environment 300; and receiving response on the freight status from the carrier environment 300. The carrier communication module 106 works like an adapter for enabling connection of the system 100 with the carrier environment 300. The carrier communication module 106 takes the processed freight information from the freight information processing module 104 and sends the processed freight information to the carrier environment 300. The carrier communication module 106 further receives the response from the carrier environment 300 which is communicated to other modules of the system 100 for sharing with the user of the freight forwarder environment 200.

[0039] Further, the system 100 comprises a user profile module 108 which is capable of customizing the system 100 for a user. Specifically, the user profile module 108 customizes the system 100 as per the requirement of the freight forwarder environment 200. The profile module 108 comprises customization components including, but not limited to, field data defaults and transmission set up.

[0040] The system 100 further comprises a history module 110. The history module 110 is capable of tracking the submitted freiglit information. Specifically, the history module 110 keeps track on the data submitted by the freight forwarder environment 200 to the earner environment 300 and vice versa via the system 100. The history module 110 comprises a database for storing of such transmitted data from the freight forwarder environment 200 to the carrier environment 300 and vice versa via the system 100. Using the system 100, the users can query the history of the transmitted data.

[0041 ] The system 100 further comprises a web services module 1 12. The web services module 112 is capable of connecting the system 100 with the World Wide Web (internet). Specifically, the web service module 112 connects the system 100 with the server which is situated outside/inside the freight forwarder environment 200. Such communication between the system 100 and server is done through internet or Hypertext Transfer Protocol Secure (HTTPS).

[0042] The system 100 further comprises a framework and utilities module 1 14 providing framework and utility functions to be used by the system 100. Specifically, the framework and utilities module 1 14 provides the reusable components and utility functions that may otherwise be used by various modules present in the system 100 as described above. The framework and utility module 1 14 comprises custom Extensible Markup Language (XML) handlers, test utilities, logging utilities and system 100 configuration programs.

[0043] FIG. 2a is a block diagram of a library deployment mode of the system 100 to the freight forwarder environment 200 that uses JAVA based IT systems. As used herein deployment modes refers to set of all activities that makes the system 100 available for use in the freight forwarder environment 200. In the library deployment mode, the system 100 is integrated within a core management module 200a of the freight forwarder environment 200. In this deployment mode, the system 100 uses JAVA based IT systems for communicating with the carrier environment 300. [0044] As used herein, the core management module 200a refers to the main processing/computer system or database system which is within the freight forwarder environment 200. The core management module 200a is the main/core data management system which comprises all the information related to the freight bookings and delivery.

[0045] The library deployment mode is implemented using a JAVA based

API and code samples. As used herein code samples refers to the programming codes which are used for integration of the system 100 with the freight forwarder IT system 200a. Specifically, such library deployment mode as illustrated in FIG. 2a is JAR dependent. As used herein JAR refers to archive file format which is used to aggregate many Java class files and associated metadata and resources (text, images and so on) into one file to distribute application software or libraries on the Java platform.

[0046] FIG. 2b is a block diagram of a localized web deployment mode of the system 100. In the localized web deployment mode, the system 100 is integrated within a separate runtime environment of the freight forwarder environment 200. In this deployment mode, the system 100 uses non JAVA based IT systems for communicating with the carrier environment 300. In the localized web deployment mode, the deployment of the system 100 is within the freight forwarder environment 200, however outside the core management module 200a. Although the system 100 is outside the core management module 200a, the system 100 is in operative communication with the core management module 200a.

[0047] In the localized web deployment mode, the system 100 is deployed in a web container present in the local web server present in the freight forwarder environment 200. Examples of web containers include, but are not limited to, TOMCAT servers. Further, such deployment is WAR dependent. As used herein WAR refers to a JAR file used to distribute a collection of Java Server Pages, Java Servlets, Java classes, XML files, tag libraries, static web pages (HTML and related files) and other resources that together constitute a web application. Further, the freight forwarder IT system 200a is in communication with the system 100 via REST interface, JSON and property based payload. Specifically, REST interface consume the plaintext payload and adhere to the JSON and property based payload format. Such communication is for transferring data /information from the freight forwarder IT system 200a to the system 100 [0048] FIG. 3 is a block diagram of a centralized web deployment mode of the system 100. In the centralized web deployment mode, the system 100 is, integrated , within a host environment 10 outside the freight forwarder environment 200. In this deployment mode, the system 100 uses non JAVA based IT systems for communicating with the carrier environment 300.

[0049] As used herein host environment 10 refers to centralized web server outside the freight forwarder environment 200.

[0050] In the centralized web deployment mode, the system 100 is deployed in a web container present in the web server outside the freight forwarder environment 200. Such examples of web containers, include, but are not limited to, TOMCAT servers. Further, such deployment is WAR dependent. In the centralized web deployment mode the freight forwarder IT system 200a is in communication with the system 100 via REST interface, JSON and property based payload. Specifically, REST interface consume the plaintext payload and adhere to the JSON and property based payload format. Such communication is for transferring data /information from the core management module 200a to the system 100.

[0051] FIG. 4 illustrates a flow diagram of a method 400 for freight information management according to an embodiment of the present invention. The method 400 depicted in flow diagram is executed by the system 100 in coordination with the freight forwarder environment 200, and carrier environment 300 of FIG. 1. Operations of the flowchart, and combinations of operation in the flowchart, may be implemented by various means, such as hardware, firmware, processor, circuitry and/or other device associated with execution of software including one or more computer program instructions. The operations of the method 400 are described with help of the system 100, the freight forwarder environment 200, the carrier environment 300, the library deployment mode, the localized web deployment mode and the centralized web deployment mode. The method 400 starts at operation 402. [0052] At 402, the method comprises invoking an application programming interface (API) 102 present of the system 100 by a user interface of the freight forwarder environment 200. The API is invoked by a user every time when there is a requirement for submitting and extracting freight information.

[0053] At 404, the method comprises validating, formatting and translating the freight information to form processed freight. Such validating, formatting and translating is done by freight processing module 104 as illustrated in FIG. 1.

[0054] At 406, the method further comprises sending the processed freight information to the carrier environment and receiving response on the freight status from the carrier environment.

[0055] FIG. 5 illustrates an implementation of the freight information management system and method of present invention for communicating with an airline environment. At 502, the freight forwarders enter consignment/freight data into a freight forwarder environment. Such freight data is stored in the database present in the freight forwarder environment.

[0056] ' At 504 the mode for the transport of the freight is decided. Such mode comprises trucks, trains, planes, ships, and other freight transportation mechanisms. At 506, the system checks whether the freight is transported via airline. If the transportation mode is not airlines then other transport options are explored. If the consignment is transported via airline then at 508, booking of the shipment with the airline environment 516 is carried out using the freight information management system of the present invention. At 512, the system checks whether the shipment is ready for drop off. If yes, then at 514 the freight data is transferred to airline environment at 516 via the freight information management system of the present invention. If the shipment is still not ready, then the system waits until shipment is ready for drop off.

[0057] Without in any way limiting the scope, interpretation, or application of the claims appearing below, advantages of one or more of the exemplary embodiments disclosed herein includes such as eliminating the need for dual entry,, one in the user interface of the freight forwarder environment and a second one in a user interface of the system. The methods and systems of the present invention provide a tool that can be directly installed in a freight forwarder information technology (IT) environment for communicating with an airline IT environment.

[0058] Further, in conventional freight information management system, a significant amount of time and effort is spent on performing the manual entry of the freight data in the carrier environment. Such manual entry leads to the dual entry and the rework by the freight forwarder staff to perform the entry of the freight infomiation which is already present in the freight forwarder environment. Further, in another conventional freight information management system which uses IATA cargo IMP messages, comprises higher message transmission cost is invested and use of private networks and further the transmission mode is asynchronous. Yet, in another conventional freight infomiation management system which uses paper documents are prone to failures because of issues such as inefficiencies of generation, tracking and maintenance. The present invention o ercomes the drawbacks inherent in the prior art offering some added advantages.

[0059] Also, techniques, devices, subsystems and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present technology. Other items shown or discussed as directly coupled or communicating with each other may be coupled through some interface or device, such that the items may no longer be considered directly coupled to each other but may still be indirectly coupled and in communication, whether electrically, mechanically, or otherwise, with one another. Other examples of changes, substitutions, and alterations ascertainable by one skilled in the art, upon studying the exemplary embodiments disclosed herein, may be made without departing from the spirit and scope of the present technology.

[0060] It should be noted that reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages should be or are in any single embodiment. Rather, language referring to the features and advantages may be understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment may be included in at least one embodiment of the present technology. Thus, discussions of the features and advantages, and similar language, throughout this specification may, but do not necessarily, refer to the same embodiment.

Claims

1. A freight information management system implemented in a freight forwarder environment, comprising:

an application programming interface capable of being invoked by a user interface of the freight forwarder environment for submitting and extracting freight information; a freight information processing module capable of validating, formatting and translating the freight information received through the application programming interface, to form processed freight information; and

a carrier communication module capable of

sending the processed freight information to a carrier environment, and receiving response on freight status from the carrier environment.

2. The system of claim 1 , further comprising a native user interface for submission and extraction of freight information.

3. The system of claim 1, further comprising a user profile module capable of customizing the system for a user.

4. The system of claim 1, further comprising a history module capable of tracking the submitted and extracted freight information.

5. The system of claim 1, further comprising a web services module capable of connecting the system with the World Wide Web.

6. The system of claim 1 , further comprising a framework and utilities module providing framework and utility functions to be used by various modules of the system.

7. The system of claim 1, wherein the application programming interface is a JAVA based interface.

8. The system of claim 1 , wherein the application programming interface is a Representative State Transfer (REST) based interface.

9. The system of claim 1 , wherein the system is incorporated within a core management module of the freight forwarder environment.

10. The system of claim 1 , wherein the system is incorporated within the freight forwarder environment and in operative communication with a core management module of the freight forwarder environment.

1 1. The system of claim 1 , wherein the system is integrated within a host environment in operative communication with the freight forwarder environment.

12. A freight information management method, comprising:

invoking an application programming interface by a user interface of a freight forwarder environment for submitting and extracting freight information;

validating, formatting and translating the freight information to form processed freight information; and

sending processed freight information to a carrier environment, and receiving response on freight status from the carrier environment.