Labor shift template not assigning workers to correct shifts after template update

MES Honeywell MES
, , , , , , , ,
1

We updated our labor shift template last week to accommodate a new 4-crew rotation schedule. Since then, workers are being assigned to the wrong shifts consistently. Day shift workers are showing up on the night shift roster, and some skilled operators are being assigned to roles they’re not qualified for.

I’ve checked the shift block time ranges in the template - they look correct (Day: 06:00-14:00, Evening: 14:00-22:00, Night: 22:00-06:00). The role-to-shift mapping seems fine too. I tried an assignment cache refresh from the Labor Management console, but workers are still misassigned when the daily schedule generates.

The weird part is that manual shift assignments work perfectly - it’s only the automatic template-based assignments that are wrong. Running HM 2023.2 with the latest patch. Anyone dealt with this?

2

You’re absolutely right - both templates are active! The old one has priority 10, and I didn’t set a priority for the new one, so it defaulted to priority 5. Lower number means higher priority, right? So the old template is winning. But why are workers ending up in wrong roles? That seems like more than just a priority issue.

3

The role misassignment is probably due to role-to-shift mapping differences between your templates. If the old template maps “Operator-A” to Day shift and the new one maps it to Evening shift, workers with that role will bounce between shifts depending on which template executes first. This gets worse when combined with overlapping time ranges. You might also have a cache issue where old mappings are stuck in memory even after template changes.

4

Templates don’t auto-deactivate. You need to explicitly disable or delete old templates, otherwise they remain active and compete with new ones. Check your Labor Management > Shift Templates screen - I bet you’ll see both the old 3-crew and new 4-crew templates marked as active. That would explain the random assignments - the system is bouncing between both templates based on internal priority rules you can’t see.

5

Let me walk you through the complete fix for this situation, addressing all three key areas:

1. Shift Block Time Ranges - Verify Boundaries: Your time ranges look correct, but check for gaps or overlaps:

<ShiftBlock id="DAY" start="06:00:00" end="14:00:00"/>
<ShiftBlock id="EVENING" start="14:00:00" end="22:00:00"/>
<ShiftBlock id="NIGHT" start="22:00:00" end="06:00:00"/>

Note: Night shift crosses midnight. Ensure your template handles the date boundary correctly with crossesMidnight="true" attribute.

2. Role-to-Shift Mapping - Fix Conflicts: This is likely your main issue. When you have multiple active templates with different role mappings, workers get assigned based on whichever template processes first. Here’s what you need to do:

a) Deactivate the old template immediately:

  • Go to Labor Management > Shift Templates
  • Find your old 3-crew template
  • Set Status = “Inactive” or delete it entirely
  • Don’t just rely on priorities - remove the conflict source

b) Verify role mappings in your new 4-crew template:

Check that each role maps to exactly ONE shift per crew rotation:

<RoleMapping role="OPERATOR_A" crew="1" shift="DAY"/>
<RoleMapping role="OPERATOR_A" crew="2" shift="EVENING"/>
<RoleMapping role="OPERATOR_A" crew="3" shift="NIGHT"/>
<RoleMapping role="OPERATOR_A" crew="4" shift="DAY"/>

c) Check qualification requirements:

If operators are being assigned to unqualified roles, your template might be missing skill validation:

<RoleMapping role="SKILLED_OPERATOR" requiresQualification="true">
  <RequiredSkill>ADVANCED_MACHINING</RequiredSkill>
</RoleMapping>

3. Assignment Cache Refresh - Complete Process: The Labor Management console cache refresh isn’t always sufficient. You need a full cache clear:

a) Server-side cache clear:

  • Stop the Labor Management service
  • Clear the assignment cache directory: `[MES_Install]\Cache\LaborAssignments\
  • Restart the service

b) Database-level cache clear (if server cache doesn’t work):

DELETE FROM LM_SHIFT_ASSIGNMENT_CACHE WHERE assignment_date >= '2025-01-08';
DELETE FROM LM_TEMPLATE_CACHE;

Then restart Labor Management service

c) Regenerate assignments:

  • Go to Labor Management > Schedule Generation
  • Select date range from when you made the template change forward
  • Click “Regenerate Assignments”
  • This forces recalculation using the correct (and now only active) template

Priority Configuration (for future reference): Since you asked: Lower number = Higher priority in HM 2023.2

  • Priority 1 = Highest (overrides everything)
  • Priority 10 = Lower priority
  • Priority 0 or null = Lowest (default)

Set your new 4-crew template to priority 1 to ensure it always wins, but honestly, just deactivate the old template instead.

Validation Steps:

  1. Confirm only ONE active shift template exists
  2. Verify role mappings don’t have duplicates or conflicts
  3. Check that shift time blocks don’t overlap (except at boundaries)
  4. Test with a single crew for one day before rolling out to all crews
  5. Monitor the assignment log (LaborAssignment.log) for any warnings

Why Manual Assignments Work: Manual assignments bypass the template engine entirely - they write directly to the assignment table. That’s why they work correctly while template-based assignments fail. This confirms your issue is 100% in the template configuration, not in the core assignment logic.

Follow this process and your shift assignments should stabilize immediately. The key is removing the old template and doing a complete cache clear, not just a console refresh.

6

This sounds like a template priority conflict. When you created the new 4-crew rotation, did you assign priority levels to each shift template? If multiple templates match the same time window, MES uses priority to decide which one applies. Without explicit priorities, it defaults to the oldest template, which might be your old 3-crew rotation.