One day in discussion with my boss, I was told one of eFlex's clients utilizing pencil and paper, and hourly manual inputs to record hourly production counts (e.g. good, rejects) on a clipboarded sheet of paper, in which then an anaylst once a week records all the manual inputs into the computer for operational anaylsis. My boss further explained our system already records this info. Tie it in with scheduling and we have it all right there on screen. No manual inputs. No paper. Add Business Intelligence (also at the time being developed) and the analysis is available realtime. Tie in operational buttons and we have a very useful OEE screen tied directly to and toggled from the current JEM station screen. With no more that that prodding, I designed the OEE screen.
OEE is tabulated by multiplying Availability x Performance x Quality. Or, another way of viewing it: OEE = (Good Count × Ideal Cycle Time) / Planned Production Time.
From a footer toggle button on JEM, the user quickly and easily accesses real-time OEE data for that station. To make this accurate, operational action buttons allowed the operator to specify a change: RUNNING, activated when operations are running properly. FAULTED, pushed when there is a machine breakdown. STARVED when the station runs out of needed parts or materials. BLOCKED activated when something up the line has stopped the process from moving forward. CHANGEOVER used when for a scheduled changeover or maintenance activity. And, lastly, BREAKS for any scheduled or unscheduled breaks. All this is tabulated in real-time, presented in actual time and an accumulated percentage of the shift.
Also, in this screen-view, I felt it helpful and useful to included a Parts Count/Target Amount display for quick reference, and possible future scheduling capabilities.
Soon after presented, and after some minor tweaks, development was immediately implemented. And soon after implemented, other requests were being considered and designed, including a direct link to the scheduling, and the ability for users to create their own custom, action buttons. The custom action buttons allowed the user to program easily accessed actions such as a maintenance call, a medical emergency, or for basic messaging.
To add a custom button or edit an existing button, click the "+" button. A configuration panel slides out allowing the user to assign the button color, its action, and association tags.
In addition, these actions can be directly tied into associated messaging (association tags easily allow this). For example, a maintenance call. The button is clicked, a modal pops up demanding a note be written and a type of call selected. This then sents an alert to the appropriate recipient—whether a direct person or a role notifying multiple persons—and the message added to a message monitor—accessible from anywhere.