Question numbers match their folders: folder 01 contains 01-01, 01-02 and so on. The starter dashboard uses 01-05, 01-08 and 01-02; process filter values come from 01-20. OBP identities and SQL filenames remain stable.
Choose a question for the decision you need to make. Find the equivalent saved question by its number in your supplied collection. If it has not been prepared, ask your administrator to create it from the linked English SQL definition before adding it to a dashboard. Filters act on existing output columns and do not override the source conditions.
The headings below match the English SQL variants in this guide. Use the stable question number to find its equivalent in your supplied collection; names can vary by language and environment.
01-08 · Overdue orders: details
Find NEW and IN_PROGRESS orders whose recorded due timestamp is already past.
Recommended display: Table
Available filters: Order, SKU, Process, Due date, Days overdue, Progress.
What the columns mean
Order: The same kind of identifier as the work-order-number column; different questions use different localized headings.
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
Due date: The planned order-completion timestamp in the due-date field. Not measured shipment or actual completion.
Days overdue: Whole-day difference between a passed due date and query execution. Applies to NEW and IN_PROGRESS orders with a past due timestamp.
Progress: The stored numeric order/run progress value: order in 01-02 and 01-08, run in 02-09. Shown without converting its scale to percentages.
When checking a discrepancy: Excludes frozen orders and missing due dates. An order can be overdue even when the whole-day difference is zero.
01-09 · Open orders without a due date
Find NEW and IN_PROGRESS orders missing expecteddate so planning can be reviewed.
Recommended display: Table
Available filters: Order, SKU, Process, Created date, Status.
What the columns mean
Order: The same kind of identifier as the work-order-number column; different questions use different localized headings.
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
Created date: Record creation: work order in 01-09, run in 02-04 and stock record in 03-04. This is not the work-start timestamp.
Status: Current work-order status name. Status meanings and permissions to change them depend on the organization's process.
When checking a discrepancy: Checks NULL only. An implausible or old date is still a populated date.
01-10 · On-time completion by month
Compare closed orders with both due and completion dates, showing measurable orders and the on-time percentage.
Recommended display: Table
Available filters: Completion month; numeric output columns are also available for filtering.
What the columns mean
Completion month: The month used to summarize completed work orders.
Orders with dates: Closed orders with both due and completion timestamps. The denominator of 01-10's on-time percentage.
Completed on time: Measurable closed orders finished by their due timestamp, including an exact match. The numerator of the on-time percentage.
On-time percentage: On-time orders divided by orders with due and completion dates, multiplied by 100. Weight by order counts when combining months; a simple average of monthly percentages can mislead.
When checking a discrepancy: Compares full timestamps. Ending exactly at the deadline is on time. Missing dates are excluded from the denominator; check 06-03.
01-11 · Work-order lead time by process
Compare approximate median days from release to completion for closed orders with usable dates.
Recommended display: Table
Available filters: Process.
What the columns mean
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
Orders: Order count within the question's month, source, SKU or other group.01-11 includes only closed orders with usable, correctly ordered dates.
Median days: Approximate median days from order release to completion. Creation substitutes for missing release, with fallback cases counted separately.
Calculated from creation: Count of observations using creation instead of missing release: lead time in 01-11 and waiting time in 02-12. This is a count, not a duration.
When checking a discrepancy: Missing releasedat falls back to createdat. Whole hours are divided by 24; check how many observations used the fallback.
01-16 · Closed orders: date details
Inspect individual END orders, their dates and on-time, late or missing-information classification.
Recommended display: Table
Available filters: Order, SKU, Process, Due date, Order completion date, On-time classification.
What the columns mean
Order: The same kind of identifier as the work-order-number column; different questions use different localized headings.
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
Due date: The planned order-completion timestamp in the due-date field. Not measured shipment or actual completion.
Order completion date: Actual completion timestamp recorded on a closed work order, not the end of one particular run.
On-time classification: Comparison of order completion with the due date: on time, late or missing information. Not proof of delivery or shipment.
When checking a discrepancy: Orders lacking due or completion dates stay visible as missing information. Exclude that group when comparing with 01-10.
01-17 · Work orders by due month
Compare orders by due month and current status.
Recommended display: Table
Available filters: Due month, Status.
What the columns mean
Due month: The month containing the order's due timestamp. Question 01-17 excludes orders without a due date.
Status: Current work-order status name. Status meanings and permissions to change them depend on the organization's process.
Orders: Order count within the question's month, source, SKU or other group.01-11 includes only closed orders with usable, correctly ordered dates.
When checking a discrepancy: This is current status grouped by due month, not status as it was in that month. Missing due dates are excluded.
01-18 · Orders due in the next seven days
Find NEW and IN_PROGRESS orders due from execution time through the next seven 24-hour periods.
Recommended display: Table
Available filters: Order, SKU, Process, Status, Due date, Order work start, Planned quantity.
What the columns mean
Order: The same kind of identifier as the work-order-number column; different questions use different localized headings.
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
Status: Current work-order status name. Status meanings and permissions to change them depend on the organization's process.
Due date: The planned order-completion timestamp in the due-date field. Not measured shipment or actual completion.
Order work start: Recorded order work-start timestamp. May be blank even when a due date exists; not order creation.
Planned quantity: Planned quantity stored on the order.01-02 shows individual orders;01-13 sums by SKU. Do not add unlike units of measure.
When checking a discrepancy: A rolling window, not a shift plan. Excludes already overdue and frozen orders. A result date filter can narrow this window but cannot expand it.