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

Australian Cost Management Manual に従って elemental cost plan を作成する

gross floor area と機能単位を確定し、AIQS の要素一覧に沿って要素ごとにプランを組み立て、分析済みプロジェクトから各要素を積算し、工事期間の中間まで escalate し、設計と施工の contingencies を分けたまま保ち、次のプロジェクトと比較できるプランを発行する。

6ステップ18 分コストコンサルティング会社 / 積算事務所デベロッパー / 発注者プロジェクト / 施工管理会社

仕組みをステップごとに

プラットフォーム全体で6ステップ - 各ステップで何をするか、そしてなぜ重要か。

1

Fix the area, the functional unit and the exclusions

見積根拠

Record the gross floor area the plan is built on, measured the way the manual measures it, the functional unit the client thinks in, beds, car spaces, classrooms or seats, and the list of what the plan excludes: land, authority charges, loose furniture, client contingency and the escalation beyond the horizon you have priced to.

理由: Two cost plans for the same building differ by a fifth when they measure area differently, and neither is wrong. Everything downstream is a rate per square metre, so an area defined loosely puts the same looseness on every element at once, and no later check finds it because every element is internally consistent.

入力Project brief and area scheduleDesign stage reached出力Gross floor area agreedInclusions and exclusions stated
2

Build the plan element by element

概算見積

Work down the element list rather than around the drawing: substructure, columns, upper floors, staircases, roof, external walls, windows and external doors, internal walls and doors, the three finishes, fittings, services and external works. Each element carries its own quantity, its element unit quantity and its cost, so the number can be argued about one element at a time.

理由: An element list worked through in order is also a completeness check, because an element with nothing against it is visible and a missing trade in a lump sum is not. It is how a plan produced in a day still has a roof in it.

入力Gross floor area agreedConcept drawings出力Cost plan by elementElement quantities
3

Rate each element against projects already analysed

Cost Explorer

Compare each element unit rate with the same element on completed projects of the same type, and write down the reason for every element that sits outside the range. A facade rate double the library is either a design decision worth naming or an error, and the difference between those two is a sentence.

理由: Elemental analysis exists so that a plan can be challenged before it is approved rather than after it is exceeded. An element that nobody could explain at the design review is the same element that becomes the overrun, and it was visible months earlier.

入力Cost plan by elementAnalysed projects出力Elements benchmarkedOutlying elements explained
4

Escalate to the middle of construction, not to today

物価指数

Record the base date the rates are current at, then escalate them to the midpoint of the construction period the programme implies. State both dates on the plan, and state the index you escalated with.

理由: A cost plan priced at today's rates for a building that starts in eighteen months is wrong on the day it is issued, and it is wrong in the direction nobody wants to discover later. Naming the base date is what lets a board read the number as an estimate of a future cost rather than as a price.

入力Elements benchmarkedIndicative programme出力Escalated to a stated dateBase date on the record
5

Keep the two contingencies apart

引当金・予備費

Carry a design contingency for the drawings that are not finished yet and a separate construction contingency for what the site will find, each as its own entry with what it is for. Reduce the design one as the design is resolved rather than letting it drift into the construction one.

理由: One combined contingency answers no question. It cannot be released as the design firms up, because nobody can say which part was for the design, and it cannot be defended when the site finds rock, because it has already been spent on documentation gaps.

入力Escalated to a stated dateKnown design gaps出力Design contingencyConstruction contingency
6

Issue it against the plan it replaces

レポート

Issue the plan with the element table, the rate per square metre, the rate per functional unit and a reconciliation against the previous plan that says which elements moved and why. Keep it as the version the next design review is measured from.

理由: A cost plan issued without a reconciliation is a new number rather than a report on the old one, and the conversation it produces is about whether to believe it. With the movement written out element by element, the same meeting is about four decisions that were already made.

入力Complete cost planPrevious cost plan出力Cost plan issuedMovement since the last plan
モジュール

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

プラットフォーム 190 モジュール中 6

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

  • AS 4000
  • Security of Payment Act

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 分開く
積算とコスト

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

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

3ステップ11 分開く