Pular para o conteúdo principal
La version française est traduite automatiquement de l'anglais. // La versión en español se traduce automáticamente del inglés. // A versão em português é traduzida automaticamente do inglês.

Section 6. Supply Planning Module: Reports

QAT reports allow the user to extract and view their supply planning data in graphs, tables, and other visual formats. The user will also be able to navigate, sort, filter, and view the data for specific needs. QAT reports produce visualizations and display data in a way that can support decision making.

Note: All QAT reports have the ability to be exported into an Excel CSV file as well as PDF format. Additionally, all graphs allow for the user to hover over a visual for a tool tip with more information.

A. Supply Plan Report​

Purpose: to allow the user to quickly assess the stock status of one or more selected programs and/or planning units, by graphically comparing the stock projections to dynamic minimum and maximum inventory levels and to be able to see all consumption (both actual and forecast), inventory, and shipping details in one place. The report provides a graphical representation of the supply plan, as well as a tabular view. The report can be exported in PDF and/or CSV format.

  • Accessible to: Realm Admins, Program Admins, Program Users, and Reports Viewer
  • Navigation: Reports → Supply Plan Report

Users can utilize the various dropdown parameters at the top of the screen to generate different views of the Supply Plan Report. Each view of report generated, will have both a graphical representation and tabular equivalent of the data. There are three main views of the Supply Plan Report:

  1. Single Program View
    1. Single program
    2. Single Planning Unit (PU) or single Alternate Reporting Unit (ARU)
    3. Shipments disaggregated by status (i.e. planning, shipped, received, etc.)

    Figure 115: Supply Plan Report: Single Program View, GraphFigure 115: Supply Plan Report: Single Program View, Graph

    Figure 116: Supply Plan Report: Single Program View, Tabular DataFigure 116: Supply Plan Report: Single Program View, Tabular Data

  2. Multi-Program View
    1. Multiple programs
    2. Single PU or ARU
    3. Shipments disaggregated by program (i.e. FASPonia Malaria MOH & FASPonia Malaria Social Marketing)
    4. Notes: QAT is able to aggregate the supply planning data across multiple programs if they share the same PU/ARU. This could be useful if a country has multiple parallel programs monitoring the same products and would like to see an aggregated or national view of the stock status over time.

    Figure 117: Supply Plan Report: Multi-program ViewFigure 117: Supply Plan Report: Multi-program View

    Figure 118: Supply Plan Report: Multi-program/EU View, Tabular DataFigure 118: Supply Plan Report: Multi-program/EU View, Tabular Data

  3. Equivalency Unit (EU) View
    1. Single or multiple programs
    2. Multiple PUs (ARUs cannot be used with EUs)
    3. Shipments disaggregated by program, PU, or program-PU
    4. Notes: QAT is able to aggregate across PUs that are different (different pack sizes, usage rates, etc.), but related by utilizing an EU (see Equivalency Units for more information) and a corresponding conversion factor. This could be useful for countries or global viewers that would like to see concepts such as, Malaria Treatments, Couples Year Protection (CYP), ARV Patient Months, etc. as an aggregate.

    Figure 119: Supply Plan Report: Equivalency Unit ViewFigure 119: Supply Plan Report: Equivalency Unit View

Note:

  1. The report utilizes the Planning Unit settings set by the Program Admin for AMC, shelf life, MIN, reorder interval, and MAX
  2. The Shipment Quantity column is the sum of all shipments that have a receive date in the same month for that planning unit
  3. The “Shipment Quantity | Funding Source | Shipment Status | Procurement Agent | RO – Prime line No | Order No – Prime line No” column allows the user to see the disaggregated shipments that have receive date in the same month, including details of quantity, procurement agent, status, funding source, and order number assigned to that order
  4. The “Consensus Consumption” column only appears if a user chooses multiple programs for aggregation
  5. The PDF and CSV exports have multiple options, similar to the report dropdowns, allowing for exports of aggregated programs, multiple single product supply plans, or aggregated products (via EUs)
Calculations for the Varying Supply Plan Report Views:
Single Program

Ending Balance = Opening Balance – Consumption + Shipments ± Adjustments – Expiries

MOS = Ending Balance / AMC

Multi-Program/Equivalency Unit
Same ending balance & MOS calculation

Forecast, Actual, Shipment, Adjustment, Expiries, MIN, MAX = Σ selected programs individual data elements

