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.
06-01 · Date coverage for cycle-time calculations
Check finished runs with usable dates versus missing or reversed dates before interpreting cycle time.
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.
Finished runs: Runs marked finished.06-01 and 06-05 include cases with missing information;02-13 groups finished-run counts by process.
Measurable orders: Finished runs with start and end and end not before start. Count eligible for elapsed-duration calculation.
Dates to review: Finished runs missing start or end, or with end before start. Excluded from valid elapsed-duration calculations.
When checking a discrepancy: A zero-length duration passes this date-order condition. This is coverage, not a check of business plausibility.
06-02 · Due-date coverage in open orders
Compare NEW and IN_PROGRESS orders with and without a recorded due date.
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.
Open orders: NEW and IN_PROGRESS order count. This measure excludes frozen and closed orders;01-02 also includes frozen orders.
With due date: NEW and IN_PROGRESS orders with a non-NULL due timestamp. Does not check plausibility or approval of the plan.
Without due date: NEW and IN_PROGRESS orders missing a due timestamp. Different from overdue orders: lateness cannot be assessed without a deadline.
When checking a discrepancy: Tests existence only, not plausibility. Frozen orders are excluded.
06-03 · Date coverage for on-time completion
Check closed orders with both due and completion dates versus missing information.
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.
Closed orders: Orders classified as closed.06-03 includes missing-date cases; its other columns show coverage.
Measurable orders: Closed orders with due and completion timestamps. Count eligible for the on-time measure.
Missing data: Closed orders missing due or completion date, preventing on-time classification.
When checking a discrepancy: Does not validate start or release dates or business plausibility of the timestamps.
06-04 · Recorded inventory-to-run links
Compare stock records with and without a stored run ID.
Recommended display: Bar chart with value labels
Available filters: Production-run link.
What the columns mean
Production-run link: Whether a run ID is stored on the stock record. Does not validate existence of the linked run or completeness of traceability.
Stock records: Count of stock records, not summed stock quantity. One record can represent a unit, batch or material quantity.
When checking a discrepancy: A non-NULL ID is treated as linked; the source does not join to confirm that the run exists.
06-05 · Positive net-time coverage in finished runs
Compare finished runs with positive net time against missing, zero or negative net time.
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.
Finished runs: Runs marked finished.06-01 and 06-05 include cases with missing information;02-13 groups finished-run counts by process.
With positive net time: Finished runs with stored net time greater than zero. Checks positivity, not reporting accuracy.
Without positive net time: Finished runs with missing, zero or negative net time. Does not prove no work was performed.
When checking a discrepancy: The population is all finished runs, not exactly the elapsed-date-valid population of 02-08. Positive does not certify accuracy.
06-06 · Run-link coverage in time reports
Group time reports by no linked runs, one linked run or multiple linked runs.
Recommended display: Bar chart with value labels
Available filters: Report run assignment.
What the columns mean
Report run assignment: Time reports grouped by zero, one or multiple stored run links. Does not allocate report duration between linked runs.
Reports: Time-report record count.04-03 counts eligible closed reports up to 12 hours;04-04–04-06,04-10 and 06-06 count their defined populations. Compare source conditions first.
When checking a discrepancy: NULL sessionids becomes an empty array. Array cardinality is not necessarily a distinct-run count; links are not validated and hours are not divided between runs.