This page (revision-18) was last changed on 25-Oct-2013 15:36 by Albrecht Striffler

This page was created on 25-Oct-2013 10:40 by Albrecht Striffler

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
18 25-Oct-2013 15:36 9 KB Albrecht Striffler to previous
17 25-Oct-2013 15:12 9 KB Albrecht Striffler to previous | to last
16 25-Oct-2013 15:12 9 KB Albrecht Striffler to previous | to last
15 25-Oct-2013 15:10 9 KB Albrecht Striffler to previous | to last
14 25-Oct-2013 15:10 9 KB Albrecht Striffler to previous | to last
13 25-Oct-2013 13:15 9 KB Albrecht Striffler to previous | to last
12 25-Oct-2013 12:42 9 KB Albrecht Striffler to previous | to last
11 25-Oct-2013 12:41 9 KB Albrecht Striffler to previous | to last
10 25-Oct-2013 12:40 9 KB Albrecht Striffler to previous | to last
9 25-Oct-2013 12:39 9 KB Albrecht Striffler to previous | to last
8 25-Oct-2013 11:44 9 KB Albrecht Striffler to previous | to last
7 25-Oct-2013 11:42 9 KB Albrecht Striffler to previous | to last
6 25-Oct-2013 11:40 9 KB Albrecht Striffler to previous | to last
5 25-Oct-2013 11:39 9 KB Albrecht Striffler to previous | to last
4 25-Oct-2013 11:24 956 bytes Albrecht Striffler to previous | to last
3 25-Oct-2013 10:59 584 bytes Albrecht Striffler to previous | to last
2 25-Oct-2013 10:59 562 bytes Albrecht Striffler to previous | to last
1 25-Oct-2013 10:40 5 bytes Albrecht Striffler to last

Page References

Incoming links Outgoing links
Doc KPI
Doc KPI

Version management

Difference between version and

