변경사항을 유상 변경계약으로 전환
신선할 때 범위 변경을 기록하고, 합의된 단가로 계약 변경계약으로 산정한 뒤 다음 기성청구에 포함시켜, 추가 작업을 조용히 흡수하지 않고 회수합니다.
Read the Deckungsbeitrag while the site is still running: set the Soll from the calculation, book progress and actual cost every period, reconcile cost against value and let earned value say where the job lands.
플랫폼 전반에 걸친 7단계 - 각 단계에서 무엇을 하는지, 그리고 왜 중요한지.
Generate the cost budget from the priced bill, then work down the budget lines category by category so the Soll carries the money your calculation carried, split the way site will actually spend it.
이유: A Soll is only worth comparing against when it comes from the calculation the job was priced on. A budget keyed in from memory turns every later variance into an argument about the budget instead of a decision about the work.
Create the baseline from that budget with its budget at completion, run the check, and approve it. From here the Soll is fixed and dated, and every later measurement is read against it.
이유: A budget nobody froze quietly swallows a Nachtrag, and the margin never moves - which is exactly how a job reads as healthy until the end. A dated, approved Soll makes added scope show up as a change you can see, price and defend.
On the cut-off date record the percent complete against the bill positions from the site measurement, then read the earned quantity and the quantity variance the entries produce.
이유: Built work is the one figure nobody can invoice their way around. Recording it position by position, on a date everyone holds to, is what keeps the value side of the reconciliation from turning into a feeling.
Raise the progress claim for the period and populate it from the progress you just recorded, then walk it from submitted through approved to certified so the period ends with a value both sides stand behind.
이유: The Leistungsmeldung is what turns built work into money you are allowed to count. Filling it from recorded progress rather than from a spreadsheet keeps the value in the reconciliation tied to something that was measured on site.
Book the cost that landed in the same period - subcontractor and supplier invoices, labour, plant - and bring in the orders placed but not yet invoiced so the Obligo sits alongside the Ist.
이유: Cost you have ordered but not yet been billed for is the part of the overrun that has already happened and cannot be seen yet. Leave it out and the margin looks fine for exactly as long as the post takes to arrive.
Open the month, set the value to date against the cost to date per cost head with the accruals in, and read the margin to date and the forecast margin. Finalise the month once the figures are agreed.
이유: One margin figure tells you there is a problem; a margin per cost head tells you which trade caused it. Finalising the month puts an agreed number on the record, so next month's movement is a comparison rather than a fresh opinion.
Record the measurement for the cut-off - earned value, actual cost, planned value - and work out the forecast. Read the cost and schedule indices, the outturn against budget, and pick up any alert that has tripped its threshold.
이유: An index under one is a forecast, not a report card: it says where the job ends up if nothing changes. Read in month three that is a plan to fix the trade that is losing. Read at the Schlussrechnung it is only the loss you already took.
플랫폼 184개 모듈 중 6개
신선할 때 범위 변경을 기록하고, 합의된 단가로 계약 변경계약으로 산정한 뒤 다음 기성청구에 포함시켜, 추가 작업을 조용히 흡수하지 않고 회수합니다.
협력업체에 공종 패키지를 발주하고, 기성 내역서와 유보금 조건을 포함한 하도급 계약으로 전환한 뒤, 실제 완료된 작업에 대해 기성 청구별로 지급합니다.
계약서 대비 해당 기간 시공된 물량을 평가하고, 근거 자료와 함께 기성 청구를 제출하며, 승인된 금액을 실제 입금액과 대조 확인한다.