eQ's deep experience based methodology for application integration, synchronization, and migration can be summarized by "IETLV". We found the traditional model of ETL to be limiting and not comprehensive for what customers actually need. We extended ETL with I for "Identify" in the beginning and V for "Validation" throughout the integration / migration process, thus "IETLV".
 

Unless customers are able to Identify ("I") the classification of data, quality of data, anomalies in the data, and patterns in the data that exists in the source system (s) or legacy system (s), it is nearly impossible for them to define business rules that would transform the source data to fit within the model of the destination system. Many integration, synchronization or migration projects muddle through a string of data issues much later in the project that were not identified up-front or the team did not know such data classifications or anomalies existed; causing expensive delays. eQube-DP (this should be a link to eQube-DP) interrogates the data in the source or legacy system (s) to understand its ‘quality'. It identifies anomalies, similarities, and patterns in the data. Such qualification of data then can be used not only to correct and repair the data, but also as an essential step in establishing transformation rules for application migration and integration.

In addition, we strongly believe, when systems are integrated or synchronized or are being migrated, end-to-end validations of data ("V") are critical. In case of large application migrations, decades of data need to be migrated to the new destination system. To perform validations manually by sampling the data (it can be terabytes of data) has many obvious limitations. Instead or in addition, many organizations resort to writing method code based validation routines with limited success. Reason being, along-with the integration or migration activities the validation routines also need to be developed, evolved, and maintained through the project life cycle. The development and maintenance of the validation routines can be a significant challenge as it becomes a major task requiring resources and time.

eQube-BI (this should be a link to eQube-BI) has unprecedented capabilities to reach out into multiple systems (both source and destination system (s)) to aggregate data in a ‘single view of data'. With its many features, eQube-BI ‘cubes' can be rapidly developed, evolved, and maintained in line with the project scope changes and schedules. With the aggregated data, analysis can be rapidly performed to identify those records that are not in-sync between the source and destination system (s) based on the established rules. This type of rapid analysis can be performed during the systems integrated testing (SIT) phase or dress-rehearsal phase or user acceptance testing (UAT) phase to ensure a validated ‘go-live' of the solution. For integration or synchronization solutions, the validation eQube-BI analysis reports can be easily scheduled to run at the appropriate frequency (daily, weekly, monthly etc.), thereby providing a ‘closed-loop' feedback of the validity of the solution.

"ETL" part of the solution is provided by the combined capabilities of eQube-MI and eQube-TM. eQube-MI establishes a Digital Backbone of integrated applications. It efficiently addresses complex application integration, synchronization, and migration challenges. In addition, eQube-MI based application integration infrastructure can be readily extended for secure, scalable, and robust information collaboration across networks, partners, suppliers, and customers that are geographically dispersed.

eQube-TM provides unprecedented capabilities to establish a knowledgebase of simple/complex maps and rule-based transformations between disparate systems. This knowledgebase is leveraged by all eQube offerings for application integration, synchronization, and migration.

eQube-TM works in an integrated manner with eQube-MI that provides flexibility in managing the maps and rules. During the integration, synchronization, or migration projects, the object model of the destination system as well as the transformation rules tend to evolve. Such changes / updates can be readily accommodated in eQube-TM without having a major impact on the eQube-MI processes, thereby providing dramatic flexibility and agility to the overall solution. Due to the inherent capabilities of both eQube-MI and eQube-TM offerings, as well as their integrated capabilities, a Digital Backbone of integrated applications can be rapidly built with tremendous flexibility to maintain such infrastructure at lower total cost of ownership.

eQ has successfully delivered many projects for application integration, synchronization, and migration across many industries due to this comprehensive and proven methodology of "IETLV" underpinned by the eQ offerings of eQube-DP, eQube-MI, eQube-TM, and eQube-BI.

 

Top

 Resources
 
 Learn More