EDIFACT message guide · Projects and construction
CONWQD Work item quantity determination
The UN/EDIFACT message used to justify the work item quantities given in messages that describe work items or their progress.
- Sent by
- Contractor or other construction partner
- Received by
- Client's representative or other partner
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT CONWQD message?
CONWQD is the UN/EDIFACT work item quantity determination message. The directory describes it as typically used between a contractor and the client's representative or other partners to justify the work item quantities given in messages that describe the work items or their progress.
Quantity determination carries the measurements and calculations behind a quantity, such as dimensions taken from drawings or site surveys. It lets the client's representative check how a reported quantity was derived without paper calculation sheets. It reduces disputes over measured quantities.
How to read this diagram: the top row shows who sends CONWQD, 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 CONWQD 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.
When it is used
- Justifying quantities in progress reports
- Exchanging measurement calculations
- Resolving disputed quantities
Where it fits in the message flow
Structure
Mandatory segments in CONWQD (directory D.21A)
In UN/EDIFACT directory D.21A, the CONWQD message has 29 segment positions arranged in 9 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
- SG6 (BII)
- UNT
Practical example
CONWQD in practice
A contractor reports 3,400 square meters of paving completed. The client's surveyor questions the figure, and the contractor sends a CONWQD with the measured areas of each section and the calculation. The surveyor checks the measurements against the drawings and accepts the quantity.
Implementation
Implementation considerations for CONWQD
- Link measurements to the work items they support.
- Use measurement rules agreed in the contract.
- Keep calculations reproducible from the data sent.
- Store determinations with the valuations they support.
How ECOM helps
Automate CONWQD with ECOM
Industry
Industrial Manufacturing
Distributor, OEM customer and supplier integration for industrial manufacturers.
Solution
B2B Integration
Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.
Solution
Financial Document Automation
Automate invoices, remittances, payment files and bank statements from capture to posting.
Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.
Related messages
Related projects and construction messages
Need help with CONWQD?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.