We’re gradually adding more processes, roles, systems, and dependencies to our ARIS environment. As the repository grows, maintaining a clear structure and avoiding duplicate or outdated process models becomes more challenging.

What practices do you use to keep a large ARIS repository organized and easy to maintain? Do you rely mainly on naming conventions, folder structures, governance rules, regular reviews, or a combination of these?

I’d be interested to hear what has worked well for teams managing larger ARIS environments.

 or register to reply.

Notify Moderator