輸送関係国際グループとの連携 - モデル事業について海外への展開

6.3. モデル事業について海外への展開

6.3.2. 輸送関係国際グループとの連携

モデル事業は、港湾物流におけるB2B (Business to Business) の部分、特に電子化が遅れている海上コンテナの陸上輸送部分に焦点を当てて、シームレスな貨物関係情報の電子化を図り、情物一致による物流の効率化、セキュリティの確保を達成することで、わが国港湾物流の国際競争力の強化に繋げようとするものである。

すでに、この分野における貨物情報の交換のための国際標準メッセージのMIG化については、

下記の図よりもわかる通り、国内外のグループにおいて既に開発を完了し、すでに使用しており、

そのMIGを一般に公開しているため、これが利用できることがモデル事業にとって大きな利点であった。（MIGを最初から開発する必要がなかった。）

従って、我々が留意したのは、1 つのメッセージのある業務への適用の妥当性を開発グループに確認すること、またセグメント、データエレメント、コード等に変更、追加の要求がモデル事業参加企業体から提起された場合、それを当該グループに対して DMR（データ保守要求）として提出することであった。（今回、モデル事業参加企業体よりの具体的なDMRの提出の要請はなかった。）

輸送関係国際グループとの連携のイメージ

UN/CEFACTフォーラム

TBG

（国際貿易・ビジネスプロセスG)

ICG

（情報コンテンツ管理G)

ATG

（技術応用G)

TMG

（技術・方法論G)

（法律関係G)

TBG2－輸送WG

TBG3ー通関WG TBG14ーBPAWG TBG15ーITPWG TBG17ーハーモナ イゼイション＆ドキュメンテーション

TBG19ーeGov

ITIGG

（国際輸送実施ガイドラインG)

SMDG

（船社とコンテナターミナルのためのユーザグループ)

PROTECT

IFTMシリーズの MIG開発のためのガイドラインを作成 1. 一般勧告 2. P&R文書 3. 実施参照ガイド

コンテナ関係の CoxxxxメッセージやBAPLIE等の MIGを開発

B2GのためのMIG を開発

BERMAN IFTDGN WASDIS APERAK

IMO/FAL委員会 ISO/TC154

港湾物流情報プラットフォーム実現に向けたモデル事業

モデル事業に関するプレゼンテーション資料

Port Logistics Information Platform Model Project in Japan

For 48^thSMDG Meeting, Sydney

Kenji Itoh Executive Director, JASTPRO Former UN/CEFACT Vice-chair & Rapporteur for Asia

PLIPF Model Project 2

Contents

Mission of the Project

What kinds of MIG to be used in the Project?

Further actions if there may be discrepancy between the

SMDG’s MIG and MIG developed in the Project

PLIPF Model Project 3

Mission of the Project

Towards the Effective Port Logistics which has

Towards the Effective Port Logistics which has international competitiveness:

international competitiveness:

to avoid cost increase and time delay by re-

to avoid cost increase and time delay by re

-entering entering

information and to reduce stocks

to meet the US 24 hours rule and to shorten cut-

to meet the US 24 hours rule and to shorten cut

-off off

date of container (at least 24 hours from 72 hours

before loading to 48 hours)

to develop a seamless container information flow

to develop a seamless container information flow from a consignor to a container terminal (for export),

from a consignor to a container terminal (for export),

and from a container terminal to a consignee (for

import).

PLIPF Model Project 4

Image of Port Logistics Information Platform (Current Situation)

Carry in ⇒ Stuffing

Consignor Tally Co./Sworn

Measurers Trucker Terminal

Operator

Carrier Loading

（To ship cargo）

To improve cargo flow and information flow

CY/Docs Cut-off

（3 days prior to ship）

To send M/F data to US Customs

Forwarder Customs Br.

（Possible to shorten by using EDI)

Current：No seamless electronic information flow

EDI Fax・Phone・Paper EDI

Ａcompany’s system _NACCS

Exchange docs/Re-enter information Need to use ＥＤI Exchange docs/Re-enter information

Model Project: Electronic Container Information Exchange

EDI Fax・Phone・Paper EDI

PLIPF Model Project 5

Image of Port Logistics Information Platform (Future Plan)

Carry in ⇒ Stuffing

Consignor Tally Co./Sworn

Measurers Trucker Terminal

Operator

Carrier Loading

（To ship cargo）

To improve cargo flow and information flow

CY/Docs Cut-off

（3 days prior to ship）

To send M/F data to US Customs

Forwarder Customs Br.

（Possible to shorten by using EDI)

NACCS

EDI EDI

To be：To shorten the haulage time (and reduce stocks) by the seamless EDI

EDI

Based on Standard Formats (Platform)

