Versions Compared

Key

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


Page Properties


Target release3.3
Epic

Jira Legacy
serverJIRA (openlmis.atlassian.net)
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-1294

Document status
Status
titleDRAFTDRAFTED
Document owner
Tech Lead


Goals

  • The goals of this requirements page is to document the user stories specifically related to the "X" feature. 

...


QuestionOutcomeStatus
1There are multiple ways countries look at the frequency for the ISA amoungs. Either we need to match these numbers to the resupply schedule or we can allow annual numbers which we divide by 12 or allow for annual numbers we divide by 24.  We need to come up with a way to determine what or how we define time period for the ISA targets.

2Open Question: Is the ISA number, which is uploaded, in doses or vials? We can calculate either way but need to make a call.Doses (because the way in which the ISA is calculated gives you an output which is dosageClosed
3Vidya – look into how the re-supply works in VIMS across multiple levels (if multiple resupply periods exist)

4Talk to SME about need for story #1 and story #2 and if it does make sense to have both (talk to them once the mock-ups are done to walk them through both stories via UI examples)

5

Need to write out the stories around calculating need with the requisition service and incorporating Chris' comment :

Typically we would calculate Max as X * AMC + Safety/Buffer stock, where X = number of months/weeks of a routine resupply period (e.g 1 month X AMC + safety stock). Safety stock is buffer plus lead time stock (stock used between when order is placed and stock is received). In practice, this might simply end up being Max = P * AMC + .5 AMC (buffer) + .5 AMC (lead time stock) = 2 MOS. Lead time stock is a variable, as is resupply period.



Out of Scope

Out of scope for this feature OR potentially saving for future development.

...