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.
- Impact of ACM Implementation on BAM
- Filtering/grouping in BAM by ‘specific’ metrics (explored solutions)
- Explored solution: Fool BAM with database hack
- Explored solution: Populating BAM using JMS
- BAM Command
- Renew BAM Demodata
- BAM Database
- BAM Projects get corrupted
- BAM Projects requirements
- BAM Data Objecten
- BAM Calculated Fields
- BAM Queries
- BAM Views
- BAM Parameters
- BAM KPIs
- BAM Alerts
- BAM Dashboards
Conclusion / Opinion
During this POC I have really learned a lot from the possibilities and impossibilities of Oracle BAM. My conclusion is that BAM is a powerful product with so many possibilities. But I have the feeling that their are only a few users. What is the cause of that?
Downside of BAM is that it is a very technical product, this makes it very difficult to explore the full potential of the product. Also the documentation not really helps here, also this is very technical in nature. There are lists of all possibilities, but effects from a business perspective is missing.
If you want to know more about a specific item, please send me a message, I will do my best to help you.