Free tool · GAEB viewer

P83 file: a GAEB 2000 request for quotation

Q: What is a P83 file?

A P83 is a request for quotation (phase 83) in GAEB DA 2000, the keyword-based format that came between GAEB 90 and GAEB DA XML. Values sit between [Key] and [end], blocks between #begin[…] and #end[…], and long texts are often RTF.

Q: How do I open a P83 file?

Drop it into the GAEB viewer on this page. It reads the keywords, turns the RTF long texts into formatted text and shows the bill of quantities in your browser. A text editor shows the raw keywords and RTF code.

Q: What is the difference between P83 and X83?

Both are phase 83, a request for quotation with texts and quantities and no prices. The P83 is written in the GAEB DA 2000 keyword format, the X83 in GAEB DA XML, the current standard.

Q: How do I convert a P83 to X83 or Excel?

For X83, open the P83 in the free GAEB converter at mercura.ai/tools/gaeb-converter; it writes GAEB DA XML 3.3 in your browser. AVA software can do it too. For Excel, CSV or PDF, open the P83 in the viewer and export it there.

Q: Is GAEB DA 2000 still supported?

Not by the GAEB: it no longer supports the older formats, and the current standard is GAEB DA XML, version 3.3. P83 files are still in use, and the viewer opens them.

Q: What are P81 and P84 files?

The same GAEB DA 2000 format in other phases: a P81 is a description of works, a P84 a bid with prices and a P86 the contract award. The viewer opens P81 to P86.

A P83 is a request for quotation in GAEB DA 2000, the keyword-based format between GAEB 90 and GAEB DA XML. It holds the same bill of quantities as an X83, with long texts often stored as RTF. Drop yours into the viewer to read it or export it to Excel; below, the format is explained block by block.

GAEB viewer

Drop a GAEB file here

orGAEB DA XML, GAEB 2000 and GAEB 90 · X81–⁠X86, P81–⁠P86, D81–⁠D86 · up to 50 MBYour file never leaves your computer.

File contents

What is in a P83

First what a P83 holds, then the start of a P83 and two of its items. Blocks run from #begin[…] to #end[…], values from [Key] to [end].

What the file holds

Content	In the file	Note
Project and LV	Yes	Blocks GAEBInfo, PrjInfo, Vergabe and LVInfo.
Sections and item numbers (OZ)	Yes	LVGlied blocks set the levels, LVBereich blocks hold the sections.
Short and long texts	Yes	[Kurztext] and [Langtext], long texts often as RTF.
Quantities and units	Yes	[Menge] with a decimal comma, [ME] for the unit.
Item types	Yes	Keys such as [Bedarf] for contingency items.
Unit prices and totals	No	The prices come back in the bid.
File format	Keywords	#begin[…] and #end[…] around blocks, [Key]…[end] around values, character set ANSI (Windows).

The sample, explained

Sample	What it says
P83, start of the file
`#begin[GAEB] #begin[GAEBInfo] [Version]1.2[end] [VersMon]3[end] [VersJahr]2002[end] [Datum]27.10.2026[end] [ProgSystem]Mercura[end] [ProgName]GAEB-Viewer Beispieldatei[end] [Zeichensatz]ANSI[end] #end[GAEBInfo]`	The file opens with #begin[GAEB]. GAEBInfo names the version of GAEB 2000, the program and the character set.
`#begin[PrjInfo] [Name]MUS-2026-017[end] [Bez]Neubau Bürogebäude Musterstraße 12[end] [Wae]EUR[end] [WaeBez]Euro[end] #end[PrjInfo]`	Project number, name and currency.
`#begin[Vergabe] [DP]83[end]`	The award block (Vergabe) with [DP]83: request for quotation.
`#begin[LV] #begin[LVInfo] [Name]LV 05[end] [Bez]Sanitär- und Heizungsinstallation[end] [Datum]27.10.2026[end] [KurzLang]1[end]`	The LV: name, description and date.
`#begin[LVGlied] [Typ]LVStufe[end] [Bez]Gewerk[end] [Laenge]2[end] #end[LVGlied] #begin[LVGlied] [Typ]LVStufe[end] [Bez]Titel[end] [Laenge]2[end] #end[LVGlied] #begin[LVGlied] [Typ]Position[end] [Laenge]4[end] #end[LVGlied] #begin[LVGlied] [Typ]Index[end] [Laenge]1[end] #end[LVGlied] #end[LVInfo]`	Four LVGlied blocks: Gewerk and Titel with two digits each, a four-digit item number and a one-character index.
`#begin[LVBereich] [OZ]01[end] [Bez]Sanitärinstallation[end] #begin[LVBereich] [OZ]0101[end] [Bez]Abwasserleitungen[end]`	Sections 01 and 01.01 (LVBereich).
Two items
`#begin[Position] [OZ]01010010[end] [Menge]48,500[end] [ME]m[end]`	Item 01010010 (01.01.0010) with quantity 48,500 and unit m.
`#begin[Beschreibung] [Kurztext]HT-Rohr DN 110[end] [Langtext]{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss Arial;}}\f0\fs20 {\b HT-Abwasserrohr DN 110} aus Polypropylen nach DIN EN 1451, schwer entflammbar, einschlie\'dflich Rohrschellen mit Schallschutzeinlage.\par Leistung umfasst:\par - Liefern und Verlegen\par - Befestigen im Abstand <= 1,0 m\par - Anschluss an bauseitige Grundleitung\par}[end] #end[Beschreibung] #end[Position]`	Short text as plain text, long text as RTF: {\b …} is bold, \par a paragraph.
`#begin[Position] [OZ]01010030[end] [Menge]4,000[end] [ME]St[end] [Bedarf]E[end]`	Item 01.01.0030 with [Bedarf]E: a contingency item without total.
`#begin[Beschreibung] [Kurztext]Revisionsöffnung 300 x 300 mm[end] [Langtext]{\rtf1\ansi\deff0{\fonttbl{\f0\fswiss Arial;}}\f0\fs20 Revisions\'f6ffnung in Schachtwand, Gr\'f6\'dfe 300 x 300 mm, mit Rahmen und Deckel, {\i nur auf Anordnung der Bauleitung}.\par}[end] #end[Beschreibung] #end[Position]`	Its texts.
`#end[LV] #end[Vergabe] #end[GAEB]`	The end of the LV, the award block and the file.

