0. Introduction
1. Scope
   1. Functional Definition
   2. Field of Application
   3. Principles
2. References
3. Message Definition
4. Message Definition
   1. Data Segment Clarification
   2. Message structure
      1. Branching Diagram
      2. Segment Table
   3. Data Segment Index (Alphabetic Sequence)

This specification provides the definition of the message Invitation to Tender (CONITT) to be used in Electronic Data Interchange (EDI) between partners involved in Administration, Commerce and Transport.

At the pre-construction stage of a construction project, the Client will wish to appoint a contractor to execute the works. The first step in this appointment process is to issue an invitation to tender (ITT) to contractors this will require a commercial offer to be made by the contractor to the client.

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.

A BoQ is a set of documentation that describes the various facets of work that make up a construction project. This documentation is often quite voluminous and typically contains information structured in accordance with several industry standards. The BoQ is a key set of documentation for a number of stages within the overall construction process. This documentation, or parts of it, are frequently exchanged between the various parties involved in the project. A significant document used within the invitation to tender process is the Bill of Quantities (BoQ). This documentation subsequently becomes the contractual basis for the project. A project is typically subdivided into individual groupings of work and within these groups are detailed work items. It is down to this level of detailed work items that commercial offer information is to be supplied. If there are any project design changes during the tender period, which have an impact on the detailed work items in a BoQ, these would also be communicated in a CONITT message. Although the initial exchange typically takes place at the pre- tender stage, it may also be used post-tender. At the tender stage, one or more competing Main Contractors will be sent by the Client or his representative, a BoQ document for the purpose of pricing the detailed work items to support the commercial tender offer. The Main Contractors in turn may wish to invite tenders

from subcontractors for specialist portions of the project. This would be done by each competing Main Contractor creating subsets of the original BoQ document for each type of specialist work and sending that in turn to a number of competing subcontractors of their choice. Once the main contract has been established with the successful Main Contractor, the ITT process will in some cases be repeated with subcontractors. This will enable the Main Contractor to seek improved offers from subcontractors following the securement of the contract. This is only one of a number of messages being designed for the BoQ and the principles for this CONITT message are consistent with those adopted for each of the other BoQ messages. There are several concepts to be understood and these are key to some of the design principles adopted. Most of these have been created to respond to two base problems associated with the BoQ documentation:

1. A BoQ is often a very large document, it is not unusual for it to run to several volumes in its paper form.
2. Given the size of the documents, there is also the problem of how to advise on the structure to which the document conforms and the accurate indexing and sequencing of information within such a volume of data.

Each individual component of work referred to in the BoQ is called a "work item" and it is at this level that progress and payments are evaluated. For each work item a description is provided and this description is very precise in its wording. This results in two things:

1. A lot of repetitive descriptions for like items at least at the higher levels within these leveled descriptions. ii) A lot of similar work items, indeed the same description, often occurs a number of times throughout the project but assigned to different work items. Point ii) above has been addressed by a concept called " standard items", this enables an equivalent to a standard library of descriptions to be exchanged and individual work items to reference a standard description that need be sent, only once. Frequently within a BoQ, elements of an item's description are common to adjacent items. When this happens the items which share the same description are grouped together and the common part of the description is presented once at the start of the group. This concept is used extensively and it is possible to have quite a number of layers of shared heading. Two distinctions need to be established, firstly, the existence of Heading text which is related to an item. There can be multiples of these as in the levels of a standard description. The second distinction is that of "Groups". Where a group is a collection of more than one work item and all of these items have a common theme. For example:

• they all belong to the same trade
• all for the same part of the project, building or structure. Despite the large number of items that they may embrace, or the fact that they represent substantial parts of the project, all of these are recognised as "groups". Thus, there can be several or many items within a group and there can be layers of groups within groups, all of which collectively constitute the project.

There are numerous variations for structuring the information that makes up the BoQ. Although, it is possible to introduce some standardisation it is clear that any message must allow the freedom to structure the data according to the dictates of a individual project. The design therefore, includes the ability to convey the document's structure as part of the BoQ message. Indeed the design allows for a different set of document structuring information, to be defined at group level as well as globally for the project. This means that a set of indexing rules can be defined to apply to the entire project and that a different set of indexing rules can be used to override these for a given group(s). To complement the indexing concept there is a component referred to as the "Project Index Reference". This is a faceted code assigned to all items of data that are to be used in conjunction with the index. In other words all pieces of data that are to be structured using the index must contain a structured code composed in accordance with the index and this is used as a "sorting" mechanism to ensure that the data is correctly structured.

