LRS - What you need to know - at Learning Solutions Conference
•Als PPTX, PDF herunterladen•
1 gefällt mir•826 views
This document summarizes different approaches to integrating an LRS (Learning Record Store) with an LMS (Learning Management System) to leverage xAPI (Experience API) data. It describes 5 models ranging from keeping the LRS and LMS separate to fully integrating them. It provides advice on choosing an approach, focusing on exporting data, flexible reporting, and starting small before expanding. The overall message is that an LRS allows for richer learning data collection, and its integration requires planning reporting and data management.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (11)
Ähnlich wie LRS - What you need to know - at Learning Solutions Conference
Ähnlich wie LRS - What you need to know - at Learning Solutions Conference (20)
Mehr von TorranceLearning
Mehr von TorranceLearning (18)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
LRS - What you need to know - at Learning Solutions Conference
- 1. Session 215 LRS: What you need to know Rob Houck, LearnShare Megan Torrance, TorranceLearning Orlando, FL • March 16 – 18, 2016
- 3. Megan Torrance CEO, TorranceLearning Rob Houck CTO, LearnShare LLC
- 4. What is xAPI? Answer #1 Next-generation SCORM Answer #2 A standard way of recording any learning experience to give a more rich picture of the development path. Answer #3 A protocol for sending, storing and retrieving data about learning and performance experiences: activity statements Answer #4 “the holy grail” where we can correlate job performance data with training data to assess people and training effectiveness
- 5. What are you doing with xAPI? I can spell xAPI. I am sending xAPI statements. I am reporting on the xAPI statements that I’m sending. I am making decisions based on what I’m collecting in the LRS.
- 6. What is an LRS? Answer #1 Learning Record Store Answer #2 It’s where we store the training data. Answer #3 It’s a database where we send xAPI activity statements and retrieve them later for decision-making. Answer #4 It’s a next-generation LMS.
- 7. The LRS is all about making xAPI work. • We want beautiful analysis • We want data justifying the training we’re delivering. • We want data to understand learner use – so we can optimize the training itself.
- 10. Your LMS today … really an ecosystem Users Courses Enrollments SCORM Data Reporting Courses Classes Certs Badges SocialLearning Messaging Performance,Talenthooks Reporting Games Sims Perf Supp Dash boards eCommerce Import/Export Biz Data
- 12. Your learning platform with xAPI Users Courses Enrollments SCORM Data Reporting Courses Classes Certs Badges SocialLearning Messaging Performance,Talenthooks Reporting Games Sims Perf Supp Dash boards eCommerce Import/Export Biz Data LRS SCORM data
- 13. The managed ecosystem approach Users Courses Classes eCommerce LRS Dash Boards Games Sims Perf Supp Reports Social Performance, Talent Other Biz Data Other LRSes LMS
- 14. All this is AWESOME but… Why don’t we just store the xAPI data in the LMS?
- 15. SCORM is structured data SCORM has “buckets” for everything it needs to store. So where do you put “experience” data? It doesn’t fit the mold! Learner Course Time Score Status Houck, R Compliance 101 28 M 85 Pass Simpson, H Compliance 101 35 M 90 Pass Torrance, M Compliance 101 26 M 70 Fail
- 16. xAPI is semi- unstructured data It starts out ok … then gets messy. Actor Verb Object Context Houck, R completed Compliance 101 85% 28M Pass Simpson, H practiced Frosting a cake 35M Pink Torrance, M read Tin Can for Dummies 4 stars
- 18. xAPI is semi- unstructured data • Unlike SCORM, xAPI doesn’t need to understand what data is being stored ahead of time. • All this requires an entirely new method of storing this data – thus the LRS. xAPI (and the LRS) allows storage of information that was previously impossible (or really, really hard) to collect.
- 19. If you don’t have an LMS and you don’t have SCORM … • Publish to xAPI. • Get an LRS product. • Rock and roll. • Grow over time. If you’re ready to dive in, adding an LRS is a relatively fast and easy way to go.
- 20. If you already have an LMS and you do have SCORM … • Do you need an LRS today? • If what you get out of our elearning today is just fine, no. • Will you want an LRS in the future? • Probably! • Listen for the right project • As course vendors start to leverage the real power of the tools, you don’t want to be on the outside.
- 21. But don’t limit yourself to thinking inside the course. • There’s a lot going on outside of your courses: • Checklists & job aids • Social interaction • Mentoring • Observations • Assessments • Performance & talent mgmt • Actual work behavior stored in other systems • Results of actual work behavior stored in other systems
- 22. A few models 1. LRS, LMS 2. LRS LMS 3. LRS & LMS BI 4. LMS LRS 5. LMS/LRS + TMS + PMS
- 23. LRS, LMS Side-by-side THIS IS YOU IF … • You’re experimenting. • You just bought an xAPI based tool. WHAT’S GOOD ABOUT IT? • First starting out • Lots of flexibility • Change it easily 1
- 24. LRS, LMS Side-by-side BUYERS GUIDE • Buy, don’t build • The LRS can be invisible • Start small & cheap, then scale up • Focus on exporting your data Tip: Think through your index values – they have to line up. 1
- 25. LRS LMS THIS IS YOU IF … • You use the LRS for what it does best (collect data). • You use the LMS for what it does best (manage training). • You might have multiple front end xAPI tools all on different LRSes. • You need that “completion” in your LMS for reporting & learning plans. WHAT’S GOOD ABOUT IT? • You have a single source of truth: the LMS 2
- 26. LRS LMS BUYER’S GUIDE • Focus on exporting your data • Limit the number of systems and moving parts to preserve your sanity • Figure out what constitutes a ”course” and a “completion” Tip: You’re not going to be happy in this spot for a long time so don’t over-invest emotionally. 2
- 27. LRS to BI THIS IS YOU IF … • You’re already spending a lot of money on BI WHAT’S GOOD ABOUT IT? • The BI team is already at “the table” • The BI team is already good at connecting multiple data streams 3
- 28. LRS to BI BUYERS GUIDE • That’s what your BI is for – work with them, not against them. • Focus on exporting your data -- keep your data orderly. • Don’t worry too much about analytics inside the LRS. Tip: Talk to BI about your unstructured data or all you’ll get out of them is SCORMy stuff. 3
- 29. LMS LRS THIS IS YOU IF … • You have multiple LMSes. • You still have legacy LMS data. • If you’re getting better reporting and visualizations from the LRS. • You want all the richness of your xAPI data. WHAT’S GOOD ABOUT IT? • Start comparing experience data with SCORM completion data 4
- 30. LMS LRS BUYER’S GUIDE • Focus on reporting since every curriculum will send different data. • Plan to add more data streams once people see this because it’ll be super cool. Tip: Demand amazingly flexible reporting. 4
- 31. LMS/LRS THIS IS YOU IF … • It’s 2017. • You’ve moved past the LMS as the center of the universe, but it’s still pretty important. • You can manage structured + unstructured data together • WHAT’S GOOD ABOUT THIS? • Everything’s in one place. • You’re able to do your own people- based BI. • You can pull in other data streams (Sf.com, Oracle, SAP…) 5
- 32. LMS/LRS Users Courses Enrollments SCORM Data Reporting Courses Classes Certs Badges SocialLearning Messaging Performance,Talenthooks Reporting Games Sims Perf Supp Dash boards eCommerce Import/Export Biz Data LRS SCORM data 5
- 33. LMS/LRS BUYERS GUIDE • If you’re buying new, you only have one thing to get through your IT. Tip: Roll in your TMS and PMS, too. Buy new business cards. 5
- 34. There Be Dragons Here Questions to ask no matter what: • What does the integration look like? Will users see a difference? How about LMS managers? • What does reporting look like? • What’s it cost? Do I need an upgrade, or can I just “do it”? • What does a pilot look like?
- 35. Getting started • Prêt-à-porter • Day hikes • Look for the right project & sponsor • Start where there is no LMS legacy • You can’t sell the alphabet soup.
- 36. In the meantime: Baby Steps • Leverage your prototypes! • Deploy – gain feedback, refine • Reporting – validate, refine • Validate your business case, • Lather, rinse, repeat Dollarphotoclub_74065258
- 37. What will you take away? Dollarphotoclub_67123634
- 39. Megan Torrance CEO, TorranceLearning Rob Houck CTO, LearnShare LLC
Hinweis der Redaktion
- Let’s go back to the ‘book”.. This is pulled from the xAPI documentation almost verbatim.. this is the “promise” of xAPI. #1 – actually this answer makes people involved with xAPI cringe. It’s like saying your smartphone is a next generation book. But it’s a good place to start the conversation. And then quickly move along. #2 – from the instructional design perspective, when your job is to build and track training. This is where it’s at. With SCORM you can track about 20 things, only 4 of which are interesting. (Location, Time, Score, Complete, Answers). Now that’s not to say that you can’t get really clever with SCORM and trick it into doing a few other things. #3 – builds off this – reinforce that learning experiences in the future won’t come entirely from e-learning. Give examples (RFID, Ab Scex KPI’s, other “triggers” that happen in the real world.. Call center logs, manufacturing floor, etc.) #4 – this is the land of unicorns.. We’ve been promised this for years.. It ain’t easy.
- Answer #1 It stands for Learning Record Store and, since we’re in Vegas, it’s the Teller to xAPI’s Penn. Or whichever is the quiet one. Answer #2 It’s where we store the training data. It’s what makes xAPI work otherwise you’re just sending statements to the ether. Answer #3 It’s a database where sent xAPI activity statements and retrieve them later. Now we start to get interesting. It does not make decisions. SCORM can make decisions – sequencing and completion and such. xAPI doesn’t. but what it does do is remember what you tell it and allow it to pull it back later. And that let’s you do some interesting things. Answer #4 It is NOT all the things that most people recognize that your LMS does. It’s not the enrollments, people data, it probably has some reporting to it but that's not part of the spec, it’s not badging or any of the other things you’ll want to do.
- When you get right down to it, the LRS is what makes xAPI work.
- So this is the part where Megan comes clean. When I first heard about xAPI and LRS … I thought, wow: this is the end of SCORM and the end of the LMS. I was only partly right. SCORM will go away. Not as soon as you want it to, but it will be pretty much dead within 5-10 years, depending on your industry. By then you won’t have to worry about legacy content. Sorry … it’ll take that long. The LRS, however, doesn’t replace your LMS. Here’s why.
- The LMS does a lot of things that are pretty useful for you. Your LMS is basically a nice neat box. It’s got some user data, and some courses it hosts. (For now I’m assuming that this is just an elearning LMS … which is probably less than what you actually have but bear with me.) The intersection of Users and Courses is an Enrollment. When that happens and people take the course, the course sends data to a SCORM database. Maybe you have some AICC in there, too, but for now we’ll just pretend it’s all SCORM. And then you can run reporting .. On users, on courses, on enrollments … but really you want reports on that SCORM data.
- Of course, this LMS wouldn’t keep you happy for very long, so you probably have some other things going on in your LMS. So your LMS vendor has added on some things that aren’t SCORM – and that’s important to know. Useful … but not SCORM. The obvious one is classroom training. People love Completion certificates. If you’re really fancy you have badges which are like souped up completion certificates. Social is really cool so the better LMSes include some of that. And there’s some basic messaging around all of that that’s really helpful. Maybe at some point you decide you need eCommerce. Games, Simulations and Performance Support … all super cool stuff. And at that point we should add Dashboards And as your learning organization matures, you’ll hook that all into Performance Support and Talent Management If you have a BI unit, you might be dumping data out to them … if there’s anything they’re paying attention to. And this is just the set of things that are attached to your LMS. Anything that’s not SCORM – because really: most of your games, performance support, random one-off learning, informal experiences – aren’t included in here.
- But for the simple sake of argument here … we’ll work with this model. And what does xAPI do? It replaces this piece. Or, because you’re not likely to be dumping all your SCORM data, it does this.
- And … according to the spec … doesn’t touch all the rest of it. Of course … that’s where things get really interesting. Now of course this is a gross oversimplification of what it actually takes to pull this off. Don’t go slamming your LMS vendor for not having done this yet. It’s way more complicated than turning a purple box to a green one … and there’s still just enough ambiguity in the spec – at least until CMI5 is finalized – that makes it tricky to pull this off seamlessly.
- So there’s another approach that you can take on this. This is what you get when you buy an LRS. The core system desired around and optimized for xAPI, that then lets you get best-of-breed tools to hook into it. Since you don’t have to be confined to just elearning courses in an LMS for tracking, you you’re tracking things that happen in the real world, and you’re able to go out and do all sorts of things outside your LMS and that pretty well rocks.
- I mean … if that’s all there is to it … what’s the big deal? The big deal is in how the data is structured.
- SCORM is “rectangular” and predictable. Databases like to be neat and tidy.. A place for everything and everything has a place. But we really can’t create a place for *anything*..
- Lets go back to that structured/unstructured concept that Megan talked about.. Databases like to be neat and tidy.. A place for everything and everything has a place. But we really can’t create a place for *anything*.. -- Verbs, more flexibility -- “context” – 4 star rating, Pink Frosting, homer simpson -- even if we use “standards” like verbs, context is there for flexibility -- Therefore critical on your reporting requirements that we talk bout later
- A traditional LMS is left looking for a course to send it data. The biggest one is .. There’s NO COURSE.. So you can see how SCORM can break down quickly!
- [Green box fades in on click] So xAPI is “unstructured” but not “illogical”… We don’t NEED a course loaded in the system to understand data.. We don’t need to know ahead of time you’re going to send something. This is an incredibly freeing concept – and one that throws a lot more onerous on ISD’s to think about their data. We haven’t really had to do that before!
- [Green box fades in on click!] If you don’t have an LMS, you have some flexibility that those of us with a solution in place already don’t. You get to start from scratch. If you’ve got a few courses just “on a sever somewhere”, an LRS may be a very inexpensive way to get tracking (plus a lot more later) or if you’re picking up a new tool – a new activity provider – you’ll get an LRS. You can then also publish courses to xAPI (even though you won’t get much interesting data, you’ll start tracking completions using xAPI alongside the rest of your activity data) and you’re ready to rock and roll. Over time, you’ll grow into something more.
- The big question whether you need an LRS right now. SCORM is perfectly OK!!! It still works. It’s not going away. If you’re tracking elearning and you don’t have anything other than courses that you’re tracking … you may not need an LRS. Will you want one in the future? Heck yeah. In the meantime you’ll be able to watch vendors learn and improve.
- LRS and LMS separate LRS send to LMS LRS to BI (assuming LMS to BI … but no one is doing this now) LMS to LRS (to get better visualizations) Best of both: integrated LMS/LRS For the really mature orgs: TMS/PMS/LMS+LRS
- When you’re first starting having a separate LRS thing makes sense, flexible, not connected Then … you’re gonna wanna do a single source of data report The reason why you’re doing this is you just bought a spiffy new tool or you want to build one and your LMS isn’t xAPI yet.
- [Green box Fades in!] BUYERS GUIDE: Buy, don’t build Don’t emotionally invest in this – go with what the tool provider uses already so you don’t have to fight it Scale – start cheap Focus on export – you & your data are not in your forever home Index value has to line up – who are my people, what are my “courses” [Index values == “Key Fields” like employee ID’s, etc]
- You can use the LRS for what it does … then you scoop the last thing off it “call it complete” And load that to your LMS. You might have multiple front end xAPI tools all on different LRSes to consolidate data with your LMS. People want to know “who’s complete” and that’s what LMSes do Your LMS is your single point of truth That way when the auditors say “did they do that” you have a single source of truth
- [Green box fades in!] This was one of the early models for integration BUYER’S GUIDE: Export functions Index values have to line up for people and courses What is a “course” – you have define what constitutes “complete” – is it X statements, is it certain statements, is it a “Completed” statement? Limit the number of LRSes possibly to help If you hear “Dump the JSON” run You’re not going to be happy in this spot for a long time so don’t over invest in this
- Ok, so if you don’t have a BI or don’t know what one is … check your phone now and I’ll let you know when to come back. You don’t want to drive this train. If one exists in your organization … jump on it! Now you have the data to play. You want data, you have a BI and that’s your source of truth Internal BI team is doing all their fancy reporting and comparing that with other types of data Makes a ton of sense when you have a ton of data from a bunch of different sources
- BUYERS GUIDE: That’s what your BI is for You may not even need to care about analytics inside the LRS because you’re getting more somewhere else Your data needs to stay in sequence You need to talk to your BI guys to let them know you have unstructured data or all you’re going to get is very scormy stuff
- If you’re getting better reporting and visualizations You want all the richness of your xAPI data and not have to flatten it to get back into the LMS And you have all your legacy LMS stuff – you have the tipping point into xAPI koolaid Multiple LMSes feed into one LRS and report from there. Start comparing experience data with SCORM completion data and maybe wrestle more value out of the old legacy stuff.
- [Green box Fades in!] Biggest hassle then is how do you report? Report from one course is not going to be relevant to another one.
- Chocolate and peanut butter Everything’s in one spot You’re doing your own people based BI in one spot You are pulling in other system data (Sf.com, Oracle, SAP…) TMS and PMS this is the big one … you get to sit at the table
- And … according to the spec … doesn’t touch all the rest of it. Of course … that’s where things get really interesting. Now of course this is a gross oversimplification of what it actually takes to pull this off. Don’t go slamming your LMS vendor for not having done this yet. It’s way more complicated than turning a purple box to a green one … and there’s still just enough ambiguity in the spec – at least until CMI5 is finalized – that makes it tricky to pull this off seamlessly.
- [Green box fades in!] More cost effective – only one thing to get through your IT, one SSO, one integration you have plans for managing structured + unstructured data together
- No matter what you have some implementation “dragons” …. Integration – watch out for integrations that are periodic feeds. This is seldom a good answer. Obviously, users shouldn’t see difference running an XAPI driven course.. But it doesn’t hurt to ask. Your LMS managers and administrators may have differences in how courses are loaded, tested and maintained. The LRS should be “heard” and not “seen”. Reporting – integrated reporting should be high on your wish list.. You don’t want to get into two reporting tools. That’s never fun. Get specific with your questions “can I pull a summary by department of anybody that did a particular activity and how they rated it?” Cost – this shouldn’t blow out your budget.. But get pricing ahead of time. “Upgrading” the LMS to “get” xAPI may or may not be worth it.. That will be dependent on the business case. Pilot – if you’ve built prototypes, you can test them in a pilot.. Validate things work the way you want.. Expand audiences gradually until you have the need to go enterprise wide.
- [Rob] Here’s where the “rubber hits the road”. We’ve done our homework.. So it’s not quite as hard as it seems.