AHU and coil family and schedule - best strategy

[HVAC-Novice]

I'm building new AHU families and want to keep them flexible enough to allow use in different configurations (DX cooling, hydronic heating, chilled water cooling, or a combination). in the past I made one AHU family and schedule and then also included the coil data (LAT, pressuredrop...).

The problem with that is that is,  if I have AHU with different type of coils (some heating, some DX, some chilled water) I end up with huge families and schedules and holes int he schedule where something is not applicable.

My idea is to end up with an AHU schedule that shows what all data AHU have (fan, filter, airflow etc.) and separate schedules for chilled water, hydronic heating, and DX coils. For that i though i use nested shared families for the coils that i nest into the AHU family. Before is tart this large task, I was wondering if someone has a better ideas or can warn me of some booby traps? 

some difficulties that come to mind are:

- the coil schedule should show the "Mark" parameter for the associated AHU

- should the coil family be an actually visible extrusion inserted and visible int he AHU? 

- should the pipe connections be part of the AHU, or the nested family? 

- I probably need some selection parameter to select what coils this AHU has and hide not applicable pipe connections etc.

Thanks for any input. As i progress i sure will have more questions. but any guidance beforehand would be appreciated.

my idea is to 

[RobDraw]

I think it would be more appropriate to create multiple families based on the different types. You're gonna have trouble with connectors for the units that aren't using them. I think it's possible to do but I wouldn't. You can do different size units within a type without too much trouble, though. Similar to what manufacturers are doing with their families. 

[HVAC-Novice]

Thanks for the reply. You are probably right. I'll play with it a bit in the next days for my current project and see what works best.