The Cove Business Standards Discussion Forums More Free Files Forum Discussion Thread Post Attachments Listing Cove Discussion Forums Main Page
UL - Underwriters Laboratories - Health Sciences
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > Common Quality Assurance Processes and Tools > Document Control Systems, Procedures, Forms and Templates
Forum Username

Elsmar Cove Forum Visitor Notice(s)

Wooden Line

How do you decide what is a Process, a Procedure or Work Instruction? - Page 5


Elsmar XML RSS Feed
Elsmar Cove Forum RSS Feed

Monitor the Elsmar Forum
Sponsor Links




Courtesy Quick Links


Links that Cove visitors will find useful in your quest for knowledge:

International Standards Bodies - World Wide Standards Bodies

ASQ - American Society for Quality

International Standards Organization - ISO Standards and Information

Howard's
International Quality Services


Marcelo Antunes'
SQR Consulting, and
Medical Devices Expert Forum


Bob Doering
Bob Doering's Blogs and,
Correct SPC - Precision Machining


Ajit Basrur
Claritas Consulting, LLC


NIST's Engineering Statistics Handbook

IRCA - International Register of Certified Auditors

SAE - Society of Automotive Engineers

Quality Digest

IEST - Institute of Environmental Sciences and Technology


Some Related Topic Tags (Not all threads are Tagged)
work instructions (wi), definitions, procedures (general), processes (general), differences (general)
Reply
 
Thread Tools Search this Thread Rating: Thread Rating: 6 votes, 5.00 average. Display Modes
  Post Number #33  
Old 23rd July 2008, 08:26 PM
Jody1's Avatar
Jody1

 
 
Total Posts: 4
Re: How do you decide what is a Process, a Procedure or Work Instruction?

Excellent knowledge on display here. I have a question.

I am new to an organisation and come form a different industry (which had procedures and work instructions)

The new place has
QM
QA procedures
SOP's Standard operating procedures and WI's

I wanted rid of the SOP's but found that the industry term for this doc is SOP and calling them WI's would only cause communication problems with customers etc.

So my thoughts are to ditch the Wi's as they are performing the same function as the SOP's and use the SOP's as the HOW TO documents and keep the QAP's as the who does what when type docs.

I need to start work on the education of the business in document structure (pyramid etc) as we currently have policies that include the how to ?

Anyhow your thoughts and suggestions welcome......

New here and really enjoyng what i have found at the cove!

Sponsored Links
  Post Number #34  
Old 23rd July 2008, 10:15 PM
Patricia Ravanello

 
 
Total Posts: 307
Re: How do you decide what is a Process, a Procedure or Work Instruction?

Quote:
In Reply to Parent Post by Jody1 View Post

Excellent knowledge on display here. I have a question.

I am new to an organisation and come form a different industry (which had procedures and work instructions)

The new place has
QM
QA procedures
SOP's Standard operating procedures and WI's

I wanted rid of the SOP's but found that the industry term for this doc is SOP and calling them WI's would only cause communication problems with customers etc.

So my thoughts are to ditch the Wi's as they are performing the same function as the SOP's and use the SOP's as the HOW TO documents and keep the QAP's as the who does what when type docs.

I need to start work on the education of the business in document structure (pyramid etc) as we currently have policies that include the how to ?

Anyhow your thoughts and suggestions welcome......

New here and really enjoyng what i have found at the cove!
Hi Jody,

I think the attachment below is fairly self explanatory, but just to set you off in the right direction...
1) Identify your KEY BUSINESS OPERATING SYSTEM PROCESSES...those will become your Procedures or SOPs...you shouldn't have more than about 12-15 of them.

2) All the other Work Instructions or sub-processes left in your existing system have to be subordinate to one of your procedures...so marry them up with the right procedure, remembering, Work Instructions are only required where more detail or information is required...there should be NO orphan Work Instructions. Each one belongs to one of your Key Processes/SOPs
.
The attached Matrix lists a sample of KEY Processes or Procedures(SOPs), and as an example, under SOP-0008 Purchasing and Materials Management, you see all the supporting Work Instructions which provide the details.

If you look at SOP-0010 Product Realization, you see that it is very complex, in that it is comprised of 10 Phases....I've chosen to use 'Phase 9 - Product Launch, Production and Delivery" to show you how the Work Instructions are matched up with their "parent" procedure.

This Documentation Matrix will help employees to understand your documentation hierarchy, so it's important that you take the time to build it correctly, and provide them with a visual that they can understand and follow. It will also help you to identify where there are gaps in documentation, or the need for additional Work Instructions, as appropriate.

Hope this helps.

Patricia