The actual appearance of the message bears no relation to the appearance of the current paper document! As there are unlimited permutations for assembling the BoQ data it has not been possible, nor desirable to make the appearance similar. The CONITT appearance is similar to the results of the data analysis exercise. Namely that there are 4 blocks or groupings of data, each of which can appear many times and that all of the mechanisms for linking and relating the components together are data elements within these blocks. The task of interpreting the indexing rules and subsequently assembling the data in the message will fall to local software. The complexity of this task has been simplified by grouping the data elements into the blocks described above. In this way the processing can follow a logical flow. This approach has several advantages over the existing rigidity of the paper document. It is clear to the message design team that BoQ documentation exchanged using EDI will deliver a variety of new opportunities to its users. This last principle offers the solution to the volume problem too. One message has a definitive number of occurrence's for each block of

data. If for a "large" project this number is exceeded then multiple versions of the same message are built. It also enables a BoQ to be exchanges in subdivisions if so desired.

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.

0010 UNH, Message header

A service segment which starts and uniquely identifies a message. The message type identifier for the UN Invitation to Tender message is 'CONITT'. Note: The CONITT message conforming to this document must contain the following data in UNH composite S009: Data element 0065 CONITT 0052 D 0054 93A 0051 UN

0020 BGM, Beginning of message

A segment which identifies the document name and the message function code.

0030 RFF, Reference

This segment is used to identify the unique project reference number.

0040 DTM, Date/time/period

The document date will be recorded using this DTM segment.

0050 AUT, Authentication result

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

0060 AGR, Agreement identification

This segment will be used to identify the "type of contract and form of tender" that apply to this contract.

0070 Segment Group 1: IND-RCS-SG2

A group of segments to record both the structure and contents of the indexing used for the BoQ document.

0080 IND, Index details

A segment to qualify whether the index applies to the whole project, part of a project (a group of items), or whether the index provides an alternative view (analysis) of the work items. The segment also indicates in the index qualifier whether it contains index structure information or describes the index contents.

0090 RCS, Requirements and conditions

A segment used to indicate the action request (add , change etc.) to be applied to the index data.

0100 Segment Group 2: GIS-SG3

A group of segments to specify the position and detailed component parts of the index information.

0110 GIS, General indicator

This indicator segment specifies one of six positions within the index structure to which the detailed information applies.

0120 Segment Group 3: BII-IMD

A group of segments to specify the detailed components of the index information.

0130 BII, Bill item identification

A segment used to specify a structured index number that is to be associated with the descriptions that follow in segment IMD.

0140 IMD, Item description

A segment to specify the descriptions in both full text and abbreviated form . These descriptions to be associated with the contents of segment BII.

0150 Segment Group 4: BII-RCS-GIS-NAD-LOC-API-ALI-QTY-DTM-RTE-SG5-SG6-SG7-SG9-SG10-SG18

This information is subordinate to the data provided within the Header section and relates to groups of work items as described in section 1.3.1 of this document. A segment group recording all the details that apply to a group of items. There can be many "Groups of items" within a project and all are to be recorded within this part of the message.

0160 BII, Bill item identification

A segment used to convey a structured index number that uniquely identifies each group of items recorded for the project.

0170 RCS, Requirements and conditions

The action to be applied to segment group 4 data is recorded here.

0180 GIS, General indicator

This indicator segment identifies what category of item grouping NAD, Name and address The recording of the name and address information applying to this group of items.

0190 LOC, Place/location identification

In addition to the name and address details above this is the identification of a location description and an abbreviated or short name by which the grouping is to be known.

0200 API, Additional price information

A segment to record a multiplication factor called "Timesing" that applies to the entire project or a specific grouping of items.

0210 ALI, Additional information

This segment would be used to denote, in a coded form, what rules were adopted for the rounding of all financial values within this group of items.

0220 QTY, Quantity

This segment enables grouping control quantities to be recorded. These are not to be confused with message control totals that appear later and use the CNT segment.

0230 DTM, Date/time/period

Any date details required for the group of items will be recorded using the DTM segment. There are a considerable number of different date qualifiers that could apply.

0240 RTE, Rate details

This segment is used to record a cost rate that may apply to this grouping.

0250 Segment Group 5: RFF-DTM-GIS-FTX

