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
- Video demo the requisition process
- High-level overview of requisition process
- Current 2.0 functionality on the demo server
Main users in the Requisition process
| Users | Role | Context, Concerns, Comments |
|---|---|---|
| Implementor/Admin User | Uploads the facilities, programs, periods, schedules |
|
| Storeroom Manager (or supervisor) | Creates and edits requisitions. Can provide overview comments and context if needed. |
|
| Facility Manager | Authorizes or declines the requisition. Can edit the requisition quantities and leave comments. |
|
| District/Regional Manager | Approves or rejects requisitions. Approvals are convered into orders. |
Initiate
Based on
- my facility (or my supervised facilities)
- program
- processing period (within a schedule)
- type (emergency or regular)
the storeroom manager (or supervisor) wants to order supplies for the specific facility
Create
Storeroom manager determines how much stock to request based on
- Stock on hand
- Consumption
- Losses and adjustments
Open Questions
- What value does the "Operated by:" field provide?
- What does the "Maximum Stock Level:" mean? Do we know if it is used in the Requisition process?
- What does "Emergency Order Point mean?"
- Can the Admin user configure different fields for this header? Within what parameters? Which are given?
Authorize
- Facility manager, based on supervisory node, reivews the requisition. Facility manager can edit the quantities requested
Approve
Convert
Mary Jo Kochendorfer (Deactivated) - for background