[I]Afterthought...For your reference...the second attachment is a fairly widely accepted interpretation and definition of the documents typically found in an ISO-compliant Management Operating System. You can structure your pyramid/model/whatever as you choose, with as many or few layers as you deem appropriate.

Also...I'm a bit confused by your company's "Quality Procedures"...why are they segregated from the SOPs??I]
Attached Files: 1. Scan for viruses before using, 2. Please report any 'bad' files by Reporting this post, 3. Use at your Own Risk.
File Type: pdf BOS Processes & Documentation Matrix .pdf (18.0 KB, 1456 views)
File Type: pdf Sample Documentation Structure.pdf (144.7 KB, 1433 views)
Thank You to Patricia Ravanello for your informative Post and/or Attachment!
Sponsored Links

  Post Number #35  
Old 23rd July 2008, 10:31 PM
Jody1's Avatar
Jody1

 
 
Total Posts: 4
Re: How do you decide what is a Process, a Procedure or Work Instruction?

Thanks for the reply, however I think you missed my objective here let me try again

The mining industry does not recognise WI's they only recognise SOP's when really the SOP's by there very nature (descriptive) are more like a WI. As our customers constantly ask "what SOP are you working to" etc. by renaming them as WI's we would only confuse and make our life harder.

The organisation has some internal WI's (this only confuses the situation)

the QAP's are what i class as the true procedures. therefore thoughts are to irradicate the WI's (so not to confuse) keep QAP as the Higher level procedure (below the QM) and then use the SOP terminology for the instructional stuff.

This would then mean that the QAP calls out the specific SOP's required to carry out activities

Therefore when external agencies ask "what SOP are you working to" we will give them our process instruction data without confusing them with "here are our Work Instructions" and them saying "we do not undersatnd please show us your SOP's"

Hope this clarifies my question. As i am already clear on the standard document pyramid etc.
  Post Number #36  
Old 23rd July 2008, 11:32 PM
Helmut Jilling

 
 
Total Posts: 4,360
Re: How do you decide what is a Process, a Procedure or Work Instruction?

Quote:
In Reply to Parent Post by Jody1 View Post

Excellent knowledge on display here. I have a question.

I am new to an organisation and come form a different industry (which had procedures and work instructions)

The new place has
QM
QA procedures
SOP's Standard operating procedures and WI's

I wanted rid of the SOP's but found that the industry term for this doc is SOP and calling them WI's would only cause communication problems with customers etc.

So my thoughts are to ditch the Wi's as they are performing the same function as the SOP's and use the SOP's as the HOW TO documents and keep the QAP's as the who does what when type docs.

I need to start work on the education of the business in document structure (pyramid etc) as we currently have policies that include the how to ?

Anyhow your thoughts and suggestions welcome......

New here and really enjoyng what i have found at the cove!
Whatever you want to call them is OK, it depends on wha is good for your organization.As to what to keep, keep those you feel provide value, and obsolete the rest. File the obsolete ones and see if anyone misses them.

The standard explains what is required in cl 4.2.1. However, you have to decide what is useful to your company. Good Luck to You...
Thanks to Helmut Jilling for your informative Post and/or Attachment!
  Post Number #37  
Old 23rd July 2008, 11:49 PM
meo786

 
 
Total Posts: 56
Re: How do you decide what is a Process, a Procedure or Work Instruction?

Dear Sir,

In my point of view, WI are create lot of problem so you can change all the WI into SOP,



Quote:
In Reply to Parent Post by Jody1 View Post

Excellent knowledge on display here. I have a question.

I am new to an organisation and come form a different industry (which had procedures and work instructions)

The new place has
QM
QA procedures
SOP's Standard operating procedures and WI's

I wanted rid of the SOP's but found that the industry term for this doc is SOP and calling them WI's would only cause communication problems with customers etc.

So my thoughts are to ditch the Wi's as they are performing the same function as the SOP's and use the SOP's as the HOW TO documents and keep the QAP's as the who does what when type docs.

I need to start work on the education of the business in document structure (pyramid etc) as we currently have policies that include the how to ?

Anyhow your thoughts and suggestions welcome......

New here and really enjoyng what i have found at the cove!
  Post Number #38  
Old 24th July 2008, 08:03 AM
Patricia Ravanello

 
 
Total Posts: 307
Re: How do you decide what is a Process, a Procedure or Work Instruction?

Quote:
In Reply to Parent Post by Jody1 View Post

Thanks for the reply, however I think you missed my objective here let me try again

The mining industry does not recognise WI's they only recognise SOP's when really the SOP's by there very nature (descriptive) are more like a WI. As our customers constantly ask "what SOP are you working to" etc. by renaming them as WI's we would only confuse and make our life harder.

Hope this clarifies my question. As i am already clear on the standard document pyramid etc.
Hi Jody,

