Skip to main content
TomorrowX

AI

New products on heritage systems

Launch new features, products and regulatory change by composition at the Data Mediation point, without waiting for core system releases.

Why this challenge is hard

New products, features and regulatory changes usually wait for the release cycle of the core systems underneath. For heritage platforms that can mean a year or more of change, testing and cost, and some changes are never attempted because the effort is prohibitive.

Risk, security and compliance requirements must still be met before anything new can launch.

What Data Mediation changes

A Data Mediation point sits in the path of the data the product depends on. New behaviour is composed there: data is enriched, transformed, validated or routed as it passes, so a new feature can go live while the core systems stay as they are. The same point applies the risk, security and compliance controls the new product needs.

Programmable Data Agents let the organisation launch its own features by composition, without waiting for a vendor release. In earlier deployments, a global bank delivered regulatory change in weeks on a multi-region corporate banking site, where the nearest alternative was more than twelve months of manual coding. A global payments company launched a new product in weeks, with its risk, security and compliance gaps closed at the Data Mediation point.

Approach

How Data Mediation is applied

  1. 01

    Choose a feature, product or regulatory change held back by the core release cycle.

  2. 02

    Place a Programmable Data Agent in the path of the data it depends on.

  3. 03

    Compose the new behaviour and its controls: enrichment, transformation, validation and routing.

  4. 04

    Go live in Listen Only, then Active, while the core system stays unchanged.

What can be demonstrated

  • A new feature live in front of an unchanged core system
  • Risk, security and compliance controls applied in the same path
  • Change delivered in weeks rather than core release cycles
  • A record of every request the new behaviour touched

The exact scope, controls and evidence depend on the customer environment and are agreed before implementation.

Start with one change the core release cycle is holding back.

Discuss this work