Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D97B Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Means of transport and equipment position message

Version:D
Release:97B
Contr. Agency:UN
Revision:1
Date:97-07-25
SOURCE:Western European EDIFACT Board - MD2

CONTENTS
Means of transport and equipment position message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
  5. MESSAGE DEFINITION
    1. Data segment clarification
    2. Data segment index (alphabetical sequence)
    3. Message structure
      1. Segment table

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction


This message also occurs in the following versions of this standard:
D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B

0. INTRODUCTION

This specification provides the definition of the Means of transport and equipment position message (MEQPOS) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional Definition

A message containing the position of a means of transport (e.g. a vessel or truck) and/or equipment related to a means of transport.


1.2. Field of Application

The Means of transport and equipment position message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.


1.3. Principles

  • The message relates to one means of transport and/or equipment related to a means of transport.
  • The message contains the last reported position of the means of transport, e.g. at sea.
  • The message contains information on the conveyance of the means of transport, possibly including the number of people on board.

Business area: control of pollution by a means of transport (e.g. maritime pollution)

Sending function: truck's driver, vessel's master, authority (e.g. port, police), centralised database of authorities

Receiving function: authority (e.g. port), search and rescue organisation


2. REFERENCES

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.


3. TERMS AND DEFINITIONS


3.1. Standard terms and definitions

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.


4. MESSAGE DEFINITION


4.1. Data Segment Clarification

This section should be read in conjunction with the Segment Table which indicate mandatory, conditional and repeating requirements.

0010 UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Means of transport and equipment position message is MEQPOS.

Note: Means of transport and equipment position messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065MEQPOS
0052D
005497B
0051UN

0020 BGM, Beginning of message

A segment to indicate the beginning of a message and to transmit the identifying number.

0030 DTM, Date/time/period

A segment to provide the date and time of the message.

0040 QTY, Quantity

A segment to indicate a quantity, such as the number of passengers on board the means of transport for a certain conveyance.

0050 LOC, Place/location identification

A segment to specify the position of the means of transport, e.g. by giving longitude and latitude coordinates of the vessel at sea.

0060 Segment Group 1: RFF-DTM

A group of segments to specify a reference applying to the whole message.

0070 RFF, Reference

A segment to specify a reference, e.g. reference to previous message.

0080 DTM, Date/time/period

A segment to indicate a date and time related to the reference.

0090 Segment Group 2: TDT-LOC-DTM

A group of segments to indicate the details of the means of transport, and related locations and arrival dates and times.

0100 TDT, Details of transport

A segment to identify the means of transport (e.g. by Lloyd's Register number of a vessel, or by the license plate number of a truck).

0110 LOC, Place/location identification

A segment to indicate a location relating to the means of transport, such as: - place or port of departure - next place or port of call.

0120 DTM, Date/time/period

A segment to indicate the estimated date and time of arrival and departure.

0130 Segment Group 3: NAD-SG4

A group of segments to identify a party and related contacts.

0140 NAD, Name and address

A segment to identify a party's name, address and function.

0150 Segment Group 4: CTA-COM

A group of segments to identify a contact and its communications related to the party.

0160 CTA, Contact information

A segment to identify a person or department within the party.

0170 COM, Communication contact

A segment to identify a communication number of a person or department to whom communication should be directed.

0180 Segment Group 5: EQD-LOC-DTM

A group of segments to identify equipment related to the means of transport, and associated locations and dates and times.

0190 EQD, Equipment details

A segment to identify equipment, such as railcars.

0200 LOC, Place/location identification

A segment to specify the location of the equipment.

0210 DTM, Date/time/period

A segment to specify a date and time related to the equipment.

0220 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.


4.2. Data segment index (Alphabetical sequence by tag)

BGM Beginning of message
COM Communication contact
CTA Contact information
DTM Date/time/period
EQD Equipment details
LOC Place/location identification
NAD Name and address
QTY Quantity
RFF Reference
TDT Details of transport
UNH Message header
UNT Message trailer

4.3. Message structure


4.3.1. Segment table

├─UNH Message header ×1 (M)
├─BGM Beginning of message ×1 (M)
├─DTM Date/time/period ×9 (C)
├─QTY Quantity ×1 (C)
├─LOC Place/location identification ×1 (M)
├─Segment Group 1 ×9 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×9 (C)
├─Segment Group 2 ×1 (M)
├─TDT Details of transport ×1 (M)
├─LOC Place/location identification ×9 (C)
└─DTM Date/time/period ×9 (C)
├─Segment Group 3 ×9 (C)
├─NAD Name and address ×1 (M)
└─Segment Group 4 ×9 (C)
──├─CTA Contact information ×1 (M)
──└─COM Communication contact ×9 (C)
├─Segment Group 5 ×999 (C)
├─EQD Equipment details ×1 (M)
├─LOC Place/location identification ×9 (C)
└─DTM Date/time/period ×9 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D97B Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools EDIFACT to XML
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.