Build your IS’s solid foundations
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 Blueway 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.
01Les points d’attention
Successful data take-on projects
Taking on or migrating static data is often a bulk processing job, and the main difficulties encountered can be summarised as follows:
- Mapping, aggregation and formatting of the data to be migrated;
- Managing transcoding and establishing transformation rules;
- Processing potentially very large volumes;
- Dealing with rejected data and quality control matters.
All of these data take-on issues are handled within the Blueway platform’s Data Foundation, the ETL functionalities of which can be used to process huge volumes of data, while incorporating transcoding, data transformation and rejected data rules. Such processing can also be directed using EAI flows, including when data transformation rules prove to be complex. The different phases can be sequenced within workflows and give rise to on-screen controls, validations and modifications implemented within the data presentation module.
02METHODS AND SOLUTIONS
The method for taking on “active” data
On the face of it, migrating “active” data presents the same degree of difficulty as that encountered when taking on static data. .
Beware of changes in data
However, the ongoing changes in this data cause an additional significant problem that should not be downplayed.
Ensure data completeness
Processing cannot be run piecemeal, otherwise you run the risk of no longer being certain your data is complete.
Choose the right time to migrate your data
Data should generally be migrated at a time when the source system is not up and running (evenings, overnight or outside business hours, ideally).
Implementing the Blueway platform for data migration means such constraints cease to be an issue. The platform is in fact able to update data in real time with de-synchronisation between source and target systems if needed. This serves to suspend updates at any point, but without losing so much as a byte of data entered or amended in the source system.
These implementations are run by means of standardised application connectors with the main ERP and CRM packages on the market, integrated within our platform.