Defining Shifts using the Ignition Schedule Manager
- Shifts that do not cross midnight should always work exactly.
- For shifts that cross midnight, we will consider the start of the shift segment which occurs after the largest gap in the schedule to be the start of the shift. The end of the shift segment preceding the largest gap will be used for the end of the shift.
- In the unlikely case that all gaps are of the same size, we will consider the start of the shift segment which occurs after the final gap in the schedule to be the start of the shift. The end of the shift segment preceding the final gap will be be used for the end of the shift.
- The MES modules will pull updated information from the Ignition schedules every hour. This means, for example, that if an Ignition schedule is changed at 8:30 AM, the MES modules will not see the changes until 9:00 AM.
- To force the MES modules to pull the newest information from the Ignition schedules for a piece of equipment, the system.mes.synchronizeIgnitionSchedules() and system.mes.synchronizeIgnitionSchedulesForEquipment(equipmentPath) scripting functions can be used.
If shifts are defined by using Ignition Schedule Management Component, enabled shifts can be defined for each production line in the Schedules menu of the OEE Equipment Manager component as shown below.
OEE Equipment Manager
You can select valid shifts by checking the corresponding box. When implementing shift management this way, leave shift tag collectors at the line and cell level in production model blank. If requiring a custom implementation, use the shift tag collectors in the production model designer to define the current Shift.
Ignition Schedule Manager Component
Defining Shift using the Shift Tag Collector
If you choose not to use the Ignition Schedule Management component, you can simply define the current shift by writing to the Shift Tag Collector provided in the production model for the line whenever the shift changes. Refer to Shift Tag Collector for more details.