Consensus consumption: Σ selected program actuals (if available), otherwise forecasts. Therefore, this could be a sum of actuals and forecasts depending on data available.

B. Supply Plan Scorecard​

Purpose: To generate an overall score for each program's supply plan based on Quality (including data completeness and procurement scheduling) and Stock Status (against minimum and maximum levels). It highlights areas needing improvement and allows global users to compare performance across programs.

  • Accessible to: Realm Admins, Program Admins, Program Users, and Report Viewers
  • Navigation: Reports → Scorecard
  • Notes:
    • The score uses the same criteria as the QAT Problem List, a validation screen for program users and admins, and it is not tied to a specific reporting period.
    • Downloaded program versions recalculate using the current date; server-based versions calculate using the upload date.
    • Results can be viewed at three levels:
      • Individual program
      • Aggregated programs by country
      • Aggregated technical areas by country
    • Higher scores indicate stronger supply plan performance. Scores are color-ranked, with a target score of 90%.

Scorecard Top Graph – View by Program Scorecard Top Graph – View by Program

Scorecard Bottom Table – View by Program Scorecard Bottom Table – View by Program

Scorecard Top Graph – View by Country x Technical Area Scorecard Top Graph – View by Country x Technical Area

Scorecard Bottom Table – View by Country x Technical Are Scorecard Bottom Table – View by Country x Technical Are


How Scores Are Calculated

  1. Overall Supply Plan Score: calculated as an average of the Quality Score and the Stock Status Score.

    Example

CategoryScore
Data Quality Score65%
Stock Status Score57%
Overall Supply Plan Score61% = (65% + 57%) / 2
  1. Quality Score: For each criterion, QAT calculates the proportion of compliant planning units relative to the number of active planning units. These compliance percentages are then averaged to produce the Quality Score.

    • Forecasted Consumption: Missing forecast consumption data in the next 18 months results in the planning unit being marked non-compliant.
    • Actual Consumption: Missing recent actual consumption data in the last 3 months or gaps within the last 6 months results in the planning unit being marked non-compliant.
    • Actual Inventory: Missing actual inventory data in the last 3 months results in the planning unit being marked non-compliant.
    • Shipments: QAT identifies planning units with procurement scheduling issues, including:
      • Shipments with past receive dates but not marked received
      • Shipments that should have been submitted, based on lead time, but are still not marked submitted
      • Note: Any procurement scheduling issue results in the entire planning unit being marked non-compliant.

    Example: The supply plan has 12 active planning units.

CriteriaPlanning Units in CompliancePercentage In-Compliance
Forecasted Consumption99 / 12 = 75%
Actual Consumption77 / 12 = 58%
Inventory55 / 12 = 42%
Shipments1010 / 12 = 83%
Quality Score65% = (75% + 58% + 42% + 83%) / 4 criteria
  1. Stock Status Score: calculated based on the number of months, 18 months into the future, that each planning unit is stocked-to-plan. QAT calculates the proportion of compliant planning unit-months, meaning stocked-to-plan, relative to the number of possible months.

    Example: The supply plan has 12 active planning units.

    • Numerator = Planning unit-months in compliance (Stocked-to-Plan)
      = 120 months
    • Denominator = Maximum planning unit-months in compliance
      = (18 months of data x number of active planning units) - months with stock status as N/A
      = (18 months of data x 12 active planning units) - 5 months as N/A
      = 211 months
StatusMonths in CompliancePercentage In-Compliance
Stocked-to-Plan120100%
Above Max310%
Below Min530%
Stocked Out70%
N/A5-
Stock Status Score-57% = 120 / 211

C. Stock Status Reports​

C1. Stock Status Over Time​

Purpose: to compare one or more products and their inventory-levels across a period time.

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports ➔ Stock Status Over Time
  • Notes: The Planning Unit can be single, multi-select, or select all. The “Select All ” option may not be advantageous if the program has many planning units, as the graph will not be able to decern the individual lines on the graph. We suggest choosing less than ten products at once. Specifically, this report can be useful to compare categories.

Stock Status Over Time Report Stock Status Over Time Report

C2. Stock Status Matrix​

