Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

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 User Personas.

UsersRoleContext, Concerns, Comments
ImplementorUploads the facilities, programs, periods, schedules
  • Intermediate technical skill set (create csv file imports)
  • Must have all data needed for configuration of the system
  • Has internet connectivity
Storeroom Clerk or 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 or Facility 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
District/Regional Manager

Approves or rejects requisitions.

  • Doesn't use OpenLMIS often, just for approvals
Warehouse ClerkApproved requisitions are converted into orders based on their supply line.
  • System can automatically convert if there isn't a choice on which supply line will be used for fullfillment

 

Mary Jo Kochendorfer (Deactivated) - for background

  • No labels