© 2018 ProgM

Nachricht CONDRO: D

BeschreibungDrawing organisation message


UNH0A 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 D A UNMandatory
BGM0A segment for unique identification of the Drawing organisation name, number and function.Mandatory
DTM0A 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).Mandatory
AUT0A segment used to authenticate the message by exchanging a password or some other form of identification agreed between the business partners.Optional
AGR0A 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.Optional
FTX0A 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.Optional
RFF1A 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.Mandatory
DOC1Document details for the reference quoted in the previous RFF segment.Optional
DTM1Date of a reference quoted in the previous RFF segment, e.g. project date or message/document date.Optional
FTX1This 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.Optional
NAD1A 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.Mandatory
LOC1A segment giving more specific location information of the party specified in the NAD segment e.g. internal site/building number.Optional
FTX1A segment giving more specific location information of the party specified in the NAD segment e.g. internal site/building number.Optional
RFF2In 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.Mandatory
CED2By 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.Optional
DTM2A segment specifying the date and/or time details related to the environment details.Optional
CTA2A segment to identify a person or department, and their function, to whom communications should be directed.Mandatory
COM2A segment to identify a communication type and number for the contact specified in the CTA segment.Optional
LOC2This 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.Optional
DOC1This segment will give the document details of the contractual document.Mandatory
INP1This segment conveys for each receiver instructions of what to do with the contractual document.Optional
RFF1A segment to indicate the unique reference number of the contractual document.Optional
MEA1This segment will give details about the scale used in the contractual document.Optional
EFI2This segment will identify each file, that is part of the contractual document, by quoting their name and a number.Mandatory
CED2The segment will give additional information about the file identified in the previous EFI segment, like for example, conversion details.Optional
DTM2This segment will convey the date/time details of the computer file identified in the previous EFI segment.Optional
BII1This segment will, through a structured index code, uniquely identify the set of information following this segment.Mandatory
GEI1This 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.Optional
DTM1Date and time details relevant to the set of information identified in the previous BII segment (e.g. list version date).Optional
IMD1This 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).Optional
RFF1This 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).Optional
QTY1This segment conveys the number of objects within the next higher level of a list.Optional
LOC2This 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).Mandatory
DIM2Dimensions (like unit of measurements) relevant to an engineering/CAD file can be quoted in this segment.Optional
QTY2A segment identifying the quantities of objects in lists or engineering/CAD files.Optional
MEA2For an engineering/CAD file, the scale used can be quoted in this segment.Optional
UNT0A 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.Mandatory