Access to coordinate data (XYZ) data was included in Ideate BIMLink for Revit 2013 just a few years ago, in large part to address some COBie-related requests. Since then we've heard of many other creative ways in which this data is being used downstream.

For reference, Ideate BIMLink provides a variety of coordinate data, depending upon the type of object. In this example the Structural Foundation link properties includes the Point_X, Point_Y, and Point_Z data (on the right) and additional coordinate data could be added via the drop-down list under the Coordinates category (shown circled). For Structural foundation elements there are also coordinates that indicate the start and end points for those wall-based foundations.

Coordinate "point" data for Structural Foundations.[/caption] Virtual Design and Construction (VDC) managers were some of the first onboard with leveraging this newly exposed data, exporting wall, foundation and column data for construction coordination work. This was followed shortly thereafter by requests from architects who wanted to be able to identify key inflection points within complex curtain panel systems and from mechanical contractors who wanted to use total stations to located ductwork hangers.

One of the challenges of using the coordinate data with Ideate BIMLink is to report only the points you need. Yes, we can easily report the end points of the curtain wall segments or the insertion point of a pad footing, but what if we need the edge and not the centerline or what if we need all four corners of the footing?

This can be easily controlled by using a custom family that will act like a point node. By placing this family either at the specific locations within the project OR by nesting it within a family, we can use Ideate BIMLink to report only on the coordinates of the 'nodes'

In this example we've made a small Generic Model family and embedded within our pad footing. Ideate BIMLink customers who want to give this method a try may contact us to request this sample coordinate 'node' family: [email protected]

About the Author

Glynnis Patterson, NCARB - Director of Software Development Glynnis is a Registered Architect and has worked with the BIM industry since 1998. A graduate of Carnegie Mellon University, she has worked as an architect, educator and construction site manager. Glynnis is currently the Director of Software Development Services at Ideate, Inc. and continues to work with AEC clients across the nation, developing, and implementing best practices solutions. In her spare time Glynnis does volunteer work and builds Lego projects. @GVPinNJ

This question arose during a recent class:  What are the implications of changing the path to the shared parameter file within Revit?  The shared parameter file location is a system setting and is not saved within the project itself.  For this reason the path has no impact on the data that is already present within the Revit project.  There's no real risk in changing the path other than that the next shared parameter to be made will be created within this new shared parameter file(by default). 

The path to the shared parameter file.

When different companies need to collaborate on the data, this question of multiple parameter files will arise.  An alternative to making a project-specific shared parameter file is to import the shared parameters directly from another Revit file via the "Insert from File" method.  Whatever the method the list of shared parameters should be spelled out within the BIM Execution Plan.  Lastly, before you make that shared parameter, you should be certain that it is truly required to be shared!  Make an informed decision about when to share by reading this earlier post: I ♥ Parameters Thank you for reading this 2 part series on Revit parameters. 

About the Author

Glynnis Patterson, NCARB - Director of Software Development Glynnis is a Registered Architect and has worked with the BIM industry since 1998. A graduate of Carnegie Mellon University, she has worked as an architect, educator and construction site manager. Glynnis is currently the Director of Software Development Services at Ideate, Inc. and continues to work with AEC clients across the nation, developing, and implementing best practices solutions. In her spare time Glynnis does volunteer work and builds Lego projects. @GVPinNJ

Okay, I don't really ♥ parameters, and I know you don't either.  Lately we've had a lot of Ideate BIMLink customers asking us to fix their shared parameters by either merging duplicate values into a single parameter or by renaming them. While Ideate BIMLink can tackle both of these issues efficiently I thought it would make for a productive discussion to review how to avoid the problem in the first place. With this in mind, I headed to the East Bay User Group in January 2014 to tackle this issue head-on.

Some of the most common shared parameter problems surface quickly when we attempt to use content prepared for us by product manufacturers. Have you ever run into these head-scratchers?

Or this one?

These problems both relate to shared parameters and for reasons that I won't go into now are not surprising given that we are using manufacturer supplied content. Our goal for this article is to prevent this from happening within your own content in the first place.

This decision tree below shows our recommendations on how to determine whether your parameter needs to be shared or not. The risks of misusing shared parameters are great and can result in lots of wasted time, so refer to this diagram before you embark on your journey into shared parameter files.

One of the biggest misperceptions about shared parameters is that they are a requirement of a project simply because linked files are involved.  This is not true. For example, if the goal is to have the parameter value appear in a schedule and the parameter in question is an instance-based parameter then the only reason you would need to have a shared parameter, is if the value will be displayed in a Tag or Title block. Note that elements such as Rooms, Spaces, Sheets, and Views are always instance-based and therefore would only ever need shared parameters if it needs to be displayed in the Title Block or within a Tag. The criteria for a parameter to work across multiple files are EITHER that it is a shared parameter OR that it's a project parameter with the same name and the same unit (text, length, etc).  

Exceptions to this rule of thumb apply primarily to the issue of whether the parameter is desired to NOT apply to all families within that category. A classic example would be for those managing Electrical Equipment elements. This Revit category is far too broad. A PROJECT parameter such as "Transformer Width" would apply not only to transformers but also to any other family falling under the Electrical Equipment category, such as a the nurse call light family. In this scenario, a shared family parameter would be recommended to avoid this problem.

