Further Actions - CAPA

How You Can Handle CAPA Programs Within ION

Overview

The issue ticket is the most direct connection to the manufacturing floor within ION Factory OS. This connection allows ION issue tickets to be automatically populated with details such as associated parts, processes, responsible teams, and supplier-related documentation. With all this information in one place, the responsible engineer can quickly determine the disposition and resolution of the issue.

The workflow continues in ION through a redlining process that captures the corrective actions needed to fix the occurrence. The final step involves relating those corrective actions to further actions. These further actions enable manufacturers to implement comprehensive changes to their processes or effectively communicate to resolve supplier-related issues, even after closing the original ION issue ticket. This is a necessary continuation of any quality process.

First Resonance has started the roll out of this feature. If you are interested in this capability please reach out to the team to get involved and benefit from giving early input.

Content

Within Furthers Actions there are three main body text fields. Natively those fields are called "Problem Statement", "Analysis Notes", and "Resolution". We realize that there may be specific terminology that you want to use for your quality process and thus (COMING SOON) we allow organizations to customize what these fields say, just like we do for our standard "Issue" ticket. That being said we want to express the intent of these fields as they are used throughout ION to capture insights into your process.

Section	ION Definition	Common Alternatives
Problem Statement	This field captures a clear, concise description of the issue being addressed. It should include specifics on what went wrong, the context in which it occurred, and any observed impacts on the product, process, or performance. The goal is to establish a shared understanding of the problem's nature and scope.	Failure Summary, Incident Report, Opportunity For Improvement
Analysis Notes	This section provides a detailed investigation of the root cause(s) of the problem. It may include contributing factors, relevant background information, and findings from diagnostic efforts or testing. The Analysis Notes aim to offer a thorough examination of why the issue occurred, supporting an informed approach to resolution.	Root Cause Analysis, Fishbone Breakdown, Observations and Findings
Resolution	The Resolution field outlines the steps taken to correct the problem and prevent recurrence. This may include corrective actions, preventive measures, and any process adjustments made. The resolution should be specific and actionable, detailing how each part of the solution addresses the identified causes of the problem. Utilize runs to capture these actions!	Mitigation Steps, Action Plan, Preventative Actions

Use Cases

1. Supplier Related ION Issues and Supplier Corrective Actions

Use Case #1 in Action:

1. Groupings of ION Issues to Address Deep Seated Root Cause

Use Case #2 in Action:

1. Further Actions to Capture Non-ION related Continuous Improvement Opportunities

Use Case #3 in Action:

1. Further actions are not just limited to the cases above. The overall flexibility these tickets offer lend themselves to good containers for a variety of objectives while still maintaining traceability back to core ION Objects. Link parts, runs, and issues however you like to create a network of connections with Further Actions.

Best Practices

Creating Resolution Actions

Define your actions for the Further Action and track progress against them.

Create one plan with all your actions within it OR create each action in a unique plan to be as granular as you wish.

Create and view actions to be taken

Define the actions needed in two ways.

• Create a blank plan and free form add steps to accomplish the requirements for resolution.

  

  Define the steps needed for resolution.

• Utilize a known process for resolution when repeat actions are needed. Choose a procedure that is templated to solve the specific occurrence.

  

  Setup your actions through standardized procedures

When to Use the Canceled State for Further Actions

The Canceled state is useful for managing the relevance and priority of further actions within your organization. Here are the key points to consider:

1. Accidental Creation: If a further action is created by mistake, it can be moved to the Canceled state to indicate that the action is not needed.

2. Editing Restrictions: Further actions in the Canceled state cannot be edited. However, they can be moved back to the In Progress state if they were accidentally canceled.

3. Avoid This Flow: If a further action is approved and then needs to be canceled, it can be moved back to the Approved state as all approval requests have been satisfied. However, this practice is not recommended. See point four for the best practice.

4. Ideal Workflow for Re-evaluation: If a resolved further action is found to be insufficient, the recommended process is to reopen the further action. This will move the action back to the In Progress state, where necessary changes can be made, and the correct approvals can be requested. This approach avoids confusion and ensures that actions are appropriately tracked and managed.

By following these guidelines, you can maintain a clear and efficient workflow for managing further actions.