During some recent searches of this forum I saw where David Bradley presented a Process (COP), SIPOC, and something called an 'octopus map.' I would like to know more about how the Octopus Map is developed / used.

Thanks,
Doug

Using the patented Claes' Two-Window Method, here's a couple of threads:
Octopi, turtles, and COPS, OH MY! (http://elsmar.com/Forums/showthread.php?t=6005&highlight=octopus)
Le Flow de Process (http://elsmar.com/Forums/showthread.php?t=6370&highlight=octopus)
The first one is pretty extensive, with a good attachment from "db".

edit:
Duh! that would be what you were talking about. energy disease: fingers faster than brain. Oh well, good reference!

For example, take the leg of the octopus (see the db diagram) labeled "order request". One side of that leg would be the Purchasing Dept. at XYZ, Inc. (let's call her Shelly). The other side of the leg would be the Receiving, Production Scheduling, Team X and Accounting.

What you are trying to do is define how YOUR process informs XYZ receiving that there is a trainload coming in on Dec 2, XYZ production scheduling that they can expect their JIT shipment to begin processing at XYZ receiving on Dec 2, the XYZ team X production team leader that their kanban request for another trainload has been processed and shipped for Dec 2 receipt, and XYZ accounting that you expect payment for a trainload on Jan 2 after you get an order from Shelly for a trainload.

Anyone else?

Icy Mountain,

Thanks for the links and description, but I would like more information on the Octopus Diagram / Model. The links did not provide information on how the Octopus Diagram was designed to be utilized. I then searched the internet, and the only information I found was a Special Reprint of The Informed Outlook (July 2002 Issue) titled "How Can You Move From QS-9000 to TS 16949:2002?" (This information was also available on the IATF site or a related site.) The article indicated that the Octopus model is an auditing methodology, which was also indicated in the links you provided. It did not describe how it was designed to be utilized. It did state that it "was discussed at the ISO/TS 16949:2002 Rollout Meeting in April, 2002 and in the IATF registrar training sessions." That was about it!

Since the COP is also utilized in the mapping of a process, I perceived that the Octopus was a tool for mapping a series of processes but did not know how it was utilized, other than the apparent listing of processes that had some sequential relationship.

As for your example, you are indicating that the legs are to be used to identify the funtions that input to the Order Review process and are the output of the process, but then when you go through the series I did not see the relationship of the Design Process. Which would lead me to the question as to how the Octopus Diagram / Model would show those processes that may be performed in parrallel or in conjunction with the overall process.

Doug

DP,
This is in French but maybe it will help the explanation. Hopefully one of our Canadian friends who parlez Francias can translate.

If my rudimentary French is adequate: "marchandises" flow through process F1 at Port 2000, with the customer (or next processor or result) being "bateliers, armatuers, routiers" which then flow through process F2 to "employes du port".

Please someone translate the F1-FC2 functions.

Would one of our international members please translate the octopus in this post:Octopus Map (http://elsmar.com/Forums/showpost.php?p=65744&postcount=4)

Icy Mountain,

I appreciate your tenacity in this matter. I take it that you were not part of this 'Rollout Meeting in April, 2002' nor 'in the IATF registrar training sessions.' Maybe someone in the forum would share this information with us and we would not have to get the french examples translated. Wouldn't that be nice!

Thanks,
Doug

Would one of our international members please translate the octopus in this post:Octopus Map (http://elsmar.com/Forums/showpost.php?p=65744&postcount=4)

Here is the best I can do -

the title is "Diagram of octopus of Project Port 2000"

F1 = "Goods"
F2 = "Boatmen Road Ship-Owners
-- = "Employees of the Port"
FC1 = "Safety"
FC2 = "Environment"

Below the title is "Functions"
F1 = Shipment of Goods
F2 = "Functions of Reception, Service, Maintenance, Control, Supply"
FC1 = "Do not attack fauna and the flora pollution"
FC2 = "Safety Vis-a-Vis the fires, with the (??) (??) safety of the people and the goods"

Hope that helps.

Dave

Icy Mountain,

I appreciate your tenacity in this matter. I take it that you were not part of this 'Rollout Meeting in April, 2002' nor 'in the IATF registrar training sessions.' Maybe someone in the forum would share this information with us and we would not have to get the french examples translated. Wouldn't that be nice!

Thanks,
Doug

I never took French, but this is how I see it. But, Happy Thanksgiving. :p

PD,

The octopus is a model that defines your business as the body of the octopus and the legs the inputs and outputs of internal processes as seen by the customer. Example, quotation. The customer sees the process as: I request a quotation and I receive a quotation. The actual RFQ may pass through multiple functions in your organization, but the customer sees it as one function.

The octopus was developed by the the big three and Plexus Corporation. If you deal with the automotive industry you will be developing Customer Oriened Processes (COP's), and they are the components of the octopus.

Hope this helps.

Dave, I think the missing words in FC2 (marées noires) would be oil slicks or something like that.

/Claes

Dave, I think the missing words in FC2 (marées noires) would be oil slicks or something like that.

/Claes

:vfunny:

Icy Mountain,
I appreciate your tenacity in this matter. I take it that you were not part of this 'Rollout Meeting in April, 2002' nor 'in the IATF registrar training sessions.' Maybe someone in the forum would share this information with us and we would not have to get the french examples translated. Wouldn't that be nice!

You are correct, sir. I'm just trying to learn something/teach something based on how I've seen these used in the past.

I found this interesting 'Octopus': http://www.usc.edu/hsc/dental/ccmb/usc-csp/octopus.jpg

So, has anyone here actually created an octopus diagram for their company? Is there a real example? All I've really seen is that generic example with the generic COPs, market analysis, bid/tender, etc. And all that is, is a circle with those processes listed around the outside. Just like that it doesn't seem to be very useful. Even the one in French only has 5 "COPs," which don't really seem to be COPs at all.

So, has anyone here actually created an octopus diagram for their company? Is there a real example? All I've really seen is that generic example with the generic COPs, market analysis, bid/tender, etc. And all that is, is a circle with those processes listed around the outside. Just like that it doesn't seem to be very useful. Even the one in French only has 5 "COPs," which don't really seem to be COPs at all.

This may be a double post. I tried to post a second ago, but nothing came up. Perhaps I've reached the limit on posting.

I haven't done one for my company, but have for several clients. I will try to find one and post it.

Other than the generic examples (which are explanatory but unfortunately not 100& satisfactory), no real examples since than. Anyone to submit a real example from their companies will be appreciated by all gents here. Thanks in advance

So, has anyone here actually created an octopus diagram for their company? Is there a real example? All I've really seen is that generic example with the generic COPs, market analysis, bid/tender, etc. And all that is, is a circle with those processes listed around the outside. Just like that it doesn't seem to be very useful. Even the one in French only has 5 "COPs," which don't really seem to be COPs at all.

In all my audits, I have never seen an octopus diagram that made sense. It was used as a teaching tool by Plexus, to attempt to explain the process approach, but didn't think much of it then either.

I see a lot of Turtles, and Process Maps, flowcharts, but no Octopuses.

Companies don't like Octopus and it is almost impossible to find Octopus in company. For me Octopus is only good philosophy. And I like this philososophy because it is philosophy of focusing on customer. Unfortunately a lot of QM systems are not focused on customer.

Companies don't like Octopus and it is almost impossible to find Octopus in company. For me Octopus is only good philosophy. And I like this philososophy because it is philosophy of focusing on customer. Unfortunately a lot of QM systems are not focused on customer.


Please see my previous post (#17). Focusing on the customer is a good idea, but the octopus is a diagram that provided little value. It looks like a bottlecap, not an octopus, and is not a realistic tool. At least the turtle is pretty useful.

I'm not sure if my reply is still relavent to a discussion several years old, but this loks similar to "Idea Mapping", which is based on "Mind Mapping".

There are a number of books on the subject. It is a visual means of displaying information in a more meaningful way.

The book enetitled; "Idea Mapping" teaches how to do this and why benficial. I have personally been using this system and has been helpful in keeping organized.