(2.21) kff rel3.2 upgrade_training_material_bpi_v.1.4

© Copyright NYK Logistics 2010

KFF Rel 3.2 Upgrade TrainingBPI

Feb 2011

Version: 1.4


Agenda

1) On-Board Date Printing on HBL

2) New Documents

3) Refresh/Calculate Button

4) Destination SOP

5) Configuration Change

6) Job Structure per Scenario

7) RLJ Definition Change


1) On-Board Date Printing on HBL


1) On Board Date Printing on HBL – Change Summery

1) [Laden on Board Vessel Date] Printing Data Source Change Rel3.1: Sailing Date Rel3.2: On Board Date

2) Default value of BL Date Change Rel3.1: Sailing Date if there is no value of BL Date Rel3.2: On Board Date if there is no value of BL Date (To Be Advise)


SE BL

Print On-Board Date under HBL

Module :

SE BL -> Transport Tab

On-board Date Printing logic under HBL:

Before the date for Laden On Board vessel would take the Sailing date, now the system change to take the On-Board date.


This value is taken from SE BL -> Others-> BL Date

This value is now taken from the On-board date instead of the Sailing Date


Another Logic related to BL Date:

Others Tab -> BL Date

As-Is:

If the BL date is empty, it would be default as the sailing date (when user propagated the sailing date from VV table the House/Master jobs)

To-Be :

If the BL date is empty, it would be default as the On-Board date.

It would also allow user to amend the BL date once it had been updated as On-Board date.

SE BL

Print On-Board Date under HBL


2) New Document


New Document Session

Agenda

Overview of Operational Document

2. Document Variation

4. Document Form Comparison As-Is Document Form (KFF 3.1) To-Be Document Form (KFF 3.2)



1. Overview of Operational Document

GDS accommodates 13 basic Global Documents - EXPORT 7- IMPORT 6

Export Operational Document

Type Document Title

BC Booking Confirmation / Shipping Order

SO Shipping Order / Dock Receipt

WO Work Order

VP Vanning Plan

SEMF Consolidation Manifest

HBL BL / SWB / FCR / 3PL BL

SI Draft MBL

Import Operational Document

Type Document Title

AN Arrival Notice

DO Deliver Order

AU Delivery Order (Authorization Release)

DVP Devanning Plan

WO Work Order

SIMF Cargo Manifest



2. Document Variation

Even under the document standardization policy, we allowed some extent of variety for each document to meet local requirements Category: 2 (Global / Local) Language Support: English / Multiple Language / Local Language

English Multiple Language

Local Language

Global-Standard Layout GDS Standard Form

that can be used for most of the countries

GDS Sub Standard Form showing local language but same logic & data with Standard Form, used by multiple countries

NANA

Local- Pre-defined layout

- Specific Label

- Special data elements

Local Specific Form NANA Local Specific Form

STDSTD S-STDS-STD

LOCALLOCALLOCALLOCAL


3. Document Comparison EXPORT DOCUMENT


Type Document Title

BC Booking Confirmation / Shipping Order

SO Shipping Order / Dock Receipt

WO Work Order

VP Vanning Plan

SEMF Consolidation Manifest

HBL BL / SWB / FCR / 3PL BL

SI Draft MBL



3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - BC

Global

NL_BK_KRLocal (Korean)Local

NL_BK_MLMultiple Language

NL_SESO_SGHK

NL_SESO_SGHK_v11

EnglishLocalShipping OrderBCSO

NL_BK

NL_BK_v13

NL_BK_v15

Form ID

English

Language

Global

Category

Booking Confirmation BC

Document TitleType

(GDS 2.0) Export Operational Document

KFF Rel 3.1 (GDS 2.0) has two different types as Booking Confirmation: Booking Confirmation Shipping Order (Only for Singapore and Hong Kong)

STDSTD

S-STDS-STD

LOCALLOCAL

Draft MBLSI

BL / SWB / FCR / 3PL BLHBL

Consolidation ManifestSEMF

Vanning PlanVP

Work OrderWO

Shipping Order / Dock ReceiptSO

Booking Confirmation / Shipping OrderBC

Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType




3. Document Comparison To-Be Forms in KFF Rel 3.2 (GDS 3.0) - BC

KFF Rel 3.2 (GDS 3.0) retains the latest version under Booking Confirmation Type: Booking Confirmation : NL_BK_v16, NL_BK_ML, NL_BK_KR Shipping Order : NL_BCSO_SG, NL_BCSO_HK

NL_BK_KRLocal (Korean)Local

NL_BK_MLMultiple Language

NL_SESO_SGHK

NL_SESO_SGHK_v11 -> NL_BCSO_SG

NL_BCSO_HK

EnglishLocalShipping OrderBCSO

NL_BK

NL_BK_v13

NL_BK_v15

NL_BK_v16

Form ID

English

Language

Global

Category

Booking Confirmation

BC

Document TitleType


STDSTD

S-STDS-STD

LOCALLOCAL

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Global



3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - SO


Type Document Title Category Language Form ID

SO Shipping Order Global English NL_SO

NL_SO_v14

Local Local (Korean) NL_BK_KR

KFF Rel 3.1 (GDS 2.0) has single type as Shipping Order

STDSTD

LOCALLOCAL

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType




3. Document Comparison To-Be Forms in KFF Rel 3.2 (GDS 3.0) - SO

KFF Rel 3.2 (GDS 3.0) will have two different types but still keep only the latest version as Shipping Order:

Shipping Order : NL_SO_v14, NL_SO_KR, NL_SO_CN Dock Receipt : NL_DR_CN



SO Shipping Order Global English NL_SO

NL_SO_v14

Local Local (Korean)

Local (Chinese)

NL_SO_KR

NL_SO_CN

SODR Dock Receipt Local Local (Chinese) NL_DR_CN

STDSTD

LOCALLOCAL

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType




3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - SEWO



SEWO SE Work Order Global English NL_SEFCL

NL_SELCL

Global Multiple Language NL_SEFCL_ML

NL_SELCL_ML

Local Local (Korean) NL_SEFCL_KR

NL_SELCL_KR

KFF Rel 3.1 (GDS 2.0) has single type as SE Work Order

STDSTD

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


LOCALLOCAL

S-STDS-STD



3. Document Comparison To-Be Forms in KFF Rel 3.2 (GDS 3.0) - SEWO

KFF Rel 3.2 (GDS 3.0) will keep only the latest version as SE Work Order: SE Work Order :

NL_SEFCL / NL_SELCL

NL_SEFCL_ML / NL_SELCL_ML

