Showing posts sorted by date for query Egress. Sort by relevance Show all posts
Showing posts sorted by date for query Egress. Sort by relevance Show all posts

Wednesday, November 28, 2018

Downloads Fixed - Some

I have been trying to carve out a little time here and there to fix the paths to downloads I've shared in the past. As of now the most requested stuff is fixed, the egress family and railing files. If you try to download something and hit a page not found warning, drop a comment in the post to bring it to my attention and I'll make it a priority.

Thanks for being patient - The mGmT...

Friday, April 17, 2015

Revit MEP - Circuit Length Calculation

I received an email asking if I thought it would be possible to use a Line Based family to calculate wire length for circuiting purposes. It was prompted by reading an earlier post about using them for Egress Path calculation and documentation. I think it's a reasonable approach for Egress Paths because there is no such tool or concept already in Revit.

Electrical circuits on the other hand do calculate their length already, granted it does so simplistically. It combines the X/Y/Z distances of the devices from the panel (and each other) to arrive at a total circuit length.


A friend some years ago sent me a PDF that showed a bunch (a couple shown above) of different equipment and device layout schemes he did to better understand how Revit arrives at a value for Circuit Length. What it shows is that Revit does nothing to factor in obstacles which force the wiring to go up or down or around the things that are more than likely going to increase the total circuit length.

To be fair...how could it really? How detailed is the model? How long do we want the software to interrogate the model, the linked models to do a better job? It's a bit like requiring all conduit to be modelled, even 3/4" conduit feeding single gang boxes in a wall when there isn't a single stud in the model. Like with so many things in life, it's about context.

It's one thing to put a single gang box on a wall to indicate one is required here and another thing entirely to run conduit to all the way to it when you can't be sure it can really go there. Or like showing a pair of outlets back to back on a demising wall in a residential project where fire rating and sound attenuation would require them to be separated by a minimum distance.

Some things are still conceptual (schematic) in nature even in fairly detailed models. If we start modeling every stud then perhaps it becomes more reasonable to expect more system detail too. Then again if I have to create a run of (15) 3/4" conduits across a wall or ceiling I probably ought to model that situation because it's going to take up a lot of space and everyone else ought to be aware of it.

It's also been my observation that no matter how good software gets at a task there are always outliers that dismiss its results as still wrong. That written, it does matter and Revit should improve how it does calculations and how much say we have in the outcome because the length it calculates is also used internally to contribute to other calculations like wire sizing and voltage drop.

