TB

Hi, Im wondering if anyone can shed some light on the difference between the following relationship types and when to use either one.

When connecting Input/output objects to a function/activity object I am presented with the following relationship types in the attached image.

Thanks......Terry

 

File attachments
by André Vitor Oliveira
Posted on Wed, 09/11/2019 - 19:42



Hi Terry,

I got some explanation from help method and also from our community and maybe some expert can add commentaries to enrich our knowledge here, please check these information:



Permanent increase of the capacity of capacity resources

The capacity of a capacity resource is increased if it is linked to a function via a produces connection and the function is carried out. You can control the quantity by which it is increased using the Quantity connection attribute of the Simulation attribute type group. If the Quantity attribute has not been specified, the capacity of the resource is not increased when the function is carried out. The function is not carried out if this causes the capacity of the resource to increase above the value specified in the Maximum capacity attribute.

Which connections are relevant to the simulation?

Name =produces  

From "Function" to "Capacity resource" 

Control attributes =Quantity

Type = Integer (0 to + infinite)

has output of/is output of (839, CT_HAS_OUTPUT_OF)

Name =has as output

From = "Function" to "ERM attribute"

Control = Operator

Type= (:=, +, -, *)

From our community:

The initial value of such an ERM attribute by connecting it with a "has output of" connection to a function and using a ":=" operator. When setting the value you can also specify a probability distribution for the operand.

The conditions allow you only to check for fixed values, e.g. "greater than zero". But you can influence the value of the ERM attribute (which actually becomes a part of the token being routed through the process). With a "has output of" connection within the loop you can, for example, decrement the value of the ERM attribute by 1. If you add such a construct, the simulation should execute the loop as many times as the initial value of the ERM attribute was and then exit through the event with the opposite condition, which could e.g. be "less or equal to zero".

BR

AO

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