Jones, Carl
My feedback
21 results found
-
4 votes
An error occurred while saving the comment Jones, Carl supported this idea · -
2 votes
An error occurred while saving the comment Jones, Carl commentedWhen technicians are putting labor stamps into jobs, if they don't do it exactly in order (Date, then hours, then minutes, then AM/PM) it resets the entire field. Can the development team change it to not reset? Would help our technicians a lot.When technicians are putting labor stamps into jobs, if they don't do it exactly in order (Date, then hours, then minutes, then AM/PM) it resets the entire field. Can the development team change it to not reset? Would help our technicians a lot.
Jones, Carl supported this idea · -
1 voteJones, Carl shared this idea ·
-
8 votesJones, Carl shared this idea ·
-
8 votesJones, Carl supported this idea ·
-
13 votesJones, Carl supported this idea ·
-
5 votes
After further review with the site, it seems there is a little confusion on this request.
"Operator error" the Operator causes the problem. "Operator performed maintenance" the Operator fixes the problem. The site is trying to use the sub-types to distinguish between who is responsible for resolving an issue and any extended downtime that occurred.
An example of "operator performed maintenance" 3rd shift operator has a non-maintenance machine issue related to training or experience that prevents running the machine. So, the machine sits idle with a down work order submitted. 1st shift operator arrives and being more experienced is able to fix the issue and begins running the machine.
This functionality will also be useful as our Operator-Performed Maintenance (OPM) program continues to grow within ATS. I am reopening the request to discuss further with our teams.
Jones, Carl shared this idea · -
21 votesJones, Carl supported this idea ·
-
2 votesJones, Carl supported this idea ·
-
12 votesJones, Carl supported this idea ·
-
1 vote
An error occurred while saving the comment Jones, Carl commentedThis is a bad idea in my humble opinion, priority 1 schedule breaks should be the exception not the rule.
-
1 voteJones, Carl shared this idea ·
-
11 votesJones, Carl supported this idea ·
-
5 votesJones, Carl supported this idea ·
-
5 votesJones, Carl supported this idea ·
-
10 votesJones, Carl supported this idea ·
-
2 votesJones, Carl supported this idea ·
-
1 voteJones, Carl shared this idea ·
-
4 votesJones, Carl shared this idea ·
-
5 votesJones, Carl shared this idea ·
When technicians are putting labor stamps into jobs, if they don't do it exactly in order (Date, then hours, then minutes, then AM/PM) it resets the entire field. Can the development team change it to not reset? Would help our technicians a lot.