Reports
Counts, scrap and rates
What Started counts parts in two ways: from the machine's own counter, sent with each ping, or from people logging them by hand. Counting parts needs a plan with machine counts (Pro and Plant). Rates can be set on any plan; they matter once counts arrive.
Counts from the machine
Send the machine's part counter as cycleCount with each ping, and a reject counter as badCount if it has one. See Send pings from a machine.
- Send the counters as they are, as running totals. What Started works out the difference itself.
- A value lower than the one before is read as a reset, such as a shift start or a PLC restart. Counting carries on from the new value; nothing is lost or counted twice.
- Good parts are parts made minus bad parts.
Counts are stored at most once per ping interval of your plan. The board's Cycles figure still updates on every ping.
Log bad parts at the QR sticker
On machines that count their own parts, operators log only the bad ones. The machine already counted them as made.
- Scan the machine's QR sticker.
- Under Bad parts, set the number with the minus and plus buttons.
- Pick a reason under Why bad? (optional), or skip it.
- Tap Log 1 bad part (or however many).
A second tap within 3 seconds is not counted twice. Anyone on your team can also log parts on the machine page under Log bad parts, for example an end-of-shift tally.
The scrap reasons are one list for the plant, under Settings → Reasons, in the Scrap reasons section. On a machine's page, under Scrap reasons, turn off the ones that make no sense on that machine.
Machines counted by hand
A machine with no counter can be counted by people instead. On the machine page under Rates, an owner or admin clicks Count by hand instead. The page then says counts come from people (manual).
The QR sticker and the machine page then ask for Good and Bad parts. Both add to parts made. Click Use the machine counter to switch back.
Ideal and target rates
Set both on the machine page under Rates, in parts per hour. Owners and admins can change them.
- Ideal, parts/h is the fastest the machine can make parts. OEE performance measures speed against it.
- Target, parts/h is what you plan for. It cannot be higher than the ideal.
The board shows the last hour's parts per hour next to the target, in red when a running machine is behind.
Rates per part
Different parts often run at different speeds. A part's rates replace the machine's while that part runs, one field at a time: leave a field empty and the machine's rate applies.
Parts create themselves. When a ping carries a partNumber, What Started adds the part and lists it on the machine page under Parts on this machine. You only fill in the rates and click Save.
To set rates before a part has run, enter its Part number, Ideal/h and Target/h and click Add. Parts are never deleted.
What you see
The machine page shows, under Production:
- Running part: the part number from the last ping.
- Last hour: parts per hour, with the target.
- Made, 24 h and Bad, 24 h, with bad as a share of made.
How counts feed OEE
- Performance is the ideal time for the parts made, each at its part's ideal rate or else the machine's, over run time. Without an ideal rate it shows as a dash.
- Quality is good parts over parts made. Bad parts come from the reject counter and from bad parts people log.
From other systems
Counts are in GET /api/v1/metrics, parts and their rates in GET /api/v1/parts, and parts people logged in GET /api/v1/part-counts of the read API. Each logged entry also sends a parts.logged webhook.