|
But be careful here. I just hired a new programmer. His reason for leaving the employer? They became ISO9001 last year and now have to fill out 4 forms in triplicate with required signatures to just blow his nose. And actually changing code is almost impossible. There is a happy medium between Control, process documentation, etc. But it can be very hard to find. Regards, Bob Crothers Cornerstone Communications, LLC www.faxserver401.com another day done all targets met all systems fully operational all customers satisfied all staff keen and motivated all pigs fed and ready to fly... -----Original Message----- From: Eric DeLong [SMTP:eric.delong@pmsi-services.com] Sent: Friday, February 05, 1999 10:14 AM To: MIDRANGE-L@midrange.com Subject: Re: ISO Cynthia, We have been ISO9001 certified since last year. I don't know the specifics of all the "hoops" we had to jump through, but it was mostly a process of documenting work instructions for each department. Think of it as creating the biggest, most comprehensive training manual you've ever seen, and you'll be close to the reality of the process. eric.delong@pmsi-services.com ______________________________ Reply Separator _________________________________ Subject: ISO Author: <MIDRANGE-L@midrange.com > at INET_WACO Date: 2/4/99 7:27 PM Our company has just committed to getting our corporate office ISO certified. Our manufacturing divisions have already received certification but not other various corporate departments. Has anyone out there had any experience in "ISO-izing" an IS department? I'm thinking I can start with Service Level Agreements (both internal and external) and analysis of Help Desk requests/completions to ensure conformance to standards. Any and all help would be greatly appreciated. By the way, many thanks to all of you who responded to my earlier question on ACOM checks printing wrong. Turned out to be a problem with our software vendor's use of printer overrides. Regards, Cynthia +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.