Extended LMS SCORM API Runtime Content Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

SCORM-compliant training content is often presented in a uniform style, making it less engaging and less effective for individual users, as it lacks personalization, leading to increased overhead in creating multiple variants and higher storage costs.

Innovation Solution

An extended Learning Management System (LMS) that supports proprietary extensions, allowing for API calls with undefined parameters to tailor SCORM-compliant content at runtime, providing user-specific information such as theme, progress, and language adjustments, enabling personalized content delivery without returning error codes for undefined elements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple variants of SCORM-compliant training content are created to make content more relevant to individual users, then content personalization and user engagement improve, but content creation time, cost, and storage overhead increase significantly

Engineering Contradiction:
Improvecontent personalizationVSAvoidcontent creation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The training content is segmented into modular SCORM-compliant units (SCOs) that can be independently assembled and customized. Each SCO represents a discrete learning object that can be dynamically combined based on user profiles, allowing personalization without creating entirely separate content variants.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A single master version of the training content is created with universal SCORM compliance, which can serve multiple users and purposes. The content is designed to be dynamically adapted through API-based personalization rather than requiring separate variants, making one content package multi-functional for different user needs.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple variants of SCORM-compliant training content are created to make content more relevant to individual users, then content personalization and user engagement improve, but storage costs and transmission overhead increase

Engineering Contradiction:
Improvecontent personalizationVSAvoidstorage overhead
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

Multiple content delivery capabilities are merged into a single SCORM-compliant content package. The content includes embedded logic and API interfaces that enable dynamic personalization, combining the functionality of what would traditionally require multiple separate content variants into one unified package that adapts at runtime.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The content is designed to accept parameter changes based on user characteristics. By using SCORM's data model and API to pass user-specific parameters (such as skill level, role, or performance data), the same content package dynamically adjusts its presentation without requiring separate stored variants for different user types.

Inventive Principle:
Principle #35Parameter changes

3Quantity of substance

If a single variant of SCORM-compliant training content is used for all users, then storage and transmission overhead are reduced, but user engagement and content effectiveness decrease due to lack of personalization

Engineering Contradiction:
Improvestorage efficiencyVSAvoidtraining effectiveness
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The training content transitions from a static, uniform presentation to a dynamic, adaptive experience. The SCORM-compliant content uses API calls to receive real-time user data and dynamically adjusts content delivery, pacing, and presentation based on individual user characteristics, maintaining engagement while using a single content package.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback loops where user interactions with the training content are tracked and used to adapt subsequent content delivery. The SCORM API enables bidirectional communication between the LMS and content, allowing the content to respond to user performance and preferences, thereby improving effectiveness without requiring multiple pre-authored variants.

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If proprietary extensions are added to the LMS to enable runtime adaptation of SCORM content, then content personalization capability improves, but system complexity increases

Engineering Contradiction:
Improveruntime content adaptationVSAvoidLMS system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The SCORM runtime environment and API serve as an intermediary layer between the LMS and the training content. This standardized interface handles the complexity of content adaptation, personalization logic, and data exchange, shielding the LMS from direct implementation complexity while enabling sophisticated runtime content modification through established SCORM mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11847579B2Systems and methods for adaptation of SCORM packages at runtime with an extended LMS
Publication Date: 2023.12.19 KNOWBE4 INC
  • US11847579B2 patent drawing
  • US11847579B2 patent drawing
  • US11847579B2 patent drawing

AI summary

Systems and methods are described for tailoring shareable content object reference model (SCORM)-compliant content to one or more users. A learning management system (LMS), configured to be SCORM-compliant, initiates shareable content object (SCO) to provide content to users. The LMS implements an instance of application programming interface (API) comprising a plurality of functions to be called by SCO during runtime to access data model elements accessible via LMS. The LMS is configured to support one or more data model elements undefined by SCORM. Further, LMS receives a call to a function of the plurality of functions of the API from SCO to access information about users. The call references a name of a data model element undefined by SCORM. The data model element identifies information about users. The LMS provides information about the users to SCO and the SCO tailors the content to the users based on the information.