Skip to content
Menu

Document control

A model viewer on site: useful views, information limits and authorized references

By Review.LivePublished 3 min readHow we write

The foreman opens a model of the mechanical penthouse to discuss installation sequence. A duct appears in a different location from the issued sheet. Before treating either view as the answer, the team needs to establish what the model represents and what is authorized for the work.

Steel conduits, a grey cable raceway and a red sprinkler pipe run side by side under a concrete waffle slab.
Photo: Nopparuj Lamaikul on Unsplash

Use the viewer for the purposes agreed on your project, with its information limits understood. A model can help the crew see a congested area and connect several systems, but its appearance does not establish that every component is current or suitable for every decision. Confirm the relevant information requirements and authorized references before relying on it.

Establish what this model can support

  1. Check purpose and authority. Read the project's model information requirements and relevant contractual arrangements. Identify the uses permitted for this issue and who can answer questions about reliance. Avoid importing another project's blanket rule that models either govern everything or can never support quantities, dimensions or layout. The actual authorized information controls the decision.
  2. Identify the relevant content. Check issue identity, date, included disciplines and any stated exclusions or limitations. Ask about the particular components and use you need, rather than treating one model date as proof that every object is equally developed. Link the model issue with its source information and the drawing register where appropriate.
  3. Use the view to frame a specific question. Locate the work area and discuss access, apparent congestion or a proposed sequence with the affected trades. Capture enough context to identify the location and model issue. Distinguish a visual concern from a verified technical conclusion; a screenshot alone does not approve a change or establish that an installation is feasible.
  4. Route differences before relying on them. Compare the relevant authorized documents and ask the responsible project team to resolve a discrepancy. Record the response and any affected work restriction through the established process. Update the field information when the answer is issued, and verify that the crew can identify the resolved reference rather than an old saved view.

Public model-development guidance distinguishes information content and reliability and explains that the applicable development levels need project definition. BIM use guidance likewise calls for specific methods and intended outcomes. These are useful industry concepts, not a substitute for your project's information requirements or a universal ranking of models against drawings.

Common mistakes

  • Equating a detailed-looking object with approved construction information.
  • Checking the overall model date but ignoring component limitations.
  • Treating a visual difference as permission to relocate the work.

Checklist

Before relying on a model view

  • Agreed purpose and permitted reliance.
  • Issue identity and relevant components.
  • Known limitations and exclusions.
  • Related authorized references.
  • Responsible reviewer and recorded resolution.

Check your understanding

The model looks clearer than the sheet. Can the crew build from it?

Show the answer
Clarity alone does not establish authority or suitability. Check the project's permitted use and relevant information status, then resolve any discrepancy through the responsible team before relying on the view.

Sources

  1. Level of Development Specification — public backgroundBIMForum · US industry guidance; actual project requirements govern · accessed
  2. NBIMS-US V4 — BIM Use DefinitionsNational Institute of Building Sciences · US industry guidance; actual project requirements govern · accessed

Related articles