Professional Documents
Culture Documents
Navedtra
Navedtra
The JDTA would look like this ...... (not complete example, but a good start to sit down with a Sonar SME to complete)
Compare with Figure 1.
Duty - Sonar
Task - Operate Sonar Equipment - KSATR - Knowledge = Different types of Arrays, Projectors,
Hydrophones. Describe SONAR.
Sub-task - Operate Transmission Sub-system / Equipment
Step - Change to Continuous Wave
Step - Change Frequency Modulation
Step - Change Frequency Pulse Rate
Step - Operate in Single Mode
Step - Operate in Multi-beam combinations
Step - Operate in Omnidirectional Transmission (ODT)
Step - Operate in Passive Mode
Step - Operate in Active Mode
Sub-task - Operate Reception Equipment
Task - Interrupt SONAR Presentations - KSATR - Knowledge = Perform Equations
Sub-Task - Determine range
Sub-Task - Determine bearing
Sub-Task - Determine speed
Sub-Task - Interrupt Principle Display Elements
NOTE: When building Learning Objectives (from JDTA) later in CPM Projects you can choose different Content Types (mix
different ones together), change Action Verbs and use the Platforms option to address specific systems.
Figure 1 - Example of a poorly constructed JDTA that is based on an existing course CTTL (knowledge only)An example of what this one
would look like if done correctly can be found here.
Figure 2 - Example of a poorly constructed JDTA that should drop the "Duties to Task" and current "Task should be sub-task or
KSATR"Besides being knowledge based, a task should never be describe or explain because that's not done on the job.
Figure 3 - A common mistake made by acquisition programs and when looking at multiple rates that perform the same jobs. It goes to lifecycle maintenance, leads to duplicate training being developed and is probable owned by the same Requirements Sponsor anyway. So
ease the job analysis process by combining into one common task (Job could be CSCS Maintenance Rates). Since CPM can now link
multiple JDTA's items together in the Projects tab this is less of a problem.
Figure 4 - Another common mistake is to try and force all of the JDTA work requirements into just the Duty and Task levels of CPM.
Hopefully with the above example (SONAR) you will see how sub-task and KSATR's can be used to make this list more manageable.
Figure 5 - JDTA's are about the work, in this case the CRF Division Officer is probable "Managing the 3M program", SKED is a tool or
"Manage the3M SKED" (other action verbs are possible). I doubt they are "Administer SKED, Administer Advanced Skills Management,
etc....). This a good example of why the ISS (ISD/SAT/LSO) needs to be involved in the process. Based on this JDTA construct, a section
(with an ELO) in Learning Object (LO) Module would be created and would prove very difficult to turn into effective training.
Figure 6 - Stay away from system/equipment specific names. "Operating the Ship Control Console" is just as effective as what is listed
above. CPM in the Data Tab allows multiple platforms, systems, sub-systems, components, non-equipment and environment that can be
used to allow these JDTA items to be used to support current and even future equipment vendors. If one maker has additional capabilities,
you just add them to the list of job task. In CPM projects only select the ones that you will be training to support.
Figure 7 - A common mistake made by acquisition programs are the fact they focus on systems and equipment, not the work. Acquisition
programs are required to complete a Job Task Analysis (JTA). Since multiple program offices might have similar requirements (operating a
crane on CVN-68 class and operating a crane on LPD-17 is different and requires the Sailor to follow different procedures. But the people
doing that work, the safety and foundational training is the same. The Learning Center / NETC are the only organizations that look across
multiple acquisition programs. So it does require the Learning Center to adopt a plan of how JTA data gets migrated over to JDTA data. You
can have multiple JTA's that link to a single JDTA based on a Sailor's rate.
Subject
Author
No Comments
! All Pages
0 - Table of Contents for this
Wiki
1 Start Here to Transfer to
other Wiki (ISD or SOP)
A different look at executing
the E2E process?
A note on the NETC SOP
Conducting an Analysis
(Based on the Work)
Replies
Views
Last Message