You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
You are viewing the article in preview mode. It is not live at the moment.
Home > FAQs > General FAQs > Glider Nexus and BIM
Glider Nexus and BIM
print icon

The NBS defines BIM as the following:

 

"BIM or Building Information Modelling is a process for creating and managing information on a construction project across the project lifecycle".

 

  • Glider Nexus is a process-driven platform for classifying, categorising, validating and tracking information.

 

"One of the key outputs of this process is the Building Information Model, the digital description of every aspect of the built asset". 

 

  • Glider Nexus focuses on creating and sharing the underlying asset data and meta data rather than file sharing.

 

"This model draws on information assembled collaboratively and updated at key stages of a project."

 

  • Glider Nexus provides a higher degree of flexibility when collaborating, sharing and transferring information between software platforms.

 

"Creating a digital Building Information Model enables those who interact with the building to optimize their actions, resulting in a greater whole life value for the asset."

 

  • Glider Nexus is built on a "single input - multiple output" architecture so that users can easily search and find information relevant to them.

 

So yes, generally all information managed using the Glider Nexus platform is "BIM". 

BIM is not defined based on the presence of a 3D model or by a COBie deliverable. When defining BIM refer to one of the levels below:

 

BIM Definition Glider Nexus 
Level 0 No collaboration on information for the as-built asset.  Digital Handover Documents based on defined Employers' Requirements or Glider's standard classification, process and templates. 
Level 1

Some collaboration on information using a CDE (Common Data Environment)

 

2D drawings and 3D models following an industry standard (e.g. BS1192, ISO 19650).

As above plus the inclusion of models.
Level 2

Collaborative working following a project specific, managed information exchange process. 

 

3D software must export to a common file format e.g. IFC (Industry Foundation Class) or COBie (Construction Operations Building Information Exchange) to enable information to be shared and federated for the built asset. 

Digital Handover Documents based on defined project-wide Information Requirements as defined in industry standards (BS, ISO etc) for models and data. 

 

All asset information can be transferred via IFC/COBie.

Level 3 (WIP)

Still to be fully industry defined. 

Total collaboration on all information for the as-built asset. (Concept, Design, Construct, Operations). 

 

All information shared (Open BIM / Open Data) and collated and federated into a single source of truth. This includes metadata and audit trails. 

Available.

 


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Glider Nexus takes a structured, process driven, shared approach to information management irrespective of; size/type of project, levels of BIM or 3D models.

By using Glider Nexus to manage information you get the benefits of structure, process, classification and auditability as standard.

 

Feedback
0 out of 0 found this helpful

scroll to top icon