ケース / コマーシャルと契約
コマーシャルと契約

Send a bill to Spain in FIEBDC-3

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ステップ11 分コストコンサルティング会社 / 積算事務所総合建設会社専門工事業者

仕組みをステップごとに

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

1

Get the bill ready to travel

内訳書

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.

入力Priced billChapter structure出力Clean chapter and item treeEvery position coded
2

Export to FIEBDC-3

内訳書

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.

入力Structured priced billFIEBDC-3 export出力BC3 budget fileHierarchy, rates and texts
3

Check the charset in the header

内訳書

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.

入力BC3 filePosition texts出力Charset named in the headerText that survives the trip
4

Prove the round trip

内訳書

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.

入力Exported BC3 fileBC3 importer出力Re-imported billConfirmed match
モジュール

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

内訳書

プラットフォーム 184 モジュール中 1

コマーシャルと契約の他のケース

コマーシャルと契約

変更を支払われる契約変更に変える

施工範囲の変更を発生時に記録し、合意単価に基づいて契約変更として見積もり、次の出来高請求に計上することで、追加工事が静かに吸収されるのではなく回収されるようにします。

3ステップ11 分開く
コマーシャルと契約

下請パッケージを運用する

下請業者に工種パッケージを発注し、出来高内訳書と保留金付きの下請契約に載せ、実際に完了した作業に対して出来高払いで支払っていく。

3ステップ11 分開く
コマーシャルと契約

出来高査定申請と照合

今期に実施した工事を契約に照らして評価し、根拠となる証憑とともに出来高査定申請を起票し、認定された内容と実際に入金された内容を照合する。

3ステップ12 分開く