Number of custom asset types and statuses best practices
Summary: The author advises limiting the number of custom asset types and statuses to enhance operating model efficiency and user experience. They recommend utilizing out-of-the-box (OOTB) asset types when possible to ensure compatibility with future updates. A Data Office governance process should guide the creation of custom asset types to avoid duplicates and unnecessary complicities in governance. For asset statuses, keeping them minimal is encouraged to prevent user confusion. Monitoring practices like the Operating Model Reverse Engineering (OMRE) are suggested for established production models.
Limit the number of custom asset types and statuses to optimize both operating model maintenance and user experience.
Impact
Use out-of-the-box (OOTB) asset types as much as possible to ensure maximum compatibility with future product features. Custom asset types should be used to meet your specific business requirement, but it is best to avoid using too many.
If there are a lot of custom asset types, you should review them and search for duplicates, as well as overlapping or unused asset types and confirm that custom asset types cannot be replaced by the use of OOTB asset types.
Ensure that you have the relevant asset types available before creating a custom asset type. This is to avoid creating unused custom asset types which can complicate the governance of the operating model.
Introduce a Data Office governance process for the creation of custom asset types. This process should provide guidance on when a custom asset type is absolutely necessary and reduce the risk of unused asset types. You should also review the number of users with permission to create custom asset types, as too many users can result in unused, duplicated or unnecessary custom asset types.
Custom statuses are encouraged to support the asset life cycle. However, keep the number of possible statuses for a given asset type as small as possible to avoid confusing users. If there are more than 30, consider consolidating to fewer statuses.
Topic area
Operating Model → Metamodel → Asset Model → Asset types
Operating Model → Execution and Monitoring Concepts → Status types
Monitoring this practice
For customers with established production models:
Run the Operating Model Reverse Engineering, or OMRE, on a regular basis to identify the elements in this article.
Contact your Collibra representative to run the Operating Model Diagnostic.
Additional information
For more information, go to the following resources:
