We have been using TIBCO Business Events in our organization for ensuring adherence to compliance and detect any frauds. There are large volumes of data and TIBCO Business Events helped in applying appropriate rules that trigger events when any anomaly is detected. This helps to meet the compliance standards that have been set and mitigate risks if any.
Pros
Trigger alerts
Automate response
Faster decision making
Works on large volumes of data
Cons
Can be difficult to learn at the beginning
Can be more user friendly
Expertise is needed to deploy and maintain
Likelihood to Recommend
TIBCO Business Events is ideal for mid to large size organization where there are large amounts of data. It can help in automating the responses based on any circumstances as it supports writing rules what trigger actions when any specific event occurs. It is great for processing complex events and can also help in real time monitoring of data for taking actions. It is not suitable for small to mid-size organizations due to complex learning curve and cost associated with the purchase and licensing.
VU
Verified User
Employee in Information Technology (5001-10,000 employees)
Our company has a long history of using the TIBCO family product, previously we majorly used the TIBCO BusinessWorks to build the data flowing and adaptation back-end process, together with the TIBCO EMS. In recent years, together with the TIBCO ActiveSpace, TIBCO BusinessEvents has been introduced into the IT department, aiming to further strengthen our efforts to leverage the "event-driven" architecture to better support our increasing real-time business decision making demand due to business expansion. TIBCO BusinessEvents has become the core technology stack of our company's Enterprise Foundation Service
Pros
It allows us to build rule-based model-driven application, to collect, filter, analyze, correlate various business events in our real-time event flow
It makes various business applications/components easy to integrate (loosely decoupled but chained via the events flow) together
Its distributed rule engine and embedded in-memory data grid (ActiveSpace) gives us a lot of flexibility and room to play with a large amount of rules and data with high performance
Cons
Due to some technical limitation of the embedded ActiveSpace, when the application is deployed in the multiple data-centers with distance, the data/event sharing across the data centers become very challenging
More machine learning and deep learning features could be added to help business further use the real-time event flow more efficiently, to support the pattern recognition and condition self-learning mechanism
More focus could be added to better integrate with public major cloud services
Likelihood to Recommend
BusinessEvents is not very well suited for Cloud native solutions, but it is suitable for traditional enterprise self-maintained data center deployment. And it gives the business the power to define/modify/update the business rules, in a visualized way, instead of asking IT team to maintain them. Generally speaking it is a very comprehensive rule engine solution, but not suitable for "hook on" some other complex computation/data processing logic
VU
Verified User
Strategist in Information Technology (10,001+ employees)
It is used across the whole organization addressing problems spanning from R&D to financial analysis.
Pros
Dashboard for real-time analysis
R-scripting, although the R editor could be improved, there are syntax inconsistencies between R-studio and R-opensource in TSSS
Basic statistics and drill down capabilities
Cons
Better integration with R versions and better debug for R-scripts in Spotfire. There are inconsistencies in syntactic expressions accepted by R-studio and not accepted in Spotfire. Accelerating the debug would be awesome. Having a command like View (data frame) that directly output in the dashboard would be a great accelerator.
Likelihood to Recommend
<p>Standard dashboard for basic statistics. GREAT</p><p>Advanced multivariate modeling needs to be coded in R for example, LESS GREAT. You would get a million users for off-the-shelf multivariate modeling like SIMCA.</p><p>The integration with Statistica is a great idea but much of its success will depend on the speed and the ergonomics by which you integrate the development workflow for multivariate models PLS/PLS-DA/ PCA etc.</p><p>You should implement some of the features offered by SIMCA (Sartorius Stedim) and expand the multivariate analysis offering and more advanced tools (from Random Forest to T-SNE and machine learning / AI). You will get lots of 'love' from pharmaceutical engineers. :)</p>
TIBCO BusinessEvents (BE) is used in multiple business applications as well as gateway implementations at Western Union. It is used to receive, transform and handle events/transactions in real-time. Business users are provided with the capability of making and changing rules dynamically using BE based applications. Since every transaction in the company deals directly with funds every application plays a critical role.
Pros
Business users have the capability of changing rules dynamically without downtime in the application.
Real-time processing capability decreases latency and increases the efficiency of the features developed in TIBCO BE.
Capability of caching the data as well as managing it as an independent entity as TIBCO Active Spaces is a huge addition.
Cons
TIBCO BusinessEvents Studio for altering the decision tables/rules can be made more robust and production ready.
TIBCO BusinessEvents views can be made more robust. This will avoid additional BI layers on top of the data.
Event Stream Processing and Pattern Matching add-on of TIBCO BE is an awesome feature. It can be made more robust by implementing machine learning and deep learning.
We Use Business Events Rule Engine in regards with Fraud Detection use cases. Various rules built and deployed to identify fraud across different channels. We use Web Studio to author most of the rules that are executed by BE Engine. ActiveSpaces used as a caching mechanism between BE and Backing Store.
Pros
Optimized Rules engine
Extremely efficient decision tables
Web based rules authoring tools
Cons
Not so easy hot deployment
Web Based tool lacks some features needed in Rules Authoring
Does not work well with public cloud vendors, e.g. not easy way to run BE and AS with ECS on Amazon Web Services
Likelihood to Recommend
Business Events is well suited for medium to complex use cases involving complex event processing. BE is useful in areas where Buisness Owners want to actually implement business rules defined by designers/developers. BE is well suited where Busieness Rules/ Thresholds change frequently; BE's hot deployment capabilities can be utilized for such scenarios. BE is very well suited for on premise deployments.
BE is not very well suited for Cloud native solutions. Specifically when it uses embedded ActiveSpaces as in memory cache.
VU
Verified User
Professional in Information Technology (10,001+ employees)
<p>BusinessEvents is used in my organisation to deliver a capability of rules-driven processing on the events that are flowing through the middleware layer. The requirements expect TIBCO BusinessEvents to process states of various electrical devices, perform actions based on the changes of a state exceeding a defined threshold of level, time, or value increment or just of a count as the event. The following business problems are being addressed by using BusinessEvents: event monitoring, event correlation, event recording and event filtering where an event may be observed as a change of state with any physical or logical or otherwise discriminated condition. Preserving the state of an object is achieved through State Machine.</p><p></p>
Pros
Process network events and use defined rules to infer system occurrences
Monitor distribution substation switches that have remote telemetry to infer the actual switch state
Perform rule based Network Alarm suppression
Cons
Ability to handle/process huge real time data
Faster processing of data with high rate of performance.
User-friendly setup and quick event formulation capabilities
Likelihood to Recommend
Well suited in scenarios where the business landscape has several probabilities of data that needs to be processed by ruke driven approach.
No suited for very huge volumens of data processing.
VU
Verified User
Consultant in Information Technology (5001-10,000 employees)
In the actual project, TIBCO BusinessEvents is being used as correlation engines. Its purpose is to collect metadata about service requests and responses across the Service Backbone, correlate them, and provide statistical information about deployed services, such as the number of hits for each service operation, successes and faults, average latency, and so on. All these information are then delivered to another component to be persisted and then read from a GUI. Thanks to this statistical information about the deployed services, the user would be able to figure out the health of the system, create business monitoring rules, and act immediately whenever unexpected patterns appear.
Pros
One of the simplest use of TIBCO BusinessEvents, is for "Condition Detection" scope. Let's assume we like to monitor business services or our corporation, and create monitoring alerts whenever certain conditions are reached. For example, a monitoring rule could be: "when a service call receives more than 80% of fault responses within a minute, generate an alert (send an email)".
In this scenario, TIBCO BusinessEvents offers a very powerful rule engine. In the rule engine will be defined all the monitoring rules, and their threshold. The rule engine will receive events with statistics information about service calls, eventually correlates and aggregates those message, and when particular condition are detected by the defined rules, an alert is generated
One interesting capability of TIBCO BusinessEvents, is to recognize situation. One example over all, could help to understand the "Situation Recognition" scenario: the Bank Fraud detection.
Let's assume a bank would like to define a solution to identify when a credit card fraud is in act. Now, a simple use of the credit card by its owner, most probably, is not a fraud. So the system should avoid to raise alert every time. But the system should be able to recognize certain suspicious conditions, as for example when the credit card has been used for purchase in a shop in Italy, and after a pair of hours in one store in USA.
This means that one single event (usage in Italy) is not enough to define the fraud, but the system is able to keep the event, and process it once others events arrive, in order to recognize suspicious situation.
One particular pattern, where TIBCO BusinessEvents would be very helpful, is for Track and Trace patterns.
Let's consider an aviation company, that needs a process to follow customer's baggage. The customer drops off his baggage at airport, a bar code is assigned to it, that belongs to the owner. The baggage should follow a route to reach the target airplane, be loaded on the airplane, once arrived at destination unloaded and sent to the correct belt to be collected by its owner.
All the steps above, con be modeled with a state machine, where the baggage change its state at each passage under a bar code reader for example.
This solution would allow companies to track baggage from the beginning (when customer drops the baggage at counter) to the end (customer collects his baggage at destination), and establish any problem during the path.
Cons
TIBCO BusinessEvents offers really several features, many way to customize and adapt it to own requirements. One interesting feature is the opportunity to create Rules, at runtime, by an user that is not developer, using rule templates.
This feature, well implemented and with few interesting addon, has an architecture not very simple.
For example, we have a Business Monitoring component, where the business user can define his monitoring rules, the rules are persisted on DB, and picked up at any time by another component.
The component that reads the rules from the DB is not a rule engine, this means that is not performing very well for this scope, and also it needs each time to retrieve the rule to execute from the Database.
Our intention is to substitute this last component with TIBCO BusinessEvents, in order to use the power of the rule engine. But, to create the rules, there is a new mechanism, that should be integrated with the existing GUI, and more else, the rules are persisted on file system.
There is no way for the developer to auto create the rules internally, and enable them in the working memory, for example generate the rules from entries on a database, and create the rules directly in the working memory.
The existing solution injects the new rules in the working memory from outside.
Likelihood to Recommend
TIBCO BusinessEvents is part of the CEP (Complex Event Processing) family, this means that it fits perfectly in all those scenarios where a correlation between incoming events is required. Where a stateful process is necessary. It does not fit well for a kind of Process Orchestrator scope, where simple events are coming in, and there is a well-defined behavior the system, would have on incoming request, and no particular reason to use a rule engine and its complexity. Anyway, there are particular cases where BusinessEvents would be a good actor in orchestrating a portion of CEP solutions activities
Currently, Fraud department in my company uses Business Events, to run rules to detect fraud based on certain data points and internal calculations. We heavily use BRMS functionality to dynamically create and deploy rules on ad-hoc bases.
Pros
BE does inferencing part very well
Correlate a lot of data streams and make decisions on very minute scales.
Cons
BRMS functionality with hot deployment should be improved a lot
As everyone is moving towards cloud, BE should easy have docker support and should be able to move dockers easily to cloud env.
Likelihood to Recommend
Business Events is well suited for the scenario where you want to use the product just as a rule engine instead of making a lot of other heavy calculations inside business events engine.
VU
Verified User
Professional in Information Technology (10,001+ employees)
It replaces the current legacy fraud operational system. We incorporated a number of producers of real-time events (e.g. web UI claims process and RSA Web Threat Detection). TIBCO BusinessEvents (BE) is the consumer that runs a set of rules against those events to determine the next steps in the claims process.
Pros
Great event driven engine with a rich event model
Provides ability to use Web Studio to generate basic rules that will drive the outcomes
Allows for Java implementations of other rule sets
Has in-memory caching abilities
Cons
We had to write our own business rules interface that matched how our previous systems operated. Web Studio has gone through some great changes but in that time we have made a decision to move to Kafka, Kinesis, and Spark for our events streaming solution in AWS.
We did not modify our business process flow to take advantage of BE. If you are not truly running an adaptive business process effort, then BE could be overkill.
Likelihood to Recommend
If you are truly event driven and are willing to implement an adaptive business process then BE is great. The challenge is involving the business and ensuring they are in charge of the product release. In our organization, when the business drove the product releases (which included BE applications) then BE was a winner. When developers took over and had no real event-driven background then all the calls were synchronous which is a killer to the event-driven process.
