Table of Contents
Background
The consortium team (VillageReach, JSI, Ona) will support the OpenLMIS community and build out the features identified in the gap analysis discovery. Given that this award is less than the total amount needed to both support the OpenLMIS community completely and deliver all the features, we have focused on outlining the scope in terms of the prioritized features.
Scope
Feature development under this subaward will include features identified in the gap analysis assessment. During the gap analysis, the OpenLMIS community collected and identified 24 gap features and 12 reports that exist in the Tanzania and Zambia eLMIS (TZM eLMIS) instances but not in OpenLMIS v3. Of the identified gaps, five of the features/reports are either not in use in TZM eLMIS or are requests for new functionality, but the team felt it important to document those requests in case the community has an opportunity to fund high-priority backlog items for the Zambia and Tanzania implementations.
We have organized the features into the following three categories to support work being done in parallel and achieve scope across all three priority areas:
- Reporting & Analytics (across levels)
- Interfaces to external systems (includes ERP, mobile, and offline applications)
- Features
- Requisition enhancements (favoriting products, columns, usability improvements, budgets)
- Fulfillment and re-supply features and enhancements
- User personalization and self-service (configuration, notifications, dashboards)
- Equipment tracking
Please reference this high-level presentation for a quick overview of the project.
The project is structured in two phases: planning and development.
- Phase 1: Planning. Will include a in-person meeting to review scope, conduct estimations, schedule work and present the roadmap to the Product Committee. This phase will entail both creating the work plan for development teams and onboarding the teams for phase 2. We anticipate that there are two in-person meetings, one for planning and one for ‘kicking-off’ the development work for onboarding.
- Phase 2: Feature development. Will include the work associated with building out the features in accordance to the roadmap. May include in-person meetings between teams or with customers when approved by the community and with adequate funding available.
Consortium Team
VillageReachVillageReach was established in 2000 to address the challenges of delivering quality healthcare at the last mile to the most underserved communities. In addition to focusing on a particular segment of the healthcare delivery challenge at the last mile, VillageReach’s focus is to improve the effectiveness and efficiency of the health system services that support the delivery of healthcare and services. Support from the Bill and Melinda Gates Foundation (BMGF) helped VillageReach establish a dedicated OpenLMIS Global Core (Core) team. The Core team has served as the backbone support organization for the continued development of OpenLMISv3 and the OpenLMIS Governance, Product and Technical communities. OpenLMISv3 was released February 2017, and new features have been released on a monthly and quarterly basis since then. In addition to the maintaining the core source code, the Core team’s dedicated Community Manager has helped formalize the committees and practices that guide the management and direction of OpenLMIS. JSIIn business for more than 35 years, John Snow, Inc. (JSI) is a public health management consulting and research organization dedicated to improving the health and wellbeing of individuals and communities throughout the world. With a portfolio of over 150 health supply chain projects in over 100 countries over three decades, JSI has deep experience optimizing supply chains that are more responsive to public health needs while contributing to global best practices in data visibility and use, system design, human resources for supply chain management, and commodity security. In recent years, JSI enhanced an earlier code branch of OpenLMIS for Tanzania, Zambia, Côte d’Ivoire and, most recently, Guinea ("eLMIS"). In both Tanzania and Zambia, the applications were deployed at national scale and are fully institutionalized within the health sector, exchanging data routinely with warehouse management systems in the medical stores of each country. As such, JSI’s subject matter expertise and ongoing operational engagement are crucial for bridging the existing gaps between the TZM code base and the OpenLMIS 3.x architecture. OnaOna is a Nairobi-based software and consulting company that offers technical consulting, design, and software-related services for organizations and projects of all sizes. The company’s consulting clients include WHO, UNDP, HNEC - Libya, The World Bank, UNICEF, and DFID. The Ona team has nearly a decade of experience designing, developing and implementing ICT enabled solutions for humanitarian, development and global health contexts. This includes developing one of the first national-level SMS facility-based reporting tools. When possible, the company tries to build on top of supported platforms and tools like Ona, RapidPro, DHIS2, and OpenMapKit, allowing them to build reliable, scalable solutions for lower cost. Ona follows an agile methodology to ensure projects are delivered on time and on budget. The team has extensive experience developing in Java, JavaScript, and Android as well as robust Sight Reliability Engineering practices. The Ona team is comprised of Matt Berg, CEO who will be acting as an adviser on the project. Peter Lubell-Doughtie, Roger Wong and Craig Appl will work as shared resources for Reporting Architecture, UI-UX and Requirements Subject Matter Expertise. The Ona Technical team is comprised of Craig Appl who is the technical project manager, Clay Crosby who is the data project manager, two senior engineers and two engineers. Each engineer is specialized in Sight Reliability Engineering (SRE) and reporting infrastructure. Team Structure
Source: https://boardthing.com/board/5a2f5126b2d40b061d0c0e19 |
In-person Meetings
Pre Award: Initial Project Discussion on at JSI office in DC.
Recap of the meeting and key outcomes: Meeting Agenda and Presentation: Only made it to slide 33. |
Phase 1: Estimation Meeting on - at JSI office in DC
GoalsTo understand the scope, estimate and create a roadmap of the work (which includes an order based on priority), and begin to assign work to teams. We will need to get the schedule approved by the Governance committee. Once that is done, we can submit deliverables to PATH and begin the second phase of the project, feature development. We will go deeper into the specific work areas than we did during our meeting in DC. We will have attendees from each organization so we can conduct estimation activities and so we can assign initial work items to different teams. Attendees
ScheduleThe person leading the conversation is identified in BLUE.
PRESENTATION: https://docs.google.com/presentation/d/1TWIpRNIG21nTGO_sTDjRXkirFb3HlV3-HeYTPK17Ttg/edit?usp=sharing |
Notes from the Estimation Meeting
Day 1
Day 2
Reporting by Muhammad Ahmed (Unlicensed), Ashraf Presentation: https://docs.google.com/presentation/d/1ZJjvb8hoUC_k3RK06Bw0eeQz4c1yepBgFTA7hGuNufc/edit?usp=sharing
OpenLMIS Reporting Strategy
Discussion Notes:
Interfaces Unfortunately it was challenging to take notes during this conversation and it was very circular.
What we have today?
What we need to do?
Locations
Day 3
Team started to discuss what each team wants to work on: JSI
Ona
VR
Team StructureTentative team structure based on Dec. 7, 2017 meeting:
source: https://boardthing.com/board/5a2f5126b2d40b061d0c0e19 |
Follow up from the Estimation Meeting
ToDo:
Items which need to be discussed for the Gap Project:
Additional Conversations which are wider than the Gap Project
|
Phase 2: Development Kick off - TBD
Location: TBD
Attendees: TBD
Call Meeting Notes
Coordination Call on
Participants: Edward, Jake, Mary Jo, Matt Agenda 1.) Agree on funding mechanism
2.) Schedule in-person (JSI-Ona-VR+USAID/PATH) for week of GDHF week? Perhaps Thursday, Dec 7th or Friday, December 8th? For the in-person in DC (which should probably include Lindabeth, Carl and maybe Kaleb), we’d like to discuss the following:
Next Steps:
|