Parameter Service changes

[ViviNyehuusAndersen]

We are currently evaluating and implementing Parameter Service as part of our enterprise BIM governance strategy.

During this process, we have identified two fundamental design limitations that significantly reduce the usability of the service in large, standards-driven organizations.

1. No support for “family-only” parameters
Parameter Service currently assumes that all shared parameters are intended for project-level category binding. This results in mandatory category selection and warning states for parameters that are intentionally designed to be used exclusively inside Revit families (e.g. visibility controls, internal calculations, symbolic switches).

In enterprise BIM workflows, family-only parameters are a first-class concept and should be supported explicitly without requiring dummy category assignments or producing validation warnings.

Requested improvement:

• Introduce a “Family-only” or “Non-project bound” parameter type

• Allow parameters without category binding to be treated as valid and intentional

• Remove warning states for parameters explicitly marked as family-only

2. Flat Collection structure without hierarchy or metadata
Collections in Parameter Service are implemented as a flat list with no support for:

• Sub-collections

• Tags or metadata

• Scopes (e.g. Project vs Family vs Internal)

This design does not scale in enterprise environments with hundreds of parameters and multiple standards domains. As a result, organizations are forced to rely on naming conventions and artificial workarounds to simulate structure.

Requested improvement:

• Support nested collections or logical grouping

• Introduce basic metadata (e.g. scope, intended usage)

• Enable filtering and governance-oriented organization

Business impact:
Without these capabilities, Parameter Service cannot function as a true single source of truth for enterprise BIM standards. This limits adoption and forces organizations to maintain parallel systems (shared parameter files, documentation, internal registries).

We strongly believe that addressing these points would significantly increase the value and adoption of Parameter Service among large, standards-driven customers.

[Ric_Weber]

@ViviNyehuusAndersen, a couple comments on this idea.  

You stated:

1. No support for “family-only” parameters

I use the Parameter service just like any other shared parameters.  I use them in families all the time.  Where are you finding that this is not possible?  The category assignment that you choose should be the one that it is going into.  You can change that when you load it into your family.  I'm not seeing the issue here.  

2. Flat Collection structure without hierarchy or metadata

It is not real intuitive, but there are several things to help here.  

1. You can add parameters to one or multiple collections (similar to Content Catalog)
2. You can add one or more "Labels" to individual parameters to help with filtering
3. You can filter then by a multitude of different columns.

This document has quite a bit of guidance on the functionality of the Parameter service.  I'd love to see something even better from Autodesk though.  Perhaps a webinar reviewing all the functionality and how to set it up?  Autodesk, any help here?  https://help.autodesk.com/view/DOCS/ENU/?guid=parameters

If you have any other questions, feel free to ask.  I think I addressed your concerns here, but perhaps I'm just misunderstanding what it is you are looking for?