Model Project: Electronic Container Information Exchange

PLIPF Model Project 6

What kinds of MIG to be used in the Project?

Two company groups were selected for the Model Project.

Invoice ＆P/L（INVOIC）

Containerized Cargo Information （IFTMIN) Shipping Instructions Information （IFTMIN) Booking Info from Carrier to

Container Terminal （IFTMBC）

Empty Container Pickup Order

& Response （COPARN）

Empty Container Shipping Order Info （IFTMIN）

Empty Container No. Info (COPINO)

UNSMs to be used

Export: Stainless Steel Coil

& Electric Goods Import: Plastic Injection Mold Export:

Construction machinery parts Outline of Logistics

Matsushita Electric Industrial Co Ltd

Atrize Yodogawa Co Ltd MBK （Komatsu）

Shipper

Osaka Area Tokyo Area

Area

Issues:

・Business scenario of the container messages developed by SMDG should be referred to make decision of what kind of message is suitable for implementing;

・MIGs developed by JILS (called as ‘GEDIS MIGs’ based on SMDG & ITIGG documents) should be referred for implementation;

・MIGs developed by NACCS should be reviewed whether in compliance with WCO Data Model and ITIGG documents.

PLIPF Model Project 7

MBK Group – Business Scenario

Booking Info （and Change, Cancel) by Phone/FAX

Firm Booking &

Change/Cancel (IFTMBC)

Empty Container Pickup Order (COPARN)

Empty Container Pickup Order (Reply) (COPARN)

Container Carriage Instructions (IFTMIN)

Pickup Order No.

(COPARN)

Container No.

(IFTMBC)

Container Carriage Instructions (IFTMIN)

Shipper

Shipping Company

Container Terminal

Haulier Forwarder

Warehouse

PLIPF Model Project 8

Matsushita/Goto Kaisoten Group – Business Scenario

Request for Import Declaration (INVOIC)

Shipping Instructions Info (IFTMIN)

Shipping Instructions Info (IFTMIN) Invoice & P/L Info for

Export Declaration (INVOIC)

Invoice & P/L Info (INVOIC)

Mixed Container Info

(COPARN)

Shipper (Matsushita)

Shipper (Atlize Yodogawa)

NACCS*

Forwarder

(Goto Kaisoten) (via Sea-NACCS System)

*NACCS: Nippon Automated Customs Clearance System

PLIPF Model Project 9

Roadmap of Model Projects

Contract between Project Groups

Jastpro Contract

between MLIT &

Jastpro Selecti

on of Project Groups

Mar Feb Jan Dec Nov Oct Sep Au g Jul Jun May Apr Mar

2006 2007

Model Projects

Evaluation &

Reporting

PLIPF Model Project 10

List of MIGs already developed

Not confirmed yet about harmonization with SMDG &

ITIGG documents COPARN COPINO COSTCO DESADV IFTMAN IFTMCS IFTMIN IFTSTA

GEDIS