Some base data about how the information for this group of items was compiled. It will identify the standard method conventions adopted, the author of the data and it will also refer to any "request for quotation" messages that are to be read in conjunction .

0260 RFF, Reference

This segment will be used to specify a series of references, including the reference to a "Request for Quotation" message, standard method identity, the identity of the author of the data and the identity, if appropriate any software tool used during the preparation process.

0270 DTM, Date/time/period

The date of the Request for Quotation message that is to be processed in conjunction with this BoQ message.

0280 GIS, General indicator

An entry in this segment will acknowledge or note the existence of variations to the standard method rules referenced in the associated RFF.

0290 FTX, Free text

In the event of variations to the standard method rules this segment will provide any necessary narrative to explain the changes.

0300 Segment Group 6: CUX-DTM-FTX

Details of which currency rules apply to this group of items.

0310 CUX, Currencies

Recording details of the currency that applies to the group of items being defined.

0320 DTM, Date/time/period

This segment will be used to recorded any dates that are applicable to qualify the currency details recorded in CUX.

0330 FTX, Free text

Any narrative necessary to explain or qualify the currency information.

0340 Segment Group 7: ALC-RFF-DTM-RNG-FTX-SG8

A group of segments used to convey details of the price fluctuation calculations to be applied.

0350 ALC, Allowance or charge

A segment to identity whether the data recorded in this segment group represents an actualization or a revision figure.

0360 RFF, Reference

A segment providing a reference to the (usually standard) formula rules to be applied.

0370 DTM, Date/time/period

A segment to record the contract base or control date to be used in the formula.

0380 RNG, Range details

Where the formula makes reference to data within a range the details of the range will be identified in this segment.

0390 FTX, Free text

A segment to convey the actual formula and narrative relating to the formula. This will be used only in the exceptional case of a non-standard formula being used.

0400 Segment Group 8: PCD-RFF

A group of segments to specify the remaining components of the price fluctuation calculation.

0410 PCD, Percentage details

A segment to specify a percentage value to be used as a coefficient in conjunction with the reference given in the following RFF.

0420 RFF, Reference

A segment to specify the reference of a work section applicable to a set of calculation components.

0430 Segment Group 9: RCS-BII-FTX

This segment group is used to record, in textual form, any terms and conditions that are deemed to apply to part or all of the group of items.

0440 RCS, Requirements and conditions

The identity of the particular conditions that are to apply and a coded reference to denote whether this is to be added or changed etc.

0450 BII, Bill item identification

A structured index reference to identify to what range within the group of items the conditions apply.

0460 FTX, Free text

The narrative description of the condition or term identified by this segment group.

0470 Segment Group 10: ARD-MOA-FTX-SG11-SG12

This segment group is used to record any financial values that apply for a group of items. There are considerable number of different values and qualifiers that will apply.

0480 ARD, Amounts relationship details

A segment to record the qualifier to the financial value. This qualifier is in addition to the qualifier used within the following MOA segment.

0490 MOA, Monetary amount

A segment to record the value of the monetary amount being defined.

0500 FTX, Free text

Any narrative qualification necessary to complete the details about a financial value will be recorded in this segment.

0510 Segment Group 11: TAX-MOA-LOC

Where specific tax rules apply to the entire project or a grouping within the project they will be recorded in this segment group.

0520 TAX, Duty/tax/fee details

Where the financial value being described within segment group 10 is a taxation or duty value, details of the tax or duty will be recorded here.

0530 MOA, Monetary amount

A segment to specify the actual monetary amount of the tax or duty.

0540 LOC, Place/location identification

A segment to specify any location details used to qualify the tax details.

0550 Segment Group 12: ALC-ALI-SG13-SG14-SG15-SG16-SG17

Where it is necessary to express the components that contribute to a monetary value this segment group will be used.

0560 ALC, Allowance or charge

A segment identifying the charge or allowance and where necessary it's calculation sequence.

0570 ALI, Additional information

A segment indicating that the allowance or charge specified is subject to special conditions owing to origin, customs preference or commercial factors.

0580 Segment Group 13: QTY-RNG

Components of a financial value expressed in terms of quantities are recorded in this segment group.

0590 QTY, Quantity

Any quantity details used to define or make precise the monetary value are recorded in this segment.

0600 RNG, Range details

Details of the range that applies to the quantity components are expressed in this segment.

0610 Segment Group 14: PCD-RNG

Components of a financial value expressed in terms of a percentage are recorded in this segment group.

