Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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
nameSimplified Requisition Process

Main users in the Requisition process

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

UsersRoleContext, Concerns, Comments
Implementor/Admin UserUploads the facilities, programs, periods, schedules
  • Basic Intermediate technical skill set (create csv file imports)
  • Must have all data needed for configuration of the system
  • Has internet connectivity
Storeroom Clerk or Manager (or supervisor)Creates and edits requisitions. Can provide overview comments and context if needed.
  • May 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.

Approvals are convered into orders. 

  • 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

...