Question of the Week – DESTINI Estimator: How can I delete links from my Recent Estimates folder in Estimator?

Question of the Week are asked and answered in the Beck Technology Community. Anyone is encouraged to join the community to discover additional tips and tricks.

Here is a quick video showing users on how to clean up their Recent Estimates folder in Estimator.

How to delete files from the Recent Estimates folder in Estimator

Question of the Week – DESTINI Estimator: Why are my costs showing up in both the Mapped and Unmapped node of the filter tree when I am comparing cost in my BIM360 models?

Question of the Week are asked and answered in the Beck Technology Community. Anyone is encouraged to join the community to discover additional tips and tricks.

When models are created with assemblies, it can be tricky when you are trying to tie cost to that assembly. We have found one of those situations in our BIM360 Comparison Window that our users should be aware of. When you have components (children) making up an assembly (parent), you may see cost showing both the Mapped and Unmapped filter tree of an estimate in the BIM360 comparison window.

This happens because the compare actually works at the assembly level (parent) while the component you selected works at the geometry level (children) in that window. Therefore, if you are associating cost to only one part of the assembly, you might be confused seeing the cost also associated with the other component associated with that assembly when you look at the filter tree.

However, in the estimate window you will only see the line item/s that cost were added to.

Here is a video showing that comparison: BIM360 comparison window cost issue

Question of the Week – DESTINI Estimator: How do I bulk add line items to the staging area?

Question of the Week are asked and answered in the Beck Technology Community. Anyone is encouraged to join the community to discover additional tips and tricks.
As we continue to improve and upgrade Estimator, we review our enhancements requests list and add some of these to the product. One of the enhancements that we added to this release is the ability to bulk add cost. Estimators now have the option to add entire folders (WBS values) of costs to the staging area allowing for much faster and easier addition of large amounts of related costs to an estimate at one time.

Take a look at this video to see how that can be done for both Line Items and Assemblies.

 

Question of the Week – DESTINI Estimator: Can I use a custom formulaic WBS property to calculate a group summary based on a selected meta data field?

Question of the Week are asked and answered in the Beck Technology Community. Anyone is encouraged to join the community to discover additional tips and tricks.

For anyone else trying to accomplish something like this, the attached images provide a good interim solution to solve this particular issue.



Question of the Week – DESTINI Estimator: Can I edit over-line totals?

Question of the Week are asked and answered in the Beck Technology Community. Anyone is encouraged to join the community to discover additional tips and tricks.

Estimators can now edit over-line totals for any group defined in the Estimate View.  This will automatically back into an escalation for that group of items.  This enhancement further supports Estimators ability to handle sub-contractor bid values and bid leveling.

Check out this video on how that can be done: Overline Editing video

 

Question of the Week – DESTINI Estimator: What does Update, Unhook, and Remove mean in the 3D model comparison window?

Question of the Week are asked and answered in the Beck Technology Community. Anyone is encouraged to join the community to discover additional tips and tricks.

Update means the line item stays connected to the component and mapped variables get updated with the new values from the component.

Unhook means the line item stays in the estimate with its current quantity but it is no longer associated with the model component in any way and will not get new values.

Remove means the line item is completely removed from the estimate.

For components that are removed from the model, Update has the same effect as Unhook.

 

 

Question of the Week – DESTINI Estimator: How do I set up a default whitelist and share it with other users in my firm?

Question of the Week are asked and answered in the Beck Technology Community. Anyone is encouraged to join the community to discover additional tips and tricks.

The basic idea is that each model will have a specific set of data based on its source (i.e. Navis, Revit, IFC, etc…).

My method is to create a whitelist for each source that I think I may deal with.  I do this by opening the model in BIM 360 proper and opening the properties of the objects in the model.  I make sure I look at a couple different objects (specifically the ones that I plan to use in my QTO) and I see what properties / categories have the information I am interested in and I add them to the whitelist.  It usually takes me about 5 or 10 minutes to create a good whitelist.”

The whitelists are all saved in one single “bulk file” now, a JSON file type, the %appdata% file path.