0620 PCD, Percentage details

This segment is used where the financial information is expressed as a percentage or a percentage is required for further qualification.

0630 RNG, Range details

Details of the range that applies to the percentage components are expressed in this segment.

0640 Segment Group 15: MOA-RNG

Any components of a monetary amount that are themselves expressed as monetary amounts are recorded in this segment group.

0650 MOA, Monetary amount

The monetary amount component is recorded in this segment.

0660 RNG, Range details

Details of the range that applies to the monetary amount components are expressed in this segment.

0670 Segment Group 16: RTE-RNG

Components of a financial value expressed in terms of a rate are recorded in this segment group.

0680 RTE, Rate details

Any rate details used to define or make precise the monetary value are recorded in this segment.

0690 RNG, Range details

Details of the range that applies to the rate components are expressed in this segment.

0700 Segment Group 17: TAX-MOA

Components of a financial value expressed in terms of a tax or duty are recorded in this segment group.

0710 TAX, Duty/tax/fee details

Any tax details used to define or make precise the monetary value are recorded in this segment.

0720 MOA, Monetary amount

A segment to specify the actual monetary amount of the tax or duty component.

0730 Segment Group 18: NAD-LOC-FII-FTX-SG19-SG20-SG21

Name and address information relating to Parties, Banks and Contacts are recorded in this segment group.

0740 NAD, Name and address

Company name and address that relate to this group of items and that have not been previously notified are recorded in this segment. Each name and address recorded is qualified by the use of the party qualifier 3035.

0750 LOC, Place/location identification

A segment used to record more specific location information of the party specified in the NAD segment, e.g. a location within a construction site.

0760 FII, Financial institution information

Bank details associated with these parties recorded in the preceding NAD segment are given here.

0770 FTX, Free text

This segment allows for any narrative that may need to accompany the name and address information about a company.

0780 Segment Group 19: RFF-DTM

This group of segments will record unique reference numbers by which the party will be known and referenced. This will ensure that each party is uniquely identified even if there is more than one party with a similar qualifier.

0790 RFF, Reference

Details of any unique referencing used within the project to identify the party. Not to be confused with the party qualifier in the NAD.

0800 DTM, Date/time/period

Date and time details that are used to qualify the party reference number are recorded in this segment.

0810 Segment Group 20: DOC-DTM

This segment group is used to identify documentation related specifically to the party being defined.

0820 DOC, Document/message details

The identity of the documentation is recorded in this segment.

0830 DTM, Date/time/period

Date details used to qualify the documentation are recorded in this segment.

0840 Segment Group 21: CTA-COM

The information about who to contact within each of the parties detailed in this segment group.

0850 CTA, Contact information

This segment will contain the identity of the individual, within a company, who is the contact point.

0860 COM, Communication contact

Here is recorded the telephone number etc. that the contact can be reached via.

UNS, Section control A service segment placed at the beginning of the detail section to avoid collision.

0870 Segment Group 22: BII-RCS-GIS-SG23-SG24-SG25-SG27-SG30-SG31-SG32-SG34

A group of segments recording all the details that apply to an item. There can be many items within a project, details of all items, regardless of where they appear in the BoQ will be recorded in this segment group.

0880 BII, Bill item identification

A segment used to convey a structured index number that uniquely identifies each item recorded for the project.

0890 RCS, Requirements and conditions

The action to be applied to this segment group data is recorded here.

0900 GIS, General indicator

Through a list of coded qualifiers this segment is used to define precisely various features about this item e.g.: - it will distinguish between standard, work or sub item types. - identify whether this item is of an agreed, disputed or provisional status. - a qualification of the type of rate that has been associated with this item. - identifying to what category this item resides.

0910 Segment Group 23: RFF-DTM

A group of segments recording additional reference information against an item of work.

0920 RFF, Reference

Where project documentation has been prepared in accordance with a Standard Methodology the item's reference to that Standard Method is recorded here. Also recorded here is the unique reference number assigned to a sub item. This reference would be used in conjunction with the item index no. in the BII of this segment group.

0930 DTM, Date/time/period

A segment to record a date for the Standard Method of Measurement reference.

0940 Segment Group 24: DIM-API-FTX

A group of segments which may be used where Segment Group 23 refers to a sub-item number. It would contain sets of dimension details to further describe the quantities.

0950 DIM, Dimensions

A segment used to record where applicable, the length, width and height for portions of work measured.

0960 API, Additional price information

