Single Flow Chart for Multiple System Procedures

[jwl84]

I am looking at changing our system procedures to a flow chart design. I think it would make it a lot simpler to read and understand. For example, I want to put Purchasing and Material Management, Handling, Storage, Packaging, Preservation, Delivery, Control of Non-Conforming Product, and Verification of Purchased product all in one procedure/flow chart. Has anyone got any ideas or examples of what I am trying to accomplish? Thanks in advance to your help.

[mmantunes]

Although i understand what you´re trying to do, i think that´s not so easy as you think. The main problem is that the whole business process is too complex to be contained in just one flowchart. What i think is the best solution (i found this idea in a book by David Hoyle called "QMS Conversiosn : a process approach - highly recommended) is to divide the the whole business model in a hierarchy of flowcharts. What you´re tryinbg to to would be the level 0 - system model. In level 1, there would be the macro-process, for example, the business management process, marketing process, etc...in level 2, process derived from these, and so on.

[AndyN]

I agree with not trying to make things too complex. From the list of items going into this 'one size fits all' process map, it appears that these aren't really business processes, so much as requirements of the standard. As a result, it's going to be a less than satisfactory description of your business.

Never forget, one of the reasons you're doing this is to be able to have others speak to (describe) what's happening in the process - if it's too complex, they won't be able to and, possibly, during an audit it will make it appear as if there's no 'management commitment'............

[jwl84]

Thanks for the comments, as they do help. What if I just try purchasing into a flow chart, has anyone got any examples of how it possibly should look like?

[AndyN]

Any process is going to vary from organization to organization. For an example, I'd recommend a search, but really, you should get together with those responsible for the process and map the process the way your people do it now........

[Benjamin28]

I'm uncertain whether you're saying you're going to completely change your current procedure into a flowchart, or if you're simply going to add a flowchart into the procedure. If the ladder I would say flowcharts can be a valuable tool to summarize a procedure and often an eloquent addition. If, however, you're hoping to change the procedure to just a flowchart I would say it's a good idea but typically not realistic. Flowcharts are a great tool for displaying how a process "flows", however, they usually are not a good tool for describing the details of the process. It could work effectively with very simple processes though.

[Benjamin28]

I feel it would be beneficial to add that what you're looking into might be not so much a flowchart as much as a process map. The bigger difference being that a process map identifies inputs/outputs as well as charting the flow of the process and interaction between processes. Again, this wouldn't be used primarily as a procedure, but would be used as a tool for improvement, i.e. you identify the required inputs and eliminate the non-required excess...if you do a search for process maps there are many examples on the web as well.

[Peter Fraser]

Originally Posted by jwl84

Thanks for the comments, as they do help. What if I just try purchasing into a flow chart, has anyone got any examples of how it possibly should look like?

This is the sort of format we use - it shows who does what, and can link to documents, sub-processes etc on the right hand side in the published (HTML) version. You do not need a separate narrative "procedure" for some processes if you can get enough detail on to the right hand side of the flowchart.