변경사항을 유상 변경계약으로 전환
신선할 때 범위 변경을 기록하고, 합의된 단가로 계약 변경계약으로 산정한 뒤 다음 기성청구에 포함시켜, 추가 작업을 조용히 흡수하지 않고 회수합니다.
Export a priced bill to FIEBDC-3, the budget format the Spanish and Latin American market exchanges in, so it opens as a real budget in a desktop estimating tool and comes back through your own reader unchanged.
플랫폼 전반에 걸친 4단계 - 각 단계에서 무엇을 하는지, 그리고 왜 중요한지.
Check the bill has the shape BC3 expects before you export anything: a chapter for each section, an item for each position, and a code, a unit, a quantity and a unit rate on every line. Long descriptions travel too, so read the ones you would rather a client did not see.
이유: BC3 carries a hierarchy, so a bill with orphaned positions or two items sharing a code arrives at the other end as a budget nobody can navigate. Sorting the tree out here takes minutes. Sorting it out after someone has started pricing in their own software is no longer your decision to make.
Export the bill to FIEBDC-3. The file carries the chapters and items with their codes, units, quantities, unit rates and long texts, which is what a Spanish desktop estimating tool needs to open it as a working budget instead of a list of numbers.
이유: BC3 is what that market actually exchanges budgets in, and for Spanish public work it is not optional. Sending a spreadsheet instead means somebody at the other end retypes your bill, and a retyped bill of four hundred positions always loses a few.
Open the file and read the charset the header declares. It is written Windows-1252 by default, which is what the desktop tools in that market expect, and it switches to UTF-8 only when a character in your texts cannot be represented. Either way the header states which one was used.
이유: A mis-declared charset is the classic BC3 failure. The file opens, the numbers are all correct, and every accented character in the descriptions comes out as rubbish. It gets spotted late, usually by the client reading your descriptions, and it makes an otherwise careful submission look sloppy.
Read the file you have just written straight back in through the BC3 importer and compare it against what you exported. Codes, chapters, quantities, units, rates and long texts should all come back the same.
이유: An export nobody has ever read back is a guess. Putting it through your own reader takes a minute and is the difference between believing the file is sound and knowing it, which matters most on the submission where you do not get a second go.
플랫폼 184개 모듈 중 1개
신선할 때 범위 변경을 기록하고, 합의된 단가로 계약 변경계약으로 산정한 뒤 다음 기성청구에 포함시켜, 추가 작업을 조용히 흡수하지 않고 회수합니다.
협력업체에 공종 패키지를 발주하고, 기성 내역서와 유보금 조건을 포함한 하도급 계약으로 전환한 뒤, 실제 완료된 작업에 대해 기성 청구별로 지급합니다.
계약서 대비 해당 기간 시공된 물량을 평가하고, 근거 자료와 함께 기성 청구를 제출하며, 승인된 금액을 실제 입금액과 대조 확인한다.