| |In certain cases, it is not practical for a customer to shut down legacy application on a particular day and move to the new one. Many factors drive towards a ‘bi-directional synchronization' as the most prudent strategy. Some of the factors are:
1.The legacy application is complex and its usage (# of active users) is extensive (several thousand active users).
2.The targeted new application does not have all the capabilities required available on day one, but it is the right solution strategically and it has a sound road map of capabilities required by the customer.
3.The legacy system works reliably every day – therefore, the users are reluctant to let go of it.
4.Most prudent strategy is to begin leveraging the required capability of the new application and migrate some of the legacy system capabilities, while keeping the remaining capability active in the legacy application. Essentially, the users will work in both systems for a period of time.
5.Over time, migrate all legacy system capabilities to the new system and phase out portions of legacy system leading to complete migration.
eQube-MI with eQube-TM have the flexibility to accommodate such complex bi-directional synchronization logic where both systems are masters for certain domains and slaves of other domains. With eQube-MI there is substantial proven capability to model and incorporate logic to consistently and reliably manage such scenarios.
eQ has successfully implemented bi-directional synchronization leading to orderly migration strategy with marquee customers in the PLM domain.