Skip to content
Language
  • English
  • French
  • Portuguese
  • Spanish
  • Arabic
OpenLMIS
  • About
    • Vision & Mission
    • Partners
    • Community
    • History
    • Principles for Digital Development
    • Blog
    • Transition
    • COVID-19 Edition
    • Demo
  • Product
    • Product Overview
    • Features
    • Interoperability
    • Flexibility
    • Product Roadmap
    • Demo
  • Impact
    • Overview
    • Implementations
  • Get Started
    • Implementer
    • Developer
    • Funder
    • Study Tours
    • Contact
  • Tools
    • Wiki
    • Resource Library
    • ReadTheDocs
    • Issue Tracking
    • Source Code
    • License
    • Demo Videos
  • Implementer Toolkit

4 – Maintain

Maintain

At this step in the implementation process, your electronic LMIS implementation is up and running. This section, 4-Maintain, will help you understand how to support and maintain your system after go-live.

This section also explains OpenLMIS’s semantic versioning process, so you can understand how to take advantage of new software releases and stay up to date with the core OpenLMIS code line.

Downloads available on this page

Generic OpenLMIS_Support Requirements_July 2019
Sample Support Plan
Release Deployment Plan Template
Release Deployment Schedule Template                                                                        
                                Sample OpenLMIS Quality Assurance Plan


OpenLMIS Version Updates

Each OpenLMIS version 3 service uses “Semantic Versioning,” where version numbers and the way they change convey meaning about the underlying code and what has been modified from one version to the next.

  • In each incremental “patch” release (3.0.1, 3.0.2, etc.), bug fixes, security updates, and performance improvements will come out on an as-needed schedule
  • In each “minor” release (3.1, 3.2, 3.3, etc.), new functionality will come out periodically and will be backwards compatible
  • A “major” release (e.g. OpenLMIS version 4) constitutes profound changes that may break backward-compatibility with the previous major release

Read more about OpenLMIS semantic versioning 

Each new OpenLMIS release has a community review period and has a significant amount of testing, both manual and automated, to ensure new versions will work smoothly for current users.

Each release also includes Release Notes that provide guidance to implementers on upgrading and flag any new features or changes that impact backwards-compatibility.

The OpenLMIS 3 architecture allows different country implementations to have some of their own custom features (through extension modules), but to still share the common, core base of software.

The patch and minor releases will be backwards compatible and easy to apply to existing implementations. In order to achieve the “shared value” community goals, it is important that implementations stay up-to-date with these releases.

When all participating countries stay up-to-date, that means any implementation can benefit from improvements made in another implementation.

See updated documentation on OpenLMIS releases here.

+ More


Maintenance

After the initial deployment or roll-out of OpenLMIS, ongoing system support and maintenance is required to ensure the application continues to function smoothly and address issues that arise. The technical team supporting the software make additional customizations, bug fixes, or enhancements that need to be incorporated into the system after the initial deployment.

Download: Sample Support Plan and OpenLMIS Support Requirements

 

Read more about maintaining and supporting your system

Ensuring the infrastructure and processes are in place to set up, configure, deploy, and maintain OpenLMIS as well as provide end-user support is key to the success of any software implementation. The OpenLMIS Support Requirements reference document provides detailed information and recommendations for technical infrastructure and support covering the following areas:

  • Requirements for hosting and sustaining technical operations of OpenLMIS
  • Support and maintenance processes at various levels, both technical and end-user support
  • Training needed to support ongoing use of OpenLMIS
  • Roles and required qualification/skills of support personnel

Additionally, the OpenLMIS Core team’s work is ongoing, and they will periodically release new versions of OpenLMIS that include bug fixes, enhancements, and new features available to anyone in the OpenLMIS Community. See section above, OpenLMIS Version Updates, for further details on releases and versioning. 

The Core releases can be incorporated into an existing instance of OpenLMIS so implementations can continue to benefit from ongoing work on the Core product.

For details on the OpenLMIS Core release and upgrade processes please visit the OpenLMIS technical documentation: http://docs.openlmis.org/en/latest/conventions/versioningReleasing.html

Periodic maintenance releases should be expected and planned for in an OpenLMIS implementation. Additionally, each release should be managed by a set of standard release processes, and a release-specific deployment plan to handle the testing and roll out.

Testing

Each maintenance release should be moved to the User Acceptance Testing (UAT or Test/Staging) instance and tested at least by the implementation team and potentially also through user-acceptance testing, if the release includes significant changes (generally, if the release requires additional training, it would likely be beneficial to have a UAT session).  

