Scheduling of 100% availability
This is feature is included in RS Production OEE.
For both OEE-measurement and downtime follow-up, scheduling is a central function. Scheduling is what you use to define maximum available time (100% Availability). All stops in scheduled time will be recorded in the downtime follow-up. For this reason, the scheduler is configured with the uptime planned for the machine.
Once a machine is scheduled, all stops will affect the scheduled time and will be counted as losses.
Be opting for a reason code to be excluded from OEE, the stop time will be outside the OEE calculation, but the stop will still appear in the stop reports.
Be opting for a reason code to be excluded from a schedule, the stop time will be outside the OEE calculation and the stop will also not appear in the stop reports.
Both exclude from OEE and exclude from schedule are set on the reason code.
By adding breaks to a schedule, you create planned holes in the scheduling that reduce the requirement for 100% available time. Stops during breaks will not be included in the stop follow-up and will not reduce the OEE-value.
Here is a brief glossary for scheduling
Term | Meaning |
Shift schedule template | A description of a cyclically recurring shift pattern that is often one or a few weeks long. If you make a change in the template, the change is not made in all the shift schedules pasted in previously, but only those that will be pasted in future. |
Shift schedule | An instance (pasted copy) of a schedule template. |
Shift | A working day for a shift team (e.g. 06:00 to 14:00) |
Shift team | A way of grouping the shift for follow-up (e.g. Morning, Afternoon ...) |
Break | Breaks split up a shift into multiple shift periods. OEE and stop time are not counted during breaks. |
Day split | Using the day split, for each shift you can mark which weekday it belongs to. In reports and analyses you will then get information per production day instead of per calendar day (00:00 to 00:00). |
Scheduling is often based on cyclically recurring patterns that are repeated an equal number of weeks. By setting up a shift schedule template that describes the shift pattern, you can later get the template to repeat itself on its own.
Here is a guide to creating a shift template that is automatically repeated.
Enter the main Production menu and then
Scheduling
When the scheduler opens, click on
the Shift schedule templates tab to open a table with all schedule templates
Click on the
Create button to open the guide for adding a new schedule template
a. Give the schedule template a name that is an accurate description of its length and the shift arrangement (e.g. triple shift with permanent nights).
b. Specify the template’s length in number of days (e.g. 14 or 21 days). This can always be altered afterwards.
c. Select the first day in the week by clicking on the ... button. Read more below on how automatic duplication of schedule templates is affected by the first weekday.
d. Give the schedule template a colour to visualize it in the user interface.
e. Click on Save and close
f. Now the shift schedule template has been created and is in the table of shift schedule templates, but it still does not contain any shifts.
Highlight the newly created shift schedule template and click
Open to start adding shifts.
Click
Create and select Shift in the dropdown menu to add a new shift.
Field | Meaning |
Shift type | E.g. morning, afternoon. Relates to the time of day. |
Shift team | E.g. Team 1. Relates to the group in question. |
Interval start | Time of start of shift. Note that the time 1000-01-01 00:00 is midnight of the first day in the shift schedule template |
Interval end | Time of end of shift. |
Weekday | The day to which the shift is assigned when day split is used. |
Remember not to enter a split for breaks. Use the break function or exclude from OEE to add breaks if the time is not to impact negatively on OEE.
Repeat point 5 until all shifts in the schedule template have been created
Repeat point 5, but select
Break instead of Shift to add breaks as well
Set the new shift schedule template as a standard schedule for the measure point by opening the
Measure point’s object card (Measure points/Machines) and open the measure point(s) that is/are to use the schedule template as a standard template. Click on the tab Standard values and select Standard schedule from the list. To gain access to this function, the user logged in must belong to the “Superuser” user group.
To automatically copy in a new schedule, the scheduler asks the following questions each day:
Is there a schedule set up for tomorrow?
If the answer is No, it asks the next question. Has this measure point a standard schedule set up for it?
If the answer is Yes, it automatically pastes in a copy of a standard shift schedule template and creates the shifts it contains.
If there is a schedule that has been entered manually, automatic scheduling will not run.
Quite frequently you will not know in advance when you are going to run e.g. overtime or over a weekend. You can therefore change the scheduling afterwards and get the correct figures in reports and analyses. Stop reason coding in Operator Tools also functions during the time you run “outside schedule”, although the stop rows are behind a semi-transparent layer to show that there is no schedule.
Here is a guide to how to add a shift afterwards.
Enter the main Production menu and then
Scheduling
When the scheduler opens, click on
the Shift list tab to open a table with all planned shifts
Click on the
Create button to add a new shift that is not included in the schedule templates.
By clicking on a shift in the timeline in Reports and analyses/Standard reports or Current situation/Timeline, you can adjust the start and end time of a shift afterwards. Please note that it is only the start and end time of the shift that is adjusted. Time stamps for produced amount, scrapped amount, stops etc. will not be changed.
At the moment there is a memory leak in the scheduler, which means that you have to restart Office tools after working with scheduling for a certain time. Otherwise there is a risk of program response slowing down.