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.
02-01 · Production runs by status
See runs grouped as waiting, in progress or finished.
Recommended display: Bar chart with value labels
Available filters: Run status.
What the columns mean
Run status: Run classification as waiting, in progress or finished. A single order can contain runs with different statuses.
Runs: Run count in the question's defined population.02-06–02-08, for example, concern finished runs; populations differ between questions.
When checking a discrepancy: Any status other than WF.NEW or WF.FINISH, including NULL, is classified as in progress. Questions 02-02,02-03,02-09 and 02-11 exclude NULL through NOT IN.
02-02 · Work in progress by process
Compare run counts whose status is neither WF.NEW nor WF.FINISH.
Recommended display: Bar chart with value labels
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.
Runs in progress: Run count with status other than waiting or finished. Not a unit count or employee-attendance measure.
When checking a discrepancy: NOT IN also excludes missing statuses. This does not prove that work is happening at this instant.
02-03 · Work in progress by next step
Locate grouped runs by process name, next reported step and next chapter.
Recommended display: Table
Available filters: Process, Reported next step, Next chapter.
What the columns mean
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
Reported next step: Next action reported on the grouped runs. Question 02-03 groups process, next step and next chapter together.
Next chapter: The next chapter recorded on the run. A chapter groups workflow steps; it is distinct from the chapter on a time report.
Runs: Run count in the question's defined population.02-06–02-08, for example, concern finished runs; populations differ between questions.
When checking a discrepancy: The grain is process × next step × next chapter. Identical names can merge groups; no station-entry timestamp is measured.
02-04 · Runs waiting to start
Find individual WF.NEW runs, ordered with the oldest created records first.
Recommended display: Table
Available filters: Run ID, Process, SKU, Created date, Stock quantity.
What the columns mean
Run ID: The internal production-run/session identifier, not the work-order number. Displayed as a value rather than a built-in report link.
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
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.
Stock quantity: Quantity recorded on the production run. Units depend on the item; one run can cover multiple units or material quantity.
When checking a discrepancy: Quantity is not a run count. Use the run identifier to inspect an individual case.
02-05 · Runs completed by week
Count finished runs with an end date, grouped by completion week.
Recommended display: Line chart over time
Available filters: Completion week.
What the columns mean
Completion week: The whole week summarized for completed production runs. A filter selects the timestamp representing that week.
Runs completed: Finished runs with an end timestamp in the weekly summary. Count of runs, not sum of output quantity.
When checking a discrepancy: Trino weeks start on Monday. A result filter selects the week-start timestamp, not individual days within that week.
02-06 · Recorded quantities in finished runs by SKU
Compare finished run counts and their recorded quantities by SKU.
Recommended display: Table
Available filters: SKU.
What the columns mean
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
Runs: Run count in the question's defined population.02-06–02-08, for example, concern finished runs; populations differ between questions.
Recorded quantity: Sum of recorded quantities in finished runs of the SKU. Quantity is different from run count and is not necessarily good quantity.
When checking a discrepancy: A missing quantity does not add to SUM but its run still counts. These quantities are not independently verified good output.
02-09 · Progress of open runs
Inspect individual runs classified as in progress, their next step and recorded progress.
Recommended display: Table
Available filters: Run ID, Process, SKU, Progress, Next step, Run start.
What the columns mean
Run ID: The internal production-run/session identifier, not the work-order number. Displayed as a value rather than a built-in report link.
Process: The workflow name associated with the result row. Filtering a name does not select a particular workflow version.
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
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.
Next step: Next reported run action. A process position, not a measurement of physical location or waiting duration.
Run start: Recorded production-run start timestamp; it may be missing in 02-09.
When checking a discrepancy: Progress is shown as stored, without converting its scale to percentages. A start timestamp is not required.
02-10 · Runs created by month
Count runs created in each month across all current statuses.
Recommended display: Line chart over time
Available filters: Creation month.
What the columns mean
Creation month: Creation month of runs in 02-10 or stock records in 03-05. These questions count different record types.
Runs created: Runs created in the displayed month, across all current statuses.
When checking a discrepancy: Creation does not mean a run started or finished. Current status does not reconstruct historical status.
02-11 · Runs in progress by SKU
Compare in-progress run counts by partsku.
Recommended display: Bar chart with value labels
Available filters: SKU.
What the columns mean
SKU: The part identifier recorded on the order, run or stock record, according to the question. It is not an individual-unit identifier.
Runs in progress: Run count with status other than waiting or finished. Not a unit count or employee-attendance measure.
When checking a discrepancy: Counts runs, not SUM(quantity). Use 02-09 to inspect a specific run.
02-13 · Finished runs by process
Count all runs marked WF.FINISH by process.
Recommended display: Bar chart with value labels
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.
When checking a discrepancy: Includes missing end dates. Totals can exceed 02-05 or 02-07, which require suitable completion dates.