What is included

The technical part is almost always solvable. The main work is agreeing which system is the master for each reference book.

Discuss the scope

Survey

Which systems, which data overlaps, where things are re entered by hand today.

Exchange model

What is transferred and in which direction, how often, who is the master for each entity.

Matching reference books

Alignment of items, counterparties and units of measurement between the systems.

Implementation

Exchange through existing interfaces or through our own layer where none exist.

Error handling

What happens when a system is unavailable or the data is not accepted. Retry, queue, notification.

Monitoring

Control over the execution of exchanges with a notification to a live person on failure.

How the work runs

A simple exchange takes two to three weeks. A complex one, with several systems and reference books, starts at a month and a half.

01

Data audit

We look at the reference books of both systems. Duplicates and discrepancies usually turn up and have to be cleared before the exchange.

02

Design

The exchange model, the priority rules, the procedure for resolving conflicts.

03

Development

Implementation on a test landscape with real data.

04

Launch

Parallel operation with manual control, then switching the manual transfer off.

A silent exchange error is worse than no exchange at all. If an exchange fails and nobody finds out, the systems drift apart for a month and it is discovered at reconciliation. A failure notification to a live person is a mandatory part, not an option.

Frequently asked questions

Put them in order before the exchange. That is work for whoever keeps the records, not for a programmer. Trying to integrate systems full of duplicates and discrepancies simply multiplies the mess across both of them.

Rarely. For most tasks an exchange once an hour or several times a day is enough, and it is far simpler and more reliable. Real time is needed where a decision is made immediately, for instance checking stock while an order is being placed.

There are workarounds: file exchange, working with the database directly, emulating user actions. All of them are worse than a proper interface and need care during system updates, but they usually solve the task.

We will connect your systems

Tell us between which programs data is moved by hand. We will estimate the exchange and say what needs putting in order before the start.