The indicator: OTIF
OTIF (On Time In Full) is the share of deliveries that arrived by the agreed date and with the full quantity ordered. A delivery that is on time but short, or complete but late, does not count.
On time = receipt date ≤ agreed date + tolerance
In full = quantity received ≥ quantity ordered × (1 − tolerance)
OTIF = deliveries on time and in full ÷ deliveries due in the period
On time % = deliveries on time ÷ deliveries due
In full % = deliveries in full ÷ deliveries due
Keeping on time and in full apart tells whether a supplier's problem is timing or quantity. The guide to supplier OTIF explains tolerances and how to use it in vendor rating.
What the dashboard shows
- Supplier ranking by OTIF, with on time and in full shown apart.
- Month by month trend for each supplier: who is getting worse and since when.
- OTIF by product family and by warehouse, because the same supplier can serve one site well and another badly.
- Average delay in days of late deliveries.
- Rows set aside by the data rules, with the reason, to be fixed in the source file.
The data you need
| Data | Where it usually sits | What it is for |
|---|---|---|
| Goods-receipt logs | Excel files in a SharePoint folder, one per warehouse or per month | Dates and quantities received |
| Purchase order lines | The ERP, or an Excel export in the same folder | Agreed date and quantity ordered |
| Supplier master | The ERP or an Excel file | Family, buyer, site served |
The key holding it all together is the order number with its line: if the receipt log does not record it, matching is done on supplier, item and date, with more room for error.
The steps in Muvia
In New source choose SharePoint, connect the account and point to the folder of goods-receipt logs. Muvia reads the files on the schedule you choose, and creates the table itself from the files' columns.
Connect the order lines: from the ERP, for example on SQL Server, or from a file in the same folder.
The data rules set aside impossible rows: receipt before the order, negative quantities, a supplier that does not exist. They stay visible, with the reason, and do not enter OTIF.
A query matches receipts with order lines and calculates on time, in full and OTIF delivery by delivery.
The dashboard shows the ranking; every month a PDF report goes to purchasing, ready for the meeting with suppliers.
The pitfalls of shared Excel files
- Different date formats: one warehouse writes 03/04 for 3 April, another for 4 March. A rule checking dates outside the expected range brings it out.
- Columns that change: if someone renames or adds a column in the template, Muvia's table does not take on new columns from a later file by itself; they have to be accepted explicitly.
- Split deliveries: several receipts for the same order line must be added up before judging “in full”.
- Requested or confirmed date: measuring against the requested date penalises a supplier for dates never accepted. Choose one of the two and write it in the definition.
- Overwritten files: if a month's log is edited after it has been read, the corrected row must be recognised as the same row, for example with a key on order, line and date.
Frequently asked questions
No. The files stay where they are and are filled in as before; Muvia reads them from the SharePoint folder. What changes is that nobody recalculates OTIF by hand any more.
They stay visible in a separate list, with the reason for rejection, and do not enter OTIF until they are fixed in the source file.
The one agreed with suppliers, usually a few days and a few percentage points. What matters is that it is the same for everyone and written down: suppliers will ask for it.
Yes: OneDrive and Google Sheets are Muvia sources too, and from the table onwards the path does not change.