Thread Content
The boss asked me to create a cause-and-effect diagram. Ahem, in our company, the cause-and-effect diagrams are created using process-related methods, while in my previous company they were created using instrumentation-related methods. . . So I’d like to ask fellow netizens, what should be kept in mind when creating causal diagrams?~
For fishbone diagrams, in the past, to create them one just needed to use a factor analysis table
Go away, the factors of man, machine, material, method, and environment – I use fishbone diagrams when teaching others. It’s not this.
Here, we first create tables and then charts; we divide things into two levels – human unsafe behaviors and unsafe conditions of objects – and then analyze them one by one, which we call “why, why analysis”. I’m not sure if it’s the same thing I’m telling you
Find a master to take a look for you – is it a logical cause-and-effect diagram? First, make assumptions; then find solutions. That’s how it is. Even the most talented people have to admit that a fishbone diagram is a type of cause-and-effect diagram – multiple factors lead to a certain outcome. If only process factors are considered, then various process conditions need to be assumed in order to determine the expected outcome. This depends on one’s experience; the more experience one has, the easier it becomes. Those with little experience can only rely on assumptions.
Causal graph? Is it a logic diagram? I think the process should take the lead, with the instruments playing a supporting role. Only after the process generates a rough logic diagram can the instruments be modified based on the interlock conditions. Below is the logic interlock diagram of our company that I created; the instruments have their DCS interlock settings based on this diagram.