Your core systems are twenty years old. Your business can't wait for it to be replaced.

The risk is not the old system: it's replacing it all at once

The core systems of a bank or an insurer hold twenty years of rules, exceptions and data. That is why no one dares touch them, and every new channel gets attached to them with one more patch. A full replacement sounds clean, but it tends to be the project that absorbs the most budget and carries the most risk of cancellation. The way out is different: surround the core with a layer that speaks today's language and renew in stages, keeping the old system running until the new one proves that the numbers match.

Three signs we have already done it

• We kept the operation of an insurer feeding its financial ERP while the ERP was being replaced, with confirmation of every submission.

• We have worked on insurance core systems such as Acsel/X, SIVI, SABE and SIS/SISnet, and on IBM's WebSphere family.

• Critical systems for banking, insurance and regulated companies since 2006.

What we offer

• Your core system as services, without replacing its logic.

  If it runs on traditional platforms such as AS/400, we turn its business functions into services your channels can call; the adjustments each interface requires are defined in the diagnosis. If it lives on Oracle —Siebel, E-Business Suite, Acsel/X, SIS/SISnet or another— we connect through its stored procedures or exchange tables, without touching its logic or its screens.

• A modern layer around the core system.

  Your channels, partners and AI talk to the layer; the layer talks to the core system. When the core system changes, the layer concentrates the adaptations in a single point and reduces the impact on your channels.

• Staged migration.

  We change one function at a time, with controlled coexistence between both systems and an agreed rollback.

• Moving off the legacy bus.

  If your integrations live in WebSphere ESB, IBM Integration Bus, MuleSoft, WSO2 or Pentaho processes that nobody wants to touch, we keep them running while we move them to a layer your team can operate.

• Less key-person risk.

  We reconstruct and document how your system works today —rules, interfaces, exceptions that only live in your experts' heads— before changing it, so that the knowledge stays in your company.

• Data that adds up during the change.

  Reconciliation between the old and the new system while they coexist, so that no figure gets lost along the way.

• With operations running.

  Agreed windows, testing against real data and a plan for each risk.

• The bridge to a platform of your own.

  If what you are renewing is your offering, sales and collections, Retícula already comes built for it and coexists with your core system.

What you receive first

Modernization map: what stays, what changes first, with what risk and what impact on the business. Your technology lead and the person who knows the system from the inside take part; it makes dependencies, operational risks and owners visible, so you can decide which stage to authorize first.

What your Compliance area receives

Operational evidence for your internal reviews and for the documentation your auditor requests: the reconciliation between the old and the new system while they coexist, the record of every operation that crosses the layer, and the acceptance evidence for each stage.