Setting aside how circuit length should be calculated (it might surprise you to know that engineers don't always agree on this), I'd consider this approach if my task was to determine how much wire was needed, a little closer to actual requirements than might show up in the circuit properties. I'd create a schedule focused on Electrical Circuits.


What you see above: I created a couple panels and added a bunch of duplex outlets. I assigned them to circuits. The schedule's second column is Revit's calculated length, no more effort on my part than placing devices, creating circuits and choosing a panel.

I sorted the schedule by Panel and then Circuit, provided a header for Panel and footer for totals. I added a parameter for Length Factor (a number) and then a Calculated Parameter for Total Estimate (a length) which uses a formula of Length Factor * Calculated (column 2).

Then I consider each circuit's circumstance and enter in a factor that increases or decreases Revit's own calculation according to how easy or hard the actual wire run or routing will be...or at least what I think it will be. A factor of 2 doubles the length etc. This calculation doesn't factor into load calculations like for Voltage Drop...but then neither would using a line based family.

This doesn't account for situations that might share a neutral (or ground) or runs that are comprised of individual conductors in conduit (like THHN or THWN) or a wiring combined into a common jacket like Cerro's NMB (a typical household wiring product).

That's the risk/difficulty of automatic calculations, the closer you examine situations the more outliers there are. It can be a bit like arguing about something being 99.6 percent correct. If it costs another $1000 to get to 99.9 or 100%...is that difference worth it?

Thursday, August 30, 2012

Egress Post Summary

As with my recent Worksharing, Site and Reference Plane summaries, I've added a link to this post which will serve as my summary landing spot for Egress Path posts. It's been about six years now since I demonstrated the new line based family as an egress path. The subject is still going strong and there are more options to choose from now.

Summary of Egress Path Posts

(2012) Egress Path Options
(2011) Bending Railings To Your Will
(2011) Stair Headroom Clearance
(2009) Egress Path Update
(2008) Egress Family Video
(2008) Egress Path Tags New Versions
(2008) Egress Math Error Bug Report
(2008) Egress Family Arc Version
(2008)Egress Example Update
(2007) Egress Path Of Travel Uh Oh
(2007) Egress Regress
(2007) Egress Path

Wednesday, August 29, 2012

Railing as Egress Paths

I've written about this before, egress stuff seems to be popular at times. A railing is a path and profile based element is easy to sketch something like the path to an exit. Straight and arc segments as well as even sloping conditions. Some of the other methods that I've written about here have the advantage that they can document the total length easily. A railing schedule will report the total length but we can't tag them with their total length.

Case-Apps to the rescue!

They've written a little application that is part of their larger suite of free, subscription and beta software for Revit. It's called "Send Railing Length to Selected Parameter".


Create a shared parameter called "Egress Path", add it to your project and assign it to the railing category. Sketch your railings disguised as egress paths. Now tag them. Oh right you can't show that value. Edit the tag family to create your own and use the same shared parameter. Reload the family and still nothing. Now use the Case app. It will let you select the parameter to use and plug the total length into each railing and that value will appear in your tags!

It's not automatic or fool proof. But it does make it a lot easier to consider a railing. If you like special graphics at the beginning and end of your egress paths then a railing is a bit fussier because you need some special "balusters" to get unique "symbols" at each end. Not impossible just a bit more work. Not necessarily more or less work than the other techniques, pick your poison!

While you are at it you should consider the rest of the pile of apps they have. You'll get their apps manager application which really makes it pretty easy to get and install them. I had both 2012 and 2013 installed in a few minutes after registering.

Thanks Case-inc guys! (wearing my T-Shirt as I write this, they gave me a shirt at RTC in Stone Mtn. in the interest of full disclosure)

Wednesday, August 15, 2012

Egress Path Options

In 2006 I demonstrated (at Autodesk University) the then new line based family type by explaining how we could use it to document egress path requirements also known as exiting plans. Since then a couple other options have come along.

One is the notion of using a railing type. They are also derived from a path and we can use a profile to represent the form of a person traveling through a corridor. That's not a requirement but it does make it easier to visualize it in 3d views.

Another is to use the newer adaptive point concepts in a family. Initially we could only use them in the massing category. As soon as they opened them up to more categories it made it more palatable to consider them for this purpose.

Defining the requirements for documenting exiting are naturally going to affect the success of any solution we try to provide. Ideal we should be able to provide a total length of travel from one place to an exit, identify the length of any segment of the path and provide a clear descriptive way to show how our design meets codes in plan views, at a minimum.

The new adaptive point approach requires building a family that provides however many segments are required in advance. It isn't possible to tag individual segments though a tag could display a summary of each segment as well as the total (Edit: there is nothing to prevent us from creating a two point family and using the chain placement approach, that would support tagging individual segments). Adaptive points don't permit nesting detail components so the annotation used to display special nodes at the beginning, end or at nodes along the path requires geometry that will take more work to scale according to a view scale.

Sean Burke shared a You Tube video of the adaptive point approach in action, check it out (embedded below). At least now there are more options to choose from. Pick the one you think best fits your requirements!

Sean Burke's example



Afredo Medina shared a You Tube video of his LBGM approach.



Summary of Past Egress Posts (a summary)
Egress Path
Egress Path Update
Egress Path Tags - New Versions
Egress Path of Travel Uh Oh
Egress Example Update
Egress Regress
Egress Family Arc Version

Tuesday, December 20, 2011

Bending Railings to Your Will

Food for thought, what if we used railings for millwork and egress paths? By millwork I mean custom work, not fixed sized cabinets which are often referred to as casework by some architecture and interior firms). As for egress paths, I've written about them many times (I've put a list of those posts at the end of this one) in the past and the example of using a line based family kept me busy for quite some time with requests from people to get their own copy. Busy enough that I finally made it possible to download directly without needing to ask. I also recently mentioned the technique that Brian Mackey uses to demonstrate stair clearance using a railing, so that's yet another way to bend railings to your will.

A railing can do the same task as the egress path I've written about. That example only came about as a possible example of how to use the new line based family template (new in 2006), not something optimized for the task but it's worked pretty well over the years. If you consider applying a "person" profile to a railing, like for Brian's stair clearance, you've just got to sketch the path the railing takes. You can schedule the railing and provide a similar tagging approach to identify each path as different as well as display the total length. Give it a go?

