TH
Background
We re-use the same role (lane-object) in a number of BPMN-models across the process hierarchy and across organizational units (e.g. the role “Field sales representative” which is used within different sales-processes in different sales-organizations within the company). So while sales-processes may differ, the role is fundamentally the same.
Currently, we work to establish a connection between roles and organizational units. We do this through matrix models, where we match roles and organizational units. The result of this will be that users through a role-portal may have immediate access to the processes relevant to them (because they belong to an organizational unit and that OU has been connected to a number of roles which are included in a set of processes).
Problem
However, we run into problems when the “Field sales representative”-role is re-used in sales-processes within for example the US-sales organization and the EU-sales organization. The sales-processes in these different organizations are not necessarily the same but the role is. So when “Field sales representative” has been connected to both US and EU in a matrix model, users from both these organizations will see the total set of processes, not just the ones belonging to their organization (EU or US). This is a problem, because it greatly reduces the value of the role-portal.
Have others faced similar issues?
Another interpretation of your problem is that various (regionally different) positions can execute the same role, whereas the role (by nature) is not regional specific.
At the same time, your regionally specific (sales) processes (seem to) have generalisations. Here, I would assign the role to these and assign positions on the detail process level only.
Consequently, the matrix should match positions and org units.
Based on a user's position(s), she accesses (regional specific) processes, like it is currently done based on the role.
Regarding your problem, the general processes and their association to org. entities (i.e. roles) are irrelevant for the user access to processes. Unless there are other reasons to deal with your general (sales) processes and corresponding roles, I would not model these.
hth
Hi,
As Roles can be performed by any person so defining it by Roles woule be ideal (Role based authorisation) .
And attaching Roles with the Position seperately would be ideal to distinguish who does what. For region specific you can define different relations (matrix). And as suggested by Stefan it should match positions with Org units.
To summarise Role should be used in the process. Authorization chart will say what position will perform what Role based on the department/organization. Org Units will have what position that Org Unit will have.
Thanks
Abhijit Das
