Frames | No Frames

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

Drawing organisation message

Version:D
Release:97A
Contr. Agency:UN
Revision:1
Date:96-12-13
SOURCE:Western European EDIFACT Board - MD5

CONTENTS
Drawing organisation 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:
D95A, D95B, D96A, D96B, 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 Drawing organisation message (CONDRO) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional Definition

The message CONDRO is intended to describe the general (project) organisation and structure, valid for a whole project or environment.

The whole process of exchanging engineering or CAD (Computer Aided Design) files between different parties within one project will be supported by EDIFACT messages. The message CONDRO is one of these messages.


1.2. Field of Application

This message type may be applied for both national and international trade. It is based on universal practice and is not dependent on the type of business or industry.

The following descriptions refer to the exchange of engineering/CAD files, but do not exclude any other type of "native" files, e.g. files originating from software packages and tools like word-processing, spreadsheet, DTP (Desk Top Publishing), graphics and so on.


1.3. Principles

CONDRO is the EDIFACT message to initiate the future exchange of engineering/CAD files, and does not consist of any engineering or graphical information. Its aim is to acquaint the participant of a project with the existing organisation, the used computer environment, the agreed conventions for structuring/naming the transferred data and in a second application to announce any changes to the above mentioned agreement. The exchange of all engineering and graphical information is administered by the EDIFACT message CONDRA (Drawing Administration). This information will be transferred by existing standard graphical exchange formats or native formats. Changes in the agreements and conventions should be minimised and be made at the beginning of a project or exchange process. Consequently it is not necessary to repeat the description of the files' organisation with every exchange of engineering/CAD files. This means not only a reduction of data volume at each exchange, but also avoiding the exchange of redundant data.


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 Drawing organisation message is CONDRO.

Note: Drawing organisation messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065CONDRO
0052D
005497A
0051UN

0020 BGM, Beginning of message

A segment for unique identification of the Drawing Organisation name, number and function.

0030 DTM, Date/time/period

A segment specifying the dates relevant to this document; e.g. the date the agreement of the drawing organisation information in this message has been defined or redefined (in case of changes).

0040 AUT, Authentication result

A segment used to authenticate the message by exchanging a password or some other form of identification agreed between the business partners.

0050 AGR, Agreement identification

A segment will be used to identify the "type of agreement of the organisation of engineering or CAD files" that apply to the information given by this message.

0060 FTX, Free text

A segment with free text information, in coded or clear form, used for any textual information. In computer to computer exchanges, such text will require the receiver to process this segment manually.

0070 Segment Group 1: RFF-DOC-DTM-FTX

A group of segments used for quoting references and their relevant dates applicable to the message. For the building industry the following recommendation is given: in the first occurrence of this segment group the project references, if relevant, should be given, in order to identify the project to which this message relates. In any later recurrence of this segment group, references to other messages (e.g. the original CONDRO when it is an update) or documents, relevant to this message, may be quoted.

0080 RFF, Reference

A segment for quoting the unique references which can be the project number for which this message is relevant, or, in the case of a reference to another message or document, that message or document's unique identifier.

0090 DOC, Document/message details

Document details for the reference quoted in the previous RFF segment.

0100 DTM, Date/time/period

Date of a reference quoted in the previous RFF segment, e.g. project date or message/document date.

0110 FTX, Free text

This segment can contain any textual information relevant to the reference quoted in the previous RFF segment, e.g. a small project or message/document description and/or other narrative, for additional information.

0120 Segment Group 2: NAD-LOC-FTX-SG3-SG4

A group of segments identifying all the relevant parties with specific information about them that other business partner should know.

0130 NAD, Name and address

A segment identifying name and address of a party, in coded or clear form, and its function relevant to the Drawing Organisation Message. This is to identify each partner involved in the future exchange of CAD files. It is recommended that where possible only the coded form of the party ID should be specified.

0140 LOC, Place/location identification

A segment giving more specific location information of the party specified in the NAD segment e.g. internal site/building number.

0150 FTX, Free text

A segment giving more specific location information of the party specified in the NAD segment e.g. internal site/building number.

0160 Segment Group 3: RFF-CED-DTM

This segment group has two functions:

Firstly, it can be used to quote specific references for each partner for internal use. Examples of references: a partner may require a internal project number or a DP number.

Secondly, the main function of this segment group, is to describe for each partner his internal computer environment, from the hardware platform and operating system to the software implemented. For each partner several environments may be described, as, particularly in large organisations, different environments can be in use simultaneously. Each environment will be identified through a unique reference number specific to that partner.

0170 RFF, Reference

In this segment specific internal references will be quoted, as and if required. When this segment group is used to describe the computer environment, this segment segment which will specify the unique reference number by which, in future, the following computer environment details for this party can be identified.

0180 CED, Computer environment details

By repeating this segment, it will describe, at each occurrence, one of the party's computer environments, identified in the previous RFF segment. The computer environment details will consist of, for example, hardware platform, operating system, software in use, converter etc.

0190 DTM, Date/time/period

A segment specifying the date and/or time details related to the environment details.

0200 Segment Group 4: CTA-COM-LOC

A group of segments giving contact details of the specific person or department within the party identified in the NAD segment.

0210 CTA, Contact information

A segment to identify a person or department, and their function, to whom communications should be directed.

0220 COM, Communication contact

A segment to identify a communication type and number for the contact specified in the CTA segment.

0230 LOC, Place/location identification

This segment specifies the location of the contact described in the previous CTA segment. In large organisations and construction projects it is possible that persons are not necessarily on the same internal site or construction site specified in the previous LOC segment in segment group 2. This segment also enables the specification of a more accurate internal site location.