Back to the idea of millwork. Railings are based on profiles, so are cabinets, at least when you are being really schematic. Obviously it won't really do the job for fabrication or construction documentation. If you want a fast way to "draw" millwork a railing works pretty well. A railing sketch is really tolerant of the path being straight or curved too. To get started you sketch the base cabinet profile, save it. Sketch the upper cabinet, save it. You can incorporate the counter profile in the base or make it separate. Load the profiles into a railing type and adjust some values and you can get something like this.


It works pretty well as long as you don't care about seeing drawers and doors. What you see in the image above is railings posing as millwork cabinets and face-based families (line work only) assigned to the Casework category.


It is necessary to keep the upper and lower cabinets separate otherwise you can't get them (upper cabinets) to show up above. In the plan view you see here I've temporarily turned on the underlay so I can apply the Linework tool to see the upper cabinet. Relatively small price to pay for the views that really need to see it.

The neat thing about this approach is that you can get schematic design info such as overall length of different millwork conditions via a schedule. Then when you are ready to dive deeper you can replace them or, as in the image, overlay face-based families to "finish" the detailing. One schedule (early) for schematic and  another (later) for a more detailed summary of cabinets pieces and parts. It isn't hard to make a railing look a lot like something else in a schedule. Just change the schedule title, rename the railing type, change the assembly code values and you've got a pretty convincing railing slash millwork. Maybe call it milling or railwork?

It won't satisfy everyone or maybe anyone...well it did make a few folks more content than they were a few years ago when we decided to do it.

Past Egress Posts (a summary)
Egress Path
Egress Path Update
Egress Path Tags - New Versions
Egress Path of Travel Uh Oh
Egress Example Update
Egress Regress
Egress Family Arc Version

Monday, November 21, 2011

Stair Headroom Clearance

In the past I've written about using a line based family to document path of egress information. Brian Mackey with BD Mackey Consulting in Denver recently shared a concept he uses for demonstrating that a stair well has sufficient clearance. He uses a railing family that has a profile to document the required clearance instead of what we'd usually use. In this example I quickly mocked up I just used a similar "guy" I'm calling Clarence, so Clarence can show the Clearance is met.


It's easy! Just create a profile family and load it into your project. Assign the profile to a new railing type, called Clearance. Assign Clarence to the Railing. Place the railing on the center line of the stair. You'll have to fuss with graphics and decide when it should be visible but it's pretty simple. To really show the zone required for clearance a simple rectangular profile off a specified height would suffice and show where no building elements should touch. A quick interference check would help catch problems too.

Cool solution Brian!

Wednesday, October 12, 2011

Room Name Alternates

This is a repost of one I wrote back in December 2008. It came up again recently in a question via email and I noticed it's a pretty old post so I thought I'd plug it again.

Sometimes a name is just too much, too long, it just doesn't fit in a room. The stock Name parameter for a room is easy, it's already there waiting for us to us. When we use abbreviations in this parameter we end up with some full names and some abbreviations. An abbreviation of "T." for Toilet might be fine on a plan view but it is less than stellar in a schedule. We could use another stock parameter like comments to store an abbreviation instead but that subverts its usefulness for actual comments.

Shared Parameters to the rescue!

I've written several posts about shared parameters in the past so I won't go into making them again in this post (see bottom). This is what you need to do to get a new parameter working in a project.

Create a shared parameter (called Abbreviation for example)

Create a room tag family that uses your shared parameter, save the Family and load the family into your project

Add a Project Parameter (Settings > Project Parameter) using your shared parameter too. Assign the parameter to the Room Category

Use the parameter in your rooms, set-up a schedule and tag your rooms with the appropriate tag.

This gives the best of both worlds. Supply abbreviations for names that are unruly and don't bother for reasonable names. A schedule will make it easy to define either and those that don't have abbreviations don't "need" them. Just make sure you use the correct tag to display the value you really want people to see. You could also use this technique to provide a room name in a second language, if necessary.

I've posted a revised copy of my Egress Example project that contains a working example of the shared parameter, tag and schedule.

This post Shared Parameter File: A Little Clarification provides a full list of the posts I've made in the past on the subject of Shared Parameters.

Friday, August 28, 2009

Egress Path Update

I don't get as many requests for this as I used to because I've made it easier to just download them directly. I got a request today from a new user who wasn't sure how to get the families and schedules into their project or template. So I wrote back to explain and while I was writing it occurred to me that maybe others might have wondered about this too.

