972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Projects and construction

CONRPW Response of pending works

The UN/EDIFACT message service providers use to respond to an advice on pending works with details of their networks in the work area.

Sent by
Utility network operator or authority
Received by
Contractor
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT CONRPW message?

CONRPW is the UN/EDIFACT response of pending works message. The directory defines it as a reply to a CONAPW message that lets service providers respond to a contractor with details of any services and networks in the location where construction work is to be undertaken.

The response may state that the operator has no networks in the area, or provide plans, depths and safety instructions for those it has. Contractors must have the responses on site before digging. It may include plans or references to them.

How the EDIFACT CONRPW message worksDiagram of the UN/EDIFACT CONRPW Response of pending works message. Utility network operator or authority sends it to contractor. It usually follows CONAPW. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), RFF (Reference) and DTM (Date/time/period), body and segment groups: the required SG1 loop with NAD (Name and address) and end of message: LOC (Place/location identification) and FTX (Free text). 1 conditional segment groups are listed by their trigger segment.How the EDIFACT CONRPW message worksResponse of pending works: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSCONAPWAdvice on pendingworksCONRPWSENDERUtility networkoperator or authorityRECEIVERContractorCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage CONRPWUNH … UNTSTART OF MESSAGEBGMBeginning of messageRFFReferenceDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 3NADName and address+ 1 conditional group, starting with:CTAEND OF MESSAGELOCPlace/location identificationFTXFree textBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for CONRPW. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT CONRPW message worksDiagram of the UN/EDIFACT CONRPW Response of pending works message. Utility network operator or authority sends it to contractor. It usually follows CONAPW. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), RFF (Reference) and DTM (Date/time/period), body and segment groups: the required SG1 loop with NAD (Name and address) and end of message: LOC (Place/location identification) and FTX (Free text). 1 conditional segment groups are listed by their trigger segment.How the EDIFACT CONRPWmessage worksResponse of pending works: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSCONAPWAdvice on pending worksCONRPWSENDERUtility networkoperator orauthorityRECEIVERContractorCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message CONRPW (UNH … UNT)START OF MESSAGEBGMBeginning of messageRFFReferenceDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 3NADName and address+ 1 conditional group, starting with:CTAEND OF MESSAGELOCPlace/location identificationFTXFree textBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for CONRPW.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends CONRPW, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around CONRPW and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Confirming networks present in a work area
  • Sending plans and safety instructions to contractors
  • Confirming that no networks are affected

Where it fits in the message flow

Usually follows CONAPW Advice on pending works
This message CONRPW Response of pending works

Structure

Mandatory segments in CONRPW (directory D.21A)

In UN/EDIFACT directory D.21A, the CONRPW message has 13 segment positions arranged in 2 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • RFF
  • DTM
  • SG1 (NAD)
  • LOC
  • FTX
  • UNT

Practical example

CONRPW in practice

A gas distributor receives a CONAPW for trenching along a city street. It replies with a CONRPW stating that a medium-pressure main runs under the sidewalk, with its approximate depth, a reference to the plan and the safety distance required. The contractor briefs its crew and hand-digs near the main.

Implementation

Implementation considerations for CONRPW

  • Respond within the legal or agreed time limit.
  • Provide plans in a format the contractor can use on site.
  • State safety requirements, such as clearances, explicitly.
  • Keep records of responses in case of damage claims.

How ECOM helps

Automate CONRPW with ECOM

Industry

Telecom and Media

Equipment supply chains, service billing and partner data exchange for telecom and media companies.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related projects and construction messages

All 14 projects and construction messages

Need help with CONRPW?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us