| Target release | 3.5 |
|---|---|
| Epic |
Ashraf please insert the edge case epic here. |
| Document status | |
| Priority | |
| eLMIS Status | |
| OpenLMIS Status | Not Implemented |
| PATH | Jenny Thompson (Unlicensed) |
| OpenLMIS | Mary Jo Kochendorfer (Deactivated) |
| JSI | Ashraf |
|
To enable import of shipment data from an ERP into OpenLMIS so that that data can be visible to facilities and districts, and so that delivery data can be compared to shipment data through OpenLMIS. Shipment data shows whether and when orders are shipped and any changes between the ordered and shipped products and quantities. If the facilities and districts have this data, they can take actions such as re-distributions or purchases through private supply chains earlier, rather than waiting for the actual MSD delivery before they know of any changes to their order. This also increases accountability and visibility showing at what point in the supply chain any problems or bottlenecks occur.
Status in eLMIS: In eLMIS, not in use
Status in OpenLMIS: Not in OpenLMIS
Priority: High priority
After MSD receives R&Rs from OpenLMIS and converts them into orders, a shipment is done. The shipment may or may not correspond exactly to the order. For example, amounts may be lower due to lack of stock at the central stores, or lack of availability of one product may lead to another similar product being substituted for it.
MSD records the shipment data in the ERP, but without this feature, this data is not accessible to facilities or districts. For that reason, facilities and districts do not know whether their order has been adjusted by MSD, whether and when it has been shipped, and when to expect delivery.
See also sections of the document “System requirements specifications for eLMIS interface with mSupply” which discuss export of shipment file. [called out in open questions]
This feature is documented at https://openlmis.atlassian.net/browse/OLMIS-644
| # | Title | User Story | Label | Importance | Notes |
|---|---|---|---|---|---|
| 1 | Import shipment data from ERP to OpenLMIS | As a facility/district user, I want to be able to import shipment data from an ERP into OpenLMIS so that data are visible to facilities and districts and delivery data can be compared to shipment data in OpenLMIS. | Tanzania eLMIS | Must Have | |
| 2 | View shipment data | As a facility/district user, I want to be able to see when shipments were made and any differences between the products and quantities shipped from what was ordered in OpenLMIS so that I can take action, such as re-distributions or purchases through private supply chains earlier. | Tanzania eLMIS | Must Have | Without this they have to wait for the actual MSD delivery before they know of any changes to their order. |
| 3 | View shipment adjustment data against orders | As a facility/district user, I want to visibility to order differences against what's shipped so that I can identify and address problems or bottlenecks in the supply chain. | Tanzania eLMIS | Must Have | |
| 4 | Export shipment data from ERP to central store | As a central store user I want data exported from the ERP to OpenLMIS when shipment occurs so that I can track shipments. | Tanzania eLMIS | Must Have | The shipment file should contain:
|
| 5 | Human readable shipment file | As an Logistics office I want data to be included in the shipment file which is human readable, including data that can be derived from the shipment file together with order data and configuration data, so that I can manually cross-check, if needed. | Tanzania eLMIS | Must Have | To make the information human-readable:
|
| 6 | Advance shipment notification | As a supervisor at a receiving facility, I want an advance shipment notification can be sent to me and my facility when shipment data is received into OpenLMIS, an the receiving facility so that I know a shipment is on its way. | Tanzania eLMIS | Must Have | |
| 7 | Error handling | Error handling for shipment files with invalid data ... |
Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.
Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.
| Description | Link |
|---|---|
| Name of story or release | Link to JIRA |
Initial communication between stakeholders and the development team to help understand scope and estimates.
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | Confirm where “System requirements specifications for eLMIS interface with mSupply” is/which document this is referring to. There's a specifications document and the interface-related Tanzania gap documentation speaks to mSupply, but it's not referenced this way. | Chris Opit (Unlicensed) could you share more information on how it is done with mSupply? How does mSupply tell eLMIS about the shipments? | Open |
| 2 | For Tanzania user stories: review the "so thats" added, review the label, and review the priority level. | Open | |
| 3 | Does this align with our documentation or understanding of shipments outlined Order and Shipment files? Is there any diagrams for these? | Open | |
| 4 | Is the shipment file in anyway related to proof of delivery and closing the loop on quantity requisitioned, ordered, shipped, received/rejected (and therefore returned), updated stock on hand at warehouse/depo? |
Gap Estimation Notes 4/12/2018