Frequently asked questions
How does Agylia pricing work?
How do I become an Agylia reseller?
Agylia are looking for established companies in the eLearning, learning management and HR industries who have existing and prospective customers who will benefit from the range of Agylia solutions.
For further information on the Agylia Reseller Partner Programme, visit www.agylia.com/resellers.html
Can Agylia be integrated with existing LMS, HR, Salesforce and other corporate systems?
Yes, Agylia can be integrated with your existing LMS, HR, Talent Management, Salesforce / CRM systems.
Agylia provides a series of Web APIs built using open, industry standard technology. If you have the internal development experience to call Web APIs then you can call the Agylia APIs directly. If you don’t, don’t worry because we can provide integration assistance during the implementation.
Does Agylia support single-sign-on (SSO)?
Yes, Agylia includes a powerful single-sign-on module that can connect to a wide range of identity provider systems. This includes Active Directory Federation Services (ADFS) for corporate Active Directory based single-sign-on and SAML support for a wide range of other identity providers; both corporate and social providers.
What type of content can be loaded and delivered by Agylia?
Agylia supports many different types of content ranging from SCORM or Experience API based eLearning and microlearning courses, to standalone videos, PDF documents, and Office documents such as Word, PowerPoint and Excel files.
In addition to these various different types of digital content, Agylia lets you publish “web links” to other internal or external resources not directly hosted by the LMS, for example links to resources on your corporate intranet, or links to videos on video sharing sites such as YouTube and Vimeo.
All forms of content access is tracked so you can see who has consumed what content. Unlike many LMS, tracking is not limited to SCORM based eLearning.
What kind of support is included with Agylia?
Agylia customers are supported by a dedicated and passionate customer support team who are available for phone contact during UK and US West Coast business hours.
Additionally, we operate an online support desk and ticketing system. By sending an email directly to the support desk, your question or issue will automatically be assigned a ticket number and will be managed through to resolution by one of our support team. The online Help Desk also includes product specific and technical FAQs, articles, videos and other useful training resources for system administrators.
How long is a typical implementation cycle?
One of the benefits of a cloud-based solution is the speed with which you can be up and running. We recognise that you will want your own company branding to be applied and your own versions of the Agylia’s mobile learning Apps to be created and deployed either via the public Apple, Google and Microsoft App stores or your own Enterprise App store. System configuration such as email templates, user profile property definition and authentication options are easily applied. A typical implementation with no additional integration requirements can be completed in less than four weeks.
If integration is required with your internal systems such as other LMS or HR systems, then this timeline is likely to extend slightly. Our implementation consultants will ensure that this is a smooth and painless process for you.
Is any training on the system included?
Yes, training for administrators is provided. This can either be delivered online or it can be delivered on site on customer request. Additionally, the Help Desk includes administrator focussed training resources including videos and help articles.
What is an LMS?
A Learning Management System (LMS) is a software application or service that is used to support the online delivery, management and tracking of online training and blended learning programmes.
An LMS traditionally lets you publish and deploy training content, manage, schedule and record training activities and enables you to report on your users’ training progress.
A modern LMS will also enable you to publish a wide range of additional learning, reference and support assets in addition to eLearning courses - for example videos, mobile learning modules, performance support tools, reference guides, PDF and Office documents, just-in-time training aids and many more.
What is an LRS?
A Learning Record Store (LRS) is a central repository for learning activity statements. These are the statements (the syntax of which is defined by the Experience API specification) that capture individual learning activities such as “Bob completed Induction Training 101 on 15th September, with a score of 86%” or “Sarah attended the company update briefing on 15th January”.
An LRS does not require an LMS and they perform different functions. However, an LRS without the additional management and content hosting capability of an LMS is of more limited and specialised use. The Agylia LMS includes an integrated LRS.
What is SCORM?
SCORM stands for the Shareable Content Object Reference Model. It has been the defacto technical standard for the online delivery of eLearning courses for many years. By using SCORM compliant eLearning you can create eLearning courses that can be hosted on any SCORM compliant LMS and you can track user interactions with this learning; such as course completions, answers to assessment questions and overall scores.
While still prevalent due to the vast quantities of SCORM content that has been produced over the years, SCORM is an aging standard originally conceived in 2000. The last major revision came in 2009, which saw the 4th edition of the SCORM 2004 standard. SCORM version 1.2 still remains the most common version with a majority of SCORM content built to this version of the specification.
SCORM is gradually being superseded and replaced by the Experience API (Tin Can) standard. If you are choosing an LMS make sure that it can support both SCORM (for legacy materials) and Experience API for the future.
What is the Experience API?
You can think of the Experience API (Tin Can) as “next generation SCORM” or SCORM for a modern, disconnected, mobile-oriented world.
By using the Experience API you can do everything you can do with SCORM, for example track course completions, record course scores, track assessment question responses and so on. However, you can also do so much more with the Experience API. You are no longer limited to tracking eLearning courses running on an LMS. You can use the Experience API to track interactions with other forms of content such as standalone videos, or electronic documents such and Office documents or PDF documents. You can also use it to record informal learning activities or activities that occur outside the boundaries of the LMS, such as classroom training (recording someone’s attendance), participation in an online webinar or perhaps a mentoring session, reading or writing a blog post, and the list goes on; only really limited by your imagination.
By being able to record all types of learning activities, the Experience API enables you to build up a rich and comprehensive picture of individuals’ learner journeys. By being able to correlate this to the behaviour changes you desire and to defined KPIs (key performance indicators) pertinent to your scenario or business, then for the first time, you can start to tangibly measure the ROI (return on investment) of your training programmes and initiatives.
Many commercially available authoring tools are now available that support the Experience API in addition to SCORM.
What are the benefits of native vs web Apps?
Mobile Apps come in many different shapes and sizes but these are broadly divided into two types; mobile web Apps and native Apps.
Native Apps, such as the Agylia mobile learning App are Apps built for specific mobile operating systems, like iOS, Android and Windows, using platform specific development tooling and technologies. The advantage of a native App is that it offers a best of breed user experience and is able to use the full power of the user’s device and mobile operating system.
Mobile web Apps, that are unable to offer the same degree of user experience and lack the ability to capitalise on the full power of the underlying device.