CONDRA Drawing administration BETA
TBG6 Architecture, Engineering and Construction
The message will be used for the administration of each exchange of a set of engineering/CAD files. It will give additional information about the files; for example, their nature, a list of their contents and technical information necessary to interpret them.
The whole process of exchanging engineering or CAD (Computer Aided Design) files between different parties within projects will be supported by EDIFACT messages. The message CONDRA is one of these messages.
A 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 0052 D 0054 21A 0051 UN
A segment for unique identification of the Drawing administration document name, number and function.
A segment specifying the dates relevant to this document; e.g. the date, when the drawing administration in this message has been defined.
A segment used to authenticate the message by exchanging a password or some other form of identification agreed between the business partners.
A segment will be used to identify the type of agreement that apply to the information given by this message.
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.
This 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.
A 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.
Document details of the reference quoted in the previous RFF segment.
Date of a reference quoted in the previous RFF segment, e.g. project date or message/document date.
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.
A 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.
A segment giving more specific location information of the party specified in the NAD segment e.g. internal site/building number.
This segment allows any narrative that may be needed to accompany the party name and address information specified in the previous NAD segment.
A 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.
A segment that gives specific requirements to each of the receivers of this message, e.g. action request.
A segment to identify a person or department, and their function, to whom communications should be directed.
A segment to identify a communication type and number for the contact specified in the CTA segment.
This 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.
This segment will identify the external files by indicating the file name, file number and its sequence number in an exchange.
A segment that gives details of a computer or software environment.
A 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.
This segment will convey the date/time details of the external engineering/CAD file.
The size/volume of the external engineering/CAD file identified in the previous EFI segment.
This segment will, through a structured index code, uniquely identify the level described in the following segments.
This 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.
Date and time details of the level identified in the previous BII segment.
This segment contains the name of the level that is identified in the previous BII segment.
This 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.
The person or department responsible (author) of this specific part (level) of the contents is recorded in this segment.
A 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.
This segment will be used to identify the "type of agreement" that applies to the information defined in the previous BII segment.
Instructions for the receiver for this specific part (level) of the contents are recorded in this segment.
Requirements for the receiver for this specific part (level) of the contents are recorded in this segment.
This location of the level (e.g. layer) in a co-ordinate system is given in this segment.
Dimensions (like size, unit of measurements) are given in this segment.
The scale used can be quoted in this segment.
An 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.
A segment identifying the beginning of a CAD-file by a sequential number.
This segment will through a structured index code uniquely identify the level referred to.
Through 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.
This segment is used to define the level type identified in the previous BII segment; like, for example, drawing sheet, view, layer group and layer.
Date/time details of the level that is referred to are quoted here.
A detailed description of the level referred to can be quoted in this segment.
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.