Smart Flow with Other Modules

How the Meetings & Actions module connects to other modules — action origins, meeting data feeds, and cross-module traceability.

Meetings and actions are where everything comes together. Data from every module feeds into meetings. Actions flow back out — to the teams and individuals who need to follow through. An action created from a quality issue during a Tier 1 meeting carries the issue context, appears in the next shift handover, and tracks to closure across every view. This is where the platform advantage over separate tools becomes most visible.

Module "Issues & Logbook"

Trigger → Action → Outcome: An issue is logged → actions can be created directly from the issue detail page → the action carries a link back to the issue, so corrective or preventive measures are always traceable to their origin.

Issue categories and subcategories can be configured with automatic action creation — when an issue is classified, the configured actions are created automatically, ensuring standard follow-up procedures are never skipped. Notifications are sent to the issue assignee when an action is added.

Issues can also be flagged for discussion in meetings with a single click, bringing them onto the meeting agenda with their current status and context.

Meetings and actions (bidirectional)

Actions and meetings have a deep, bidirectional integration:

• Create actions during a meeting — While a meeting is in progress, actions can be created directly from the meeting view. They automatically link to that meeting.

• Outstanding actions from previous meetings — When you open a meeting in a series, all open actions from previous meetings are visible. Last meeting's actions are front and center — making recurring meetings effective for follow-up, not just review.

• Privacy inheritance — When an action is linked to a private meeting, the meeting's audience (organizers + participants) is automatically included in the action's visibility. If meeting participants change, action visibility updates accordingly.

Module "Checklists & Planned Work"

Trigger → Action → Outcome: A checklist check reveals a deviation → the operator creates an action directly from the check → the action links back to the specific check for full traceability. Checklist compliance data and trends can be embedded in meeting dashboards for performance review.

Production Orders

Actions can be linked to production orders, connecting follow-up tasks to the specific production context that triggered them. This ensures improvement actions are traceable to the product, batch, or run where the issue occurred.

BOS (Basis of Safety) Entries

Actions can originate from BOS entries, linking safety observations to concrete follow-up tasks. This connects the safety observation practice directly to tracked improvement.

Root Cause Analysis (Why-Why)

Trigger → Action → Outcome: A root cause analysis is performed using the Why-Why tool → actions can be created from individual "why" nodes → the action links not only to the why node but also to the underlying entity (e.g. the issue being analyzed), maintaining full traceability from root cause to corrective action.

Module "Downtimes"

Downtime data (OEE availability, Pareto charts, trend analysis) can be embedded directly in meeting dashboards. This means performance meetings discuss facts — current data, not last week's spreadsheet. Downtime trends visible in meetings trigger improvement actions that are tracked to closure.

Concrete example: from meeting to closed action

Wednesday morning, Tier 2 meeting. The production manager opens the weekly review. The meeting auto-populates: OEE is down 4% from last week. The downtime Pareto shows "Unplanned — Label applicator fault" as the #2 contributor. An issue from Monday's shift is flagged for discussion — root cause confirmed as worn guide rails. The team creates an improvement action: replace guide rails preventively on all four packaging lines. Assigned to the maintenance lead, deadline in two weeks.

The following Wednesday, the action appears in the same meeting series as "open from last week." The maintenance lead reports: Lines 1 and 2 done, Lines 3 and 4 scheduled for the weekend. Two weeks later, the action is closed. The next month's downtime Pareto shows label applicator stops dropped from #2 to not visible. The loop is closed — from data, through meeting, to action, to result.