The Client of the project was a large international bank that offers services in the field of daily banking, personal accounts and credit cards, savings and loans, as well as in the fields of leasing, investment and insurance. The bank has an extensive network of its own branches and partner outlets throughout Europe and is considered to be one of the most innovative banks in Poland, very advanced in electronic banking.


In connection with the decision to migrate from the silo architecture to the service architecture with the Profile central system, there was a need to transfer support for backoffice processes to the new system. As there were no ready-made solutions in the new system to provide comprehensive support for these processes, it was decided to automate them using WebMethods BPMS – a technology that the client already had in their own infrastructure and that met client’s expectations. As part of the project, a decision was made to automate a number of processes including: handling insurance claims, resignation from insurance, restructuring loans and changing the interest rate on a special purpose loan after fulfilling the purpose.


Since the beginning of the project, analysts from Inteca worked closely with target users, i.e. people dealing with the processes covered by the project on a daily basis. Thanks to this cooperation, the processes have been designed to simplify the work of target users as much as possible and automate as many activities as possible.

Users have been relieved thanks to such functionalities as automatic closing of applications after the deadlines (about which the user is informed by email), or automatic generation of all required documents. They also do not have to search for information in various systems – all information necessary for the operator to make decisions is downloaded from the Bank’s

central system using the SOA service layer and displayed on the screen. SOA services are also used to protect against user errors. Thanks to the implemented business rules and validations (such as e.g. automatic checking of the account status to confirm whether it can be restructured or accepted), the risk of human error has been minimized.

The user interface has also been designed in cooperation with target users, making it legible and intuitive. What’s more, the team leaders gained the ability to assign specific users to process instances and monitor their progress in handling applications, which makes it easier for them to manage resources and verify employees’ decisions.


Traditional IT architecture brings complications not only of an IT nature, related to the fact that data are ocated in different systems and are not integrated; users work with many applications to perform their activities, because they need specific functionalities. This creates the socalled business silos that hinder information exchange and thus process optimization. Due to the implementation of SOA / APIs service architecture, data becomes a shared resource of the organization, and access to the functionality of existing and newly built systems becomes easy and common. This is the basis for building automated business processes that, working on the BPM platform, coordinate data exchange and perform business transactions, and allow real-time monitoring and process analytics. This is the key to building real digital businesses.


As part of the solution, automation of each process was designed and implemented. WebMethods BPMS technology was used, which allows for rapid development of software for process automation and supports many business aspects of such automation. Important functionalities of WebMethods BPMS are easy assignment of business roles to users, monitoring of users’ effectiveness in working with the process and the possibility of quick changes in business rules used in the process. The user interface has been implemented using Responsive Web Design, i.e. a web design technique so that its appearance automatically adapts to the size of the browser window, and thus, to various devices (e.g. computer, telephone, tablet). Due to the client’s using the SOA architecture in the enterprise, the implemented processes communicated with the Bank’s systems using the SOA service layer. As a result, WebMethods BPMS processes can be initiated in other applications, and the processes themselves repeatedly establish communication with the central system and the customer directory. Thanks to this, the user can read and update data in various systems, generate relevant documents and send them to the print queue, without having to directly use many applications.