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

Build a parametric assembly

Give an assembly named parameters and drive its component quantities from formulas over them: enter the wall area when you apply it and let the reinforcement, the concrete and the composite rate follow.

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

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

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

1

Name the parameters

מכלולים

Give the assembly the few named parameters it really turns on. Each is one of three kinds: an input the estimator enters when they apply it, with a sensible default; a constant that does not move, such as a rebar ratio; or a calculated value derived from the others, such as area from length times height.

למה: The parameters are the questions the assembly asks whoever uses it, so keep them to the ones that genuinely change between jobs. Every extra input is another figure somebody has to be right about at half past five on the day the tender goes in.

נכנסBuild-up you price repeatedlyWhat actually varies job to jobיוצאNamed parametersResolved default values
2

Drive the quantities from a formula

מכלולים

Set a component's quantity from a formula over the parameters instead of a fixed number, the reinforcement as wall area times the rebar ratio, the formwork as area times a double-sided factor. Any line whose quantity is computed carries an fx marker on it.

למה: A fixed recipe makes you re-derive the steel by hand every time the wall moves. Written as a formula the relationship is stated once, so the ratio you agreed with the engineer is the ratio in every priced line, and the fx marker stops anyone reading a derived quantity as one that was measured.

נכנסNamed parametersComponent linesיוצאQuantity formulasComputed lines marked fx
3

Prove it before anyone uses it

מכלולים

The editor checks the parameter graph as you work and flags problems inline against the parameter or component they belong to: a name referenced but never defined, two parameters sharing a name, a formula that will not parse, a cycle where two calculated values depend on each other. Then run the expansion preview at real values and read the quantity each line moves from and to, plus the rolled-up rate the server will write.

למה: A cycle or a stale reference does not announce itself in a spreadsheet, it just returns a number that looks plausible. Previewing at values you actually expect is what catches a formula that is right in principle and out by a factor of ten, and because the preview runs on the same decimal arithmetic as the live expansion, the rate you read here is the rate that lands, exact to the cent.

נכנסDraft parametric assemblyValues you expect on the jobיוצאNamed errors, if anyBefore and after per line
4

Apply it to the bill

כתב כמויות

Place the assembly on a bill position and enter the one figure it asks for, the wall area for that element. The components expand at those values and the composite rate follows, with nobody retyping a quantity.

למה: This is where the parametric version earns its keep over a fixed recipe. When the wall grows at the next design issue you change one input rather than eleven component quantities, and the two or three that would quietly have been forgotten move with the rest.

נכנסProven assemblyWall area for this elementיוצאPriced bill positionComponents at computed quantities
מודולים

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

2 מתוך 184 מודולי הפלטפורמה

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

אומדן ותמחור

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

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

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

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

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

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

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

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

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