Machine Downtime reporting

MPath

Hi smarties,

Thought I ask you for a bit of help, since I can not get any good idea on how to tackle my idea/request.

I want to make a sheet with a form attached where I can have operators report downtime. The issue I have is that I want them to report the date and time of a breakdown and then when resuming work on the machine, report the date and time they are commencing their work.

It's basicly 5 pressbrakes where I want them (and so would they) to report on: when (date) at what time (time) did what machine breakdown (dropdown selection) and why (Dropdown selection) and who reported (Textfield)

And then when commencing working on the machine (can be an hour, could be weeks, even months) report the machine back on-line.

Ofcourse, I would like to be able to gather usefull data of it on a daily/weekly/monthly/X basis.

Any thoughts? Not looking on a easy way out because I'm lazy, just haven't got a clue on how to do so.

Thanks for any hints beforehand!

Greetings,

Maurice

Kerry St. Thomas

If you don't have Machine ID's, institute that first. Get people fluent with referring consistently to "Machine 3" instead of "The red one in the corner by Jim's station." You can then create a sheet (and from that, a form) that collects Machine ID (as a dropdown), the event (Stop work, resume work), Date & time dropdowns as you mention above, and any other required elements for your Quality Management documentation. (YOU CAN set up a form so that it captures the login for the person filling out the form; if you use that, you don't need to ask their name because you'll already have identifying information).

You'll be able to use things like the Created Date timestamp along with MAX to flag those individual rows with the current status of each machine. Pivot App or Reports (with grouping and summary functionality) can be used to show a history of any given machine; Dashboards can be based on either of these to show the information you are collecting, based on the specific business case you have for display and consumption of the data.

The sky's really the limit on this one - my biggest suggestion is to start sketching out exactly what data your leadership will need to consume on a periodic basis (and what that update cadence will be) - when you know what they'll need to see, you'll know what the form should really be. Starting at the end and working your way backward might seem counterintuitive, but if you have your end goal in mind for your entire build project (UP TO AND INCLUDING AN ACTUAL DRAWING OF A DASHBOARD) you'll be able to look at the individual steps you need to take in order to show that data (e.g. ensuring you collect the correct data points, you know what formulas you'll need to write, and so on).

Good luck!