% Response.CharSet="utf-8" %>
This message is available for formal trial in the present version for a period of at least twelve months from the date of approval by the UN/ECE/TRADE/WP.4.
Organisations are invited to trial this message and are requested to notify their Rapporteur Team Secretariat of their intention. Comments on the results from the trial should also be forwarded to the Secretariat as soon as they are available. Based on the results of the trials, a UNSM will be issued.
It should be noted that this material is contained in a Trial Directory; however, it may differ from that in the UN Directories (UNTDID) having the same identfying tags. Any differences will be reconciled prior to the message becoming a UNSM.
|SOURCE:||Western European EDIFACT Board - MD5|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.5, UN/ECE UNSM General Introduction.
This message also occurs in the following versions of this standard:|
D93A, 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 Quantity Valuation message (CONQVA) to be used in Electronic Data Interchange (EDI) between partners involved in Administration, Commerce and Transport.
Typically this message will be used for a contractor to submit progress details to a client or his representative. The message will be used also for subsets of the project where work has been contracted out to other parties. In these cases the exchange would be between the subcontractor and the party that subcontracted the work.
This message type may be applied for both national and international trade. It is based on universal practice and is not dependent on the type of business or industry. The following descriptions refer to the construction industry as an example, but do not exclude other business sectors' implementation.
This message is to be used to support the business of exchanging progress information for groups of work items which make up a construction project. There are several examples within the construction process where one party is required to advise another party about the quantity of work performed for a specific time period or since the start of the project. A project may be subdivided into individual groupings of work referred to as items and it is against these items that progress quantities are reported. During the design of this message every effort has been made to adopt a "generic" approach and it seems possible that other industries may find this a suitable message to adopt. This is only one of a number of messages being designed for the Construction industry. This particular message refers to already established items of work, these items will be defined at the start of a project. Work is well advanced on suitable EDI messages to address this part of the process. Allowance has been made within the CONQVA message for "new" items of work. There are a number of reasons why additional items of work will occur once a project has started. Each work item may contain more than one quantity and this has been accommodated. An example of this would be the quoting of both a cumulative and a "this period" quantity.
See UNTDID, Part 4 Section 2.5 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Section 2.5 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type identifier for the UN Quantity Valuation Message is 'CONQVA'. Note: Quantity Valuation Message conforming to this document must contain the following data in UNH, composite S009: Data element 0065 CONQVA 0052 D 0054 93A 0051 UN
A segment for unique identification of the Quantity Valuation document name, number and function.
A segment specifying the dates that apply, e.g. date of valuation, date of submission, acceptance date, etc.
A segment used to authenticate the message by exchanging a password or some other form of identification agreed between the trading partners.
A segment with free text information, in coded or clear form, used for any textual qualification. In computer to computer exchanges, such text will require the receiver to process this segment manually.
A group of segments for quoting references and their relevant dates that are applicable to the message.
A segment for quoting references that are applicable to this message, e.g. contract identity, operational references, former valuation reference number.
Date of references quoted in the previous RFF segment.
A group of segments identifying the parties with associated information.
A segment identifying names and addresses of the parties, in coded or clear form, and their functions relevant to the valuation. It is recommended that where possible only the coded form of the party ID should be specified. e.g. The contractor and client are known to each other, thus only the coded ID is required, but the subcontractors addresses may vary and would have to be clearly specified, preferably in structured format.
A segment giving more specific location information of the party specified in the NAD segment e.g. internal site/building number.
A segment identifying the financial institution (e.g. bank) and relevant account numbers for the contractor, client and where necessary other parties.
A group of segments for giving references only relevant to the specified party rather than the whole valuation.
A segment identifying the reference by its number and where appropriate a line number within a document.
A segment specifying the date and/or time related to the reference.
A group of segments identifying the documentary requirements of the specified party.
A segment identifying and providing information relating to the documents required by the party specified by the NAD.
A segment specifying the date and/or time of the document.
A group of segments giving contact details of the specific person or department within the party identified in the NAD segment.
A segment to identify a person or department, and their function, to whom communications should be directed.
A segment to identify a communications type and number for the contact specified in the CTA segment.
A group of segments providing the quantities and the corresponding prices of the works performed for each item, or group of items.
A segment to identify the item of work (or group of items) to which the quantities apply.
A segment to provide requirements that are applicable to the whole group of segments: financial status (when an item is added to the BOQ, day works for example), and an action request.
A segment giving the quantity of works performed, in cumulative, last period cumulative, quantity of the period, and other forms as required.
A segment used to indicate the unit price of the items. This segment is to be used in conjunction with SG7 and SG9 when an item is created in the quantity valuation e.g. day works.
A group of segments to record descriptive text for items that are added into existing groups during the completion of the works, e.g. day works.
A segment to record a qualifier specifying that we are at item level.
A group of segments to record the description line details together with text reference numbers and change action codes used to identify who is authorised to apply changes.
This segment is used to convey any descriptive material to be recorded for the item. This descriptive material can apply to the item description and item heading information.
A segment used to record up to two text reference numbers per item description line.
A segment used to record up to two text change action codes per item description line. In this context suppression is not allowed.
A group of segments specifying tax related information for this item when it is specific to this item or different from the group to which it belongs, and when necessary, the location(s) to which that tax information relates. This group is to be used only when the item is created in the quantity valuation, e.g. day works and the relevant tax is different to the one described to group referred to in BII.
A segment specifying a tax type, category and rate, or exemption, relating to the group of items referred to in BII, e.g. Value Added Tax at the standard rate is applicable for all items.
A segment specifying the amount for the identified tax/fee.
A segment indicating the location to which the tax or exemption specified in the TAX segment applies, e.g. city or state or country tax.
A segment by which control totals may be provided by the sender for checking by the receiver.
A service segment ending a message, giving the total number of segments in the message, and the control reference number of the message.
|├─UNH Message header||×1||(M)|
|├─BGM Beginning of message||×1||(M)|
|├─AUT Authentication result||×2||(C)|
|├─FTX Free text||×5||(C)|
|├─Segment Group 1||×9||(C)|
|├─Segment Group 2||×9||(M)|
|│─├─NAD Name and address||×1||(M)|
|│─├─LOC Place/location identification||×25||(C)|
|│─├─FII Financial institution information||×5||(C)|
|│─├─Segment Group 3||×10||(C)|
|│─├─Segment Group 4||×5||(C)|
|│─│─├─DOC Document/message details||×1||(M)|
|│─└─Segment Group 5||×5||(C)|
|│───├─CTA Contact information||×1||(M)|
|│───└─COM Communication contact||×5||(C)|
|├─Segment Group 6||×100000||(C)|
|│─├─BII Bill item identification||×1||(M)|
|│─├─RCS Requirements and conditions||×1||(C)|
|│─├─PRI Price details||×1||(C)|
|│─├─Segment Group 7||×100||(M)|
|│─│─├─LIN Line item||×1||(M)|
|│─│─└─Segment Group 8||×1000||(C)|
|│─│───├─IMD Item description||×1||(M)|
|│─│───└─GIS General indicator||×5||(C)|
|│─└─Segment Group 9||×5||(C)|
|│───├─TAX Duty/tax/fee details||×1||(M)|
|│───├─MOA Monetary amount||×1||(C)|
|│───└─LOC Place/location identification||×5||(C)|
|├─CNT Control total||×5||(C)|
|└─UNT Message trailer||×1||(M)|
|BGM||Beginning of message|
|BII||Bill item identification|
|FII||Financial institution information|
|NAD||Name and address|
|RCS||Requirements and conditions|