Successful OpenLMIS Implementation Models - Aligning Funder/MoH/Implementer/Community Goals Session Description: What are possible/preferred OpenLMIS implementation models for the future? Identify strategies for addressing the conflicting goals of country implementations (time, specific requirements) and funder/community goals (code reuse/contributions to core). Goal: Define effective reference implementation models/guidance for future projects (not prescriptive) Structure: Part 1 - Look Back: Implementations Lessons Learned Part 2 - Look Forward: To-Be Implementation Scenario

Look Back: Implementations Lesson Learned Activity: For specific implementations, brainstorm what worked and what didn’t work Volunteer leaders and form groups minute discussion Report back on top-3 from “worked” and “didn’t work” What WorkedWhat Didn’t Work

Look Forward: To-Be Implementation Activity Activity: Work through a fictitious implementation scenario as a large group to define how we would would set the project up for success in the future. Assumptions: The following community and tech essentials are in place: Modular architecture: Core, Community-Supported Modules, Custom Modules Product roadmap, and process for adding items to the roadmap Communication processes between community members Community decision making process

Implementation Scenario GlobalHealth4U is working with Uzbekistan – they are looking for a LMIS and are almost ready to decide to implement OpenLMIS GlobalHealth4U has experience implementing OpenLMIS GlobalHealth4U has conducted a requirements workshop. OpenLMIS meets 75% of the country requirements, but they also needs: – Offline requisitions – on the OpenLMIS product roadmap for delivery in 18 mos – 3 new reports – Supplemental data on surveillance collected during the requisitions process There is a funded global OpenLMIS team with some resources to support implementation projects GlobalHealth4U has a funder lined up for the project. The funder at the global level wants all of their investment to result in software that can be used by other countries. The MoH wants the project completed with 6 months GlobalHealth4U has two developers in their Uzbekistan country team. They have a little Java experience, but haven’t worked on OpenLMIS before.

Project Objectives I Want… MoH GlobalHealth4U Funders OpenLMIS Community

Planning the Project How does GlobalHealth4U and OpenLMIS Community decide what should be built as custom modules, vs. community-supported modules? Analyze the requirements and split across each bucket, using some of the criteria below: Bring 25% of the requirements to the community. Is this something we see on a regular basis or not? If yes, community provides Custom: Requirements derived from one country; Timelines don’t allow for to meet community module standards; Could become community-supported later (via curation, editorial, but this is expensive and can be difficult to fund fixing later); Can be of value to other projects; Quick and dirty has value. Community Supported: Clear standards for community supported modules; Community approval process. Offline Functionality: -Reprioritize roadmap with community -Send one person from global team to the country to work with the local team to build it -Hire out work to additional team (pre-approved?) How does GlobalHealth4U work with the donor to set realistic expectation on how much reuse can be achieved with their investment? What can OpenLMIS community do to support this conversation? -Toolkit with timelines showing realistic LOE for community-support modules -Value proposition for custom modules -Consider phased approach -Include a technical architect in conversations with funder – intentional, thoughtful approach

How does GlobalHealth4U work with the MoH to set realistic expectation about project delivery timelines and what level of customization will be possible with their implementation? --Donor works with country to set expectations that OpenLMIS is not bespoke system -- Donor: We will fund you if you do it in this way -- Community: We will assist you if you do it in this way --Work with country to discuss timeframe flexibility --Emphasize where customization is possible, whereas where the system is less flexible (more UI flexibility?) --Articulate trade-offs product backlog in delivery plan

Roles & Responsibilities Who?How Funded? Configure OpenLMIS Develop Custom Module(s) Gather requirements for Community- Support Module(s) Develop Community-Supported Module(s) Provide OpenLMIS Support to GlobalHealth4U What Else? Possible Actors: GlobalHealth4U Local SDE Partner “Certified” OpenLMIS Dev Partner OpenLMIS Community OpenLMIS Global Team Possible Actors: GlobalHealth4U Local SDE Partner “Certified” OpenLMIS Dev Partner OpenLMIS Community OpenLMIS Global Team