Inconsistent Shift Handover Logs Fixed by MES and CMMS-Integrated Digital Logbook, Improving Workflow Coordination

Overview

A multi-site operation struggled with shift handovers that depended on notebooks, spreadsheets, and memory. Critical events and alarms were recapped differently by each crew, open actions fell through the cracks, and recurring issues stayed invisible across sites. Intelligex implemented a structured digital logbook integrated with the existing Manufacturing Execution System (MES) and Computerized Maintenance Management System (CMMS). The logbook captured key events, production context, alarms, and open actions with role-based signoffs, and analytics highlighted patterns by line, shift, and site. Handoffs became consistent, repeated mistakes declined, and managers spotted trends earlier—without replacing core systems or adding new screens at every station.

Client Profile

• Industry: Multi-site discrete and light process manufacturing
• Company size (range): Regional and international sites with common products
• Stage: Established MES/CMMS; handovers based on paper logs and ad hoc emails
• Department owner: Operations & Manufacturing
• Other stakeholders: Production Supervisors, Maintenance/Reliability, Quality, EHS, IT/OT, Site Leadership

The Challenge

Shift leads wrote handover notes in notebooks or shared spreadsheets, then walked the incoming crew through recent issues and priorities. The content varied by person and site: some logs listed downtime and scrap events; others focused on staffing or material risks. Alarms were discussed if someone remembered the details, and open work orders were mentioned if the right person was present. When the next shift faced the same problem, they often started from scratch because the previous context was hard to find or incomplete.

Systems had the data but not the workflow. MES tracked orders, states, and losses; CMMS contained open work orders and downtime causes; building or line systems produced alarms. None of that fed a structured handover tied to a specific line and shift. Email recaps and radio calls filled the gaps, which worked on quiet days but failed during changeovers or when a key lead was out. Leadership wanted consistent, searchable entries and a way to see patterns without turning every supervisor into a data analyst.

Sites also needed discipline around alarms and event capture. Teams were sensitive to alarm noise and did not want a tool that flooded handovers with raw alerts. Any solution had to filter and contextualize events, align with alarm management good practice such as ISA?18.2, and integrate with existing MES/CMMS without rip-and-replace. For integration boundaries and data ownership, the design followed ISA?95 principles.

Why It Was Happening

Root causes were fragmentation, variability, and a lack of a single place to capture decisions. Each site used its own handover format; content depended on the lead’s preferences; follow-ups lived in email or on whiteboards. MES and CMMS were separate islands, so a downtime event and its work order were rarely presented together during shift change. Alarms were visible on HMI screens but not retained in a way that made sense for handover. Without a structured log linked to orders, assets, and actions, teams repeated investigations and missed the opportunity to standardize fixes.

Ownership was diffuse. Operations owned handovers, Maintenance owned work orders, Quality owned deviations, and IT/OT owned the systems. There was no lightweight workflow to pull the right insights into a single record, require signoff, and make the handoff searchable across shifts and sites. The result was effort spent on reconstruction instead of execution.

The Solution

Intelligex delivered a digital logbook that sat alongside MES and CMMS. Supervisors captured shift highlights against a line and order, with prompts for downtime, quality events, alarms of interest, safety observations, and open actions. The logbook synchronized context from MES, surfaced relevant work orders from CMMS, and attached supporting evidence. Alarms were filtered and grouped before inclusion, and actions were assigned with owners and due horizons. Outgoing and incoming leads signed off, creating a clear chain of custody for decisions and outstanding items.

• Integrations: Read production states, orders, and losses from MES (e.g., Siemens Opcenter, Rockwell FactoryTalk ProductionCentre, SAP ME). Pulled open work orders, planned maintenance, and downtime causes from CMMS (e.g., IBM Maximo, Fiix). Optional read-only alarm and event feeds from SCADA/Historian via Open Platform Communications Unified Architecture (OPC UA) informed the log; reference: OPC UA.
• Structured entries: Templates by area prompted for the essentials—order status, top losses, quality holds, safety/environment observations, notable alarms, and handoffs. Free text was supported but guided by tags.
• Action tracking: Assigned actions with owners, links to work orders or deviations, and visibility until closure. Items aged visibly across shifts.
• Alarm and event curation: Grouped related alarms, suppressed chattering, and tied events to assets and time windows. Entries referenced alarm rationales and priorities aligned with ISA?18.2 practices.
• Signoffs and permissions: Outgoing and incoming leads e-signed handovers. Role-based access restricted edits and exposed read-only views to maintenance, quality, and management.
• Search and analytics: Full-text search with filters for line, asset, tag, and shift. Trend views and Pareto-style rollups highlighted recurring issues by site and asset family.
• Notifications: Summaries and escalations flowed to Microsoft Teams or email for actions that stalled or repeated.
• Security and retention: Least-privilege access with identity integration. Retention and export aligned to site policies and audit needs.

