EDIFACTORY

UNH M(1) : 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 element 0065 CONDRO 0052 D 0054 05A 0051 UN

BGM M(1) : Beginning of message

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

DTM M(5) : 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).

AUT C(2) : Authentication result

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

AGR C(2) : 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.

FTX C(10) : 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.

SG1 M(5) : 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.

RFF M(1) : 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.

DOC C(1) : Document/message details

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

DTM C(1) : Date/time/period

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

FTX C(5) : 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.

SG2 M(999) : 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.

NAD M(1) : 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.

LOC C(99) : Place/location identification

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

FTX C(10) : Free text

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

SG3 C(10) : 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.

RFF M(1) : 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 which will specify the unique reference number by which, in future, the following computer environment details for this party can be identified.

CED C(10) : 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.

DTM C(1) : Date/time/period

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

SG4 C(10) : CTA-COM-LOC

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

CTA M(1) : Contact information

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

COM C(5) : Communication contact

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

LOC C(1) : 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.

SG5 C(999) : 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.

DOC M(1) : Document/message details

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

INP C(99) : Parties and instruction

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

RFF C(1) : Reference

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

MEA C(1) : Measurements

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

SG6 C(99) : 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.

EFI M(1) : External file link identification

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

CED C(10) : Computer environment details

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

DTM C(5) : Date/time/period

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

SG7 C(100000) : BII-GEI-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.

BII M(1) : Structure identification

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

GEI C(1) : Processing information

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.

DTM C(1) : Date/time/period

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

IMD C(1) : 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).

RFF C(5) : 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).

QTY C(1) : Quantity

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

SG8 C(1) : LOC-DIM-QTY-MEA

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

LOC M(1) : 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).

DIM C(5) : Dimensions

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

QTY C(5) : Quantity

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

MEA C(1) : Measurements

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

UNT M(1) : Message trailer

A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.