Revit OpEd: Revit MEP 2014 - Reapply Type

Revit OpEd: Revit MEP 2014 - Reapply Type: This button snuck past me in my reading about what's new. I don't see anything at all about it in the What's New documentation a...

Redlining & Revit

Regardless what you think about Revit, you’ll probably agree that Revit is disruptive technology. You can push rope and try to adapt CAD functionality to Revit or you can adapt/change your workflow to accommodate Revit’s workflow. This process change, good or bad is disruptive. The choices you make can mean the difference between profit and lose on a project.

One area that Revit provides that opportunity for process change is with Redlines. With Revit and Design Review we have an opportunity to create and manage redlines differently than what has been done in the past. This does not mean that the  Revit/Design Review process is better or worse, it’s just different.

Pen & Paper / Redlined PDF

Traditionally redlines have been created using red pen on paper and that gets passed off to someone to get picked up. Those redlines can be scanned and a PDF created or electronic documents can be marked up electronically and passed onto someone to get picked up. As the person picks up the redlines they may or may not highlight which items have been picked up. At some point, we hope that someone then back checks to make sure that the redlines were picked up and addressed correctly.

There are many pros and cons to this workflow. On the Pro side, it is a workflow that is familiar to most users and good or bad, familiarity makes people more comfortable. The Cons to this workflow is that the redline is not integrated into Revit like an overlay, it’s external.

Revit / Design Review

An Alternate workflow to creating and managing redlines is to utilize the Deisgn Web Format (DWF) as a distribution and communication of redlines. DWF files are in many like PDF files, but you use the Design Review application to markup the documents electronically and those redlines/markups can then be linked back into Revit as an overlay. As the markups are addressed, comments can be added.

Before I go into the process, let’s talk about the CONS to this approach. The BIG CON is that DWF markups have to be created digitally using Design Review. It’s been my experience that the drawback is with people learning to digitally markup drawings rather than using pen on paper. In fact, I’m guilty of it. If I have a choice, pen on paper is my preferred method as marking up with the mouse sucks. There is an improvement though when working with a tablet, especially one of the higher end models like the Wacom Cintiq pen displays.

Workflow

The first thing we need to have to create markups in Design Review with DWF files is Sheets in our Revit model. Revit allows you to export sheets and views to either a DWF or DWFx file type. Now is probably as good a time as any to explain the difference between a DWF and DWFx file. DWFx allows you to export the 3D model and any associate parameter data associated with the objects. DWF/DWFx can be used to export sheets and views to a file.

If you want to use the DWF file to roundtrip redlines (Revit to Design Review to Revit) then you have to export sheet. When we have sheets, we can then export DWF file. From the Revit application button (Big R) select Export > DWF/DWFx.

Figure 1

The DWF Export Settings dialog (Figure 2) will open and this allows us to specify what sheets/views we want to export and to adjust DWF/DWFx export settings. In the View/Sheets tab, select the from the Export: dropdown. From the Show in list: dropdown, select Sheets in the Model, this will allow you to select from just the sheets in the model. Select all the sheets.

Figure 2

After you make your selection, you can save your selection for future use by using the New Set button as shown in Figure 3.

Figure 3

Click the Next button to save your file and export your sheets. The exported DWF file can then be opened in Design Review and your markups added.

Design Review is very similar to Acrobat or Bluebeam. There are tools to make it comments, redlines, measure, query, etc. They are very straightforward and simple enough to use.

Figure 4

As you make your redlines, Design Review keeps track of those markups. Figure 5 shows an example of some markups. Notice the second column of symbols that I have highlighted in Figure 5. These show the status of the markup. The outline of a checkmark means no action has occurred to that markup in Revit. A green checkmark means the markup has been marked as Done. The question mark means that markup has been marked with a question.

Figure 5 - Markup Tracking in Design Review

This markup tracking system helps everyone associated with the redlines keep track of what has been done, what needs to be done and what items need further clarification.

Once you have marked up the DWF file in Design Review, we can link it back into Revit. We Link in a DWF markup set like we would a Revit or CAD file. From the Inset tab, link panel, click on the DWF markup button (Figure 6). This will open the Import/Link DWF file dialog. Navigate to the location of your DWF file and then select Open.

Figure 6 - DWF Markup button

The Link Markup Page to Revit Sheets dialog (Figure 7) will then open. On the left side (DWF View) of the dialog will be a listing of those sheets that have markups from Design Review. It will only list the sheets that have markups, sheets with no markups are not listed. The right side (Revit View) of the dialog will display the Revit sheet that corresponds to the DWF view.

You want to make sure that you review this dialog very carefully. If you have renumbered, added or deleted sheets since the DWF file was created, it is possible that Revit could list the wrong Revit View for a DWF View. I have not had this occur, but something to keep in mind.

