1.7
The idea of a Visual QMS implementation is to allow its users to see everything they need in a way that makes sense, from any perspective/context they might need it. Based on their role or preference, perhaps they need to see their QMS information from a process perspective. Others might prefer to see it from a Regulation/Compliance Statement point-of-view (what are our regulatory statements, ISO etc.? How do we work to live up to them?) instead. Some might just want to do a free search on documents, and still see the processes and compliance statements those documents are related to. What is in it? So what you do with a Visual QMS sounds pretty straight-forward:
Draw your Visual Processes to form an easily navigated, visual map Import your Regulatory Statements (ISO, etc.) into your requirement library Create a library for your Guiding Documents, with the right metadata for people to easily find their information and the right creation and approval flows to let the organization publish new content more easily. Set up the QMS Support modules you need to help standardize different tasks surrounding the Quality Assurance work
Online
Windows
Self-Hosted
Software as a Service SaaS
qms
m-files
co-author
qms-software
document-control
quality-management
documentmanagement
document-processing
Proprietary and Commercial product.
English