Shippers' Declaration for Dangerous Goods

More documents

Recommendations

Info

- IATA updated the definition and the matrix in the specification accordingly with theproposed changes.RESPONSE TYPEReceived Processed RejectedRESPONSESUMMARYCATEGORIESAcknowledgement Optional Mandatory ProhibitedWarning Prohibited Optional OptionalError Prohibited Prohibited Mandatory- The group endorsed the Response (Error & Acknowledgment) specification andasked IATA to make the schemas available to the group.7. Technical Discussion- IATA reminded that the UTF8 would be the default character set however localrequirements may require a bilateral agreement for a different character set.Case-Sensitivity Fields- The members emphasized the need to consider how the case sensitivity would behandled as issues arose with the EU ICS implementation with fields containinglower and upper case.- The members asked IATA to further investigate with the WCO and its Data Modelto understand how this issue was addressed on their side.- The members recognized the need to set best practice and suggested that theupper case be used.- IATA to further investigate with the WCO on the use of lower and upper case intheir Data Model.Kuehne & Nagel proposal on WSDL (Web Services Description Language) files- Samuli Hiltunen (Kuehne & Nagel) presented their proposal on WSDL (WebServices Description Language) open standard files. The purpose of thepresentation was to propose to the CXMLTF to recommend the use of the WSDLas a standard:‣ To exchange messages with common functionalities and name with theaim of keeping it simple and reusable;‣ To provide parties with the necessary information when startingimplementing synchronous systems;‣ To avoid maintaining multiple web services.- Samuli Hiltunen (Kuehne & Nagel) stated that the intention was not to impose theuse of WSDL but to ensure the CXMLTF proposed some standard in that respect.Page 10 of 16
- The group recognized the need to set standards and proposed to share thedocument with the other members of the Task Force for further consideration.- IATA to share the presentation to the other members of the Task Force members.8. Review the Customs Status Notification (CSN) message- IATA asked the members prior to the face-to-face meeting to come back to thegroup on the functions expected by Customs that the message would have toaccommodate.- The member mentioned the following:‣ The CSN was currently not used as it was designed for because themessage was not triggered from the Customs system.‣ There was a usage problem wit the CSN message as all the needed datacan’t be provided.‣ With regards to the EU ICS each Member States has its own application asno standard was available.‣ GLSHK were using CSN to distribute customs replies (Accept, Hold, andHold-Release) to both carrier and GHA systems.‣ The CSN XML message should be as flexible as possible and used tocommunicate any kind of regulatory information between any involvedparties. To achieve this the Cargo-IMP CSN message itself (which wouldrequire consultation and approval of other bodies) shouldn’t be re-purpose,but a brand new XML message that replaces the CSN would need to bedesigned adding as well functions.‣ The split entries for declared House Waybills should be considered‣ While the list below (which was a ‘non-standard’ list) maps to the ICSresponses from EU MS, there were other status types for goodsdeclarations which would need to be considered.- ACKNOWLEDGED, ACCEPTED, ACCEPTED_ARRIVAL,REJECTED, ON_HOLD (non EU), RELEASED‣ The development of a new CSN XML message should be the opportunityto possibly rectify some issues with regards to the content of the message.- The group recognized that the following items would need to be addressed:‣ Customs, Security and other regulatory information would need to be look at.‣ If there was a need of a new message and if there was, what structureshould it have?‣ Can the FSU message with the OCI line meet the CSN requirement?- The members emphasized the need to have a clear business understanding ofthe interface between the Customs and Ground Handlers as well as whatinformation could be provided.Page 11 of 16
Page 1 and 2: Cargo XML Task ForceFace-to-Face Me
Page 4 and 5: - IATA mentioned that in EDIFACT th
Page 6 and 7: proprietary to Cargo 2000 IATA woul
Page 8 and 9: ULD Number Details (= Optional)- A
Page 12 and 13: - The group agreed to set up a work
Page 14 and 15: ‣ Develop the updated schemas for
Page 16: EGYPTAIR CARGOEMIRATESEMIRATESFEDEX

Shippers' Declaration for Dangerous Goods

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?