To enter Task Analysis information in VISION:
1.On the Main Menu select "Workbench", then "Analysis Activities" and choose the "Task Analysis" activity. The task analysis activity is actually just a continuation of the job analysis activity. You will use the same Analysis Hierarchy window as used when performing a job analysis.
2.If the Open Analysis Work Area window appears, select the work area that contains the tasks you want to analyze. Then click OK.
3.In the Task Analysis Workbench that appears, expand the hierarchy so that you can see the tasks. Decide which task you want to analyze.
4.Double-click on the text of the task to open the Task Properties workscreen.
5.If needed, modify the task statement (the Text field).
6. Click on the Conditions tab; then enter the conditions under which the task is to be performed (see steps below).
7. Click on the Standards tab; then enter the standards that define the indicators of task proficiency (see steps below).
8.Click the Analysis tab and change the Analysis Status to Developing.
9.Click the OK button to save the task properties.
10.Now you can use the Analysis Hierarchy Assistant to enter the elements (steps) and the skill/knowledge components of the task. Click Node on the Main Menu and select Analysis Assistant from the Main Menu.
11.Once you are finished analyzing the task, double-click on the text of the task and click the Analysis tab. Change the Analysis Status to Reviewing if the task needs to be reviewed or Completed if the analysis is complete. Click the OK button to save your changes.
12.Repeat the process to analyze the remaining tasks.
To enter conditions, follow these steps:
1.Click the New button.
2.In the window "Edit Current Condition:" type in one condition.
3.Click the Save button.
4.Repeat this process to enter additional conditions.
To enter standards, follow these steps:
1.Click the New button.
2.In the window "Edit Current Standard:" type in one standard.
3.Click the Save button.
4.Repeat the process to enter additional standards.
What’s next?
Do you want to produce special documents now? For example, you can produce:
•Job Qualification Card
•Task Performance Evaluation
You may even be able to produce worthwhile Work Procedures.
In order to prepare the documents, you still need to make cross reference links. From the Main Menu, select Cross Reference and Open.
If you're ready to move on to the design activities, select Workbench, Design Activities, and Objective Design from the Main Menu. The first design activity is usually to create a Training Objectives Hierarchy from your task analysis data.
Tips for Performing a Task Analysis
With VISION, you can produce various outcomes directly from task analysis data.
For example, you can produce procedures and on-the-job evaluation checklists (Task Performance Evaluations) directly from the task analysis.
•Ideally, these documents were planned at the beginning of the project and you have set up the project accordingly. This should have occurred while you set up your project. All of this should have happened before the task analysis began. •At this point in the project, you should know whether or not procedures, qualification checklists or other such documents are expected as a result of the task analysis. This is because the data you will collect during the task analysis will be influenced by whether or not such documents will be produced. •If you do not know which procedures, checklists or other documents will be generated from the task analysis, ask the appropriate project team member or supervisor. |
Sometimes a good procedure is all that is required to solve a performance problem or support task performance. Detailed training may not be necessary.
If procedures are sufficient, focus your task analysis data collection on the following information for each task:
•Conditions of task performance •Standards of proficiency •Steps of the task (task elements) •Cross Reference links required for procedures |
As an option, you can include knowledge questions on your Task Performance Evaluations. In that case, you'll need to collect skill and knowledge components that can be used on the checklist. Focus on the critical issues, not the detail.
If Task Performance Evaluations are an expected outcome of your task analysis, you will need the following data for each task:
•Conditions of task performance •Standards of proficiency •Steps of the task (task elements) •Cross Reference links required for Task Performance Evaluations •Critical skill and knowledge components (if you want knowledge questions on the checklist) |
Remember that there are two ways to enter components in the Analysis Hierarchy. One method is to use the Analysis Hierarchy Assistant. The other method is to use the insert operations—which are accessible through either the 'insert' menu items or through the following buttons on the Workbench Toolbar:
•Insert as last child. •Insert as sibling above. •Insert as sibling below. Use whatever method is easier for you.
|
It is usually important and worthwhile to get 'Subject Matter Experts' or others to review and verify the Task Analysis. To assist you in the verification process, you can generate a Task Analysis Verification Form from VISION. To generate this form, follow these steps:
1.On the Main Menu, click Outcomes and then VISION Documents. 2.Click on the Review Forms tab and highlight "Task Analysis Verification". 3.Click the run button and then select all applicable Report Choices. 4.click OK to run the report. This document will provide all of the information needed for verification, in a format that is convenient for Subject Matter Experts (SMEs).
When the task analysis is finally done, you can generate another form from the same list, the "Approved Task List". This report provides a place to get signatures that verify completion and acceptance of the task analysis.
|
Related Topics
How to trace the audit trail of a selected objective
How to color hierarchy components to see selected attributes
Follow the steps below to unconsolidate an analysis component from an Objective:
1.In the Objective Hierarchy window, highlight the objective that contains the consolidated components. 2.In analysis links window (usually located below the hierarchy), highlight one or more of the components that you want to unconsolidate. 3.Right-click on the selected components and choose "Unlink" or "Unlink and Move to Holding Bin" from the popup menu. 4.A dialog box will ask you to confirm if you want to unlink the items. Click the OK button. Alternatively, you can double-click on the objective in Step 1 and click the Consolidation Tab. This tab shows a list of all analysis components that have been consolidated into the objective. To unconsolidate an objective here, right-click on it and select Unlink. The only disadvantage of unconsolidating analysis components here is that you cannot move them into the Holding Bin.
|
To change to another project, follow these steps:
On the project toolbar, simply select another project.
--OR--
1.From the Main Menu, select Project  Change Project. 2.When the list of projects appear, select the desired project and click the OK button. Note: If any windows are open when you change projects, nothing will change in any of the windows. The only indications that you are logged into another project are in the project toolbar and on the Status Bar as shown below.
|
"LIGHTWAVE:LIGHTWAVE" identifies the project that you are currently logged in under (the first LIGHTWAVE) and the project the last selected hierarchy node belongs to (the second LIGHTWAVE). If you were logged into a project called LIGHTWAVE and the last node selected in a hierarchy window belonged to a project called "ELECTRICAL", the text "LIGHTWAVE:ELECTRICAL" would appear in the Status Bar at the lower right corner of your screen. If a Workbench is not open, you would only see "LIGHTWAVE".
If you already have a Workbench open, you can open hierarchy windows in the project you changed to or you can open a new Workbench. If you are working with multiple projects at the same time, we recommend that you have one Workbench open for each project instead of multiple hierarchy windows open from different projects in one Workbench.
|
Almost every type of record that can be created in VISION must be assigned to a project. We say "almost" because there are some instances where a record can be shared across all projects. The following list shows the rules that VISION applies when creating records in VISION.
•Any node created in any hierarchy belongs to the same project as the new node's parent. In other words, if you are logged into project ELECTRICAL and you create a child under a node that belongs to project CHEM, the new child will belong to project CHEM. •When you create a Cross Reference Table, you can choose whether the new table will belong to the project you are currently logged into or whether the new table will be shared across all projects. •A new cross reference item created under a Cross Reference Table will belong to the same project as the table belongs. •A new test always belongs to the project under which you are currently logged. •A new question always belongs to the same project as the objective the question was created for. •When you create a new report, document or search, you can choose whether it will belong to the project you are currently logged into or whether the new report will be shared across all projects. |
Think about the outcomes (special documents) you want