Changes become traceable working states, versions and releases. The LXMS brings maintenance, review, delivery and continuous development together in one operating model.
Subject-matter corrections, new language versions and media updates are part of ongoing operations. The LXMS keeps each change connected to the learning experience and its published version.
From working state to release
It remains clear what is in progress, what has been reviewed and which version is actually published. Within the content lifecycle, the LXMS connects changes, versions, reviews, releases and delivery.
Change → Review → Version → Release → Delivery
One learning experience, multiple states
As the portfolio grows, working states, approved versions, published versions, language versions and variants exist in parallel. The LXMS keeps these relationships connected.
Review and approval in ongoing operations
Changes do not have to be organised as a completely new project every time. Teams can review and approve them selectively, then include them in a new release.
Delivery belongs to the version
A release is only unambiguous when it is clear which version is used in which context. The LXMS therefore connects version, release and delivery.
Existing content remains part of the portfolio
Learning Operations is not limited to newly developed learning experiences. Learning Content Operations also includes existing SCORM and legacy content that needs to be maintained, evaluated, kept in operation or modernised step by step.
Usage data extends the operational view of a learning experience. Published versions generate new evidence for maintenance, further development and the next design state.
