It is also pretty easy to code the guidelines in these tools to validate business rules, including external database lookups so that you can run a sample file through the tool and get an error report of what failed and why. I couldn't even imagine how long it would take using Word to have it evaluate a file and throw an error if a customer or item number was not found in a database.
Tor From: [email protected] [mailto:[email protected]] On Behalf Of Art Douglas Sent: Thursday, January 22, 2009 10:47 AM To: 'Bill Laidley'; [email protected] Subject: RE: [EDI-L] Call for Analogies I don't know, Bill. (Sentence works without the comma too.) I have used both tools that I mentioned, EDIFECS SpecBuilder and Foresight EDISIM. True, you can use either one to simply pull out the applicable standards. But both of them offer extensive opportunities to add comments. I have used them to add business context. When I was setting up a custom IG for a contract manufacturer my client used in Taiwan and it appeared that they were only on hour three of Learn EDI in 24 Hours for Dummys, I included explanations for each and every element, including the zeroes in ISA01 etc. I explained that they shouldn't send the REF if they didn't have a value to place in REF02, and I told them that they might expect a second N3 segment in the event the ship-to required three lines to fully describe, but that one would be okay too. I explained right in that document that when I sent them a piece of data coded as Commercial Invoice, they should print that value on the case label and put it on the paperwork for the customs agent. I found the tool extremely useful, and what I did in six weeks I couldn't have done a small percentage of with Word or Excel in that time. From: [email protected] <mailto:EDI-L%40yahoogroups.com> [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> ] On Behalf Of Bill Laidley Sent: Thursday, January 22, 2009 10:31 AM To: [email protected] <mailto:EDI-L%40yahoogroups.com> Subject: FW: [EDI-L] Call for Analogies I'll offer a counterpoint. Yes the software to create implementation guides is faster, etc. What it does not do is explain your business context, or your EDI context, or frankly anyone's context. All they do is suck out a subset of the standards. Not really all that useful. I do a lot of EDI implementations and my idea of a good implementation guide is the one that does not require lots of telephone calls and emails to get clarification. Good implementation guides get written by hand, by someone who understands both EDI and the business context in which the EDI will be used. Which usually means using Word or some equivalent. Bill Laidley CT Resources [email protected] <mailto:bill.laidley%40shaw.ca> <mailto:bill.laidley%40shaw.ca> Voice: 604-628-7121 Cell: 604-723-7871 From: [email protected] <mailto:EDI-L%40yahoogroups.com> <mailto:EDI-L%40yahoogroups.com> [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> <mailto:EDI-L%40yahoogroups.com> ] On Behalf Of Norton, Karen Sent: Thursday, January 22, 2009 9:51 AM To: [email protected] <mailto:EDI-L%40yahoogroups.com> <mailto:EDI-L%40yahoogroups.com> Subject: [EDI-L] Call for Analogies Hi everyone. I want to justify purchasing some software to create implementation guidelines because we're on a big standardization kick for 2009, but when I mentioned it to my boss, he said "<groan> More money? Can't you just do them as Word documents?" At that point, I stopped talking because I knew I could explain the need but it would take me about 30 min. and several pieces of paper, and by the time I finish he'll just be ticked off, even if I convince him. So I need an analogy. I don't need cost/benefit analysis, or ROI, etc. I need something relatively short and snappy that will turn on the light bulb over the head. Something on the order of "Imagine creating that fancy newsletter when all you have is Notepad -- yes, you can do it, but with lots of pain and effort and asterisks and pipes and dashes". But with more oomph, to impart the intricacies of code lists, required vs. optional, segment descriptions, etc. I had ideas like building a car without design diagrams, or making a chip without whatever, but I don't know enough about either to make the analogy work. Ideas? Thanks for your help. Karen Norton. Atmel Corp. [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] CONFIDENTIALITY NOTICE The information in this message is intended only for the addressee or the addressee's authorized agent. The message may contain information that is privileged, confidential, or otherwise exempt from disclosure. If the reader of this message is not the intended recipient or the recipient's authorized agent, then you are notified that any dissemination, distribution or copying of this message is prohibited. If you have received this message in error, please reply to the sender and then delete the message. [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: mailto:[email protected] mailto:[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/
