phkapa
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
phkapa [27/07/2016 17:59] – [Actions] phalkaline | phkapa [24/02/2021 10:52] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== pHKapa ====== | ====== pHKapa ====== | ||
- | pHKapa nonconformity management software allows you to generate | + | pHKapa nonconformity management software allows you to generate ticket |
- | that routes through register, review, plan and implement, and verification stages.\\ | + | that routes through register, review, plan/implement, and verification stages, providind |
- | This action tracking software provides an effective | + | |
===== Purpose ===== | ===== Purpose ===== | ||
- | pHKapa is designed to correct and eliminate the root causes of nonconformities.\\ | + | pHKapa is designed to help register, |
Ensuring that corrective and preventive action is a vital closed loop system of root cause analysis, | Ensuring that corrective and preventive action is a vital closed loop system of root cause analysis, | ||
documented action, verification of effectiveness, | documented action, verification of effectiveness, | ||
Line 13: | Line 12: | ||
===== Scope ===== | ===== Scope ===== | ||
- | Implementing immediate solution for the nonconformity.\\ | + | Implementing immediate solution for the nonconformity |
- | Performing a Corrective Action | + | Help the performing of CAPAS to eliminate the root causes of Nonconformities.\\ |
- | Executing a flexible Action | + | Executing a flexible Action |
- | Performing a Preventive Action to eliminate the root causes of a potential Nonconformity.\\ | + | |
This procedure applies to identified product, process, system nonconformities and problematic | This procedure applies to identified product, process, system nonconformities and problematic | ||
performance with respect to internal quality, manufacturing, | performance with respect to internal quality, manufacturing, | ||
Line 23: | Line 21: | ||
===== Create Users and Access ===== | ===== Create Users and Access ===== | ||
- | First thing to do before using pHKapa is create your Users and define | + | First thing to do before using pHKapa is create your Users and define |
- | Only with administrator accounts you can create Users and define Access settings, to do this you must go access area -> Key Icon -> < | + | Only with administrator accounts you can create Users and define Access settings, to do this you must enter access area -> Key Icon -> < |
More info at [[administration|Users and Access]] .\\ | More info at [[administration|Users and Access]] .\\ | ||
- | Users loaded | + | Users loaded |
Default user password equals username -> username : quality , password : quality \\ | Default user password equals username -> username : quality , password : quality \\ | ||
- | |||
- | After you have your users and processes defined, you should define on witch business process the users will work. This means that if you assign a user to Information Systems process, this user will have access to Tickets related to Information Systems. By default all users also has access to self-registered tickets.\\ | ||
===== Fill Classification Tables ===== | ===== Fill Classification Tables ===== | ||
Line 41: | Line 37: | ||
One important topic is relations between classify tables.\\ | One important topic is relations between classify tables.\\ | ||
- | Processes has many Activities and Categories.\\ | + | It works this way, at Register, |
- | Categories has many Causes.\\ | + | |
- | It works this way, at Register, you choose a Process | + | |
When a ticket reaches PLAN stage, Cause field options is loaded only with Cause values related to Ticket Category.\\ | When a ticket reaches PLAN stage, Cause field options is loaded only with Cause values related to Ticket Category.\\ | ||
More info at [[phkapaadministration# | More info at [[phkapaadministration# | ||
Next task is define each Process a User belongs to.\\ | Next task is define each Process a User belongs to.\\ | ||
- | This task sets user access to tickets. each user will only have acess and receive notifications on self registered tickets and tickets on processes this user belongs to.\\ | ||
Go to pHKapa Setup → < | Go to pHKapa Setup → < | ||
More info at [[phkapaadministration# | More info at [[phkapaadministration# | ||
Line 54: | Line 47: | ||
Next task is fill up Action Classification Options.\\ | Next task is fill up Action Classification Options.\\ | ||
- | Each ticket | + | Each ticket |
- | Action types are managed on menu Action Type , and you can have as many as you want.\\ | + | Action types , you can have as many as you want.\\ |
- | On Action Type, when checking “Verification” option you set “Action Effectiveness” as required for this action/ | + | |
More info at [[phkapaadministration# | More info at [[phkapaadministration# | ||
Line 65: | Line 57: | ||
===== REGISTER - Originating a Request ===== | ===== REGISTER - Originating a Request ===== | ||
- | When identified a potential or actual problem or nonconformance , a request action must be registered and submitted as soon as possible.\\ | + | When identified a potentia, |
- | Click Menu -> Add Ticket and insert | + | Click Menu -> Add Ticket and fill values for requested fields.\\ |
- | **Origin Date, Type, Origin, Process, Activity, Category, Priority, Safety are required**\\ | + | **Origin Date, Type, Origin, Process, Activity, Category, Priority, Safety, Cost ( may put 0 ), are required**\\ |
How to configure values for this tables? goto [[pHKapaAdministration|pHKapa Setup]]\\ | How to configure values for this tables? goto [[pHKapaAdministration|pHKapa Setup]]\\ | ||
Line 75: | Line 67: | ||
===== REVIEW - Quality Assurance Review ===== | ===== REVIEW - Quality Assurance Review ===== | ||
- | At REVIEW stage a ticket must have a review | + | At REVIEW stage a ticket must have a review |
- | Edit option is always available but you must edit and save your ticket at least once to have Send to Plan option ( When Approved ) or Close option ( When Unapproved ) available.\\ | ||
Here all initially fields can be reviewed and changed, also some review notes can be inserted\\ | Here all initially fields can be reviewed and changed, also some review notes can be inserted\\ | ||
Approving a ticket, determines that actions are required.\\ | Approving a ticket, determines that actions are required.\\ | ||
- | After you have completed your review | + | After you have completed your review and all values are OK. Approve, save and then click Plan to " |
- | Closed Tickets will be available for consulting at QUERY option. \\ | + | Edit option is always available, but you must edit and save your ticket at least once to have Send to Plan option ( When Approved ) or Close option ( When Unapproved ) available.\\ |
+ | |||
+ | Closed Tickets will be available for consulting at QUERY. \\ | ||
Line 91: | Line 84: | ||
===== PLAN Action Implementation ===== | ===== PLAN Action Implementation ===== | ||
- | A ticket | + | Whan a ticket |
- | So first:\\ | + | You must:\\ |
* Investigate the potential root-cause; | * Investigate the potential root-cause; | ||
* Analyze suspect processes and/or operations to determine the specific root cause. | * Analyze suspect processes and/or operations to determine the specific root cause. | ||
Line 101: | Line 94: | ||
Click PLAN to access list of tickets at PLAN stage. \\ | Click PLAN to access list of tickets at PLAN stage. \\ | ||
- | Edit Ticket , fist submit Cause and Cause Notes and then Add planned Actions. | + | Edit Ticket , first submit Cause and Cause Notes ( 5 Whys or other schema ) and then Add planned Actions. |
Line 109: | Line 102: | ||
==== Actions ==== | ==== Actions ==== | ||
- | On List Actions / Plan area , for every action planed | + | At List Actions / Plan area , to register actions |
**Action Type, Description, | **Action Type, Description, | ||
- | After "Saved with success", | + | After "Saved with success", |
- | Every Action Type has a rule defined about action effectiveness evaluation, so when you add at least one action with " | + | Every Action Type has a rule defined about action effectiveness evaluation, so when you add at least one action |
You can configure each action type at pHKapa Setup -> < | You can configure each action type at pHKapa Setup -> < | ||
- | ==== Some specific rules at PLAN stage ==== | + | ==== Some specific |
- | Close or Verify | + | Close or Verify |
Close option will be available when ticket has no actions.\\ | Close option will be available when ticket has no actions.\\ | ||
- | Send option will be available when ticket has all actions Closed and at least one action type that requires Effectiveness Evaluation otherwise it will be Close option available.\\ | + | Send to Verify |
Line 167: | Line 160: | ||
When a user belongs to the same process as this ticket, he will receive notification.\\ | When a user belongs to the same process as this ticket, he will receive notification.\\ | ||
If this user has a valid email defined and pHKapa configuration has email notifications on, this user will also receive notification by email.\\ | If this user has a valid email defined and pHKapa configuration has email notifications on, this user will also receive notification by email.\\ | ||
+ | |||
+ | ===== New Features / Functionalities ===== | ||
+ | |||
+ | pHKapa was developed on the principle of simplicity for effective management of your CAPAS.\\ | ||
+ | But sometimes you need to upgrade with new features according to your needs.\\ | ||
+ | Feel free to contact us, we are here to help you. |
phkapa.1469635151.txt.gz · Last modified: 27/07/2016 16:59 (external edit)