OpenLMIS needs a description of how it releases non-functional requirements, and specifically performance ones, and a process to guide the project to defining them.
The description needs to orient the reader toward what a non-functional requirement is: which stakeholders does it serve and how does it serve them.
A few key considerations:
Total set of entities v. active use
By domain: Requisition's vs. CCE
By rural to urban connections (2G, 3G, etc)
By client device (web vs. mobile)
RTD page that introduces non-functional requirements, with a focus on performance
RTD section that introduces a simple process of determining what the requirement is - how to give a best recommendation even though field environments are quite variable.
Start and/or write further tickets for existing domains.