This repository contains a description of a new experimental concept in IBM Operational Decision Manager V8.10.0 called "business situations" and includes a set of examples. Business situations aims to address some complex event processing (CEP) use cases.
Decision Server Insights tracks and analyzes (processing) information (data) about things that happen (events), and derives a conclusion from this data. Keeping data long enough to make the right decision is a CEP dilemma.
Business situations is a concept to identify, detect, and be notified of circumstances that are of special interest. It can keep the special data for longer time periods to counteract something harmful or undesirable, or take advantage of an opportunity.
- 1.0 What are business situations
- 2.0 Experimenting with business situations
- 2.1 How to enable business situations in Insight Designer
- 2.2 How to define business situations
- 2.3 How to identify business situations
- 2.4 How to update/end/abort business situations
- 2.5 How to emit events when business situations are beginning/ongoing/ending
- 2.6 How to test your business situations
- 3.0 Example use cases for business situations
- 3.1 Patient staying in hospital example (event interval, regular notification)
- 3.2 Fire detection using 2 criteria example (simple state over sliding window)
- 3.3 Fire detection using a number of criteria example (more complex state over sliding window)
- 3.4 Shipping package example (timeout)
- 3.5 Detecting missing sensor event (detecting absence of events)
- 3.6 Promotion (a situation that follows a situation)
For issues relating to IBM Operational Decision Manager you can get help through the ODMDev community or, if you have production licenses for Operational Decision Manager, via the usual support channels. We welcome contributions following our guidelines.
© Copyright IBM Corporation 2018.
Icons from https://github.com/IBM-Design/icons licensed under Creative Commons Attribution 4.0 International License