As Helmut said...call them whatever you want. You still need to organize them so they make sense, both to you and your customers, where applicable. I understand your nomenclature problem...you still have to be able to distinguish between the different types of documents (especially for system and audit planning purposes) - that was the point of my first attachment (above).

Perhaps, where it's useful or important to have a distinction in document types, you could use numbering to identify the different kinds of documents, without adding new terminology, while respecting the old.

Example:
...If one of your Key Process is:
SOP-08 Purchasing & Materials Management


...you could Name the associated/supporting Instructions:
SOP-08.1 Material Requisition
SOP-08.2 Supplier Selection
SOP-08.3 Supplier Performance Evaluation


You could even carry it further by labelling associated forms by adding another decimal place...
SOP-08.01.1 Purchase Requisition Form
SOP-08.01.2 Purchase Order Form

In this way, you don't confuse the customer, and you've distiguished the levels of documentation within your system and created families of documents. The Purchasing Department would most likely "own" all the documents starting with SOP-08...

That way you can stick with "SOPs", and you can still structure your system in a logical manner....I don't know how you'd ever make the distinction for the purposes of addressing 4.1.a and b...defining the key Management System Processes...their sequence and interaction, if everything is called an SOP.

Good Luck,
Patricia
Thanks to Patricia Ravanello for your informative Post and/or Attachment!
  Post Number #39  
Old 19th November 2008, 01:58 PM
gfreely's Avatar
gfreely

 
 
Total Posts: 44
I Say... Re: How do you decide what is a Process, a Procedure or Work Instruction?

Just a little unsolicited input...

In one of my previous lives (career fields), we were one branch of a national company. We had the QAM, corporate-controlled SOPs, and our branch's LOPs (our attempt at WIs).

Just thought I'd share...

and by-the-by, you want to talk CONFUSING ...

at my present position, I am taking a newer department of my company (who had their OWN doc system set up) and bridging/integrating it into the company's QMS. Try and tell a 20 yr Manufacturing manager that you are changing his documentation system...it's like trying to yank a steak away from a pit bull...
  Post Number #40  
Old 16th January 2010, 08:50 AM
Bill Goss

 
 
Total Posts: 39
Re: How do you decide what is a Process, a Procedure or Work Instruction?

I would not get too hung up on what a document is called. For example, in the old days we were all using the pyramid showing the 5 levels of documentation. Remember this? The level 1 was a policy (Quality Manual) that defined the high level commitment from management, sort of a "I swear to Quality" type of document. Then the level 2's were the procedures that defined who does what, when, where, and sometimes why. The level 3's were the work instructions or Standard Operating procedures (SOP's) that defined the "how" and these supported the level 2 procedures.

Well, in real life often we find the "how" in the level 2 procedure. So people were unsure what to call the document. My advice was always to call it at the highest level it could possibly cover. So if a procedure included "how" information, just call it a procedure and don't get hung up on what it is called.

These days, with electronic documentation system, like the e-Doc Plus 3.2 system that I sell, has so many ways to index and search for documents that finding any document you are looking for takes 2 seconds. So the level really does not matter any longer. Paper-based systems, that are rarely used these days, I can see where the category that the documents are in could matter. But who has the time and money to be using a paper-based document control system these days?

Bill Goss

Last edited by Stijloor; 16th January 2010 at 01:13 PM. Reason: Removed company name.
Thank You to Bill Goss for your informative Post and/or Attachment!
Reply

Lower Navigation Bar
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > Common Quality Assurance Processes and Tools > Document Control Systems, Procedures, Forms and Templates

Bookmarks



Visitors Currently Viewing this Thread: 1 (0 Registered Visitors (Members) and 1 Unregistered Guest Visitors)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Forum Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
Procedure vs. Work Instruction (WI) - What is the difference? eramanath Document Control Systems, Procedures, Forms and Templates 74 13th May 2016 03:13 PM
Process Flow Chart is a Work Procedure or a Work Guide, or a Work Instruction jm1231 Document Control Systems, Procedures, Forms and Templates 28 9th March 2012 12:52 AM
AS9100C Special Process Procedure - Work Instruction for AS9100 Clause 7.5.2 wanted Rockanna AS9100, IAQG 9100, Nadcap and related Aerospace Standards and Requirements 3 26th July 2011 10:27 PM
What is the difference between a Procedure and a Work Instruction? abcauto ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 2 15th July 2010 07:29 AM
When to have top level procedure in order to have a work instruction for a process goodnede Document Control Systems, Procedures, Forms and Templates 6 14th April 2009 10:18 PM



The time now is 02:03 PM. All times are GMT -4.
Your time zone can be changed in your UserCP --> Options.


 
 


NOTE: This forum uses "Cookies" - A Peachfarm Internet Property