תרחישים / אומדן ותמחור
אומדן ותמחור

תמחור כתב כמויות הונגרי לפי נורמה ו-rezsióradíj

בנו את ה-tételes költségvetés ההונגרי כפי שקוראים אותו: נורמה מאחורי כל tétel, ה-anyag וה-díj מוצגים בנפרד, ה-díj נבנה משעות הנורמה ומ-rezsióradíj מוצהר, ו-főösszesítő לפי munkanem שהלקוח יכול לבדוק שורה אחר שורה.

7 שלבים13 דק׳קבלן ראשיקבלן משנה מתמחהייעוץ עלויות / כמויות

איך זה עובד, שלב אחר שלב

7 שלבים לאורך הפלטפורמה - מה עושים בכל שלב ולמה זה חשוב.

1

Take in the tetel list and group it by munkanem

כתב כמויות

Bring the tetel list in as the bill you will price, keeping the numbering, the unit and the quantity as issued, and group it by munkanem so each trade section can be totalled and read on its own. Flag the work the drawings show and the list does not, rather than silently pricing it inside a neighbouring tetel.

למה: Government Decree 191/2009 (IX. 15.), the Epkiv., requires the kivitelezesi szerzodes to be in writing and lists what it carries, the unpriced itemised bill among them. So this list is not working material, it is the annex the contract will be measured against for the whole job. Work you absorb into another line now is work you cannot bill separately later, and a tetel you add without saying so reads as a different offer from everyone else's.

נכנסArazatlan koltsegvetesi kiirasDrawings and specificationיוצאTetel list by munkanemMissing tetel flagged
2

Put a norm behind every tetel

נורמות ייצור

For each tetel record the labour time and the material consumption per unit that the price assumes, and name where that norm came from: a published norm collection with its edition year, or your own measured output from a comparable job. Adjust it for the conditions this site imposes rather than editing the rate at the end to make the total look right.

למה: A norm with a name and a year can be argued with. A rate that arrived from nowhere can only be believed or disbelieved. That difference decides how a variation is settled, how a claim for extra work is read, and whether a justification for a low price is accepted, and it costs nothing to record while you are already looking at the tetel.

נכנסTetel and its unitMethod and site conditionsיוצאNorm hours per unitMaterial consumption per unit
3

Build the rezsioradij you will actually use

תעריפי עבודה

Build the hourly rate from its parts: gross wage, the employer contributions on it, paid non-working time, small plant and hand tools, site running costs and the share of company overhead the job carries. Keep the build-up attached to the rate so anyone can see which of those parts is doing the work.

למה: The rezsioradij is the single number that decides whether a Hungarian bid is profitable, and it is the number most often carried over from last year without being rebuilt. It is also not a free choice. A minimum construction rezsioradij is set by ministerial decree for the year, and on public work an offer calculated below it can be found invalid, so a rate under the minimum has to be a decision somebody made rather than a number that came out of a spreadsheet.

נכנסWages and contributionsSite and company overheadיוצאRezsioradij for the jobRate build-up on record
4

Assemble each tetel as anyag plus dij

מכלולים

Build the unit price as an assembly rather than typing it. The dij is the norm hours multiplied by the rezsioradij, the anyag is the consumption multiplied by the material price including waste and delivery, and hired plant sits on its own line rather than being smeared through the hourly rate.

למה: Hungarian bills are read with the anyag and the dij apart, and the two move for different reasons: material prices move with the market and the dij moves with wages and productivity. A single blended number hides which one moved, which is exactly what you need to show when a client asks why a rate has changed since last year.

נכנסNorm hours and materialsRezsioradij and material pricesיוצאAnyag side of the unit priceDij side of the unit price
5

Add the markups where they can be seen

כתב כמויות

In the bill's Markups & Overheads panel, apply the markups as their own layer over the direct cost, so the direct cost stays readable underneath. Decide once whether overhead already sits inside the rezsioradij or on top of the tetel, and apply that decision everywhere rather than per section.

למה: Overhead counted twice, once inside the hourly rate and once as a percentage on the total, is the commonest quiet error in an itemised bill and it is invisible in the total. Keeping the layer separate makes it a thing you can look at, and it also makes a discount a decision about margin rather than an unexplained edit to a unit rate.

נכנסDirect cost per tetelMarkup policyיוצאMarkups appliedOffer price per tetel
6

Check the bill against the list you were given

אימות

Run validation over the priced bill: nothing left at zero, no unit or quantity drifted from the kiiras, no tetel priced far outside the band its neighbours sit in, and every rate carrying the norm and the rate basis it claims.

למה: An outlier is not automatically wrong, and that is the point of looking: half of them are a decimal place and half of them are the one tetel on the job where your method genuinely differs. You want to know which is which before the client tells you, because only one of the two is worth defending.

נכנסPriced koltsegvetesOriginal kiirasיוצאValidation reportFindings cleared
7

Issue the koltsegvetes with its foosszesito

דוחות

Produce the document rather than the spreadsheet: the tetel detail under each munkanem, the anyag and dij columns kept apart, a summary per munkanem and a foosszesito that carries the sections up to the offer total.

למה: The foosszesito is how a Hungarian client reads a price, and a bill delivered without one gets retyped into that shape by somebody who was not there when it was priced. Issuing it in the expected form is the difference between a price that gets discussed and a price that gets rebuilt.

נכנסValidated priced billMunkanem structureיוצאFoosszesito by munkanemKoltsegvetes for the client
מודולים

המודולים בתרחיש הזה

6 מתוך 190 מודולי הפלטפורמה

The market this case is written for

הונגריה

Everything in this case follows how construction work is measured, priced and paid for in this market. The forms, the cost breakdown and the payment rules are the ones used there, not a generic version of them.

Standards it follows

  • Kbt.
  • TSZSZ

You do not have to set any of that up by hand. The first time you open the platform it asks which market you work in. Choose this one and it sets the interface language, loads the matching cost database and records the cost classification, and it adds an example project you can open straight away.

The rule checks for this market come with the platform too. Switch them on once and an estimate that misses something the market expects is flagged while you are still working on it, not after the tender has gone out.

עוד ב-אומדן ותמחור

אומדן ותמחור

בדיקת אומדן לפני שליחתו

העבירו כתב מתומחר דרך כללי האימות, נקו כל אזהרה ושגיאה, ואז ייצאו דוח נקי שאפשר למסור ישירות…

3 שלבים8 דק׳פתיחה
אומדן ותמחור

אומדן ממאגר עלויות

משכו סעיפים מתומחרים ממאגר עלויות אמיתי, בנו מהם את הכתב, קבצו מבני חישוב חוזרים למכלולים וה…

4 שלבים12 דק׳פתיחה
אומדן ותמחור

קביעת רזרבה מסיכון עלות

הפכו אומדן חד-נקודתי לטווח, הריצו סימולציית מונטה קרלו על השורות שבאמת לא ודאיות, קראו את הפ…

3 שלבים11 דק׳פתיחה