| 0010 |
|
|
UNH |
| Message header |
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 07A
0051 UN |
|
M |
1 |
| 0020 |
|
|
BGM |
| Beginning of message |
| A segment for unique identification of the Drawing administration document name, number and function. |
|
M |
1 |
| 0030 |
|
|
DTM |
| Date/time/period |
| A segment specifying the dates relevant to this document; e.g. the date, when the drawing administration in this message has been defined. |
|
M |
5 |
| 0040 |
|
|
AUT |
| Authentication result |
| A segment used to authenticate the message by exchanging a password or some other form of identification agreed between the business partners. |
|
C |
2 |
| 0050 |
|
|
AGR |
| Agreement identification |
| A segment will be used to identify the type of agreement that apply to the information given by this message. |
|
C |
2 |
| 0060 |
|
|
FTX |
| 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. |
|
C |
10 |
| 0070 |
|
|
QTY |
| Quantity |
| 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. |
|
C |
5 |
| 0080 |
|
|
SG1 |
| 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, can be given, in order to identify the project to which this message relates. In any subsequent 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. |
|
M |
10 |
| 0090 |
|
|
RFF |
| Reference |
| 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. |
|
M |
1 |
| 0100 |
|
|
DOC |
| Document/message details |
| Document details of the reference quoted in the previous RFF segment. |
|
C |
1 |
| 0110 |
|
|
DTM |
| Date/time/period |
| Date of a reference quoted in the previous RFF segment, e.g. project date or message/document date. |
|
C |
1 |
| 0120 |
|
|
FTX |
| 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. |
|
C |
5 |
| 0130 |
|
|
SG2 |
| NAD-LOC-FTX-INP-RCS-SG3-SG4 |
| A group of segments identifying all the relevant parties with specific information about them that other business partner should know. |
|
M |
999 |
| 0140 |
|
|
NAD |
| Name and address |
| 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. |
|
M |
1 |
| 0150 |
|
|
LOC |
| Place/location identification |
| A segment giving more specific location information of the party specified in the NAD segment e.g. internal site/building number. |
|
C |
99 |
| 0160 |
|
|
FTX |
| Free text |
| This segment allows any narrative that may be needed to accompany the party name and address information specified in the previous NAD segment. |
|
C |
10 |
| 0170 |
|
|
INP |
| Parties and instruction |
| 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. |
|
C |
10 |
| 0180 |
|
|
RCS |
| Requirements and conditions |
| A segment that gives specific requirements to each of the receivers of this message, e.g. action request. |
|
C |
10 |
| 0190 |
|
|
SG3 |
| RFF-DTM |
| This segment group can be used to quote specific references for each partner, that may be needed for internal use. Examples of references that a partner may require are internal project number. |
|
C |
5 |
| 0200 |
|
|
RFF |
| Reference |
| In this segment specific internal references will be quoted, as and when required. |
|
M |
1 |
| 0210 |
|
|
DTM |
| Date/time/period |
| A segment specifying the date and/or time details related to the party's specific internal references. |
|
C |
1 |
| 0220 |
|
|
SG4 |
| CTA-COM-LOC |
| A group of segments giving contact details of the specific person or department within the party identified in the NAD segment. |
|
C |
10 |
| 0230 |
|
|
CTA |
| Contact information |
| A segment to identify a person or department, and their function, to whom communications should be directed. |
|
M |
1 |
| 0240 |
|
|
COM |
| Communication contact |
| A segment to identify a communication type and number for the contact specified in the CTA segment. |
|
C |
5 |
| 0250 |
|
|
LOC |
| Place/location identification |
| 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. |
|
C |
1 |
| 0260 |
|
|
SG5 |
| EFI-CED-RFF-DTM-QTY-SG6 |
| A group of segments that refers through an external file identification to each of the external engineering/CAD files and giving additional information about each of the files. |
|
C |
99 |
| 0270 |
|
|
EFI |
| External file link identification |
| This segment will identify the external files by indicating the file name, file number and its sequence number in an exchange. |
|
M |
1 |
| 0280 |
|
|
CED |
| Computer environment details |
| A segment that gives details of a computer or software environment. |
|
M |
10 |
| 0290 |
|
|
RFF |
| Reference |
| 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. |
|
C |
10 |
| 0300 |
|
|
DTM |
| Date/time/period |
| This segment will convey the date/time details of the external engineering/CAD file. |
|
C |
5 |
| 0310 |
|
|
QTY |
| Quantity |
| The size/volume of the external engineering/CAD file identified in the previous EFI segment. |
|
C |
5 |
| 0320 |
|
|
SG6 |
| BII-GEI-DTM-IMD-QTY-CTA-AUT-AGR-INP-RCS-LOC-DIM-MEA-SG7 |
| A group of segments that records more detailed information about the contents of the external engineering/CAD file is identified in the previous EFI segment. This information is organised hierarchically. First, each hierarchy is identified, followed by the type of hierarchy. |
|
C |
100000 |
| 0330 |
|
|
BII |
| Structure identification |
| This segment will, through a structured index code, uniquely identify the level described in the following segments. |
|
M |
1 |
| 0340 |
|
|
GEI |
| Processing information |
| 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. |
|
C |
5 |
| 0350 |
|
|
DTM |
| Date/time/period |
| Date and time details of the level identified in the previous BII segment. |
|
C |
10 |
| 0360 |
|
|
IMD |
| Item description |
| This segment contains the name of the level that is identified in the previous BII segment. |
|
C |
1 |
| 0370 |
|
|
QTY |
| Quantity |
| 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. |
|
C |
10 |
| 0380 |
|
|
CTA |
| Contact information |
| The person or department responsible (author) of this specific part (level) of the contents is recorded in this segment. |
|
C |
1 |
| 0390 |
|
|
AUT |
| Authentication result |
| 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. |
|
C |
2 |
| 0400 |
|
|
AGR |
| Agreement identification |
| This segment will be used to identify the "type of agreement" that applies to the information defined in the previous BII segment. |
|
C |
2 |
| 0410 |
|
|
INP |
| Parties and instruction |
| Instructions for the receiver for this specific part (level) of the contents are recorded in this segment. |
|
C |
10 |
| 0420 |
|
|
RCS |
| Requirements and conditions |
| Requirements for the receiver for this specific part (level) of the contents are recorded in this segment. |
|
C |
10 |
| 0430 |
|
|
LOC |
| Place/location identification |
| This location of the level (e.g. layer) in a co-ordinate system is given in this segment. |
|
C |
5 |
| 0440 |
|
|
DIM |
| Dimensions |
| Dimensions (like size, unit of measurements) are given in this segment. |
|
C |
5 |
| 0450 |
|
|
MEA |
| Measurements |
| The scale used can be quoted in this segment. |
|
C |
1 |
| 0460 |
|
|
SG7 |
| RFF-SG8-SG9 |
| For each of the levels that are identified in the previous BII segment it is possible to refer to other messages/documents on other levels of the structure of the engineering/CAD file identified in the previous EFI segment. It is also possible to refer to other levels which are part of a different engineering/CAD file than the one identified in the previous EFI segment. If needed, here should also be made a reference to a contractual document or to a revision number. |
|
C |
99 |
| 0470 |
|
|
RFF |
| Reference |
| 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. |
|
M |
1 |
| 0480 |
|
|
SG8 |
| DOC-DTM |
| If the reference number quoted in the previous RFF segment is a reference to another message/document, this segment group is used to give more details about this message/document. |
|
C |
1 |
| 0490 |
|
|
DOC |
| Document/message details |
| The details of the message/document referred to are quoted in this segment. |
|
M |
1 |
| 0500 |
|
|
DTM |
| Date/time/period |
| Date/time details of the message/document referred to are quoted in this segment. |
|
C |
1 |
| 0510 |
|
|
SG9 |
| SEQ-BII-RFF-GEI-DTM-IMD |
This segment group will be used when a reference is made to another specific level in the structure of an engineering/CAD file.
If in the previous RFF segment a standard dummy value is quoted, the level referred to is part of the engineering/CAD file identified in the previous EFI segment. If, however, in the previous RFF segment any other value is quoted, the level described in the following BII segment is part of the engineering/CAD file identified by the ID number. |
|
C |
999 |
| 0520 |
|
|
SEQ |
| Sequence details |
| A segment identifying the beginning of a CAD-file by a sequential number. |
|
M |
1 |
| 0530 |
|
|
BII |
| Structure identification |
| This segment will through a structured index code uniquely identify the level referred to. |
|
M |
1 |
| 0540 |
|
|
RFF |
| Reference |
| 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. |
|
C |
1 |
| 0550 |
|
|
GEI |
| Processing information |
| 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. |
|
M |
5 |
| 0560 |
|
|
DTM |
| Date/time/period |
| Date/time details of the level that is referred to are quoted here. |
|
C |
1 |
| 0570 |
|
|
IMD |
| Item description |
| A detailed description of the level referred to can be quoted in this segment. |
|
C |
1 |
| 0580 |
|
|
UNT |
| 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. |
|
M |
1 |
