Collective Generation of Evaluations by the Evaluators Information
When in Others > Indications, Information tab, the Management per Competencies field is set as 3-Activate without legacy, this window is not displayed.
Through this window, it is possible to generate evaluations (performance, excellence and knowledge) automatically for several workers, based on the menu items of the evaluators information (Jobs and Salaries: Skills > Evaluations > Evaluators Information, and Trainings: Development > Performance and Competency Evaluation > Evaluators Information).
Important
This menu item will be presented only when the Evaluation Restriction field = N or when the logged user is an ADM (system administrator) or COORDINATOR.
Only users COORDINATORS may process(save) or delete(Delete button) evaluations presented on this window.
Identify the evaluations to be generated with a cycle code.
Important
This field will only appear if in the General Settings Cycle is marked as "S".
In the Trainings module, this field will be available only if the Jobs and Salaries module is integrated with the database.
Defines in which competence the evaluations will be generated.
Important
When the field Cycle is displayed, the month and year of Cycle start will be loaded in the competency field. If the user wants to report another period the system will allow, since it is within the period comprised by the beginning and end date of the cycle.
Please state the deadline for the evaluation to take place.
Important
This field may be left blank, in this situation the evaluation may be done in any date.
For Knowledge Evaluations
The knowledge to be generated in the evaluations for each worker will be searched according to the definition in the Considers Knowledge Requirements field, in Other > Indications.
Indicate whether to generate Self-Assessment *, or evaluation of Superior, or Subordinate, Charge, Client, Supplier, Instructor or Consensus. It will be possible generating only one type of evaluator at each time.
Notes
- The consensus evaluation does not use the evaluators information, the generation occurs as follows: the last subordinate evaluation of each evaluated returned from the selection is checked (considering the indication of completed evaluation), from this last evaluation it is checked if still not have a consensus evaluation generated for the evaluated and for the same evaluator with date greater than the subordinate’s last evaluation found, and if it is not found, it means that the consensus evaluation must be generated, then, the system will present to the user the evaluated from the selection and the evaluator who has evaluated the subordinate.
- The self-evaluations will be generated from the similar job, superior, subordinate, customer, supplier and instructor evaluations already generated and that still do not have a self-evaluation registered with posterior date.
That is, the system generates self-evaluations only for workers involved in the evaluation process (who have already been evaluated).
Example if a subordinate evaluation has been generated by considering sampling, in this situation, not all subordinates have been evaluated by the superior, then, the self-evaluation must be generated again for the workers who started the process and were evaluated (who were picked by sampling). - The cycle will be considered when consulting the previous evaluations of each evaluated in the generation of Consensus and Self-Evaluation evaluations when the Identifies Cycle field (from the window of Definitions > Skills > Evaluations > Definitions) is defined as 1 or 2.
Indicate whether you should consider the last completed subordinate evaluation of the assessed to generate the consensus assessment, if this assertion is not set, will generate the consensus assessment based on the last subordinate assessment of the independent evaluator whether it is completed or not. Note: This indication will be enabled only when the evaluation focus is Consensus.
Group (Individual, Org. Unit/Job and Org. Unit)
When indicating this option, the system will search for evaluators also in the org. unit/job information and org. unit information, even if an evaluator is found in the individual information. All evaluators who are found in the three registered (individual, org. unit/job and org. unit) will be the evaluators of the evaluated in question, that is, even if an evaluated has an evaluator individually registered and this same evaluated has an org. unit who evaluates it, all workers of the org. unit and from the individual information will be the evaluators of this evaluated, if the option is not indicated only the worker individually registered will be the evaluator, disregarding the information per org. unit.
Important
This option will be enabled only when the focus of the evaluation is superior, subordinate, client or supplier, and will be checked for the top and client types, because in these cases it is more common for the evaluator entries to be grouped.
Sets whether the ranges entered on the Selection and in the fields of Screen Selection will be considered for the Evaluator, Evaluated, or for Both.
By selecting the "Both" option, the system will make the same consistency for both the evaluator and the evaluator. As for example, when performing a filter using the option "Both" and informing in the field Register the value "10", both the appraiser and the appraiser must have this registration number in order for them to be presented in the result.
Important
The existing coverage on the generation screen will be updated with the ranges selection button.
The sampling fields limit the quantity of evaluations that will be generated. If must not generate 100% of evaluations, they will be randomly generated.
Per Evaluated
Defines that the values reported in the % fields, Minimum and Maximum will be applied Per Evaluated.
Per Evaluator
Defines that the values reported in the % fields, Minimum and Maximum will be applied Per Evaluator.
%
Defines the percentage of all the possible group of evaluations (according to the ranges and filters defined on the window) which must be generated.
Minimum
Defines the minimum quantity of all the possible group of evaluations (according to the ranges and filters defined on the window) which must be generated.
Maximum: Defines the maximum quantity of all the possible group of evaluations (according to the ranges and filters defined on the window) which must be generated.
In the image below, it is possible identifying two highlighted areas (green and yellow). In each of them there are 3 different evaluations (knowledge, performance and excellence) for a certain worker evaluated. Observed both groups, we see that they are six evaluations (these six represent all the possible group of evaluations according to the ranges and filters defined on the window), for two workers and all with the same evaluator.
However, these evaluations not necessarily need to be generated, the system can pick some of them to be registered on the database, counting on the sampling routine. Assuming that the following situation is presented:
In this case, the system will pick (Per Evaluator) 50% of the evaluations from the example to be generated. But the routine does not see the result as a group of 6 evaluations, but as 3 groups with two evaluations each (all them with the same evaluator and with the same type of evaluation, only with different evaluated). That is, in this sortition of 50%, considering the case presented, the system will generate ONE Knowledge evaluation, ONE Performance evaluation and ONE Excellence evaluation.
The minimum and maximum fields can also be used in this case. For example, if the user uses the following combination:
The system will understand that a minimum of 8 and a maximum of 10 evaluations should be available to be generated. Thus, in the example, the query would return a blank result because the number of possible evaluations (2 of each type) did not achieve the desired minimum (8).
In the case above, the system will make the draw for the evaluations by selecting 50% of them (what will return 1 evaluation of each type), not reaching the desired minimum of 8 evaluations.
In generations of evaluation where the focus of the evaluation is equal to Similar Job, the Both option is presented in the sampling, in addition to the Per Evaluated and Per Evaluator options.
Referring to the evaluation per Similar Job, the LOG will be generated when the sampling (by some reason) cannot generate the evaluations.
The range will filter evaluated and evaluators, since that in this case the involved evaluate themselves among them.
When set to generate the Knowledge evaluation, it is necessary to report if only the knowledge must be presented. Required, Desirable or Both, as defined in the Knowledge information with the Technical Skills and Requirements.
Consider Laid-off in the Month
Determine whether or not the system should allow the generation of assessments for those dismissed on the screen.
Important The system will check until the last day of the period reported, in order to see which are the laid-off of the month.
When set to overlap the existing register, the system will overlap any register that is found for the same worker with the same competency and with same evaluation focus.
Important If this option is not set, and the system finds an identical register, it will position the new evaluation in another Sequence, for example to 2.
Selection Button
Sets the evaluator or evaluator scope or both.
The ranges existing on the generation window, in the Ranges of Selection, will be updated with the ranges reported in the Selection button.
In these fields it is possible to filter the workers to which the evaluations will be generated.
They can be filtered by the ranges below:
- Batch (when reporting a batch of Workers in the Company, Type and Information field will be disabled)
- Company
- Branch
- Type
- Information
- Org. Unit
- Job
- Schedule
- Bond
Identification Number
When generating evaluations for one or more workers, they will be identified by an Identification Number (as detail below), which can subsequently be used to Exclude collectively in the evaluations generated with a same identifier.
After clicking the Show button, the data are loaded to the Evaluations grid (the number that is displayed next to the grid is the quantity of evaluations that can be generated).
Grid
When it is not possible generating evaluations for a certain worker, its line is in red in the grid, and the reason of this impossibility is showed in the Note field (as the example in the image above).
The following rules per process are available for this window:
92-Inclusion of Knowledge Assessment
94-Exclusion of Knowledge Assessment
95-Inclusion of Performance Evaluation
97-Exclusion of Performance Evaluation
98-Inclusion of Assessment of Excellence
100-Exclusion of Evaluation of Excellence
437-Collective Ratings Filter
616-Generation Ratings - Employee Upload
Veja também:
English
Español
