IBSO
IBSO is an industrial platform capable of handling high transaction loads, thousands of users and millions of documents and accounts.
IBSO is divided into the following logical levels:
- Level 1. Application data storage for the application model: Oracle server tables and views
- Level 2. Business logic: stored Oracle server procedures
- Level 3. Navigator user work station: a universal client implementing the logic of application model presentation to the end user.
IBSO provides the bank with:
- Creating information technology infrastructure that would be complete in terms of functionalities to the maximum extent possible (corporate services, retail services, remote services, management accounting and budget planning, internal administrative management, data storage)
- – High performance volumes thanks to an efficient and scalable system architecture which allows connecting additional server hardware as the business expands.
The recommended deployment option for IBSO is to run it via the IBSO_3L application server in IBSO emulation mode. The solution is supplied as a separate application and requires separate licensing.
ARCHITECTURAL AND TECHNOLOGICAL ADVANTAGES
Apart from the development of well-structured, operationally reliable and easily modifiable software solutions, the IBSO toolkit enables linking information systems together and in doing so ensures full business integration for the bank.
Scalability
IBSO-based information systems have virtually unlimited scalability: as the business expands, the bank can connect additional servers to the system. This is particularly relevant for banks planning active business growth, as there are no limitations on the capabilities of the banking information system, regardless of the size of the bank’s branch network or the volume of transactions processed.
Modular structure
IBSO-based information systems have virtually unlimited scalability: as the business expands, the bank can connect additional servers to the system. This is particularly relevant for banks planning active business growth, as there are no limitations on the capabilities of the banking information system, regardless of the size of the bank’s branch network or the volume of transactions processed.
At the same time, IBSO ensures centralised storage of core data and conflict-free operation of integrated information systems. Various IBSO-based solutions are available to support banks of any size and type of business.
Extensive functionality of IBSO-based systems
IBSO-based software solutions provide extensive functional coverage in their specific domain and flexible capabilities for creating and configuring new financial products.
IBSO-based systems build on the concept of continuous development and flexible enhancement of functionalities through financial business applications.
CORE DESIGN PRINCIPLES
Integration with external components
The core IBSO module includes a multi-purpose data export / import gateway in various formats which enables integration with various external applications, processing and information systems.
Centralised data model
The IBSO information storage system is based on a single database ensuring full integration at the data storage level in IBSO-based software solutions. The single storage makes it possible to access all accumulated information at the time of performance of any transactions in the system.
SECURITY SYSTEM ORGANISATION
Ensuring logical data integrity
Data integrity is secured by DBMS mechanisms. Data in the system can only be modified via registered transactions; users are prohibited from accessing DBMS tables directly. This ensures consistency of banking information.
User operation mode control
User operation modes and password creation and change rules are determined by a system utility that is part of the Oracle DBMS.
Defining user’s information access rights
The access control system in IBSO-based solutions is an extension of the Oracle DBMS access control system. It builds on the following principles:
- Ensuring the necessary level of flexibility and granularity in controlling user access to the system’s information resources. For this purpose, every element of banking business (transaction, report, data view table, etc.) has its own identifier and can be assigned to a user individually. If a group of users requires identical rights, they are added to a single functional group.
- Implementation of the server-side access system prevents users from accessing IBSO information resources by evading the access control system through the use of Oracle DBMS software other than the IBSO client workstation.
System data change logs
User actions in the system are audited through the following logs:
- Transactions execution log. Any data modification action can be recorded in the log if the banking model administrator has defined that it requires logging.
- User rights allocation.
- Changes to details. Any detail in the banking system can be defined as logged. In this case, the entire history of changes to that detail’s values is recorded and maintained.
- History of object status changes, primarily for payment documents. The logs are automatically populated by the corresponding system functions. Users whose actions are logged cannot delete log entries. All logs have a logging flag (or level).