TH

Hi forum,

We use collapsed pools to create interfaces to other processes throughout our process map. In some cases, a process will have interfaces to so many other processes that the number of collapsed pools on the model prevent users from getting an overview (see attached example).

We are looking for ideas on how to model these cases in a way that allows us to retain our data structure (a process knows by the connections established to other processes how it is connected to the rest of the process map) but also allows users to get an overview of a process model with many process interfaces. Also we would prefer to not modify BPMN-methodology.

Any good ideas out there?

File attachments

Featured achievement

Rookie
Say hello to the ARIS Community! Personalize your community experience by following forums or tags, liking a post or uploading a profile picture.
Recent Unlocks

Leaderboard

|
icon-arrow-down icon-arrow-cerulean-left icon-arrow-cerulean-right icon-arrow-down icon-arrow-left icon-arrow-right icon-arrow icon-back icon-close icon-comments icon-correct-answer icon-tick icon-download icon-facebook icon-flag icon-google-plus icon-hamburger icon-in icon-info icon-instagram icon-login-true icon-login icon-mail-notification icon-mail icon-mortarboard icon-newsletter icon-notification icon-pinterest icon-plus icon-rss icon-search icon-share icon-shield icon-snapchat icon-star icon-tutorials icon-twitter icon-universities icon-videos icon-views icon-whatsapp icon-xing icon-youtube icon-jobs icon-heart icon-heart2 aris-express bpm-glossary help-intro help-design Process_Mining_Icon help-publishing help-administration help-dashboarding help-archive help-risk icon-knowledge icon-question icon-events icon-message icon-more icon-pencil forum-icon icon-lock