Doorgaan naar hoofdcontent

Creating KPI with Cordys BAM

Introduction

In a previous Blog I showed how to create a Dashboard from a Business Measure. In this Blog I will show how to create a KPI (Key Performance Indicator). As can be seen from the picture, a KPI is based on a Business Measure. A Business Measure measures parts of a process or data and a KPI monitors whether the measured part reaches a particular value. So:
KPI helps to monitor and capture critical information pertaining to Business Process or Activity.


Step 1 - Create Business Measure for KPI

First you have to create a Business Measure on which the KPI will be based. In this example we take a Webservice as the source for the business measure.
  • Create Business Measure
  • Fill in the following details, and choose the correct Webservice
  • Click Next and Select New to create a new webservice
  • Click Finish
The Business Measure and its corresponding webservice is generated.


The UnitsinstocksMeasure can be used in a Dashboard.

Step 2 - Create KPI

  • Create a KPI
  • Fill in the details of the KPI:
    Name - The name of the KPI
    Description - The description of the KPI
    Goal - Describe the goal of the KPI, in this case the units in stock may not be too low
    Unit of measure - This is the unit in which the value is measured
    Target Value - The value for the enterprise against which is measured
    Ranges - Here you can define several ranges for the KPI
    Select source type - The source of the KPI. In this case it is a webservice, which can not be selected yet in BOP4.0 and must be left empty.

  • Click Next
  • Now you select the Business Measure on which the KPI is based (Select '+') and fill in the parameters



  • Click Next

Now you have to select the value (XPath expression) on which you want to build your KPI. Do not forget to  check "Define Schedule". The schedule is used to call the measure within the defined timeframe within the schedule.


  • Click Next
  • In this screen you can enter the schedule times. DO not forget to check "Define Actions". These actions are triggered when the KPI is reached.


  • Click Next
  • In this screen you can define the Actions, For each action you have the following possibilities:
    - Notification
    - Invoke BPM
    - Call Webservice

Note that the Condition is the Range you have defined in the KPI definition previously.

This concludes the definition of this KPI. The Schedule can be activated by going to the Schedule Manager and execute the schedule for this KPI.



Reacties

Een reactie posten

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept of servin