bruce huff
My feedback
5 results found
-
7 votes
An error occurred while saving the comment An error occurred while saving the comment bruce huff
commented
This also poses a problem with the customer perception of the ATS team. Currently, the process is to cancel the WO with notes referencing the newly created, corrected WO. However, this notifies the customer of WO completion without notifying them when the actual, corrected, WO is completed. This gives the perception of pencil-whipping, completing WOs without actually completing the work. There are no systematic accountability measures to prevent these WOs from being cancelled and never followed up on.
bruce huff
supported this idea
·
-
5 votes
An error occurred while saving the comment bruce huff
commented
This would help assist in validating/justifying when to Repair vs Replace or vice-a-versa
bruce huff
supported this idea
·
-
19 votesbruce huff
shared this idea
·
-
5 votesunder review ·
AdminMichelle Oldfield
(Business Analyst, Advanced Technology Services, Inc.)
responded
Thank you for your feedback! Our Power BI analyst team is looking at your suggestion and determining how we could implement this.
An error occurred while saving the comment bruce huff
commented
This is more important now than ever as RCA tracking has become part of the FMS OS maturity. This could also be done in eFP as a tag to a WO that meets customizable RCA triggers (similar to the escalation feature in the control panel).
bruce huff
supported this idea
·
-
21 votes
An error occurred while saving the comment bruce huff
commented
This will also help design and strategically target improvement activities. It is easier to click a button than rely on technician notes for specific problems (ex. identifying an issue with the entry conveyor of the machine vs a function part of the machine)
bruce huff
supported this idea
·
+4 votes in reference UserVoice linked here https://uservoice.advancedtech.com/forums/348516-efactorypro-3-0/suggestions/46987498-change-mrct-wo-task-type-to-pr