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] Voice: 604-628-7121 Cell: 604-723-7871 From: [email protected] [mailto:[email protected]] On Behalf Of Norton, Karen Sent: Thursday, January 22, 2009 9:51 AM To: [email protected] 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] ------------------------------------ ... 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/