Also be aware that if you select a sheet on the DWF View side and then click OK to the Link Markup Page to Revit Sheets dialog, Revit will only link that single selected DWF View.

If your view(s) correspond correctly, you can click OK to start the DWF linking process.

Figure 7 - Link Markup Page to Revit Sheets dialog

Once your DWF file(s) have been linked into Revit, we need to find which sheets have them. Revit currently doesn’t allow us to generate a schedule to easily locate and track them, so we have to do a little digging if you don’t want to open the Design Review file.

The easiest method to find your markups is to open Manage Links (Insert tab, Link Panel) as shown in Figure 8 and make the DWF Markups tab active.

Figure 8 - Linked DWF files

Select anyone of the linked files. Then at the bottom of the dialog, click on the Located In… button. This will open the Link Markup Page to Revit Sheet dialog (Figure 7) and you can use that to make note of what Revit sheets have markups. In this example, the project file I am using only have 5 sheets so tracking done the markups is not that difficult. However on a real projects, you definitely do not want to go sheet-by-sheet looking for redlines.

We can now navigate to one of our markups in Revit. Figure 9 shows an example of a markup. When you select a markup the Properties palette will provide you with some basic information about the markup as well as giving you the options to change the status of the markup. In the example shown in Figure 9, I clicked on the History button in the Properties palette and is gives me basic information about the history of that particular redline.

Figure 9 - DWF markup in Revit

If I click on the Notes button in the Properties palette, the Edit Text dialog will open (Figure 10). This allows you to add notes, comments or questions that you might have regarding a particular markup. Figure 11 shows how that Note appears in Design Review.

Figure 10 - Associating a Note with a Markup

Figure 11 – Note from Revit

When you save your Revit project file, any changes to the status of the DWF is automatically saved to the DWF file.

The great thing about using DWF files for processing markups is that they are easily tracked and they markups are an overlay to the Revit sheets. If you can get over the hump of marking up digitally, then using DWF files can make your life easier.

Revit OpEd: Five Minutes Working with Rotated Views

Revit OpEd: Five Minutes Working with Rotated Views: A common question from people with experience using AutoCAD is, "Does Revit have a UCS too?". There isn't a literal equal tool...

CloudsCarsCameras: Using Bluebeam Revu to assist in upgrading a Revit Project

Saw this post on CloudsCarsCameras.com that I thought I would share with you. Great idea.

Posted on July 7, 2013

Using Bluebeam Revu to assist in upgrading a Revit Project

With a new release of Revit every year, it makes it increasingly difficult not upgrade an active Revit project.  What makes it even more difficult is the uncertainty when Revit upgrades your project.  Are all my objects there?  Is everything in the right place?  In this post and video we are going to go thought the steps to upgrade your Revit project from 2013 to 2014. Then we will use Bluebeam’s Revu to help us find any items that may have changed or gone missing after the upgrade process.


If you want more information regarding Bluebeam please drop me a note at bill@bim9.com

Here are the steps I use in the video:

Step 1  Backup

You should always create a backup of your or your companies work when ever you make a change that will impact the entire project, this would be one of those times.  Here are some ways that you can backup your project:

• Copy to local workstation
• Copy to USB drive
• Rely on your I.T. department to have a backup.
• Use a service like CrashPlan or Dropbox to copy your project files off site.
• You only need to archive/backup the .RVT files and its links.

Step 2  Check your Project

You should always check each central file before the upgrade process. It is always a good idea to know what errors are in the file before you begin the upgrade process.

1. Open each .RVT file and check for errors.
2. Document what files are linked to where.
3. Use Bluebeam to create a PDF of each sheet and view in your project.

Step 3  Copy the Project to a new folder

You may or may not want to have a new folder for you project, but I find that its a good idea to do so.  you don’t need to make an entirely new project folder just a new folder to store your central files.

1. Create a new folder.
2. Copy the RVT central files to that folder.
3. Rename the central files if necessary to have the version number in the name.

Step 4:  Upgrade Project

1. You will want to start with the files with the least amount of links.
2. Here is the order for my example project:
   MEP
   Structural
   Architectural
   Site
3. Use Bluebeam to Create a PDF of each sheet and view in your project.

Step 5   Check your work with Bluebeam

Now for the fun part; we will use Bluebeam Revu to compare both PDF files created in the earlier steps.

1. Use Bluebeam Revu to compare the 2013 and the 2014 project files.
2. When you select the 2013 PDF you will see all the changes in the Markup List.
3. Double click the markup to see both the 2013 and 2014 versions.
4. Using Bluebeam Revu you can quickly find all the differences.

If you want more information regarding Bluebeam please drop me a note at bill@bim9.com

CASE apps

