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 within 3.3
- Current 2.0 functionality on the demo server
Table of Contents
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.
Gliffy | ||||
---|---|---|---|---|
|
Main users in the Requisition process
The following users are pulled from the larger list of External User Profiles.
Users | Role | Context, Concerns, Comments | ||
---|---|---|---|---|
Implementor/Admin User | Uploads Configures the system and uploads facilities, programs, periods, schedules |
| Storeroom Manager (or supervisor), and other reference data. |
|
Storeroom manager | Creates and edits requisitions. Can provide overview comments and context if needed. |
| ||
Facility Store Manager | Authorizes or declines the requisition. Can edit the requisition quantities and leave comments. |
| ||
District/Regional ManagerProgram Supervisor | Approves or rejects requisitions. Approvals are convered |
| ||
Warehouse Clerk | Takes the approved requisitions and converts them into orders. |
Mary Jo Kochendorfer (Deactivated) - for background
...
|
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
Gliffy | ||||
---|---|---|---|---|
|