Valuation & Accounting

Combining the files of one asset

Summary

A building or a bridge is rarely delivered as one IFC file. The architect, the structural engineer, the installers and the suppliers each export their own, and every delivery round adds another version. Valued one by one, these files count the same work and the same elements several times. An asset in forensicBIM is one building or structure together with every audited file that describes it, valued as one data set.

The rule behind it is short: cost is counted per authoring, use is counted per physical element. Each file keeps the cost of the work that went into it, unless it is a copy, an extract or an older version. The savings, value in use and value at stake are worked out once, on the elements of all files together, with every element counted once.

All figures on an asset page are the value of the asset’s data, not of the building.

Creating an asset

On the dashboard, choose Select files, tick the files of one building and choose Combine into an asset. The Assets page also suggests groups of your files that look like one asset (same project, same site, the same location); Review starts from such a group and Not one asset hides it for good.

The engine then matches the files and opens the review step: what each file is to the others, which decisions are yours, and what the asset is worth with the defaults. Nothing is decided silently. You confirm the proposals, and your decisions are kept: they are applied again every time the asset is recomputed.

RuleWhy
A file belongs to one assetOtherwise its cost would be counted in two places in your portfolio.
The files of an asset are stored in one regionThe asset’s results (combined figures, the picture, the georeferencing check) are stored in the region where its files are stored, as each file report is. Files you uploaded to another region go into an asset of their own.
Up to 100 files and 5 GB of IFC per assetThe matching reads the stored audit results, never the IFC files again; these limits keep it quick.
Creating and changing assets needs a Pro planAs for the valuation inputs; the suggestions are shown to everyone.
Each file keeps its own reportThe file report is unchanged. Its sidebar shows the asset the file belongs to and its part in it.

How the files relate

The engine compares the files element by element: by the IFC GlobalId where the files share elements, and by place and kind where they describe the same physical element under different ids. From that, every file gets one relationship. The two shares in the last columns are the ones the review step and the asset page show for every file.

RelationshipWhat it meansCounts for costCounts for use
PrimaryThe file with the most elements. The others are compared with it; it gives the asset its location and its kind (building or infrastructure).In fullIn full
ComplementaryAdds elements nobody else has: the structure next to the architecture, the installations, a supplier’s parts.In fullIn full
OverlappingShares part of its elements, by GlobalId, with a larger file.Its own elements in full, the shared ones for a small share (the work of exporting and coordinating them)Its own elements; the shared ones are already counted
Described twiceModels the same physical elements as another file under other ids, typically a structural model next to the architect’s walls and floors. Found by place and kind: the same class of element in the same place.In full: both were authoredOnly what it adds: the elements described twice count once
Extract or copyMost of its elements (90 % or more) sit in a larger file: a COBie export, a discipline view, the same file uploaded twice.Only its own few elements; a copy nothingOnly its own few elements; a copy nothing
Older versionReplaced by a newer delivery of the same model. Proposed from the names, the content and the export dates; you confirm.NothingNothing
Merged fileA federation of the other members (a coordination model). Proposed when most of its elements sit in two or more other members.Nothing on the asset; shown beside it with its own figuresNothing on the asset
ContextNot part of the asset: a terrain or city model, neighbouring buildings, a massing study.NothingNothing
Data layerAn older version or an extract you keep because it carries data the kept file lacks, such as classification or maintenance properties.A small shareNo elements of its own, but where it describes elements better, the asset takes its data

A file whose elements have no boxes in its audit (an audit in safe mode measures placements only) is matched on its ids only. The review step says so, and such a file is never counted as describing another file’s elements.

What this does to each figure

Figure on the asset pageHow it is built
Reproduction cost, current cost, depreciated replacement cost, origination costThe files’ own figures, each weighted by its share for cost. A copy or an older version adds nothing.
Carrying amountStraight-line from the cost at recognition, as for a file. By default the cost is the weighted reproduction cost; you can enter the asset’s own cost at recognition in its settings. File-level entries are not used on the asset page.
Value in use and the savingsOne run on the elements of all files together, each element counted once and with the best data any file holds for it. One-off work, such as collecting the missing data, is counted once for the asset.
Value at stake and re-acquisitionOne run on the same set, with one replacement value: the largest measured floor area among the files, not the sum. The asset page says which file it came from.
Transfer value, recoverable amount, deprival valueFrom the figures above, with the same rules as for a file.

