Win a GAEB tender, from the LV to the Angebot
Read the client's GAEB X83 tender straight into a bill instead of retyping it, price every position, check the total, and hand the offer back as a GAEB X84 Angebotsabgabe.
仕組みをステップごとに
プラットフォーム全体で7ステップ - 各ステップで何をするか、そしてなぜ重要か。
File the tender documents as received
文書Save the GAEB X83 and the rest of the Vergabeunterlagen into the project files exactly as the client sent them, with the date they arrived and the Angebotsfrist recorded alongside.
理由: Tenders get corrected and reissued during the bidding period. Keeping the file you actually priced on record is what lets you show, weeks later, which version your offer answers.
Import the X83 as a new LV
GAEB交換Open the Import tab, drop the X83 in, check the preview of the parsed positions, then import them into a new bill named after the tender. The Ordnungszahl, the unit, the quantity and the long text of every position arrive unchanged.
理由: This is the step that removes the retyping. Keying several hundred positions by hand is exactly where a transposed quantity or a dropped position turns into a loss you only notice on site.
Settle the rate basis you price from
単価データベースIn the cost database, decide which rates this offer is built on, whether that is your own recorded costs or a maintained catalog, and add the items the LV asks for that you do not carry a price for yet.
理由: A rate whose origin you can name is a rate you can defend if the client asks you to explain it. Fixing the basis up front also stops the same work being priced two different ways inside one offer.
Price every position and read the Langtext
内訳書Work down the bill and put a unit price on every position, reading the long text as you go so a duty buried in a description is priced rather than discovered later. The bill totals each position and rolls up the Angebotssumme as you type.
理由: The long text is where the risk sits: a wording that quietly hands you the substrate, the disposal or the working hours. Catching it while you price costs minutes, catching it on site costs the margin.
Check the offer before it leaves the house
検証Run validation over the priced bill and clear what it finds: a position still standing at zero, a quantity or unit that drifted away from the LV, a structure rule the return file has to honour. Then check the Angebotssumme for plausibility against a job of this size.
理由: One unpriced position can take the whole offer out of the evaluation, and a total that is out by a decimal place is worse than losing the job. These five minutes are the cheapest insurance in the entire tender.
Export the Angebotsabgabe as X84
GAEB交換Switch to the Export tab, pick the priced bill and choose the X84 format. What you get back is the Angebotsabgabe: your Bieter details, a unit price and a total on each position, and the offer totals, all on the same Ordnungszahl you were sent.
理由: X84 is the exchange phase the client's software expects an offer to arrive in. Returning the numbering they issued means your prices load straight into their Preisspiegel instead of being retyped or set aside.
Submit the Angebot and log what went out
送付Assemble the X84 with the signed tender forms and any Nebenangebot the tender allows into one submission, issue it before the Angebotsfrist, and keep the record of what went out, to whom and when.
理由: A strong price inside an incomplete or late submission is not a price, it is an exclusion. The dated record of what you sent is also the starting point for any Nachtrag discussion once you win.
このプレイブックのモジュール
プラットフォーム 184 モジュール中 6 個
