POET is not designed to serve as the system of record for regulated processes, therefore not subject to GxP requirements. It is designed to enable cross-organizational collaboration and process orchestration, while the system of record for each process remains within the respective enterprise systems.
CAPA Exchanges
In regulated pharmaceutical and life sciences supply chains, CAPA (Corrective and Preventive Action) exchanges enable organizations and their partners to collaboratively investigate quality issues, implement corrective actions, and prevent recurrence across the network.
What is a CAPA Exchange
A CAPA exchange is a structured process used to investigate issues, identify root causes, define corrective and preventive actions, and verify their effectiveness. CAPA exchanges ensure regulatory compliance, operational transparency, and cross-partner accountability. The CAPA exchange lifecycle typically includes the following steps:
- Issue Detection: A quality event such as a deviation, complaint, audit finding, or incident triggers a CAPA record.
- Assignment: A CAPA owner is assigned to coordinate investigation and resolution activities.
- Root Cause Investigation: Teams collaborate to determine the underlying cause of the issue.
- Corrective Actions: Immediate measures are defined to correct the issue.
- Preventive Actions: Long-term improvements are implemented to prevent recurrence.
- Effectiveness Verification: The implemented actions are evaluated to ensure the issue is resolved.
- Closure: The CAPA exchange is formally closed once effectiveness is confirmed and documentation is complete.
Types of CAPA Exchanges
-
Deviation CAPAs: Triggered by manufacturing or operational deviations.
-
Complaint CAPAs: Initiated due to product quality complaints.
-
Audit CAPAs: Created from audit findings requiring remediation.
-
Excursion CAPAs: Initiated when environmental or operational excursions occur.
-
Incident CAPAs: Initiated from operational or supply chain incidents.
How to configure the CAPA Exchanges marketplace solution
Before using the CAPA Exchanges marketplace solution, Solution Designers must first configure the solution in Opus Solution Environment (OSE) by following the steps listed below:
Solution Designers must first save the latest version of the marketplace solution from the marketplace catalog as a company solution.
- Select the Main Menu
icon. - Select .
- Select from the left menu.
- Select .
- On the Search Solutions page, filter the list of solutions to find the required solution.
- Find the latest version of the solution and select the to open the solution.
- On the Solution Details page, select .
- On the Save As panel, fill in the following fields:
- field – The name of the solution that will be saved as a company solution.
- field – (Optional) The description of the solution.
- Select .
The marketplace will be saved as a company solution in the Available tab on the left menu.
After saving the solution as a Company Solution, Solution designers must create a network for the solution from OPUS Administration.
- Select the Main Menu
icon. - Select .
- Select from the left menu.
- Select .
- In the Network Information section, fill in the following fields:
- drop-down – Select the application for which you want to configure the marketplace solution. For e.g. Process Orchestration for Empowered Teams.
- field – The name of the network being created.
- field – (Optional) The description of the network being created.
- In the Solution section, fill in the following fields:
- toggle – This value must be no as the solution for which the network is being created is a marketplace solution.
- field – Select the solution that you saved as a company solution in the previous procedure.
- Select .
The new network is created and the solution is ready for use.
After creating a network for the solution, Solution Designers must define roles for accessing the network.
- Select the Main Menu
icon. - Select .
- Select from the left menu.
- Select from the left menu.
- On the Search Network Members page, filter the list of network members by the network created in the previous procedure.
- Select the user email of the user who created the network.
- Select .
- In the Roles section, select the role required to access the network.
- Select .
The role to access the new network is configured.
Add a CAPA Exchange
- Select the Main Menu
icon. - Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the drop-down in the header.
- Select .
- Select from the left menu.
- Select .
- In the General section fill in the following fields:
- field – Title describing the CAPA exchange.
- field – Description of the issue, including context and supporting details.
- Select .
The CAPA exchange is created in the Draft state. - To move the CAPA exchange to To Do state, select .
Modify a CAPA Exchange
- Select the Main Menu
icon. - Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the drop-down in the header.
- Select .
- Select from the left menu.
- Select the Display Identifier of the CAPA exchange to edit.
- Select .
- In the General section update the following fields:
- field – System-generated CAPA identifier.
- field – CAPA title summarizing the issue.
- field – Target completion date for the CAPA.
- field – Description of the CAPA issue.
- field – Manufacturing, Logistics, Transportation, Commerce, or Other.
- field – Deviation, Complaint, Audit, Excursion, or Incident.
- field – Critical, High, Medium, or Low.
- In the Participants section update the following fields:
- field – Company that initiated the CAPA.
- field – Responsible partner company.
- field – Person accountable for CAPA execution.
- In the Impact Assessment section update the following fields:
- field – Critical, High, Medium, or Low.
- field – Indicates compliance or regulatory reporting impact.
- field – None, Potential, or Confirmed.
- field – Responsible evaluator.
- In the Root Cause Analysis section update the following fields:
- field – Final root cause description.
- field – RCA methodology used.
- field – Indicates if issue is recurring.
- field – Supporting RCA documentation.
- field – Person responsible for investigation.
- In the Corrective Actions section update the following fields:
- field – Immediate corrective action.
- field – Responsible person.
- field – Target completion date.
- field – Corrective action evidence.
- field – Acceptance criteria for corrective action.
- In the Preventive Actions section update the following fields:
- field – Preventive measure.
- field – Responsible person.
- field – Preventive action deadline.
- field – Preventive documentation.
- field – Acceptance criteria.
- In the Effectiveness Check section update the following fields:
- field – Definition of success.
- field – Effective, Ineffective, or Partially Effective.
- field – Verification date.
- field – Effectiveness verification report.
- field – Responsible evaluator.
- In the Closure Summary section update the following fields:
- field – Closed-Effective, Closed-Ineffective, or Withdrawn.
- field – Summary and justification for closure.
- field – Formal closure date.
- field – Responsible person closing the CAPA.
- In the Comments and Attachments section update the following fields:
- field – User who entered the comment.
- field – Comment content.
- field – Supporting CAPA documentation.
- The Followers section displays users following the CAPA exchange.
CAPA Exchanges workflow
The following workflow states are used to track the progress of a CAPA exchange:
| Base State | Workflow State | Description |
|---|---|---|
| Draft | Draft | The CAPA exchange is being created and initial issue details are captured. The CAPA has not yet been formally submitted for review or investigation. |
| To Do | To Do | The CAPA exchange has been formally logged and assigned to a responsible owner. Initial impact assessment and investigation planning may begin. |
| In Progress | Under Investigation | Root cause analysis is actively being conducted. Internal teams and external partners collaborate to identify the underlying cause of the issue. |
| In Progress | Under Implementation | Corrective and preventive actions are being executed. Assigned owners implement action plans and upload supporting evidence. |
| In Progress | Under Effectiveness Check | The effectiveness of the implemented actions is being evaluated to confirm that the issue has been resolved and will not recur. |
| Done | Closed | The CAPA exchange is formally completed after successful verification of effectiveness and completion of all required documentation. |
The workflow ensures visibility, accountability, and traceability of CAPA activities across the supply chain network.
Monitor CAPA Exchanges
A high level understanding of the state of all CAPA exchanges that you have access to.
- Select the Main Menu
icon. - Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the drop-down in the header.
- Select .
- Select from the left menu.
View the widgets in the dashboard, which display pre-defined queries to demonstrate the state of all CAPA exchanges at a high level.
| Metric | Description |
|---|---|
| Current Trends | |
| CAPA Exchanges by Status – Open | Total number of CAPA Exchanges categorized by currentState (Draft, To Do, In Progress). Provides real-time visibility into CAPA lifecycle distribution and bottlenecks. |
| CAPA Exchanges by Business Priority | Total number of CAPA Exchanges by priority by currentState (Draft, To Do, In Progress). Enables CAPA tracking by business priority. |
| Open CAPA Exchanges by Risk Level | Open CAPA Exchanges categorized by Severity (Critical, High, Medium, Low) by currentState. Enables risk-based prioritization. |
| CAPA Exchanges by CAPA Reason | Distribution by Trigger Source (Deviation, Complaint, Audit, Excursion, Incident) by currentState. Identifies systemic issue origins. |
| Due Date Monitoring | |
| CAPA Exchanges Overdue | CAPA Exchanges past Due Date by currentState. Escalates compliance and execution risks. |
| CAPA Exchanges Due in Next 24 Hours | CAPA Exchanges due within 24 hours by currentState. Highlights items requiring immediate executive attention. |
| CAPA Exchanges Due in Next 7 Days | CAPA Exchanges due within 7 days by currentState. Supports short-term workload planning. |
| CAPA Exchanges Due in Future | CAPA Exchanges due beyond 7 days by currentState. Supports capacity forecasting. |
| Network Performance | |
| CAPA Exchanges by Partner | CAPA Exchanges grouped by Assignee Company and stacked by currentState. Identifies partner risk exposure and recurring issues. |
| CAPA Exchanges by Regulatory Impact | CAPA Exchanges categorized by Regulatory Impact (Yes/No) by currentState. Tracks compliance exposure. |
| Effectiveness Failure Rate | Percentage of CAPA Exchanges marked Not Effective. Identifies weak root cause analysis or preventive controls. |
| Organizational Performance | |
| CAPA Exchanges by CAPA Owner | Distribution of CAPA Exchanges by owner. Enables workload balancing. |
| CAPA Exchanges by Closure Status | Closed CAPA Exchanges categorized by Closure Status (Closed-Effective, Closed-Ineffective, Withdrawn). Measures CAPA quality and governance. |
| Average Time to Close CAPA Exchanges by Risk Level | Average duration from creation to Done state classified by risk level. |
| Average Time to Close CAPA Exchanges by Customer Impact | Average duration from creation to Done state classified by customer impact. |
- Select the Main Menu
icon. - Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the drop-down in the header.
- Select .
- Select from the left menu.
View the widgets in the dashboard, which display pre-defined queries to demonstrate the state of all CAPA exchanges at a high level.
| Metric | Description |
|---|---|
| Current Trends | |
| CAPA Exchanges by Status – Open | CAPA Exchanges categorized by currentState (Draft, To Do, In Progress). Provides visibility into active CAPA Exchanges at the partner site. |
| CAPA Exchanges by Business Priority | Total number of CAPA Exchanges by priority by currentState (Draft, To Do, In Progress). Enables CAPA tracking by business priority. |
| CAPA Exchanges by Risk Level | Open CAPA Exchanges categorized by Severity. Identifies critical compliance risks. |
| CAPA Exchanges by CAPA Reason | Distribution by Trigger Source by currentState. Identifies recurring systemic issues. |
| Due Date Monitoring | |
| CAPA Exchanges Overdue | CAPA Exchanges past Due Date by currentState. Escalates partner compliance delays. |
| CAPA Exchanges Due in Next 24 Hours | CAPA Exchanges due within 24 hours by currentState. Highlights urgent action items. |
| CAPA Exchanges Due in Next 7 Days | CAPA Exchanges due within 7 days by currentState. Supports short-term partner workload planning. |
| CAPA Exchanges Due in Future | CAPA Exchanges due beyond 7 days by currentState. Provides planning visibility. |
| Network Performance | |
| CAPA Exchanges by Customer Impact | CAPA Exchanges categorized by Customer Impact. Tracks downstream service and product impact. |
| CAPA Exchanges by Regulatory Impact | CAPA Exchanges categorized by Regulatory Impact. Tracks compliance exposure at the partner site. |
| Organizational Performance | |
| Average Time to Close CAPA Exchanges by Risk Level | Average closure duration for partner-owned CAPA Exchanges classified by risk level. |
| Average Time to Close CAPA Exchanges by Customer Impact | Average closure duration for partner-owned CAPA Exchanges classified by customer impact. |
| CAPA Exchanges by Closure Status (My Site) | Closed CAPA Exchanges categorized by Closure Status for the partner site. Reflects CAPA quality and completion outcomes. |
- Select the Main Menu
icon. - Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the drop-down in the header.
- Select .
- Select from the left menu.
- Select .
-
In the Filters panel, fill in one or more of the following fields to filter the results:
- field – Unique identifier of the CAPA exchange.
- field – Title of the CAPA exchange.
- field – Workflow state of the CAPA exchange such as Draft, To Do, In Progress, or Done.
- field – The date and time when the CAPA exchange was created.
- field – The business name and identifier of the company that initiated the CAPA exchange.
- field – The business name and identifier of the company assigned to the CAPA exchange.
- field – The user responsible for managing the CAPA exchange.
- field – The due date by which the CAPA exchange must be completed.
- field – Category classification of the CAPA exchange.
- field – Event that triggered the CAPA exchange such as deviation, complaint, audit, or incident.
- field – Indicates the risk level associated with the CAPA exchange.
- field – Indicates whether the CAPA exchange has regulatory impact.
- field – Displays the time period when the CAPA exchange was last updated.
-
Select .
All CAPA exchanges matching the filter criteria are displayed.


