By using ACTICO Rules as a Central Rule Engine, companies bring operational efficiency to a new level. They centralize and standardize business rules to consistently provide them as shared services across their organization. The approach allows maximum flexibility in case of changes.
Central repository for rule maintenance and deployment
Integration as consistent, reusable web services
Highly efficient, automated rule execution
Central Rule Engines combine the service-oriented architecture (SOA) concept and the business rules approach. The combination allows companies to increase efficiency, flexibility and agility.
Easy maintenance of business rules in the central repository
Flexible and secure changes through business users
Provisioning of reusable shared services
Time-critical, high performance applications (e.g. trading systems) usually do not access webservice/microservice functionality. Instead of using services, these applications can directly integrate executable business rule code accessed from the same central repository that supplies the services. The whole time, ACTICO Rules ensures continuous consistency of the centrally provided business logic that is integrated into the applications.
Business experts and IT collaboratively use ACTICO's business rules management system ACTICO Rules as a common platform to create, implement, test and improve operational decisions.
ACTICO offers a unique graphical approach for modeling decisions, rules and workflows. Business experts transfer their new insights or changes rapidly into graphical models – without the need for special IT skills.
All models of your decision logic are maintained centrally in the repository, and documented and deployed uniformly. By avoiding redundancies, the central rule engine ensures consistent decisions and reduces errors.
From the central repository, your decision logic is deployed as a reusable Central Decision Service – in the form of a classic webservice or as a lightweight microservice.
Time-critical applications with high performance requirements (e.g. trading systems) can use the decision logic from the central repository in the form of directly integrated Java code.
With features like version management, change logging, decision-making records or user and authorization concepts our Central Rule Engine helps you meet your governance requirements.
"Any system that contains a number of rules should be using a rule engine."
By managing decision logic in a central place and distributing it from there, companies ensure consistency across all processes, channels, and applications.
By decoupling business logic from applications, optimizing business-IT alignment, and using a central approach, companies accelerate time to market new or updated decision models significantly.
By reducing time required for development, testing and coordination, and by avoiding system discontinuities, you can realize significant cost savings: up to 50% in the development phase, and up to 70% in the maintenance phase.
Decision models are maintained where they are "at home": in the business department. This way, companies empower their business experts and relieve their IT departments.
The central approach helps you minimize redundancies while test support within the BRMS helps track down and avoid technical errors.
Business logic deployed as a webservice or microservice can be reused and jointly used by various processes and client applications. This enables the simplification of a company's IT application landscape.