Enterprise Identity Provider

Solution: Staff Augmentation

The Challenge:
Centralized Enterprise Identity Provider.

  • Client recommendations in regards of the benefits of an Identity Provider (Idp).
  • Diagnostic and evaluation across vendors (AWS Cognito, KeyCloak, IdentityServer, Auth0, Okta).
  • Services modernization to achieve better scalability.
  • Complete adoption of AWS Cognito as the main data identity provider.

The engagement:
Manageability and Usability.

  • NovaComp provided a developer with experience .NET Core, Angular and AWS Services.
  • Full assessment performed to understand the current identity provider setup.
  • Cost optimization due to growing number of users.
  • Full platform integration provided to current applications.

The benefit:
Access and optimal use of implemented identity provider on the public cloud.

  • The client went from a distributed (one account per application) authentication to a centralized model (one account per user).
  • Allows future implementation of single sign-on.
  • Major security improvements on authentication services.
  • Support and guidance for all AWS Cognito setup.
  • The client improved user experience, merging multiple accounts into a single one.
  • Server and services performance improvements.

The result:
Time to detect and respond to security incidents: the organization was able to identify them  in one hour.

Adjustment of Accounting Balances to Zero in the Reception of Damage Insurance Premium Payment Transactions

Solution: AS400 Cobol

For the past 15 years, we have partnered with a leading Insurance Company, deploying a dedicated team of over 90 professionals to manage their accounting processes. Historically, the company faced challenges in financial reconciliation due to residual balances remaining in their accounting system. To address this, they utilized a tool named “Nativa en Cero” for necessary accounting adjustments. However, this tool, developed years ago, was limited by its single-user functionality and time-consuming operation, leading to significant delays in closing monthly financial statements.


  • How to make the application multi-user, as it originally functioned with a virtual screen device simulating manual user execution.
  • How to reduce the processing time of the adjustment process significantly.


  1. The entire logic, initially written in native Cobol, was analyzed, and the routines were gradually migrated to SQL DB2 Stored Procedures.
  2. Although there was a substantial reduction in execution time, further optimization was achieved using SQL Execution Planning and SQL Performance Monitor tools to enhance code efficiency and table access, considering tables with millions of rows.
  3. Instead of using the virtual screen, the QTEMP library was employed. This library assigns each user or job a specific area in each server session, enabling multiple users from each branch to reconcile their policies swiftly and thus expedite the overall accounting process.

Execution of Received Premiums for Accounting in Accordance with International Financial Reporting Standards (IFRS)

Solution: SQL migration


Each branch of the Insurance Company is required to compile information on issued, paid, and canceled premiums from the beginning of the year. This information needs to be transcribed into a format that will be used when implementing the IFRS (International Financial Reporting Standards) project, which will be a global financial standard.

The target date for the implementation of this accounting standard is set for January 1, 2025. However, to prepare for this and avoid migrating a massive amount of information all at once, the request was made to develop a process that loads monthly premium accounting information into a repository. This repository allows BI (Business Intelligence) processes to extract and load the data into an Oracle database, which is prepared for the eventual implementation of the IFRS.


  • Reduce the execution time of the Company-developed Cobol program, which was approximately 18 hours. The process follows a monthly loading pattern: in January, only January premiums are loaded; in February, January and February premiums are loaded, and so on until December. The January process alone took 3 hours.
  • Reprogram all Cobol logic into Stored Procedures.
  • Despite a significant reduction in execution time, the process was still unsatisfactory in terms of time efficiency.


The entire logic, initially written in native Cobol, was analyzed, and the routines were gradually migrated to SQL DB2 Stored Procedures.​

Further optimization of the code was achieved using DB2 tools for code improvement, including the utilization of the date dimension. Although not native to DB2, the date dimension is widely used in BI to streamline connections between tables with different date formats, avoiding concatenations and data conversions that slow down the code. This optimization resulted in an average execution time of around 10 minutes for the entire process.