Purpose: to provide a quick snapshot of the months of stock across time in an easy-to-read table format.

  • Accessible to: Realm Admins, Program Admins, Report Viewers and Program Users
  • Navigation: Reports ➔ Stock Status ➔ Stock Status Matrix
  • Notes:
    • One row is shown for every planning unit & year combination, based on what’s selected in the top filters.
    • QAT will display the MOS or quantity for each planning unit based on whether the product is planned by quantity or MOS, as selected in the Update Planning Units screen (see Section 4.A2).
    • Colors corresponds to the stock levels during that particular month:
      • Red – Stocked Out
      • Orange – Under Stocked
      • Green – Stocked to Plan
      • Yellow – Over Stocked
      • Grey – N/A (QAT is unable to calculate the value due to missing data)
    • Although the CSVs does not export the conditionally formatted colors, the PDF contains the colors and users may copy and paste the table to keep all the colors and formatting.

Stock Status Snapshot Report Stock Status Snapshot Report

C3. Stock Status Snapshot​

Purpose: to give a high-level view of a program’s stock status across planning units at a single point in time (one month).

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports ➔ Stock Status Snapshot
  • Notes:
    • The various color corresponds to the stock levels during that particular month:
      • Red – Stocked Out
      • Orange – Under Stocked
      • Green – Stocked to Plan
      • Yellow – Over Stocked
      • Grey – N/A (QAT is unable to calculate the value due to missing data)
    • Although the PDF and CSV do not export the conditionally formatted colors, users may copy and paste the table to keep all the colors and formatting.

Stock Status Snapshot Report Stock Status Snapshot Report

C4. Stock Status Snapshot (Global)​

Purpose: to give a high-level view of a program’s stock status across planning units at a single point in time (one month) for multiple programs.

  • Accessible to: Realm Admins, Program Admins, Program Users, and Report Viewers
  • Navigation: Reports ➔ Stock Status Snapshot (Global)
  • Notes:
    • The various color corresponds to the stock levels during that particular month:
      • Red – Stocked Out
      • Orange – Under Stocked
      • Green – Stocked to Plan
      • Yellow – Over Stocked
    • Although the PDF and CSV do not export the conditionally formatted colors, users may copy and paste the table to keep all the colors and formatting.

Stock Status Snapshot (Global) Report Stock Status Snapshot (Global) Report

D. Consumption Reports​

DI. Consumption (Global)​

Purpose: to visually show the consumption of a planning unit or multiple planning units across countries.

  • Accessible to: Realm Admins, Program Admins, Program Users, and Report Viewers
  • Navigation: Reports ➔ Consumption (Global)
    • Notes:
      • The various colors stacked in the horizontal bars represent different countries. Users can determine which country by referencing the graph legend.
      • The x-axis corresponds to the consumption quantity (in millions) for each country.

D2. Forecast Error (Monthly)​

Purpose: to visually show forecast accuracy using the weighted average percent error (WAPE) method, over time, while viewing the forecasted consumption against the actual consumption.

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports ➔ Forecast Error (Monthly)

Forecast Error (Monthly) Report Forecast Error (Monthly) Report

  • Notes:
    • In the graph, the red vertical bars represent the actual consumption, the blue vertical bars represents the forecasted consumption, the green line (which uses the right axis), represents the forecast error, and the turquoise dotted line represents the forecast error threshold (see Figure 115: Forecast Error (Monthly) Report).
    • The forecast error threshold (%) per planning unit is set by the Program Admin in the Update Planning Units screen. If a forecast error is above the set forecast error threshold (%), it will appear in red text in the data table.
    • The Report View can be viewed in multiple ways:
      • Forecasting unit. A user may want to choose forecasting unit when comparing in base units, such as with medicines that have different bottle sizes (planning units) sharing the same forecasting unit (e.g. the antiretroviral TLD30 vs TLD90 - See Figure 116.)
      • Equivalency Unit: A user may want to choose forecasting unit when comparing products with different forecasting units, but some programmatic link (e.g. malaria treatments AL 6x1 vs 6x2 – see Figure 117.)
      • “Show consumption adjusted for stock out?”: If this checkbox is checked, QAT uses the adjusted actual consumption instead of the actual consumption. QAT calculates the total days in the month based on the calendar.
    • Missing Data:
      • If data is missing for either forecasted or actual consumption, there will be a missing segment of the line or a missing bar in the graph
      • If there is missing data for actual or forecasted consumption, it will not be possible to calculate the forecast error and the user may see a gap in the line graph
    • Formula: Forecast Error uses the Weighted Average Percent Error (WAPE) formula. The example below uses the time windows of 6 months.
      • Time Window: For non-seasonal products with predictable consumption pattern, use a short time window, but consider using a longer time window for those products with a more variable consumption or those with seasonality (use a time window at least long enough to consider the entire season).
      • For more details on the logic QAT uses to calculate this report, see the “Show Formulae” in the tool.

