J
jm1231
Is a Process Flow Chart is a Work Procedure or a Work Guide, or a Work Instructions? How those documents differ? Thank you.
Is a Process Flow Chart is a Work Procedure or a Work Guide, or a Work Instructions? How those documents differ? Thank you.
Is a Process Flow Chart is a Work Procedure or a Work Guide, or a Work Instructions? How those documents differ? Thank you.
2.7.2 Types of document used in quality management systems
The following types of document are used in quality management systems:
a) documents that provide consistent information, both internally and externally, about the organization's quality management system; such documents are referred to as quality manuals;
b) documents that describe how the quality management system is applied to a specific product, project or contract; such documents are referred to as quality plans;
c) documents stating requirements; such documents are referred to as specifications;
d) documents stating recommendations or suggestions; such documents are referred to as guidelines;
e) documents that provide information about how to perform activities and processes consistently; such
documents can include documented procedures, work instructions and drawings;
f) documents that provide objective evidence of activities performed or results achieved; such documents are referred to as records.
Thanks for the information.
I therefore conclude that process flow chart is regarded as under statement letter e. But again, work procedures and work instruction is both described on letter e as one, does it mean that work instructions and work procedures can be used interchangebly? They dont differ on either way?
WI = WP?
I think the OP is right. A process flow chart would probably qualify as a procedure unless it is optional and then it becomes a guideline.Probably No. Point (e) says it (category of docs.) can include 'procedures' and 'work instructions'.
They are both procedures. A work instruction just happens to be more detailed.Infact a procedure, as the definition goes, is a specified way to carry out an activity or a process whereas a 'Work instruction' is a step by step description of carrying out a specific task.
Now I recognize that I am probably alone in this but feel that purchasing is not a process on its own but is an activity that supports a lot of the 'product realization' processes. A flow chart can also describe a process. As soon as it prescribes the way of doing things then it becomes a procedure.e.g. Purchasing is a process and can be summarized in the form of a Process Flow chart depicting how different activities are carried out in a defined way but you can have a work instruction on how to generate, e.g. a Purchase Request through ERP/ SAP or by whatever means.
Hope this clarifies.
Hardly there's any harm in calling both the documents as procedures but at some point we need to differentiate the two. 'Procedures' are normally defined at the 'Process or 'activity level' (largely at the functional/ department level) but certainly the work instructions come into way at the 'task level’. The task level is at the level of the individual. A process is not a ‘work’ (task) but a set of activities or tasks and hence the two cannot be considered as one and the same thing.They are both procedures. A work instruction just happens to be more detailed.
Since 'purchasing' fits well into the definition of a 'process', I know it as a 'process' but in the big picture (Product Realization), it can also be termed as a 'sub-process' (undefined). There's no fine line where we stop calling an 'activity' a 'process'. If you further go up, Product Realization Process may look like a sub-process of the 'Demand Fulfillment Process' which again is a subset of the higher level Business processes. It all depends on the way one looks at the things.Now I recognize that I am probably alone in this but feel that purchasing is not a process on its own but is an activity that supports a lot of the 'product realization' processes.
By your own reasoning, it can also be tagged as a Work Instruction (the way of doing things). 'things' is a confusing word - if you replace it with 'process or activity', then it's a procedure but if you replace it with 'work' or 'task', then it should logically be a WI.A flow chart can also describe a process. As soon as it prescribes the way of doing things then it becomes a procedure.