LINQ won't let you connect two systems to one action, that's because there is likely to be information and actions between the systems. When you add the missing information and actions to the Information Supply Chain they become visible, and potentially reusable in other parts of your organisation.
When you model each separate use of a system with a different action, you are documenting the reality of the systems enabling the flow of information through your Information Supply Chain. In the future, these connections will provide insight about the systems used in your organisation, who uses them and how much they cost as an allocation through your business.
Neil Calvert
LINQ won't let you connect two systems to one action, that's because there is likely to be information and actions between the systems. When you add the missing information and actions to the Information Supply Chain they become visible, and potentially reusable in other parts of your organisation.
When you model each separate use of a system with a different action, you are documenting the reality of the systems enabling the flow of information through your Information Supply Chain. In the future, these connections will provide insight about the systems used in your organisation, who uses them and how much they cost as an allocation through your business.