On this screen, you can set the criteria for determining the carrier model level.
Set the method for determining the level for each second level of the career model.
The available methods are as follows:
・Average value
The standard judgment method for SkillNavi. The level is judged based on the average of the skill answer values in the tasks associated with each specialty.
The average value is tallied for each task, and if the judgment conditions are met for all tasks within the specialty, the level of the specialty is judged.
・Number of clear conditions
The level is judged based on the number of skills that meet each answer rank.
Judgment is made for each task classification, and this judgment method sets the number of skills required for level judgment, such as Level 1, where the condition is three R1 skills and two R2 skills.
・Task level
A judgment method that uses the task level (level judged for each task) that is automatically judged based on the answer value as the condition.
For each associated task, set the arbitrary level of that task as the judgment condition.
・Reuse judgment level
A judgment method that uses the level acquisition of other career models as a condition. This is a special judgment method in which the level is judged recursively at the time when the level is judged in other career models, rather than directly associating it with tasks.
・Weighted average
A judgment method that uses a weighted average that weights the average answer value for each task.
For each task at the lowest level that makes up the second tier of the relevant career model, you specify the point allocation ratio taking into account weighting (how many points to allocate with the total being 100).
After selecting the assessment method you want to use for each task at the second tier of the career model (e.g. area of expertise), be sure to click the "Update" button at the top of the screen.
You will be redirected to the screen where you can actually set the judgment conditions.
For details, please refer to the page on configuring judgment condition patterns.
In addition to the judgment conditions, you can also place restrictions on level acquisition.
・Add a child element
The following four items can be set as level restrictions.
Career model (assessment level)
Exam
Training
Qualifications
Unless you meet the level restriction conditions, you will not be judged at that level even if you meet the assessment conditions.
For example, in the example below, the required number is "2", so you will not be judged at Level 1 or above unless you score 70 points or more on the "Programmer Promotion Criteria" exam and obtain the "Oracle Master Bronze" qualification.
Also, if the required number was set to "1" in the example below, the level restriction conditions would be met by achieving either the exam or qualification displayed.
To add a level restriction, select the item you want to set as the upper limit from "Add child element", enter the required score in the case of an exam and click the "Update" button.
To delete a restriction you have already set, click "Delete" to the right of each item to remove it from the table, and then click the "Update" button.
・Add a child group
By adding child groups, you can set level restriction conditions hierarchically.
For example, in the example below, the top required number is "3", so you will not be judged to be at Level 1 or above unless you score 70 or more on the "Programmer Promotion Criteria" exam, obtain the "Oracle Master Bronze" qualification, and achieve the child groups listed below.
To achieve a child group, you must either take the "Data Structures and Algorithms using Java" training course or obtain the "Fundamental Information Technology Engineer Examination (FE), formerly known as "Type 2 Information Processing Engineer", as the required number is "1".
Click "Add child group" to add a child group, add the child elements required for the level restriction, and specify the required number for each group.
Carrier models will be reassessed for all users at once.
This function will reassess all at once if, for example, you have changed the judgment condition pattern and recreated the judgment condition data.