Skip to:



 

Escalator - Going up?

March 19th, 2008

Escalator render

 

When the escalator question was put to us a short while ago, we took time to scout around and see what was already available in one form or another. But what we found didn’t really float our collective boat. We certainly saw some very pretty models, make no mistake about it, but they were lacking something… Steps for one, along with the point and click ease which we rely on so often and almost take for granted in the program we all hate to love: Revit.

So we gathered round the table, coffee or tea in hand, depending on national preference, and asked ourselves: What would we want from an escalator family? To which we replied:

  - Automatic sizing between levels
  - Steps

Doesn’t seem like too much to ask, right?

Not so fast. Getting a model, one built in a Mechanical Equipment Template, to auto-connect between floors is easier said than done. So we searched for a while, and finally found a template that auto-leveled. We did a few tests, and realized that it could work. There were a few false starts, however, as we discovered that putting any kind of dimension in between the levels completely negated the template’s auto-leveling abilities. So we made the top and bottom landings on their appropriate planes, and had the rising structure of the escalator as a sweep, locked at an angle to the horizontal plane, with the end points of its path locked to the two levels. Worked like a charm.

Escalator in-product screenshot

 

Next came the introduction of the steps. In previous escalator models, we had access to the vertical distance between levels and the horizontal length of the model as family parameters, which made step numbers and placement a simple application of your old friend Pythagoras’ theorem. Alas, in the all-singing-all-dancing auto-leveler, we didn’t have access to any of the lengths - horizontal, vertical or diagonal. Why not? Because just like with the space between levels, attaching dimensions to any one of the lengths broke the automation.

Again, there was much discussion and drinking of hot beverages.

Then a member of our team had an epiphany: There is one type of family that doesn’t need a length dimension. If you just click and draw a line, the family repeats itself along it ad infinitum. The Generic Line Based Family! This led to some preemptive rejoicing, as we ended up having to re-build and re-nest the Line Based family a number of times to actually get the thing to work.

Escalator wireframe

 

In our first attempt, we thought we were being clever and seeing problems before they occurred. We said to ourselves, “If the line is going to follow the rising sweep of the escalator, and we build the steps flat… they’ll make a segmented slide, and we don’t want that!” So we built the steps at an angle with the tread of each step 30° from the horizontal, from the path of the Line Based Model. Didn’t work.

Looking back, a little pre-testing should have been done. The steps were indeed at an angle, but in a line stretching horizontally from the base of the escalator backwards, into the distance, and never rising from that plane. Apparently, the Generic Line Based model’s path doesn’t like being hosted on geometry, and without any major planes built between levels, there was nowhere other than lower level plane to draw it.

We needed a quick re-think, again. This time around we found our answer, one that now seems almost obvious. We built the steps rising from the path in the Nested Generic Line based model. “Of Course,” we said, slapping out foreheads at the simple logic of it all. From there, we nested the family’s reference planes in place, and it was all-systems-go. Buy & Download this Revit Escalator Family.

Jonathan Lloyd
BIM Modeler

 

1 Star2 Stars3 Stars4 Stars5 Stars (21 votes, average: 2.9 out of 5)
Loading ... Loading ...

Presenting the Zee

February 26th, 2008

Zee render

 

We recently received a request to model the Artis Zee Biplane System, and quickly discovered this was not your run of the mill Revit family. Made by Siemens, the Artis Zee Biplane is a cutting-edge, robotic, medical diagnostic device consisting of a bed, a display arm, a ceiling mounted C-arm, and a base C-arm. The arms, or Zees, as Siemens calls them, are each made up of multiple pieces that rotate or spin along different axes, which allows for tremendous freedom of movement. The bed can also rotate around three axes. And of course our client wanted the ability to freely arrange each element’s position. So we’re talking parameters, parameters, and…more parameters.

Zee in-product screenshot

 

Zee parameters

 

“Congrats to you and your team for making such a complex model. The manual is also incredibly helpful for understanding how the parameters have been set up.”

Luckily for us, we have an outstanding team of modelers that more than rose to the occasion. They built the system as one family with four nested files. Since the requirements were to make the Zee system fully movable while still looking great rendered, small file size wasn’t a priority for the client. We first modeled the reference lines laced with their appropriate parameters to act as an “armature” for the geometric model.

The main obstacle during the modeling process proved to be the Zees’ electrical conduits, which were supposed to hang freely depending on the movement of the arms. Making smooth curved geometries that change shape through parameters does tend to be difficult in Revit. More so when those changes are angular rather than linear. After some brainstorming, followed by some trial and error, it was decided that to ensure problem-free movement, the cables should have limited movement; they would stay beside their corresponding arms to avoid parameter errors.

Once the separate families were ready (Zee arms and display arm), they were nested inside the bed family. Their parameters were then linked and materials assigned, completing the family for delivery to the client.

The process of building a complex family like the Zee reinforces some basic principles of successful modeling:

1. Make sure you create families on the right plane

2. Name the reference planes explicitly

3. Flex, flex, and flex again

With its multiple free-moving parts, the Artis Zee Biplane was certainly a family more challenging than most. But in the end our modelers really shined and we came away quite happy with the results. This request gave us the chance to experiment with some new techniques, and to create what we feel is a truly beautiful Revit family.

Cristobal Bernal
Project Manager

 

1 Star2 Stars3 Stars4 Stars5 Stars (19 votes, average: 2.68 out of 5)
Loading ... Loading ...

Older Posts

Packs 101

January 30th, 2008

People keep asking me about our new Family Packs and how they work - what they cover, how long they last, etc. I was going to write about a few ideas we’re developing for enterprise tools, but since I think the packs offer fantastic value to our customers, I thought I should take advantage of the extra real estate to clarify all their ins and outs.

2008: looking ahead.

January 4th, 2008

2007 has been a big year for all of us at Broutek. We’ve gone from idea to launch, and worked hard to create a full-service website backed by an expert team of Revit modelers. Looking back over the past 9 months, we have come a long way, and our expectations have been greatly exceeded, thanks in large part to your interest and feedback.

Broutek Exhibiting at Autodesk University

November 24th, 2007

We’re pleased to announce that Broutek will be exhibiting at next week’s Autodesk University in Las Vegas. Come see how our product families can unlock the power of Revit, and get a 50% discount on any of our new family packs.