Yes, it is possible. You need a combination of several things:

Shared parameters:

1)Object_X_dimension
2)Object_Y_dimension
3)Object_Z_dimension
4)Rebar info

Families:

# 1) A detail component family showing the concrete footing. Since it is a 2D drawing, two of the dimensions (depending on whether you show plan or section) should be tied to length parameters, linked to their correspondent shared parameters. The other third dimension should be a length shared parameter, just data, not associated with the graphics.

# 2) A detail component family, showing the rebar graphics, with a text parameter to hold the description of the rebar. This is nested into family # 1; then family # 2 becomes a label for a family type parameter. The text parameter that comes from family # 2, is tied to the shared parameter for rebar info. You can nest as many similar families as rebar configurations you want.

Tag:

1) A Detail item tag family with one label including all 4 shared parameters.

See illustration.

Thanks Alf!

This was just what I needed. The only issue I have is that I can't get the rebar info parameter to read on the tag in the project.
Does this have to be an instance parameter at any point in the process?

Nevermind, I fixed it. I forgot to change the parameter within the project itself to the text I wanted to show. It was a blank string of text. That's why it was not showing.

Thanks for all your help!

Juan, I'm guessing you were referring to the workflow used in "normal" families with making nested components shared. That can't be done for detail components. The only possible way is to link parameters as Alfredo described.

Of course, if you want, you can systematically make it so you dont have to manually check the Shared Parameter for the rebar info, versus which rebar detail component is used in the nest.

Set the detail component to have Instance parameters for the rebar data you need. Then you are doing what Alf described above, except not with the description parameters. Use a Label that references the multiple parameters that are actually controlling the Nested DC's data. (Size of bars, number of bars, etc).

If you have a Number of bars parameter and a Size of bars parameter, those parameters can be nested, and can directly be in the tag as well.

:thumbsup: to all that contributed your knowledge to my brain

I followed what Alfredo and Aaron suggested and finally completed my first official parametric Detail component (Im sure I could add some more info like temperature reinforcing and ties but my brain is fried

Nested DC screen capture.jpg

BTW Aaron, I saw the naming conventions for families that you guys use and I think they are great. Just one question: On the PDF, it mentions that DETAIL COMPONENTS and PROFILES receive a different naming convention. How do you go about naming them?

Nice looking detail component. When I get some time I am going to create something very similar. Excellent thread!

Juan,

How did you get the array working? I couldnt stop myself from starting on this family, all the other stuff can wait. I have no idea how you did the array of rebar.

Thanks

Here is the Family
Its easier than explaning

DTL-FOOTING-CONCRETE-IMARA-UH.rfa

Hope this helps

Let me know if you have any questions about the family and when I have more time I can write a more detailed explanation