I am a real fan of the CAD apps. They offer some unique tools that can really save you a lot of time and frustration. Even better, many of them are FREE. If you read RevitOpEd (and who doesn't) then you have heard Steve discuss the CASE apps as well. Check them out here

Revit OpEd: Revision Numbering

Revit OpEd: Revision Numbering: A month or so ago I received an email from a friend asking about dealing with revision numbering in Revit. Apparently the project team is ex...

Revit API Wishlist - Repost from the Revit Clinic

Wish upon a Revit

Our friends over with the Autodesk Developer Network have recently launched the Revit API wishlist survey.  This is a great chance to provide feedback on the future of the Revit API and let your voice be heard.
The survey is open till June 15th 2013.  Head on over the the AEC DevBlog for more info here.

Navisworks Database Link - Primer

One of the things I like about my job is that is the clients I get to interact with. Their needs and challenges are different which makes the job very interesting. Today one of my clients needed to connect database information with their Navisworks models. This is essentially a FM exercise as the data about the equipment is stored in the database and the geometry is in Navisworks. Fortunately, Navisworks provides the means and method to do this, if you can make heads or tails of the process. So lets go thru the process.

For this demo, I am going to use the Gatehouse sample file that ships with Navisworks 2014. You can find the files C:\Program Files\Autodesk\Navisworks Manage 2014\Samples\gatehouse\

The Process

In order to connect an external data source such as an Excel spreadsheet 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.

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 7 64-bit workstations. My PC’s are using Microsoft Office 2007 or 2010 64-bit. My Mac running Windows 7 64-bit on parallels using OpenOffice. I have only been able to make the Navisworks database connection work using 64-bit database drivers. You can download them for free from: http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en. Make sure that you have download and installed these drivers.

Data Source

The Gatehouse project includes a sample Excel spreadsheet. The first thing I did to the file was add three column headers to identify the “Name”, “Finish” and “Notes” columns (Figure 1). We are creating these labels to identify the columns.

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 “Gatehouse Example”. We then need to select the ODBC Driver Connection type. We are going to be working with a Microsoft Excel data source, so select the “Microsoft Excel Driver (*.xls, *.xlsx, )” driver.  Then click the Setup button to open the ODBC Microsoft Excel Setup dialog.

Figure 4 - New Database Connection Link dialog

In the ODBC Microsoft Excel Setup dialog (Figure 5), we will select the version of Excel data file and select the file we will be using. The sample data file that we are using is a Excel 97-2000 version so select “Excel 97-2000” from the Version: dropdown. Then click on the Select Workbook button to find and select the Excel data file. If you have the default installation of Navisworks 2014 and are using the Gatehouse example, you can find the file at: C:\Program Files\Autodesk\Navisworks Manage 2014\Samples\gatehouse\ After you have selected your excel file, click OK to close the ODBC Microsoft Excel Setup dialog.

If you are having issues with your Database Link connecting to Excel, be sure to check the Version of Excel database that you are using.

Figure 5 - ODBC Setup Dialog for Excel

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

SQL String

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 Excel sheet tab name that we want to query in our Excel spreadsheet. The Excel sheet tab name must be spelled just as it is in Excel and should be followed with the “$”.

WHERE "Name" = %prop("Item","Layer"); This is where we are going to define what data we are going to bring from the Excel spreadsheet 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 colum of the Excel spreadsheet.

“Name” refers to column that we will be searching in the Excel file.

%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 7).

Figure 7 – 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 8), we are going to specify what Field names to list and the display name to use. Using Figure 8 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 Excel spreadsheet refers to an AutoCAD Layer and rather than changing the column name in Excel, we can have Navisworks use a different Display Name.

Figure 8 - Inserting the Field and Display Names

After you have entering the Field Names, click OK to close the Edit Link dialog box. Make sure that the “Gatehouse Example” 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 9 - DataTools

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

Figure 10 - Foundation Selected with External Data Displayed

If you have gotten this far and it is not working, a lot can go wrong. I think setting up the DataTool link can be as complicated and frustrating as using Timeliner. The first thing to check is the SQL String text. Then check to make sure that your using the correct version of Excel, which might be different than the selection, I made in Figure 5.

This Gatehouse example is not the most robust example around, but it is a great starting point. 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.

Revit Tips and Tricks - Re-arrange a Ribbon Tab

One of the questions I get somewhat frequently is about re-arranging the Ribbon tabs. Yes, you can re-arrange the tabs on the ribbon by holding down the CTRL key and then dragging the desired Tab to a new location.

Navisworks 2013 - Importing Search Sets

From time to time I will be asked how to utilize a Search Set from a previous project in Navisworks. So I thought I would quickly post the steps.

In Navisworks 2013, switch to the View tab and select the Windows dropdown in the Workspace panel. Make sure that the Sets checkbox is checked. This will open the he Sets dialog box where you can import/export search sets.


 By clicking on the icon indicated above, you can export or import search sets.

All Things BIM: SmartMarket Report on BIM 2012

All Things BIM: SmartMarket Report on BIM 2012