0.    INTRODUCTION

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

1.    SCOPE

       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

       Typically, this message is to enable a contractor who intends
       to start works to advise public authorities and water, gas,
       telephone, electricity ... distributors of his intention and to
       request them to send back plans or information under any form
       concerning existing networks.

1.2   Field of Application

       The parties involved in such transfers belong to various
       industry sectors : 
       
       - the construction industry: contractors are often the
       originating parties of the message.
              
       - gas, electricity, ... and more generally network distributors
       who are among the recipients of such messages, and who will
       process them to check whether they operate networks in an area
       concerned by works.
              
       - 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 advice may contain 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.
              
       Within the construction industry, there are numerous rules
       which govern this part of the process. Although, efforts have
       been made to keep the design of the message generic, other
       potential users of this message are cautioned about the
       specific and original role for which this message has been
       designed.

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.
       "Sending" process of the message : the message is originated by
       one party, but is sent to numerous recipients (from 10 to 20).
       This is the reason why an opportunity is given to use this
       message in conjunction with an appropriate service message wich
       enables the sender to indicate to a VAN operator that a
       considered message has to be distributed to more than one
       receiver.
       This message contains a request for information, to be provided
       back in another appropriate EDI message. The type of the
       information to convey in the "flow" CONAPW is not only
       alphanumeric, but some geographical and graphical information
       may be conveyed in conjunction with the advice itself, in order
       that the recipient gets all the relevant elements on the
       pending works. 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 CONAPW itself, but to give an
       opportunity to link CONAPW with the drawing organization
       message.
       In addition, some recipients are interested in receiving the
       list of the other recipients. For the reason that this is not
       systematic, and in order to keep the design of the message as
       simple as possible, it has been decided to use an other
       appropriate service message providing a circulation list, and
       to give an opportunity to link CONAPW with this circulation
       message.

2.    REFERENCES

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

3.    TERMS AND DEFINITIONS

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

4.    MESSAGE DEFINITION

4.1   Data Segment Clarification

       This section should be read in conjunction with the Branching
       Diagram and the Segment Table which indicate mandatory,
       conditional and repeating requirements.

 | UNH, Message header
       A service segment starting and uniquely identifying a message.
       The message type code for the Advice on pending works message
       is CONAPW.
       
       Note: Advice on pending works messages conforming to this
       document must contain the following data in segment UNH,
       composite S009:

       Data element  0065 CONAPW
                     0052 D
                     0054 95B
                     0051 UN

   BGM, Beginning of message
       A segment for unique identification of the Advice on Pending
       Works number and type of document.

   RFF, Reference
       A segment to give prior references of the whole document, for
       example, project number or contract number, and authorization
       references if required.

   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.


   Segment group 1: NAD-SG2
       A group of segments identifying names, addresses and contacts
       relevant to the advice.

      NAD, Name and address
          A segment identifying names and addresses and their function
          relevant for the whole advice on pending works. In the
          construction industry parties involved are e.g. the
          contractor, the designer, the client.


      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.

         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.

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

   LOC, Place/location identification
       A segment, which enables the sender to specify in some
       occurrences the location(s) of the project.

   FTX, Free text
       A segment to specify the nature of the works, in coded and/or
       clear form.

   DOC, Document/message details
       A segment to specify which other documents (drawing
       organization, circulation list, plans, etc.) are to be sent and
       processed in conjunction with CONAPW, and what is the
       communication channel used to transfer them.

   CNT, Control total
       A segment enabling controls, for example, the number of
       documents attached to CONAPW.

   AUT, Authentication result
       A segment to provide an authentication of the message.

   UNT, Message trailer
       A service segment ending a message, giving the total number of
       segments in the message and the control reference number of the
       message.

4.2   Data 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

 Contents of D.95B