First, if you don't know what this is about you can use THIS SEARCH to see all the posts I've made about it already.

Second, I recorded a VIDEO to explain how.

Third, you can watch or at least listen below to see how to get the content in your project or template:


I used Revit Architecture 2009 to record the video because that was the file version that I happened choose. I probably should have done it with 2010 but the concepts are the same.

Fourth, I've added another video to demo how to use them, as requested.


Last, seasoned users know that there are other ways to get the content in the project too as well as using them in the project. I just showed one, pretty simple, way to get where you want to go.

Monday, December 15, 2008

Room Name - Full or Abbreviation

Sometimes a name is just too much, too long, it just doesn't fit in a room. The stock Name parameter for a room is easy, it's already there waiting for us to us. When we use abbreviations in this parameter we end up with some full names and some abbreviations. An abbreviation of "T." for Toilet might be fine on a plan view but it is less than stellar in a schedule. We could use another stock parameter like comments to store an abbreviation instead but that subverts its usefulness for actual comments.

Shared Parameters to the rescue!

I've written several posts about shared parameters in the past so I won't go into making them again in this post (see bottom). This is what you need to do to get a new parameter working in a project.

Create a shared parameter (called Abbreviation for example)

Create a room tag family that uses your shared parameter, save the Family and load the family into your project

Add a Project Parameter (Settings > Project Parameter) using your shared parameter too. Assign the parameter to the Room Category

Use the parameter in your rooms, set-up a schedule and tag your rooms with the appropriate tag.

This gives the best of both worlds. Supply abbreviations for names that are unruly and don't bother for reasonable names. A schedule will make it easy to define either and those that don't have abbreviations don't "need" them. Just make sure you use the correct tag to display the value you really want people to see.

I've posted a revised copy of my Egress Example project that contains a working example of the shared parameter, tag and schedule.

This post Shared Parameter File: A Little Clarification provides a full list of the posts I've made in the past on the subject of Shared Parameters.

Wednesday, September 24, 2008

Egress Family Video

Michael Bass with Microdesk started a blog called Building Informed Models that contains videos for a variety of Revit related tasks. He just posted a video explaining the basic concepts involved with making the tag and the line based family that I used with my Egress Family examples that I've posted here at various times. Videos are great vehicle for explaining concepts, check them out.

Friday, August 15, 2008

Egress Path Tags - New Versions

As requested by email I've created a couple new tags for the Egress Path example I've shared here before. There is a Metric Tag set to millimeters and a combo tag that demonstrates how to display both Imperial and Metric data in a single tag.


Hope they prove useful!

Download the Metric Tag (136 kb)
Download the Combo Tag (148 kb)

Interested in all the downloads? Visit my DOWNLOAD PAGE.
If you'd like to see how to get this stuff into your template file you can WATCH the VIDEO.

Wednesday, July 16, 2008

Egress Math Error - Bug Report

For those who have downloaded the latest arc egress example, sorry! David Baldacchino pointed out a math error in my work. I've fixed it and have posted new files at the site again. I also tweaked the schedule formatting a tiny bit.

Download the fixed (project file) 2008 version CLICK HERE 2008 (792 kb)
Download the fixed (project file) 2009 version CLICK HERE 2009. (936 kb)

Download just the 2008 arc Family CLICK HERE. (188 kb)
Download just the 2009 arc Family CLICK HERE. (232 kb)

By the way, David provided me with an example that includes the arrow and dot but they can't resize with scale change so I haven't included that...yet.

Monday, July 14, 2008

Egress Family - Arc Version

I've added a new segment that permits sketching an arc segment. The path length is derived from trigonometric formulas and is "close" enough for its purpose, I assume. You'll have to decide for yourself if you choose to use it.

Thanks to Mr. Raiz for the formula I needed to do the calculation. It is setup to use as a middle segment as I assume that it probably wouldn't be used to start or end. Arbitrary assumption perhaps. The "hard part" (meaning time to work it out is short right now) is getting the arrow to point in the correct direction relative to the arc.


To download the new 2009 version CLICK HERE 2009.
To download the new 2008 version CLICK HERE 2008

Friday, June 27, 2008

Occupancy Calculations

