© 2018 ProgM

Nachricht CONDRA: D

NameCONDRA
VersionD
Release18A
BeschreibungDrawing administration message

Elemente

SegmentEbeneBeschreibungOpt/Mand.
UNH0A service segment starting and uniquely identifying a message. The message type code for the Drawing administration message is CONDRA. Note: Drawing administration messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 CONDRA D A UNMandatory
BGM0A segment for unique identification of the Drawing administration document name, number and function.Mandatory
DTM0A segment specifying the dates relevant to this document; e.g. the date, when the drawing administration in this message has been defined.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 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
QTY0This segment conveys exchange information like the number of engineering/CAD files and their total size (volume) that form part of the exchange of this message and to which this message refers.Optional
SG10SG1Optional
RFF1A segment for quoting the unique references which can be the project number to 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 of 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
SG20SG2Optional
NAD1A segment identifying name and address of a party, in coded or clear form, and its function relevant to the Message. 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
FTX1This segment allows any narrative that may be needed to accompany the party name and address information specified in the previous NAD segment.Optional
INP1A segment that gives each of the receivers their specific instructions for what they should do with this message and the files to which this message refers.Optional
RCS1A segment that gives specific requirements to each of the receivers of this message, e.g. action request.Optional
SG31SG3Optional
RFF2In this segment specific internal references will be quoted, as and when required.Mandatory
DTM2A segment specifying the date and/or time details related to the party's specific internal references.Optional
SG41SG4Optional
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 specified 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
SG50SG5Optional
EFI1This segment will identify the external files by indicating the file name, file number and its sequence number in an exchange.Mandatory
CED1A segment that gives details of a computer or software environment.Mandatory
RFF1A segment giving reference related to the file, identified by the previous EFI segment. This reference number is specific to the sender, and the receivers may be informed about its full meaning through another message (e.g. for the building industry message CONDRO) if this feature is used.Optional
DTM1This segment will convey the date/time details of the external engineering/CAD file.Optional
QTY1The size/volume of the external engineering/CAD file identified in the previous EFI segment.Optional
SG61SG6Optional
BII2This segment will, through a structured index code, uniquely identify the level described in the following segments.Mandatory
GEI2This segment is used to define the level type identified by the previous BII segment, like, for example, drawing sheet, view, layer group, and layer, but also phase etc.Optional
DTM2Date and time details of the level identified in the previous BII segment.Optional
IMD2This segment contains the name of the level that is identified in the previous BII segment.Optional
QTY2This segment conveys quantity details of the level identified in the previous BII segment. This quantity details concern the precision or the number of objects in the lower level, e.g. number of drawing views.Optional
CTA2The person or department responsible (author) of this specific part (level) of the contents is recorded in this segment.Optional
AUT2A segment used to authenticate the part of the message identified in the previous BII segment by exchanging a password or some other form of identification agreed between the business partners.Optional
AGR2This segment will be used to identify the "type of agreement" that applies to the information defined in the previous BII segment.Optional
INP2Instructions for the receiver for this specific part (level) of the contents are recorded in this segment.Optional
RCS2Requirements for the receiver for this specific part (level) of the contents are recorded in this segment.Optional
LOC2This location of the level (e.g. layer) in a co-ordinate system is given in this segment.Optional
DIM2Dimensions (like size, unit of measurements) are given in this segment.Optional
MEA2The scale used can be quoted in this segment.Optional
SG72SG7Optional
RFF3An ID number will be used to refer to either another message/document or to another engineering/CAD file. If needed, here should also be made a reference to a contractual document or to a revision number.Mandatory
SG83SG8Mandatory
DOC4The details of the message/document referred to are quoted in this segment.Mandatory
DTM4Date/time details of the message/document referred to are quoted in this segment.Optional
SG93SG9Optional
SEQ4A segment identifying the beginning of a CAD-file by a sequential number.Mandatory
BII4This segment will through a structured index code uniquely identify the level referred to.Mandatory
RFF4Through an "index system", updates (versions) can be recorded in a reference number. In this segment the version of the level referred to can be quoted.Optional
GEI4This segment is used to define the level type identified in the previous BII segment; like, for example, drawing sheet, view, layer group and layer.Mandatory
DTM4Date/time details of the level that is referred to are quoted here.Optional
IMD4A detailed description of the level referred to 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