Automating SARCADAPTER with SSIS to feed ITSARC WEB

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

SARCADAPTER required manual execution and was outside the initial scope of the ITSARC migration. Leaving that step unresolved would have retained an operational dependency in the flow feeding the new platform.

Our approach

Eximus examined SARCADAPTER —an application built in Visual Studio 2005 on .NET Framework 3.5—and identified its actual job: transform flat files before feeding ITSARC WEB. After agreeing the additional scope with IT Consulting, the team built an SSIS package to automate that processing and connect it to the platform, so data could be supplied through the web environment.

Results

The automated workflow was integrated with ITSARC WEB within the agreed window of under three weeks. The public historical source reports runs of about five minutes. Because that same source gives two different durations for the previous process, we do not calculate a percentage improvement or present a before-and-after timing as a commercial promise.

Tech & services used

SQL Server Integration Services (SSIS), flat-file processing and ITSARC WEB. 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.