Browse Prior Art Database

Event Processing Simulator Disclosure Number: IPCOM000202527D
Publication Date: 2010-Dec-21
Document File: 1 page(s) / 40K

Publishing Venue

The Prior Art Database


An event processing simulator to allow automatic calculation of financial and resource statistics. The simulator takes given inputs for cost and resources and delivers statistics that would result from the processing of events and actions in the system over time. Different results can automatically be obtained by modifying the attributes and repeating the simulation. This provides a way to create an adaptable financial model for an event processing application.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 54% of the total text.

Page 01 of 1

Event Processing Simulator

Disclosed is a simulator which is integral to Event Processing tools. This allows the user to construct the event processing logic and also attribute cost/revenue to incoming events and to outgoing triggered activities and actions, directly into the event process.

    Once the event process is constructed, it can then be simulated with a set amount of workload (a days/weeks/months worth of projected work). While this simulator runs, it is able to produce financial information based directly on the event process the business user has designed.

    Any change in the business process automatically changes the financial model. Once the simulator has finished the workload, the user is presented with a report containing key financial indicators, such as the profitability of the event process, break-even points, return on investment and most profitable of event/action relationship.

    There is no need for a separate financial model to create and maintain as it would be constructed as part of the event logic itself. As the logic changes, so does the financial model.

The process to set-up and run such a simulation can be described as:
1. The user constructs an event process, which includes incoming events and outgoing actions (triggered as a result of a concatenation of the incoming events meeting a set criteria).
2. The user then attributes cost/time/resources required, directly to the events and the outgoing actions, in the tool, as the event logic is constructed. Examples of each type of attribute are:
- Cost of processing an event. For example, handling a car sales enquiry. This may includ...