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

Minstroy 환산지수로 기준연도 smeta에 단가를 매기기

가격 기준시점과 그것이 속한 분기를 기록하고, 자신의 지역과 공사 종류에 대해 공표된 지수를 입력하고, 그것을 여전히 기준가격으로 남아 있는 항목에만 적용하고, 계수와 그 출처를 문서에 명시한다.

6단계12 분원가 컨설팅 / 적산 업체종합건설사시행사 / 발주처

작동 방식, 단계별로

플랫폼 전반에 걸친 6단계 - 각 단계에서 무엇을 하는지, 그리고 왜 중요한지.

1

Declare the price base and the date it belongs to

내역서

Set the base date on the bill header, the 2001 base or the quarter of a current price base, so the estimate states which roubles it is in, and record the period you need the money brought to, the region and the type of construction in the basis of estimate beside it.

이유: An index is a ratio between two periods and it means nothing without both of them. The base date on the bill is the price level validation reads, and a smeta that does not state it cannot be re-checked by anyone, including the person who wrote it six months later.

입력Smeta in base pricesTarget quarter결과Base date on the billRegion and type of construction
2

Enter the index the Ministry published for the quarter

물가 지수

Create an index series for the recalculation index the Ministry of Construction published for your type of construction, with the quarter as the period and the published value as the factor, and where the publication splits the index by element make a series for each: one for construction and assembly work as a whole, and separate ones for labour, machine operation and materials. Put the region on the location factor and the publication reference in the series description.

이유: One index for the whole smeta is the shortcut that costs most. Labour, machines and materials move at different speeds, and where the publication gives separate coefficients an expertise reviewer expects them applied separately. An index taken from a neighbouring region or from a different type of construction produces a defensible looking total that is simply the wrong one.

입력Index published for the quarterRegion and type of construction결과Coefficients by elementPublication reference
3

Apply the factor only to what is still in base money

물가 지수

Run the escalation preview scoped to this project, from each rate's own price date to the target quarter, and read it line by line: the factor, the escalated rate and, for a rate the preview could not escalate, the note saying why. Then carry the escalated rates onto the positions still in base money yourself, leave anything already priced from a quotation or an invoice untouched, and keep the preview's list of what was left out.

이유: Double indexing is the quiet error of this method: equipment bought on a current quotation, or a material priced from a real invoice, gets multiplied a second time by a coefficient built for base year money. The preview writes nothing to the bill, which is the point: the rate that reaches a position is one an estimator read and accepted, and the note on a rate with no price date is the exception list rather than a silent skip.

입력Positions in base moneyCoefficients by element결과Escalated rate per positionRates the preview could not escalate
4

Check what the coefficient should never have touched

검증

Run validation on the indexed bill and read what the Russian rules report: a bill with no base date declared, a line without a norm code or with one that is not in the base, a rate with no resources behind it, and any markup line whose base is not settled. Then go back to the preview's list for the positions the coefficient should not have touched, and clear both lists before the smeta leaves.

이유: The arithmetic of indexing is trivial and always passes, so validation reads the document rather than the sum: whether it says which roubles it is in and whether every line can be traced to a published norm, which is what an expertise reviewer checks first. The positions indexed twice or priced from a quotation are not a rule's business, they are the preview's, and the two lists together are the whole check.

입력Indexed smetaValidation rule set결과Exception listCorrections applied
5

Test the heaviest positions against a resource price

Cost Explorer

Take the positions that carry most of the total, price a handful of them from resources at today's money, and compare the two answers. Record the gap and the reason for it, not only the number.

이유: This is the resource index method used as a check rather than as a method. An index describes an average, and the positions that dominate your total are the ones least likely to be average. Where the two answers diverge sharply you have found either a stale coefficient or a position built on the wrong norm, and both are far cheaper to find before the contract is signed.

입력Positions carrying the costResource priced check결과Gap per positionReason on record
6

Show the coefficient and its source on the document

보고서

Issue the smeta with the base, the base date, the target quarter, the coefficient applied to each element and where it was published, printed on the face of the document rather than kept in a working file on somebody's machine.

이유: The customer, the expertise reviewer and the auditor all check the same thing first: which coefficient was used and for which period. A smeta that carries that on its face is checked in minutes, one that does not comes back as a request for clarification and costs a full review cycle.

입력Checked smetaIndex provenance결과Issued smetaReproducible calculation trail
모듈

이 플레이북의 모듈

플랫폼 190개 모듈 중 5

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

  • GESN/FER
  • KS-2 / KS-3

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 분열기