Adjusting Revit 2013 Assemblies Schedule

I am working with assemblies in Revit 2013. I am currently building 500+ assemblies and each time I use the auto create views it populates the views for me which is great. What is not great is that for the 500+ panels I have to go adjust each schedule with the information I want. The default is Catagory, Family and type, and count. I am not sure about how to get the schedule to populate the information I want not the default stuff revit puts in there. In addition I would like to set up the default views to be a specific way as well. I am having to go in and apply view templates each assembly created. If anybody knows how to do this I sure could use the help. Thank you in advance. :banghead:

Assembly Schedules are trash because of this very reason. Since you can't create them based on a template and you cant match it to another schedule. It forces you to make a schedule from scratch every time rather than using a template. I really don't understand why a view template cant include all the information from a schedule...granted there would have to be some boundaries like trying to apply a column schedule to a foundation schedule...

Rather than using assembly schedules just use regular schedules and filter by Assembly Name. Once you have it all set up you can then go and duplicate it numerous times and just switch which Assembly name it is using to filter. This is much quicker than using the assembly schedules.

Quote:

---

Originally Posted by gdoherty0102

Assembly Schedules are trash because of this very reason. Since you can't create them based on a template and you cant match it to another schedule. It forces you to make a schedule from scratch every time rather than using a template. I really don't understand why a view template cant include all the information from a schedule...granted there would have to be some boundaries like trying to apply a column schedule to a foundation schedule...

Rather than using assembly schedules just use regular schedules and filter by Assembly Name. Once you have it all set up you can then go and duplicate it numerous times and just switch which Assembly name it is using to filter. This is much quicker than using the assembly schedules.

---

Wholey Cow, Autodesk really hosed the pooch on this one. It makes absolutely no sense they would make the assemblies so generic with no capabilities for change. I called Autodesk and they refereed me to a software salesman saying they will have more answers than they do :( Bummer.

Thanks for the help :beer:

Quote:

---

Originally Posted by gdoherty0102

Assembly Schedules are trash because of this very reason. Since you can't create them based on a template and you cant match it to another schedule. It forces you to make a schedule from scratch every time rather than using a template. I really don't understand why a view template cant include all the information from a schedule...granted there would have to be some boundaries like trying to apply a column schedule to a foundation schedule...

Rather than using assembly schedules just use regular schedules and filter by Assembly Name. Once you have it all set up you can then go and duplicate it numerous times and just switch which Assembly name it is using to filter. This is much quicker than using the assembly schedules.

---

Hi, gdoherty,

Sorry to dig up an old post, but this is something I am currently struggling with.

I am trying to follow your advice, but I am not seeing Assembly Name as a field that I can add to my schedule. I have tried family and type, but these fields are not available in the schedule filters. Is there any chance you could elaborate on the above please, before I pull my hair out completely!

Many Thanks

Dave

What type of schedule are you trying to make? What category?

Hi,

Thank you for getting back to me so quickly.

I have a set of assemblies (around 50 No.) full of generic objects. It is a precast concrete assembly and the parts are lifting inserts, void formers reinforcement bars (Also modelled as generic objects) etc. All of the parts are full of parameters needed for pricing, perimeter length, surface area and volume of the concrete for example. Does this answer your question?

(I am using Revit Structures 2013).

Regards

Dave

p.s. are you really replying to my post at 5 O'Clock in the morning? :-o

Hi Again,

I have been playing around with this today and I think I understand why it isn't working.

I created a dummy assembly using 3 columns and 1 beam. When you create the assembly it asks you to choose a category, Structural columns or structural beams in my case. Basically you have to choose a category of one of the selected objects. In my original case, all the objects were the same, i.e. generic so the drop down box was greyed out and I didn't notice it, or realise its implications.

When scheduling from my dummy assembly, you have to pick a category to schedule from, Choosing columns enables you to filter by assembly name. Choosing Multi category does not give this option, and you can't create a Generic object assembly so basically I am stuffed using this approach as far as I can see.

The only way I can see this working for me is to take a step backwards and use nested families as 'assemblies' and add an instance parameter so I can isolate each 'assembly' for scheduling.

This does however, give me the advantage that I can build some parametric functionality into the nested family that I couldn't in the assembly.

One other avenue I tried previously was to create a nested family and bring this into an assembly on it's own, but this won't allow you to schedule out the nested objects.

The assemblies thing looks great, but it just doesn't seem to be developed enough to suit our intended workflow.

Rgds

Dave

Good catch, I am not sure if I would have caught this. Typically our assemblies are purely Rebar, and sometimes GM and Rebar. Was kind of curious what that did, but I suppose that makes sense for how it would make the Assembly Schedule.

And yes, I reply early in the morning. I typically get to work around 6:00, yesterday was an early day!