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

Populating BAM using JMS

Recently I did a POC with BAM 12c at the customer. In a series of post’s I will describe my findings/experiences.
In the first post of this series I described the initial situation (Impact of ACM Implementation on BAM). This post ended up with the following challenge.

We have a ACM Case consisting of about thirty Case Activities. The Case and the individual Case Activities are housed in a private composite (1 + ~30 composites).

Challenge: How can we group/filter in BAM by ‘specific’ metrics that are present in each Composite. For example ‘Department ‘.

In the second post Filtering/grouping in BAM by ‘specific’ metrics (explored solutions) I have 10 recognized/examined solutions appointed for this challenge. In this post one of these solutions (number 10) is further developed.

I will describe an implementation of how to populate BAM via a JMS queue. In a nutshell: we have the following situation:
An ACM Case Management composite (CASE A) with the Case Activities implemented in external BPM processes (Proces 1,2 and 3). The humantask metrics are available in BAM via the ‘default’ channel. For other metrics the composites have to send events. These events are catched by the Event Handling Service. This service puts them on the JMS Queue BAM uses as input source. Graphically represented:

3image1 Continue reading

Filtering/grouping in BAM by ‘specific’ metrics (explored solutions)

Recently I did a POC with BAM 12c at the customer. In a series of post’s I will describe my findings/experiences.
In a previous post I described the initial situation (Impact of ACM Implementation on BAM). That post ended up with the following problem description.

Problem description

We have a ACM case consisting of about thirty Case Activities. The Case and the individual Case Activities are housed in a private (1 + ~30 composites).

Challenge: How can we group/filter in BAM by ‘specific’ metrics that are present in each composite. For example ‘Department’.

In this post I will describe solutions we have recognised/examined to make Management Information (MI) available for this ACM implementation.  Continue reading

Impact of ACM Implementation on BAM

Recently I did a POC with BAM 12c at the customer. In a series of post’s I will describe my findings/experiences.
This is the first post in the series.

As a starting point we have the following situation:

We have an ACM composite consisting of a case with associated BusinessRule component and different BPM processes implemented as Case Activities. See figure below.

1image1

This is one single composite application. This means that there are two objects for BAM (‘VeryHugeCase Activity’ and ‘VeryHugeCase Process’) generated in the ‘Process Analytics’ project.
1image2

Continue reading

BPM PS6: A first brush on the new Case Management functionality

Case management is a way of modeling very flexible and data intensive business processes.

Case management enables you to handle unstructured, ad-hoc processes and their contents and information so that you can make optimal business decision. It focuses on unpredictable business processes which rely on worker knowledge and involve human participants. Case management relies on content and information that help the participants make a decision .

A case can be a collection of information, processes, tasks, rules, services. It requires the worker knowledge, their involvement and active collaboration.

Case management enables you to only define the different activities a user can perform to achieve a goal without defining the workflow process. However it supports dynamic workflows, structured processes and a combinations of both.

Continue reading