To accelerate the creation of new business domains and to increase the automation of business processes, the LV publishing house decided to undergo a stepwise modernization of its heterogeneous and dated IT landscape. Given the fact that most systems were integrated via inadequately documented point-topoint interfaces, this proved to be a complex undertaking, especially since the relevant knowledge was dispersed among many employees.
By introducing an integration platform for processes and applications, the LV saw a unique opportunity to clean up its home-grown infrastructure. However, this had to be done in a way that didn’t expose daily business operations to additional risk caused by the modernization. The replacement of the legacy ERP was already decided. Other key applications, however, had to be enabled for later replacement when business considerations required.
It was clear that such an undertaking required a highly iterative approach that pulled in ALL stakeholders, not just those with a business or IT development background, but also IT operations – ideally across the entire lifecycle of the modernization effort. The LV chose the E2E Bridge® for this challenging task.
The E2E Bridge as organic Glueware for reshaping the LV IT landscape
About the Landwirtschaftsverlag Münster (LV)
The Landwirtschaftsverlag Münster (LV) employs over 500 staff and publishes journals, books and new media. With more than 20 business-related and special interest titles, LV is the leading European publishing house for farming and agriculture.
- Based on E2E’s model-driven approach, we are reshaping our publishing business in such a way, that we can react in an agile, secure and scalable fashion to the ever changing world of media.
- The E2E Bridge is a universal, easy-to-learn tool, which we employ for all our use cases in the domains of process and system integration.
As the first step of the modernization, three particular use cases were to be implemented using the E2E Bridge. These would serve as role models for the further course of the initiative. The use cases were: (1) online synchronization between the existing CRM (Cover) and the new ERP (MS Dynamics NAV), (2) the data migration for the accounts receivable master of the legacy ERP (Gypsilon) into the new ERP system, and (3) the implementation of a coordination process for Newsletter orders with the ASP partner xQueue.
For the CRM/ERP synchronization, the creation of customer records was implemented based on outstanding invoices that are created in Cover and which are handed over as open items into MS Dynamics NAV.
In this process, the E2E Bridge takes on all tasks starting with the periodic check for new invoices from Cover, their transformation into the data structure required by MS Dynamics NAV, checking the availability of a corresponding customer record, and if not available, the creation thereof in the accounts receivable master. The return process was implemented in form of a Web service that delivers all open items per customer.
For the second use case, the E2E Bridge reads the accounts receivable master of Gypsilon. Thereafter, the E2E Bridge transforms debtor data from Gypsilon and automatically creates new debtor and open item records in MS Dynamics NAV.
Finally, and as a third use case, a service was implemented which ensures the synchronicity of Newsletter orders on the xQueue system with those of Cover. Before launching the overall modernization effort, this use case also served as a 3-part proofof- concept scenario during the evaluation phase of the E2E Bridge selection, the results of which could be reused in the production phases of the final project.
For the complete implementation of all use cases from planning to production use, less than 10 weeks were needed in total.
Results & Benefits
- Implementation of all use cases using the E2E Bridge as the ONLY tool, leading to a drastic reduction of complexity and time to market
- With the E2E Bridge, processes, services and interfaces can be planned, developed and operated rapidly and with high quality
- Executable models are the basis for specification and production, therefore they are easily maintained and can be changed rapidly
- Existing infrastructure can be totally reused, legacy systems are encapsulated for subsequent modernization and migration
- Technical and non-technical coworkers can be easily trained to use the model-driven development methodology on an everyday basis
- The model-based approach fosters communication and collaboration between business, IT development and IT operations