Actually I've found that to be a big difference between consultants and employees. Any consultant who has been at more than one company for very long or on more than one project, will usually have some sort of documentation mentality and use that practice as part of the project.
It's the employees who have the mindset that I don't have to worry about their jobs and "I have this in my head" that don't document the processes. And most companies never find out the ramifications until that person either moves on within the company, gets let go with little warning or worse, gets injured or killed and can't return for some time, if ever. It's amazing how some companies will have elaborate DRP (Disaster Recovery Procedures) or LRP (Lan Recover Procedures) processes in place, yet have little or no documentation about EDI and the related processes... It's only when one of the above happens that the real 'gap analysis' begins... Ken P.S. Sorta like some of those personal home users computers I've worked on where the owners never understand the value of a backup or other precautionary actions, then call me trying to recover their data after their hard drive went belly up. I almost want to respond with Ron White's infamous title from his last CD "you can't fix stupid".... ________________________________ From: Dave Records <[email protected]> To: Chris Johnson <[email protected]> Cc: [email protected] Sent: Mon, March 28, 2011 9:48:24 AM Subject: Re: [EDI-L] What should I do with our vast EDI system? Ah, but now we are talking about documenting how everything works and fits together! But developers don't like to take the time to document, yet that needs to be part of every project. Dave Records On Mar 28, 2011, at 9:36 AM, Chris Johnson wrote: > Quoted text is from <[email protected]>, by > Leah Halpin <[email protected]> > > >With a standardized, supported solution in place, people can come and > >go without > >holding the business hostage, so to speak. > > It depends just how 'home-grown' the original system was. If it was a > labyrinth of batch files and Perl scripts then there is truth in what > you say. > > However in many cases the complexity and nuances of the EDI system are a > reflection of the complexity and nuances of the business process it > supports, so a change of EDI system may still leave you dependent on > someone who understands how it all fits together. > > Regards > Chris > -- > Chris Johnson mobile:+44 (0)7785 302122 Fax: +44 (0)870 0519 818 > EDI website http://www.edimatrix.co.uk > EDIMatrix Ltd work: 0845 126 0680 or +44 20 8778 1402 > Registered in UK no. 2777624 Reg.Office: 34 Sydenham Rd, London SE26 5QF > [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/
