Summary

Terms of Reference

I. General Terms of Reference for the Firm of Consultants

...

The here tendered service package falls under the outcome 1 "An active network of developers and practitioners continuously advances the openIMIS software core, modules and country specific adaptation". The following outputs were defined for this outcome 1:

1. The openIMIS source code is publicly accessible under an open source license for country-specific customisation.

2. A community of open source software developers is established and active.

3. A feedback exchange between developers and actual users is facilitated regularly.

The work of the Firm of Consultants will contribute to the achievement of outcome 1.

...

Ongoing activities that have to be taken into account and built upon during this assignment are:

1. a commission on community building and regional support structures. This activity is supplemented by additional contracts for two regional openIMIS hubs in South-East Asia and Sub-Saharan Africa.

2. a commission on transitioning the openIMIS architecture into a modular design in an open source development framework.

3. a co-funded pilot project on the modular transformation of openIMIS co-ordinated by the Digital Square platform.

Developments that may lead to difficulties in a later project phase should be identified as quickly as possible. Furthermore, in view of the focus on results described above, results monitoring is crucially important. An efficient monitoring and evaluation system must therefore be proposed and set up that allows all entities of the openIMIS governance structure, the Firm of Consultants and the GIZ Sector Initiative Social Protection to monitor project progress. Progress reports are submitted quarterly based on a format which will be agreed upon during the inception. Regular feedback sessions may be convened by the GIZ Sector Programme Social Protection depending on the progress of the assigned tasks. The Firm of Consultants is expected to respond to changes flexibly, especially if the project is in danger of straying from outputs mentioned in Chapter 1.

...

The existing communication channels and community platforms that were established by the openIMIS Initiative shall be used. Specifically, these are

• openIMIS code repositories (https://github.com/openimis)

• openIMIS issue tracker (https://openimis.atlassian.net)

• openIMIS documentation server (https://openimis.readthedocs.io)

• openIMIS wiki (https://openimis.atlassian.net/wiki/spaces/OP)

Within the openIMIS governance structure regular exchange meetings are foreseen for different stakeholders, some of which are also relevant for the Firm of Consultants. In the context of this commission, the Firm of Consultants is currently especially expected to take part in the weekly calls of the IT & Product Group but might be invited for additional events.

...

The openIMIS Initiative together with other development partners has previously supported the maintenance and support of the openIMIS product. The results include among others:

• A harmonised master version was created from the country specific adaptations of the openIMIS software package and made available in a public code repository. It is updated regularly with recent code contributions. (https://github.com/openimis)

• A technical roadmap was developed as a living and constantly updated technical document based on a series of workshops with different stakeholders, code reviews of the master version and ongoing technical strategy discussions.

(https://openimis.atlassian.net/wiki/spaces/OP/pages/40763442/Product+roadmap)

• Community platforms were set up as resource repositories and communication channels for the openIMIS community (compare chapter 2.I.b).

f. Data Protection

In the course of the commission, the Firm of Consultants might be exposed to data on health issues and financial transactions of individuals. The Firm of Consultants is expected to treat any personal information of individuals according to the highest applicable data confidentiality standards. At the same time, the Firm of Consultants is expected to contribute to the security of individual data by applying adequate quality standards.

...

In order to achieve the aim of the project, the following objectives shall be pursued:

1. Implementers of openIMIS are supported on issues that are related to the source code of the openIMIS distribution (3rd level user support)

2. The existing code base is managed and kept up to date (software maintenance).

3. New software releases are managed and published on a regular basis (release management).

b. Specific Tasks of the Project

...

Work Package 1: 3rd Level User Support

1. Provide remote, technical troubleshooting support, based on clearly defined service level response times that reflect the sensitivity of financial transactions related to the provision of health services.

2. Constantly monitor the public issue queue and review single issues in a timely manner.

3. Together with the implementers, discuss issues and further refine them into the appropriate channel of the change process.

4. Implement bug fixes and back ports if needed.

5. Publishing all information and solutions in a timely and participative manner on the appropriate platform.

6. Support community managers, trainers and higher support levels with technical expertise. This includes support during technical workshops and product presentations.

7. Maintain real-time statistics on volume and distribution of user support issues and their solutions.

Work Package 2: Software Maintenance

1. Proactively analyse and quality check the existing source code and propose technical changes and fixes via the issue tracker where needed (e.g. security fixes or performance optimizations).

2. Programming of new functions as part of the release cycle.

3. Manage external code contributions (pull requests) and integrate them as appropriate within agreed service level response times.

4. Closely co-operate with the modular transformation project and initiate changes that allow an appropriate modularisation of the legacy system as well as a smooth integration of the new components of the new architecture.

5. Do extensive developer and integration tests.

6. Assess all changes according to their effect on the upgrade process for implementers and on communication interfaces, especially after data model changes.

7. Document all changes in the appropriate platforms (including inline code documentation) and initiate secondary documentation changes (e.g. user manuals, translations).

Work Package 3: Release Management

1. Manage the release cycle and ensure the timely delivery of new releases according to the release plan for updates regarding existing functionality (bug fixing, small functional changes) and new functionality (including changes to system architecture, interoperability and modularization).

2. In close co-operation with the modular transition project establish a building and packaging mechanism that allows a full install of the software and a successive integration of the work results of the modular transition project.

3. In close co-operation with the community building project coordinate user and developer communities to capture change and feature requests.

4. Draft and review change requests together with the requestor and identify the importance of change request.

5. Approve developers contributions to source-code (pull requests) and harmonize implementation specific changes into the generic master version.

6. Manage release priorities and identify updates to be included in a release in close co-ordination with the Program Coordination Desk

7. In accordance to the release schedule suggest an implementation work-plan for releases to the release committee and to the technical advisory group (TAG).

8. Ensure proper quality assurance of changes through diverse testing mechanisms regarding their functional validity, their proper integration into the master version, the performance and vulnerability of the system and also the acceptance by the end users.

9. Ensure documentation updates and the upgrade of the demo server to the new release.

10. Release the new version and inform all stakeholders via the defined communication channels.

11. Provide basic support to user organisations who want to upgrade openIMIS to a new version of the software.

c. Expected deliverables

The following deliverables are expected from the Firm of Consultants:

1. Inception report to be submitted 4 weeks after commencement of services specifying a work plan and a technical roadmap for the planned activities for each work package.

2. At any given moment the issue queue may not contain any user request in a status that does not comply to the agreed service levels.

3. The agreed number of software releases was done, each providing a fully installable installation package.

4. The openIMIS source code repository contains a branch of the complete code needed for a complete installation package of any openIMIS release.

5. The openIMIS source code repository contains not more than the agreed number of unattended pull request, especially regarding the developments from the modular transformation project.

6. One release recommendation document for TAG on prioritization of bug fixes per release.

7. The demo server is updated to the latest release one day before every public release announcement.

8. For each openIMIS release a document freeze exists, that reflects the full functionality of the respective software release on the day of the public release announcement. Each document freeze includes the complete technical and user documentations, an installation and an upgrade guideline.

9. Quarterly reports and updated work plans to be submitted by the 5^th day of every third month after the acceptance of the inception report.

10. Final report based on a GIZ reporting format to be submitted on 15.06.2020.