ケース / 積算とコスト
積算とコスト

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
モジュール

このプレイブックのモジュール

プラットフォーム 184 モジュール中 2

積算とコストの他のケース

積算とコスト

送付前に見積を確認する

積算済みの内訳書を検証ルールにかけ、すべての警告とエラーを解消し、そのまま顧客に渡せるきれいなレポートを出力する。

3ステップ8 分開く
積算とコスト

コストデータベースから見積を作成する

実在のコストデータベースから積算項目を取り出して内訳書を組み立て、繰り返し使う積み上げをアセンブリにまとめ、入札額を確定する前にチェックを実行します。

4ステップ12 分開く
積算とコスト

コストリスクから予備費を設定する

単一値の見積を幅のある値に変え、本当に不確実性のある項目についてモンテカルロシミュレーションを実行し、P50からP90の分布を読み取り、行ごとに根拠を示せる予備費を設定します。

3ステップ11 分開く