Action Plan
This routine aims to register remedial actions, ancillary action and improvement action to be used in the found occurrences/non-conformance.
Actions registered with execution term, its respective phases and closings, being that the proper System create identification codes in sequential form automatically.
When registering Action Plans, note the registration of the following items:
| • | Actions/Phases |
| • | Causes |
| • | Documents |
| • | Costs |
| • | Teams |
| • | Occurrences/Non-compliance |
After informing Action Plan data, the System automatically sends, by e-mail, pendings to the respective responsible people, just after this person defines it as Proceed.
To indicates if action plan phases will be available after being classified as Proceed, the System verifies if contents of MV_QNCIOPC parameter is set as 1.
Parameter MV_QNCIOPC includes an Action Plan in a direct manner or only by Occurrence/Non-Conformity Forms.
When a user that is not responsible for the Plan or for one of the Phases tries to see a secret Action Plan through the Secrecy? field, the System informs which users are authorized to perform the activity, not allowing that data be seen. |
When there is integration between SIGAQNC x SIGAPMS, the system informs which available resource that has the necessary skills to perform the task, considering deadline and duration, making possible to allocate the resource which fits better to this task. |
Procedures
To register an action plan:
| 1. | In the maintenance window of Action Plan, click Add. |
The system displays the add screen.
| 2. | Fill out data according to field help. |
| 3. | In Related Features, there are some options to register its respective items: |
| • | Causes |
| • | Costs |
| • | Teams |
| 4. | Check data and confirm Action Plan adding. |
The Action Plan cannot be deleted while it is linked to the transactions. |
When viewing the register, notice that, on the upper part of the screen, are shown information on the client in question. But it is required that the parameter MV_QTMKPMS is configured equal to 4, indicating the integration between the modules PMS, TMK and QNC.
See also
To query the registered Action Plans, the available reports are:
To check the registering of Occurrences/Non-Conformance Forms, query the routine Occurrences Non-Conformance Forms.
Know the Steps/Phases Models, through the topic Steps/Phases Models.