CASE STUDY: ERP REAL TIME INTEGRATION



Integrating Customer Experiences Despite Disparate ERPs

About Client
The Client makes, sells, and rents hospital beds and other patient-room furniture and equipment, along with stretchers, surgical tables and accessories, and other equipment for lifting and transporting patients. Because these products were attached to healthcare use cases, they also integrated with other electronic medical record solutions in the marketplace. Thus the Client is a highly integrated medical device manufacturer, and a global leader in its discipline.

About Telligens
Telligens is a solutions company with its diverse team located in North America and Asia Pacific. The team members at Telligens have been handpicked over the course of 5 years, and represent the top talent globally in the discipline of I.T. Technology.


CHALLENGE AND WINS

CHALLENGE
The Client leveraged SAP for their ERP, however after acquiring another major medical device manufacturer, they inherited a second massive JD Edwards implementation. They were faced with the decision of whether to fund a giant conversion effort into SAP or living with separate systems. The go forward decision ultimately landed with both SAP and JD Edwards working in parallel. However this decision also meant that the customer facing aspects of their business required legitimate integration. This was immediately evident during an SAP Hybris deployment which required an integrated view of product and service offerings. The service provider implementing SAP Hybris was delayed by almost a year in their delivery schedule, and a big impediment was the lack of data integration. To address this problem the Client began investigating software and service solution partners that could help them obtain productive integration.

TOOLING
The Client ultimately decided to leverage on Microsoft Dynamics.
While the tool was chosen, they did not have a solution provider. After an extensive review of references and background the Client decided to engage Telligens to conduct the solution deployment.

NAVIGATING CONSTRAINTS

DATA LATENCY
The deployment of Microsoft Dynamics had varying levels of data access velocity which it required. Others like the production of lists, could be driven with more structured queries. However, the requirements for each of these access velocities was something the joint teams had not explored in detail.
BI-DIRECTIONAL SYNC
The solution required the ability to read data from the previous erp system and the ability to write back. This mixed requirement along with the data latency requirements created a challenging scenario to architect.

STARTING BEHIND THE 8 BALL
The on-boarding of the data project had come as part of the Microsoft Dynamics deployment which was already a year behind schedule. Thus Telligens would be playing catchup so that the data pipelines would be available as deployment approached a testing phase. However, the first testing was needed on month 1 of a 4 month project, creating an immediate bottleneck.

MULTIPLE APPLICATION FUNCTIONS AND USE CASES
The priority of the projects started in the Product, Order Entry, Order Status, B2B Pricing, Inventory and User Management categories. However, this was just the beginning of the required application functions which the Client wanted to deliver. Many other functions including the future deployments of international currencies and rental automation were required. Thus the platform needed to support an expansive number of application functions beyond the initial deployment.
Find out how we championed the clients deployment and winning its challenges.
Contact us at: letstalk@telligens.com

 

 

Similar Posts