NL_SEFCL_KR / NL_SELCL_KR, NL_SEFCL_CN / NL_SELCL_CN

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType




SEWO SE Work Order Global English NL_SEFCL

NL_SELCL

Global Multiple Language NL_SEFCL_ML

NL_SELCL_ML

Local Local (Korean) NL_SEFCL_KR

NL_SELCL_KR

NL_SEFCL_CN

NL_SELCL_CN

STDSTD

LOCALLOCAL

S-STDS-STD



3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - VP



VP Vanning Plan Global English NL_SE_VANNINGPLAN

NL_SE_VANNINGPLAN_v132

Global Multiple Language NL_SE_VANNINGPLAN_ML

KFF Rel 3.1 (GDS 2.0) has single type as Vanning Plan

STDSTD

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


S-STDS-STD



3. Document Comparison To-Be Forms in KFF Rel 3.2 (GDS 3.0) - VP

KFF Rel 3.2 (GDS 3.0) will keep only the latest version as Vanning Plan: Vanning Plan :


NL_SE_VANNINGPLAN_ML

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType




VP Vanning Plan Global English NL_SE_VANNINGPLAN


Global Multiple Language NL_SE_VANNINGPLAN_ML

Local Local (Chinese) NL_SE_VANNINGPLAN_CN

STDSTD

S-STDS-STD

LOCALLOCAL



3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - SEMF



SEMF SE Consolidation Manifest

Global English NL_SE_MANF

KFF Rel 3.1 (GDS 2.0) has single type as Consolidation Manifest

STDSTD

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType




3. Document Comparison To-Be Forms in KFF Rel 3.2 (GDS 3.0) - SEMF

KFF Rel 3.2 (GDS 3.0) will have only the latest version as Consolidation Manifest: Consolidation Manifest :

NL_SE_MANF

NL_SE_MANF_CN

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType





Global English NL_SE_MANF

Local Local (Chinese) NL_SE_MANF_CN

STDSTD

LOCALLOCAL



3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - HBL



HBL DWE Bill of Lading Global English NL_HBL

NL_HBL_v15

NL_HBL_v16

DWE Sea Waybill Global English NL_SWBL

NL_HBL_v13

NL_HBL_v14

FCR Global English NL_FCR

NL_FCR_v13

3PL BL Global English NL_3PL_MELCO, NL_3PL_MELCO_v13

NL_3PL_MELCO_v14

NL_3PL_UNIX, NL_3PL_JOT

NL_3PL_OTHERS_v13, NL_3PL_OTHERS_v14

NL_3PL_YUSEN

NL_3PL_YUSEN_v14

KFF Rel 3.1 (GDS 2.0) has single type as HBL while ….1) There are FOUR different Form Layout

DWE Bill of Lading DWE Sea Waybill

STDSTD

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


STDSTD

STDSTD

FCR 3PL BL (MELCO, YUSEN, OTHERS)

STDSTD



3. Document Comparison To-Be Forms in KFF Rel 3.2 (GDS 3.0) - HBL 1/3

KFF Rel 3.2 (GDS 3.0) will retain four different form layouts under HBL, and will have TWO types of DWE HBL in terms of Body Contents Structure.

1) There are FOUR different Form Layout under HBL Documents DWE Bill of Lading DWE Sea Waybill FCR 3PL BL (MELCO, YUSEN, OTHERS)

TWO type HBL-A (Existing) : Showing Items & Containers without linkage based on Job Item HBL-B (New) : Showing Item Breakdown per container based on CLP

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


NEW

HBL-A HBL-BContainer No No pf Package Goods Description ….Marks

ITEM AXXXXXXXXXXXXX

ITEM BXXXXXXXXXXX

100Cartons

20BAGS

Container No No pf Package Goods Description ….Marks

NYKUXXXXXXX1 / XXXXXXXX / 20DR / 50 PACKAGES ….NYKUXXXXXXX2 / XXXXXXXX / 20DR / 70 PACKAGES ….

MARKSXXXXXXXXXXXX

MARKS”XXXXXXXXX

ITEM AXXXXXXXXXXXXX

ITEM AXXXXXXXXXXXXX

ITEM BXXXXXXXXXXX

50Cartons

50Cartons

20BAGS

MARKSXXXXXXXXXXXX

MARKSXXXXXXXXXXXX

MARKS”XXXXXXXXX

NYKUXXXXXXX1 / 20DR

NYKUXXXXXXX2 / 20DR

Item info from Job

Container info from

CLP

Item info under Container

from CLP


from CLP




Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


KFF Rel 3.2 (GDS 3.0) will have only the latest version of two types of four forms in HBL Documents;

- HBL-A DWE Bill of Lading : NL_HBL_A, NL_HBL_LETTER_A DWE Sea Waybill : NL_SWBL_A, NL_HBL_LETTER_A FCR : NL_FCR_A 3PL BL : NL_3PL_MELCO_V14, NL_3PL_YUSEN_v14, NL_3PL_OTHERS_V14



HBL-A DWE Bill of Lading Global English NL_HBL , NL_HBL_v15, NL_HBL_v16

NL_HBL_A

Local (US) English NL_HBL_LETTER_A

DWE Sea Waybill Global English NL_SWBL, NL_SWBL_v13, NL_SWBL_v14

NL_SWBL_A

Local (US) English NL_SWBL_LETTER_A

FCR Global English NL_FCR, NL_FCR_v13

NL_FCR_A

3PL BL Global English NL_3PL_MELCO, NL_3PL_MELCO_v13

NL_3PL_MELCO_v14

NL_3PL_UNIX, NL_3PL_JOT, NL_3PL_OTHERS_v13,

NL_3PL_OTHERS_v14

NL_3PL_YUSEN, NL_3PL_YUSEN_v14

STDSTD

LOCALLOCAL

STDSTD

STDSTD

STDSTD

LOCALLOCAL




HBL-B DWE Bill of Lading

- Item Breakdown per CTN

Global English NL_HBL_B

Local (US) English NL_HBL_LETTER_B

DWE Sea Waybill

- Item Breakdown per CTN

Global English NL_SWBL_B

Local (US) English NL_SWBL_LETTER_B



Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


STDSTD

STDSTD

LOCALLOCAL

LOCALLOCAL

KFF Rel 3.2 (GDS 3.0) will have only the latest version of two types of four Forms in HBL Documents:

- HBL-B DWE Bill of Lading : NL_HBL_B, NL_HBL_LETTER_B

DWE Sea Waybill : NL_SWBL_B, NL_HBL_LETTER_B

FCR

3PL BL (MELCO, YUSEN, OTHERS)



3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - SI



