Business Process Monitoring concept

1. Use case and context

Many companies staying on path of digital transformation. Digital transformation is a way how companies execute and understand their business processes, and business process management often used to make transformation possible.

Business process managment concept contain 4 high coupled topics of activity:

1. Design (Plan) 

2. Execution (Do)

3. Monitoring (Check)

4. Change (Act)

Right now Storbpmn make customer life easy in terms of design; execution commonly automated in ERP-like systems ( rarely BPMS-like); monitoring covered by BI-systems; changes performed manually by specific team.

Enterprises seldom use BPMS-systems to automate their processes, because it cost lot of time, money and competence, so natural way to monitor and analize data, provided by BPMS-systems, impossible.

BI-system have lack of BPMN-style visualization, so monitoring in BI impossible.

Last way to automate process monitoring -  use Process Mining tools, but they often target to scrap and collect data from different sources and transform  this data to process description. PM tools aimed to design topic. Also they cost lots time and money. So online monitoring in PM is hard.

2. Solution description

Business Process Monitoring in Stormbpmn is a fast, reliable tool to build a bridge betwin design and monitoring through current IT-system. Using of Storm Business Process Monitoring required tineest changes in it-systems. 

It is saas or on-primise web-based application and REST API / Kafka API., where users should convert current process diagram to monitoring unit and map each element to event, recievied via API.

Is best case connect 1 system to API cost ±1 man-day.

3. Who is customer

1. Huge enterprise with many legacy systems on way of Digital Transformation.
2. Mid-size companies with many SAAS systems, that automate some business process together.

4. Key benefits

1. Visually understand current status of processes/document/application/sales etc.
2. Find bottle neck.
3. Notification about delay in process.
4. Find path of specific process instance.
5. Calculate standard process metircs - throughput, WIP, reservs, most overhelmed activity, etc.
6. Embedded and share report.

5. Public API design

All systems, than can provide event, must send small piece of data via REST API/Kafka API.

All calculation, aggregation and mapping performed by backend with ClickHouse and ElasticSearch. 

Becouse of that contract to API tiny:

POST /v1/public-api/monitoring/event

{
"eventName": "Meeting schedulled", // required
"eventTime": "12:20:03 01.01.2021", //required
"entityId": "rth456-w45hsrth", //required
 "systemName": "1c",//required
"payload": { //
}
}

Rate-limit, authentication and other necessary stuff must be applied to solution.