Hopefully this diagram will help you make an informed decision about your data structure and will help avoid the problems of duplicate shared parameters. I want to thank those in attendance at the East Bay User Group - it was a great discussion.  Perhaps there are now a few who may also ♥ Revit Parameters.

Check out Part 2 of this topic: I ♥ Revit Parameters Part 2: The Shared Parameter File Path. 

For in-depth consulting on organizing your data structure within Revit, contact [email protected].

About the Author

Glynnis Patterson, NCARB - Director of Software Development Glynnis is a Registered Architect and has worked with the BIM industry since 1998. A graduate of Carnegie Mellon University, she has worked as an architect, educator and construction site manager. Glynnis is currently the Director of Software Development Services at Ideate, Inc. and continues to work with AEC clients across the nation, developing, and implementing best practices solutions. In her spare time Glynnis does volunteer work and builds Lego projects. @GVPinNJ

Felipe Contier, Principal, Architect, Contier Arquitetura, Sao Paulo, Brazil explains some of a recent project's size and complexity issues. The main or master file had to be divided into different sub-files, such as "Tower," "Underground," and "Ground Level." A change to the values of any parameters in one might or might not affect one or both of the others. Before the deployment of Ideate BIMLink, the team had to copy exactly the same text in every file.

The firm needed a reliable, practical, easy and stable way to change values of parameters and copy to Families. They also needed to organize their schedules, verify values and changed descriptions.

With Ideate BIMLink, the team is able to standardize sizes, naming conventions and parameter values. Once data is standardized in Excel, the team can quickly push processed data back into the Revit model using Ideate BIMLink. This capability has eliminated confusion and errors based on different people having assigned different names for Rooms and other elements. It has also increased accuracy, since values are processed via the automated capabilities of Excel. One Ideate BIMLink use case that Contier Arquitetura provides relates to managing wall families. The wall instance and type data would need to be synchronized across at least two of the three aforementioned files - the Tower and the Ground Level.

Contier Arquitetura project using Ideate BIMLink to manage various wall families in Revit.

Felipe Contier describes the dilemma by saying, "If in the course of the project we change the description of the wall, even if the change is very minor such as adding a comma, we had to make the same change in all files without fail. If the wall description in one file included the comma, and in the other omitted the comma, the quantity take off file would appear blank with no value at all for that description."

What Contier needed was a way to link all sub-files to each other and to a master file. With Ideate BIMLink, the Contier team can explore and edit the schedules for each file.

"Ideate BIMLink is saving us time. For example," Felipe Contier adds, "We have 68 kinds of electrical fixtures. For each one of them we have a parameter in the form of a description. We have the quantity, the energy consumption, and other data. To change each parameter in one single sub-file, even if I had the text, it would take probably a half-day. When the data is in three different files, it would take much more time, something like four or five times this, so about two days."

"With Ideate BIMLink, we can change the parameters in less time, say about one hour. But that is not the most important thing to us. What is more important to us than the time savings is the guarantee that the data is correct. That is the most valuable advantage."

For the whole story on how Contier Arquitetura utilizes Ideate BIMLink in their Revit data editing, look here: Accuracy Transcends Speed for Contier Arquitetura

The most rewarding aspect of software development for me is to make things appear simple, even when they are not. Recently, in the 2014.1 version of Ideate BIMLink we implemented a feature that seems like a small thing and often times gets overlooked. The problem was simple: in Autodesk Revit some parameters allow you to pick from a list of choices, but in the export that Ideate BIMLink created our customers were finding a number. Through some trial and error by the user the meaning of the numbers could be deduced, but that was hardly a simple or rewarding task. Some examples had more than one hundred choices and the value '95' did little to inform the user that the space type was 'Operating Room - Hospital/Healthcare'. We strove to do better. 

Before BIMLink Update - Coded Space Types

The source of the problem is that Revit is available in several languages. The list of choices changes based on the language that Revit is using. As you can imagine, translation becomes an issue and there needs to be a universal meaning behind each name. To do this Revit uses numbers to store the choice, and that is how Revit shares the choice to us. It is that seemingly arbitrary number that we were then showing.

After BIMLink Update - Easily Identifiable Space Types

I took on the task of changing that number into the name that our users are more familiar with. It seemed like a simple enough task in English, but that wasn't enough. We needed it to work for all languages of Revit. It was a challenge that I took on with vigor and I am happy is included in the 2014 version of Ideate BIMLink. It may seem like a small thing, but it is the small things that make our more difficult tasks easier to bear. Let us show you how Ideate BIMLink can improve your workflow: download the trial version of Ideate BIMLink.

About the Author

Jesika DiGregorio - Software Team Lead Jesika received her Bachelor of Architecture from the University of Oregon in Eugene where she also spent time studying advanced math. Her work experience includes Junior Designer at an award-winning firm specializing in architecture and land planning, and Intern Architect at a firm that provides services in planning, design, construction documents and construction administration for projects of all sizes. After working in architecture design for several years, Jesika decided to pursue her interest in programming and her love of efficient systems. She now serves as a Software Team Lead for Ideate Software.