Calulated Values Displayed in Tag

[marcoavallone]

So since this has been a problem for a years, has any one over at the desk figured it out yet. It seems that I can't display a simple calculated value in a room tag, STILL...No this can be.. Someone please enlighten me... Or at least properly caffinate the right people to get this thing figured out.... Please tell me that this one is solved and I just missed it....

[Scott D Davis]

No you still not display a calculated value in a tag. You must make a parameter you can schedule and display it next to the calculated value in the schedule. then compare the columns and manually (yes, manually...i know i know) fill in the value to display in the tag. At least in 2010 and 2011 you can use conditional formatting in the schedule to highligh the values that don't match.

Its on the list at the Factory...

[Scott Womack]

No you still not display a calculated value in a tag. You must make a parameter you can schedule and display it next to the calculated value in the schedule. then compare the columns and manually (yes, manually...i know i know) fill in the value to display in the tag. At least in 2010 and 2011 you can use conditional formatting in the schedule to highligh the values that don't match.

Its on the list at the Factory...
Scott,

This is true for system families, such as areas and rooms. It is not necessarily true for component families. The trick is to do the calculations in the component family itself, with the result going into a Shared Parameter within the family. At that point that Shared parameter is a calculated value, and can appear in a tag for that category of object, like the egress capacity of a door, based on its width.

[Scott D Davis]

Scott,

This is true for system families, such as areas and rooms. It is not necessarily true for component families. The trick is to do the calculations in the component family itself, with the result going into a Shared Parameter within the family. At that point that Shared parameter is a calculated value, and can appear in a tag for that category of object, like the egress capacity of a door, based on its width.

interesting...can you post an example?

[Scott Womack]

interesting...can you post an example?

I'm looking. I'll have to "fish" them out of a project where I know it was working........

[Scott Womack]

Ok, the attached zip has a single door in it. There are check boxes to turn on the calc, if it is an exterior egress door. The tag will pick up the info, and display it.

[Scott D Davis]

Ok, the attached zip has a single door in it. There are check boxes to turn on the calc, if it is an exterior egress door. The tag will pick up the info, and display it.

Ah ok, I see what you mean now. Yes, in that case, you can display a calculated value in a tag because its really all inside the family.

The need extends to calculated values that are reading info frrom the project and calculating it. For instance take your door and place it in a room. A parameter of the room could be occupancy, and there would also be a parameter for occupant load factor for that space. The tag would read the room SF, the OLF, and the Occupancy, as well as the door width, and then report how many people can exit the door based on the capacity of the room. Then insert another door and the tag should update to exit half of the room's capacity through that door.

[marcoavallone]

Guys, Thanks for the insight. I will try that door family out when I do my next exiting analysis. I should also try that conditional formatting function out too. Sure hope the original issue gets figured out before the next fandangled feature is added.

[Scott Womack]

The need extends to calculated values that are reading info frrom the project and calculating it. For instance take your door and place it in a room. A parameter of the room could be occupancy, and there would also be a parameter for occupant load factor for that space. The tag would read the room SF, the OLF, and the Occupancy, as well as the door width, and then report how many people can exit the door based on the capacity of the room. Then insert another door and the tag should update to exit half of the room's capacity through that door.

I completely agree with the "need" as you describe it. As I have placed on the wishlist before, alot of this could be accomplished if the grand total could be "assigned" to a single shared parameter, of the Project Information category, which is then able to be included in other schedules. This way, the grand total of building Capacity from an Area Schedule, could be used in a Plumbing fixture schedule, to calculate the total number of fixtures required for a given building, etc.

[rtaube]

Sorry, a bit of a newbie question as I'm trying to figure out how to use this capability. My old office used to to do production tract housing and their method of tagging the windows was to put a notation that had the size of the window directly on the plan (for example 4050 SL, for a 4'-0" x 5'-0" slider) , rather than put a note, and then schedule the window.

Is this the type of thing that this thread is talking about?
(obviously there would be some more hoops to jump through in order to convert 4'-0" x 5'-0" slider to 4050 SL)

[marcoavallone]

Ryan, I think you are talking about just making a tag that that displays the name of the component. Eg 3040. The windows can be sceduled aswell. I would be sure that the name of the windows match the actuall dim's so that they show up correct if the dim's are listed.

[rtaube]

That would probably be the easiest, but I have no idea how to do that (still kinda new to this sorta thing) Can you start me off in the right direction? I guess I'm not sure about how to make a tag that pulls information from Type Data.

Edit: Nevermind, I should probably just delve a little deeper into making my own tags, I figured out how link the text to other parameters, such as Description, and then fill in the 3040 (for example) there.

[lbjorn]

This is an item that I have added to the wishlist. I believe it is in the top 30 because I was recently able to vote for it. Check it out and vote!