Finding and fixing ARIS Models that were created with a different method?

by Mr. Edmund Tan (2010-12-06) in group We Love BPM

Hi Everyone,

Is it possible to search for all models within an ARIS tADB hat were created with a different method that you are currently logged in as? (currently this ADB is just south of 10k models)

I've inherited an ARIS installation that for some reason or other had allowed users to employ the entire method for model creation.  As you can imagine now with a specific method in place the models created during this period will/are having issues (shadow boxes, ARIS BP representations, etc.).  I'm attempting to scan the ADB in order to locate these guys and attempt to fix them for the exsiting method.  I'm wondering if there are any tools or techniques within ARIS that could help me.

Please and thanks

Edmund


Comments

by Mr. Rick Bosworth (2010-12-06)

I created a semantic check that looks for objects that are used but are not in our BP filter. Unfortunately it will only work at the object level as symbols are not available in semantic checks (unless you write your own in java). That would sure be a useful report to have though!


by Mr. Martin Schröder (2010-12-08)

Hello Edmund,

the semantic check approach will give the most precise results, but there are some features of ARIS to help you to narrowing down your suspects.

You can generate a new filter from the ADB (details see this post), output the filter information in Excel and compare it with the report of your desired method filter. A diff would show the object or symbol types to look for.

Then you can apply the predefined report in the category administration to replace unwanted object types.

Maybe this macro and report by Adnan Shahab is useful. If you had complete meta-models of both filters you could do a model comparison report to find unwanted model, object or symbol types.

Regards, Martin


by Mr. Edmund Tan (2010-12-15)

Thanks for your insights at very least you've pointed me in a positive direction to persue such an issue.  I'll keep you posted on what I find.

 

Edmund.