There are some general settings you have to do to prepare the Template App:

 

Enable logging with the Template App:

1.If you want to trace the MPM app's performance adjust the settings that enable logging. Then the script will write a log to a QVD file which also can be analyzed on the sheet Application Performance Log.

a)Navigate to the tab 0. Init in the data load editor.

b)Create a data connection where you would like to save the qvd file that is generated  when logging is activated. Save the data connection in the variable mvDir_logs.

 

Let mvDir_logs = 'lib://MPM_Logs/';

 

c)If you want to log the script performance and find script-optimization potential set the variable mvLogApplicationPerformance to 1. If you do not want to enable logging set it to 0.

 

Let mvLogApplicationPerformance = 0;

 

2.If you want the logging to be enabled but don't want it to appear in the data model and the front end at the sheet Application Performance Log, just activate the "DROP Table $(mvLogTable)" part by deleting the comment-slashes.

 

if('$(mvLogApplicationPerformance)'='1') then 

 call MW_stopLogService;

 //DROP Table $(mvLogTable);

end if

 

 

 

Variable: mvStoreMPMModelQVD

1.Navigate to the tab 0. Init in the data load editor.

In line 23 you have the variable mvStoreMPMModelQVD which stores the output of the MPM algorithm in the data folder.

2.If you want to save the .qvd-output-data, set it to "1". If you don't want to save it, set the variable to "0".

Keep in mind that if you set the variable to "1", physical memory is used to store the data on your server. If you set it to "0", RAM memory is used to store the data. Therefore, we do not recommend setting the variable to "0" when there are large datasets.

 

Let mvStoreMPMModelQVD = 0; 

 

 

Variable: mvSurpressLoops

2.If you want to reduce the number of process variants by surpressing direct loops, set it to "1". If you don't want to surpress direct loops, set the variable to "0". Default is  "0".

Surpress direct loops means that, for three variants 0-101-102-99999999,  0-101-102-102-99999999,  0-101-102-102-102-99999999 only two process variants are caluclated: one without loop and one with loop 102-102.

If you do not surpress the direct loops, three process variants will be calculated: one without loop, one with exactly one loop and one with exactly two loops.

 

Let mvSurpressLoops = 1; 

 

 

Variable: mvDeltaLoad

3.If you want to delta load the app, set the variable to "1". If you don't want to, set the variable to "0". Default is  "0".

For delta load the script tab 1. Load Delta EventLog needs to be used instead of 1B. Load EventLog.

 

Let mvDeltaLoad = 0; 

// set to 1 if you want to load an eventlog delta and concatenate it to the older eventlog output; set to 0 if you load a complete event log

 

 

Variable: mvLeadTimeFormat

4.Choose the time format that you prefer for the time related PPIs.

•"TimeDynamic" - the time related PPIs will be shown dynamically as days, hours, minutes or seconds, but front-end performance might be slower,

•"TimeInDays" - the time related PPIs will be shown as days,

•"TimeInHours" - the time related PPIs will be shown as hours,

•"TimeInMinutes" - the time related PPIs will be shown as minutes,

•"TimeInSeconds" - the time related PPIs will be shown as seconds,  

•"TimeAsDuration" - the time related PPIs will be shown as a duration in the format 'd hh:mm:ss'.

 

Let mvLeadTimeFormat = 'TimeAsDuration';

 

Variable: mvTimeRange

5.If you want to change the time frame for the strategic dashboard, choose between the following values:

•"YTD" - YearToMonth,

•"MTD" - MonthToDate,  

•"FYTD" - FiscalYearToDate.

 

Let mvTimeRange = 'MTD';

 

 

Variable: mvCalendarFM

6.This variable helps to configure the master calendar. Just insert the number of the month in which the fiscal year starts.

 

LET mvCalendarFM = 8;

 

 

Variable: mvMaxDateOrToday

7.You can set the reference date for time range comparisons on the strategic dashboard like year to date or month to date. The possibles values are "maxDate" (default setting) or "today".

 

Let mvMaxDateOrToday = 'maxDate';

 

Variables: mvProcessDescription and mvCaseLabel

8.Change the names of the two Scenario variables and Case definition variables.

d)Navigate to the tab 0. Init in the data load editor.

e)Adjust the process name of your analysis which is stored in the variable mvProcessDescription (line 28). Some examples for process names are Purchase to Pay (P2P), Order to Cash (O2C), Manufacturing Process, Helpdesk, etc.

f)Label a case by saving a new name in the variable mvCaseLabel (line 31).

 

LET mvProcessDescription = 'PROCESS_DESCRIPTION';

LETmvCaseLabel = 'CASE_LABEL';

 

 Helpdesk example:

 

LET mvProcessDescription = 'Helpdesk';

LET mvCaseLabel = 'CaseID';

 

 

Tutorial

 

Start the video below to see a short tutorial about how to use the sheet.