SI Draft MBL

(Shipping Instruction)

Global English NL_MBL

NL_MBL_v24

Global Multiple Language NL_MBL_ML

Local Local (Korean) NL_MBL_KR

KFF Rel 3.1 (GDS 2.0) has single type as Draft MBL (Shipping Instruction)

STDSTD

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


LOCALLOCAL

S-STDS-STD



3. Document Comparison To-Be Forms in KFF Rel 3.2 (GDS 3.0) - SI 1/2

KFF Rel 3.2 (GDS 3.0) will have TWO types of Draft MBL (Shipping Instruction) in terms of Body Contents Structure following HBL Document enhancement

TWO types SI-A (Existing) : Showing Items & Containers without linkage based on Job Item SI-B (New) : Showing Item Breakdown per container based on CLP

NEW

SI-A SI-BContainer No No pf Package Goods Description ….Marks

ITEM AXXXXXXXXXXXXX

ITEM BXXXXXXXXXXX

100Cartons

20BAGS

Container No No pf Package Goods Description ….Marks

NYKUXXXXXXX1 / XXXXXXXX / 20DR / 50 PACKAGES ….NYKUXXXXXXX2 / XXXXXXXX / 20DR / 70 PACKAGES ….

MARKSXXXXXXXXXXXX

MARKS”XXXXXXXXX

ITEM AXXXXXXXXXXXXX

ITEM AXXXXXXXXXXXXX

ITEM BXXXXXXXXXXX

50Cartons

50Cartons

20BAGS

MARKSXXXXXXXXXXXX

MARKSXXXXXXXXXXXX

MARKS”XXXXXXXXX

NYKUXXXXXXX1 / 20DR

NYKUXXXXXXX2 / 20DR

Item info from Job

Container info from

CLP


from CLP


from CLP

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType




3. Document Comparison To-Be Forms in KFF Rel 3.2 (GDS 3.0) - SI 2/2

Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


Draft MBLSI



Vanning PlanVP

Work OrderWO



Document TitleType


KFF Rel 3.2 (GDS 3.0) will have only the latest version of TWO types in Draft MBL (Shipping Instruction) :

- SI-A: NL_MBL_A, NL_MBL_ML, NL_MBL_KR, NL_MBL_HK

- SI-B NL_MBL_B, NL_MBL_B_HK



SI-A Draft MBL


Global English NL_MBL

NL_MBL_v24

NL_MBL_A

Global Multiple Language NL_MBL_ML


Local (Chinese)

NL_MBL_KR

NL_MBL_HK

SI-B Draft MBL Item Breakdown - Item Breakdown per CTN


Global English NL_MBL_B

Global Multiple Language ….


Local (Chinese)

….

NL_MBL_B_HK

STDSTD

LOCALLOCAL

S-STDS-STD

STDSTD

LOCALLOCAL


3. Document Comparison IMPORT DOCUMENT


Type Document Title

AN Arrival Notice

DO Deliver Order

AU Delivery Order (Authorization Release)

DVP Devanning Plan

WO Work Order

SIMF Cargo Manifest



3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - AN

KFF Rel 3.1 (GDS 2.0) has two different types as Arrival Notice: Arrival Notice TAX Arrival Notice



AN Arrival Notice Global English NL_AN

NL_AN_V24

NL_AN_V27

Global Multiple Language NL_AN_ML

Local Local (Chinese) NL_AN_KR

NL_AN_VN

NL_AN_VN_ADJUSTED

ANTAX TAX Arrival Notice Global English NL_TAXAN

NL_TAXAN_V13

STDSTD

S-STDS-STD

LOCALLOCAL

STDSTD

Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP

Delivery Order (Authorization Release)AU

Deliver OrderDO

Arrival NoticeAN

Document TitleType


Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType




3. Document Comparison To-Be Forms in KFF Rel 3.2 (GDS 3.0) - AN

KFF Rel 3.2 (GDS 3.0) will have THREE types of Arrival Notice, and still retains the latest versions only.

Arrival Notice : NL_AN_v27, NL_AN_ML, NL_AN_KR/VN_ADJUSTED/HK/CN TAX Arrival Notice: NL_TAXAN_V13 Arrival Notice Due Bill : NL_DBAN



AN Arrival Notice Global English NL_AN, NL_AN_V24

NL_AN_V27

Global Multiple Language NL_AN_ML


Local (Vietnamese)

Local (Chinese)

NL_AN_KR

NL_AN_VN, NL_AN_VN_ADJUSTED

NL_AN_HK

NL_AN_CN

TAXAN TAX Arrival Notice Global English NL_TAXAN

NL_TAXAN_V13

DBAN Arrival Notice Due Bill Global English NL_DBAN

STDSTD

S-STDS-STD

LOCALLOCAL

STDSTD

STDSTD

Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType


Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType




3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - DO

KFF Rel 3.1 (GDS 2.0) has single type of Delivery Order:



DO Delivery Order Global English NL_SIDO


Local (Vietnamese)

NL_SIDO_KR

NL_SIDO_VN

Local (Malaysia)

English NL_SIDO_PKLC

NL_SIDO_PPLC

STDSTD

LOCALLOCAL

Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType


Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType




3. Document ComparisonAs-Is Forms in KFF Rel 3.2 (GDS 3.0) - DO

KFF Rel 3.1 (GDS 2.0) will retain the latest version of Delivery Order:Delivery Order

NL_SIDO_V20 NL_SIDO_KR/VN/HK/AR NL_SIDO_PKLC/PPLC



DO Delivery Order Global English NL_SIDO

NL_SIDO_V20


Local (Vietnamese)

Local (Chinese)

Local (Spanish)

NL_SIDO_KR

NL_SIDO_VN

NL_SIDO_HK

NL_SIDO_AR

Local (Malaysia)

English NL_SIDO_PKLC

NL_SIDO_PPLC

STDSTD

LOCALLOCAL

Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType


Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType




3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - AU

KFF Rel 3.1 (GDS 2.0) has single type of Delivery Order (Authorization Release):



DO Delivery Order (Authorization Release)

Global English NL_AUTHREL

NL_AUTHREL_V25

NL_AUTHREL_V26


Local (Vietnamese)

NL_AUTHREL_KR

NL_AUTHREL_VN

Local

(Sri Lanka)

English NL_AUTHREL_LK

STDSTD

LOCALLOCAL

Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType


Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType




3. Document ComparisonAs-Is Forms in KFF Rel 3.2 (GDS 3.0) - AU

KFF Rel 3.1 (GDS 2.0) will retain the latest version of Delivery Order (Authorization Release): :