The useful life, the hourly rate and the currency are the asset’s own: one setting for all its files, taken from the primary file. The life selector, the savings chart (per year, total over time, or both) and the eleven figures work as on a file report, described in The eleven numbers and Operate & maintain savings.

Why the asset is worth less than the sum of its files

Because the sum counts things more than once. The asset page shows the plain sum of the files next to each figure, so the difference is visible. Across the 236 public test files we combined into assets, the plain sum overstated the cost by about a fifth and value in use by about a fifth as well; in folders full of versions and exports it was two to three times too high. The cost side shrinks through copies, extracts and older versions; the use side through elements described twice and through one-off work that is no longer repeated per file.

Who brings what

The asset page shows, for every file, its share of the asset’s value in use and what the asset would lose without it. For the primary file the loss is not a meaningful number (the others would be compared with another file), so the page says “the asset as a whole”. The chart Who brings the savings splits the yearly saving the same way.

Older versions and the carrying amount

An older version counts nothing on the asset page: its content lives on in the newer one. That is a statement about the data, not an accounting entry. If you recognised the older version as an asset in your books, replacing it is a question for your accountant or auditor: whether the old carrying amount is derecognised, or the new delivery is treated as a subsequent cost of the same asset. The asset page can help by showing which files are older versions and what the newer ones added.

This is not accounting advice. Whether model data can be recognised at all, and how a replaced version is treated, is decided by you and your auditor under the rules that apply to you. See Why BIM data is worth less on the balance sheet.

Merged files and context models

A coordination model that merges the other deliveries holds nothing new: valued as a member it would add the cost of work that was never done. It is shown next to the asset with its own figures, so you can still see what it holds, and it adds nothing to the asset. When the merge is the only large file and the separate deliveries are missing, it is not proposed as merged: then it is the asset.

A context model describes the surroundings, not the asset. A city model of the neighbourhood can carry a value at stake of millions on its own; counted into one building, it would drown the building’s figures. Context models are therefore left out by default. When every file is a context model (three massing studies, say), none is proposed as context and they are valued as they are.

Alignment: do the files sit in the same place?

The asset page draws all files in one picture, each in its own colour, around one shared anchor: the centre of the primary file. A file that sits eight metres off is drawn eight metres off. Next to the picture, the alignment table compares each file’s extent with the primary file’s:

VerdictWhat it means
alignedThe footprints overlap and the heights match. A file with one storey counts as aligned when it sits within the building’s height.
aligned, own elevationSame footprint, but the file starts up to one storey higher or lower: a supplier who modelled from its own zero.
aligned, different part of the siteLittle or no overlap, but the extents touch: the next wing, the parking deck.
shifted verticallySame footprint, more than a storey off in height.
shiftedElsewhere, with little or no overlap. The offset is shown in metres.
placed differentlyThe file shares elements with another file by GlobalId, and those elements sit at another place. The shift is shown.
rotated, not matchedThe shared elements sit at different places in a pattern that is not a shift: the file is turned. It is not used for matching.
wrong units or scaleThe file is a hundred times or more larger or smaller than the primary file: millimetres read as metres, or the reverse.
other frameOne file is in map coordinates and the other is not, so the two cannot be compared.
no boxesThe audit holds placements only; the file is not drawn.

A shifted or rotated file is a delivery defect, not a matter of taste. Federated models are coordinated by overlaying them; a file that does not sit where the others are hides clashes, shows clashes that are not there, and puts every quantity taken from the federation at risk. Where a misplaced file shares elements with another file by GlobalId, the engine uses those elements to correct the shift before it matches by place. Without shared elements, or when the file is turned, it cannot: an element the file describes twice is then counted twice on the use side. The asset page flags such files, and fixing the placement removes the flag. How a file is placed on the map is explained in Georeferencing.

Georeferencing: does each file put itself in the right place?

