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-07 · Elapsed cycle time by process
Compare approximate median and P90 elapsed hours in finished runs with usable start and end 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.
Runs: Run count in the question's defined population.02-06–02-08, for example, concern finished runs; populations differ between questions.
Median hours: Approximate median elapsed start-to-end hours for finished runs with usable, correctly ordered dates.
P90 hours: Approximate elapsed duration at or below which about 90% of measured runs finished. Complements the median by showing the longer-duration tail.
When checking a discrepancy: Requires start and end in the correct order. Check the measured run count and date coverage in 06-01.
02-08 · Net and elapsed time by process
Compare recorded net-time and elapsed-time medians for finished runs.
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.
Runs: Run count in the question's defined population.02-06–02-08, for example, concern finished runs; populations differ between questions.
Median net hours: Median recorded run net time in hours. NULL is excluded; zero and negative values can currently enter the calculation. Not employee attendance time.
Median elapsed hours: Median elapsed time from run start to end. The difference from net time does not measure a cause of waiting.
When checking a discrepancy: Elapsed dates are validated, but net time need not be positive. NULL net values are omitted; zero or negative values can enter the median. The two medians can use different populations; check 06-05.
02-12 · Waiting time before work starts
Compare approximate median days from release to work start by process.
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 measured: Orders with usable correctly ordered dates included in waiting-time-to-start calculations, even if still open.
Median waiting days: Approximate median days from release to work start. Missing release falls back to creation.
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 release falls back to creation. Unlike 01-11, the source does not require END status; an already-started open order can qualify.
02-14 · Finished runs: time details
Inspect individual finished runs and their recorded net and calculated elapsed hours.
Recommended display: Table
Available filters: Run ID, Process, SKU, Run start, Run end.
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.
Run start: Recorded production-run start timestamp; it may be missing in 02-09.
Run end: Recorded end timestamp for the run, not for the whole work order.
Elapsed hours: Individual-run elapsed hours when start and end exist and end is not before start. Blank when no valid duration can be computed.
Net hours: Recorded net time for an individual run, expressed in hours. Zero or missing values require review of reporting practices.
When checking a discrepancy: All WF.FINISH runs remain visible. Elapsed hours are blank for missing or reversed dates; net hours are shown separately without a positivity test.