Authorization Release NL_AUTHREL_V26 NL_AUTHREL_KR/VN/LK



DO Delivery Order (Authorization Release)

Global English NL_AUTHREL

NL_AUTHREL_V25

NL_AUTHREL_V26


Local (Vietnamese)

NL_AUTHREL_KR

NL_AUTHREL_VN

Local

(Sri Lanka)

English NL_AUTHREL_LK

STDSTD

LOCALLOCAL

Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType


Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType




3. Document ComparisonAs-Is & To-Be Forms - DVP

(GDS 2.0) Export Operational DocumentD


DVP Devanning Plan Global English NL_SIDEVANNINGPLAN

KFF Rel 3.1 (GDS 2.0) has single type as Devanning Plan.

KFF Rel 3.2 (GDS 3.0) will keep only the latest version as Devanning Plan.

NL_SIDEVANNINGPLAN

STDSTD

Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType


Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType




3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - SIWO



SIWO SI Work Order Global English NL_SIFCL, NL_SILCL

NL_SIFCL_v23, NL_SILCL_v23


Global Multiple Language NL_SIFCL_ML

NL_SILCL_ML

Local Local (Korean) NL_SIFCL_KR

NL_SILCL_KR

KFF Rel 3.1 (GDS 2.0) has single type as SI Work Order

STDSTD

LOCALLOCAL

S-STDS-STD

Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType


Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType




3. Document Comparison To-Be Forms in KFF Rel 3.2 (GDS 3.0) - SIWO

KFF Rel 3.2 (GDS 3.0) will keep only the latest version as SI Work Order: SE Work Order :


NL_SIFCL_ML, NL_SILCL_ML

NL_SIFCL_KR/CN/BR, NL_SILCL_KR/CN/BR

Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType


Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType




SIWO SI Work Order Global English NL_SIFCL, NL_SILCL




Global Multiple Language NL_SIFCL_ML

NL_SILCL_ML


Local (Chinese)

Local (Portuguese)

NL_SIFCL_KR, NL_SILCL_KR

NL_SIFCL_CN, NL_SILCL_CN

NL_SIFCL_BR, NL_SILCL_BR

STDSTD

LOCALLOCAL

S-STDS-STD



3. Document ComparisonAs-Is Forms in KFF Rel 3.1 (GDS 2.0) - SIMF




Global English NL_SI_MANIFEST

NL_SI_MANIFEST_v23

NL_SI_MANIFEST_v26

NL_SI_MANIFEST_v29

Global Multiple Language NL_SI_MANIFEST_ML

KFF Rel 3.1 (GDS 2.0) has single type as Cargo Manifest

STDSTD

Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType


Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType


S-STDS-STD



3. Document Comparison To-Be Forms in KFF Rel 3.2 (GDS 3.0) - SIMF

KFF Rel 3.2 (GDS 3.0) will have only the latest version as Cargo Manifest: Cargo Manifest :

NL_SI_MANIFEST_v29

NL_SI_MANIFEST_ML

NL_SI_MANIFEST_CN/CL

Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType


Cargo ManifestSIMF

Work OrderWO

Devanning PlanDVP


Deliver OrderDO

Arrival NoticeAN

Document TitleType





Global English NL_SI_MANIFEST

NL_SI_MANIFEST_v23

NL_SI_MANIFEST_v26

NL_SI_MANIFEST_v29

Global Multiple Language NL_SI_MANIFEST_ML

Local Local (Chinese)

Local (Spanish)

NL_SI_MANIFEST_CN

NL_SI_MANIFEST_CL

STDSTD

S-STDS-STD

LOCALLOCAL


APENDIX

Form Comparison among versions

Document Form List per country

WIP


3) Calculate and Refresh Button


3) Calculate and Refresh button – Summery

There is no functionality enhancement as compared with Rel 3.1 before the

Rate Management integration with downstream. This session is to introduce the

current system functionality.

Calculate and Refresh button system functionality will be changed based on RM

downstream function which will be released later this year.


Introduction

‘Calculate and ‘Refresh’ button are located in Revenue Tab of SE Booking, SE BL and SI BL.

Usage of ‘Calculate’ buttons are: 1) generate OFT revenue

charge line based on Actual Rate in Job

2) Refresh of ALL charges based on changes in Job.

Usage of ‘Refresh’ buttons is: 1) Refresh of selected

charge line based on changes in Job.


How to input OFT without using ‘Calculate’ button

Without using ‘Calculate’ Button, users need to input Ocean Freight Charge first by adding a new charge line with Charge Code ‘OFT – OCEAN FREIGHT’ under Revenue Tab manually.

All the data will be populated based on the data in Job. - For FCL shipments, Rate,

Quantity and UOM are came from Container session under Item tab

- For LCL shipments, data are came from Quantity Information session under Item Tab.

FCL

LCL


Usage 1 of Calculate Button: Calculation of OFT

Input Container Type, Quantity and Actual Rate in Item Tab.

All the information will be brought over to Revenue Tab

In this example, there are 2 different types of Container in this shipment with different Rates.

Example of FCL shipment


Usage 1 of Calculate Button: Calculation of OFT

After clicking ‘Calculate’ button, system will generate the OFT revenue charge line in Revenue tab automatically.

Since there are 2 different container types in this shipment, 2 revenue charge lines are generated.

This function works the same for LCL and BLUK shipments.


Synchronization of data between Item Tab and Revenue Tab Without clicking ‘Calculate’

button, limited data elements will be synchronized in Revenue tab according to the change in Job for Charge Code ‘OFT’: - FCL Shipment

‘UOM’, ‘Quantity’, ‘Rate’ will be synchronized according to the change in Container session (CTN Type, Qty and Actual Rate) under Item Tab

- LCL Shipment Only ‘Actual Rate’ will be

synchronized in Revenue Tab ‘Rate’ field’ automatically if there is any change under Quantity Information session of Item Tab.

Users need to update ‘Quantity’ manually in Revenue Tab or user ‘Calculate’ / ‘Refresh’ Button

For the rest of Charge Code, is no synchronization. Users need to update the data in Revenue Tab manually.

FCL LCL


Synchronization of data between Item Tab and Revenue Tab

Any change of below data elements in the job would NOT be synchronized in Revenue Tab automatically:1) Bill To Party (from either

‘Shipper’ for prepaid charges or ‘Overseas Agent’ for Collect shipments)

2) PC Indicator (from Freight and Other Prepaid / Collect checkbox)

3) Ex. Rate for OFT (from OFT Curr/Ex. Rate)

Users need to update the data in Revenue Tab manually OR use ‘Calculate’ / ‘Refresh’ button

