Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D01A Messages page.

Response of pending works message

Contr. Agency:UN
SOURCE:D7 Architecture, Engineering and Construction (SWG)

Response of pending works message
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
    1. Standard terms and definitions
    1. Segment clarification
    2. Segment index (alphabetical sequence by tag)
    3. Message structure
      1. Segment table

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction

This message also occurs in the following versions of this standard:
D94A, D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B


This specification provides the definition of the Response of pending works message (CONRPW) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


The construction industry uses this message during its design, building and maintenance stages. It communicates with organisations about existing and planned services in the vicinity of the works.

1.1. Functional definition

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.

1.2. Field of application

The Response of pending works message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.

The parties involved in such transfers belong to various industry sectors :

  • the construction industry : contractors are the recipients of the message.
  • gas, electricity, ... and more generally network distributors who are among the senders of such messages, and who will process them to advise contractors of the presence of existing networks.
  • public authorities, which may be
  • clients or designers of projects
  • in charge of specific responsibilities eventually affected by the projects.
  • in some cases, this type of response on a formal advice may have a legal status, the consequence of it may be the liability of the sender or receiver. Some insurance companies also may be concerned by this message.

1.3. Principles

This is only one of a group of messages being designed for this flow among construction industry. Many aspects have to be considered, they are described in the following paragraphs.

This message is the response to a prior request of information, which has eventually been sent through another appropriate EDI message.

The type of the information to convey in the "flow" CONRPW is not only alphanumeric, but some geographical and graphical information may be conveyed in conjunction with the response itself, in order that the recipient gets all the relevant elements on the existing networks. There is another appropriate EDI message being designed to convey information on plans and drawing organization, and it has been decided not to put this information in the message CONRPW itself, but to give an opportunity to link CONRPW with the drawing organization message.


See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.


3.1. Standard terms and definitions

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.


4.1. Segment clarification

This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.

0010 UNH, Message header

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 element0065CONRPW

0020 BGM, Beginning of message

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

0030 RFF, Reference

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.

0040 DTM, Date/time/period

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.

0050 Segment Group 1: NAD-SG2

A group of segments identifying names, addresses and contacts relevant to the response.

0060 NAD, Name and address

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.

0070 Segment Group 2: CTA-COM

A group of segments giving contact details of the specific person or department within the party identified in the NAD segment.

0080 CTA, Contact information

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

0090 COM, Communication contact

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

0100 LOC, Place/location identification

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

0110 FTX, Free text

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.

0120 DOC, Document/message details

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.

0130 CNT, Control total

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

0140 AUT, Authentication result

A segment to provide an authentication of the message.

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

4.2. Segment index (alphabetical sequence by tag)

AUT Authentication result
BGM Beginning of message
CNT Control total
COM Communication contact
CTA Contact information
DOC Document/message details
DTM Date/time/period
FTX Free text
LOC Place/location identification
NAD Name and address
RFF Reference
UNH Message header
UNT Message trailer

4.3. Message structure

4.3.1. Segment table

├─UNH Message header ×1 (M)
├─BGM Beginning of message ×1 (M)
├─RFF Reference ×9 (M)
├─DTM Date/time/period ×9 (M)
├─Segment Group 1 ×3 (M)
├─NAD Name and address ×1 (M)
└─Segment Group 2 ×2 (C)
──├─CTA Contact information ×1 (M)
──└─COM Communication contact ×3 (C)
├─LOC Place/location identification ×99 (M)
├─FTX Free text ×99 (M)
├─DOC Document/message details ×9 (C)
├─CNT Control total ×5 (C)
├─AUT Authentication result ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D01A Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools EDIFACT to XML
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.