A segment to record a multiplication factor called "Timesing" that applies to a set of dimensions.

0970 FTX, Free text

A segment to record an annotation for each set of dimensions.

0980 Segment Group 25: LIN-SG26

A group of segments to record descriptive text for items and headings for groupings of items.

0990 LIN, Line item

A segment to record a qualifier as to whether it is a description for an item or a heading for a group of items. This would also include a number identifying the level the description applies to, within a set of leveled headings.

1000 Segment Group 26: IMD-RFF-GIS

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.

1010 IMD, Item description

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. The distinction is explained in section 1.3 of this paper.

1020 RFF, Reference

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

1030 GIS, General indicator

A segment used to record up to five text change action codes per item description line.

1040 Segment Group 27: QTY-GIS-API-SG28

This segment group is used to record the complex range of quantity values and prices that apply to an item.

1050 QTY, Quantity

Many different quantity values can be applied to an item during it's execution. All of these quantities will be recorded in this segment.

1060 GIS, General indicator

This segment is used to provide the qualifiers that apply to the various quantities in the previous segment.

1070 API, Additional price information

Item quantities are frequently accompanied by some multiplicands. This API segment is used to record these.

1080 Segment Group 28: PRI-GIS-SG29

A group of segments to record a series of prices and monetary amounts relating to each QTY value.

1090 PRI, Price details

A segment to record up to three price values for each QTY value.

1100 GIS, General indicator

A segment to record up to three qualifiers for each price.

1110 Segment Group 29: ARD-MOA

A group of segments to record the monetary amounts , currency, tax details resulting from the multiplication of QTY and PRI values.

1120 ARD, Amounts relationship details

A segment to qualify the monetary amount as to it's purpose in the business exchange.

1130 MOA, Monetary amount

A segment to record the value and currency of the monetary amount.

1140 Segment Group 30: TAX-MOA-LOC

A group of segments in which is detailed taxation information, which applies to the item . There are often several different types of tax which need to be applied.

1150 TAX, Duty/tax/fee details

Details of the taxation to be applied is recorded here.

1160 MOA, Monetary amount

A segment to record the value and currency of the monetary amount.

1170 LOC, Place/location identification

A segment to specify location codes relating to the tax details recorded in this segment group.

1180 Segment Group 31: BII-GIS

Where it is necessary to record a relationship about the current item and it's association with another item, this segment group will be used.

1190 BII, Bill item identification

Record here the structured index number of the other item to which the current item relates.

1200 GIS, General indicator

This is the segment where a coded reference describing the item relationship is recorded.

1210 Segment Group 32: ALC-RFF-DTM-RNG-FTX-SG33

A group of segments used to convey details of the price fluctuation calculations to be applied to the item.

1220 ALC, Allowance or charge

A segment to identity whether the data recorded in this segment group represents an actualization or a revision figure.

1230 RFF, Reference

A segment providing a reference to the (usually standard) formula rules to be applied.

1240 DTM, Date/time/period

A segment to record the contract base or control date to be used in the formula.

1250 RNG, Range details

Where the formula makes reference to data within a range the details of the range will be identified in this segment.

1260 FTX, Free text

A segment to convey the actual formula and narrative relating to the formula . This will be used only in the exceptional case of a non- standard formula being used.

1270 Segment Group 33: PCD-RFF

A group of segments to specify the remaining components of the price fluctuation calculation.

1280 PCD, Percentage details

A segment to specify a percentage value to be used as a coefficient in conjunction with the reference given in the following RFF.

1290 RFF, Reference

A segment to specify the reference of a work section applicable to a set of calculation components.

1300 Segment Group 34: IMD-QTY-MOA-PRI

A segment group to record where necessary alternative index information for an item. The validity of an alternative index would be defined in the Segment Group 3 IMD.

1310 IMD, Item description

A segment used to record an alternative index description (pre-viously defined in Segment Group 3 IMD), that relates to this item.

1320 QTY, Quantity

A segment to record the quantity and measurement unit that relates to the coded entry for the item.

1330 MOA, Monetary amount

A segment to record the currency and value associated with the item.

1340 PRI, Price details

A segment to record the monetary rate of the code associated with the item.

1350 CNT, Control total

Various control total checks may be taken and the resultant values would be recorded in this segment. Typically these checks will be counts of quantity and monetary values that apply to the entire message.

1360 UNT, Message trailer

A service segment ending a message, giving the total numbers of segments in the message and the control reference number of the message.