1

1

2

2

3

3

1


Usage 2 of Calculate Button: Refresh data as change in Job

After clicking ‘Calculate’ button, all the data elements that highlight in the screenshot will be refreshed if the data in the Job is changed. It applies for every charge line in the revenue tab.

‘Refresh’ button has the same functionality as ‘Calculate’ button except it applies to the selected charge line only. - In this example, system

refreshes the data in the 1st line only.

System only refresh Ex. Rate for 2) OFT Charge3) Charges which currency is

the same as OFT Currency


Usage 2 of Calculate Button: Refresh data as change in Job

When refreshing the data, system overwrites value of the below data elements to the original default value:1) Charge Name (from

Charge Code Master)

2) Bill To Party (from either ‘Shipper’ for prepaid charges or ‘Overseas Agent’ for Collect shipments)

3) UOM (based on the setting in Charge Code Master)

4) PC Indictor (from Freight and Other Prepaid / Collect checkbox

Attention!

1 2

3 4


4) Global SOP – Destination Specific Rules


4) Global SOP – Destination Specific Rule - Summary

When handling shipment to below destinations, Origin office should be aware of belowrules:

Destination Related Area Rule Description

Bangladesh Revenue Charge Payment related

ALL import charges should be paid by Freight Payer

China MBL Prep 1) MBL should show Actual Consignee as Consignee for scrap cargo

2) MBL should show Actual Consignee as Consignee for shipments to Fuzhou or Xiamen and NLCN Fuzhou office or Xiamen office as Notify Party

Indonesia HBL and MBL Prep 1) Description of goods on the packing list should be the same as that on HBL and MBL.

2) MBL should show Actual Consignee as Consignee and NL-ID as Notify Party



Country Related Area Rule Description

Taiwan HBL Prep Exact Description has to be shown on HBL (Marks

& Nos) for LCL shipments. ‘No Mark’ is not

accepted.

Thailand HBL Prep UN Number has to be shown on HBL for

Dangerous Goods Cargo.

Russia 1), 2) & 5) MBL Prep

3) Trade Term

4) HBL Prep

1) HS code, Weight/Measurement and Case Mark should be the same on MBL and Commercial Invoice and Packing List.

2) ‘To Order of NYK Logistics Rus’ should be shown on MBL

3) Inco Term as ‘DDP’ is not allowed

4) Obtain Shipper’s Authorization on amendment of Consignee Name before Customs Clearance at Russia

5) No cost information should be shown on MBL



Country Related Area Rule Description

Argentina HBL Prepare 1) Consignee and Notify Party full style (with CUIT) should be shown on HBL

2) Original HBL should be issued

Brazil HBL & MBL Prep 1) HBL signature should be original by hand written

2) Original HBL should be issued

3) ‘Freight as arranged’ MBL and HBL are NOT allowed

4) HBL Amendment should be done at least 48 hours prior to ETA at POD

5) Company CNPJ# and Cargo NCM# are mandatory on HBL and MBL.

Chile HBL Prep Original HBL should be issued


Bangladesh Rule 1: Payee for Import ChargesRule #: Rule Title BD-R1: Payee for Import Charges

Process ID – Activity/Task 3.1.1.6 – Checking Quotation/Selling Rate

System Module & Function N/A

Training Material N/A

Rule Description According to Bangladesh regulatory requirement, ALL import charges, including DTHC (Destination Terminal Handling Charge), should be paid by Freight Payer.

If Freight payment term is "PREPAID" for a particular shipment, all freight & charges of both ends (origin & destination) should be paid by Shipper (or third party) at Origin.

If Freight payment term is "COLLECT" for a particular shipment, all freight & charges of both ends (origin & destination) should be paid by Consignee at Destination.

User should ensure all import charges are captured during booking process for Bangladesh shipments.

Consequence of Violation Shipment will not be released until correction is made according to Freight payment term

Related KPI N/A

Monitory Party Export Manager (at Origin Office)


China Rule 1: Actual Consignee for Scrap Cargo

Rule #: Rule Title CN-R1: Actual Consignee for Scrap Cargo

Process ID – Process Title 4.3.3.1 – Capture Required information for MBL



Rule Description If the commodity name belongs to scrap cargo, Origin Office must ensure the MBL shows the actual consignee name as consignee instead of NVOCC name.

Consequence of Violation Customs will reject import customs clearance and user must amend MBL which may cause delays

Related KPI N/A

Monitory Party Export Operation Manager (at Origin Office)


China Rule 2: Actual Consignee for Fuzhou / Xiamen Shipments

Rule #: Rule Title CN-R2 Actual Consignee for Fuzhou/Xiamen Shipments




Rule Description

For all shipments destined for China: Fuzhou or Xiamen, Origin Office must ensure the

MBL shows:

- actual consignee name as consignee instead of NVOCC name

- notify party as:

Fuzhou: NYK Logistics (China) Co., Ltd. Fuzhou Branch Xiamen: NYK Logistics (China) Co., Ltd. Xiamen Branch

Consequence of Violation Customs clearance would be failed. MBL must be amended to show actual Consignee and correct Notify Party which causes amendment fee.

Related KPI N/A



Indonesia Rule 1: Matching Goods Description

Rule #: Rule Title ID-R1: Matching Goods Description

Process ID – Process Title 4.3.2.1 – Register/Update S/I Information4.3.3.1 – Capture required information for MBL



Rule Description User should ensure the description of goods on the packing list is the same as that on the HBL, and also on the MBL.In the case that there are over 5 item descriptions of goods on the packing list, a minimum of 5 items should be included on the HBL/MBL as per Indonesia custom regulation.

Consequence of Violation Fines/Penalties issued by Indonesian Customs, Claim from customer due to late delivery, Storage & Demurrage charge due to late delivery

Related KPI N/A

Monitory Party Export Operations Manager (at Origin Office)


Indonesia Rule 2: Actual Consignee on MBL

Rule #: Rule Title ID-R2: Actual Consignee on MBL




Rule Description For all shipments destined for Indonesia, Origin Office must ensure the MBL shows:

- actual consignee name as consignee instead of NVOCC name

- notify party as NVOCC name Consequence of Violation Customs will reject import customs clearance and user must amend MBL which may

cause delays

Related KPI N/A



Taiwan Rule 1: LCL Cargo Description

Rule #: Rule Title TW-R1: LCL Cargo Description

Process ID – Process Title 3.1.1.10 – Capture Booking Information



Rule Description For LCL shipment, should be indicated the exact description to specify the nature of commodity. “No mark” description is unacceptable.

