Use case: Continuously improve processes
The use case is an example of the business flow in credit processing. The change management activities described in the following correspond to those described in the procedure model. The starting point is the existing credit process that is to be changed due to the improvement potential identified in the use case.
The specified processes and databases are fictional and are only intended to illustrate a change management process and the change management functionality in ARIS.
This use case is based on the following scenario:
After a credit application was received, the person responsible as a model user refers to the QM database to obtain information about processing steps and approval paths. The person responsible notifies the process manager about possible process improvements. The process manager arranges for the process change to be implemented by involving the improvement manager who, in turn, ensures process adaptation by the modeler. Now, the process manager can publish the changed process.
The use case includes the following steps:
The person responsible discusses the suggestion with the process manager. Both deem the suggestion a significant process improvement because the application wait times and orientations would be significantly reduced:
Persons responsible would only have to process credit applications twice instead of three times, that is, once when the application comes in, and the second time when the application is finalized.
The superior would see the unquestionable credit applications only once, that is, before finalization. The superior could check the credit applications and decide about their approval by viewing the data only once.
Person responsible and process manager come to the result of suggesting a model change: The procedure for questionable credit applications is to be retained and the procedure for unquestionable credit applications is to be redefined.
The person responsible enters the model change proposal using ARIS.
To do so, the person responsible clicks the model name on the Explorer tab, activates the Contents tab bar, and selects
Change management > Submit proposal. The Submit improvement proposals dialog opens.First, the person responsible verifies in the Previous proposals box whether the improvement has not been suggested by any other model user. This is not the case.
Then, the person responsible ensures that the language is selected in which the proposal is to be entered.
Now, the person responsible enters the improvement proposal.
Afterwards, the person responsible saves the improvement proposal by clicking OK and closing Submit improvement proposals dialog.
As soon as the improvement proposals are saved they are available to the improvement manager.
Because the improvement manager has the privileges required, he selects the model name Credit processing, activates the Contents tab bar and clicks
Change management > Edit proposals. The Edit improvement proposals dialog opens.The improvement manager selects the relevant language and evaluates the improvement proposals entered in this language.
For the improvement proposal submitted by the person responsible, the improvement manager defines the measure "Please change the model in line with the proposal."
The improvement manager adds this comment: "The process participants are informed."
The measure is assigned priority 9 because the company requires that the highest number means highest priority. The improvement manager decides on this categorization because this simple process change results in significant time savings and should therefore be implemented as quickly as possible.
The end date is the date of the work day after next.
The improvement manager sets the status to In process.
From the list, the improvement manager selects modeler Meyer as the person responsible and exits the dialog by clicking OK.
As soon as the improvement manager has exited the dialog, the modeler in charge can view the tasks.