300 likes | 819 Views
2. 34th IMO/FAL Committee Meeting Report. 34th IMO/FAL Committee Meeting was held on 26-30 March 2007 in London (International Coffee Organization)EDI Working Group (WG2) met 26-28 March under the chairmanship of Kenji ItohMajor tasks of the Group are:To revise the FAL Compendium (2001 version);
E N D
1. 1 34th IMO/FAL Committee Meeting Report For SMDG Meeting
April 24 – 26, 2007
Piraeus, Athens
Kenji Itoh (Japan)
2. 2 34th IMO/FAL Committee Meeting Report 34th IMO/FAL Committee Meeting was held on 26-30 March 2007 in London (International Coffee Organization)
EDI Working Group (WG2) met 26-28 March under the chairmanship of Kenji Itoh
Major tasks of the Group are:
To revise the FAL Compendium (2001 version);
To develop a uniform ship’s pre-arrival electronic message taking into consideration SOLAS Chapter XI-2, the ISPS Code and MSC/Circ.1130; and
To develop the Single Window System for the exchange and management of information in Port Community.
3. 3
4. EDI Implementation of IMO FAL Forms
5. 5 More about UNSMs
6. 6
7. 7
8. 8
9. 9
10. 10
11. 11
12. 12 DOC DOCUMENT/MESSAGE DETAILSFunction: To identify documents and details directly related to it. ----------------------------------------------------------------------
010 C002 DOCUMENT/MESSAGE NAME M 1
1001 Document name code C an..3 (36 - Seaman‘s passport)
1131 Code list identification code C an..17
3055 Code list responsible agency code C an..3
1000 Document name C an..35
020 C503 DOCUMENT/MESSAGE DETAILS C 1
1004 Document identifier C an..35
1373 Document status code C an..3
1366 Document source description C an..70
3453 Language name code C an..3
1056 Version identifier C an..9
1060 Revision identifier C an..6
030 3153 COMMUNICATION MEDIUM TYPE CODE C 1 an..3
040 1220 DOCUMENT COPIES REQUIRED QUANTITY C 1 n..2
050 1218 DOCUMENT ORIGINALS REQUIRED QUANTITY C 1 n..2
----------------------------------------------------------------------
13. 13 COM COMMUNICATION CONTACTFunction: To identify a communication number of a department or a person to whom communication should be directed. ----------------------------------------------------------------------
010 C076 COMMUNICATION CONTACT M 3
3148 Communication address identifier M an..512
3155 Communication address code qualifier M an..3
----------------------------------------------------------------------
14. 14 TSR TRANSPORT SERVICE REQUIREMENTSFunction: To specify the contract and carriage conditions and service and priority requirements for the transport. ----------------------------------------------------------------------
010 C536 CONTRACT AND CARRIAGE CONDITION C 1
4065 Contract and carriage condition code M an..3
1131 Code list identification code C an..17
3055 Code list responsible agency code C an..3
020 C233 SERVICE C 1
7273 Service requirement code M an..3
1131 Code list identification code C an..17
3055 Code list responsible agency code C an..3
7273 Service requirement code C an..3
1131 Code list identification code C an..17
3055 Code list responsible agency code C an..3
030 C537 TRANSPORT PRIORITY C 1
4219 Transport service priority code M an..3
1131 Code list identification code C an..17
3055 Code list responsible agency code C an..3
040 C703 NATURE OF CARGO C 1
7085 Cargo type classification code M an..3
1131 Code list identification code C an..17
3055 Code list responsible agency code C an..3
----------------------------------------------------------------------
15. 15
16. 16 Fact-finding through activities (5) D.05B PAXLST has GID segment (Goods items details) in Gr.6 under Gr.4 to indicate the personal effects associated with a passenger or crew members.
There was a comment at the last TBG3 meeting in Barcelona that it was not suitable to use PAXLST for “Ship’s Store Declaration” and it would be much better to add TDT segment in “INVRPT” message.
17. 17
18. 18 Security-related message requested by the MSC/Circ.1130 – Three Options CUSREP (Customs Conveyance Report)
BERMAN (Berth Management)
Develop a new message “SECREP”
A comparison of the first two options showed that the segments in options 1 and 2 contained too many free text (FTX) segments which are not appropriate in the use of electronic data.
19. 19
20. STANDARD DATA SET OF SECURITY-RELATED INFORMATION (1) Requested by MSC/Circ.1130
21. STANDARD DATA SET OF SECURITY-RELATED INFORMATION (2)
22. STANDARD DATA SET OF SECURITY-RELATED INFORMATION (3)
23. STANDARD DATA SET OF SECURITY-RELATED INFORMATION (4)
24. STANDARD DATA SET OF SECURITY-RELATED INFORMATION (5)
25. STANDARD DATA SET OF SECURITY-RELATED INFORMATION (5)
26. 26
27. 27 More thought about FAL Form 7 (Dangerous Goods Manifest) Based on the outcome of the 11th session of the Sub-Committee on Dangerous Goods, Solid Cargoes and Containers (DSC), some additional information should be entered ((See document FAL 34/11, Annex).
For this purpose, the current FAL Form 7 is also amended to allow entering such additional information.
In this regard, the FAL 34 decided as follows (extract from doc FAL 34/WP.8):
11.11 In the above context, having noted that as it had already agreed on the provision for additional information in IMO FAL Form 7, which is in line with the provisions of IMDG Code, IATA Dangerous Goods Transport Document and UN/CEFACT draft revised Recommendation 11, the Committee approved, with the view to adoption at FAL 35, the following draft amendments to the FAL Convention:
28. 28 More thought about FAL Form 7 (Dangerous Goods Manifest) (2) .1 at the end of Standard 2.8.1, the following new item is added:
“·Additional information.”, and
.2 in appendix 1, below IMO FAL Form 7, a box containing the text “Additional information:….” is inserted.
11.12 The Committee recalled that it referred the outcome of DSC 11 in relation to matters pertaining to the revision of the IMO Compendium on Electronic Business to the Working Group on Electronic means for the clearance of ships for the necessary actions on the understanding that the group will be informed of any salient issues which may transpire during the consideration of the matter under this agenda.
This should be consulted with “PROTECT” Group for further necessary amendment of IFTDGN message.
29. 29 Next IMO/FAL Committee meeting and other related meetings Schedule UN/CEFACT Plenary, 14-16 May, 2007, Geneva
WCO DMPT Meeting, xx-xx June, 2007, Brussels
TBG3 Interim Meeting, 2-6 July, 2007, Oslo
UN/CEFACT Forum, 24-28 Sept., 2007, Stockholm
No.50 SMDG Meeting, 22-26 Oct., 2007, Salerno
TBG3 Interim Meeting, xx-xx Jan., 2008, Paris (?)
UN/CEFACT Forum, xx-xx March, 2008, USA (?)
……………
IMO/FAL 35 Meeting, 8-12 September, 2008
Venue: IMO Headquarter Building, London
30. 30 Thank you for your attention!