Changes to applications, version upgrades, applying extra add-ons, or integrating a new subsidiary running disparate applications requiring replacement – all these often generate highly unrewarding work in terms of data migration or take-on.
Handling static data (items, customers, suppliers, bills of materials, etc.) requires a different approach if it is not to clash with the management of active data (customer orders, production orders and monitoring, etc.) to deal with the specific features each entails.
The Phoenix integrated platform makes all these data manipulations easier for you, thanks to its ETL and EAI functionalities, and also makes it possible for you to deal with any data governance issues with its MDM (Master Data Management) toolset that handles data quality and completeness. Complex data take-on operations, requiring a number of intermediate steps between starting and finishing, can be made easier using the Blueway application bus that guarantees both the routing and persistence of data.
Here are a few examples of contexts in which data recovery is a key issue
As a reminder, data recovery is an essential operation for transferring data from an old system to a new one, while preserving its value, integrity and quality. It requires a series of steps including data cleansing, field mapping, parameterisation, validation and acceptance, to ensure successful and functional integration into the new system.
Here are a few examples of projects in which data recovery plays an important role:
- Mergers and acquisitions, of course. In these cases, it is essential to ensure that the data of two separate entities is integrated efficiently and securely, in order to maintain continuity of operations and maximise the value of the merged company.
- Disaster recovery. After a disaster or major disruption, data recovery is essential to restore information systems and get back to business. This often involves recovering data from backups, and reintegrating it to resume normal operations.
- Integration of several ERP (Enterprise Resource Planning) systems. This may or may not be linked to the merger of two companies: optimised data recovery must ensure that crucial information such as inventories and financial data are correctly merged. The challenges of mapping and ensuring the consistency of the information must of course be anticipated!
- Changes in the regulatory context and/or data governance policy. Data migration and recovery will accompany the implementation of the new governance framework.
How process (BPM) and data (ESB) integration can create value for IT and business departments ?
Successful data take-on projects
The recovery of static data is often a mass processing operation, the main difficulties of which can be summarised as follows:
- Mapping, aggregation and formatting of data to be transferred.
- Transcoding management and implementation of transformation rules.
- Handling of potentially large volumes of data.
- Rejection management and data quality control.
These existing data recovery issues are fully taken into account in the Phoenix platform’s Data Foundation, whose ETL functionalities can handle large volumes of data, as well as all aspects of transcoding, transformation and reject management. This processing can also be carried out using EAI flows, particularly when the transformation rules are complex. The various phases and processes can be chained together in workflows, giving rise to checks, validations and modifications within screens implemented in the Data Presentation module.
How do you transfer data between two companies?
The transfer of “live” data presents, a priori, the same level of difficulties as those encountered when transferring static data, and must follow structured steps. Here are a few tips:
Beware of data evolution
However, the constant evolution of this data brings with it a significant additional problem that should not be underestimated.
ESB vs ETL ? The distinction between is no longer relevant relative to today’s business requirements.
Guarantee the completeness of your data
Processing cannot be carried out on a piecemeal basis, otherwise it will no longer be possible to guarantee the completeness of the data.
Choose the right time to recover your data
Recovery generally has to take place during periods when the source system is shut down (in the evening, at night or, ideally, outside business hours).
Recovery generally has to take place during periods when the source system is shut down (in the evening, at night or, ideally, outside business hours).
Davy Hassenboehler, Pre-Sales Manager at Blueway
Implementing Blueway’s Phoenix data platform for your data recovery operations eliminates these constraints. The platform is capable of updating data in real time, with desynchronisation between sources and targets if necessary. This means that updates can be suspended at any time without losing any information entered or modified in the source system.
These implementations are facilitated by the standardised application connectors with the main ERP and CRM software packages on the market that we have integrated into our platform.
Want to discuss interoperability challenges with an expert?
