D05A
Message D05A/CONRPW
Response of pending works message
This message is a reply to a CONAPW message and enables service providers to respond to a contractor giving details of any services and networks in the location where construction work is to be undertaken.
Message description
UNH
M(1) : Message headerA service segment starting and uniquely identifying a message. The message type code for the Response of pending works message is CONRPW. Note: Response of pending works messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 CONRPW 0052 D 0054 05A 0051 UN
BGM
M(1) : Beginning of messageA segment for unique identification of the Response on pending works number and type of document.
RFF
M(9) : ReferenceA segment to give prior references of the whole document, for example, project number or contract number, and authorization references if required, and the reference to the prior Advice on Pending Works.
DTM
M(9) : Date/time/periodA segment specifying the dates that apply, e.g. forecasted date to start works, duration of the project and/or forecasted date of end of the works.
SG1 M(3) : NAD-SG2
A group of segments identifying names, addresses and contacts relevant to the response.
NAD
M(1) : Name and addressA segment identifying names and addresses and their function relevant for the whole response on pending works. In the construction industry parties involved are e.g. the contractor, the designer, the client.
SG2 C(2) : CTA-COM
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 informationA segment giving additional contact information relating to the party specified in the NAD segment, e.g. contact name, department or function.
COM
C(3) : Communication contactA segment to identify a communication number of the previous information given in CTA (phone, fax, telex, etc.).
LOC
M(99) : Place/location identificationA segment which enables the sender to specify, in some occurrences, the location of the project and of existing networks.
FTX
M(99) : Free textA segment to specify some special indications on the nature of the networks, in coded and/or clear form, that is not possible to indicate in the LOC segment.
DOC
C(9) : Document/message detailsA segment to specify which other documents (drawing organization, circulation list, plans, etc.) are to be processed in conjunction with CONAPW, and what is the communication channel used to transfer them.
CNT
C(5) : Control totalA segment providing a control total, for example, the number of documents attached to CONAPW.
AUT
C(1) : Authentication resultA segment to provide an authentication of the message.
UNT
M(1) : Message trailerA 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.
Message structure
UNH, Message header M 1 BGM, Beginning of message M 1 RFF, Reference M 9 DTM, Date/time/period M 9 --- Segment Group 1 ------------------------- M 3 -------+ NAD, Name and address M 1 | | --- Segment Group 2 ------------------------- C 2 ------+| CTA, Contact information M 1 || COM, Communication contact C 3 || ---- ----------------------------------------------------------++ LOC, Place/location identification M 99 FTX, Free text M 99 DOC, Document/message details C 9 CNT, Control total C 5 AUT, Authentication result C 1 UNT, Message trailer M 1