|
How to Perform Root Cause Analysis on Custom Process Optimization Potentials |
Scroll Previous Topic Top Next Topic More |
Probably, the default process behaviors that are provided by the mpmX Root Cause Analysis Template do not cover every optimization potential in a specific process. Therefore, it is possible to aggregate custom process optimization potentials to the root cause analysis.
First of all, we need to specify some guideline to create a new problem.
•Problems need to be created within a table (existing or new) which is connected to the mpmX Data Model by either the key field "CaseID" or the key field "ProcessPathUniqueNo".
•The optimization potential needs to be created as a binary flag within the data model to be recognized correctly by the RCA. The value "1" of this flag means that the case or process variant shows a problem while the value "o" means that the case or process variant shows no problem.
•It is important, that the binary fields get a unique and readable name, because this field names will be displayed as the anomaly descriptions in the front end.
|
The optimization potential has to be created for a CaseID or a ProcessPathUniqueNo as a binary flag, where the value "1" represents the problem and the value "0" represents that there is no problem. Give the flag a readable and unique name. |
To create a new optimization potential for the root cause analysis the following steps are recommended:
1.Define the optimization potential and think about how it can be detected in the data.
2."Simulate" the calculation of the optimization potential in the front end to understand which fields of the data model are included and which fields need to be calculated in the script.
3.Create a new tab in the script editor, place it before the tab "5. Root Cause Analysis" and give it a name, for example "Custom RCA-Rules".
4.Calculate the new flag and connect it either to the CaseID or the ProcessPathUniqueNo.
|
Be cautious not to duplicate table entries, revise this in the data model, if the table with the new flag has more CaseID than the CaseTimes-table or more ProcessPathUniqueNo than the pa_activity_log, something went wrong. |
5.Write the new flag into the inline table "RootCauseAnalysisFlags" that was introduced in the section Use Root Cause Analysis on Your Data.
In the example below the flag "My new process optimization potential" was added in the first line.
Decide on which dashboard you want to display the root cause results for the optimization potential by adding the sheet name in the column "RelatedSheet".
RootCauseAnalysisFlags:
load * inline
[CalculateInRCA, |
FlagName, |
FlagTable, |
ObservationType |
RelatedSheet |
y, |
My new automation optimization potential, |
CaseInformation, |
CaseID |
Automation |
y, |
Low process governance, |
CaseTimes_$(mvProcessDescription), |
CaseID |
Conformance |
y, |
Target lead time missed, |
CaseTimes_$(mvProcessDescription), |
CaseID |
Lead Time |
n, |
Target processing time missed, |
CaseTimes_$(mvProcessDescription), |
CaseID |
Lead Time |
n, |
Target idle time missed, |
CaseTimes_$(mvProcessDescription), |
CaseID |
Lead Time |
]; |
|
|
|
|
6.Run the data load. The new problem will be investigated and the results will automatically show up in the front end.
If any problem with the custom optimization potential should occur, think again: is the optimization potential a flag with the values "1" or "0" for a process variant or case?