0240 Segment Group 5: DOC-INP-RFF-MEA-SG6

In this segment group a "contractual document" can be described that is relevant to a certain project or project phase. A contractual document consists of one or more computer files which be quoted and linked by a file identification to the corresponding contractual document.

0250 DOC, Document/message details

This segment will give the document details of the contractual document.

0260 INP, Parties to instruction

This segment conveys for each receiver instructions of what to do with the contractual document.

0270 RFF, Reference

A segment to indicate the unique reference number of the contractual document.

0280 MEA, Measurements

This segment will give details about the scale used in the contractual document.

0290 Segment Group 6: EFI-CED-DTM

In this segment group files may be identified which will form part of the previously quoted contractual document. These computer files are external ones which will not necessarily be part of the exchange of the message.

0300 EFI, External file link identification

This segment will identify each file, that is part of the contractual document, by quoting their name and a number.

0310 CED, Computer environment details

The segment will give additional information about the file identified in the previous EFI segment, like for example, conversion details.

0320 DTM, Date/time/period

This segment will convey the date/time details of the computer file identified in the previous EFI segment.

0330 Segment Group 7: BII-GIS-DTM-IMD-RFF-QTY-SG8

This segment group can be used to record two types of information:

Firstly, information about all kinds of lists (like naming conventions, libraries used etc.) with their object descriptions and other details relevant to the exchanged engineering/CAD files.

Secondly, detailed descriptions about the structure of the engineering/CAD files.

In both cases, the information is organised hierarchically in several levels. The level will be identified first and will contain its own specific set of information, like technical data, references, etc. This segment group therefore varies depending on the type of information, the application of the segments and whether they will be used or not.

0340 BII, Structure identification

This segment will, through a structured index code, uniquely identify the set of information following this segment.

0350 GIS, General indicator

This segment is used to define the type of information (lists or engineering/CAD file structure) appearing in this segment group identified by the previous BII segment.

0360 DTM, Date/time/period

Date and time details relevant to the set of information identified in the previous BII segment (e.g. list version date).

0370 IMD, Item description

This segment records the details of the set of information identified in the previous BII segment (e.g. descriptions of the hierarchical levels or objects, part of the lists).

0380 RFF, Reference

This segment will give a reference to another set of information (e.g. engineering/CAD file structure referring to naming conventions given in a previously-supplied list).

0390 QTY, Quantity

This segment conveys the number of objects within the next higher level of a list.

0400 Segment Group 8: LOC-DIM-QTY-MEA

A group of segments to record the technical data of the set of information identified in the previous BII segment.

0410 LOC, Place/location identification

This segment will give detailed information of the position in a co-ordinate system in case the structure of an engineering/CAD file is described (e.g. the co-ordinate details of a layer group or a layer in a CAD file).

0420 DIM, Dimensions

Dimensions (like unit of measurements) relevant to an engineering/CAD file can be quoted in this segment.

0430 QTY, Quantity

A segment identifying the quantities of objects in lists or engineering/CAD files.

0440 MEA, Measurements

For an engineering/CAD file, the scale used can be quoted in this segment.

0450 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)

AGR Agreement identification
AUT Authentication result
BGM Beginning of message
BII Structure identification
CED Computer environment details
COM Communication contact
CTA Contact information
DIM Dimensions
DOC Document/message details
DTM Date/time/period
EFI External file link identification
FTX Free text
GIS General indicator
IMD Item description
INP Parties to instruction
LOC Place/location identification
MEA Measurements
NAD Name and address
QTY Quantity
RFF Reference
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 ×5 (M)
├─AUT Authentication result ×2 (C)
├─AGR Agreement identification ×2 (C)
├─FTX Free text ×10 (C)
├─Segment Group 1 ×5 (M)
├─RFF Reference ×1 (M)
├─DOC Document/message details ×1 (C)
├─DTM Date/time/period ×1 (C)
└─FTX Free text ×5 (C)
├─Segment Group 2 ×999 (M)
├─NAD Name and address ×1 (M)
├─LOC Place/location identification ×99 (C)
├─FTX Free text ×10 (C)
├─Segment Group 3 ×10 (C)
├─RFF Reference ×1 (M)
├─CED Computer environment details ×10 (C)
└─DTM Date/time/period ×1 (C)
└─Segment Group 4 ×10 (C)
──├─CTA Contact information ×1 (M)
──├─COM Communication contact ×5 (C)
──└─LOC Place/location identification ×1 (C)
├─Segment Group 5 ×999 (C)
├─DOC Document/message details ×1 (M)
├─INP Parties to instruction ×99 (C)
├─RFF Reference ×1 (C)
├─MEA Measurements ×1 (C)
└─Segment Group 6 ×99 (C)
──├─EFI External file link identification ×1 (M)
──├─CED Computer environment details ×10 (C)
──└─DTM Date/time/period ×5 (C)
├─Segment Group 7 ×10000 (C)
├─BII Structure identification ×1 (M)
├─GIS General indicator ×1 (C)
├─DTM Date/time/period ×1 (C)
├─IMD Item description ×1 (C)
├─RFF Reference ×5 (C)
├─QTY Quantity ×1 (C)
└─Segment Group 8 ×1 (C)
──├─LOC Place/location identification ×1 (M)
──├─DIM Dimensions ×5 (C)
──├─QTY Quantity ×5 (C)
──└─MEA Measurements ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D97A 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 Simplify Legacy Data Integration with Stylus Studio XML Enterprise Edition - Free Download!
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-2011 All Rights Reserved.