BAM POC wrap-up and recording

This is the last post in a series about BAM. In this series of a total of 18 post (including this one) I have described my overall experiences with BAM while performing a POC. Each post contains a piece of the BAM journey of discovery. All post together hopefully give a picture of the possibilities of BAM, but no more than that. Because BAM has many more possibilities.  I started sketching the initial situation (an ACM implementation), the problems we have encountered in the filling of BAM and the examined solutions (some in more detail). Next requirements and an issue I had during the writing of this series. In total I have devoted 9 posts to it. Next I described the experiences per development step in BAM (see figure below). The following table lists all the post, including a link to the post.

  1. Impact of ACM Implementation on BAM
  2. Filtering/grouping in BAM by ‘specific’ metrics (explored solutions)
  3. Explored solution: Fool BAM with database hack
  4. Explored solution: Populating BAM using JMS
  5. BAM Command
  6. Renew BAM Demodata
  7. BAM Database
  8. BAM Projects get corrupted
  9. BAM Projects requirements
  10. BAM Data Objecten
  11. BAM Calculated Fields
  12. BAM Queries
  13. BAM Views
  14. BAM Parameters
  15. BAM KPIs
  16. BAM Alerts
  17. BAM Dashboards

Continue reading

BAM Dashboards

I shall now turn to the last part in the development cycle of a BAM project. The part where it for the end user is all about. The dashboards.

As usual first a brief explanation from the Oracle documentation.

A business view is a visual representation of data fetched by a business query or one or more key performance indicators (KPIs). A dashboard is a collection of related business views. To display data to users, a view must be included in a dashboard. Dashboards can display point-in-time or real-time information (active data). A tabbed dashboard contains other complete dashboards, which you view by clicking the tabs.

In my example project I created a tabbed dashboard containing two dashboards.

Continue reading

BAM Alerts

This post (next in the BAM series) is about BAM Alerts. Alerts were not part of the POC, but in the blog series I also wanted to pay attention to it, resulting in this post. I have made a very small example to get some feeling in there and will not get into all the details of alerts.

As usual, first a piece of theory from the Oracle documentation:

An alert performs one or more actions when launched by an event and filtered by one or more conditions. An event can be an amount of time, a specific time, a date and time, a repeating event between two dates, a change in a data object, output from a continuous query, or a manual event. A condition restricts the alert to an event occurring between two times or dates or to a specific day of the week. An action can send a notification, perform a data object operation, invoke a web service, call an external method, or launch other alerts. Continue reading

BAM Parameters

Next in the row of my BAM series will be the BAM Parameters.

First some theory from the oracle documentation

A parameter is a variable representing the value of a data field. A filter is a condition applied to data retrieved by a query or view, which can reference one or more parameters. A prompt is a request for the user to specify the value of a parameter. For example, you can filter an asylum cases query by judicial authority, create a parameter for the judicial authority, and prompt the user to choose the judicial authority when the query is referenced by a view in a dashboard. Continue reading

BAM Views

After the Queries and KPIs I will continue with the next topic. Business Views or shortly just Views.

As usual I first start with a piece of theory from the oracle documentation.

business view is a visual representation of data fetched by a business query or one or more KPIs. In most views, numeric data fields, called measures, are grouped by non-numeric data fields, called dimensions. For example, lawsuit costs, a measure, can be grouped by department, a dimension. An aggregation is a computation based on multiple values in a data field, such as a sum or average. Continue reading

BAM KPIs

BAM KPIs

Next I my BAM Series, a post about BAM KPIs.


First the theory from the oracle documentation

Understanding KPIs

There are two major types of performance indicators: outcome metrics and driver metrics. Outcome metrics, sometimes called lagging indicators, measure business activity that a strategy is designed to achieve, such as return rate per month or average call processing time for the last moving hour. Driver metrics, sometimes called leading indicators, measure business activity that influences the outcome metrics. Continue reading

BAM Project Requirements

In recent posts I treated BAM Data Objecten and BAM Calculated Fields. I am now at the point to start with a so called BAM project. But before I will do that, first something else.

The problem of last week (BAM Projects get corrupted) has given me extra time to think about the rest of the blog series. In doing so, I came to the conclusion that I had not yet taken the functional requirements as a subject. But without these requirements the upcoming blogs are hard to follow, so in this post I first will mention the functional requirements, from a technical point of view (and briefly describe them). I have translated a drawn dashboard image into the following requirements.

  1. Click through to humantask. Link to a rule action. Add ability to click through to the related humantask, to view it or act on it as assigned rep.
  2. Change View type at runtime. Possibility to switch from view of e.g. a line chart to a bar chart or a list view.
  3. Click through to case details via the used hierarchical organization structure (Judicial System, Department, Team and Employee).
  4. Summary of tasks. Showing number of open tasks, newly opened tasks and recently closed tasks. Increase/decrease in percentage of number of tasks.
  5. Starting a related system. Link to a view action. E.g. start the worklist application or a specific website.
  6. Filter of displayed data in multiple views at once. E.g. all views in which a department is shown, and where it is possible to filter on the department, display information of the same department(s).
  7. Showing tasks and deadline’s. Indicate how many urgent tasks there are on the basis of urgency.
  8. Change parameters at runtime such as the degree of urgency. Urgency is the number of days for due before it is urgent.
  9. Updating views without pressing the refresh button. Use active data so that the view is dynamically updated.
  10. Dynamic displaying images. Depending on the selected data a different picture is shown.

Continue reading

BAM Calculated Fields

In my previous blog, I have made a start with the study of the BAM components. I have started with the Data Objects (BAM Data Objecten). In this post I will continue with them.

1-project-dataobjects

In order to be able to make the desired dashboard for the POC, there is a need for yet a number of calculated fields. These calculated fields are defined as part part of the Data Object. Several of the required calculated fields are also present in the standard Data Objects. These can be taken over. Because the field names do not match directly these must still be adapted. In the standard Data Objects are all calculated fields defined as attribute. To give them some context I have defined some of them as dimensions and measure. But this affects the different queries where this is not immediately obvious. It is stated at the different query types but it is rather unclear.  Continue reading