Profile picture for user jpicchioni

VACD Symbols

In the Value Added Chain Diagram, VACD, there are two different types of chevron symbols that I have seen for a function.  Can someone provide some insight as two what the difference is between the two symbols and when/why you would use one over the other?  Thanks!

 

 

by Alexander Cherednichenko
Badge for 'Answermachine' achievement
Posted on Fri, 01/20/2012 - 16:25

In practice, two different symbols on VACD model may be used for visual separation of processes, which are situated on different level of specification.  For example, lower symbol may be used for processes of the first level (core processes) and upper symbol for processes of the second level (subprocesses)

0
by Roland Woldt
Posted on Fri, 01/20/2012 - 18:06

There is no difference in the symbol except the shape (all attributes are identical for example). What I do as one of the first things in a Methods and Conventions workshop is to agree on one of the two and remove the other one from the filter to avoid confusion with clients.

0
by John A. Picchioni Author
Posted on Sun, 02/05/2012 - 22:54

Thanks for the feedback!

0
by Krisztian Varga
Posted on Fri, 09/22/2017 - 11:12

Hi Everyone,

Although this thread is kinda old, I just had the same question, and found in practice, that I cannot connect the second type of symbol to a Organizational unit, but I can do that with the first object.

So... there might be some difference.

Regards,

Krisztián VARGA

0
by M. Zschuckelt
Posted on Fri, 09/22/2017 - 11:51

Hello,

my answer is just about the same one as Roland's 5 years ago. In your conventions workshop you decide on the method, what to depict in which model type at what level. And if you are missing a connection type you desperately want, either modify the model type to allow it (or maybe it's just a matter of allowing the connection in the filter), or derive a model type from VACD (named with the terminology of your metamodel, e.g. "Level 1 process" or whatever) and allow the connection there. You might go as far as defining your own derived model types for every artefact in your method. Especially in the Enterprise Architecture part of modelling this is a strong tool, because application system type diagrams tend to be used for multiple stakeholders. If you give each type of stakeholder his individual derived model type you can differentiate them in the method filter and everybody gets a sensible model type name and more importantly, only the symbols and connections he needs for his viewpoint.

Regards, M. Zschuckelt

0

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