Consequence of Violation Violation of this rule will result in rejection of declaration by custom

Related KPI N/A



Thailand Rule 1: Capture UN Number

Rule #: Rule Title TH-R1: Capture UN Number

Process ID – Process Title 3.1.1.10 – Capture Booking Information



Rule Description In the case of Dangerous Goods cargo, Export user must capture the UN Number in the HBL.

Consequence of Violation May incur penalty from carrier

Related KPI N/A



Russia Rule 1: MBL Follow information on Commercial Invoice and Packing List

Rule #: Rule Title RU-R1: MBL Follow information on Commercial Invoice and Packing List

Process ID – Process Title 4.3.2.1 – Register/Update S/I Information4.3.3.1 – Capture required information for MBL



Rule Description 1) HS codes must be shown in Commercial Invoice and Packing List

2) Weight and measurement on HBL must be correct and the same in MBL, Commercial

Invoice and Packing list

3) Case mark on HBL must be same as in MBL, Commercial Invoice and Packing List

Consequence of Violation May incur amendment at destination

Related KPI N/A



Russia Rule 2: Inco Terms as ‘DDP’ only is NOT allowed

Rule #: Rule Title RU-R2: Inco terms as ‘DDP’ only is NOT allowed

Process ID – Process Title N/A



Rule Description According to Russian Law, DDP term only is not accepted. The most preferred is DDU, CTP and CIP.

Consequence of Violation May incur penalty from Russia Customs

Related KPI N/A



Russia Rule 3: ‘To Order’ MBL

Rule #: Rule Title RU-R3: ‘To Order’ MBL

Process ID – Process Title 4.3.3 – MBL Arrangement



Rule Description ‘To Order’ MBL should be issued for Russia shipments. On MBL, consignee should be shown as:

TO ORDER OF NYK Logistics Rus, 4th Lesony pereulok, 13. Office building VIKA, 6th floor, Moscow, RUSSIA

Consequence of Violation Cannot reserve the right to hold the cargo until collect money from actual consignee securely.

Related KPI N/A



Russia Rule 4: Obtain Shipper’s Authorization for Amendment on Consignee

Rule #: Rule Title RU-R4: Obtain Shipper’s Authorization for Amendment on Consignee

Process ID – Process Title 3.1.1 – Booking Enquiry Capturing



Rule Description Origin office should confirm shipper’s authorization on amendment of Consignee name as it is required before Customs Clearance at Russia.

Consequence of Violation Amendment cannot be done without authorizationDelay of authorization will incur additional demurrage and detention at destination side.

Related KPI N/A



Russia Rule 5: Special attention for MBL and HBL preparation

Rule #: Rule Title RU-R5: Special attention for MBL and HBL preparation

Process ID – Process Title 4.3.1 – SI Confirmation4.3.2 - HBL Preparation 4.3.3 - MBL Arrangement



Rule Description) MBL must have the same shipment information as in HBL, Commercial Invoice and

Packing List.

) No price or cost information is allowed on MBL. While selling rate is allowed on HBL

) Request to confirm MBL and HBL draft with NL-Russia before shipment.

Consequence of Violation Amendment cannot be done without authorizationDelay of authorization will incur additional demurrage and detention at destination side.

Related KPI N/A



Argentina Rule 1: Showing Consignee and Notify Party in full style on HBL

Rule #: Rule Title AR-R1: Showing Consignee and Notify Party in full style on HBL




Rule Description Consignee Company name, Address, Phone/Fax number, CUIT(Argentine Tax ID number); Notify's full style: Company name, Address,Phone/Fax number, CUIT (Argentine Tax ID number); * Cargo HS Code -minimum the first 6 (six) digits. In case of several goods type, the one with highest value must be declared.

Consequence of Violation Violation of this rule will result in rejection of declaration by custom or even penalty.

Related KPI N/A



Argentina Rule 2: HBL Release Type

Rule #: Rule Title AR-R2: HBL Release Type

Process ID – Process Title 4.3.1.2 - Validate SI information


Training Material 12. HBL Prep 2

Rule Description For shipment going to Argentina, Original HBL should be issued as this is necessary for Customs Clearance. Seawaybill or Surrender HBL at origin office or 3rd office is NOT allowed.

Consequence of Violation Delay of Customs Clearance process

Related KPI N/A



Brazil Rule 1: HBL Signature Requirement

Rule #: Rule Title BR-R1: HBL Signature Requirement

Process ID – Process Title 4.3.5.8 – Print out HBL and Sign



Rule Description For shipment going to Brazil, HBL Signature should be original by hand written. Signature as chop or electronic signature is NOT allowed.

Consequence of Violation Violation of this rule will result in rejection of declaration by custom or even penalty.

Related KPI N/A



Brazil Rule 2: HBL Release Type

Rule #: Rule Title BR-R2: HBL Release Type




Rule Description For shipment going to Brazil, Original HBL should be issued as this is necessary for Customs Clearance. Seawaybill or Surrender HBL at origin office or 3rd office is NOT allowed.


Related KPI N/A



Brazil Rule 3: ‘Freight as arranged’ MBL and HBL is NOT allowed

Rule #: Rule Title BR-R3: ‘Freight as arranged’ MBL and HBL is NOT allowed

Process ID – Process Title 4.3.1.2 - Validate SI information4.3.3.4 – Validate Draft MBL Info



Rule Description MBL and HBL charges are required to be manifested in Brazil Customs system. Charges should be shown on MBL and HBL but no simply 'freight as arranged' no matter freight is prepaid at origin or collected at Brazil.

Consequence of Violation Violation of this rule will result in penalty from Brazil Customs as USD2,500/BL

Related KPI N/A



Brazil Rule 4: HBL Amendment 48 hours prior to ETA at Port of Discharge

Rule #: Rule Title BR-R4: HBL Amendment 48 hours prior to ETA at Port of Discharge




Rule Description HBL amendment must be done before registering manifest data in Brazil Customs system which is 48 hours prior to ETD at Port of Discharge


Related KPI N/A



Brazil Rule 5: Company CNPJ# and cargo NCM# on HBL and MBL

Rule #: Rule Title BR-R5: Company CNPJ# and cargo NCM# on HBL and MBL




Rule Description Company CNPJ# (Company Registration Number in Brazil) is mandatory to state on Consignee and Notify Party on HBL and MBL. Cargo NCM# (equal to HS#) are also mandatory to show in Cargo Description on HBL and MBL.


Related KPI N/A



Chile Rule 1: HBL Release Type

Rule #: Rule Title CL-R1: HBL Release Type




