|
Process
Our processes are developed to work with the current bandwidth limitations prevalent in South Africa. We use the most common communication port possible and with this have achieved high, security, speed and accurate data transfers between entities.
The process flow explains how such processes operate from the Forwarding agents desk to the required destination address and back to the client.
Caspnet has written a XML schema with a soap component to integrate the data from the Freight forwarder to the required data at the airline, on the following messages:
FWB - Master AWB data
FHL - Manifest and House data for USA traffic
FSR - Freight Status requests
FSU - Freight Status Updates
FSA - Freight Status Answers
The FWB, FHL & FSR data can be exchanged from the freight forwarders desk in two methods:
A) Via Soap/XML
B) Via Synapse
Via Soap/XML
Should the Freight Agent or their service provider have the skills, it is quite simple to generate a XML file and process this via SOAP referencing the Caspnet XML URL to deliver the above messages for processing.
Via Synapse
Caspnet has also developed a communication application named “Synapse”. This tool will be loaded on the agents server where its main task is to pick up and convert “flat” files (.txt) to XML “Synapse” will then schedule the communication link and deliver the required file to Caspnet for further processing.
The choice of the two above mentioned methods reside with the freight agent and the skill-set he has on staff.
Once Caspnet receive the XML file the data will be written into the Agents own Unique sequel (SQL) database.
As part of their services Caspnet provide a Web portal to their clients, through which they can link to their database to monitor their message exchanges. Each client has direct access and can submit, track, trace and view the AWB’s submitted. The AWB’s can also be printed from the web by simply double clicking on the required message tab.
Once the data has been submitted it is translated to the Cargo-imp standard. It is then send to the destination via Caspnet’s SITA link.
Each Transport document submitted electronically to the airline will in return receive 5 status updates. These updates will be returned from the respective airline back to the client.
The airline’s standard response to the FWB or FHL messages are the following:
Rcs. – Confirm receipt of message
Man. - Manifested
Dep. - Departed
Del. - Delivered
Dis. - Discrepancies
Once the data is received back from the airlines the client’s database is updated. The data is then posted to reflect in the Clients Portal in an easy to read and understandable format.
|