Oh no - I was only generalizing on the 6 month rule. Some of these systems do take years.
And good luck waiving out of the 20% (19%, 18%) annual maintenance. Even if they'd let you, you;d have to be nuts to do it. This isn't [pick your favorite call me for $29.95 to fix this problem vendor], you CAN'T call with a credit card to get a support call. If yhey don't know you, you can't talk to them. Not even for cash on the call. Brian Lehrhoff, EA ([email protected]) Messaging Consultant 201-913-4506 Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html ________________________________ From: Ken Etter <[email protected]> To: Brian Lehrhoff <[email protected]>; [email protected] Sent: Mon, March 28, 2011 9:31:09 AM Subject: Re: [EDI-L] What should I do with our vast EDI system? Excellent point... But not only do you have the cost of the software, the cost of the time to implment, but also there's an additional YEARLY 20% maintenance fee on top of everything else. Now you can obviously choose to forgo that, but then you also forgo free customer support and in some cases free updates along the way as well. if you're putting in a new EDI system, I would highly advise NOT to forgo the maintenance fee. And depending on what the EDI staff's responsibilities, 6 months to complete might be a bit short. I've usually found with any sort of medium or larger (volume) system it takes close to a year or more by the time you go through the decision making process about what software is going to be used, getting the software installed and initially stabilized, training (whether self or formal courseware or classes through the EDI software company) then you get to start working on maps, testing and moving all the TP setups over, connectivity setups for VAN, FTP and AS2, etc.. If you have an EDI team you might be able to do it this (6 months) quicker or sooner , but with a one or two man shop, 6 months might be a bit short... And keep in mind you still have to keep the old system going until you have everything moved over and still take care of any production issues as well.... Ken [email protected] ________________________________ From: Brian Lehrhoff <[email protected]> To: [email protected] Sent: Mon, March 28, 2011 8:27:34 AM Subject: Re: [EDI-L] What should I do with our vast EDI system? If it's not broken, why are you trying to fix it? Any commercial software will take you 6 months to learn and implement, and will cost 100% of the acquisition cost for implementation. Is this a cost that your company wants to take on? Brian Lehrhoff, EA ([email protected]) Messaging Consultant 201-913-4506 Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html ________________________________ From: karnaf62 <[email protected]> To: [email protected] Sent: Sun, March 27, 2011 6:43:30 PM Subject: [EDI-L] What should I do with our vast EDI system? We have an in-house EDI server, EDI software, 100s of trading partners, 15 different EDI transactions, X12 and XML, various custom-files exchanged using EDI between several in-house systems and much more. Since we are a "Vendor" and our Trading Partners are "The Customer", according to EDI de-facto rules, we have a custom map for each TP/Transaction. This vast system is a product of my hard work for over 15 years at my company . Everything is working very well, self supported, no issues. But(!), nothing will stay the same for ever... including myself (I moving to a new role in the company) and our aging EDI system that will have to be replaced by new software (i.e. throw away all the current maps and setups and write them from scratch). We are not opposed to outsourcing, especially with EDI which, in general, requires a one-time setup for each interchange and not much of maintenance after that. But, because we are so dependent on EDI with our customers (EDI brings more than 90% of our sales) we want costs to be down, and fast response to changes and new setups. What would you recommend? ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links [Non-text portions of this message have been removed] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
