CONQVA Quantity valuation

TBG6 Architecture, Engineering and Construction

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.

Header

Position
Segment
Name
Max use
  1. A service segment starting and uniquely identifying a message. The message type code for the Quantity valuation message is CONQVA. Note: Quantity valuation messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 CONQVA 0052 D 0054 21A 0051 UN

    1. Data element S009/0057 is retained for upward compatibility. The use of
    S016 and/or S017 is encouraged in preference.
    2. The combination of the values carried in data elements 0062 and S009 shall
    be used to identify uniquely the message within its group (if used) or if
    not used, within its interchange, for the purpose of acknowledgement.
  2. A segment for unique identification of the Quantity valuation document name, number and function.

  3. A segment specifying the dates that apply, e.g. date of valuation, date of submission, acceptance date, etc.

  4. A segment used to authenticate the message by exchanging a password or some other form of identification agreed between the trading partners.

  5. 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.

  6. Segment group 1
    Repeat 9
    1. A segment for quoting references that are applicable to this message, e.g. contract identity, operational references, former valuation reference number.

    2. Date of references quoted in the previous RFF segment.

  7. Segment group 2
    Repeat 9
    1. 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.

    2. A segment giving more specific location information of the party specified in the NAD segment e.g. internal site/building number.

    3. A segment identifying the financial institution (e.g. bank) and relevant account numbers for the contractor, client and where necessary other parties.

    4. Segment group 3
      Repeat 10
      1. A segment identifying the reference by its number and where appropriate a line number within a document.

      2. A segment specifying the date and/or time related to the reference.

    5. Segment group 4
      Repeat 5
      1. A segment identifying and providing information relating to the documents required by the party specified by the NAD.

      2. A segment specifying the date and/or time of the document.

    6. Segment group 5
      Repeat 5
      1. A segment to identify a person or department, and their function, to whom communications should be directed.

      2. A segment to identify a communications type and number for the contact specified in the CTA segment.

Detail

Position
Segment
Name
Max use
  1. Segment group 6
    Repeat 100000
    1. A segment to identify the item of work (or group of items) to which the quantities apply.

    2. A segment to provide requirements that are applicable to the whole group of segments: financial status (when an item is added to the BOQ, dayworks for example), and an action request.

    3. A segment giving the quantity of works performed, in cumulative, last period cumulative, quantity of the period, and other forms as required.

    4. 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. dayworks.

    5. Segment group 7
      Repeat 100
      1. A segment to record a qualifier specifying that we are at item level.

      2. Segment group 8
        Repeat 1000
        1. 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.

        2. A segment used to record up to two text reference numbers per item description line.

        3. A segment used to record up to two text change action codes per item description line. In this context suppression is not allowed.

    6. Segment group 9
      Repeat 5
      1. 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.

      2. A segment specifying the amount for the identified tax/fee.

      3. 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.

Summary

Position
Segment
Name
Max use
  1. A segment by which control totals may be provided by the sender for checking by the receiver.

  2. A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.