Additionally, the implementation team should ensure that there are plans to notify users and stakeholders, additional training, review of testing results, and approve of the release.

See the release deployment plan template and release deployment schedule template below for support in the creation of these plans.

Download: Release Deployment Plan Template
Download: Release Deployment Schedule Template

+ More


Training

After the initial rollout and deployment of OpenLMIS, ongoing training is necessary to ensure that users understand the system and are using it correctly and efficiently. The implementation should include plans to meet ongoing training needs, including:

  •      Need to train new staff
  •      Refresher training to ensure optimal system use
  •      Need for additional superusers/trainers (if using a train-the-trainer method)
  •      Training for new or updated features or functionality
  •      Training based on new or updated processes

Read more about training

Ongoing training needs can be met in a variety of ways, from large training workshops, smaller, locally-based trainings, on-the-job instruction during supportive supervision, or virtual learning methods. Each implementation will need to identify which approaches are best suited to their needs and resources.

For example, if staff turnover is low, on-the-job training during supportive supervision as needed may be the most efficient way to ensure new staff know how to use the system. If staff turnover is frequent, however, it may be hard to individually train all new staff in a timely manner, or even to keep track of the training needs.

Large training workshops allow many users to be trained simultaneously, but require significant preparation, planning, and resources. Further, users may have conflicts with other job duties or personal commitments that prevent them from attending.

All training approaches have their own benefits and disadvantages, and an approach that works for some users in some situations may not be effective for others. An implementation will likely need to identify a mix of approaches to meet all needs over time. Several factors should be considered to identify the best approach:

  •      Ability to identify and track training needs to ensure they are met in a timely fashion
  •      Frequency of staff turnover/new staff
  •      Number of trainers available
  •      Training budget
  •      Required training materials, infrastructure, time, and resources
  •      Travel required (for trainers or attendees)
  •      Need to cover new or different information

+ More


Quality Assurance

Having a documented plan for how to ensure ongoing quality assurance (QA) of the system is recommended. This Sample OpenLMIS Quality Assurance Plan outlines the testing strategies, tools, and processes used to ensure complete validation that OpenLMIS configuration and development meets the business and software requirements of your program. An OpenLMIS QA plan has several objectives:

  • Ensure the system is stable and performing well
  • Ensure configuration of master and reference data is accurate and as intended
  • Confirm the functionality of country-specific changes and customizations
  • Avoid/minimize regressions
  • Identify and resolve issues prior to release

Some examples of common QA activities that an implementation team will perform in order to achieve the above objectives are:

  • Verifying that software requirements are complete and accurate
  • Performing detailed test planning
  • Identifying standards and test procedures that will be used in the project
  • Identifying responsibilities for testing tasks within the project
  • Preparing and documenting test data, test scenarios and test cases
  • Regression testing to validate that unchanged functionality has not been affected by new code
  • Managing the defect tracking process
  • Providing test metrics / test summary reports
  • Ensuring that the application is certified for launch in the production environment
  • Defining requirements for Go / No Go

Download: Sample OpenLMIS Quality Assurance Plan

Implementer Toolkit

  • 0 – Get Started
  • 1 – Plan
  • 2 – Implement
  • 3 – Expand
  • 4 – Maintain
  • Home
  • Blog
  • Community
  • Demo
  • Contact
  • About
    • Mission & Vision
    • Partners
    • Community
    • History
    • Jobs with OpenLMIS
  • Product
    • Product Overview
    • Features
    • Flexibility
    • Interoperability
    • Product Roadmap
  • Impact
    • Overview
    • Implementations
  • Get Started
    • Implementer
    • Developer
    • Funder
  • Tools
    • Wiki
    • Resource Library
    • ReadTheDocs
    • Issue Tracking
    • Source Code
    • License

Sign up for e-News

OpenLMIS
© OpenLMIS 2023
  • Privacy Policy
  • Terms & Conditions
Website design by The Medium
  • Home
  • Blog
  • Community
  • Demo
  • Contact
  • About
    • Vision & Mission
    • Partners
    • Community
    • History
    • Principles for Digital Development
    • Blog
    • Transition
    • COVID-19 Edition
    • Demo
  • Product
    • Product Overview
    • Features
    • Interoperability
    • Flexibility
    • Product Roadmap
    • Demo
  • Impact
    • Overview
    • Implementations
  • Get Started
    • Implementer
    • Developer
    • Funder
    • Study Tours
    • Contact
  • Tools
    • Wiki
    • Resource Library
    • ReadTheDocs
    • Issue Tracking
    • Source Code
    • License
    • Demo Videos
  • Implementer Toolkit