A time consuming task for architects is the evaluation of the project's intended occupancy and its impact on egress from a building. It is possible to improve this process considerably with Revit by reporting data in Room schedules. However simply reporting this same information in a room tag isn't so trivial.

The fundamental problem is that we can not display data that we calculate inside the project in a tag yet. A tag family can not use the area value in an equation because it doesn't exist until you are in a project.

This FILE is an example of a strategy that reduces some of the drudgery of looking up data and having the numbers "crunched" but leaves us with manual data entry to get the information in tags so it can be display meaningfully in plan views as well as listed in a schedule. I did the work in this example but the inspiration goes to WLC Architects, where Scott Davis used to work. It is an imperfect example/solution but should serve as inspiration for your own approach to this issue.

Some of my thoughts about how this might change in Revit:

We need a way to tell Revit that a tag will use a project value, like area, once it is inserted and an object is tagged. A placeholder for AREA that will assume the true value when you tag a space but in the family itself substitutes a temporary value so the formula will "work".

Alternatively we need a system family tag type that can combine instance data like Area with other shared parameters to display calculations.

A third concept might be schedules that actually behave like tags and allow freeform placement of parameters and linework to look like a tag.

Yet another is to allow us to map one parameter to another within a project. Essentially allowing what we have done in these schedules manually to be done automatically, ala Excel...Cell A1 is equal to Cell J4.

In terms of value delivered, this sort of evaluation/calculation is a process that all firms go through to some extent. Evaluating occupied spaces and demonstrating how the design meets the code. This is a business problem Revit needs to help us resolve. Giving us greater ability to decide where and how information will be displayed is very important.

The bottom line is we need a way to display calculated data in tags.

Friday, June 20, 2008

Egress Example - Update

This single little contribution of mine to the Revit community has been the most continuously requested thing I've done. Something so seemingly simple borne out of a fellow user's request.


I'm glad that this has been useful to so many. Now I've updated it for 2009 and added another tag as well as a "schedule as tag" approach to displaying the total length at the end of a path. You can now download it freely instead of having to email me to get it! Happy Exiting!

Egress Path for Revit 2009
Egress Path for Revit 2008

Previous related posts:
Egress Path
Egress Regress
Egress Path Uh Oh!

Monday, May 05, 2008

Dept. of Subtle - Filter Parameter in Tags (really subtle)

This item is very arcane and until recently just another little mystery to me. While working on the egress family and its tag family that I made and posted about in the past I noticed the following item.


I hadn't noticed it in the past and searched for any information that might be available in the help files. Truthfully I wasn't too surprised when nothing jumped out at me in a few tries at a search. Unfortunately the help files are bit too sparse when it comes to the family editor "secrets".

So I posted a question to the gallant folks at Autodesk and I received this explanation:

“It is used to control which elements are taggable by a multi-category tag family. You can select a shared parameter as the filter parameter, and then when placing a multi-category tag, the tag placement tool will only let you place the tag on elements that contain that parameter (either because the parameter was added to the element’s family or because it was added to the element’s category as a project parameter).”

(My thanks to Steven Campbell and the "unknown" developer who came to my aid!)

This applies to Multi-Category tags. As it applies to my Egress family, this means I can tell Revit to filter for a specific parameter so that my "Multi-Category" tag will only tag "my" family..or any other that I associate that parameter with.

Thursday, October 25, 2007

Egress - Path of Travel - Uh oh...

Of all the stuff I've done over the last couple years the Egress/Path of Travel family has to be the biggest hit. It has generated more email requests than anything else. I'm glad I've managed to do something useful!! If only I charged money for it! 8-)

So I'm writing to let anyone who has actually used it that there is a bug present in Revit right now that messes it up. The little dot and arrow at the end of the line-based segment won't print as filled in the latest build of Revit. If it doesn't work in earlier builds no one has said so and I can't test it on any earlier builds now either. Don't look back...keep moving forward...new build...well in this case it is a slight step backward.

The "fix" according to Revit Support staff is to print the views that these are used in using "Raster" instead of "Vector". Phew...that was close, I thought I was going to have to come up with a different strategy for those little guys.

Hopefully the bug will be fixed in a future build. For what it is worth, this most likely affects any nested annotation symbol that uses a filled region.

Tuesday, January 09, 2007

Egress Re-gress

I've enhanced the earlier example by adding annotation symbols "Dot" and "Arrow" to the Egress family: Path of Travel. There are three types within, Start Middle and End. She looks like this now...you could do the same...