Professional Documents
Culture Documents
TPFREP D00B Terminal Performance Report Implementation Guide - Hapag-Llo...
TPFREP D00B Terminal Performance Report Implementation Guide - Hapag-Llo...
Version 3.0
1. INTRODUCTION
These instructions are valid for the "UN/EDIFACT UNITED NATIONS STANDARD
MESSAGE (UNSM) TERMINAL PERFORMANCE MESSAGE" (TPFREP), version 3.0, date
February 2002 as designed by the SMDG (User Group for Shipping Lines and Container
Terminals)
The instructions in this manual are valid for fully cellular container ships and feeder vessels.
This manual is intended for use by ship owners, tonnage centres, terminal operators, shipping lines, vessels,
etc.
This "User Manual" (or "Implementation Guide") Version 3.0 was developed by the SMDG User
Group for Shipping Lines and Container Terminals
The SMDG is a "Worldwide User Group" under the auspices of the Western European EDIFACT Board
(WEEB).
The SMDG claims full copyright to this manual and its contents, however, the manual may be copied and
used by anyone, without the consent of the SMDG.
Any remarks, comments or questions can be addressed to one of the following addresses:
SMDG Secretariat
c/o ECT
P.O.Box 7400
3000 HK Rotterdam
The Netherlands
Phone: 31-10-4916075
Fax: 31-10-4916865
Email: Secretariat@smdg.org
Website: www.smdg.org
or to:
Wolf Retzko
Hapag-Lloyd AG
Consulting e-business
Ballindamm 25
D-20095 Hamburg
Phone: +49 (0)40 3001-2967
wolf-dietrich.retzko@hlag.com
www.hlag.com
Or to any active member of the SMDG, see the member pages on our website for email addresses.
Any remarks or questions can also be placed on our forum: go to www.smdg.org and select “forum”.
The EDIFACT Message "TPFREP" will be used to transmit information relating to the operations carried
out by terminal operators such as the loading, discharging and re-handling of containers and hatch covers
etc.
The TPFREP message will be transmitted by a terminal operator to the ship operator, tonnage center or
shipping line.
Conventions
In this document a data element will be identified by the lowercase letter "e" followed by its element number
(example: e8053). A data element within a composite will be identified by the lowercase letter "c" followed
by the composite number followed by a full stop "." followed by the lowercase letter "e" followed by the
element number (example: c237.e8260).
Immediately below the segment tags and data element identification the usage of same will be mentioned as
follows:
'M' = mandatory The segment or data element is mandatory and must be given.
'R' = required The segment or data element is conditional but MUST be used anyway.
'D' = dependent The segment or data element is conditional and its use depends on some
condition. This condition must be clarified in the description.
'A' = recommended The segment or data element is conditional and its use is recommended.
'O' = optional The segment or data element is conditional and its use is optional at the
discretion of the sender.
'X' = not used The segment must not be used.
Next to the usage indicator the official format of the field will be given, i.e. a4 or an..15. The description may
further limit the format of the field, for example a field with a format an..17 may be limited to an12 by its
description.
If composites or data-elements are repeated within a segment, respectively a composite, the occurrences of the
composites or data-elements can be indicated by its sequence number within the segment or composite
between brackets, e.g. "(1)" being the first occurrence of the composite or data-element within the segment. If
its occurrence within the segment or composite is of no relevance then the sequence number will not be
mentioned. If the sequence numbers are mentioned, but not all of them (e.g. only 2 out of 5 occurrences are
described), then the remaining occurrences may NOT be used, unless agreed otherwise between partners.
Data elements within the segments that are not mentioned here will not be used, resp. should not contain
important information, since they will probably not be seen by the recipient, unless agreed otherwise.
SMDG recommends to use only data elements, qualifiers and codes described in this manual. If partners agree
to use additional data elements, qualifiers and codes, not described in this manual, then specific and detailed
agreement about those data elements, qualifiers and codes should be made!
Optional data elements may be omitted, unless specifically made compulsory by this manual (Indicator "R" =
required), or unless agreed otherwise between partners.
In no case neither mandatory segments (according to TPFREP) nor mandatory composites or data elements
according to the relevant Segment Directory may be omitted.
4. VERSIONS
Data elements, composites and segments of the UN/EDIFACT directory D00B are used in this manual.
Codes and qualifiers used, are according to UN/EDIFACT Directory D00B Code List.
In some occasions, however, the required code or qualifier could not be found in the code list. In such cases
special codes were assigned, to be maintained by the SMDG.
This version 3.0 is based upon the previous version 2.0 with some adjustments, corrections and
improvements, as proposed by the members of SMDG.
This is an updated version of UN/EDIFACT Message Implementation Guideline to the Terminal Performance Report
TPFREP version 2.0, issued by SMDG in 10/98. It is based on the UN/EDIFACT Draft Messages and Directories
Version D00B.
1M 1 2M 999
SMDG_TPF (D.00B)
1 FTX TDT EQD
C 999 M 1 M 1
3M 999
3 FTX
C 1
6
4
0 UNT
M 1
4C 999
SMDG_TPF (D.00B)
1 NAD
M 1
5C 999
2 EQD
M 1
6C 999
3 QTY
M 1
7
4 FTX
C 1
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
M 0050 TDT Details of Transport M 1
R 0060 LOC Place/Location Identification C 1
R 0070 DTM Date/Time/Period C 9
O 0080 RFF Reference C 9
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
M 0100 EQD Equipment Details M 1
R 0115 QTY Quantity C 99
0120 Segment Group 3: Date/Time/Period M 999
Example: EQD+GC+TMV'
or
EQD+GC+1'
EQD+GC+2'
Restowages:
One Moves ->
SHI Shift on Board (SOB), Total
TSH SOB, Under terminal instruction
CSH SOB, Under carrier instruction
OSH SOB, Others
DLD Discharge component of a restow
DLL Loading component of a restow
Hatch Covers:
HCV = Hatch Cover (one move)
Total Moves:
TMV = Total Moves
STF Note: Stacking Frames are used to secure a block of containers stowed in certain
non-cellular ships.
The number of moves involved in actually handling stacking frames is to be recorded against
STF.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
M 0130 DTM Date/Time/Period M 1
O 0140 FTX Free Text C 1
Example: DTM+LOT:0100:401'
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
M 0160 NAD Name and Address M 1
0170 Segment Group 5: Equipment Details C 999
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
M 0180 EQD Equipment Details M 1
0190 Segment Group 6: Quantity C 999
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat
M 0200 QTY Quantity M 1
O 0210 FTX Free Text C 1
Load
Restows
UNB+UNOA:1+SENDER:ZZ+RECIPIENT:ZZ+011126:0900+56'
UNH+258+TPFREP:D:00B:UN:SMDG30'
BGM+265+258+9'
DTM+137:200111261027:203'
TDT+20+8767+1++MIS:172:20+++1234233:146:11:SHIPNAME'
LOC+5+AUXXX+TERM1+4'
DTM+ATA:200111182200:203'
DTM+ATD:200111190600:203'
DTM+ARB:200111182144:203'
DTM+SAI:200111190610:203'
DTM+LON:200111182200:203'
DTM+LOF:200111190355:203'
RFF+VON:9767'
RFF+VM:CALLSIGN'
EQD+GC+P1'
QTY+CMV:90'
QTY+RES:8'
DTM+LOT:0010:401'
FTX+ZZZ+++DELAY BEFORE LABOUR ABOARD TIME'
DTM+LOT:0045:401'
FTX+ZZZ+++DELAYS AFTER LABOUR ASHORE TIME'
DTM+SPE:0030:401'
FTX+ZZZ+++BOOM UP/DOWN FOR PASSING SHIPS'
DTM+LOT:0015:401'
FTX+ZZZ+++LABOUR REST PERIOD'
DTM+MSC:0015:401'
FTX+ZZZ+++QUAY CRANE BREAKDOWN'
DTM+HLD:0010:401'
FTX+ZZZ+++CRANE HANDLING HATCH LIDS'
DTM+MSC:0015:401'
FTX+ZZZ+++ATTACHING/REMOVING SPREADERS'
DTM+MSC:0010:401'
FTX+ZZZ+++CAGE WORK'
EQD+GC+P1'
QTY+CMV:90'
QTY+RES:8'
DTM+CFL:200111182230:203'
DTM+CLL:200111190240:203'
DTM+LOT:0010:401'
FTX+ZZZ+++DELAY BEFORE LABOUR ABOARD TIME'
DTM+LOT:0045:401'
FTX+ZZZ+++DELAYS AFTER LABOUR ASHORE TIME'
DTM+SPE:0030:401'
FTX+ZZZ+++BOOM UP/DOWN FOR PASSING SHIPS'
DTM+LOT:0015:401'
FTX+ZZZ+++LABOUR REST PERIOD'
DTM+MSC:0015:401'
FTX+ZZZ+++QUAY CRANE BREAKDOWN'
DTM+HLD:0010:401'
FTX+ZZZ+++CRANE HANDLING HATCH LIDS'
SMDG_TPF (D.00B) 31 February 19, 2002
DTM+MSC:0015:401'
FTX+ZZZ+++ATTACHING/REMOVING SPREADERS'
DTM+MSC:0010:401'
FTX+ZZZ+++CAGE WORK'
DTM+SPE:0015:401'
FTX+ZZZ+++BOOM UP/DOWN FOR PASSING SHIPS'
DTM+LOT:0025:401'
FTX+ZZZ+++LABOUR REST PERIOD'
DTM+MSC:0025:401'
FTX+ZZZ+++QUAY CRANE BREAKDOWN'
DTM+HLD:0020:401'
FTX+ZZZ+++CRANE HANDLING HATCH LIDS'
DTM+MSC:0015:401'
FTX+ZZZ+++ATTACHING/REMOVING SPREADERS'
EQD+GC+P2'
QTY+HCV:4'
QTY+CMV:105'
DTM+CFL:200111182200:203'
DTM+CLL:200111190355:203'
DTM+LOT:0010:401'
FTX+ZZZ+++DELAY BEFORE LABOUR ABOARD TIME'
DTM+LOT:0045:401'
FTX+ZZZ+++DELAYS AFTER LABOUR ASHORE TIME'
DTM+SPE:0030:401'
FTX+ZZZ+++BOOM UP/DOWN FOR PASSING SHIPS'
DTM+LOT:0015:401'
FTX+ZZZ+++LABOUR REST PERIOD'
DTM+MSC:0015:401'
FTX+ZZZ+++QUAY CRANE BREAKDOWN'
DTM+HLD:0010:401'
FTX+ZZZ+++CRANE HANDLING HATCH LIDS'
DTM+MSC:0015:401'
FTX+ZZZ+++ATTACHING/REMOVING SPREADERS'
DTM+MSC:0010:401'
FTX+ZZZ+++CAGE WORK'
DTM+SPE:0020:401'
FTX+ZZZ+++BOOM UP/DOWN FOR PASSING SHIPS'
DTM+MSC:0020:401'
FTX+ZZZ+++DELAYS CAUSED BY SHIP OR AGENT'
DTM+LOT:0015:401'
FTX+ZZZ+++LABOUR REST PERIOD'
DTM+HLD:0010:401'
FTX+ZZZ+++CRANE HANDLING HATCH LIDS'
DTM+MSC:0010:401'
FTX+ZZZ+++CAGE WORK'
NAD+CF+HLL'
EQD+CN++20FT+++5'
QTY+LOD:1'
FTX+AID+++DEEP SEA'
NAD+CF+PON'
EQD+CN++20FT+++5'
QTY+DIS:31'
SMDG_TPF (D.00B) 32 February 19, 2002
QTY+RST:3'
QTY+LOD:64'
FTX+AID+++DEEP SEA'
EQD+CN++40FT+++5'
QTY+DIS:31'
QTY+LOD:9'
FTX+AID+++DEEP SEA'
NAD+CF+CSA'
EQD+CN++20FT+++4'
QTY+LOD:4'
FTX+AID+++DEEP SEA'
EQD+CN++40FT+++4'
QTY+RST:1'
QTY+LOD:26'
FTX+AID+++DEEP SEA'
EQD+CN++20FT+++5'
QTY+DIS:10'
QTY+LOD:7'
FTX+AID+++DEEP SEA'
QTY+LOD:3'
FTX+AID+++SHORT SEA'
EQD+CN++40FT+++5'
QTY+DIS:8'
QTY+LOD:1'
FTX+AID+++DEEP SEA'
UNT+95+258'
UNZ+1+56'