What is
Glass Box
Approach?

Traditional design approaches commonly referred as Black Box and White Box, can be described as two ends of a spectrum, where business users, either have their hands completely tied or have just too many configurations to manage. In either case, there is significant effort on the business user to manage and adhere to regulatory changes.

The need of the hour is to think out-of-the-box and come up with a design approach which uniquely blends the traditional approaches and provides business users with the right amount of flexibility and aims at significantly reducing the business user effort.

In this unique approach, the data is pushed to the reporting solution as is (similar to White Box approach), but the Argus configuration engine helps business users to map and configure conditions to a pre-defined reporting taxonomy (similar to the Black Box approach), thereby eliminating the need to have the configurations defined and applied at each reporting line.

With the above approach, the business users would have a consolidated view of all the business configurations at a single interface and once the configurations are set up, they only need to generate the reports and proceed with the submission process.

image

Source System

Requirements

  • icon

    Integration of various systems that house bank’s data. E.g., Core Banking, Treasury Systems, Ledger Data, Trade, Loans etc.

  • icon

    Accommodation of external datasets from multiple flat-files. The file formats could be xls, xlsx, csv etc.

Argus Offering

  • icon

    Experience of working with various Source Systems.

  • icon

    Unique blend of techno-functional banking experts with an excellent understanding of regulatory reporting landscape.

What is Black
Box Approach?

In a Black Box approach, the design provides for a pre-defined taxonomy, against which the data needs to be pushed to the reporting solution. The taxonomy is defined as per the business criteria mentioned by regulators across all reporting forms.

The business logic to identify and map data from different data sources, to the solution specific taxonomy, remains outside of scope of the reporting solution.

In a nutshell, the overall solution behaves like an aggregation platform, where the values are rolled-up basis the pre-defined taxonomy and associated with the end reporting outcome.

image

Source System

Requirements

  • icon

    Various systems that house banks data. E.g, Core Banking, Treasury Systems, Ledger Data, Trade, Loans etc.

  • icon

    Can also include external datasets from various flat files. The format can be xls, xlsx, .txt, xml etc.

Black Box Vendor Offering

  • icon

    Experience of integrating with disparate source systems

  • icon

    A blend of techno-functional banking experts with a good understanding of regulatory reporting landscape

What is White
Box Approach?

In a White Box Approach, the design is primarily aimed at providing business users with a platform that empowers them to have any level of reporting generated out of the solution. The data is pushed to the reporting solution, as is from the respective data sources, and the solution then provides for maintaining historical cuts of data, by incorporating logical relationships across various entities.

Once the data is pushed to the solution, the business users have the flexibility to define, their own business definitions/configurations across various reporting lines, in-line with the regulatory requirements, and proceed with reporting submissions.

image

Source System

Requirements

  • icon

    Various systems that house banks data. E.g, Core Banking, Treasury Systems, Ledger Data, Trade, Loans etc.

  • icon

    Can also include external datasets from various flat files. The format can be xls, xlsx, .txt, xml etc.

White Box Vendor Offering

  • icon

    Experience of integrating with disparate source systems.

  • icon

    A blend of techno-functional banking experts with a good understanding of regulatory reporting landscape.

image