케이스 / 적산 및 원가
적산 및 원가

Australian Cost Management Manual에 따라 elemental cost plan 작성하기

gross floor area와 기능 단위를 확정하고, AIQS 요소 목록에 따라 요소별로 계획을 구성하고, 분석된 프로젝트로부터 각 요소의 가격을 매기고, 공사 중간 시점까지 escalate하고, 설계와 시공 contingencies를 분리해 유지하고, 다음 계획과 비교할 수 있는 계획을 발행한다.

6단계18 분원가 컨설팅 / 적산 업체시행사 / 발주처PM/CM 업체

작동 방식, 단계별로

플랫폼 전반에 걸친 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 분열기