v0.7.1
Accomplishments represent specific milestones that the trainee can accomplish. An accomplishment can represent a correct action, an incorrect action, or even just a change in program state that isn't the direct result of a trainee action. Accomplishments themselves are not used for scoring or presenting information to the trainee, but they are vital in ensuring the other parts of the scenario are triggered and presented correctly.
Accomplishments can only be completed once. They have two main purposes:
Name
GainSA
Criteria
CheckOneline
Description
The trainee must check onelines to gain Situational Awareness. The alarms are shown at Kabwe and Leopard, so the trainee must check these onelines.
Requirements
Kabwe, Leopard
Partial
False
Phase
I
ITS Score
10
This accomplishment for the transmission simulator is completed when both the Kabwe and Leopard onelines have been looked at, meaning that the trainee has finished the GainSA milestone.
An Accomplishment is represented by its name and its Completion Criteria. Multiple accomplishments can have the same name, but if they do, they must have different criteria. (Example: GainSA / CheckOneline and GainSA / OpenWindow.) Accomplishments with the same name are considered to represent the same milestone, and so they should have the same prerequisites, antirequisites, score, and phase. Additionally, when any accomplishment is completed, all accomplishments with the same name are also marked as completed.
The Completion Criteria is the general type of action that must be performed. For example, CheckOneline means that the accomplishment is completed when the trainee checks a station line. Some Completion Criteria support Requirements, which add specificity to the triggers. For example, adding the Kabwe and Leopard requirements means that accomplishment will only be crossed off when both of those specific onelines are checked.
Not all criteria support requirements. If a criteria is selected but no requirements are provided, the accomplishment will be completed the next time the most basic criteria is met.
See the Completion Criteria page, as well as the definitions on your simulator page, for a list of available criteria.
Accomplishments, Violations, Communications, Coaching Hints, and Checks can all have Prerequisites and Antirequisites. These reference Accomplishments by name and determine when the entity can be triggered or displayed. All prerequisite accomplishments must be fully completed, and no antirequisite accomplishments can be fully completed. If the prerequisites or antirequisites for an entity are not fulfilled, that affects the entity in the following ways:
This allows accomplishments to control the flow of training, despite not directly being used in scoring.
The name FINISH is a special case for accomplishments. When any accomplishment with this name is completed, GOAT will end training and progress to the After-Action Report. This can be used to create custom methods for completing a scenario, such as communicating correctly that the scenario has been resolved.
An accomplishment with the name FINISH and criteria CompleteScenario is created by GOAT at the start of training, which ensures the Done button in the simulator always triggers the After-Action Report.