ARIS HR Strategy

Hi Andy. To date we are using role (ex: Project Team, Sourcing Specialist, Customer Service Specialist, Demand Planner, etc.) or department. As an organization we aren't necessarily consistent in Titles throughout different business units and regions and sometimes we use generic titles (ex: IS Professional to cover about 30 different people/roles). This can make it difficult to manage Titles in ARIS and it probably wouldn't add any more value than capturing role at this time. I'd be interested to hear how others are having success with this.

Angie

Hi Guys,

As a part of a systems implementation project we have some very detailed and granular roles defined in our lower level business processes. E.g. purchase order processor, work order approver, maintenance master data approver.

From a system's security perspective such roles provide some good insight into the system objects relevant for that role. The lower level processes include transaction codes and system functionalities that the role must have. However from a business end user perspective they are not able to relate to such specific and granular roles. I totally understand their problem, I'd rather use roles such as employee, manager, warehouse clerk etc. 

We're still looking for a solution that meets both business end user's needs and the system security needs.

Any ideas?

Cheers

Ganesh