Revit OpEd: Revit 2017 - Calculated Values in Tags

Revit OpEd: Revit 2017 - Calculated Values in Tags: This addition permits us to do the same thing to tags that we've been using in schedules. For example, in a tag I'd like to show the...

Evacuation Path Analysis with Dynamo and Revit

Report from BIM Toolbox

04/22/2016

Evacuation Path Analysis with Dynamo and Revit

More and more we face challenges to find new ways to perform custom architectural analysis. In this post I want to share with you a short and simple (for once) Dynamo script that can be used to analyze the evacuation paths in your building design in Revit. The script (that you can download at the bottom of this post) will calculate the accumulated distance from several points to a selected emergency exit and display the results in a selected Revit view.


A detailed explanation and full script and dataset can be found on this link.
Dieter Vermeulen

Revit OpEd: Revit 2017 - Text Editor Features

Revit OpEd: Revit 2017 - Text Editor Features: Long awaited, much rejoicing was heard when Revit users heard the news, there is a new text editor. Really? Can it be true? Yes they've ...

Combining the Power of ITO with a Model Comparison Check

From the Solibri blog.

In addition to using the Model Comparison Ruleset to compare model versions, this article defines the steps to create an Information Takeoff (ITO) that displays the changes in Quantities in the ITO table format. This allows for easy review of any changes in the model quantities, in real-time.

A model recreating the screenshots and model conditions in this article is available here: SMC Building – ITO Model Comparision.smc

For tutorial information about using the ITO tool, please see our previous article on the topic:  Understanding Information Takeoff (ITO)

In Solibri Model Checker, with two different IFC versions of the same model loaded, create an ITO sorting the model by Components. ITO sorts elements within the model by the values of their properties of the left most columns.

Now, create an ITO column for the “Model” property of the “Identification” column type and ensure that “Grouping” is checked.  By doing this, ITO will create an individual row for each type of component in each model.  In other words, one type of component will be listed twice: one row representing the component(s) in Model A, and a second row representing the component(s) in Model B.



Next, decide which quantities are relevant for the comparison.  In this example, we have added columns for length, width, height, area, volume, and count.  For each column, ensure that “Grouping” is turned OFF, and the function is set to “SUM”.  This means that ITO will not use these columns as a sorted grouping mechanism and that the quantity displayed in the column will be a sum for the components.



The resulting ITO will resemble the results below.  Each Component type is listed on two rows, representing the components and their quantities from each of the respective two model versions.



Please use the example model to explore the screenshots from this article, and to experiment with the settings in ITO.

Revit OpEd: Revit 2017 - New Features and Enhancements

Revit OpEd: Revit 2017 - New Features and Enhancements: Long Post Warning, worth it I hope. Last night I was able to download and install Building Design Suite 2017 from my Autodesk subscription...

New COBie for Navisworks tool now available

Over at Beyond Design, they have an interesting blog post on the new COBie tool for Autodesk Navisworks. Even if you don't intend on using Navisworks as part of your COBie delivery process, the post is interesting.

Model Checking - What Tools Do You Use?

Working on updating my Modeling checking presentation for RTC EU. There are a lot of good model checking tools on the market including but not limited to:

• Autodesk Revit Model Review
• Autodesk Model Checker for Revit
• BIMAssure
• Assemble Systems Insight
• Solibri

I am interested in hearing about other tools that people might be using for model checking in addition to those listed above.

Revit OpEd: Space Naming Utility for Revit 2017

Revit OpEd: Space Naming Utility for Revit 2017: Hi Autodesk Revit Team! It's me Mr. OpEd again. Imagine me with a pointy stick , I'm poking you in the eye...metaphorically...with ...

BIM in the Field

I have been looking for cost effective ways to bring BIM to the field wondering what options other people have found.

I have used Glue in the past, but it's very expensive. While I have not used it, I do have some colleagues that are using the MS Surface successfully. But I don't own a surface and not very many of those on the jobsite.

What have you used and what are the pros and cons?

Model Review - What's in the Model

During a visit with a client this morning, I was reminded on a common task we perform to review models. One of the first things I like to do when reviewing models is see how the Revit sheets were put together. Is the geometry from model elements, Revit's 2D elements or CAD.

Our process is very simple. We simply compare the original sheets provided by the designer to sheets we create out of Revit after we get rid of any linked CAD files, CAD imports and Revit's 2D linework. We then use the power of Bluebeam to compare the two sets of PDFs. Bluebeam will highlight the differences between the two sets of PDF's.

Why is the beneficial? It really depends on how you intend to use the model.

I have seen a lot of "BIM jobs" that have sheets that have been exported out of Revit and "embellished" in AutoCAD. The embellishments are very interesting as this can be anything from adding new callouts to altering the geometry. Using this PDF compare method will quickly allow you to see what is from the model and what is from elsewhere.

This process can be done very quickly. In 15 minutes you can determine how deep you need to dive into your Revit model review.

Navisworks 2016 Database Link w/ MS Access - Primer

In a previous post, I discussed the process of connecting a external data source (Excel) with a Navisworks model. In this post, we will connect an MS Access database with a Navisworks model. As before, I’ll walk you thru how to setup the database link. For this demo, I am going to use the Gatehouse sample file that ships with Navisworks 2016. You can find the files C:\Program Files\Autodesk\Navisworks Manage 2014\Samples\Gatehouse\

The Process