Tender phase

Where the P83 fits in a tender

The 83 is the request for quotation, the P is the format GAEB DA 2000. It uses the phase numbers 81 to 86, like the other formats.

Phase	Name	What it is
80	Universal LV data	Any LV data, not tied to a step of the tender.
81	Leistungsbeschreibung (description of works)	The LV with its texts, as the planner hands it to the client. Usually without prices.
82	Kostenanschlag (cost estimate)	The LV with estimated prices, for award decisions and cost control.
83	Angebotsaufforderung (request for quotation) this file	The LV without prices, sent to the companies invited to bid.
84	Angebotsabgabe (bid)	The bidder's prices, text additions and free quantities, sent back to the client.
85	Nebenangebot (alternative bid)	A bid with an alternative way of execution, if the client allows it.
86	Auftragserteilung (contract award)	The award to the most economical bid. With it, the construction contract is concluded.
87	Auftragsbestätigung (order confirmation)	The contractor confirms the order.
89	Rechnung (invoice)	The invoice with items and quantities, which can be backed by quantity take-offs.
93–97	Trade (Handel)	Between contractor and manufacturer or wholesaler: price request (93), price offer (94), order (96), order confirmation (97).

Three generations of the format

Format	Files	Status
GAEB DA XML	.X80 to .X89, plus other phases	The current standard, version 3.3 (edition 2023-01).
GAEB DA 2000 this file	.P81 to .P86	Keyword format. No longer supported by the GAEB.
GAEB 90	.D81 to .D86	Line format with fixed columns. No longer supported by the GAEB.

Open and convert

How to open and convert a P83

These are the ways to read, export and convert a P83.

Task	How
Read it now	Drop the file into the viewer at the top of this page. It opens X8x, P8x and D8x files in your browser; the file is not uploaded.
Excel or CSV	In the viewer, choose Excel (.xlsx) or CSV: one row per item with OZ, short and long text, quantity, unit and prices.
PDF	Open the print view in the viewer and save it as PDF.
Work with it	AVA or estimating software with a GAEB interface. The BVBS certifies such interfaces for GAEB DA XML 3.1 to 3.3.
Convert to X83	The GAEB converter turns a P83 into an X83 (GAEB DA XML 3.3) in your browser and lists anything it cannot carry over.
Text editor	A P83 is plain text with [Key] markers. Long texts are often RTF code, which an editor shows raw.

PDF and Excel tenders

Not every tender comes as GAEB.

Many bills of quantities still arrive as PDF, scan or Excel, and someone types them in. Mercura reads tenders in GAEB and PDF and suggests matching articles from your catalogue for every item, so a PDF tender is handled like an X83.

FAQ

Questions about GAEB files.

A P83 is a request for quotation (phase 83) in GAEB DA 2000, the keyword-based format that came between GAEB 90 and GAEB DA XML. Values sit between [Key] and [end], blocks between #begin[…] and #end[…], and long texts are often RTF.

Drop it into the GAEB viewer on this page. It reads the keywords, turns the RTF long texts into formatted text and shows the bill of quantities in your browser. A text editor shows the raw keywords and RTF code.

Both are phase 83, a request for quotation with texts and quantities and no prices. The P83 is written in the GAEB DA 2000 keyword format, the X83 in GAEB DA XML, the current standard.

For X83, open the P83 in the free GAEB converter at mercura.ai/tools/gaeb-converter; it writes GAEB DA XML 3.3 in your browser. AVA software can do it too. For Excel, CSV or PDF, open the P83 in the viewer and export it there.

Not by the GAEB: it no longer supports the older formats, and the current standard is GAEB DA XML, version 3.3. P83 files are still in use, and the viewer opens them.

The same GAEB DA 2000 format in other phases: a P81 is a description of works, a P84 a bid with prices and a P86 the contract award. The viewer opens P81 to P86.

GAEB formats

More GAEB formats, explained.

X83

Request for quotation

The bill of quantities without prices that bidders receive.

GAEB formats

X, P and D, phases 80 to 89

All formats and phases at a glance.

D83

Request for quotation, GAEB 90

The same request in the GAEB 90 line format.

X84

Bid

The bidder's prices for every item number.

X81

Description of works

The description of works from the planner.

Open any other GAEB file in the GAEB viewer →

Book a demo

See Mercura on

your own tenders.

Bring a real GAEB file. We’ll show you how Mercura reads it and matches every item to your catalog.

Book a demo

See Mercura on

your own tenders.

Bring a real GAEB file. We’ll show you how Mercura reads it and matches every item to your catalog.

Book a demo

See Mercura on

your own tenders.

Bring a real GAEB file. We’ll show you how Mercura reads it and matches every item to your catalog.

Book a demo