Scope of a "process"? What is a Process?

[Bifften]

Processes exist at every level. I sense you are thinking very "macro" by the sounds of it.

I'm currently producing maps at department level, going into more task orientated detail where neccessary and then ultimetly hoping to produce a top-level (macro) overview when its all complete.

This is an example of one I've produced for a Contracts process within the company. In full this process will then form one step in a full process from Marketing -to- Sales -to- Estimating -to- Contracts -to- Service Aftercare etc ....

 

[AustQFS]

Perhaps the attached documents will help.
The first outlines some standard terminology for describing the system --> process area --> process --> activity/task.
The second is an example of how this might be used (it refers to Business continuity not ISO9001 but helped me anyway).
The final two are from PriceWaterhouseCoopers, similar to the above.

Finally, I find that procedures can cover anything from a set of processes, down to a specific activity or task. It depends on how the organisation works (if one person is responsible for a whole set of processes it makes sense for the procedure to cover them all - perhaps not in much detail because after all, that one person presumably is familiar enough not to need detailed guidance.) If one area is rather complex and important, you might wish to describe all the "must do bits" it in its own detailed procedure.).

 

[tmoreau]

Re: Scope of a "processes"?

Sorry, but with this addition, now I'm even more confused. You started off talking about '2 flowcharts' (which is what I thought covered your processes...' Why are you adding in this bit about quantity of docuemntation/procedures (if we're focussing on processes)?

Because we are focusing on what IS a process, how wide is your lens.

How do you define a process? In a company is there:

A) Only 1 process, the top level map
B) 11 proceses, each of the boxes on the map
C) 4,782 processes, every task ever able to have defined inputs and outputs

My final conclusion was that the auditor was a little daft, upon actually reading the documents he readily agreed everything is ok and performed a seamless audit.

1 box on the top map = 1 procedure = 1 process, no problem.

 

[Sidney Vianna]

Re: Scope of a "processes"?

1 box on the top map = 1 procedure = 1 process, no problem.

So, what is a system?

 

[AustQFS]

Re: Scope of a "processes"?

So, what is a system?

LOL.. Download the links in this thread - "guidance on process approach" and the 4 documents I just posted.

 

[tmoreau]

Re: Scope of a "processes"?

Main Entry:sys·tem

Pronunciation: \ˈsis-təm\ Function:noun

1: a regularly interacting or interdependent group of items forming a unified whole <a number system>

2: an organized set of doctrines, ideas, or principles usually intended to explain the arrangement or working of a systematic whole <the Newtonian system of mechanics>

So, according to the dictionary, a system would have to be everything.

 

[Sidney Vianna]

Re: Scope of a "processes"?

Main Entry:sys·tem

Pronunciation: \ˈsis-təm\ Function:noun

1: a regularly interacting or interdependent group of items forming a unified whole <a number system>

2: an organized set of doctrines, ideas, or principles usually intended to explain the arrangement or working of a systematic whole <the Newtonian system of mechanics>

So, according to the dictionary, a system would have to be everything.

Meet ISO 9000 principle # 5, System approach to management.

 

[AustQFS]

Re: Scope of a "processes"?

Or, in plainer English - all the bits you're responsible for while getting your product to the customer?

 

[Peter Fraser]

A (business management) system is "the structure, processes and resources needed to establish an organisation’s policy and objectives and to achieve those objectives”.

 

[qualitymanager]

Re: Scope of a "processes"?

...
How do you define a process?
...

ISO/TC 176 has a definition. It does not speak to the scope.

IMO you define the scope based on your output (and input, and activities, and resources and "transformation"). Once it meets the definition, its a process (or a duck, but I digress).

...

My final conclusion was that the auditor was a little daft, upon actually reading the documents he readily agreed everything is ok and performed a seamless audit.

1 box on the top map = 1 procedure = 1 process, no problem.

Well, what is a procedure (ISO/TC 176 definition), after all?

And a "system" is a collection of processes.

Marc has good diagram which I've attached (can't find it on the Cove right now).