Skip to content
Art ConstructionTenders
Practical guide

Norm SIA 451: .01s, .crbx, and .ifcbx Files for Quote Data Exchange

Technical guide to quote data exchange in Switzerland: master .01s, .crbx, and .ifcbx files under norm SIA 451 to safeguard your tender submissions.

Table of contents
The 3 Major Site Risks
  1. Financial / Margin: Conversion error or decimal truncation during digital quote import, causing a non-negotiable price discrepancy under the lump-sum regime of art. 373 CO (a net loss illustrating an order of magnitude of 3 % to 8 % of the total awarded amount).
  2. Legal / Joint Body / SUVA: Alteration of CAN standardized item descriptions or unauthorized modification of variables during tender file export, exposing the firm to the risk of exclusion from the procedure by the contracting authority under art. 44 LMP in case of formal defects or failure to comply with call for tenders requirements.
  3. Administrative / Handover: Data schema incompatibility between the contractor's software and the site management platform, preventing bid evaluation under art. 38 LMP and delaying the integration of quantity surveys for establishing contractual progress payments defined by norm SIA 118.

In the Swiss construction sector, rigorous transmission of call for tenders data constitutes a decisive operational prerequisite for company managers, estimators, and tender managers. Norm SIA 451 governs the standardized electronic exchange of work descriptions and bills of quantities between professional design consultants and tendering contractors. This technical standardization ensures that each priced item corresponds strictly to the work defined by the designer, while limiting manual re-entry within contractor estimation tools.

The gradual transition from traditional .01s text formats to contemporary .crbx XML schemas and .ifcbx open models is profoundly transforming bid calculation methods in French-speaking Switzerland. Using a compliant structure prevents any dispute regarding bid consistency upon concluding a contract for work governed by art. 363 CO. Understanding the internal mechanics of these software extensions enables technical offices to secure their unit prices, automate exchanges with cantonal platforms, and prevent tender rejections due to formal defects.

Architecture of exchange formats: from the .01s text file to crbx and ifcbx containers

In Switzerland, digital data exchange for preparing bids relies on the strict application of norm SIA 451. This technical standard governs data structuring between designers' planning software and contractors' calculation tools. The legacy structure relies on structured text files carrying the .01s extension for the initial call for tenders phase, or .02s for returning the priced bid by the prospective contractor. This sequential mechanism ensures that the item ordering of the Standard Item Catalogue (CAN) remains inviolable.

Technological evolution promoted by the Swiss Research Centre for Rationalization in Building and Civil Engineering (CRB) introduces modern compressed digital containers, specifically the crbx format and the ifcbx BIM container. The crbx file bundles, within a secure standardized archive, the entire bill of quantities structured by Construction Cost Code (CFC) chapters, standardized item texts, special tender conditions, and project metadata. This structure eliminates the character set incompatibility risks seen with legacy text files during cross-platform transfers.

The ifcbx format extends this logic to digital building models by integrating OpenBIM open data structures. It links measured quantities from three-dimensional objects directly to CAN quote description items. Within public procurement governed by the LMP, using these unified exchange formats ensures equal treatment of tenderers as prescribed in art. 2 LMP. The digital integrity of the transmitted file is essential: no manual editing of the internal syntax is tolerated, or the bid will be rendered technically inadmissible during automated compliance checks.

Technical specifications and comparative analysis of exchange formats

Selecting and handling these containers depends on the digital maturity of the stakeholders, specifications requirements, and whether or not a three-dimensional building model is integrated. The following table summarizes the functional and normative properties of exchange formats compliant with norm SIA 451.

Assessment criterion.01s / .02s text formatCRBX container (.crbx)IFCBX hybrid format (.ifcbx)
Underlying structureASCII / ANSI text file with fixed columns and delimitersCompressed archive containing standardized XML filesArchive combining OpenBIM IFC schema and CRB metadata
Handling supplementary textLimited, frequent risk of truncating long stringsComplete, native support for complex formattingComplete, direct interfacing with 3D object properties
Data integrity checkBasic checksums on priced itemsStrict XML schema validation and software signaturesDual consistency between BIM geometry and CAN items
Swiss software interoperabilityUniversal across tools certified under norm SIA 451Widespread across current calculation suitesRolling out across BIM-compatible solutions
Quantity survey integrationFixed gross quantities per tender itemDetailed quantities structured by CFC and elementsBidirectional link between geometric takeoff and quote

During bid evaluation under art. 38 LMP, the contracting authority verifies compliance with formal requirements and corrects obvious calculation errors ex officio (para. 1). Using a format compliant with norm SIA 451 limits arithmetic discrepancies, because unit price multipliers and chapter totals are recalculated deterministically by the digital evaluation engine.

Pricing rules, item variables, and frequent pitfalls

In a call for tenders drafted under the CAN, the tendering contractor does not have complete freedom of input. Standardized items contain locked, non-editable descriptions and variable lines identified by specific tags. When pricing within a .01s or crbx file, the estimator must exclusively complete the fields intended for the unit price, the total item amount, and any product specifications required by the designer.

A common mistake is modifying the text of a CAN item to match the properties of an alternative material without going through the formal variant bid procedure. Such an alteration in the data structure causes the file to be rejected by bid opening software. Under art. 44 LMP, the contracting authority may exclude a tenderer notably if they submit an offer with significant formal defects. Similarly, if the estimator omits a price on a locked item without justification, this omission can be deemed an incomplete bid.

