[DISC] Reporting Domain: Delivery/Re-Supply KPIs

Target release

Vaccine Module

EpicReporting Domain
Document status
DRAFT
Document owner
Technical LeadTechnical Lead who reviews or supports document

Goals/Scope

    • This page captures the KPIs needed for the Reporting Domain, pertaining to Delivery/Re-Supply.
    • This only captures KPIs as per global standards (DISC Guidance) and not the KPIs that might be used at country level or the custom reports required by specific users to support their workflow (Captured elsewhere).

Background

Are there any country specific features that should be noted? Who are the personas? Who are the users that will be interacting with this functionality? What are their challenges, responsibilities, and level of connectivity? These personas are intended to be representative archetypes of the key stakeholders who will participate in theses workflows/scenarios. 

Assumptions

  • What are technical or business specific details and characteristics that should be known to explain the environment? List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this features from a tablet).

User Stories

Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.

#TitleUser StoryDefinitionLabelImportanceNotes
1On-Time and In-Full Deliveries Describe the user and what they are trying to achieve

As a ______ I want/need to ________ so that I _______.

- High level acceptance criteria

Percentage of deliveries delivered on-time and in-full (OTIF) with OTIF defined as order fulfilled: store can fulfil the complete order (i.e. provide all products and quantities requested); on time: order is delivered when expected (e.g. on a specific date or time range); and accurate: orders are delivered in the correct quantities and products (i.e. delivered products and quantities match the delivery note)

This is a composite indicator arrived at by looking at two indicators --

% on time delivered/fulfilled

and

% of orders delivered/fulfilled in full

The common factor in both indicators becomes the OTIF indicator

DISCMust Have
  • Used to ensure appropriate store ability to meet the needs of the clients, as well as timeliness and reliability of order deliveries. The indicator can be used to monitor in-coming shipments, in-country distribution by the national store or outsourced distributors.



Calculation, Data Needed, Data Sources

KPICalculationData NeededData Sources
On-Time and In-Full Deliveries

Proportional vaccine wastage in unopened vials = (number of doses discarded during reporting period) / (doses under management during the same period) x 100%                                      

Doses under management is defined as the opening balance plus all doses that were received during the period. Issued doses should not be subtracted.

Order requested by product and quantity.

Order picked and dispatched by product and quantity.

Scheduled delivery date or delivery range.

Products, quantities and time of receipt for dispatched orders by order.

Order delivery note.

Submitted requisition / order.

Proof of delivery.

Delivery schedule.

Vaccine arrival report.

Advanced shipment notification.

Need a diagram in place showing nodes of where the indicator is reviewed and which aspects of the node between them are impactd by this

Diagrams

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.


Dependencies

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.

DescriptionLink
Name of story or release Link to JIRA


Open Questions

Initial communication between stakeholders and the development team to help understand scope and estimates.

Below is a list of questions to be addressed as a result of this requirements document:

#QuestionOutcomeStatus
1(e.g. How we make users more aware of this feature?)Communicate the decision reached Open, In Progress, Closed, and date of closure

Out of Scope

    • List the features discussed which are out of scope or might be revisited in a later release. 


OpenLMIS: the global initiative for powerful LMIS software