PlantOps BI

On-Time Delivery (OTD)

Formula
Orders delivered on or before the promised date divided by orders due
Typical range
95%+ is a common target for finished goods; under 90% usually points to scheduling, not logistics
Direction
Higher is better

Open the Calculator Generate the DAX

On-time delivery (OTD) measures the percentage of orders that reach the customer on or before the date you promised, not the date you shipped. It is the metric the customer actually feels, which is why it shows up on a supplier scorecard whether you track it internally or not.

What Good Looks Like

Most finished-goods operations target 95% or higher, with anything below 90% treated as a signal that the problem sits upstream of the shipping dock: bad promise dates, thin capacity, or a schedule that was never realistic to begin with. Chronic misses below 85% are rarely a logistics problem; they are a planning problem wearing a logistics costume.

Watch for OTD measured against ship date instead of delivery date. A plant can hit 98% “on time” by its own definition while the customer’s receiving dock sees late trucks all month, because transit time never entered the calculation. The other common trick is quietly pushing the promise date once a miss looks likely, which flatters the metric while the customer relationship erodes.

On-Time Delivery in Power BI (DAX)

With an order fact carrying promise_date and actual_delivery_date, one row per order or one row per order line, and dim_date related on promise_date:

Orders Due =
COUNTROWS (
    FILTER (
        VALUES ( fact_orders[order_id] ),
        CALCULATE ( COUNTROWS ( FILTER ( fact_orders, NOT ISBLANK ( fact_orders[promise_date] ) && fact_orders[promise_date] < TODAY () ) ) ) > 0
    )
)

On-Time Orders =
COUNTROWS (
    FILTER (
        VALUES ( fact_orders[order_id] ),
        VAR DueLines =
            CALCULATE ( COUNTROWS ( FILTER ( fact_orders, NOT ISBLANK ( fact_orders[promise_date] ) && fact_orders[promise_date] < TODAY () ) ) )
        VAR GoodLines =
            CALCULATE (
                COUNTROWS (
                    FILTER (
                        fact_orders,
                        NOT ISBLANK ( fact_orders[promise_date] ) && fact_orders[promise_date] < TODAY ()
                            && NOT ISBLANK ( fact_orders[actual_delivery_date] )
                            && fact_orders[actual_delivery_date] <= fact_orders[promise_date]
                    )
                )
            )
        RETURN
            DueLines > 0 && GoodLines = DueLines
    )
)

OTD % = DIVIDE ( [On-Time Orders], [Orders Due] )

OTD % (Rolling 4wk) =
CALCULATE (
    [OTD %],
    DATESINPERIOD ( dim_date[date], MIN ( MAX ( dim_date[date] ), TODAY () ), -28, DAY )
)

This is order grain. An order is on time only if every line whose promise date has passed was delivered on or before it. The NOT ISBLANK matters: DAX treats a blank date as earlier than any real date, so without it an order that hasn’t arrived passes the test.

A line counts once its promise date is before today. An open line past its promise date is a miss, an open line promised for today or later stays out, and so does a later line on an order that is otherwise due. Dividing by shipped orders only would hide the first kind.

The rolling window stops at today. Without that, a date table that runs into the future would put the window over days with no orders and the measure would come back blank.

Keep promise_date as the original commitment, captured once at order entry and never overwritten. If the schedule changes, log a revision, do not update the field in place, or the metric loses its meaning.

Common Mistakes

  1. Using ship date instead of delivery date. Ship date measures the plant’s performance, not the customer’s experience, and the two diverge as soon as a carrier has a bad week.
  2. Redefining “on time” with a hidden window. A plant that quietly counts anything within two days of promise as on time is measuring a different, easier metric without telling anyone.
  3. Excluding cancelled or expedited orders from the denominator. Both are real events that affected a real customer; dropping them from the count flatters the number without fixing anything.

Table and column names in the DAX above are examples. Use the DAX generator below to fill in your own.

On-Time Delivery Calculator

Runs in your browser

Nothing you type is sent anywhere. Your inputs only go into a URL if you click Copy Share Link, and anyone with that link can read them.

Result

DAX Generator

Use My Own Table and Column NamesUpdates as You Type

Type your own table and column names. The measures update as you type. Leave a field blank to keep the example name.

Tables
Columns
Your measures
Orders Due =
COUNTROWS (
    FILTER (
        VALUES ( fact_orders[order_id] ),
        CALCULATE ( COUNTROWS ( FILTER ( fact_orders, NOT ISBLANK ( fact_orders[promise_date] ) && fact_orders[promise_date] < TODAY () ) ) ) > 0
    )
)

On-Time Orders =
COUNTROWS (
    FILTER (
        VALUES ( fact_orders[order_id] ),
        VAR DueLines =
            CALCULATE ( COUNTROWS ( FILTER ( fact_orders, NOT ISBLANK ( fact_orders[promise_date] ) && fact_orders[promise_date] < TODAY () ) ) )
        VAR GoodLines =
            CALCULATE (
                COUNTROWS (
                    FILTER (
                        fact_orders,
                        NOT ISBLANK ( fact_orders[promise_date] ) && fact_orders[promise_date] < TODAY ()
                            && NOT ISBLANK ( fact_orders[actual_delivery_date] )
                            && fact_orders[actual_delivery_date] <= fact_orders[promise_date]
                    )
                )
            )
        RETURN
            DueLines > 0 && GoodLines = DueLines
    )
)

OTD % = DIVIDE ( [On-Time Orders], [Orders Due] )

OTD % (Rolling 4wk) =
CALCULATE (
    [OTD %],
    DATESINPERIOD ( dim_date[date], MIN ( MAX ( dim_date[date] ), TODAY () ), -28, DAY )
)