I’m looking for best practices for creating and managing reusable, version-controlled parameters across multiple models (parts/products). This is to better manage our interface development during early stages when things are less formal. 

Expected Goals:

• Single source of truth for these parameters
• Version control with revision and release states
  • Only allow use of released parameter definitions
• Ability to either link or copy parameters depending on use case
• Traceability to identify which models are using a given parameter revision

Desired capabilities:

• Revise and release updated parameter sets
• Identify all consuming models impacted by a change
• Selectively update those models (or create new revisions if required)
• Potentially automate this process (e.g., script or rule-based update)

Questions:

1. Does anything like this exist? 
   1. I have just started going through the Templates and Rules Designer training and am learning a lot, however this is a small start up and I wear a lot of hats so I don’t have enough time to research this completely. I am hoping one of you kind people can point me in the right direction. 
2. Is there a recommended way to structure a reusable “parameter library” in 3DEXPERIENCE (e.g., template part, product, catalog, EKL-driven approach, etc.)?
   1. Is so how are revision control and release typically handled for shared parameters, if at all?
   2. Are there tools or methods exist to track which models reference a given parameter?
3. Has anyone implemented automation (EKL, scripts, or ENOVIA processes) to manage updates and impact propagation?

I’m trying to avoid unmanaged duplication and move toward a scalable, controlled approach.

Parametric DesignParametricArchitecture