MEASURE ALL command

Summary

This button evaluates loaded BIM models against all enabled document budget rules

Description

The whole process is described in the following schema:

The process is performed following these steps:

• Removal of all automatic, non-locked, take-off lines from previous budget items

  Manual take-off lines will always be preserved

  Locked BIM elements belonging to a non-locked take-off line will be preserved as well

  • For each budget item in every non-disabled budget rule, the algorithm will search for code-matching item in budget destination path

    Notice that the only check of the algorithm is the code, so summary and unit will be discarded (except for bulk items creation)

• If item does not exist in path:

  • But budget item exists in document (another path), it will be copy to new destination

    Be aware that destination also depends on each budget item specification

  • Otherwise, it will be retrieved from provided remote destinations following this order:

    Item → Budget Rule → Document

  • If previous step fails but Settings allow to create bulk items, a new budget item will be created in location path with provided values
  • If last step also fails, an error will be logged for further feed-back and no more steps will be performed for this BIM element

    Depending on Settings, warning may not be visible

• Loop among all non-locked, passing BIM elements

  • If there is a similar take-off line with same values for the current BIM element, units will increment by one

    Be aware that all property values of the take-off lines must match, including those customized by you

    DASSIT™ tends to group take-off lines as much as possible. If this is not the desired behavior, just add a custom column mapping the GUID

  • Otherwise, a new automatic take-of line will be created

    Be aware that custom columns are only filled up during the cost estimating process, so, if the column is added after, running the process again is mandatory

    Another reason for empty custom column values may be the inexistance of parameter mapping for that column. If so, just define alternate mappings for the column

• If budget rule item has opening discount set, loop among all non-locked, passing nested BIM openings

  To avoid missing opening discounts, may worth to check that checkbox is on, correct filters have been added to opening discount criteria, and there is a effective BIM relationship between host and opening

  • If there is a similar take-off line with same values for the current BIM element, units will decrement by one

    Openings are computed in a negative way by default

  • Otherwise, a new automatic take-of line will be created

Context Menu

The UI control does not contain a context menu