Final APR

334 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
334
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • A commander or HR officer needs to staff a joint mission made up of warfighters from the Army and the Navy. They need to determine what roles need to be filled in the team, select staff to fill the roles, and determine if they are ready, or if training is required. They need to be able to repeat the skill gap analysis process until readiness is reached. In the demonstration you’ll see in a few minutes, we will use the CTRMS solution to take us through these steps, focusing on readying a team that includes a combat medic.
  • This is a straightforward problem, easy to state and understand—what makes it so hard? LMSes all implement competencies in their own proprietary ways; no standards such as SCORM are applied to competency systems. Systems don’t integrate with each other, unless on a case-by-case basis Joint operations involve training data recorded in different systems Army and Navy have different job descriptions and competencies (tasks) Army and Navy have different terminologies Picture – isolation? Non fitting parts?
  • * Store competency taxonomies using RDCEO Discover SCORM packages whose metadata references RDCEO’s. Use vCard to store personnel information Employ IMS Job Header to tie competencies to roles Integrate with Sample SCORM RTE through a REST-based Web service Integrate with Practice ADL-R through http interface Import competency definitions in standard format into Tenereo, aka XML SCORM Studio, Eduworks’ SCORM packaging and editing tool Use Eduworks’ ACE solution for competency translations from one taxonomy to another
  • Eduworks CTRMS solution is in the upper left corner. We also demonstrated at ImplementationFest 2007 an integration with two other prototype teams, from BBN and ECS, to show how our solution ties in with theirs. A video of that demo can be seen at this booth.
  • UPDATE DIAGRAM
  • The source is in C#, runs on .NET 2.0. Integrates through HTTP, some REST-based, some SOAP-based Web services Data stored in XML, XSDs defined by standards or created Custom UI controls
  • A commander or HR officer needs to staff a joint mission made up of warfighters from the Army and the Navy. They need to determine what roles need to be filled in the team, select staff to fill the roles, and determine if they are ready, or if training is required. They need to be able to repeat the skill gap analysis process until readiness is reached. In the demonstration you’ll see in a few minutes, we will use the CTRMS solution to take us through these steps, focusing on readying a team that includes a combat medic.
  • We said we would use testbed data from the Navy, Army, etc. We worked most closely with NAVSEA Keyport. The data was never delivered. We regularly communicated with them, asking for the deliverables, asking for dates for the deliverables, we did not get them. We do not know what the nature of the delay was.
  • Further integrations with personnel system through Learner Information Profiles standard More reporting functions, create/edit data Tools to assist in creating the data models, particularly the competency models
  • Final APR

    1. 1. Competency and Training Record Management System (CTRMS) Joint ADL Co-Lab 2007 Prototype FPR November 28, 2007
    2. 2. This Project is Dedicated to Claude Ostyn <ul><li>1950 - 2007 </li></ul>
    3. 3. Agenda <ul><li>Motivation and Challenges </li></ul><ul><li>Project Goals </li></ul><ul><li>System and Scenario description </li></ul><ul><li>Demo and Results </li></ul><ul><li>Lessons Learned </li></ul><ul><li>Project Team </li></ul>
    4. 4. Motivation and Challenges <ul><li>Basic problem: Find the right people for the job and ensure their readiness </li></ul><ul><li>Challenges: </li></ul><ul><ul><li>Identify skills a team needs </li></ul></ul><ul><ul><li>Identify warfighter skills </li></ul></ul><ul><ul><li>Identify skills when different vocabularies are used for the same or similar things </li></ul></ul><ul><ul><li>Identify, assign and engage in focused training – “Time is readiness!” </li></ul></ul><ul><ul><li>Provide useful overview of readiness </li></ul></ul>
    5. 5. It all looks great on paper <ul><li>But for this to work on a computer </li></ul><ul><li>“ Competencies” must be stored in a way that can be used by multiple system components </li></ul><ul><li>Taxonomies of skills from different agencies must be codified and correlated </li></ul><ul><li>Individuals / roles must be chosen based on contributions to team readiness </li></ul><ul><li>Training must be matched to skills and skills must be recorded when training is completed </li></ul><ul><li>“ Training” includes immersive training </li></ul><ul><li>Information on readiness must be formatted in ways that make sense </li></ul>
    6. 6. What we set out to do Goals and Requirements from Phase 1 and Phase 2
    7. 7. Phase I Goals <ul><li>Solve practical problems in readiness and training </li></ul><ul><li>Research and solve problems concerning storing , mapping and “ rolling up ” competencies. </li></ul><ul><li>Support joint training scenarios </li></ul><ul><li>Develop and demonstrate an SOA solution </li></ul><ul><li>Integrate multiple systems : </li></ul><ul><ul><li>Competency and training management </li></ul></ul><ul><ul><li>Training systems </li></ul></ul><ul><ul><li>SCORM Runtime Environment </li></ul></ul><ul><li>Use NAVSEA and TRADOC test beds </li></ul>
    8. 8. Further Goals from a proposed Phase II <ul><li>Extend scope to more service scenarios and systems </li></ul><ul><li>Support team competencies. </li></ul><ul><li>Handle and respond to queries about competencies </li></ul><ul><li>Apply to experiential training </li></ul><ul><li>Integrate with Personnel Management systems </li></ul>
    9. 9. And last but not least … <ul><li>Provide JADL with feedback and recommendations on applications of standards to competency management to integrated architectures </li></ul>
    10. 10. What We Did <ul><li>Met all Phase I (and some Phase II) goals* : </li></ul><ul><ul><li>Store and manage competencies using RCD </li></ul></ul><ul><ul><li>Integrate with RTE, SCORM 2004 tool, and other Prototypes using Web services </li></ul></ul><ul><ul><li>Mapped taxonomies using semantic technologies </li></ul></ul><ul><ul><li>Developed content using (commercial version evolved from) XML SCORM Studio </li></ul></ul><ul><ul><li>Built system to support joint training scenarios </li></ul></ul><ul><ul><li>System answers queries concerning individual competencies & supports team concepts </li></ul></ul><ul><li>Successfully applied relevant standards </li></ul>* Except for acquisition of data from TRADOC / NAVSEA
    11. 11. System Description Competencies & Maps LMS (SCORM RTE) Personnel Management (Currently Stubbed) IMMERSIVE TRAINING SYSTEMS Integration through Web Service Calls Taxonomy mapping done using LSA ADL Registry 11/26/2007 Eduworks Contributions to ECS Team USER INTERFACE
    12. 12. Scenario <ul><li>Mission </li></ul><ul><li>Team </li></ul><ul><li>Staff </li></ul><ul><li>Readiness </li></ul>
    13. 13. Motivation <ul><li>Differences in: </li></ul><ul><ul><ul><li>Data </li></ul></ul></ul><ul><ul><ul><li>Terminology </li></ul></ul></ul><ul><ul><ul><li>Jobs </li></ul></ul></ul>
    14. 14. Goals <ul><li>Apply standards, specifications </li></ul><ul><li>Integrate systems, data </li></ul><ul><li>Research mappings </li></ul><ul><li>Implement roll-up </li></ul><ul><li>Support joint training </li></ul><ul><li>Contribute to IPA improvements </li></ul>
    15. 15. System Functionality <ul><li>Manages lists of individuals and roles </li></ul><ul><li>Manages skills needed for a mission (including “auto staff”) </li></ul><ul><li>Translates skills from different agencies </li></ul><ul><li>Enables selection of individuals </li></ul><ul><li>Does team skill gap analysis </li></ul><ul><li>Searches for training in Practice ADL-R </li></ul><ul><li>Recommends training interventions </li></ul><ul><li>Retrieves status of skills from RTE </li></ul><ul><li>Provides & updates readiness overview </li></ul>
    16. 16. JADL 2012 Integrated Prototype Architecture (IPA) – Baseline Model Web Browser Lobby Distributed Training Event Coordination Service  Schedule Data  Access Learning Content Schedule Training Events Sequencing SCO LSF 3 SCO SCO Global Learner Profile (LP 1 )/SSP 2 Service Learning Management System LTP 4 SCORM Course Learner LP 1 & LSF 3  Attend Training Events  Learner Profiles   State Data   LP 1   State Data  LP-Learner Profile SSP-Shared State Persistence LSF-Lightweight Scenario Format LTP-Local Training Package  Synchronize  Run - Time Design - Time LSF 3 Repository Instructional Designers Content Creators Programmers ADL Registry Content Repositories Create Local Training Packages Policy Makers Field Instructors Rapid Scenario Development Tools Rapid Content Development Tools HR and Competency Management Systems Mission Essential Task Lists Deploy Rapid-Developed Courseware Live Event Game Other… Simulation BBN Integrating Simulation-Based Training ECS Learner Assessment Data Model & Authoring Eduworks Competency & Training Record Management System
    17. 18. Standards & Specs Used <ul><li>RCD (Reusable Competency Definitions) </li></ul><ul><li>SCORM </li></ul><ul><li>vCard </li></ul><ul><li>IMS Job Header </li></ul><ul><li>LOM </li></ul>
    18. 19. Systems used <ul><li>SCORM Sample RTE </li></ul><ul><li>Practice ADL-R </li></ul><ul><li>Eduworks Tenereo* </li></ul><ul><li>Eduworks “ACE” technologies** </li></ul><ul><li>ECS & BBN systems for demo </li></ul>*Commercial version of XML SCORM Studio independently developed by Eduworks ** Automated Content Enhancement: Applications of semantic technologies developed independently by Eduworks
    19. 20. Skills Mapping using LSA <ul><li>Latent Semantic Analysis: Matches text based on tendency to appear in the same context in domain-specific documents </li></ul>
    20. 21. Competency Mapping and Systems Integration <ul><li>Roll-up and maps based on Ostyn models (with simplifications) </li></ul><ul><li>Joint training scenario based on Army and Navy training </li></ul><ul><li>RTE Web service </li></ul><ul><li>Vcard used to stub personnel management system </li></ul>
    21. 22. Programming Languages, Protocols & Frameworks <ul><li>C# </li></ul><ul><li>.NET 2.0 </li></ul><ul><li>HTTP, REST, SOAP </li></ul><ul><li>XML, XSD </li></ul><ul><li>Custom UI controls </li></ul>
    22. 23. Demo <ul><li>Mission </li></ul><ul><li>Team </li></ul><ul><li>Staff </li></ul><ul><li>Readiness </li></ul>
    23. 24. Results & Lessons Learned <ul><li>Obtaining test bed data was problematic </li></ul><ul><li>One year is short: need bridge to commercialization </li></ul><ul><li>Ostyn framework worked </li></ul><ul><li>Web services approach worked </li></ul><ul><li>Separating competency management from learning management has advantages </li></ul><ul><li>Staffing models are still too simplistic </li></ul><ul><li>Developing taxonomies is large challenge </li></ul><ul><li>Semantic techniques are promising </li></ul>
    24. 25. Future <ul><li>Continue to develop to support DoD & Government requirements </li></ul>
    25. 26. Credits
    26. 27. Questions?

    ×