Rule Description For shipment going to Chile, Original HBL should be issued as this is necessary for Customs Clearance. Seawaybill or Surrender HBL at origin office or 3rd office is NOT allowed.


Related KPI N/A



5) Configuration Change


5) Configuration Change - Summary

1) Remove Mandatory check on ‘Booking Weight’ for FCL

2) Local Vessel Voyage UI Change

3) eDoc upload for SIDO

4) Mandatory field for Direct Shipment

5) Remove logic between Incoterms and Freight Terms

6) Add Move Type ‘CY/CFS’ for LCL shipment

7) ‘Lot Number’ as mandatory field for Sub-House Job

8) Configure ‘Consol FCL By’ value under Sub-House Job


1) Remove mandatory check on Booking Weight for FCL

Before the configuration change, ‘Booking Weight’ is mandatory if Load Term is either ‘FCL’, ‘LCL’ or ‘Bulk’

After the change, ‘Booking Weight’ is mandatory only if Load Term is either ‘LCL’ or ‘Bulk.

SE Booking > Cargo Tab


1) Remove mandatory check on Booking Weight for FCL

Booking Pcs Booking Weight Booking Volume

FCL

LCL

BLUK

Load Term

Field

Summary of Mandatory check between Load Term and Booking Details in SE Booking:

= Mandatory

= Not Mandatory


2) Local VV UI Change

Disable particular field in SE & SI VV

1. Lane, Call Sign, RegCountry & Lioyds Reg No. was disable because we don’t expect user change the value from VV screen

2. Handling Party was disable because no usage/linkage with job

3. On Board Date was disable because we don’t expect user update it in VV

4. Ref No.2 was disable because Ref No.1 is good enough for VV usage


3) eDoc upload for SIDO

Upload is successful indication for SIDO

1. Enable “Upload is successful” pop up box when printing SIDO

2. SI DO can be print out without fill in DO Release Date


4) System Mandatory field when Shipment Type = D (Direct)

Below are the fields which have to be made mandatory in SE BOOKING and SE BL as well as SI BL:

Field Module Tab When is mandatory? Remarks

Customer SE/SI Related Party Upon save

Controlling Agent

SE/SI Related Party Upon save Future report purpose

Biz Scope SE/SI BL Information Upon save

Job Date SE/SI BL Information Upon save

Freight/Other SE/SI Item Upon save Can not set conditional setting against with DWE shipment

No of BL/Copy SE BL Transport Upon save Can not set conditional setting against with DWE shipment

Operator SE/SI Others Upon save

Since the scope of direct job usage is broad, the mandatory fields are intended not covering some key elements like vessel voyage, package information. Although they are not mandatory, users should key in the relevant information being relevant and being informative.


5) Remove logic between Incoterms and freight terms

Module :

SE BK -> Terms tab

SE BL -> Item Tab

SI BL -> Item Tab

Remove Logic:

Connection between Incoterms & Freight Terms

Before that the payment term checkbox (prepaid/Collect) of “Freight” and “Others” would be automatically ticked based on the different Inco Term selected.

Now the logic between Inco Term & Payment terms had been removed, user required to manually define the payment term in prepaid or collect.


Module :

SE BK -> Terms tab

SE BL -> Other Tab

Configuration Change:

Add Move type “CY/CFS” for the load term = LCL for both house and master job,

Latest Move Type options for LCL shipments.

- CFS/CFS

- CFS/CY

- CY/CFS

- CFS/DOOR

- DOOR/CFS

- DOOR/DOOR

This applied to both Master and House job

6) Add Move type “CY/CFS” for LCL shipment


Module :

SE BL -> BL Information

Job type: Sub-house (B)

New Mandatory field:

Lot number ( This field would be same as the House Booking number)

If system missed this lot number at SE BL module, system cannot link the data between the B job at sub-house level and H job at house level accordingly.

7) Set “Lot Number” as mandatory field for sub-house job


8) Configure the “Consol FCL By” value under sub-house job

Module :

SE BK -> SE Booking Tab

SE BL -> BL Information Tab

Job type: Sub-house (B)

Configuration:

Configure the “Consol FCL By” value for sub-house job:

This allow user to select the “Buyer Consol” under “Consol FCL By” for FCR cases, in order to identify the job between own consol and buyer consol (for FCR) under the same load term .


6) Job Structure per Scenario


6) Job Structure Usage in GDS

Job Structure is important in GDS in the sense of 1) Lifting Report – System extract lifting data based on defined Job structure

2) Document – the printing logic is affected by Job structure

3) System Logic – System logic, like default value is also different based on Job Structure

Therefore, local companies are highly recommended to follow the defined Job

Structure by GDS Core Team.


Job Structure Usage in GDS – DWE

NO Ship. Type

Description of Shipment Business ScopeHBL FCR

(1) FCL Shipment DWEM

H (s)

MBL

(2) LCL Shipment (Co-load out case) DWEM

H

(3) Own Consolidation Shipment DWEM

H (s)

(4) Buyer’s Consolidation ShipmentAt

B Level

DWE

M

H

B (s)

(5) Direct Buyer Consolidation Shipment

DWE HBL is NOT issued but only FCR At H Level

DirectM

H (s)

(6)

Direct Shipment DWE HBL is NOT Issued Reselling Model (OFT contract between Customer and NYK Logistics)

DirectD


Job Structure Usage in GDS – Non DWE

NO Ship. Type

Description of Shipment Business ScopeHBL FCRMBL

(1) Merchant Haulage Non DWED

(2) Booking Agency

Commission Module (OFT contract is between Customer and Carrier)

Non DWED

(3) Forwarding Agency

3rd Party HBL (NOT DWE) is issuedNon DWE

M

H (s)

(4) Customs Clearance Arrangement Non DWED

(5) Documentation Service Non DWED


7) RLJ Definition Change


7) RLJ Definition Change – Change Summery

1) Definition Change

2) Functionality Changea) Post Pre-alert

b) Default of Shipper and Consignee in SE and SI

c) Default Bill to Party in Revenue Tab based on b)

Notes: The change will be applied in Production Environment in 25th Feb 2011.


New Definition of RLJ

As-Is To-Be

R – Routing Ocean Freight is paid by Consignee or party other than Shipper or Consignee

Business initiated by Destination office

L – Local Ocean Freight is paid by Shipper

Business initiated by Origin office

J - Joint Not Use in Rel 3.1 Business initiated by 3rd office, RHQ and GHQ

Definition RLJ fieldAs-Is: an indicator of WHO pay Ocean FreightTo-Be: an indicator of WHO get the business

Scenario for when R, L and J should be chosen.


