Directory   Messages   Segments   Composites   Data elements   Codes Meaning of the change indicators
  UN/EDIFACT  D.03A (Batch) Syntax version 3 Issue date 2003-06-23  
  Message type specification CONDRO
CONDRO 2 Drawing organisation message  

TBG6 Architecture, Engineering and Construction

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.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
The Drawing organisation 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.

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.

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


3.1 Standard terms and definitions
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.


4.1 Data segment clarification
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
  Generated by GEFEG.FX