Siloed Training Records Integrated with MES for Automated Skill-Based Dispatch in Food Processing

Overview

A food processor risked assigning operators to restricted tasks because certification and training records lived only in Human Resources. Supervisors relied on spreadsheets and radio calls to verify qualifications, and the Manufacturing Execution System (MES) could not block work when a certification lapsed. Intelligex integrated the Human Resources Information System (HRIS) and Learning Management System (LMS) with MES and the Quality Management System (QMS) to enable skill-based dispatch, enforce gates for restricted steps, and log exceptions with e-signatures. Work stayed compliant, line starts were smoother, and supervisors spent less time cross-checking credentials.

Client Profile

• Industry: Food processing and packaging
• Company size (range): Multi-plant operation with rotating shifts
• Stage: Established HRIS/LMS and MES; training records siloed in HR
• Department owner: Operations & Manufacturing
• Other stakeholders: Human Resources, Training/Learning & Development, Food Safety/FSQA, Quality Assurance, IT/OT Security, EHS, Labor Relations

The Challenge

Restricted tasks—such as allergen changeovers, metal detector verification, pasteurization checks, or powered industrial truck operation—required current training and certifications. Those records were maintained in HR and the LMS, while the floor relied on MES to schedule and execute work. The two worlds did not meet at the station. Supervisors cross-checked names against a spreadsheet or called HR to verify status, especially during shift changes, overtime, and temporary staffing. Mistakes slipped through when schedules changed quickly.

Operators moved between lines based on demand. A person qualified on one filler might not be cleared for another variant, or a certification might have expired overnight. The MES allowed sign-on without regard to training status, and the QMS only learned about gaps when a deviation was opened after the fact. Both Operations and HR wanted a reliable gate that respected privacy, kept the floor moving, and produced clean audit evidence that training and certification were enforced.

Constraints were practical. The organization could not replace its HRIS or MES. Access to employee data was governed by policy and collective bargaining agreements. IT required read-only, least-privilege integrations and did not want to introduce identity sprawl. Any solution had to reuse existing systems, be simple for operators, and avoid disrupting validated processes tied to food safety requirements in 21 CFR Part 117.

Why It Was Happening

Fragmentation and manual handoffs were the root causes. HR and the LMS held the authoritative record for what each person was trained to do and when that status expired. MES and scheduling knew who was on shift and what work needed to be done. Without a shared skill model and automated checks, supervisors became the bridge—printing rosters, maintaining spreadsheets, and making judgment calls under time pressure.

Ownership was diffuse. HR owned training validity, Operations owned assignment, Quality owned compliance outcomes, and IT owned the systems. Identity mismatches and contractor onboarding added complexity, with duplicate IDs and slow updates when roles changed. The last mile had no enforcement: even when training lapsed, the system did not stop an operator from starting a restricted task.

The Solution

Intelligex implemented a skill-based dispatch layer that synchronized training and certification status from HRIS/LMS into MES, enforced station and task gates, and recorded exceptions in the QMS. The approach mapped employees to roles, stations, and restricted tasks; pushed eligibility flags to MES sign-on and job start; and routed any override through a documented approval flow. The result was a controlled handoff from HR to Operations that worked with existing tools.

• Integrations: Pulled employee status and training completions from HRIS/LMS platforms such as Workday, SAP SuccessFactors, or UKG; synchronized shift rosters from workforce management; enforced sign-on and job start in MES (e.g., Siemens Opcenter, Rockwell FactoryTalk ProductionCentre, SAP ME); and logged exceptions and deviations in the QMS (e.g., ETQ Reliance, MasterControl, TrackWise).
• Skill and certification model: Defined a canonical skill matrix tying roles, stations, and restricted tasks to required courses, assessments, and certification expirations. Included prerequisites and shadowing rules where applicable.
• Dispatch gating: MES blocked sign-on for restricted tasks without current training; presented qualified alternates; and allowed time-bound overrides with reason codes, supervisor approval, and Quality concurrence. All actions carried e-signatures and timestamps.
• Proactive alerts: Notified supervisors of upcoming expirations for rostered employees. Flagged shifts where planned assignments conflicted with eligibility, giving time to adjust before the line started.
• Privacy and security: Shared only minimum attributes (employee ID, role, site, skill flags, expiration dates) with MES; personal data remained in HRIS. Used single sign-on and least-privilege service accounts. Audit logs lived in the QMS and MES.
• Compliance alignment: Structured records supported training and qualification expectations under 21 CFR Part 117, which emphasizes personnel training and documented practices for human food.

Implementation

