Implementers - August 13 2019

Software Development Update

Roadmap: Living Product Roadmap 

Current sprint: Backlog Grooming Sprint 130

Upcoming sprint: Backlog Grooming Sprint 131

Version 3.7: 

• What to see what is being worked on in this release, please see: https://openlmis.atlassian.net/projects/OLMIS/versions/12809/tab/release-report-done

Team stats: https://openlmis.atlassian.net/secure/Dashboard.jspa?selectPageId=12504

Velocity: 

Open

@Wesley Brown, @Sebastian Brudziński(5 min)

Living Product Roadmap Updated

Version 3.7 Update

• Development budget reduced - this affects the work that can be delivered

• Admin messages feature is complete

• Working on updating of Orderables

  • Already able to edit orderables via REST

  • Requisitions and Fulfillment services updated to "understand" the orderable version change

  • Edits via the UI are underway - mostly done

  • Client-side caching may not be completed in the 3.7 timeframe

Implementation Introductions

@Wesley Brown (10 min)

Quick introductions of the implementations on the call on the people representing them.

Study Tours

@Rebecca Alban (Unlicensed) (5 min)

For general Study Tour information http://openlmis.org/study-tours/

• Goal: to help countries willing to/interested in implementing OpenLMIS - eg. by visting a country that has already implemented OpenLMIS

• Countries can apply for funding by filling in the application available via the link above

OpenLMIS Community Meeting

@Rebecca Alban (Unlicensed)

• Planned for November 2019 in Johannesburg (around same time & place that GHSCS)

  • OLMIS Community Meeting - Nov 18-20 (Monday-Wednesday)

  • GHSCS - Nov 20-22 (Wednesday-Friday)

  • More info to follow

OpenLMIS in Emergency Contexts

@Wesley Brown (15 min)

We are looking for feedback on on this Discourse post by Josh: https://forum.openlmis.org/t/brainstorming-openlmis-in-disaster-crisis-conflict-contexts/5227

• Context: OpenLMIS could be well-suited for emergency situations

• Would need to work on making it easier to configure (a few days max, rather than several weeks)

• Matt: some organizations are interested in tools for such contexts

• Gaurav: Reach out to MSF, Save the Children, UNHCR

• Dercio: in Moz this was needed to track stock levels at facilities and to track expiration dates, especially with a lot of foreign aid coming to the country; must be easy to deploy

• Community input very appreciated in the topic above

Ways to filter Sources for Stock Movements

@Ben Leibert (Unlicensed) (5 min)

More info at: https://forum.openlmis.org/t/specification-of-stock-sources-and-destinations/5258

• Currently: Stock management allows to move stock or receive stock from another facility

  • Requires configuration: sources, destinations, organizations

• What is needed: limit the list of sources/destinations by geographic zone (same geo zone that the facility is in)

• Might need even more ways to filter sources/destination

• In Moz limiting by geo zones usually makes sense

  • There are rare cases where facility may need to receive/issue from another district (eg. because it's closer than a facility from the same district)

• Could introduce machine learning to "prioritize" or manage the order of the facilities in the dropdown by what's most often selected (automatically)

3.7 Feature Priorities

@Wesley Brown (5 min)

New Page for Feature Backlog: Feature Backlog

Potential 3.7 Feature and Priorities: 3.7 Scope Planning

This will be updated to only include those features scheduled for 3.7

Please fill out the ranking poll here: http://www.polljunkie.com/poll/wakcoc/openlmis-37-feature-priorities

Next PC meeting: Topic ideas??

Implementation/Partner Update, Feature Priorities

• Worth talking more about where each implementation stands

• Discussing plans for upgrade - Rebecca can showcase new toolkit docs

• Would the PC be a right place to invite interested countries to ask some questions about OpenLMIS? (pre-study tour)

  • Could show how community supports OpenLMIS implementations

• Dercio to talk about Angola implementation

Additional Requests and Information: