Application Architecture
The Avaloq Banking System's high level of abstraction allows your bank to optimise its processes within a short period of time. The system's design, architecture and technology provide you with the best possible conditions to achieve your growth targets.
One major advantage of the application architecture is the Avaloq object model, which enables you to model the desired business structures and data records.
All objects in the Avaloq Banking System represent kernel data which is stored persistently in the database. A distinction is made between static data and data of positions and bookings which result from business transactions. Depending on their roles and rights, users of the Avaloq Banking System can access and modify specific kernel data.
Both data types can only be modified by performing a process step which has been previously defined by the bank. Any modifications to data are entered as "orders", and every modification or process step may be audited.
In order to enable users to access the data as quickly as possible, some data is deliberately stored redundantly in what are termed "pillars".
Avaloq Script, the Avaloq Banking System's script language, facilitates entering specific business logic. The structure of the data that can be accessed through Avaloq Script is defined in a DDIC (Data Dictionary), making it unnecessary to know the data storage structure.
The Avaloq Report Writer, which is also based on Avaloq Script, is a tool facilitating the extraction, consolidation, aggregation and display of data, and is therefore ideally suited to the implementation of data retrieval interfaces.
Finally, the open Avaloq Message Interface (AMI) enables communication with other systems using text-based, standardised and structured notifications, thus simplifying the integration of third-party systems into the Avaloq Banking System. The AMI can also be used for internal communication between Avaloq modules and business units.