Estimated reading time: 4 minutes, 32 seconds

Hello All; Yes, I've been absent for a few weeks. But I'm back on the road again after a painfully long adventure into an implementation, subsequent removal, and finally a successful deployment. But first, the important issues...

My stint was in Denver, Colorado - where I went to school for a couple years. Needless to say, Denver has changed a lot since I was there but I still love the climate, the view of the mountains, and the occasional trip to Red Rocks park. Unfortunately, I'm a little old to go climbing the rocks and spelunking, even though the caves are shallow. While I was there, I visited Buckhorn Exchange (www.buckhorn.com/supper.htm), a restaurant I could only get to very occasionally during my college days (money was always an issue). Buckhorn is a remnant of Denver history with a menu that includes rattlesnake, buffalo steak, rocky mountain oysters, and of course, beef steak. I had to go back several times, partly for old times sake, but mostly for the atmosphere and to work my way through the menu. I can still taste the Elk... But back to business My client had decided to install a full blown EDI system on their own equipment, using their own IT staff, and connecting to their internal ERP system. To be kind, I won't mention the vendor's name, but you would certainly recognize it as a long time player in the EDI software market.

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.


While they were doing their research, I took off for the mountains for a week. When I got back, they had decided to take what they lovingly termed "the no-brainer way out." They had initially found three or four EDI companies that required no hardware and no locally installed software. These constitute the current, growing wave of SaaS providers. After interviewing them all and determining that all of the companies subscribed to the 'reuse it all' software philosophy, they picked one. Again, I won't name names, but also again, you would certainly recognize this player. So, for the next week I essentially watched as the IT team set up their connection to the SaaS applications, installed the pre-built ERP connectors, selected the existing maps for their customers, and started moving transactions. Don't get me wrong... I helped out with plenty of advice and commentary. But to be honest, I'm thinking I need to hone my specialties a bit so as to be better equipped to help with these kinds of implementations. I also may need to learn how to work my way through a menu more efficiently since it looks like my engagements may be getting shorter as this kind of implementation catches on. One last comment ----
Don't forget that UConnect is close upon us (June 4-7) in Orlando. I went to the Gaylord Palms for a visit a few weeks ago, and I can tell you that if you enjoyed the other Gaylord venues, you'll love this one too. As an added treat, this year ec-bp.org will have its own booth. Scott Koegler has demanded that I be there, and I've promised to show up (at least for part of the time). And if you come by the booth, Scott promises to have a special souvenir for you. I'm not sure what he has up his sleeve, but I want one. See you in June! Cecil

Last modified on Friday, 17 February 2012
Read 1620 times
Rate this item
(0 votes)

Visit other PMG Sites:

click me
PMG360 is committed to protecting the privacy of the personal data we collect from our subscribers/agents/customers/exhibitors and sponsors. On May 25th, the European's GDPR policy will be enforced. Nothing is changing about your current settings or how your information is processed, however, we have made a few changes. We have updated our Privacy Policy and Cookie Policy to make it easier for you to understand what information we collect, how and why we collect it.
Ok Decline