What will happen to countries that have implemented OpenLMIS or earlier (ie. eLMIS in Tanzania and Zambia)? How do they stay on board moving forward?
Existing implementations can choose to continue on their current version without upgrading, or plan an upgrade project. Countries staying on the current version can continue to receive OpenLMIS community support, as well as implementation partner support in-country. If there is an active interest in upgrading the system to 3.0, this can be considered either as a distinct project, or as part of the suite of menu options presented in the scope of 3.0. We need input from partners and donors responsible for legacy implementation on whether they want an upgrade project scoped in concert with the 3.0 release.
How do current implementations take advantage of new modules or features?
If a country upgrades to the new version, they will be able to take advantage of those new modules or features.
What kind of support (Tier 3, etc.) can the OpenLMIS community provide to existing implementations, and how long with this be provided?
Through the OpenLMIS Community, bugs and additional issues may be presented to the community, which then may respond with assistance in managing the issue. Any member of the Community is welcome to present their issues for assistance. Community members may present issues and request support via the following committee groups:
With the 3.0 version, a warranty may be crafted to guarantee provision of support.
The community was not sufficiently included in the creation of re-architecture alternatives (incremental approach vs. rewrite). They were presented as the only decisions/options
This feedback has been duly noted. In the next phase of the project, the OpenLMIS Core Team has reached out to implementers and partners to get the full scope of the feature list for the next phase, incorporating community review of re-architecture deliverables, and including community participants in design sessions for the product.
Lowering migration burden should be a priority of the re-architecture
Yes, this is a priority and this objective will be included as part of the 3.0 design. The re-architecture project will provide an upgrade path from countries that implement on 2.0 to upgrade to 3.0, provide migration scripts for core system data, and provide samples of how to use extension points to extend OpenLMIS using modules.
Upgrading software, particularly software that has been customized, is a significant undertaking that will require funding. Countries that have already deployed earlier version of OpenLMIS will need to decide whether to stay on their current version of OpenLMIS, or upgrade. Countries wishing to upgrade can coordinate with the OpenLMIS community to plan a migration project.
Migration is a top concern and the global team will make its best effort to include as much in scope for 3.0 as possible. For those items that may fall out of scope, the global team will work with partners to develop a plan. In scope for 3.0 are data migration scripts for core pieces, and customizations will be handled on a case-by-case basis.