1 / 6

Business Activity Monitoring and Management Panel Session Summary Draft

Business Activity Monitoring and Management Panel Session Summary Draft. Event Processing Symposium March 14-16, 2006 Eric Wayne, IBM (on behalf of six panelists) ewayne@us.ibm.com. BAM Panelists. Summary– Common Elements.

harsha
Download Presentation

Business Activity Monitoring and Management Panel Session Summary Draft

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Business Activity Monitoring and ManagementPanel Session Summary Draft Event Processing Symposium March 14-16, 2006 Eric Wayne, IBM (on behalf of six panelists) ewayne@us.ibm.com

  2. BAM Panelists

  3. Summary– Common Elements • Industries: Energy, Financial Services, Manufacturing/Logistics, Shipping/Logistics • Integration of BAM with other software in customer environment • BPM, rules engine, packaged apps, legacy/custom apps, • System Management, • Business Intelligence • Recurring use cases • Track and trace • Process visibility spanning apps and silos • *External partners – where control leaves enterprise – key visibility pain point • Dashboards/alerts, detection of patterns representing an issue or situation • Impact of system events on business • Anticipate problems • Range of event volume metrics. Range of analysis, correlation techniques.

  4. Summary– Common Elements • Issue: Scope creep on BAM requirements • When LOB views a dashboard, quickly see new possibilities/areas • When process being monitored are designed concurrently • Question discussed: is approach of using a standard event format necessarily in conflict with requirement for being non-intrusive to systems being monitored? • Issue: Out of order events, good programmer-free solution?

More Related