This page would be used to broadly review each individual lesson in the training flow. Primary use is to identify problematic lessons/sweatbox scenarios. Information would be derived from Training Tickets dated within the last 90 days.
Average No. of Points of Improvement: I envisioned this as a means of identifying if the sweatbox scenarios are effective in teaching students whatever they are designed to. Originally, I was considering having this list the more commonly used terms across training tickets. Perhaps this metric may not be feasible.
Outstanding Sweatbox Errors: A link to the ticket and a short description of the error. Have an additional field on the training ticket page that will open a ticket on the FACT page. Green checkmark marks the ticket as resolved and removes it from this page. Current TA is OK with leaving this OUT and using the current method (ZTL Discord) for issue reporting.
ADD: Controller Rating Analyzer For Training
This page would serve as a one stop shop for individual students/ratings. The "Next/Previous Student" button cycles between the pages.
RATING OVERVIEW:
The rating overview would show relevant statistics for each rating/major endorsement.
The student overview page would show in-depth statistics for each individual member of the ARTCC. Statistics are color coded based on their relation to the average time for each rating.
Some of the more weird items:
Student Access to Training Score: A comparison of this student's ability to other students of the same rating.
Student Progression Index: THIS SHOULD FILTER OUT MONITORING SESSIONS. The progression index is the number of sessions it takes for student x to get to next milestone over the number of lessons in milestone. For example, a student that takes 20 sessions when 10 sessions are in the flow for the new rating would have an index value of 2.
Time to (Rating) is a counter that starts after the first ticket is submitted. TA should be able to suspend/deactivate to prevent skewing.
jahaight
commented
5 days ago
I don't know where these would go, but:
ADD: Flow Analysis and Consistency Terminal
This page would be used to broadly review each individual lesson in the training flow. Primary use is to identify problematic lessons/sweatbox scenarios. Information would be derived from Training Tickets dated within the last 90 days.
Average No. of Points of Improvement: I envisioned this as a means of identifying if the sweatbox scenarios are effective in teaching students whatever they are designed to. Originally, I was considering having this list the more commonly used terms across training tickets. Perhaps this metric may not be feasible. Outstanding Sweatbox Errors: A link to the ticket and a short description of the error. Have an additional field on the training ticket page that will open a ticket on the FACT page. Green checkmark marks the ticket as resolved and removes it from this page. Current TA is OK with leaving this OUT and using the current method (ZTL Discord) for issue reporting.
ADD: Controller Rating Analyzer For Training
This page would serve as a one stop shop for individual students/ratings. The "Next/Previous Student" button cycles between the pages. RATING OVERVIEW:
The rating overview would show relevant statistics for each rating/major endorsement.
Some of the more weird items: Student Access to Training Score: A comparison of this student's ability to other students of the same rating. Student Progression Index: THIS SHOULD FILTER OUT MONITORING SESSIONS. The progression index is the number of sessions it takes for student x to get to next milestone over the number of lessons in milestone. For example, a student that takes 20 sessions when 10 sessions are in the flow for the new rating would have an index value of 2. Time to (Rating) is a counter that starts after the first ticket is submitted. TA should be able to suspend/deactivate to prevent skewing.