You can edit any whitelist in Estimator and the changes will be pushed to this file – or you can open this file and work in a notepad environment to accomplish the same. This makes it easy for you, as a super user, to build out the whitelist(s) that work for your people, based on source data type, and push it to their appdata folder.

Sharing this JSON file is as easy as copy/pasting it into their machine. Whether that is manual or via scripting is up to you.

Question of the Week – DESTINI Estimator: How do I QC a 3D model?

Question of the Week are asked and answered in the Beck Technology Community. Anyone is encouraged to join the community to discover additional tips and tricks.

Great question for the community, Doug.  Admittedly, this is a challenge stemming from new model-based workflows that we are not yet used to working.  But we are seeing some things that will ultimately help us establish a best practice.  Much of what I am implementing stems from having to QA/QC someone else’s DESTINI Profiler models and estimates. So we have some precedent to help us understand the model-based workflow.  What I am finding is that there is a three-step approach that seems to help us ensure we have covered all the bases.

1) The first step is to ensure that the estimate provides 100% coverage of the scope of the project.  This is no different than QA/QC’ing someone’s traditionally-derived estimate. It helps if the estimate can be organized by a familiar group structure (i.e. CSI or Uniformat) so to serve as a checklist or guide.  So, for the first step, I am simply reviewing the estimate to verify scope coverage by the estimate cost items for each major division.   My next concern deals with validation of quantities, but now, instead of verifying against 2D quantity takeoff values, we need to validate quantities from the model.  This takes us to step 2.

2) The second step involves verifying that the quantities in each line item make sense.  This applies regardless of where the quantities come from. We don’t want to forget estimating basics just because our workflow has been modified.  For any line item whose quantity source needs to be verified, select on the row header for the line item and select the “Review Takeoff” command.  This will reveal the source of the line item’s quantity and whether it has been hard-coded, or whether it has been tied to a model component variable, such as Area or Perimeter, or some combination of the above. (Note: If you are only concerned about quantities derived from the model, then it might be helpful to use the “Is-Mapped” field as a major grouping field in the Group Panel.  Once a quantity source has been verified, then we can work to locate the quantity and understand how it was derived.  Which takes us to step 3.

3) The third step includes “interrogating” the model to understand how a specific quantity was derived.  For example, if my estimate shows the slab on grade tied to an “Area” variable value, then I might want to investigate that Area value in the model to ensure it picks up all relevant slab areas.  For this, I will switch over to the Takeoff View and begin to evaluate model components.  I’ve found that creating a proper Filter grouping is key here,  and often set up the filter grouping on “Is-Mapped” followed by one or two other common value across all model components (i.e. Assembly Code and/or Identity Data – Type Name), and then end on “Component Name” so that I can get down to the level of the individual model components.  In this example, I would isolate the slab on grade and ensure that value for the area of the slab component matches the one that was linked in the line item.

So far, I have found that repeating this process is a solid work-flow for QA/QC’ing an estimate tied to a 3D model.

 

Question of the Week – DESTINI Estimator: Where do I save a custom report so that it is accessible from the Report drop-down menu?

Questions of the Week are asked and answered in the Beck Technology Community. Anyone is encouraged to join the community to discover additional tips and tricks.

1) Select the new report file, and cut or copy it from the current location

2) Go to a Windows File Folder

3) Type %programdata% in the address menu and press Enter

4) Select the DESTINI Estimator folder

5) Select the Custom Reports program

6) Save the file in this folder, and it will be available via the drop-down menu in the Reports commands

Question of the Week – DESTINI Estimator: Can I turn on a legend in 2D takeoff drawings?

Questions of the Week are asked and answered in the Beck Technology Community. Anyone is encouraged to join the community to discover additional tips and tricks.

Can I turn on a legend in 2D takeoff drawings?

Select your Takeoff view in the ribbon – notice the Reports tab in dark blue that appears?

Select that view, and you’ll be able to turn on your legend and format its appearance:

You can choose whether a takeoff condition has to be totally contained within the view to show in the legend, or if “partial components” should be listed.

It’s that easy! For more information on printing 2D Takeoff, click here.