Academic ADL Co-Lab Partnership Conference Call

1. Academic ADL Co-LabPartnership Conference Call Monday, August 28, 20001:00 PM CDT www.adlnet.org

2. Welcome • Academic ADL Co-Lab Leadership Team • University of Wisconsin • Wisconsin Technical College System • Higher Ed Partners • Pending Partners • eArmyU Team • Other Co-Labs www.adlnet.org

3. Penn State University of California – Irvine University of Washington Rochester Institute of Technology United States Open University Mississippi State University University of Nebraska – Lincoln Carnegie Mellon University University of California – Berkeley North Harris Montgomery Community College District University of Maryland University College Central Texas College Iowa State University Academic ADL Co-Lab Partnerships www.adlnet.org

4. Agenda • ADL Overview • Co-Lab • Status • Plans • Opportunities • Discussion www.adlnet.org

5. Home Field Distributed Learning Distributed Simulation Performance Assessment School In Transit Office Embedded Training Digital Knowledge Libraries Provide access to the highest quality education and training, tailored to individual needs, delivered cost effectively, anywhere and anytime. The ADL Vision www.adlnet.org

6. ADL Strategy • Exploit existing network-based technologies • Create platform-neutral, reusable courseware and content to lower costs • Promote widespread collaboration to satisfy common needs • Enhance performance with emerging and next-generation learning technologies • Develop common specifications and standards that drives COTS product cycle • Provide incentives for organizational and cultural change www.adlnet.org

7. ADL Functional Requirements Accessibility: access instructional components from one remote location and deliver them to many other locations Interoperability: use instructional components developed in one location, with one set of tools or platform, in another location, with a different set of tools or platform Reusability: incorporate instructional components into multiple applications Durability: operate instructional components when base technology changes, without redesign or recoding Affordability: increase learning effectiveness significantly while reducing time and costs www.adlnet.org

8. ADL Co-Lab Goals • Develop and refine the SCORM • Assess ADL tools and prototypes • Facilitate collaborative resource sharing • Collect and disseminate data and lessons learned • Conduct tutorials and demonstrations • Support and advise federal, state, and local agencies www.adlnet.org

9. Expanded ADL Co-Labs Academic ADL Co-Lab Higher Ed Focus with Partners Accredited degrees, certification ADL Co-Lab Hub Policies, Tools, and Standards DoD-Federal Integration ADL Portal and Clearinghouse JOINT ADL Co-Lab Military Services Training Systems Acquisition Community - - - - - - - - - - - - - - - - - $$ Incentive Funds www.adlnet.org

10. Plugfests • “Really a wonderful thing – so simple” • “Opportunity to personalize content to learner” • “Potential to increase level of competition to provide quality content” • Very “positive experience” • “Elegant system for interoperability” • “SCORM document is tremendous” • “SCORM is going to make it a lot easier for us to distribute our content.” www.adlnet.org

11. Academic ADL Co-Lab • Research and development of advanced learning technologies • Assess ADL compliant tools • Conformance testing for learning objects • Research and evaluation of intelligent tutors • Application and evaluation of assessment tools • Learning Management System evaluation www.adlnet.org

12. http://wiadlcolab.org • [PlaceWare Web Page. Use PlaceWare > Edit Slide Properties... to edit.]

13. Academic Co-Lab Status • Plugfest 2 • Funding • Staffing • Labor project • LMS (DAU) • ADL / ET • Weekly newshttp://wiadlcolab.org/news www.adlnet.org

14. http://www.trainingsystems.org/events/adlc0900/adlc_front.ht...http://www.trainingsystems.org/events/adlc0900/adlc_front.ht... • [PlaceWare Web Page. Use PlaceWare > Edit Slide Properties... to edit.]

15. Plans • SCORM • Content – Learning Objects • Repository • LMS • Research • Assessment www.adlnet.org

16. Opportunities • SCORM • Best practices • Access • eArmyU www.adlnet.org

17. eArmyU • Integrator • Aggregator • SOC • Exclusive vs. non-exclusive www.adlnet.org

18. http://www.soc.aascu.org/ • [PlaceWare Web Page. Use PlaceWare > Edit Slide Properties... to edit.]

19. eArmyU Discussion • Claudine - UMUC: Interest, but with a team - by end of week or early next week • How work together? • Assuming that the integrator/aggregator - hope for a role for Co-Lab • Other option is to work with a single integrator/aggregator • Mary Beth: Berkeley - Sloan Foundation looking at downstream discussions • Chris: RIT - contact with similar list - Global University Alliance (GUA) - 9 universities - need competencies for modular levels www.adlnet.org

20. Poll: What is your primary area of interest? #1 #2 • Standards (IMS / SCORM) 2 1 • Learning Objects 1 3 • Repositories 4 0 • LMS 1 1 • Best Practices 0 0 • Content 2 1 • Research and Assessment 1 2 www.adlnet.org

21. General Discussion • Dan - CMU - Educating the rest of the community or what this is and what it isn't - Off base descriptions • Administrative understanding • Content & repositories - running LMS for 5 years now - significant resistant from faculty to commit to rules based system since it requires preparing ahead of time • Hal - UWSA - modular content - what is the hurdle to Dan's concerns • Chris - building knowledge base - have to do business in a different way - different • Looking forward to figuring out together • Claudine - request from faculty to share modular content - people want to learn from what others have done - discipline focused • Mike - concern about how we identify the meta levels - technical vs. non-technical - Need to figure out how we are to relate and create sub-discussion groups www.adlnet.org

22. Poll: How often would you like to meet? • Monthly 5 • Bi-monthly 4 • Quarterly 2 • As needed 1 • Don't know 0 www.adlnet.org

23. Wrap • Tool bash session possible in late October in Alexandria Co-Lab (week Oct. 23?) • Technical meeting of IMS TWG in September • Very little academic participation - being driven by vendors • Call for academic involvement • We will let partners know of developments www.adlnet.org

24. Contacts • Ed Meachen – emeachen@uwsa.edu • Judy Brown – jbrown@uwsa.edu • Mike Offerman – offerman@learn.uwsa.edu • http://www.wiadlcolab.org • http://www.adlnet.org www.adlnet.org

25. Questions / Discussion ? ? ? ? ? ? ? ? www.adlnet.org

26. ADL Co-Lab Functions • Cooperate with industry and academia to develop common guidelines for ADL; • Perform technical evaluations of ADL tools and prototypes; • Perform content and training effectiveness evaluations of ADL tools and prototypes; • Facilitate collaborative partnerships and resource sharing among all stakeholders www.adlnet.org

27. ADL Co-Lab Functions • Collect, coordinate, and disseminate data and lessons learned; • Conduct tutorials and demonstrations of ADL applications and technologies; • Support and advise federal, state, and local agencies on development and implementation of ADL. www.adlnet.org

28. www.adlnet.org