INVOIC (Incl.

P/L）

IFTMIN IFTMCS SC/SF-Net CUSRES

CUSREP CUSCAR CUSDEC (not implemented）

PAXLST CODECO COPARN IFTMIN APERAK CONTRL NACCS

Not confirmed yet about harmonization with SMDG &

ITIGG documents IFTMIN COSTCO APERAK IFTMCS

POLINET

DMRs will be submitted to the oganization if required.

Remarks

BERMAN IFTDGN WASDIS APERAK CALINF

COARRI CODECO CODENO COEDOR COHAOR COPARN COPINO COPRAR COREOR COSTCO COSTOR DESTIM VESDEP ITIGG develops guidelines

to develop MIGs for IFTM series messages:

1. General recommendation 2. Principles & Rules 3. IFCSUM (M/F) =

CUSCAR Message

Type

PROTECT TBG３ ←ITIGG SMDG

Bodies

Note: ITIGG uses M, R, D, O, X as a usage indicator.

PLIPF Model Project 11

Further actions if needed

If there may be differences between the SMDG’s MIG and MIG developed in the Project

To submit DMRs to SMDG first (then UN/CEFACT TBG3) for consideration

UN Standard Messages developed and used in the project should be reused under the Port Logistics Information Platform (= JCL Net) for more effective port logistics.

PLIPF Model Project 12

Thank you for your attention

！

Welcome your comments and suggestions.

Kenji Itoh ([email protected])

第33回IMO/FAL会議に関するプレゼンテーション資料

33

^rd

IMO/FAL Committee Meeting Report

For SMDG Meeting

Oct. 31 – Nov.2, 2006

Sydney, Australia

Kenji Itoh (Japan)

33

^rd

IMO/FAL Committee Meeting Report

33^rdIMO/FAL Committee Meeting was held on 3-7 July 2006 in London (IMO Headquarters)

EDI Working Group (WG1) met 3-5 July 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.

EDI Implementation of IMO FAL Forms

¾FAL Form1 (General Declaration) CUSREP

¾FAL Form2 (Cargo Declaration) CUSCAR

¾FAL Form3 (Ship’s Store Declaration) INVRPT

¾FAL Form4 (Crew Effects Declaration)

-¾FAL Form5 (Crew List) PAXLST

¾FAL Form6 (Passenger List) PAXLST

¾FAL Form7 (DG Manifest) IFTDGN

¾ISSP Code (MSC/Circ.1130)

IMO FAL Forms v.s. UNSMs suggested by FAL Compendium FAL Compendium

(→PAXLST) (→PAXLST)

BERMAN

(Red-colour shows proposed UNSMs suggested by Japanese Group)

More about UNSMs

Passenger List PAXLST

(Current INVREP has no TDT segment.)

7 6 5 4 3 2 1

Dangerous Goods Manifest IFTDGN

Dangerous Goods Manifest

Passenger List PAXLST

Passenger List

Passenger List PAXLST

Crew List Crew Effects Declaration

Inventory Report INVREP

Ship’s Store Declaration

Customs Cargo Report CUSCAR

Cargo Declaration

Customs Conveyance Report CUSREP

General Declaration

UNSM – Message Name UNSM

Message Type FAL Form

Fact-finding through activities (1)

1. FAL Form 1 (CUSREP):

“RFF” segment to be added within TDT segment group since

“Call Sign” needed in addition to “IMO Number”

2. FAL Form 2 (CUSCAR):

“RFF” segment to be added within TDT segment group since

“Call Sign” needed in addition to “IMO Number”

3. FAL Form 3,4,5,6 (PAXLST):

“RFF” segment to be added within TDT segment group No.2 since “Call Sign” needed in addition to “IMO Number”

Message Structure Change should be made by TBG4

POS TAG Name (Segment)

0360 --- Segment group 8 --- C 99---+

0370 TDT Transport information M 1 | 0380 TPL Transport placement C 1 | 0390 DTM Date/time/period C 1 | 0391 RFF Reference C 9 |

| 0400 --- Segment group 9 --- C 99---+|

0410 LOC Place/location identification M 1 ||

0420 DTM Date/time/period C 9 ||

0430 QTY Quantity C 9 ||

0440 NAD Name and address C 99 ||

0450 MEA Measurements C 9 ||

0460 POC Purpose of conveyance call C 9 ||

0470 STS Status C 9 ||

0480 FTX Free text C 9---++

Message structure change in CUSREP

POS TAG Name (Segment)

0160 --- Segment group 4 --- C 9---+

0170 TDT Transport information M 1 | 0180 LOC Place/location identification C 99 | 0190 DTM Date/time/period C 99 | 0191 RFF Reference C 9---+

Message structure change in CUSCAR

0200 GEI Processing information C 9 0210 --- Segment group 5 --- C 9999---+

POS TAG Name (Segment)

0090 --- Segment group 2 --- M 10---+

0100 TDT Transport information M 1 | 0110 DTM Date/time/period M 1 |

0111 RFF Reference C 9

| 0120 --- Segment group 3 --- C 99---+|

0130 LOC Place/location identification M 1 ||

0140 DTM Date/time/period C 5---++

Message structure change in PAXLST

New code request （１）: no necessary

IMO Crew List requests to input “Nature and No.

of identity document (seaman’s passport

Fact-finding through activities (2)

)” under the column no.6.

BGM – DE1001 – 250 (Crew list declaration) – DE 1001 in DOC segment – 36 (Non-passport:

Identity card, official document to identify a person), 39 (Passport) can be applicable.

New code request （2）: no necessary

ISPS code Security message requests to input

“Security Officer”

as a NAD qualifier. However, DMR for new code request is no necessary since it is input as a Message Sender.

New code request （3）:

ISPS code Security message requests to input

“Inmarsat call numbers

Security information

Fact-finding through activities (3)

”

under the item no.1.7. This call number should be input as DE3148

(Communication address identifier) with the qualifier DE3155 (Communication address code qualifier) in COM segment. The qualifier to designate “Inmarsat”

should be added.

New code request （4）:

ISPS code Security message, under the TSR

(Transport service requirements), DE7273 (Service requirement code is necessary to input. So far there is

no code for “

”.

DOC DOCUMENT/MESSAGE DETAILS

Function: 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

---12

COM COMMUNICATION CONTACT

Function: 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

---13

TSR TRANSPORT SERVICE REQUIREMENTS

Function: 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