Describe your lines, shifts and reason codes, and Netiva’s agent builds a web app for output against target, downtime minutes, scrap and open work orders.
Build a production dashboard for a plant with four lines on two shifts. Store lines with an area, a target rate in units per hour and a shift pattern. Track work orders with a number, part number, line, quantity ordered, due date and status (released, running, on hold, complete). Supervisors sign in and log each shift run at the line: good count, scrap count and scrap reason. They add downtime events with a start time, minutes lost, machine and a reason code from our list. Stamp every entry with the supervisor who logged it. Show a floor view of output against target per line, and rank downtime reasons by minutes lost this week.
By Monday morning the whiteboard from Friday’s second shift is already wiped. Counts get retyped into a spreadsheet, the reason a line stopped for 40 minutes lives in a supervisor’s memory, and nobody can say whether the packing line hit its target three days running. A production dashboard built with Netiva keeps shift counts, downtime events, scrap and open work orders in one place, grouped by line and shift, so the morning meeting starts from the same numbers the floor logged the night before.
Each line shows what it has produced this shift next to the target rate you set, so a supervisor sees at 10 a.m. that packing is 300 units behind instead of finding out at handover.
Every stop is logged against the line and the machine with the minutes lost and a reason from your own code list, so the weekly review argues about causes rather than about the numbers.
Open work orders sit on a board by status and due date with the quantity still to make, so the scheduler can see which order is at risk before the customer calls to ask about it.
Supervisors sign in and enter counts, scrap and stops on the tablet at the line. A scheduled job emails the shift summary to the plant manager and the incoming supervisor when the shift closes.
Netiva keeps your records in built-in collections. Here’s a starting structure — the agent adapts it to your prompt, and you can change it any time.
The lines, cells or work centers you report on, and the rate each one should run at.
What the plant has been asked to make, and where each order stands.
One record per line per shift — or per hour block if you want counts that fine — holding what the supervisor logged.
Every stop on a line, with how long it lasted and why it happened.
Required field. Types are Netiva collection field types.
A typical first version. Ask the agent for more, or annotate the preview to change any of them.
Every line side by side: output against target for the shift in progress, minutes down, scrap and the work order running.
Your teamOne line over recent shifts: counts against target, the stops that cost the most minutes and the orders queued behind the one running.
Your teamStops ranked by minutes lost, filtered by line, shift, machine or reason code, with the longest events shown alongside their notes.
Your teamOpen orders by status and due date, with the quantity still to make and the line running each one.
Your teamThe tablet screen at the line: pick the shift and work order, enter good and scrap counts and add each stop with its minutes and reason.
Signed-in usersOutput, scrap rate and downtime by line and shift for the week, with the reason codes that cost the most time.
Your teamTell Netiva how many lines you run, which shifts cover them and what your reason codes are. The agent drafts collections for lines, work orders, shift runs and downtime events.
Add each line with its area and target rate in the collection grid, then paste in the orders that are open now. The collection assistant can fill missing part numbers or tidy reason codes across rows.
Put one finished shift through the entry screen and look at the floor view. Annotate anything a supervisor would trip over — a missing code, a count in the wrong unit — and the agent changes it.
Publish in one click, give supervisors their sign-ins and put the link on the tablet at each line. Later edits are checkpointed, so a rule you regret takes a rollback, not a rebuild.
| Criterion | With Netiva | Traditional build |
|---|---|---|
| Shift reporting | Counts entered at the line and totaled against target as soon as the shift closes | Whiteboard counts photographed at handover and retyped into a spreadsheet the next morning |
| Downtime analysis | Minutes lost ranked by reason, line and shift on a screen anyone on the floor can open | Reason codes exported from the machine monitoring system once a month, if anyone gets to it |
| Getting started | Describe what you need in chat and watch it take shape in a live preview | Hire developers, or stitch together templates, plugins and a hosting plan |
| Content and data | Built-in collections with nine field types, bound straight to your pages | Set up and connect a separate database or CMS |
| Making changes | Ask the agent; every change is checkpointed and reversible | File a ticket, wait for a sprint, redeploy |
| Hosting and domain | Global hosting and automatic SSL; connect a custom domain from the Starter plan | Buy hosting, then install and renew SSL certificates yourself |
| Code ownership | Clean production code you own and can export | Locked into a template, plugin or agency setup |
Job quantities are small and changeovers are frequent. Supervisors log setup minutes apart from run minutes, so the owner can see which part numbers swallow a whole shift in changeovers before quoting them again.
The packing line sets the pace for the whole site. The floor view shows cases per hour against the target rate, and the night supervisor hands over with every stop already written down and coded.
Work orders carry a promised ship date. The board sorts by due date and marks orders whose remaining quantity cannot be finished at the current rate, so the scheduler can move work between cells early.
Nothing connects to a PLC or a sensor on its own. Counts and stops are entered by supervisors unless your machine monitoring platform or historian exposes an HTTP or REST API that the app can call with a key kept secure.
This dashboard reports on production. It does not plan material, release work orders, post inventory transactions or cost jobs. Keep scheduling where your planners already do it and mirror the order number here.
A short list people actually use beats 60 codes that all get logged as “other”. Write the list with your supervisors before you build, and expect to trim it again after the first month of real data.
An OEE figure is only as good as the planned time, cycle times and quality counts behind it. Without a real good-versus-scrap count, the number you are looking at is closer to machine utilization.
OEE multiplies three ratios: availability, effectiveness — often called performance — and quality. Availability compares the time a line actually ran with the time it was scheduled to run, so every downtime minute you log pulls it down. Effectiveness compares the ideal cycle time for the pieces produced against that run time, and quality is good pieces against total pieces. You tell the agent which shift hours count as planned time, and the tile is worked out from your shift runs and downtime minutes.
Only through something that speaks HTTP. An app built in Netiva can call a REST API and keep the key secure, so if your machine monitoring platform, historian or MTConnect agent answers HTTP requests, ask the agent to poll it hourly for run time, stop times and piece counts. Where a line has no feed, supervisors keep entering counts and both sources sit side by side.
On the entry screen at the line. A supervisor signs in on the tablet, picks the shift and the work order, enters good and scrap counts, then adds each stop with its start time, minutes lost, machine and reason code. Every entry is stamped with who logged it. Most plants record a stop as it clears, which keeps the note useful at the morning meeting.
It depends on the process, so treat published figures with care. In discrete manufacturing 85% is a widely quoted goal, and a NIST case study at an aerospace plant notes that readings above it can point to a bottleneck rather than to a better line. The comparison worth watching is your own line against last month, which is what the weekly review screen shows.
Yes. Each shift run carries its line, its shift and its work order, and the work order carries the part number, so filtered and sorted views can cut output any of those ways and be saved for the people who open them daily. A continuous improvement lead usually keeps one view per line, while the plant manager keeps one per shift.
Yes. The code Netiva generates is clean and framework-standard, yours to read in the editor and export at any time, with no proprietary runtime underneath. Plants keep reporting tools for years, so that matters: if your IT group takes the dashboard over later, they inherit readable source, and every edit made before the handover is checkpointed.
Drafted with AI assistance from Netiva’s product pages and reviewed by the Netiva team. Example data models, screens and prompts are illustrative starting points, not customer projects.
Describe it in a sentence and watch Netiva’s agent build it. Free to start — no credit card required.