Alignment compares the files with each other. Georeferencing asks something else: where does each file’s own georeferencing put it on the map, and do the files agree? Every file is placed by what it says itself; a file is never moved onto the others, because that would hide exactly the error you are looking for. The asset page lists the verdicts in the Georeferencing card, and Check on the map opens all files on one map, one colour per file.

Files carry their georeferencing in one of three ways:

Placed byWhat it isHow reliable
map conversionAn IfcMapConversion with eastings, northings, height, rotation and scale, and the coordinate system it refers to.Full. A scale written as the unit ratio (0.001 for millimetres) is corrected, as in the 3D Map.
map coordinates in the placementsNo map conversion, but the elements sit at map coordinates (for example E 2’689’000 / N 1’253’000). Common in infrastructure.Good, but the file names no coordinate system. It is inferred from the coordinate range, another file of the asset, the site address or the site latitude/longitude, and marked probable.
site latitude/longitudeOnly RefLatitude / RefLongitude on the site.Rough: a point, no rotation. Often a software default; Boston, Revit’s default project location, is flagged as such.

Two files agree when the elements they share, by GlobalId, land on the same map point: within 0.5 m horizontally, 0.5 m vertically and 0.2° of rotation. Files that share no GlobalIds can still agree when elements of the same kind coincide in place, such as a wall in both the architectural and the structural model. The reference is the largest group of files that agree with each other, not simply the primary file: when five files agree and the primary sits 12 m off, the primary is flagged.

VerdictWhat it means
agreesIn the group of files that agree.
offIts shared elements land elsewhere. The offset east, north and in height is shown in metres.
rotatedIts shared elements land in place at the centre but turned: the map conversion’s rotation differs.
referenceNo two files agree, so the files that share elements with this one are measured against it. Either side can be the wrong one.
not comparedPlaced on the map, but it shares no elements with the other files (a different discipline or a different part of the line). Only the map can tell; the nearest other file and its distance are given.
rough locationSite latitude/longitude only.
no coordinate systemMap coordinates, but no coordinate system is named and none fits, so the file cannot be put on the map.
not georeferencedNothing to place the file with. On the map it can be shown faint where another file’s map conversion would put it.

The card also flags what is wrong inside one file: a map conversion that names EPSG:0, a map conversion without coordinates, a site latitude/longitude far from where the map coordinates put the file, and a file whose map conversion lands outside the area its coordinate system is meant for (often map coordinates added twice, or a northing counted from the equator). Such a map conversion cannot place the file, as the IFC Georeferencer refuses it too; when the file’s site latitude/longitude lies in the area, the map shows the file there instead (its origin on the site point; approximate), with a red warning. Files that share the same wrong map conversion keep their positions relative to each other. On the map, each other file first appears as element boxes and then as its 3D model, each drawn around its own anchor so that a file kilometres down the line is not bent by the map projection.

The delivery check

The review step opens with a short check of the delivery as a whole: which disciplines are present and which are missing, which files are placed differently or in other units, which files were uploaded twice, which versions replace which, which elements are described twice, and which files cannot be used yet. It is the same evidence the asset’s figures are built on, read as a list of questions for the next delivery.

Keeping the asset current

An asset is recomputed when you change its files or confirm a decision. When one of its files is audited again, the asset page says the figures are out of date and offers Recompute. When a file is deleted, it leaves the asset. Results computed with an older version of the engine are marked the same way.

Questions

Why does the asset have a lower reproduction cost than my files together?

Because some files are copies, extracts or older versions of others. Their work is already in the files they were taken from. The review step names each one and why.

A structural model and an architectural model both have the floors. Are both paid for?

For cost, yes: both were authored. For use, the floors count once, so the savings are not doubled.

The engine proposed two files as versions, but both are live. What do I do?

Choose Both are live versions in the review step. The decision is kept and the proposal does not come back.

Can I put one file in two assets?

No. Its cost would be counted twice in your portfolio. Take it out of the first asset to add it to another.

Does combining change my file reports?

No. Every file keeps its own report and figures. Only the sidebar shows the asset it belongs to.