Recognising this constraint and that this software is used throughout the bank and hence is a legitimate purchase, it is possible to charge the cost of this software to multiple cost centres such that it is distributed evenly, thus enabling this transaction to be completed without much administrative hassle. All this is done through establishing a set of rules in the rules engine and having the engine deploy the relevant actions.

Such a purchase also has to take the various approving authorities into consideration. As this is a software requisition, the IT sourcing team needs to approve the purchase to ensure the compatibility of the software with other bank-wide standards. The corporate security team also needs to approve it as they are in charge of ensuring all software installations in the company is certified safe and free from tampering. Should there be a need to make changes to the approving officers or to add new approving authorities, all that has to be done is to amend the existing rule or include a new rule in the rules engine.

The ILOG rules engine simplifies this process in a dual-prong approach to increase overall efficiency and turnaround time for development. First of all, compared with traditional development practices, the development and implementation of the system is reduced by at least 50% with just eight simple steps. Please see diagram “8 Steps To Deploy Business Rule Management System” for illustration. Secondly, future change requests can be directly updated by the authorised business unit administrator instead of having to activate the Information Systems department. BRMS is thus an ideal solution for the bank to manage frequent business rule changes.

8 Steps To Deploy Business Rule Management System