CONRPW Response of pending works

TBG6 Architecture, Engineering and Construction

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.

Header

1. 00010 · UNH · Message header · Max 1 · Mandatory

   A 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 11B 0051 UN

   1. Data element S009/0057 is retained for upward compatibility. The use of
   S016 and/or S017 is encouraged in preference.
   2. The combination of the values carried in data elements 0062 and S009 shall
   be used to identify uniquely the message within its group (if used) or if
   not used, within its interchange, for the purpose of acknowledgement.

2. 00020 · BGM · Beginning of message · Max 1 · Mandatory

   A segment for unique identification of the Response on pending works number and type of document.

3. 00030 · RFF · Reference · Max 9 · Mandatory

   A 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.

4. 00040 · DTM · Date/time/period · Max 9 · Mandatory

   A 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.

5. Segment group 1 Repeat 3

   1. 00060 · NAD · Name and address · Max 1 · Mandatory

      A 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.

   2. Segment group 2 Repeat 2

      1. 00080 · CTA · Contact information · Max 1 · Mandatory

         A segment giving additional contact information relating to the party specified in the NAD segment, e.g. contact name, department or function.

      2. 00090 · COM · Communication contact · Max 3 · Conditional

         A segment to identify a communication number of the previous information given in CTA (phone, fax, telex, etc.).

6. 00100 · LOC · Place/location identification · Max 99 · Mandatory

   A segment which enables the sender to specify, in some occurrences, the location of the project and of existing networks.

7. 00110 · FTX · Free text · Max 99 · Mandatory

   A 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.

8. 00120 · DOC · Document/message details · Max 9 · Conditional

   A 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.

9. 00130 · CNT · Control total · Max 5 · Conditional

   A segment providing a control total, for example, the number of documents attached to CONAPW.

10. 00140 · AUT · Authentication result · Max 1 · Conditional

    A segment to provide an authentication of the message.

11. 00150 · UNT · Message trailer · Max 1 · Mandatory

    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.

    1. 0062, the value shall be identical to the value in 0062 in the
    corresponding UNH segment.