Make the Key Plan a Shared Nested Family in the titleblock, with a Family Type Parameter. Then just have different Types for the areas, with the shaded parameters different in each type.

Then, you can even use dynamo to set all those parameters automatically, based on the Sheet Name (Does it say Area 1, Area 2, Area 3, etc). thats how mine are all done. The Dynamo graph looks to see if the Sheet name says PLAN, and then looks to see if the Sheet Name says AREA X. If it does both, it sets the areas automatically. If it doesnt, it turns off the key plan.

I think I understand your first paragraph. Since I have different pour zones for each floor, I should put in the nested families depicting each key plan so I don't have to create a different sheet family for each floor. The problem for me seems to be the same though (creating multiple sheet families vs inserting various nested families into the one sheet family)...in the project, I still have to open the sheet from the project browser, select the sheet family, watch the properties palette display the visibility options, then check the appropriate box for the pour zone.

This is what I want to avoid so I can assign pour zones to sheets without opening a drawing.

Which sounds like it leads to your second paragraph about the dynamo (I really have to sit down with that one day).

Is there a way to select the pour zone without opening any sheets and without dynamo? *fingers crossed*

If you do it my way, yes. What im talking about is a Family Type Parameter in the TITLEBLOCK, not the SHEET. So you could technically use a tool that can change the properties of the Titleblocks, if you dont want to learn Dynamo. I think i did it once with CTC Schedule XL, but there was some trickery involved.

Finally started a new project. Still stumped on this one, hoping you could help. Pretty sure I'm still doing this wrong.

I created a generic annotation family, went into Family Category and Parameters dialogue box, checked "Shared" check box.


That's the main thing I didn't do before. Now I have a generic annotation family set to "Shared". I created five "filled regions" representing each area on the key plan, associated them with Family Type parameters, and finally created five types. Each type is parametrically set to display only one "filled region".

This shared generic annotation family is now loaded into my TB family.

This means it's a nested shared generic annotation family right?

In the TB family, I set the first copy of this nested shared generic annotation family as the AREA 01 type, and associated it with a family parameter for visibility. Copy/paste aligned, set this second instance as the AREA 02 type and associated IT with another family parameter for visibility...etc.

Each type of nested shared generic annotation family is displaying hatching of its own area.

(Previous key plan exercises involved creating the hatched "filled region" in the TB family.)

Loaded this TB family into my project and I still can't see any check boxes or options unless I open the sheet and select the TB family and access key plan options on the Properties palette.

Can you tell me where I'm going wrong?

I want to shade the key plan using check boxes via the Project browser without opening any sheets.

Sorry if the post is extremely verbose and repetitive. I want to make sure I have the terminology right.

Can you please elaborate on that part?

When you select a sheet in the Project Browser, you can see the sheet properties in the Properties palette.

I'm trying to get the key plan areas listed with check boxes in the Properties palette:



This way I can set all shaded areas for all 900+ sheets in my project without opening a single sheet (hopefully from a schedule, and eventually in dynamo).

What are you going to schedule? Sheets. You cannot schedule Titleblocks. And the visibility parameters of the keyplan family are properties of the titleblock, not properties of the sheet. So you have to work with titleblocks. I doubt that this task is possible to do without opening a single sheet as you say.

The parameters of the keyplan are properties of the generic annotation family, which are being carried by the TB and the project since I've nested it into the TB and loaded into the project. Does that change your perspective?

I'm going to run a few experiments tomorrow night. Will let you know what I find.

At this point, with what I have set up, I can change the key plans from my starting page without opening any sheets or loading any worksets (just have to edit ONE generic annotation family). This is a huge advancement because when the GC publishes their pour breaks, I can modify a whole floor plan and all sheets carrying that key plan will update.

Also, initial set up is not that bad when I do it with all worksets closed.

If pour breaks vary from floor to floor, I can add another gen anno family and that will STILL be quicker than going into each TB family.

This is all uncharted territory for me, but...it's kind of fun in a twisted sort of way.

Sent from my SM-N950W using Tapatalk

Hmm... not yet. Let's stay in touch to see what happens next.