Implementation

• Discovery: Mapped current handover practices and pain points by site. Collected sample notebooks, spreadsheets, and email formats. Identified priority lines, common losses, key alarm sources, and how CMMS work orders were handed off.
• Design: Defined the logbook templates by area, action taxonomy, and signoff flow. Specified MES/CMMS context fields, alarm filters, and tags. Set permissions and retention rules. Agreed on dashboards for daily huddles and weekly reviews.
• Build: Configured connectors to MES and CMMS; implemented the logbook app with templates, tagging, and e-signatures; built alarm curation using read-only feeds; stood up search, dashboards, and notifications.
• Testing/QA: Ran in shadow mode while teams kept their current logs. Compared structured entries to existing notes for completeness. Tuned templates, alarm filters, and action routing. Included a human-in-the-loop review with site leads and maintenance.
• Rollout: Enabled by line and site in waves, starting with areas that experienced frequent repeat issues. Kept notebooks as a controlled fallback during early cycles. Integrated the logbook into start-of-shift and end-of-shift routines.
• Training/hand-off: Delivered short sessions during crew meetings for supervisors and key operators. Updated SOPs for handovers and action follow-up. Transferred ownership of templates, filters, and dashboards to Operations with IT support and change control.

Results

Handover notes moved from variable and hard-to-find records to structured entries with the same prompts at every site. Supervisors captured the relevant context quickly, open items carried owners, and incoming crews saw a consistent summary with links to MES and CMMS. Alarms of interest were grouped and referenced rather than pasted as noise. The handoff conversation shifted to decisions and next steps instead of recreating what happened.

Patterns surfaced earlier. Sites compared recurring issues by asset family and time of day, and maintenance focused on equipment that drove repeat downtime. Quality and EHS used the same records to review holds and observations. Managers scanned summaries across sites to allocate support where it was needed most. Core systems remained unchanged; the difference was a disciplined handover workflow and a shared view of what mattered.

What Changed for the Team

• Before: Notebooks and memory drove handovers. After: A structured logbook captured events, actions, and signoffs with links to MES and CMMS.
• Before: Alarms were recapped inconsistently. After: Curated alarm groups and tags referenced the events that mattered.
• Before: Open items drifted without owners. After: Actions carried owners and stayed visible until closure.
• Before: Each site used a different format. After: Templates aligned content while allowing local notes where needed.
• Before: Managers pieced together trends. After: Search and analytics highlighted recurring issues across lines and sites.
• Before: Handover quality varied by person. After: Prompts and e-signatures created consistent expectations and accountability.

Key Takeaways

• Make handovers a workflow, not a memo; structured templates and signoffs raise consistency without slowing crews.
• Pull context from systems of record; linking MES and CMMS data to the logbook reduces transcription and misses.
• Curate alarms before they hit the handover; grouping and suppression aligned to ISA?18.2 practices keep focus on what matters.
• Assign owners to actions; visible follow-through across shifts reduces repeated mistakes.
• Start in shadow mode, tune, then standardize; involve site leads to match templates to real work.
• Respect integration boundaries; follow ISA?95 for clean separation of control and business layers.

FAQ

What tools did this integrate with? The logbook read production states and orders from MES (for example, Siemens Opcenter, Rockwell FactoryTalk ProductionCentre, or SAP ME), pulled open work orders and downtime causes from CMMS (such as IBM Maximo or Fiix), and optionally consumed alarm and event feeds from SCADA/Historian via OPC UA. Dashboards and notifications surfaced in the organization’s BI tools and Microsoft Teams.

How did you handle quality control and governance? Templates, tags, and alarm filters lived under change control with Operations ownership and IT support. Entries captured user identity, time, and line context. Outgoing and incoming leads e-signed the handover. Edits preserved originals with reason codes. Retention followed site policy, and access was role-based.

How did you roll this out without disruption? The logbook ran in shadow mode first. Supervisors entered a structured handover while keeping their existing notebooks and spreadsheets. After tuning templates and alarm filters with site leads, the digital logbook became the default, with legacy methods retained as a controlled fallback for a limited period.

How were alarms and events filtered so the logbook didn’t become noisy? The service grouped related alarms, suppressed rapid repeats, and tied events to assets and windows. Only alarms that met defined criteria—impact on production or safety, repeated occurrences, or operator acknowledgment—were suggested for inclusion. Supervisors could add or remove items, and filters evolved under change control.

How did you ensure adoption on the floor? Templates matched the language crews used, and entries took only a few minutes. The logbook was embedded in existing shift routines, and value was visible immediately through better handoffs and fewer repeated investigations. Short, role-based training and early wins on recurring issues built trust, and signoffs reinforced accountability without adding bureaucracy.