Job Description

Hi,

You should understand that for JD generation you need not only one EPC but “the net” of EPC, because your workers works not only in one process. So you need to consider the complete architecture of business processes and also data, organizational architecture. By my practice they are always different for every company (I mean processes and organizational modeling methodology). So you need:

1. Define your methodology of modeling (I think it have already done).

2. Define your template of JD (as a rule it is just Word document with marks of ARIS attributes and rules of their evaluation) and align it with methodology

Regards, Alex

Hi,

Do you know any company which use ARIS job description as a company documentation? I mean, there is no another Job Descripton or Work Description document, they use ARIS document for all the employees.

Best regards,

Ayca

Hello Ayca,

just a few thoughts: It may be a good idea to use capability objects and relate them to the position objects. This way you are independent of actually modelled processes. Generate your job description simply by reporting on the capability descriptions related to a position.

When modelling processes you should assign capabilities needed to support a process step in the EPC. It is true, that this way you achieve a very loose coupling between the process and the position. Also you have to consider how to handle the concept of "roles" in relation to capabilities.

Regards, M. Zschuckelt

Hi,

Yes, some of my clients use job description generated from ARIS, even some of them have covered all core processes in this way.

Regards, Alex