When you first start using family tables well, you see the entire world open up. You can make thousands of parts in seconds. Everything is great.
Some time goes by, and you become more familiar with them. You have to change a parameter and realize you have to check everything out to propagate that parameter to every model. Maybe you start making family tables of family tables. Maybe you make family table assemblies.
It's not long when you start to realize the bigger and more complicated the tables, the more trouble they cause.
Especially when the people making them aren't as experienced and they are being used in many different uses.
So the situation we faced were some of our engineers were using family table assemblies to make items that were not tabulated items.
One example was a motor with different wire routing, Some were the same motor, some had different wiring options. Another case was using a family table assembly to create a simplified representation of a design assembly. The list goes on and on.
Tabulated items typically vary by a dimension, maybe even a material, usually some small parametric constraint. Tabulated items are not meant to be different configurations, different parts, different assemblies, etc. Even shown and opposite, or left hand/right hand items can be trouble because sometimes you can't assume they will always be identical. Reassembling parts that are already symmetrical is another issue, but mirrored items is a topic for another post.
Family table assemblies can also be difficult with ModelCheck and Gatekeeper getting everything verified and without errors. We have a few open support tickets on this issue.
If it breaks the tabulated drawing rule of ASME Y14.24, then it's probably not a good use for family tables.
In our case we've recommended no family table assemblies except for certain cases that meet the tabulated rules, even then we ask our end users to ask us (Creo Admin/Experienced Users group) first. I'm not saying don't use family tables. All I can say is, use caution with family tables, and know what problems you can cause by using them. With great power, comes great responsibility.
-- My words are my own and do not represent any of the companies I work for. --