Learning Management System (LMS) Demonstration Needs

This document is just covering the items that we, Carrapateena, would like to see demonstrated, or have
discussions about, with respect to a new Learning Management System (LMS) for our site.

Must Have:

1) Onboarding processes
a) the ability to allow users to create a personal profile, upload documents, and complete initial online courses such as site inductions
b) the ability to sub-divide new users to be able to be managed by different company administrators (i.e. Byrnecut, etc)
c) the ability to see persons progress through onboarding requirements (see what they have completed / not completed)
d) the ability to handle short-term users as well as long-term (truck drivers coming to site once or twice versus permanent employees)

2) Front page navigation
a) structure allowing users to log-in
b) create new user profile
c) resolve a ‘lost password’ issue, etc.

3) LMS course visual structures
a) intuitiveness of screens and ease of use (particularly from non-technical user perspective)
b) visual structures that can be built
c) course appearances
d) appearance on different mobile platforms (phone, tablet, laptop)

4) Overall course structures
a) loading courses into system (SCORM 2004, etc)
b) setting up course structure i.e. modules within a course.
c) completion certificates

5) User structures
a) can users be grouped (portals)
b) can we set course requirements to be completed by group/portal or at individual level
c) can course requirements be set to be completed by a date (i.e. 30 days after start)

6) Administration
a) administration tools – search functions, favourites list, etc
b) troubleshooting methods – password resets, dual profiles, etc

7) Reporting systems
a) Individual completions, reporting by teams, completion of requirements reports, etc
b) dashboards – metrics

8) Support Systems
a) Installation support team including technical and design support
b) User guides, troubleshooting documents, and vendor support system

9) Ability to interface with INX products (InTuition, InFlight, InControl)
a) Do they have Technical support personnel to create API’s
b) Ability to work with Carrapateena ICT to create seamless data movement

10) Pricing structure – single lease price / per user / etc.

Nice To Have:

1) Appearance – modern, appealing
2) xAPI capable / TinCan API / CMI5 – this would allow us to future proof system
3) Where possible the user should be able to self-correct without need of administration involvement i.e. lost password – user identifies, system employs a system to accurately identify the user (identification test of some sort), and if currently identified the password is automatically reset to a generic one or allows user to reset it.
4) With ‘new user’ profile system checks for already existing profiles that match (name and date of birth) and checks if that matches this user. If it is - asks the user identification test questions, resets password, and then log them in. If they fail the test notifies administrator in order to proceed.