Page Comparison

...

Attendees

• Sam Im (Deactivated)

• Mary Jo Kochendorfer (Deactivated)

• Nick Reid (Deactivated)
• Rachel Powers (Deactivated)
• Chongsun Ahn (Unlicensed)
• Josh Zamor
• Brandon Bowersox-Johnson

Goals

1. Align on terms and understand our system's particulars
   1. General logistics process (SCOR overview) vs Openlmis processOpenLMIS process 
      1. Requisitions and Stock Management are specific concepts for OpenLMIS
2. Agreement on 3.3 Re-Supply scope so that we can move forward with requirements
   1. /wiki/spaces/OP/pages/118816956
   2. Create an Order (aka Simple Requisition)
   3. (Focus on high level overview of Re-Supply only)
   4. /wiki/spaces/OP/pages/135823499
   5. /wiki/spaces/OP/pages/88670474

OpenLMIS Services

Requisitions 3.0 handles three functionalities: Reporting, Requests, and Stock Management, all within one requisition.

Meeting Notes:

• Mary Jo explained the table above (live picture below):
  Image Added
• Lots of discussion about terminology and what parts to build first.

Questions:

• What terms do we need to align on to continue this discussion?
• Why did we decide to start on certain pieces first?
• What is "enable" in SCOR? Human resources, finance, costs, asset mgmt (per SCOR)
• Does SM tie into Local Fulfillment and POD? Yes
• MVP is described as:
  • Req Pickup
  • Req Deliver
  • Allocate Pickup (create an order directly)
    • create an order that needs to quickly fulfill
  • Allocate Deliver (plan a distribution)
• For allocation, does that mean there will be no POD because there is a pickup? There is still the concept of POD because it may be printed and signed for confirmation.

...

Assumptions:

Discussion items

...

Action items

• There is no shipment created in this scenario (Shipment-less POD).
• Convert to Order question: Local fulfill vs external fulfillment. How do we convert to order for local fulfillment? This question is on the requirements page for Create an Order
• Dependencies:
  • Question: How do we manage UI component dependencies that depend on different back-end services being on or off?
  • Josh: we need to come up with patterns
  • "soft dependencies" versus "hard dependencies"
  • "feature-based dependencies"
  • need to be clear which are build-time dependencies versus run-time
  • temporary decision: make Fulfillment dependent on CCE and SM for now (and revisit later; see Action Item below)
• Configuration has lots of open questions.
• If SM is not turned on, can you still fulfill an order using Local Fulfillment (when setting fill quantities?) No, stock management is needed to display your SOH.
• Which workflows need to work offline?
  • It depends. The SM Requisition could come from an offline tool.
  • The approvals could also be more offline (like you get an email–you don't have to log in to approve). But that is more of a different feature rather than standard "offline".
  • Local fulfillment might need to always be online.
  • Maybe we need to get it built and working and then once we see it working we can decide what parts work offline.

Action items

•  Josh Zamor and Nick Reid (Deactivated) hold the discussion about Dependencies, then share outcomes/decisions (consider if you want to share on Dev Forum or Tech Committee; also consider if Patterns come from this)
•  Nick Reid (Deactivated) notify SolDevelo that we want to create hard dependencies for the short term
•  Josh Zamor make a design document about services and responsibilities
•  Josh Zamor propose configuration of supply lines, local fulfillment, and SM Requisition/stock-based requisition template
•  Sam Im (Deactivated) hold a team kick-off of SM Requisition/stock-based requisition work (when we are ready; when it has a tech lead)
•   
•