GAEB files are standardized exchange files for bills of quantities and proposals in German construction — GAEB stands for 'Gemeinsamer Ausschuss Elektronik im Bauwesen' (Joint Committee for Electronics in Construction), the body behind the standard. Anyone processing public tenders in the construction sector cannot avoid this format. Yet there's often uncertainty: What do the different format numbers mean? How do you read a GAEB file correctly? And what software do you need? This guide answers the most important questions.
What is GAEB?
GAEB stands for 'Gemeinsamer Ausschuss Elektronik im Bauwesen' (Joint Committee for Electronics in Construction). It's a standardized data exchange format for bills of quantities and proposals in construction. The standard was developed to unify electronic data exchange between clients, planners, and contractors. For over 30 years, GAEB has been the de facto standard for construction procurement in Germany.
The Most Important GAEB Formats at a Glance
GAEB distinguishes different exchange phases, identified by format numbers: X81 (bill of quantities) contains the unpriced BoQ for handover. X82 (cost quotation) is a priced BoQ used before the formal bidding phase. X83 (bid request) is the unpriced BoQ the contracting authority issues to bidders. X84 (bid submission) is your priced response returned to the authority. X85 (side offer) carries alternative proposals in addition to the main bid. X86 (contract award) transmits the commissioning. For bidders, X83 and X84 are the most relevant formats.
Structure of a GAEB X81 File
An X81 file is built in XML format and contains hierarchically structured information: header data with project information, one or more service areas (BoQCtgy), and line items (LVItem) within them containing quantities, units, and descriptions. Each line item has a unique reference number, a quantity with unit, and a more or less detailed service description.
Common Problems in GAEB Processing
Practice repeatedly shows typical stumbling blocks: encoding issues due to incorrect character sets (GAEB requires UTF-8), missing or invalid mandatory fields, incompatibilities between different GAEB versions (DA81 vs. GAEB XML 3.2), and rounding differences in quantities and prices. Many of these problems can be detected early through validation tools.
Software for GAEB Processing
There are various solutions for working with GAEB files: Specialized AVA software like ORCA, California, or RIB iTWO offers comprehensive functions for large construction companies. For smaller companies, there are also lightweight solutions and online tools. It's important that the chosen software supports both import and export of the required GAEB versions.
GAEB and AI: New Possibilities
Modern AI solutions can significantly accelerate GAEB processing. Automatic analysis of service texts, intelligent matching with your own product catalog, and detection of risks or ambiguities in tender documents are just a few examples. The potential of automation becomes especially apparent with extensive bills of quantities containing hundreds of line items.
Conclusion
GAEB files may seem complex at first glance, but they follow a clear logic. Anyone who understands the basic structure and works with suitable software can handle the exchange efficiently. For mid-sized construction companies, investing in good GAEB tools pays off – it saves time and reduces errors in proposal processing.