On a contractual level, once the contract has been awarded and the contract for work concluded under art. 363 CO, the imported amounts determine the financial commitment. If the agreement stipulates a lump sum within the meaning of art. 373 CO, the contractor executes the work for the agreed amount and cannot claim any increase, even if the work required more labor or expenses. An input error resulting from a faulty conversion of a .01s file causes a direct financial loss for the company, in the range of 45 000,00 CHF to 120 000,00 CHF on a structural work package, with no possibility of retroactive adjustment.

The overall evaluation of the bid is based on the award criteria set out in the tender documents. Under art. 29 LMP, the contracting authority evaluates bids based on performance-related criteria, including price, quality, deadlines, technical value, cost-effectiveness, or bid plausibility (para. 3). If the overall price appears out of touch with reality due to a data export anomaly, art. 38 LMP requires the contracting authority, upon receiving a bid with an abnormally low total price, to request relevant clarification from the tenderer to ensure eligibility criteria are met and call for tenders requirements were understood (para. 3).

Illustrative practical cases (typical scenarios on Swiss construction sites)

The figures presented in the following scenarios are illustrative examples developed to analyze digital data exchange mechanisms.

Scenario 1: Tender for a school complex in the canton of Vaud

A mid-sized general contractor with 45 employees responds to a public call for tenders for the construction of a three-story school building in Lausanne. The tender dossier includes several chapters of CFC 211 (Masonry and reinforced concrete), transmitted as a .01s file generated under norm SIA 451.

The estimator exports the quote to their internal software without checking the character set or decimal separator format. When exporting the response file in .02s format, the decimals for unit prices on three slab formwork items are truncated. The total package amount drops from 1 850 400,00 CHF to 1 732 200,00 CHF, representing a discrepancy of 118 200,00 CHF against the contractor. The bid is awarded based on the erroneous amount. Under art. 373 CO, the contractor is bound by this lump sum, drastically eroding the construction site's gross margin right from the initial award phase.

Scenario 2: Administrative building renovation in the Canton of Geneva

An SME specializing in MEP finishing work (18 employees) tenders for the overhaul of plumbing systems in an administrative building in Geneva. The call for tenders is delivered in the crbx container format, incorporating CAN 381. The specifications require a strictly paperless submission via the cantonal public procurement platform.

The company uses software certified for norm SIA 451, ensuring validation schema compliance. The tender manager meticulously completes the locked variables regarding pipe classes and specific fixtures. The final bid is priced at 485 250,65 CHF including all taxes (Swiss VAT of 8,1 % included). During bid opening and technical review, the crbx file is instantly validated by the site management algorithms, eliminating any risk of formal rejection under art. 44 LMP and ensuring full compliance with procedural requirements.

Calls for tenders: free tools

Direct public procurement tenders, AIMP thresholds by canton, converting SIA 451 to Excel, quantity takeoff from an IFC model.

View tendering tools

Frequently asked questions

How do you check the validity of a .01s file before submitting a financial bid?

The estimator must open the file in an editor compliant with norm SIA 451 to verify the integrity of CAN item lines. Under art. 38 LMP, the contracting authority corrects obvious calculation errors but may dismiss a corrupted bid of 150 000,00 CHF for an irremediable formal defect.

What is the fundamental difference between the .crbx format and the legacy .01s file?

The .01s format relies on a sequential text structure stemming from norm SIA 451, whereas the .crbx format utilizes a modern XML hierarchy validated by CRB. It secures CAN item descriptions, eliminating text truncation risks during a cantonal public tender.

Can a tenderer modify the quantities set in an .ifcbx bill of quantities?

No. Modifying quantities derived from the digital model on an itemized basis without instruction from site management constitutes a prohibited alteration of the call for tenders. Under art. 44 LMP, arbitrarily altering a quantity survey for an 85 000,00 CHF trade package exposes the tendering firm to exclusion from the procedure.

What risks does a contractor run if a unit price is omitted in the returned .01s export?

Omitting a unit price on a CAN item can be treated as an incomplete bid. In accordance with art. 38 LMP, the contracting authority requests technical clarification, but rejects the bid if the omission alters the overall amount without respecting equal treatment among bidders.

How do contractor open items align with the SIA 451 digital structure?

Open items added by the bidder must strictly follow the CAN numbering mask defined by the designer. Any field overflow or non-compliant description prevents automated import by the awarding authority and invalidates the digital bill of quantities during the formal tender compliance check.

How to resolve an import error linked to the 8,1 % Swiss VAT in a .crbx file?

The .crbx file applies the statutory Swiss rate of 8,1 % to the summary recap. The contractor must align its software tables to this exact rate; a rounding difference of 0,05 CHF on the final account blocks the digital integration of the quote into the tender platform.

Mastering digital exchanges in Swiss construction procurement

The transition to .crbx and .ifcbx files reinforces the rigorous standards imposed by SIA 451 and official construction catalogues. A precise understanding of data structures protects bidders from formal defects when submitting tenders on cantonal procurement platforms. To learn more about Swiss building standards, explore our specialised guides:

Art Construction is an independent company: it is not affiliated with the SIA, CRB, SUVA, or KBOB. Referenced norms and standards point to publications from these bodies; only official versions are legally binding.