New Definition & Usage of RLJ

Reason for redefining RLJ definition & usage

Based on the fact that the current RLJ definition and system behavior confused users (in Rel 3.0 - 3.1), the RLJ definition was reviewed to be refined in the following two aspects:

Consistency of RLJ definition

RLJ definition should be consistent regardless the role of offices (SE – Export office or SI- Import office).

RLJ should be utilized to define the nature of the Job as easy operational indicator and reporting indicator.

RLJ value usage for operation efficiency

RLJ definition should help users to accurately register the data in Job by defaulting some of the predefined value into the related data fields.


Functionality Change – 1) Post Pre- alert

SE SI

As-Is RLJ Field = L RLJ Field = R (swap by system automatically)

Customer = [Real Consignee] in SE Job (System Default)

To-Be RLJ Field = L RLJ Field = L (No Change)

Customer = copied [Customer] in SE Job

Case 1- Business initiated by Origin office

SE SI

As-Is RLJ Field = R RLJ Field = L (swap by system automatically)


To-Be RLJ Field = R RLJ Field = R (No Change)


Case 2- Business initiated by Destination Office


Functionality Change – 1) Post Pre- alert

Case 3 - Business initiated by 3rd office, RHQ and GHQ

SE SI

As-Is RLJ Field = L RLJ Field = R (swap by system automatically)


To-Be RLJ Field = J RLJ Field = J (No Change)



SI-job default value [RLJ] & [Customer] by Posting/Confirm pre-alert function

To-be system behavior


Functionality Change – 2) Default of Shipper and Consignee in SE

Definition of Customer is still WHO pay Ocean Freight. ‘Customer’ will be default as Shipper or Consignee depends on the value in RLJ field.

Shipper Consignee Statistics Party

As-Is Copied from [Customer] Manual Input Copied from [Customer]

To-Be Copied from [Customer] Manual Input Copied from [Customer]

Case 1- Business initiated by Origin office (RLJ = L)


As-Is Manual Input Copied from [Customer] Copied from [Customer]

To-Be Manual Input Copied from [Customer] Copied from [Customer]

Case 2- Business initiated by Destination office (RLJ = R)No Change


Functionality Change – 2) Default of Shipper and Consignee in SE

Case 3- Business initiated by 3rd office, RHQ and GHQ (RLJ = J)


As-Is N/A N/A N/A

To-Be Manual Input Manual Input Copied from [Customer]


Functionality Change – 2) Default of Shipper and Consignee in SI


As-Is Manual Input Copied from [Customer] Copied from [Customer]

To-Be Copied from [Customer] Manual Input Copied from [Customer]

Case 1- Business initiated by Origin office (RLJ = L)


As-Is Manual Input Manual Input Copied from [Customer]

To-Be Manual Input Copied from [Customer] Copied from [Customer]

Case 2- Business initiated by Destination office (RLJ = R)

If the SI Job is created by Confirm Pre-alert, [Shipper], [Consignee], [Statistic Party] are copied from SE Job without any change. However, if SI Job is created by manual input, the below system logic will be applied:


Functionality Change – 2) Default of Shipper and Consignee in SI

Case 3- Business initiated by 3rd office, RHQ and GHQ (RLJ = J)


As-Is N/A N/A N/A

To-Be Manual Input Manual Input Copied from [Customer]


Propagate function [Shipper], [Consignee] and [Statistic party] from [Customer] in SI-job

As-is System behavior



To-be System behavior


As-is system behavior of RLJ

As-is Definition L: “L” stands for “Local” business. When this is selected, the business is supposed to be initiated by

the own office of job creation.

R: “R” stands for “Routing” business. When this is selected ,the business is supposed to be initiated the other office from the job creation

J: No usage

As-is Functionality Default value of [RLJ], [Customer], [Shipper], [Consignee], [Statistic party] and [Bill to party] are

controlled by SE-job, Pre-alert function and SI-job function as follows.

SE-job SI-job created by Pre-alert SI-job created by "add" function[RLJ] manual entry Swapping from SE-job manual entry

(f.i. If SE is "L", SI will be "R".)[Customer] manual entry no matter [RLJ] value, manual entry

default value is as per [real consignee] of SE-job.

[Shipper] copied from [Customer] if [RLJ] is "L" copied from SE-job.[Consignee] copied from [Customer] if [RLJ] is "R" copied from SE-job. copied from [Customer] if [RLJ] is "L"[Statistic party] copied from [Customer] copied from SE-job. copied from [Customer] if [RLJ] is "L"[Bill to party] retrieve from [Customer] retrieve from [Customer] retrieve from [Customer]

(A)

(A)

(B)(B)(B)(C)(C)


Functionality Change – 3) Default Bill to Party in Revenue Tab

SE Job SI Job (Confirm Pre-Alert) SI Job (Manual Input)

As-Is Copied from [Customer] Copied from [Customer] Copied from [Customer]

To-Be Copied from [Customer] Copied from [Real Consignee] Copied from [Real Consignee]

No matter what is the value in RLJ Field, Default Bill to Party in Revenue Tab is as below:


Default value of [Bill to party] in SI-job

As-is System behavior


Default value of [Bill to party] in SI-job



To-be system behavior of RLJ

To-be Definition L: “L” means that the shipment is initiated “Origin office”

R: “R” means that the shipment is initiated “Destination office”

J: “J” means that the shipment is initiated other than Origin and Destination office

To-be Functionality Default value of [RLJ], [Customer], [Shipper], [Consignee], [Statistic party] and [Bill to party] would

be controlled by SE-job, Pre-alert function and SI-job function as follows.

SE-job SI-job created by Pre-alert SI-job created by "add" function[RLJ] manual entry Copied from SE-job manual entry

(f.i. If SE is "L", SI will be "L".)[Customer] manual entry default value is as per manual entry

[Customer] of SE-job.[Shipper] copied from [Customer] if [RLJ] is "L" copied from SE-job. copied from [Customer]

if [RLJ] is "L"[Consignee] copied from [Customer] if [RLJ] is "R" copied from SE-job. copied from [Customer]

if [RLJ] is "R"[Statistic party] copied from [Customer] copied from SE-job. copied from [Customer]

[Bill to party] retrieve from [Customer] retrieve from [Real retrieve from [RealConsignee] Consignee]

(A)

(A)

(B)

(B)

(B)

(C)(C)

(Gray area is AS-IS)

(2.21) kff rel3.2 upgrade_training_material_bpi_v.1.4

Technology

value of bl date rel3

sailing date rel3

hbl copyright nyk logistics

document variation

document form kff

document form comparison

new document session1

new document session2