Section 8: BCIS XML schema for elemental analyses

BCIS has developed an XML schema for elemental analyses to encourage the use and exchange of analyses. The schema is designed to enable analyses to be reliably transferred between applications and to provide a neutral format for analysis data.

XML is widely used within IT as a format for the exchange of information and standard software tools are available to help process XML files. XML itself is only a set of rules for encoding information: the XML schema is the definition of what data can be stored in a particular subject area and how it is ordered. BCIS developed the schema for elemental analyses in 2001 and issued a revised version in 2010.

An important function is to avoid ambiguity. This is most easily illustrated with dates, which can be represented in a variety of formats – many of which are ambiguous, for example, '01/10/18' does this mean January or October, 1918 or 2018? The schema defines how dates must be represented.

The schema does not define the elements (that is the role of the SFCA), so the BCIS schema could be used with other element definitions.

Context is vital when using analyses and the schema includes the background information and notes (areas, dates, specifications, contractual arrangements, etc.) that would normally come with an analysis.

Various applications can read and/or write analyses in the BCIS analyses XML format. BCIS Online and the equivalent BCIS SOAP services deliver analyses in this format. Various leading third party budget estimating/cost planning systems can read analysis XML files, including CATO and RIPAC. The equivalent BQ packages can also export analyses in this format and BCIS has developed an application that can create and edit analyses stored as XML files. The schema itself is in the public domain so that others can develop interfaces.

BCIS relies on subscribers submitting analyses and would like to see more data submitted electronically to save time and costs, and help further improve quality. To this end, the BCIS Analysis XML Writer is available for free download. The application will allow you to create a BCIS Analyses XML file and edit such files to add or amend details. The application includes extensive checks so that common problems can be identified and corrected immediately.

An analyses XML file may contain 1 or several analyses. BCIS recommended practice is that each file should contain all analyses associated with 1 project (‘complex contacts’), and that separate projects are held in separate XML files, but circumstances will vary and other practices will be appropriate at times.

XML files can be read as text files, but this is by no means easy. To make the BCIS Analyses XML files more useful and flexible, there is a style sheet which, when referenced in an appropriate web browser, will format the analysis in a layout suitable for display on the screen or printing.

Analyses can be prepared in many different ways depending on the procurement route as well as the software employed. Here are a few scenarios:

‘Traditional procurement’ (BQ or priced schedule), prepared using a BQ package that supports XML export:

• items coded elementally when measure;
• enter rates from tender when received;
• BQ package generates analysis and exports as XML file;
• BCIS Analysis XML Writer used to edit file and add additional information (specifications, element unit quantities, tender list, etc. where not supported by BQ package).

Design and Build Contract Sum Analysis:

• provided that the contract sum analysis was required in elemental form, the tender documents contain all that is needed;
• the BCIS Analysis XML writer can be used to create a new XML file and details added direct from the documents.

‘Traditional procurement’ (BQ or priced schedule), prepared using a system that does not support XML export or where items were not coded elementally when measured:

• use the Excel template to abstract the items into elements;
• export the data as XML; and
• then use the BCIS Analysis XML Writer to add additional information (areas, specifications, element unit quantities, tender list, etc.).

At the end of each of these processes you will have an analysis in XML format that contains all the information needed to make use of the data in a format that can be imported into leading cost planning applications. It is also ready to be submitted to BCIS for publication.