instance with incremental instences inside

[danezeq]

Hey 🙂

I'm not really sure how to call the function i'm looking for, or even if it's exist.

I'm trying to build a signage plan so every symbol represent a sign which consist of few plates.

The plan view should show only 2d line.

The thing is i should have the option to add up until 10 plates for each symbol on "incremental" way.

That 2d line can actually represent 1-10 plates, it will stay the same on plan view.

Every plate should have 22 different parameters. (like front text, back text, in 3 different languages and other more info)

so, are we gonna end up with 10*22=220 parameters of each familty type?
or
is it possible to add another set of 22 parameters to the family only when i'll need too add a plate to the family?

I know i can built it in a way so every plate will be a seperate instance but i want that the tag will include all plates on a pole.

Is it possible somehow?

BTW i dont need the sign to be atually 3-d built. i'll use one plan view.

[ToanDN]

Read up on using Family Type parameters to create drop-down selections.

https://www.linkedin.com/pulse/add-choices-your-revit-families-family-type-parameters-paul-aubin

[danezeq]

this article is quite hard for a rockie like me in families.

maybe is there any family built this way someone can upload just for example?

[mhiserZFHXS]

The solution described in the article is the best way to address this. If that article is too challenging for you to follow then you probably need to take couple of steps back and solidify your foundational skills for creating Revit families.

[kh_jea]

"10*22=220 parameters of each familty type"

If you need this many parameters, I suggest creating more than 1 family.

220 parameters is a nightmare to manage and use.

[danezeq]

i thought about this option, the only thing preventing me from doing so is that i'll need the tag to include all the signs texts in one tag, is that option exist?

 

[Mike.FORM]

In my opinion the tag should only include the pole number and then you should have a schedule indicating what info is shown on each pole. The parameters will need to be shared parameters so they can be scheduled. This way all the info is on the schedule in one location and the plan is only indicating where the signage is placed.

[danezeq]

Did you mean that every plate will have it's own instance with it's 22 parameters,

While the tag will refer just to the pole,

and somehow will recall all the "front text" parameters from each instance?

[Mike.FORM]

Yes. If you have the parameters setup as "shared" then they can be scheduled and thusly you could list what text is on what pole/sign in the schedule. You would still need to fill out those parameters individually per sign but this could also be done in the schedule.

[danezeq]

the schdule isn't my problem, but the tag is.

how can the tag recall parameters of another families?

[Mike.FORM]

The shared parameter would need to be loaded into the tag family and the sign family, then in project the shared parameter would need to be loaded and assigned to a project parameter. This makes the parameter the exact same across any family it is loaded into and the project.

[danezeq]

after loading the shred parameters to each one of them (project, tag, and all plates)

i dont under stand how should the tag take all these parameters and displays them, i mean the tag should know where to look them first.

lets say there is 1 tag, 1  pole (that is one family) and 4 plates (that is 1 another family + 4 instences) the plates has a parameter names "front text" now the tag has label refer to shared parameter named "front text"

ok, what then? there are 4 different parameters values. 4 different "front text"

How should the tag know about this?

[danezeq]

Here is the the tag and the families in case i havn't explained it clear enough. sorry for my english.

and, also a small illustration of how it should be look like:

[Mike.FORM]

You need to make a decision on how you want the information displayed. Would organize it something like this excel example shown. All the parameters would need to be shared parameters applied to the signage category. The only parameters that you would need in the tag and pole family are the pole number. Everything else can live in the project as a shared parameter. Some may be a yes no parameter, some might be text it doesn't matter. You just need to figure out how to convey it and trying to do it all in the tag is not practical.

[danezeq]

sorry i didnt get it. where does the excel sheet part comes in? does revit sync with excel?

[Mike.FORM]

I just did it in excel to show what the schedule layout might look like. I didn't have time to make a mock up schedule in revit (more involved setting up) so I just did it in excel as a visual only.