
This numbered Frameworks Page covers a single Visual Knowledge Model (VKM). Refer to Tags at the bottom for content classification and source publication if any. The page may be updated to connect with newer Frameworks Pages. The number is for pages, not for content.
Published on December 1, 2014 | Last Updated on September 20, 2025
This is the collector/index page for all Frameworks content.
Updated August 9, 2019 (Original post October 23, 2014): To enable the definition of physical deliverables (Physical Assets) in a flexible manner, the concept of Asset Unit is needed (to be covered in a separate post). An Asset Unit combines: (i) a variable Asset Scale (e.g. a component, an assembly, a building, or a whole city) derived from the Asset Hierarchy (see below), with (ii) an Asset List defined by the Demand Entity (Employer, Client, Appointing Party) within an Information Cycle (a list of assets to be designed delivered, and/or utilised), and (iii) Asset Attributes derived from the Conceptual (BIM) Ontology (e.g. Asset Function, Asset Location, and Asset Cost).
Asset Hierarchy – v2.0, 2018 – Link to older version (v1, 2011)
The Asset Hierarchy organises Physical Deliverables/Assets by relative scale by combining taxonomies developed by OSCRE[1] and Transport for North South Wales[2]. The diagram does not differentiate between assets – Buildings as a sample scale – by their size, monetary value, location, or designated function[3] – e.g. Cultural, Transportation, or Recreation[4] but by their granularity relative to each other. The diagram includes a numbering system (scale 10-70) to establish an Asset’s relative position on the scale. The diagram also highlights how:
- The Assets Scale bridges the semantic and informational divide between three complementary industries and their respective information domains. At the upper-end of the scale, the Geospatial Industry and its Geographic Information System (GIS) domain overlaps with the Construction Industry and its BIM domain; while at the lower-end of the scale, it overlaps with the Manufacturing Industry and its Product Lifecycle Management (PLM) domain[5].
- An Asset can be a member of three Asset Clusters:
- An Asset Portfolio (scale 300) is a clustering of assets for the purposes of strategic investment, operation, and management. Asset Portfolios may also be referred to as ‘asset groupings’ or ‘asset systems’[6];
- A Modular Assembly (scale 500) is a functional clustering of assets for the purposes of Design for Manufacturing and Assembly (DfMA) and similar offsite methods. Examples of Modular Assemblies and Sub-Assemblies include prefabricated houses, pre-assembled mechanical risers, and pre-constructed wall sections[7]. Treated as a single Asset Unit, a Modular Assembly can be (a) first developed and tested in digital space; (b) prototyped, manufactured, constructed, and/or pre-assembled offsite; (c) packaged and readied for transportation; (d) transported for storage on site or delivered Just-In-Time (JIT); and (e) unpacked, erected, and/or assembled; and
- A Temporary Package (scale 700) is a clustering of assets for the purposes of transportation and storage logistics. Examples of Temporary Packages include standardised shipping containers and logistical package[8]. Temporary Packages also include bundled materials (e.g. a sandbag, load, or palette).
- Systems are treated as dynamic sub-scales that – depending on the Physical Asset being measured – may be more/less granular than other assets. Systems span the entire hierarchy (from scale 15 to 65) and can flexibly connect information deliverables and requirements across the BIM, GIS, and PLM domains.
Using a variable Asset Scale allows the dynamic assignment of less granular assets at the start of an information cycle. More information about how Asset Scales and Asset Units are used will be explained in future posts.
[1] Fuhrman, A. (2007). The Hybrid Taxonomy Real Estate Focus, The Open Standards Consortium for Real Estate (OSCRE).
[2] TfNSW. (2015). Systems Engineering, Transport for NSW, New South Wales Government (T MU AM 06006 GU). Retrieved from https://www.transport.nsw.gov.au/system/files/media/asa_standards/2017/t-mu-am-06006-st-v2.0.pdf Last accessed Aug 9, 2019
[3] Assets can be classified under many concepts which should not be combined in a single taxonomy. Information Actors will need to identify the number of classifications needed to manage their asset information. For example, an Information Actor may use three primary classifications to identify a Physical Asset: Asset Scale (e,g. Lighting System), Asset Function (Lighting), and Asset Location (e.g. In Room 391 or along Highway A5, Exit Ramp 17).
[4] OmniClass. (2013). OmniClass | Construction Classification System, Retrieved from http://www.omniclass.org/; and NBS. (2015). UniClass 2015 (1.7 ed.). Retrieved from https://buildig.com/uniclass-2015/ Last accessed Aug 9, 2019.
[5] Overlaps between the BIM and GIS/PLM domains are well-covered in: Song, Y., Wang, X., Tan, Y., Wu, P., Sutrisna, M., Cheng, J. C., & Hampson, K. (2017). Trends and Opportunities of BIM-GIS Integration in the Architecture, Engineering and Construction Industry: A Review from a Spatio-Temporal Statistical Perspective. ISPRS International Journal of Geo-Information, 6(12), 397; and in Jupp, J. R., & Singh, V. (2014). Similar concepts, distinct solutions, common problems: learning from PLM and BIM deployment. Paper presented at the IFIP International Conference on Product Lifecycle Management.
[6] ISO. (2014). ISO 55000:2014 Asset management – Overview, principles and terminology. Retrieved from https://www.iso.org/standard/55088.html Last accessed Aug 9, 2019
[7] BWTL. (2018). Platforms Bridging the gap between construction + manufacturing, Brydon Wood Technology Limited (BWTL) for the Centre for Digital Built Britain (CDBB), University of Cambridge. Retrieved from https://www.cdbb.cam.ac.uk/system/files/documents/2018Platforms_Bridgingthegapbetweenconstructionandmanufacturing.pdf Last accessed Aug 9, 2019
[8] Saghir, M. (2004). The concept of packaging logistics. Paper presented at the Proceedings of the Fifteenth Annual POMS Conference, Cancun, April.
Cite as: BIMe Initiative (2025), '30. Asset Hierarchy', https://bimexcellence.org/frameworks/asset-hierarchy/. First published 1 December 2014. Viewed 27 September 2025
The diagrammatic representation show a clear relationship between each sub-system. Great
This is a great illustration.
Very helpful. Thank you.
Bilal, Actually this was based on some work I had done while at NAVFAC and NIBS at the start of NBIMS when bSI was still IAI. We were working with Andy who you referenced and Dianne Davis, who should also be referenced. Initially it was based on a discussion that you can summarize information up the chain, but you really need to have the detail data, and more importantly you cannot go the other way. I can send you the original graphics from 2005 if you would like. I do like this version and how it has matured.
Hi Deke. Good to hear from you and thank you for this. Yes please send me the graphic and Dianne Davis’ publication so I can read it and reference it as well. True, this new graphic is a maturation of the first version but includes an important new concept – the sliding Systems Scale. As Schilling (2000, p. 314) puts it, “at any unit of analysis, the entity is a system of components and each of those components is, in turn, a system of finer components”. Using this sliding scale, the main purpose of this update is really to say that, in contrast to the focus on Building Components (scale 60) by current industry standards and protocols, the BIM Framework advocates for the adoption of Systems in general, and Building Systems (scale 55) in particular, as a primary Asset Scale for assigning, verifying, and exchanging structured information across the information lifecycle. Also, but maybe slightly different to what you’ve mentioned, the attributes of a parent Asset Scale (e.g. Built Facility scale 40) can be – depending on the Degree of Integration – inherited by child asset scales (e.g. Systems and Components within that Built Facility) (bSI, 2018) (bSDD, 2018) (ISO, 2007).
These are some of the basic concept of asset hierarchy. It’s more of a important things in the organization classification. I love reading the article and it teaches me a lot.