Module 04 · akcniplan.idomino.cz

Action Plan

From problem to solution. Systematically.

A digital action plan that connects root-cause analysis, corrective actions and effectiveness verification into one closed PDCA cycle. Part of the iDomino Platform.

YAPP team with a tablet

Why Action Plan?

Problems recur because they aren't solved systematically.

Problems come back

Without analyzing the real cause (5 Whys, Ishikawa), only the symptom gets fixed. A week later the problem is back.

Actions get lost

Who was supposed to do what? By when? Did they? In spreadsheets and e-mails this information falls apart fast.

Effectiveness can't be proven

Without a link to real production data (OEE, scrap, downtime), the effectiveness assessment stays subjective.

The solution

Action Plan is an iDomino Platform module that guides you through the entire process - from identifying the problem, through root-cause analysis and defining actions, to verifying their effectiveness. All in one app, with clear accountability, deadlines and measurable impact.

  1. 1
    IDENTIFY
    the problem
  2. 2
    ANALYZE
    causes
  3. 3
    ACTIONS
    immediate, corrective, preventive
  4. 4
    IMPLEMENT
    tasks
  5. 5
    VERIFY
    effectiveness

←←← CLOSED PDCA CYCLE →→→

6 key features

1. Structured project

Problem description, priority, category, clearly assigned roles (Owner, Initiator, Observers), deadlines - all in one place.

2. Analytical tools

Built-in root-cause analysis with 5 Whys and the Ishikawa diagram. Risk analysis right in the project.

3. Three levels of action

Immediate (correction), corrective and preventive actions. Each has an Implementer and an Effectiveness inspector - no action goes unchecked.

4. Documentation links

Requests to revise internal documents (work instructions, FMEA, control plans) linked directly to actions.

5. Managed workflow

The project moves through clear states (New → In progress → Implemented → Closed). Every role sees exactly what they need.

6. Measurable results

Tracking of costs and savings. Connected to TPM Analytics - the impact of each action is verifiable against real data on OEE, downtime and scrap.

From analytics straight into action, in one click

Spot a recurring problem in the fault overview or analytics? In one click you create an action plan with all relevant data carried over automatically. After implementing the actions, you verify their effectiveness again against production data.

TPM Analytics
Fault reports
Fault types
Machine location
Shift team
Scrap reason
── 1 click ──▶
Action Plan
Project
Root-cause analysis
Actions
Tasks
Effectiveness check

Detailed feature overview

Project creation and management

Problem description with photos and attachments · Priority and category from a code list (production problem, improvement suggestion, customer complaint, audit finding) · Role assignment: Initiator, Owner, Observers · Key dates: start, required completion date · Location: plant → workstation → station · Link to a customer project / product line · Link to an incident report from TPM&M

Root-cause and risk analysis

Built-in 5 Whys (5Why) method · Ishikawa (fishbone) diagram · Risk analysis

Actions and tasks

Immediate actions (correction) · Corrective actions (removing the cause) · Preventive actions (preventing recurrence) · Each has an assigned Implementer and Effectiveness inspector · Sub-tasks with an Assignee and deadline · Requests to revise internal documents linked to actions

Documents

Project attachments: photos, files, protocols · Editable in all states except Closed · Accessible to everyone with access to the project detail

Tracking and evaluation

Implementation costs and savings achieved · Connected to OEE Analytics data for measurable impact verification · Complete resolution history, traceable anytime

Overview, filtering and workflow

Project list with extensive filtering · States: New → In progress → Implemented → Closed (with the option to return) · Three visibility levels (all / own / assigned) · Restrictions by user location

Action Plan for individual roles

Every project has an Initiator, Owner, Project administrator and optionally Observers. At the action level, Implementers and Effectiveness inspectors work. Tasks are carried out by Assignees.

STATES: New → In progress → Implemented → Closed

Initiator / Administrator

Creates the project, structures the problem, assigns the Owner. Runs root-cause analysis (5 Whys, Ishikawa). Moves the project through states. The only one who can finally close the project.

Project owner

The main responsible person. The broadest editing rights. Manages tasks and actions, assigns assignees, tracks costs and savings, evaluates impact.

Implementer

Implements the assigned action and documents the execution. Adds sub-tasks within their action. Can edit the record while the action is awaiting verification.

Effectiveness inspector

Verifies the effectiveness of the implemented action, confirms it or returns it for rework with a comment. The core of the PDCA cycle at the action level.

Task assignee

Responsible for completing a specific task. Sees only projects with their tasks. Starts and finishes tasks. Focused access - sees exactly what they need.

Management / Observer

An overview of project status without needing to actively intervene. A monitoring and decision-making role. The department manager has full editing rights.

Connected to the iDomino Platform

TPM&M
TPM activities · OEE Analytics · Preventive maintenance
Action Plan
Problem solving · Root-cause analysis · Actions and tasks · Effectiveness verification
AMS
Internal audits · Product inspection · AI report generation
01
TPM AnalyticsAction Plan

A recurring fault, excessive scrap or long downtime? From analytics, create an action plan with pre-filled data in one click.

02
AMSAction Plan

An audit finding that needs a systematic solution? The link lets you tie an action plan to a specific audit nonconformity.

03
Action PlanAnalytics

After implementing the action, you verify its effectiveness against real production data - OEE, downtime and scrap.

FAQ

Frequently asked questions

A system for structured problem solving: identification, root-cause analysis (5 Whys, Ishikawa), three levels of measures (immediate, corrective, preventive) and verifying effectiveness on production data. It closes the PDCA cycle.

Automatically from audits (AMS), from meetings, Gemba walks and from deviations revealed in TPM Analytics. Instead of getting lost in inboxes and heads, they live in one place with an owner and a deadline.

Every measure has an owner and a deadline. Overdue items escalate to the supervisor. Management sees the status of all measures in a single overview.

The action-plan module automatically loads data from TPM Analytics, so you see the effectiveness on real numbers - for example a drop in scrap or a rise in OEE after a change is implemented.

Yes. You can start with just the action plan and add AMS, TPM&M and Analytics over time. The biggest benefit, though, comes from connecting them - that is when the whole PDCA cycle closes.

Stop solving problems in spreadsheets

From problem to solution. Systematically.

kamil.vasak@idomino.cz · +420 724 135 735