Up-to-date OEE reports via the Split & Insert Procedure
Today I'll be addressing an other function of ProMISe that supports a clean desk policy within your operations.
There are situations where parts of your process are not running during elongated periods.
At the start of such a period ProMISe can receive an incoming alarm event, but the going alarm event can come many hours, in specific cases even many days, later.
Awaiting the going event, ProMISe shows, in the registration module, the number of ongoing alarms with this spinning wheel icon.
If you click this icon, a dialog with all ongoing event will be shown.
One of the options is the split and insert option.
Image you as operator already know that one of the ongoing alarm will last past the end of your shift. For example due to maintenance work being done.
Now you could simply pass this ongoing alarm onto your successor by writing a message, something like the root-cause of the downtime, via the comment icon.
See the video linked here above to see how that works.
However, since, at the end of your shift, this will still be an open alarm, this downtime will not be accounted for in your OEE reporting. Hence on closure of your shift, only an incomplete OEE report can be shown. A situation that in some industries can last for days.
To enable ProMISe to take that downtime into account in the OEE reports, you can split the ongoing alarm and eject a forced alarm going event in the future.
Here is how to do this.
In the ongoing alarm dialog select the event you would like to split. Click the split and insert icon. A new dialog comes up where you can provide ProMISe with an end time for this event. Presumably the end time of your shift.
Then fill in the comment that is placed by the alarm that you are providing with the future end-time.
Next you can provide a comment for your successor that will be confronted with the alarm to inform them about the root-cause.
Split the ongoing event by clicking this button.
ProMISe will now close the dialog and scroll towards your modified event, still colored red, where you van process the event as any other alarm in ProMISe.
What just happend I will try to visualize with help of a small animation.
At a given time an upcoming alarm is received by ProMISe, indicated by the red arrow coming down. From that moment on ProMISe keeps track of the ongoing alarm.
Somewhere during that period an operator opens the ongoing event and fills in the end of his shift, in the animation represented by the yellow dashed line, (or any other future moment in time, as you like). The action of the operator is represented in this animation by the blue arrow.
As soon as the operator compleets the split and insert procedure, a complete alarm is generated to be edited, and a next ongoing event is created that starts at the end time of the initial event. After processing the alarm the event will now be taken into account in an OEE report.
Some time in the future the going alarm message will be received by ProMISe and then an Alarm will be generated with the duration between the split moment (the dashed yellow line) and the moment the going alarm message came in. Represented by the green arrow.
If the newly generated event lasts even past the next shift exchange, you are free the apply the split and insert procedure again, als often as needed.
https://www.optimizeyourprocess.com
00:00 Introduction
00:14 The case
00:36 The explainer
02:07 How to
03:03 Need to know!