AY
Hi Aris,
Quick question ...
May I know under what conditions during the design of VACD, EPC and FAD, an occurrence copy should be encouraged to use while under what conditions during modelling an occurrence should be strongly discouraged?
It would be good if you can provide an example in your explanation. Thanks.
AY
Hello AY,
the rule is very simple: In an EPC everything on the control flow (Functions, Rules, Events) should be never re-used as occurrence copies. They are the unique place where the resources (Roles, IT Systems, Risks, Capabilities, Services, Business objects, Products ...) of your enterprise come together to describe their contribution to the value creation. Those resources are taken from other areas of management ("object libraries" in the simplest form). Hence they are used as occurrence copies from the place where they are managed. Two exceptions from this rule: The process interface is an occurrence copy of the object from a VACD one level above the EPC. The event following the predecessor process interface is an occurrence copy of the terminating event in the predecessor process (where it leads to a process interface to "this" process).
In VACDs you don't have occurrence copies of value-added chains. Exception only, if you want to depict the object from the hierarchy level above as an occurrence copy. If you show other objects, e.g. Products or org. units in your VACDs they are occurrence copies.
FADs always have the function object from the EPC or VACD they are assigned to as an occurrence copy. Additionally all satellites you show in the FAD should be occurrence copies from their respective areas of management. This is the same rule as in the EPC. FAD is only the layout-helper to hide information in the EPC to the FAD and make the EPC leaner.
