T

1 Message

 • 

200 Points

Monday, October 14th, 2024 4:13 PM

Relationships Operating Model: How to ensure Alignment of Physical Assets between different types of Data Assets

We have just finished rapid start and have built an operating model for processes which looks like this:

Business Process >  Business Terms  > Physical Assets

However we amended this operating model to include Machine Learning Models which operates like this:

Machine Learning Model > Features > Physical Assets

We then combined these two flows to look like the diagram:

Please note only certain processes in the business make use of Machine Learning Models

However because features and Business Terms are independently linked to Physical Assets there is the potential that the two won't align.  i.e. if a feature is changed and the business terms are not updated if you look at Physical Assets used in the Machine Learning model this won't give the same list of Physical Assets linked via the Business Process.  We don't want Features linked to Physical Assets via Business Terms.

Is there a way to amend this model or use particular relationship types to avoid the misalignment described in paragraph above.

Other mitigations we are considering are using reporting to monitor and potentially workflows to enforce changes are done together.

132 Messages

 • 

9.1K Points

1 month ago

What you have there is an Asset Model, not an Operating Model. You're on the right track;

  • build your asset model, do your best to use OOTB asset types and relationships (and attributes, also less-so)
  • deploy the model via site-specific Scopes (leave Global Assignment untouched, as a reference)
  • leverage the OMRE WF on marketplace ... it comes in handy
  • be careful building WFs to add integrity ... it's expensive to keep building for boundaries you have missed ... often it's easier to police integrity via Global Views, at least when getting going

(edited)

132 Messages

 • 

9.1K Points

BTW you might want to look at Validation Rules as a way to check for integrity >> Validation rules (collibra.com)

or of course a more fully blown solution using site-specific reports across a site-specific reporting data layer (populated from Insights or Output Module or GraphQL extracts)

Loading...