Two years ago I had to replace a very aging GENTRAN system with GIS. GENTRAN could no longer handle the volume. From the time we acquired the software until I had everything converted was about 9 months. In spite of the expense, the volume problem went away and stayed away. It brought a tremendous peace of mind. For over 10 years the GENTRAN ran just fine, then we acquired Wal-mart for a customer and that tripled our volume which meant we had to acquire a much more robust system. Hence "nothing will stay the same for ever."
Sincerely, Jason McMahon 8079 Village Drive Cincinnati, OH 45242-4315 <mailto:[email protected]> [email protected] http://gutausse.weebly.com/articles.html <http://gutausse.blogspot.com> http://gutausse.blogspot.com <http://www.linkedin.com/pub/jason-mcmahon/11/743/51b> http://www.linkedin.com/pub/jason-mcmahon/11/743/51b _____ From: [email protected] [mailto:[email protected]] On Behalf Of Brian Lehrhoff Sent: Monday, March 28, 2011 8:28 AM To: [email protected] 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] <mailto:blehrhof%40cybernex.net> ) 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] <mailto:raananh%40gmail.com> > To: [email protected] <mailto:EDI-L%40yahoogroups.com> 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 <*> 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/
