T
I have a question about employee access to the QMS. We are currently implementing ISO 9001:2008 at a small manufacturer and though we are in two separate buildings, there is no network. The product we are using is meant to run on a network, but can also be purchased as a single user. The single user license is meant to give companies a platform on which to develop until the system is ready to be deployed thus saving the cost of a network version throughout the implementation and writing process.
There is some resistance to to putting in a network-perhaps over security concerns or the possibility of people accessing the internet. However, employee access to the manual seems to be a requirement of ISO. I suppose we can print it out, but that seems to defeat the purpose of having an electronic quality manual, not to mention creating a paperwork headache. Others insist that changes to procedures are so rare that it would not be a problem. But isn't a QMS supposed to be dynamic even if it is tracking only minor changes? Isn't continual improvement part of the equation? I thought a compromise position might be to post it on a workstation computer in each building as a PDF file and updating the PDF version as it changes, but the product that we have allows for any employee to access the system directly to suggest corrective actions. In electronic form, changes are automatic and there is no need to update multiple PC's. It is also easy to navigate and find exactly what you are looking for, whereas a PDF is just a big file that you would need to scroll through to find what you are seeking.
Any thoughts on how to make the case for deploying this the way it was meant to be?
There is some resistance to to putting in a network-perhaps over security concerns or the possibility of people accessing the internet. However, employee access to the manual seems to be a requirement of ISO. I suppose we can print it out, but that seems to defeat the purpose of having an electronic quality manual, not to mention creating a paperwork headache. Others insist that changes to procedures are so rare that it would not be a problem. But isn't a QMS supposed to be dynamic even if it is tracking only minor changes? Isn't continual improvement part of the equation? I thought a compromise position might be to post it on a workstation computer in each building as a PDF file and updating the PDF version as it changes, but the product that we have allows for any employee to access the system directly to suggest corrective actions. In electronic form, changes are automatic and there is no need to update multiple PC's. It is also easy to navigate and find exactly what you are looking for, whereas a PDF is just a big file that you would need to scroll through to find what you are seeking.
Any thoughts on how to make the case for deploying this the way it was meant to be?