Does anyone use the 'Reason' field?

Comments

7 comments

  • Official comment
    Suomala, Kyle

    Hi Dave,

    We use reason codes at our facility and they work well for us. It helps us out a lot when we look at our reports and also makes it easy for the people who are creating alerts to select from a drop down list of why they are having an issue. We also have our reason codes set up so they correspond with the proper dispatch type. For example, if they select "IT" as the dispatch type, they will only see "computer issue" as a reason code. Conversely, if they select "Manufacturing Engineering" for the dispatch type, they will not see "computer issue" but instead they will see "BOM issue", "Routing issue", etc. One thing to note, if you set your system up to have specialized reason codes for each dispatch, there is potential to lose the reason code if someone changes the dispatch type. For example, if someone were to create a dispatch for "IT" with a reason code "computer issue" and then the dispatch was later changed to "Manufacturing Engineering" it would then have a blank reason code because "Manufacturing Engineering" was never set up to have a "computer issue" code. Overall, the reason codes are very beneficial and I recommend you explore this option based on your current situation. I hope this helps.

    Kyle

    Originally answered Apr 22, 2015 at 2:26 pm

    Comment actions Permalink
  • Holman, Nathaniel J

    I agree I have had the reason codes set up since day one of launch and for reporting services it is such a benefit to be able to break down our downtime to the next level and be able to focus on specific issues. The biggest issue I have had with it is getting the people on the floor to remember to use that field. I think that will come with time and more familiarity with what we are doing with the information.

    Originally answered Apr 22, 2015 at 2:33 pm

    0
    Comment actions Permalink
  • Thomas, Barry

    Hello Dave We have been using Reason Codes at our facility for about a year and a half and we find it beneficial. I set up Reason Codes initially on our Production Module to eliminate the paper work and be able to categorize downtime reasons on a Pareto. We took the Downtime codes from the Operators paperwork and created the reason codes by machine. When the Operator launches an Operator Fix they select the Reason Code as the Downtime type. Reason codes include for us( Material Stockout, Meeting, Changeover, Conveyor Jam, etc..) This has allowed us to standardize the Nomenclature and look for repetetive issues. I am now in process of applying this to the Dispatch side. Barry

    Originally answered Apr 22, 2015 at 2:40 pm

    0
    Comment actions Permalink
  • Ginnow, David

    We don't use the Operator Portal. But, do you feel it would be beneficial for the "Reason" field to be visible in the "Create Dispatch" area on the main dispatch screen (for Resources and Admins) so those users can use it as well? Seems strange that it would be an option in the Operator Portal but not for the dispatcher... No?
    I did notice that even when selecting a 'Reason', the system still forces a 'Description'. That seems unnecessary. You should be able to supplement a reason with a comment, but a Reason should be able to stand alone. Thoughts?

    Originally answered Apr 22, 2015 at 3:23 pm

    0
    Comment actions Permalink
  • Holman, Nathaniel J

    I can see how it would seem redundant to have both reason and description. We put very very detailed descriptions in our dispatches to the point of what die number we have issues with what particular part of the machine is malfunctioning. The way I look at reason codes is more if you ran a report of code red instances everything is lumped into one big block which is useful as an overall but you want to see things broke down into more categories. Mechanical failure quality issues no parts Etc. Then once you break it down to that level you can see the history detail for that reason and be even more specific by reading the descriptions.

    Originally answered Apr 22, 2015 at 3:29 pm

    0
    Comment actions Permalink
  • Ginnow, David

    Nate, do you not use the 'Tooling' field for keeping track of which die is in a machine? Also, when I setup our area, our overall "machine" is actually the 'Line'. Our machine is made up of about 2 dozen different stations. Those stations are our 'Machines'. The terminology took a little getting used to, but people get it now. Being setup this way, when I search Cod Red's for a particular cell and machine combination, I'm drilled down pretty far already. Although, I like your idea of the reasons being general buckets like 'Mechanical Failure', 'Quality Issue', etc. I don't know why, but I had never thought to use Dispatch to track when an operator is waiting for parts. That'll be useful - thanks! :)

    Originally answered Apr 22, 2015 at 3:40 pm

    0
    Comment actions Permalink
  • Holman, Nathaniel J

    We are using the tooling field a bit but not to much. I have a line set up for die repair to track which dies are being repaired the most to test that out. Issue is at our facility we have right around 800 different dies so its something I'm gradually playing with. We have been rearranging our "lines" if you will in the system for a bit now. Most areas we have the line concept works pretty well but for our casting and aluminum machining department that runs 10-15 models on the same line at the same time its getting fairly muddied up to separate that data.

    Also senior management here made a big push to me to hold our materials group a bit more responsible for not getting parts or clearing full containers from the line on time so we started tracking that awhile ago I was actually shocked on the results from that

    Originally answered Apr 22, 2015 at 3:47 pm

    0
    Comment actions Permalink

Please sign in to leave a comment.