Difference between revisions of "Process troubleshooting - 2012"

From Engineering Economics and Problem Solving: 4N4
Jump to navigation Jump to search
m
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Course material ==
__NOTOC__{{ClassSidebar
 
| date = 15 and 16 November
Please bring the notes from tab 6 in your binder.
| dates_alt_text =  
 
| vimeoID1 = 53621739
== Troubleshooting tutorial ==
| vimeoID2 = 53708417
 
| vimeoID3 =
There are 3 roles in the tutorial
| vimeoID4 =
 
| vimeoID5 =
[[Image:Triad-Troubleshooting.jpg|800px]]''click for larger version''
| vimeoID6 =
 
| vimeoID7 =
 
| vimeoID8 =
==== Observer ====
| vimeoID9 =
 
| vimeoID10 =
As the Troubleshooter is tackling the problem, your task is to assess how well the problem solving components are handled. This is challenging because the skills are difficult to identify let alone observe and assess. The evaluation sheet is made to help you look at the mental process used by the trouble shooter. Try to focus more on the "types of questions asked", and " how can I create a hypothesis and test it?" and not on "what information do I need?" or on "what action should I take?". Look at the organizational pattern used; listen for the monitoring of the process.
| course_notes_PDF =
Consider, "does he/she confuse activities unknowingly?"
| course_notes_alt = Course notes
 
| overheads_PDF =
Let the Expert System focus on "how well the trouble shooter wrote out the questions and tasks to be done".  
| assignment_instructions =
 
| assignment_solutions =
 
| video_download_link_MP4 = http://learnche.mcmaster.ca/media/4N4-2012-11B.mp4
====Expert System====
| video_download_link_MP4_size = 115M
 
| video_notes1 =
You will have received a binder before the tutorial, read over this background material. Understand the process extremely well. Think about how "the fault" will affect all of the process variables. Try to anticipate the kinds of questions that the Troubleshooter might ask; or experiments that he/she might ask to be performed. What would the fault do to the system under those conditions? Give results of experiments. '''Do not give explanations'''. Give correct information but do not be generous. If, for example, the fault occurs periodically, and you are asked to give the lab analysis for one sample taken: assume Murphy's law applies and give them the result when the system was operating normally.
| video_download_link2_MP4 = http://learnche.mcmaster.ca/media/4N4-2012-11C.mp4
 
| video_download_link2_MP4_size = 120M
Insist that they write out all requests; write down the results opposite. Do not talk..... just acknowledge that they are working on it by saying  "Ahemmm, mmmmm,"
| video_notes2 =
 
}}
Insist on their instructions, or requests be written precisely.
 
If they write, " Inspect the instrument" then respond "It's OK". If they ask what you did, then say "I went out and looked at it." Be tough. Do not offer more information than they asked for.
 
* Please do not share information about your case with anyone.
* '''Do not mark''' the stapled sheets in the folder; these folders are reused in future years and cost substantial time and money to prepare.
 
====Troubleshooter====
 
You have a challenging role to play.
 
You are to talk aloud so that the Observer can track what you are doing. Think about the process you will be using: are you searching for change or for hypotheses; whether you are clarifying the situation or testing an idea. You may feel frustrated because the Expert System is going to supply written responses to your requests; the Expert System will not discuss things with you. He/she may say "Hmmm" or "mmmmmm" to you occasionally so that you do not feel too much like talking to a wall but basically the Expert System is there to provide instant system written response to your requests.
 
You are to display all the good problem solving skills we have developed. Do this by verbally monitoring your progress, being active with pencil and paper to keep track of the route you are following,
 
You are to write out your requests for information from the Expert System. These should be written out precisely. A sample form is given below.


== Selected references ==
== Selected references ==
Line 59: Line 43:
|-
|-
|}
|}
== Class materials ==
* The slides are in [[Course_pack_for_2012 | tab 6 of the notes]].
* The [http://learnche.mcmaster.ca/media/mcmaster/4N04_TS_2012_VisualAids.pdf slides with full solutions].
* A [http://learnche.mcmaster.ca/media/mcmaster/Marlin--Troubleshooting-chapter.pdf complete chapter on troubleshooting]. All the details about the method. Please email Dr. Marlin any feedback on this document: he's working on an amazing book, and this is one of the chapters.
* The [[Media:Triads-Handout-2012.pdf | handout used for troubleshooting]] - bring this to the exam and keep it for the rest of your career.
=== 15 November 2012 (11B) ===
* Started the troubleshooting topic
* [http://learnche.mcmaster.ca/media/4N4-2012-Class-11B.mp3 Audio] and [http://learnche.mcmaster.ca/media/4N4-2012-11B.mp4 video] recording of the class
=== 16 November 2012 (11C) ===
* Completed most of the troubleshooting topic
* [http://learnche.mcmaster.ca/media/4N4-2012-Class-11C.mp3 Audio] and [http://learnche.mcmaster.ca/media/4N4-2012-11C.mp4 video] recording of the class

Latest revision as of 22:33, 2 December 2012

Class date(s): 15 and 16 November
Download video: Link [115M]
Download video: Link [120M]

Selected references

The following printed materials have influenced the course content. In alphabetical order:

Author(s) Title Library link Google search for ISBN Amazon link for ISBN
Woods Successful trouble shooting for process engineers McMaster Google Amazon

Class materials


15 November 2012 (11B)

  • Started the troubleshooting topic
  • Audio and video recording of the class

16 November 2012 (11C)

  • Completed most of the troubleshooting topic
  • Audio and video recording of the class
Retrieved from "https://learnche.org/wiki_4N4/index.php?title=Process_troubleshooting_-_2012&oldid=488"