Problem is there are a LOT of categories that would be helpful. to be honest, in every firm I've worked on most parameters get sorted under other, general, identity data. Some things like graphics, visibility, constraints, and dims are generally clear. some new categories have been added like life safety (thankfully) but these happen slowly over years.
I'm a BIM manager so grouping parameters in some category that makes sense is important and it drives me nuts I can't organize things better! I've found people get overwhelmed when 10+parameters live under one category. In addition the following information doesn't have good categories.
All of these generally can fall under other, data, or general but those parameters get cluttered after a while.
- Organization parameters (parameters used for organizing views, schedules and sheets)
- in house/company parameters (office identifiers, version information, any other parameters used in house or for identifying in the model NOT the element itself).
- ADA parameters (these are much better grouped under ADA than separating across data, text and visibility)
- formulas and crap we don't want to have visible almost wish there was a group called formulas, and have that invisible to users. I like how unreal engine uses graphic programing underneath to create these elements so that users have more control over them and the interface only has what it needs.
When using nested/smart families, there tend to be more parameters while this sometimes is overkill, things like doors, windows, and some other elements are good examples of families with nested families for panels, frame profiles, and lites. These families would benefit the most from custom organization because you could group things like lite dimensions, panel dimensions, overall dimensions. Then you could have an ADA section, and a hardware section.
Hardcoding doesn't mean everyone sees things the same. it would likely be much easier to navigate if we could customize it, at least at a high level (bim managers) maybe it's something that can be in a ACC library like parameters are moving to, and each project must have the same groups, but they are customizable.
Combine this issue with hardcoded parameters and you get confusion no matter how clean a template is. Haven't been to one office that doesn't ignore at least some of the system parameters for various reasons (either because they don't agree with type/instance or the group they fall into, or the name). Then you end up with multiple similar parameters.
Clearly this is low on the list of needs, but many other design programs have this functionality so not sure why we can't.