Excel: Production by Workcenter
Twelve months of good production rolled up to workcenter and part
Overview
Twelve months of good production rolled up to workcenter and part
Twelve months of good production, summed by workcenter and part: workcenter code, name and type, the part, produced quantity and net weight, the number of production events, and the first and last report dates in the window.
Rejection records are excluded — they are not output. Scrap has its own table.
Take the .xlsx link rather than .csv. Part numbers that start with a zero are common, and CSV carries no type information, so Excel would quietly turn 00124735 into 124735. The xlsx feed keeps it as text.
How to connect it
Open the script, click Connect to Excel and copy the link. In Excel, Data → From Web, paste, choose Anonymous, and Load. From then on Refresh All re-runs the query — there is no exported file to hunt down, nothing is scheduled and nothing is emailed around.
How current is it?
This table reads Plex over its ODBC reporting connection, not the live transactional system. That copy can trail production by up to about four hours, so treat the numbers as recent rather than real-time. Refreshing re-runs the query, but it re-runs it against the same reporting copy — it does not reach past it.
That is the right trade for reporting, review meetings and models. Anything that has to be accurate to the minute — shipping a container, releasing a job — belongs in Plex itself, not in a workbook.
Filters
Every input is an optional URL query parameter on the link, so one script serves a whole team: two sheets can be the same feed with different values. For example ?workcenter=VALUE&part_no=VALUE.
| Input | What it does |
|---|---|
workcenter | substring match on Workcenter or Workcenter Code |
part_no | substring match on Part No or Part Name |
min_qty | keep only rows producing at least this quantity |
max_rows | keep only the first N rows |
What this installs
The Excel Data - Production by Workcenter script and one saved SQL query it runs on. The SQL lives in the SQL editor, so a column you want added is an edit in one place that every workbook picks up on its next refresh. The table has 11 columns as shipped, and no row cap — a cap would truncate silently and the workbook would look complete.
What you need
One ODBC credential pointed at your Plex reporting connection. The install wizard asks for it once and applies it to the query. If you do not have one yet, create it first in Script Engine → Credentials with type odbc.
What's Included
Use Cases
- Compare output against scrap by workcenter over a rolling year
- Find the parts a machine actually runs most
- Build a utilisation model in Power BI that reloads on schedule
- Check production history before quoting a new volume
Benefits
- Re-queries the source on refresh instead of holding an emailed copy
- Rolled up in SQL, so the workbook loads a summary not a million rows
- Rejections excluded, so the number is real output
- Pairs directly with the scrap table on workcenter
Configuration Steps
After installation, you'll configure:
- Plex ODBC connection