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

内訳書をFIEBDC-3でスペインに送る

価格入りの内訳書をFIEBDC-3(スペイン・中南米市場で標準的に使われる予算フォーマット)へ出力し、デスクトップ積算ソフトで実際の予算として開けるようにし、自社のリーダーで読み込んでも内容が変わらないことを確認する。

4ステップ11 分コストコンサルティング会社 / 積算事務所総合建設会社専門工事業者

仕組みをステップごとに

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

1

Get the bill ready to travel

BOQ

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

BOQ

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

BOQ

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

BOQ

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
モジュール

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

Bill of Quantities

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

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

  • FIEBDC-3 (BC3)
  • LCSP

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.

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

コマーシャルと契約

Turn a change into a paid variation

Capture a scope change while it is fresh, price it as a contract variation on your agreed r…

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

Run a subcontractor package

Award a trade package to a subcontractor, place it on a subcontract with a schedule of valu…

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

Payment application and reconciliation

Value the work put in place this period against the contract, raise the application with th…

3ステップ12 分開く