Case study · IT Consulting

Automating SARCADAPTER with SSIS to feed ITSARC WEB

Eximus helped IT Consulting integrate an SSIS ETL with ITSARC WEB, resolving a manual dependency in under three weeks.

Outcome and scope

The upstream process was automated and integrated with ITSARC WEB in under three weeks; the historical source reports runs of about five minutes.

Client
IT Consulting
Country
Colombia
Sector
Banking and finance · credit-risk data integration
Service
Business Software Development

Project technologies and environment

  • SQL Server Integration Services (SSIS)
  • SQL Server 2008 R2 → 2019
  • Visual Studio 2005
  • Microsoft .NET Framework 3.5
  • Visual Studio 2019 Community
  • Integration Services Data Tools
  • SSISDB
  • GeneXus 16
  • IIS

The case at a glance

01 · Challenge

A manual desktop process still prepared the flat files needed by ITSARC WEB and was outside the initial scope.

02 · Intervention

We analyzed SARCADAPTER, built an SSIS package to automate processing and integrated the flow with ITSARC WEB.

03 · Outcome

The upstream process was automated and integrated with ITSARC WEB in under three weeks; the historical source reports runs of about five minutes.

During an ITSARC WEB implementation for a financial institution, IT Consulting and Eximus found an upstream step that still required users to run SARCADAPTER manually. They agreed to address it as additional scope and moved the process into a SQL Server Integration Services (SSIS) ETL integrated with the platform. The work was completed in under three weeks.

Client and context

ITSARC is IT Consulting's credit risk management system. In the implementation described by Eximus's historical case, SARCADAPTER processed a financial institution's flat files and prepared the files ITSARC WEB needed. This is a related delivery within the ITSARC modernization, not a separate client or program.

Challenge: modernizing the platform without retaining a manual dependency

Moving to ITSARC WEB did not by itself remove the need to prepare incoming data. SARCADAPTER remained a desktop application that users had to run to process flat files from a financial institution and generate inputs required by ITSARC.

The problem was not simply outdated software. The new web workflow still depended on an earlier manual operation, and automating that operation was outside the initial migration scope. IT Consulting and Eximus identified the gap and agreed on an additional, well-defined integration assignment.

Technical solution

Eximus analyzed SARCADAPTER, originally built in Visual Studio 2005 on .NET Framework 3.5. Rather than rebuild the desktop interface, the team focused on the operation the application performed: transforming flat files into inputs for ITSARC WEB.

The integration followed a clear flow:

  1. Input: flat files received from a financial institution.
  2. Transformation: an ETL package built with SQL Server Integration Services (SSIS) replaced the manual desktop processing step.
  3. Integration: the automated processing was connected to the ITSARC WEB data flow.
  4. Downstream use: the processed inputs could feed the credit risk management platform.

This was a targeted modernization of an operational dependency within the broader ITSARC program. The technical description distinguishes the historical delivery from the subsequently documented operating environment. Client-specific field-level transformation rules, accounts and configuration remain private.

Verified results

Under three weeks: documented time to deliver the additional integration scope and connect it to ITSARC WEB.

Approximately five minutes: automated execution time reported in Eximus's historical case study.

Manual step replaced: flat-file preparation moved from running SARCADAPTER by hand to an SSIS-based ETL connected with the web solution.

The historical source gives inconsistent timings for the old process. We therefore do not publish a percentage improvement or claim unsupported cost savings, error rates or record volumes.

Technical value and lessons

A platform modernization can leave important upstream processes untouched. By examining the complete input flow, Eximus and IT Consulting identified the desktop application's useful responsibility and implemented it with a data integration tool instead of rebuilding its user interface.

The engagement demonstrates Eximus's experience with legacy software modernization and SQL Server data integration, while remaining distinct from the larger ITSARC migration. It does not imply that all ITSARC logic was migrated to SSIS.

Project technologies and environment

The source was a Windows application developed with Visual Studio 2005 and .NET Framework 3.5. The migration replaced its flat-file processing with a SQL Server Integration Services (SSIS) package; the historical table records SQL Server 2008 R2 as the source and SQL Server 2019 as the destination. The documented operating environment uses Visual Studio 2019 Community with Integration Services Data Tools and deploys packages to SSISDB. ITSARC WEB, developed with GeneXus 16 and hosted in IIS in that environment, invokes the ETL under its application-pool identity. These references describe the documented scope and environment without identifying bank servers, accounts or data.

Related service: business software development. The ITSARC modernization is the parent engagement, covered in its own case.

Lessons learned

A platform migration can leave upstream operational dependencies outside the initial scope. Reviewing the complete input flow revealed the manual step and made it possible to address it as a distinct delivery connected to the main implementation.

Next step

If your platform depends on manual data preparation, we can review that flow and define an appropriate integration. Discuss your context.

Continue exploring

More decisions in similar contexts