• Discovery: Mapped restricted tasks by asset and process step, reviewed training curricula and certification rules, and inventoried identity sources for employees and contractors. Documented current sign-on practices and common exceptions that led to deviations.
• Design: Defined the skill matrix and data contracts among HRIS/LMS, scheduling, MES, and QMS. Set gating points (log-in, job start, critical steps), exception paths with required approvals, and e-signature requirements. Established privacy constraints and audit fields.
• Build: Configured HRIS/LMS feeds to publish eligibility updates, built the MES gate logic and station prompts, and implemented QMS records for overrides and deviations. Set up roster-based alerts and dashboards for supervisors and FSQA.
• Testing/QA: Ran in shadow mode with real rosters, comparing gate decisions to supervisor verifications. Validated identity matching, expiration handling, and override flows. Human-in-the-loop reviews confirmed that gating aligned with procedures before enabling hard stops.
• Rollout: Enabled gating by area and task category, starting with allergen changeovers and critical control verifications. Kept manual cross-checks as a controlled fallback until confidence was established. No changes were made to core HR or MES interfaces beyond approved connectors.
• Training/hand-off: Delivered role-based sessions for supervisors, schedulers, and operators focused on sign-on prompts, alternates, and override policies. Updated SOPs and transferred ownership of the skill matrix to HR and Training under change control.

Results

Assignments lined up with qualifications by default. Operators were routed to tasks they were cleared to perform, and restricted steps prompted for the right credentials. Supervisors spent less time chasing spreadsheets and more time managing the plan. When an exception was necessary, it was documented with clear approvals, reason codes, and follow-up actions in the QMS.

Compliance became easier to demonstrate. Auditors saw a consistent record that linked training status to station sign-on and critical steps. The MES prevented starts when training lapsed, and proactive alerts gave teams time to adjust rosters. Food safety and quality leaders gained confidence that personnel controls were enforced in the workflow, not reconstructed after the fact.

What Changed for the Team

• Before: Supervisors checked spreadsheets and called HR. After: MES sign-on and job start enforced eligibility automatically.
• Before: Operators could start restricted tasks with lapsed training. After: Gating blocked starts and suggested qualified alternates.
• Before: Exceptions were informal. After: Overrides required e-signatures with reason codes and Quality concurrence.
• Before: Training gaps surfaced during audits. After: Expirations triggered alerts ahead of the shift.
• Before: HR held the records; the floor guessed. After: HR remained the system of record, and MES consumed governed eligibility flags.
• Before: Deviations lacked clear cause. After: QMS captured decisions and evidence tied to each assignment.

Key Takeaways

• Bring training and certification signals from HRIS/LMS into MES so dispatch reflects reality at the station.
• Block restricted tasks by default and provide a governed override; compliance improves when controls live in the workflow.
• Use a shared skill matrix across HR, Operations, and Quality; clear definitions prevent inconsistent judgments.
• Alert on expirations and conflicts before the shift; prevention is easier than mid-run corrections.
• Respect privacy: sync only eligibility and identifiers, not full personnel files, and keep audit trails in governed systems.
• Integrate, don’t replace: reuse HRIS, MES, and QMS, and add the gating and logging that ties them together.

FAQ

What tools did this integrate with? The solution pulled training and certification status from HRIS/LMS platforms such as Workday, SAP SuccessFactors, or UKG. It synchronized rosters from workforce management and enforced sign-on and job start in MES systems like Siemens Opcenter, Rockwell FactoryTalk ProductionCentre, or SAP ME. Overrides and deviations were logged in the QMS (for example, ETQ Reliance, MasterControl, or TrackWise). Alerts and dashboards surfaced in Microsoft Teams or existing supervisor portals.

How did you handle quality control and governance? Restricted tasks were mapped to required training and certifications in a controlled skill matrix. MES enforced gates with e-signatures and reason codes for exceptions. All overrides created QMS records with audit trails and, when needed, triggered corrective actions. The approach supported training documentation expectations under 21 CFR Part 117, and changes followed site validation and change control.

How did you roll this out without disruption? Gating ran in shadow mode first, showing supervisors what would have been blocked while the legacy process continued. After confirming accuracy, hard stops were enabled for selected tasks and areas, with manual checks kept as a controlled fallback during early cycles. Operators did not learn a new system; they saw clear prompts inside the MES sign-on and job start screens.

How was employee privacy protected? Only the minimum necessary data flowed from HRIS/LMS: unique employee identifiers, site and role, skill flags, and expiration dates. No compensation or sensitive personal details were shared with MES. Access used single sign-on and least-privilege service accounts, and all eligibility data changes were audited. HR remained the system of record.

How did you handle contractors and temporary staff? Contractors were provisioned in HRIS or an approved vendor system with unique IDs and required training records. The same skill matrix and gates applied. Deprovisioning disabled MES sign-on automatically at contract end, and any exception required the same e-signature approvals and QMS logging as for employees.