The following comes from a discussion (on June 6, 2016) of the current state of OpenLMIS and the desired future state in 3.x.  Many questions are open and the concepts are draft.

Review and Reference

Table of Contents

High-level process for requisitions


It is important to note that the configuration of the requisition template dictates what the requisition form includes in terms of what columns, fields, and functionality (calculated versus user input) are available for the requisition creation and submission process.  


Main users in the Requisition process

The following users are pulled from the larger list of External User Profiles.

UsersRoleContext, Concerns, Comments
ImplementorConfigures the system and uploads facilities, programs, periods, schedules, and other reference data.
  • Intermediate technical skill set (create csv file imports)
  • Must have all data needed for configuration of the system
  • Has internet connectivity
Storeroom managerCreates and edits requisitions. Can provide overview comments and context if needed.
  • Data entry may be on or offline
  • Easy data entry
  • Only see relevant information
Store ManagerAuthorizes or declines the requisition. Can edit the requisition quantities and leave comments.
  • the authorizer is based on the supervisory nodes
  • May be on or offline
Program Supervisor

Approves or rejects requisitions.

  • Doesn't use OpenLMIS often, just for approvals
Warehouse ClerkTakes the approved requisitions and converts them into orders.
  • System can automatically convert if there isn't a choice on which supply line will be used for fulfillment


OpenLMIS 2.0: Configuring the system through requisitions

The following helps visualize the order of steps taken in the configuration guide.  Not all of the following will be applicable for 3.x OpenLMIS.  Please use the following for informational purposes but not requirement definitions.

Mock ups