In order to connect an Access database to a Navisworks model, we need to configure a DataTools within Navisworks. We will then be configuring the database connection. When working with the DataTools in Navisworks, there are a few very important rules to keep in mind. If you are using a 32-bit workstation, then you need to utilize the 32-bit ODBC drivers. 64-bit workstations need to utilize 64-bit ODBC drivers. It is also important to note, that the link to Navisworks is one way. Data can be linked and viewed inside of Navisworks, but the data can’t be updated within Navisworks.

My workstations are all Windows 10 64-bit workstations. My PC’s are using Microsoft Office 365. My Mac running Windows 10 64-bit on parallels using Office 365. The MS Access 2013 runtime drivers can be downloaded here: https://www.microsoft.com/en-us/download/confirmation.aspx?id=39358 If you are using an older version of office the MS Access 2010 drivers can be downloaded from here: https://www.microsoft.com/en-us/download/details.aspx?id=13255.

Data Source

The Gatehouse project includes a sample MS Access database which is why I am using it as an example

Figure 1 - Data Source with column labels

Our next step is to open Navisworks and the Navisworks model that you want to connect your external data source to. In Navisworks, on the Home tab, Project panel, click on the File Options button (Figure 2). This will open the File Options dialog.

Figure 2 – Accessing the File Options

In the File Options dialog, we will start the process of configure our database connection (Figure 3). As shown in Figure 1, click the DataTools tab and then click the New button to create a new DataTools link to open the New Link dialog.

 Figure 3 - File Options dialog for creating a new DataTools link

In the New Link dialog (Figure 4), we first want to name the new link connection we are creating. For this example, I am using the name “Gate - MS Access Connection”. We then need to select the ODBC Driver Connection type. We are going to be working with a MS Access data source, so select the “Microsoft Access Driver” driver.  Then click the Setup button to open the ODBC Microsoft Access Setup dialog.

Figure 4 - New Database Connection Link dialog

In the ODBC Microsoft Access Setup dialog (Figure 5), we will select the MS Access data file and select the file we will be using. If you have the default installation of Navisworks 2016 and are using the Gatehouse example, you can find the file at: C:\Program Files\Autodesk\Navisworks Manage 2016\Samples\gatehouse\. After you have selected your MS Access file, click OK to close the ODBC Microsoft Access Setup dialog.

Figure 5 - ODBC Setup Dialog for MS Access

We are now back to the Edit Link dialog box (Figure 6). If we look in the connection section portion of the dialog, under the ODBC Driver selection, you can see that the connection has been updated. We can now complete the SQL String and Fields section of the dialog.

Figure 6 - Edit Link

The SQL string is used to specify how the database will be queried. I have found this part of configuring the database connection to be the most difficult. Fortunately, there are a lot of external resources available for creating SQL strings. My personal recommendation is to keep it as simple as possible.

The code that we will be creating for this example is:
SELECT * FROM Gatehouse_Layerinfo WHERE "Name" = %prop("Item","Layer");

We start out our SQL String with SELECT * FROM The “*” is actually a field name, in this particular example, I am using the wildcard to query all the fields.

Gatehouse_Layerinfo This is the MS Access table name (Figure 7) that we want to query.

Figure 7 - MS Access Table

 
WHERE "Name" = %prop("Item","Layer"); This is where we are going to define what data we are going to bring from the MS Access tbale into Navisworks. For our example, we are going to conditional match the value Layer property data for each element that can be found in the Item tab and match that with a value in the Name column of the MS Access table.

“Name” refers to column that we will be searching.
%prop is a SQL command that allow you to retrieve model data for conditional matching.
("Item","Layer"); “Item” refers to the Item tab in the Properties Window. “Layer” refers to the internal file property, in this example, the Layer (Figure 8).

Figure 8 – Navisworks Properties Window

In the SQL String section of the Edit Link dialog, enter the following string of text.
SELECT * FROM [Gatehouse_Layerinfo$] WHERE "Name" = %prop("Item","Layer");
The next step in the process is to specify what information we are going to display in the Properties window. In the Field section of the Edit Link dialog (Figure 9), we are going to specify what Field names to list and the display name to use. Using Figure 9 as a reference, add the Field and Display Names.

Note that we are having the Field Name “Name” display as “Layer” in Navisworks. The Name column in our MS Access table refers to an AutoCAD Layer and rather than changing the column name in MS Access, we can have Navisworks use a different Display Name.

Figure 9 - Inserting Field and Display Names

After you have entering the Field Names, click OK to close the Edit Link dialog box. Make sure that the “Gate - MS Access Connection” DataTools Link that we just created is checked. This will enable it in our current session. Click OK to close the File Options dialog.

Figure 10 - DataTools

When you select an object in Navisworks, note that the Properties Window has a new tab called “Gate - MS Access Connection”. That is the name of the DataTools link that we created. Figure 11 shows an example where we have selected the roof and in the Gatehouse tab in the Properties window provides us with the Layer, Finish and Note information from the Excel data file.

Figure 11 - Roof Selected with External Data Displayed

If you have gotten this far and it is not working, a lot can go wrong. The first thing to check is the SQL String text. Then check to make sure that your using the correct version of MS Access, which might be different than the selection, I made in Figure 5. Also, make sure that the MS Access file you are trying to access in Navisworks is not open. That can cause issues as well.

This Gatehouse example is not the most robust example around, but it is a great starting point. Start with something simple so you can make sure that your database connection is working, before trying it on a more complicated project with a lot of data to query. As many of you are aware, CAD and BIM applications are not great data entry applications, so having this type of data linking capabilities is very beneficial.