Incentage Process Cockpit

With the Incentage Process Cockpit you stay in control of your business processes and service quality. The Incentage Process Cockpit protects you from reputation risk and risk of financial damage.

The Challenge

The requirements of business process automation go beyond the topics of transport and conversion. Often, due to business needs, some processes in an organisation are outsourced. Process steps are spread across multiple business units both inside and outside the organisation. Business activity monitoring and transaction control is especially important when working with external organisations (e.g. when dealing with a broker, it is important to automate processing and raise alerts when processes do not behave as expected).

Co-operation in the financial industry depends on the quality of information flowing between the participants. The Incentage Process Cockpit controls the quality of both the information and the processes.

The Solution

The Incentage Process Cockpit has the flexibility to monitor and control any business process, information flow and systems of an infrastructure – including in–house developed systems, package solutions and industry systems.

Users are informed of the quality and completeness of freely configurable events. Business partners can be assessed by the quality of their processes. Infrastructure components can be analysed for their availability and quality. When used in a SWIFT context the Incentage Process Cockpit integrates with the SWIFTNet Exceptions and Investigations services.

Background

With the Process Cockpit, Incentage introduces a system which is optimised for clarity and for ease of use. The IPC collects status and events, processes this information and provides a view onto the business activity from different angles.

There are IPC Gates that collect information about messages from various sources and IPC Sensors that track the state and health of the involved infrastructure. The collected information is processed and forms part of message flows as well as processes that may span over multiple separate messages. The picture below illustrates the dynamic way of deriving sub-flows. Sub-flows can be defined by simply selecting a step of the overall flow. Any message that occurred in that step is automatically part of the sub-flow.

The behaviour of the IPC Engine can be configured with parameters for thresholds. These threshold parameters define which values of a sensor for a certain infrastructure object are valid. Also they define which behaviour of messages in flows or processes is correct in terms of step sequence and timing. Expected events can be registered as well to control if they occur in the message flow as expected.