At line 1 added 4 lines
%%information
The functionalities described on this page are only available using a commercial extension.
/%
At line 20 added one line
At line 19 removed one line
At line 21 changed one line
In the following section a common way to define a KPI analysis is described. For most use cases a more plain configuration may be sufficient, as described in [section 3.2]
In the following section a common way to define a KPI analysis is described. For most use cases a more plain configuration may be sufficient, as described in section ["Plain KPI Configuration"|Doc KPI#Plain KPI Configuration]
At line 31 changed one line
Using the new knowledgebase, as the next step the actual variables used in the KPI analysis can be collected and defined using the %%Question-markup.
Using the new knowledgebase, as the next step the actual variables used in the KPI analysis can be collected and defined using the {{%%Question-markup}}.
At line 36 removed 3 lines
denkbares GmbH Seite 5 von 12
User Manual „KPI-Analysis“, 18.10.2013, Version 1.3
At line 73 changed 6 lines
3.1.4 Specifying the KPI Markup
After all KPIs are defined and calculated, the actual %%KPIAnalysis markup needs to be added to KPI page. In the markup, the different KPIs to be analyzed and also the cases to be executed have to be specified. The KPIs will be evaluated for every knowledge base that compiles the package the KPI markup is part of.
To add a particular KPI, the annotation @column can be used, defining a column in the excel analysis result file. Any question or solution in the knowledge base can be set as a KPI. The added KPIs will be displayed as the columns in the resulting excel table (see section 4.1).
To add cases, the annotation @case can be used. All cases or test cases defined in the knowledge base can be set. Auto completion will help to use the right name/identifier for the case. Additionally, a regular expression can be used to define all cases that should be included in the result.
By default, all purging is disabled for KPI analysis. This may lead to high memory consumption if analyzing huge cases with very frequent value changes. To avoid this, purging can be enabled by using the annotation @purge, which can be set to enabled or disabled.
3.1.5 Example for a KPI wiki page
!Specifying the KPI Markup
After all KPIs are defined and calculated, the actual %%KPIAnalysis markup needs to be added to KPI page. In the markup, the different KPIs to be analyzed and also the cases to be executed have to be specified. The KPIs will be evaluated for every knowledge base that compiles the package the KPI markup is part of.\\
To add a particular KPI, the annotation @column can be used, defining a column in the excel analysis result file. Any question or solution in the knowledge base can be set as a KPI. The added KPIs will be displayed as the columns in the resulting excel table (see section [KPI Result|Doc KPI#Generating the KPI results]).\\
To add cases, the annotation @case can be used. All cases or test cases defined in the knowledge base can be set. Auto completion will help to use the right name/identifier for the case. Additionally, a regular expression can be used to define all cases that should be included in the result.\\
By default, all purging is disabled for KPI analysis. This may lead to high memory consumption if analyzing huge cases with very frequent value changes. To avoid this, purging can be enabled by using the annotation @purge, which can be set to enabled or disabled.\\
! Example for a KPI wiki page
At line 81 added 3 lines
%%prettify
{{{
At line 85 added one line
At line 89 added one line
At line 85 changed one line
%%Question KPI_Date [date] KPI_YN [yn] KPI_Choice [oc] KPI_Num [num] KPI_Text [text] %
%%Question
KPI_Date [date]
KPI_YN [yn]
KPI_Choice [oc]
KPI_Num [num]
KPI_Text [text]
%
At line 87 changed 4 lines
%%Variable KPI_Date = firstChange(filter(Solution[], established)) %%Variable KPI_YN = QuestionNum[KPI_Date] > 15
denkbares GmbH Seite 7 von 12
User Manual „KPI-Analysis“, 18.10.2013, Version 1.3
%%Variable KPI_Num = count(filter(QuestionNum[], '>', 25)) %%Variable KPI_Text = QuestionText[KPI_Date]
%%Variable KPI_Date = firstChange(filter(Solution[], established))
%%Variable KPI_YN = QuestionNum[KPI_Date] > 15
%%Variable KPI_Num = count(filter(QuestionNum[], '>', 25))
%%Variable KPI_Text = QuestionText[KPI_Date]
At line 107 added one line
At line 93 changed one line
@column: KPI_Date @column: KPI_YN @column: KPI_Choice @column: KPI_Num @column: KPI_Text @case: Cases/2012031332 @case: Cases/2012070952 @case: Cases/2012035580 @case: Cases/2012066245 @case: Cases/2012119943
@column: KPI_Date
@column: KPI_YN
@column: KPI_Choice
@column: KPI_Num
@column: KPI_Text
@case: Cases/2012031332
@case: Cases/2012070952
@case: Cases/2012035580
@case: Cases/2012066245
@case: Cases/2012119943
At line 95 changed one line
3.2 Plain KPI Configuration
}}}
/%
!! Plain KPI Configuration
At line 97 changed one line
Example:
\\
Example:\\
%%prettify
{{{
At line 99 changed 3 lines
@column: KPI_Date = firstChange(filter(Solution[], established)) @column: KPI_YN = QuestionNum[KPI_Date] > 15
@column: KPI_Num = count(filter(QuestionNum[], '>', 25)) @column: KPI_Text = QuestionText[KPI_Date]
@case: Cases/.*
@column: KPI_Date = firstChange(filter(Solution[], established)) @column: KPI_YN = QuestionNum[KPI_Date] > 15
@column: KPI_Num = count(filter(QuestionNum[], '>', 25)) @column: KPI_Text = QuestionText[KPI_Date]
@case: Cases/.*
At line 137 added 3 lines
}}}
/%
At line 104 changed one line
3.3 Generating the KPI results
!! Generating the KPI results
At line 106 changed 6 lines
3.3.1 Run Analysis in KnowWE
The tool menu of the KPI markup will contain a button to run all the cases and simultaneously generate the KPI results. After the results are generated, they will be
denkbares GmbH Seite 8 von 12
User Manual „KPI-Analysis“, 18.10.2013, Version 1.3
added as an attachment to the KPI page and the KPI markup will provide a link to directly download the latest result.
3.3.2 KPIs using KnowWE-Headless-App
! Run Analysis in KnowWE
The tool menu of the KPI markup will contain a button to run all the cases and simultaneously generate the KPI results. After the results are generated, they will be added as an attachment to the KPI page and the KPI markup will provide a link to directly download the latest result.
! KPIs using KnowWE-Headless-App
At line 113 changed one line
To generate a specific KPI result, the argument –kpi followed by the name of the KPI article can be added. The argument –sd will allow to specify a directory where
To generate a specific KPI result, the argument –kpi followed by the name of the KPI article can be added. The argument –sd will allow to specify a directory where\\
At line 154 added 6 lines
This page (revision-18) was last changed on 25-Oct-2013 15:36 by Albrecht Striffler Top