Performance shows 140% on one line since we changed products

[HMIDesign]

On our filling line the Performance gauge has been showing values between 130% and 145% for the last three days. Before that it was around 85%, which matched what we expected. The only thing that changed is that we started running a new bottle size, and someone created a new product for it.
The counter itself looks fine, the quantity on the dashboard matches the paper count at the end of the shift. So I assume the problem is on the "expected" side of the calculation, but I don't know where that value comes from in the web version. Where should I look, and how do I fix the past days?

[Technical Support]

Your assumption is right. Performance compares the actual quantity with the ideal quantity the machine should have produced in its running time. If the actual count is correct and Performance is far above 100%, the ideal rate for the running product is too low.
Please check the following:

1. Ideal Production Quantity of the new product. Open DEVELOPMENT > PRODUCT and find the new bottle size. The field is Ideal Production Quantity (pieces/min), so it is a rate per minute. A very common mistake is entering a per-hour or per-shift value, or a rate taken from a slower product. Correct the value and save.
2. The product on the work order. Performance uses the product of the work order that is running on the machine. Open WORK ORDERS and confirm that the running order really refers to the new product and not to an older, slower one.
3. Compare on the dashboard. Under the Performance gauge you see Ideal Quantity and Actual Quantity. After the fix, the ideal quantity should be in the same range as what the line can realistically produce.

About the past days: the correction is meant to fix the calculation going forward. If the reports for the last three days must be corrected as well, note the affected dates and contact us with the exact time range, so we can review those records with you.
Tip: for products that share a line, use the nominal speed from the machine builder's specification, not an observed best-case value.
Documentation: https://greensoft.ai/documentation/p...ser-interface/