CMI 5 Working Group Meeting Minutes – December 23rd, 2022

cmi5 Working Group Meeting Minutes – December 23rd, 2022

Attendee List

• Bill McDonald (working group leader)
• Andy Johnson (ADL)
• Megan Bohland (ADL)
• Christopher Thompson
• Martin Koob (VideoLinkWell)
• George Vilches ()
• Henry Ryng (InXSOL)
• Tyler Mulligan (SANS)

Notes

The group discussed AU session/cumulative time calculation in cmi5 based on questions about how the LMS should calculate duration in an abandoned scenario.

Total Time in AU vs Time in AU to Completion. The group identified 4 time collection scenarios.

1. Total Time = Cumulative time for all sessions (in normal, review, etc.)
2. Total Time to “Satisfaction” = Cumulative time for all sessions (Completed/Passed)
3. Wall Clock Time = launch and exit as observed by the LMS
4. Total (Wall Clock Time) = Cumulative time for all launches and exit as observed by the LMS

Abandoned Statement

• Cumulative time is calculated by the LMS
• (Duration) Session Time is calculated by the last statement made from launch. (terminated, or abandoned)
• LMS can make the duration determination based on other methods

Possible new features- Using State API to store aggregate times in a State Document:

• Best Practice ?
• example stat document Lms.AUReportData (per registration)
• Provided to make it easier for the LMS to calculate times?
• Concerns expressed if this an appropriate use of the State API

Other Documentation APIs:

• Agent Profile (Overall)
• Activity Profile (Overall)
• State (user/activity registration specific)
  • Is State API intended to exist after registration?
  • Is State API intended to be used by the LMS? (should it only be used by AU?)

Possible new feature - “Running Total” statement extension

• for AU’s to calculate total time (Across all Sessions in a Registration) (i.e. ISO 8601 Duration)
• Does not deal with the Satisfied time (or other specific use cases)
• A lot of configuration

Use launchMode to aid in time calculation scenarios

• If section 9.6.3.3 launchMode were updated to require the AU to include launchMode in all (Duration) Statement Contexts, the LMS could calculate "time to satisfaction" from querying statements

---

All Previous cmi5 Meeting Minutes

https://github.com/AICC/CMI-5_Spec_Current/wiki

cmi5 on GitHub:

http://aicc.github.io/CMI-5_Spec_Current/