Differences

This shows you the differences between two versions of the page.

--- phkapa [27/07/2016 17:59] – [Actions] phalkaline
+++ phkapa [26/09/2024 18:57] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== pHKapa ======
-pHKapa nonconformity management software allows you to generate a ticket request
+pHKapa nonconformity management software allows you to generate ticket requests
-that routes through register, review, plan and implement, and verification stages.\\
+that routes through register, review, plan/implement, and verification stages, providind effective mechanisms to determinate the source and costs of problems.\\
-This action tracking software provides an effective mechanism for determinate the source and costs of problems.\\
 ===== Purpose =====
-pHKapa is designed to correct and eliminate the root causes of nonconformities.\\
+pHKapa is designed to help register, correct and eliminate the root causes of nonconformities.\\
 Ensuring that corrective and preventive action is a vital closed loop system of root cause analysis,
 documented action, verification of effectiveness, and prevention of recurrence.\\
@@ Line 13: / Line 12: @@
 ===== Scope =====
-Implementing immediate solution for the nonconformity.\\
+Implementing immediate solution for the nonconformity ( CAPA ).\\
-Performing a Corrective Action to eliminate the root causes of the Nonconformity.\\
+Help the performing of CAPAS to eliminate the root causes of Nonconformities.\\
-Executing a flexible Action Plan.\\
+Executing a flexible Action Plans.\\
-Performing a Preventive Action to eliminate the root causes of a potential Nonconformity.\\
 This procedure applies to identified product, process, system nonconformities and problematic
 performance with respect to internal quality, manufacturing, customer complaints, work safety issues and
@@ Line 23: / Line 21: @@
 ===== Create Users and Access =====
-First thing to do before using pHKapa is create your Users and define the Access settings.\\
+First thing to do before using pHKapa is create your Users and define access settings.\\
-Only with administrator accounts you can create Users and define Access settings, to do this you must go access area -> Key Icon -> <nowiki>http://{your-url-for-pHKapa}/access</nowiki> .\\
+Only with administrator accounts you can create Users and define Access settings, to do this you must enter access area -> Key Icon -> <nowiki>http://{your-url-for-pHKapa}/access</nowiki> .\\
 More info at [[administration|Users and Access]] .\\
-Users loaded for demonstration are : admin , quality , op , macs , mcb , rec , cd , hr , aaf , phkapa \\
+Users loaded with demonstration are : admin , quality , op , macs , mcb , rec , cd , hr , aaf , phkapa \\
 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 =====
@@ Line 41: / Line 37: @@
 One important topic is relations between classify tables.\\
-Processes has many Activities and Categories.\\
+It works this way, at Register, when you choose a Process, Category and Activity fields are loaded automaticaly only with Process related values.\\
-Categories has many Causes.\\
-It works this way, at Register, you choose a Process and the Category and Activity fields are loaded only with Process related values.\\
 When a ticket reaches PLAN stage, Cause field options is loaded only with Cause values related to Ticket Category.\\
 More info at [[phkapaadministration#relations|pHKapa Setup ( Relations ) ]] .\\
 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 → <nowiki>http://{your-url-for-pHKapa}/admin/phkapa</nowiki> ( Menu → Users → Edit ) .\\
 More info at [[phkapaadministration#assign_one_or_more_processes_to_users| pHKapa Setup ( User settings ) ]] .\\
@@ Line 54: / Line 47: @@
 Next task is fill up Action Classification Options.\\
-Each ticket can have many actions, and each action is classified with Action Types, like corrective, preventive or other.\\
+Each ticket may have many actions, and each action is classified with Action Types, like corrective, preventive or other.\\
-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/ticket at VERIFY stage.\\
 More info at [[phkapaadministration#classify_actions|pHKapa Setup ( Classify Actions ) ]] .\\
@@ Line 65: / Line 57: @@
 ===== 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, actual problem or nonconformance , a request action must be registered and submitted as soon as possible.\\
-Click Menu -> Add Ticket and insert values for requested fields.\\
+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]]\\
@@ Line 75: / Line 67: @@
 ===== REVIEW - Quality Assurance Review =====
-At REVIEW stage a ticket must have a review to approve or disapprove as soon as possible.\\
+At REVIEW stage a ticket must have a review by someone responsible, and approve or disapprove as soon as possible.\\
-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\\
 Approving a ticket, determines that actions are required.\\
-After you have completed your review , approved and all values are OK Click Plan. This will "SEND" your ticket for PLAN stage.\\
+After you have completed your review and all values are OK. Approve, save and then click Plan to "SEND" your ticket to PLAN stage.\\
-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 =====
-A ticket is now at PLAN stage.\\
+Whan a ticket arrives to PLAN stage.\\
-So first:\\
+You must:\\
   * Investigate the potential 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. \\
-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 ====
-On List Actions / Plan area , for every action planed Click Add Action, and insert requested fields.\\
+At List Actions / Plan area , to register actions Click Add Action, and fill requested fields.\\
 **Action Type, Description, Deadline ( deadline is the number of days this action has to be closed ), Closed**\\
-After "Saved with success", it will show up on List Actions / Plan area.\\
+After "Saved with success", it will show up at List Actions / Plan area.\\
-Every Action Type has a rule defined about action effectiveness evaluation, so when you add at least one action with "Verification" active you determinate that a ticket must be sent to VERIFY stage for action evaluation.\\
+Every Action Type has a rule defined about action effectiveness evaluation, so when you add at least one action type defined with "Verification" active, you determinate that a ticket must be sent to VERIFY stage for action evaluation.\\
 You can configure each action type at pHKapa Setup -> <nowiki>http://{your-url-for-pHKapa}/admin/phkapa</nowiki> , more info at [[phkapaadministration#classify_actions|Classify Actions]]\\
-==== Some specific rules at PLAN stage ====
+==== Some specific UI rules at PLAN stage ====
-Close or Verify options are only available when Cause field has values.\\
+Close or Verify menu actions, are only available when Cause field has values, and actions closed.\\
 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 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.\\
@@ Line 167: / Line 160: @@
 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.\\
+===== 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.