WAPE Formula with 6-month time window as example

WAPE Formula with 6-month time window as example

Forecast Error (Monthly) Report – displayed by forecasting unit Forecast Error (Monthly) Report – displayed by forecasting unit

Forecast Error (Monthly) Report – displayed by equivalency unit Forecast Error (Monthly) Report – displayed by equivalency unit

D3. Forecast Error (by Planning Unit)​

Purpose: to assess forecast accuracy for selected products during a specific month across countries and programs.

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports ➔ Forecast Error (by Planning Unit)
    • Notes:
      • For the time window, non-seasonal products with predictable consumption pattern can have a short time window, but those that have a more variable consumption/those with seasons should have a long-time window, or at least long enough to consider the entire season.
      • In the table, the forecast error percentages that are above the forecast error threshold (%), set by a Program Admin in the Update Planning Units screen, will be highlighted red
      • If there is missing data for actual or forecasted consumption, it will not be possible to calculate the forecast error and the user will see an error message in the table.
      • Forecast Error uses the Weighted Average Percent Error (WAPE) formula:

WAPE Formula WAPE Formula

Forecast Error (by Planning Unit) Report Forecast Error (by Planning Unit) Report

E. Shipment Reports​

EI. Shipment (Global)​

Purpose: to aggregate procurement quantities by funding source, procurement agent, and procurement agent type across all countries and programs.

  • Accessible to: Realm Admins, Program Admins, Program Users, and Report Viewers
  • Navigation: Reports ➔ Shipments (Global)
    • Notes:
      • The two graphs that appear first in the Shipments (Global) Report depict the aggregated quantity of shipments per country and cost of the shipments (in USD) per funding source for a single planning unit. For a tabular view of the data, the user may find details in the bottom two tables.
      • If a country does not procure the selected planning unit, it will not appear in the graph of the tables in the report.

Shipment (Global) Report Shipment (Global) Report

E2. Shipment Overview​

Purpose: to aggregate procurement quantities by funding source or by procurement agent type across all countries and programs.

  • Accessible to: Realm Admins, Program Admins/Users, and Report Viewers
  • Navigation: Reports → Shipment Overview
  • Notes:
    • Once navigating to the Shipment Overview screen, Users will see dropdowns in which they must fill out to show specific data. Once selecting certain dropdowns or all, users are shown a graph and a pie chart. The graph that appears first in the Shipments Overview Report depicts the aggregated quantity of shipments across countries and cost (in USD) of the shipments per funding source across planning units. The pie chart shows percentages of Funding Source depending on user selections while also being able to hover over to see the total amount (in USD). Users may also choose to group the data by Procurement Agent Type or Funding Source Type. For a tabular view of the data, the user may find details in the bottom table.

Shipment Overview Report Shipment Overview Report

E3. Shipment Details​

Purpose: to provide a comprehensive view of all shipments for a program.

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports → Shipment Details
  • Notes:
    • The top graphs shows total USD per month by shipment status
    • There are two tables below the graph: the first one provides a summary and the second one provides detailed information on shipments.
      • The summary table shows the total number of shipments, and total costs per funding source, for the selected time period.
      • The detailed table contains the shipments disaggregated by planning unit, etc.

Shipment Details Report Shipment Details Report

E4. Shipment Cost Details​

Purpose: to provide a simple view of all shipments for a program and their total costs.

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports → Shipment Cost Details
  • Notes:
    • Can be displayed by funding source, procurement agent, or planning unit.

Shipment Cost Details Report Shipment Cost Details Report

E5. Shipment Cost Overview​

Purpose: to provide a general view of the total shipment costs per calendar year for a program and planning unit, by funding source.

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports → Shipment Cost Overview
  • Notes:
    • This report can be viewed in PDF or Excel (CSV) format
    • This report can be based on either the shipment receive date, or the shipment submitted date

Shipment Cost Overview Report Shipment Cost Overview Report

E6. Budget​

