|
Written by Cecil T. Wulfe
|
|
Tuesday, 29 May 2007 |
|
Page 2 of 4
In the beginning, all went fairly well. My role was to install the software on their brand new server purchased specifically for this installation. No problem. The installation went fine. My next task was to train the IT staff on integration, creating maps, and dealing with the company's customers.
To their credit, the staff understood the application. They caught on to the idea of mapping even though they had some initial confusion over the use of the term 'standard' and the need to make everything custom. And they were champs at integrating the EDI system with their ERP system.
What they had difficulty with was the concept of creating everything from scratch for each of their customers. This was tough for them to swallow since they knew that their software vendor had already supplied systems to hundreds of other companies. And many, if not most of those companies were already connected with the same customers they wanted to connect with, but they couldn't get a copy of the maps that were already in use. To be honest, I've always had a hard time understanding why these things aren't simply collected, updated, and made available for free, but who am I?
But my own understanding and gentle ways were not enough for two of the IT directors at my client's site. Even though they were close to completing their implementation, they were adamant that there had to be a better way to deal with these things.
Part of their frustration came from the fact that their entire IT environment was based on reusable code. They believed that if they could use the same complex code multiple times and save the expense of redeveloping, there was no reason they couldn't reuse something as common as an EDI map.
Out With the Old
So it was more out of protest to the business practice that they decided to tear out the system we had spent the last three weeks putting together. They went back to the drawing board (actually they went to Google) and searched for EDI providers.
|
