Velocity:Context: Includes all four teams. Team performance is impacted by manual testing, regression testing began in Sprint 105, released 3.4 in Sprint 106, released 3.5 in Sprint 113, Holidays impacted 114 and 115.
Provide the MoH with context for how a digitized supply chain can benefit them. There were a number of training and capacity building activities to that end
SIGLOFA is the name in Angola- Sistema Informatica de Gestao de Logistica Farmaceutica de Angola
Rollout of the initial pilot in March - Hospitals in Luwanda, another pilot in April, testing and training May-June, June-July UAT (last pilot), National launch in August (many trainings throughout the country)
Provided responsibilities within the MoH within a technical working group-foster ownership and sustainability. Lead of the group is the IT Lead with the MoH
Refined requirements and got more user feedback in 2 learning sessions, 3 days each. That included the launch of the validation instance
Established a lot of SOPs for supply chain at various levels, and an M&E plan - from scratch! Need to create an SOP that works with OLMIS as well as the fallback paper-based system.
Goals of the pilot: evaluate the system, provide training to users, install hardware, re-assess sites for readiness, re-assess inventory
Most sites have reliable(ish) power. The power still goes out 4-5 times a week for less than a couple of hours. They are currently not targeting the cold chain.
There were some issues completing the inventory process (meds were not the same as what was listed on National Med List).
SOPs needed updating to improve how they do reporting
Differences in how stock is counted between sites
Area for improvement: MoH use of GS1 standards
Reinforce messages from the SOPs in the roll out training since the SOPs are new, they are still not well adhered to
Still working on version 3.5 due to the scheduling of 3.6 release
Large amount of work to get the OpenLMIS Reports set up and configured
Translation work has taken longer than expected
Built-in OpenLMIS Translations worked fine, implementation-specific changes were problematic
Products that are used for multiple programs: if you create different product codes that can introduce issues with GS1; want to have visibility of data–if it gets updated for one program, does it update for others? Yes, if you are using the stock management function, it would get updated for the other program. If there are different codes associated with different programs then they would be treated separately. There could be other implications here that need to be validated/thought through