• Products
  • Services
  • About
  • Contacts
РУСENG

IBSO

IBSO is an enterprise-grade platform designed to handle high transaction volumes, thousands of users, and millions of documents and accounts.

IBSO Architecture
IBSO is structured into the following logical layers:
  • Level 1. Application data storage: Oracle Database tables and views used by the application model
  • Level 2. Business logic: Stored procedures running on the Oracle Database server
  • Level 3. Navigator workstation: A universal client responsible for presenting the application model logic to the end user
IBSO provides the bank with:
  • A comprehensive information technology infrastructure covering a wide range of business functions, including corporate banking, retail banking, remote banking services, management accounting and budget planning, internal administrative management, and data storage
  • High performance and scalability through an efficient system architecture that allows additional server hardware to be added as the business grows
The recommended deployment option for IBSO is to run the system through the IBSO_3L application server in IBSO emulation mode. The solution is supplied as a separate application and requires a separate license.

ARCHITECTURAL AND TECHNOLOGICAL ADVANTAGES

The IBSO toolkit enables not only the development of well-structured, reliable, and easily modifiable software solutions, but also the integration of information systems, thereby ensuring comprehensive business integration across the bank.

Scalability

IBSO-based information systems offer virtually unlimited scalability: as the business expands, the bank can add additional servers to the system. This is particularly relevant for banks planning active business growth, as the banking information system can scale regardless of the size of the bank’s branch network or the volume of transactions processed.

Modular Structure

The IBSO system is designed as a set of separate functional blocks (modules), each responsible for automating a specific business area of the bank, such as settlement and cash services, lending, deposit accounting, plastic card operations, regulatory reporting, and others.

This modular architecture allows the bank to select and configure the functionality required to meet its current business needs.

Extensive Functionality of IBSO-Based Systems

IBSO-based software solutions provide extensive functional coverage within their respective business areas, as well as flexible capabilities for creating and configuring new financial products.
IBSO-based systems are built around the concept of continuous development and flexible enhancement of functionality through financial business applications.

CORE DESIGN PRINCIPLES

Integration with External Components

The core IBSO module includes a versatile data import and export gateway supporting various formats, enabling integration with external applications, processing systems, and information systems.

Centralised Data Model

The IBSO data storage system is based on a single database, ensuring seamless data integration across IBSO-based software solutions. A centralised data store provides access to all accumulated information when performing any transaction in the system.

SECURITY SYSTEM ORGANISATION

Ensuring Logical Data Integrity

Data integrity is ensured by DBMS mechanisms. Data in the system can only be modified through registered transactions; direct user access to DBMS tables is prohibited. This ensures the consistency and integrity of banking information.

User Operation Mode Control

User operation modes, as well as password creation and change rules, are managed by a system utility included in the Oracle DBMS.

Defining User Information Access Rights

The access control system in IBSO-based solutions extends the Oracle DBMS access control system and is based on the following principles:
  1. Flexible and granular access control. The system provides the required level of flexibility and granularity in controlling user access to information resources. Each element of the banking business — such as a transaction, report, or data view — has a unique identifier and can be assigned to an individual user. If a group of users requires the same access rights, they can be assigned to a single functional group.
  2. Server-side access control. The server-side access control system prevents users from accessing IBSO information resources by bypassing the IBSO access control mechanisms through Oracle DBMS tools other than the IBSO client workstation.

System Data Change Logs

User actions in the system are audited through the following types of logs:
  1. Transaction execution log. Any data modification operation can be recorded in the log if the banking model administrator has configured the corresponding transaction for logging.
  2. User access rights log. Records the allocation of user access rights.
  3. Data change log. Any data field in the banking system can be configured for logging. In this case, the complete history of changes to the field values is recorded and maintained.
  4. Object status change history. Primarily used 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 logging level.
  • IB SYSTEM OBJECT
  • IBSO
  • IBSO_3L