Skip to main content

I have 7 different Machines on my shop floor.

 

My operators who run these machines are not allowed phones on the floor. They also don’t have company email addresses. Each machine has a windows workstation.

Their team leaders do (have company phones & emails & have the MaintainX app), but are not always at the machine.

At the min, if my machine operators have a breakdown or issue, they say to my engineers - then if my engineer remembers, he will log the ticket.

 

To get around it on a Test machine. I’ve signed up for a requestor account called the machine name using a disposable email address. Then they use the browser on the machine to raise a WO/Ticket.

 

I want to get away from my engineers doing jobs without a record. So I was going to tell my operators to raise a ticket 1st - I was also going to tell my engineers not to do any jobs that don’t have a ticket.

 

How do you do this?

Hi ​@Shay, 

I agree that encouraging the team not to do undocumented work is good practice in general. Relying on someone’s memory is a surefire path to chaos during unplanned breakdowns, especially if that person isn’t on shift!

Have you tried using the work request portal feature (Settings > Features > Request Portals)? It generates a web link that anyone can use to submit work requests, without any kind of MaintainX account or even email, if you set it up correctly. Once you have the portal set up, you can save it on the workstation’s browser bookmarks or save the shortcut to the desktop for easy access.

Setting guidelines for what does and doesn’t need a request can be helpful as this removes some of the ambiguity from the process. Operators and engineers both tend to work best with clear instructions available and plenty of machine issues probably won’t need to be addressed formally (eg. machine was off from planned shutdown, need to turn it on). I find a good rule of thumb is if it takes less than 5 minutes, doesn’t require tools, and doesn’t change machine settings/operation, then it probably doesn’t need a work order.

Setting rewards and publicizing successes using work order count can be good motivation tools to help the team to ensure their work is recorded.

Hope this helps. Let me know if you need any assistance setting up the request portal. 🙂

Reply


Terms & ConditionsCookie settings