Purpose: to show the different budgets assigned to a program(s), the amounts allocated to shipments, the amount overspent (if applicable), and estimated amounts remaining. This program dropdown in this report is multi-select since multiple programs can share the same budget.

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports → Budget
  • Notes:
    • The graph shows every predefined Budget in a program and whether it is allocated to shipments (planned or ordered) and the remaining amount.
    • The tabular view of the graph also provides information on the funding source for each budget, start and end date, and other detailed information.

Budget Report Budget Report

F. Inventory Reports​

F1. Expiries​

Purpose: to provide planners with estimated quantities of planning units expiring in the future based on batch/shelf life

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports → Expiries
  • Notes:
    • This report pulls from data previously entered by including batch information on shipments, inventory, and actual consumption, and shelf life per planning unit. It displays the batch numbers, the receive date of the batch, shelf life of that batch (or planning unit), expiry date, and cost of the expired product.
    • The report can include quantities in planned shipments expected to arrive and expiry during the selected timeframe.
    • It will calculate (based on shelf life, stock projections, and forecast consumption) how much of a particular batch is expected to expire and when.
    • The report will calculate a cost of expired product, based on the quantity expired and the planning unit default price set by the user in the Update Planning Units screen.
    • The table is interactive. When the user clicks on the expired quantity, QAT will open a pop up with the batch ledger.

Expiries Report Expiries Report

F2. Cost of Inventory​

Purpose: for a selected month, provides an estimated cost of inventory based on actual or projected stock on hand and the planning unit catalog price.

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports → Cost of Inventory
  • Notes:
    • The report can include quantities in planned shipments expected to arrive during the selected timeframe.
    • The stock column could be based on an actual inventory or projected ending balance.
    • This report uses the following formula:

Cost of Inventory Formula

Cost of Inventory Formula

Cost of Inventory Report Cost of Inventory Report

F3. Inventory Turns​

Purpose: to show the number of inventory turns per planning unit, program, country, or planning unit category at a particular point in time. Inventory turns are a way to measure the velocity of the supply plans. Inventory turnover is a key performance metric often used to signal supply chain management effectiveness. It is usually a backward looking metric, but because QAT uses forecast data to estimate stock projections into the future, the report can also be used to view estimated inventory turns based on the plans. Generally, higher turns mean a healthier supply chain – products are moving downstream and being replaced by fresh products more frequently. Low turnover implies low consumption, possibly excess inventory – it could point for instance to program targets being too ambitious.

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports → Inventory Turns
  • Notes:
    • This report calculates inventory turns at various levels: at the individual planning unit level, at an aggregate level for an entire program (multiple planning units), and at an aggregate level for an entire country (multiple programs), or commodity category.
    • Planned Inventory turns: Are the possible months of stock for each month over 12 months if the inventory rules worked perfectly considering the Planning Unit’s MIN and Reorder Interval.
      • At the planning unit level, the report utilizes the MIN and Reorder Interval from Planning Unit Settings to calculate the “Planned” inventory turns.
      • At the program level (multiple planning units) QAT utilizes the mode of all planned inventory turns of all Planning units under a specific program.
      • At the country and/or Planning Unit Category level QAT utilizes the mode of all planned inventory turns of all Planning units under a specific country / PU Category.
    • Actual inventory turns:
      • At the planning unit level, QAT uses the following formula for each planning unit to calculate the actual inventory turns:

Inventory Turns Formula at the planning unit level

Inventory Turns Formula at the planning unit level

      • For each planning unit, the report compares the actual and planned turns, and calculates the MAPE and MSE.
      • To calculate the actual inventory turns at the program level, QAT will look for the mode across all planning units in that program. If no mode can be found, QAT will use the average from all planning units as that program’s actual inventory turns.
      • To calculate the actual inventory turns at the country (or commodity category) level, QAT will look for the mode across all programs. If no mode can be found, QAT will use the average.

Inventory Turns Report Inventory Turns Report

F4. Stock Adjustment​

Purpose: to show a list of all the manually entered stock adjustments in a program. Note: automatically calculated adjustments will not display on this report.

  • Accessible to: Realm Admins, Program Admins, Report Viewers, and Program Users
  • Navigation: Reports → Stock Adjustment
  • Notes:
    • Automatically calculated adjustments (as a result of a difference between projected ending balance and an inventory count) do not appear in this report.

Stock Adjustment Report Stock Adjustment Report