Return to EDIFACT D99A Messages page.Response of pending works message
0. INTRODUCTIONThis 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. 1. SCOPEThe 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 DefinitionThis 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 ApplicationThe 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 :
1.3. PrinciplesThis 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. 2. REFERENCESSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONS3.1. Standard terms and definitionsSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION4.1. Data Segment ClarificationThis section should be read in conjunction with the Segment Table which indicates mandatory, conditional and repeating requirements. 0010 UNH, 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:
0020 BGM, Beginning of messageA segment for unique identification of the Response on Pending Works number and type of document. 0030 RFF, 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. 0040 DTM, 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. 0050 Segment Group 1: NAD-SG2A group of segments identifying names, addresses and contacts relevant to the response. 0060 NAD, 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. 0070 Segment Group 2: CTA-COMA group of segments giving contact details of the specific person or department within the party identified in the NAD segment. 0080 CTA, Contact informationA segment giving additional contact information relating to the party specified in the NAD segment, e.g. contact name, department or function. 0090 COM, Communication contactA segment to identify a communication number of the previous information given in CTA (phone, fax, telex, etc.). 0100 LOC, Place/location identificationA segment which enables the sender to specify, in some occurrences, the location of the project and of existing networks. 0110 FTX, 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. 0120 DOC, 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. 0130 CNT, Control totalA segment providing a control total, for example, the number of documents attached to CONAPW. 0140 AUT, Authentication resultA segment to provide an authentication of the message. 0150 UNT, Message trailerA 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)
4.3. Message structure4.3.1. Segment table
Return to EDIFACT D99A Messages page. |