← All use cases

Managing existing, demolition, new and temporary with models

DES-EXISTING-MODELS · General · Design

Split models by existing, demolish, new and temporary - so it is immediately clear what is new and what is removed, and whole models can be toggled on and off.

Starting point

  • Mixing existing, demolish and new in one model hurts readability; toggling by status is cumbersome.
  • Without a filename marker, the federated model does not show at a glance which file holds existing, demolish, new or temporary.

Goal & benefit

  • Split models by status; the letter sits in the filename right after the project number.
  • Understand models quickly and toggle what is new versus what is removed.

Process

  1. Set status per element (NEW, EXISTING, DEMOLISH, TEMPORARY).
  2. Split models by status and mark the letter in the filename after the project number (E, D, N or T).
  3. Toggle existing, demolish, new and temporary in the coordination model.

Outcome

  • Models split by status that can be read and switched quickly.

Deliverables

  • Models split by status; filename with letter after the project number (E existing, D demolish, N new, T temporary)
  • Status according to Pset_*Common: NEW, EXISTING, DEMOLISH, TEMPORARY
  • ElementStatus (ePset_ElementStatus) as IFC2x3 substitute

Activated by project goals

Related workflows

Contact

abstract ag

Imprint · Picassoplatz 4, 4052 Basel