Skip to content

Every Production Outcome Has a Story in the Data.

Understanding yield performance requires connecting what entered production, what happened during processing, what came out, and which conditions shaped the result.

This page follows one example production run, AP-2417: 24,000 kg of apples processed into puree on Line 2. The method is what we want you to examine.

  1. 1

    Connect Production Records

    The run begins as six records in five places. A weighbridge ticket states 24.0 t net. The ERP goods receipt, posted by a supplier-facing team, states 52,911 lb under receipt GR 88/A. The batch sheet refers to Lot 0088, and the laboratory export calls it LOT-88. The filler count sits in a spreadsheet. A pomace inventory adjustment appears later with no reference to the run at all.

    Connection means establishing that these are the same event. Identifiers are resolved against site-specific rules, units are converted, and timestamps are aligned. The tank transfer log and line schedule then allow each movement to be attributed to the run. Every link is recorded along with the basis for making it, and links made on weaker evidence, such as a time window, are marked so they can be questioned. Originals are preserved unchanged.

  2. 2

    Establish Material Accountability

    24,000 kg went in and 15,480 kg of finished puree came out. Read naively, that suggests 8,520 kg of waste. It is the most common misreading in food manufacturing, because not every decrease in finished-product weight represents waste.

    The balance classifies mass by what actually happened to it. Select each class below to see its definition and the evidence behind it.

    Where 24,000 kg went: run AP-2417Example data

    3,600 kg

    Not waste. It is the process working as intended.

    Water removed on purpose to reach the solids target. The evaporator takes in 20,160 kg at 13.0 °Bx and delivers 16,560 kg at 15.8 °Bx. Soluble solids stay constant while mass falls, which is why finished weight alone would misrepresent this stage.

    Evidence: Calculated from a solids balance using lab Brix readings. Marked as calculated, not measured.

    The stream table underneath is the same balance, stage by stage. Marking each stream as measured or calculated matters as much as the mass. Evaporated water in this run is calculated from Brix readings, so an error in a lab reading would move it, and with it the unresolved figure. An engineer reading this table can see where that dependency sits.

    Stream table, run AP-24178 h, Line 2 · Example data
    Mass by process stream for example run AP-2417
    StreamDescriptionMass% inputBasis
    S1Apples received, net24,000 kg100.0%Measured
    S2Sorting rejects720 kg3.0%Measured
    S3Sorted fruit to extraction23,280 kg97.0%Calculated
    S4Pomace, sold3,120 kg13.0%Measured
    S5Feed to evaporator20,160 kg84.0%Calculated
    S6Evaporated water3,600 kg15.0%Calculated
    S7Concentrate to filling16,560 kg69.0%Calculated
    S8QA-rejected drums360 kg1.5%Measured
    S9Line-clearance solids240 kg1.0%Measured
    S10Finished puree, released15,480 kg64.5%Measured
    S11Unresolved discrepancy480 kg2.0%Balance closure

    S1 = S2 + S4 + S6 + S8 + S9 + S10 + S11. Closed streams are counted once. Intermediates S3, S5 and S7 are carried for the stage balance.

  3. 3

    Model Expected Performance

    With a reconciled history available, a yield figure can be compared with something more meaningful than an annual standard. For AP-2417, a model trained on this line’s past runs estimates 66.2%, with a range of 65.1% to 67.3%. It uses information known about the lot and the run, including solids, firmness, variety and product specification.

    Actual yield was 64.5%. That is 144 kg below the bottom of the range and 408 kg below its centre. Most runs on the chart fall inside their ranges, even where their yields differ noticeably, and those differences do not call for investigation. This is the distinction between normal process variation and a deviation worth examining.

    Expected versus actual yield, comparable runsApple puree, Line 2 · Example data
    • Expected range
    • Actual yield
    • Outside expected range
    64%65%66%67%68%AP-2417: 64.5%AP-2402AP-2408AP-2414AP-2417
    View chart data as a table
    Expected and actual yield for twelve example runs
    RunExpectedRangeActual
    AP-239866.0%64.9 to 67.166.4%
    AP-240065.6%64.5 to 66.765.1%
    AP-240266.4%65.3 to 67.566.9%
    AP-240466.7%65.6 to 67.866.2%
    AP-240665.8%64.7 to 66.966.3%
    AP-240866.1%65.0 to 67.265.5%
    AP-241066.9%65.8 to 68.067.4%
    AP-241266.3%65.2 to 67.465.9%
    AP-241465.5%64.4 to 66.665.8%
    AP-241566.5%65.4 to 67.666.0%
    AP-241666.0%64.9 to 67.166.5%
    AP-241766.2%65.1 to 67.364.5%
  4. 4

    Investigate Deviations

    A flag prompts a question, and it arrives with material to answer that question faster: the factors most strongly associated with the difference, the runs most like this one, and the records that are missing. The value of the gap is stated as a range, which helps a reviewer decide how much effort it merits. The full brief for this run appears further down the page.

    Investigation is where the plant’s own knowledge takes over. The people who know the line check the finisher, ask about the fruit, and look in the tank. Their conclusions become part of the record.

  5. 5

    Evaluate Operational Improvements

    Suppose engineers act on the finisher finding and adjust maintenance. Did it work? Comparing average yield before and after can mislead, since better fruit arriving the following month would look like a process improvement. Comparing each run with its own expected yield removes much of that effect, because the model already accounts for the raw material.

    The result is reported with its uncertainty, and quality outcomes are reviewed alongside it. An improvement that moved product toward a specification limit is a different result from one that did not.

    Evaluating a finisher maintenance changeTen runs either side · Example data
    -1.0-0.50.0+0.5BeforeBefore, run 1: -0.6 ptsBefore, run 2: -0.2 ptsBefore, run 3: -0.9 ptsBefore, run 4: -0.3 ptsBefore, run 5: -0.7 ptsBefore, run 6: -0.1 ptsBefore, run 7: -0.7 ptsBefore, run 8: -0.4 ptsBefore, run 9: -0.8 ptsBefore, run 10: -0.3 pts-0.50AfterAfter, run 1: +0.1 ptsAfter, run 2: -0.2 ptsAfter, run 3: +0.3 ptsAfter, run 4: -0.1 ptsAfter, run 5: +0.2 ptsAfter, run 6: -0.4 ptsAfter, run 7: 0.0 ptsAfter, run 8: +0.3 ptsAfter, run 9: -0.2 ptsAfter, run 10: +0.1 pts+0.01

    Actual minus expected yield, points. Line marks the mean.

    Difference in means +0.51 points, 95% interval +0.27 to +0.75. Because each run is compared with its own expected yield, a run of better fruit is not credited to the change. Ten runs still leave uncertainty, and the comparison is observational.

Intelligence Should Be Explainable.

A plant manager will not change a line because a model said so, and should not. For analytical findings to earn a place in production decisions, the people accountable for those decisions need to be able to see how they were reached.

Data provenance
Any figure can be followed to the records it came from: which ticket, which export, when it arrived, and whether it was measured, calculated or inferred. When a number is challenged in a production meeting, the answer should be available in the same meeting.
Model confidence
An estimate carries an indication of how much it should be trusted. Thin history, unfamiliar raw material and missing inputs widen the expected range and lower the stated confidence, so a weak estimate is visibly weak.
Historical comparisons
Reviewers can see the actual past runs behind a comparison, including how they were alike and how they differed. An engineer who knows that a line was rebuilt last spring can exclude the runs before it.
Operational validation
Model output is checked against what people on the floor observed, and the result is kept. A finding that an experienced operator can explain in a sentence is still useful, because it teaches the system what context it was missing.

How we approach responsible AI

From Analysis to Actionable Investigation.

How the platform is designed to present AP-2417 to a reviewer. It flags the deviation, ranks associated factors, and proposes technical checks in the order most likely to be useful.

A predictive correlation does not prove the cause of a production loss. High pomace and low yield may share a cause, and soft fruit could be behind both. That is why the output is a proposed investigation for a person to carry out.

Investigation brief, run AP-2417Example data

Flag

-1.7 pts

64.5% actual, range 65.1 to 67.3%

Value at stake

$186 to $526

If the gap proves recoverable

Status

Awaiting human review

Assigned to process engineer

Factors associated with the deviation, ranked by strength of association
Associated factorAssociationEvidenceSuggested check
1. Pomace above comparable runs13.0% of input, against a median of 11.8% across 11 comparable runs. A difference of up to 288 kg.StrongPomace bin tickets, comparable-run setInspect finisher screen condition and paddle clearance. Review feed rate during the run.
2. Softer fruit in lot L-88Intake firmness in the lowest quarter of lots this season.ModerateQC intake record, supplier lotReview maturity data with QA. Compare with other runs drawn from the same lot.
3. No closing level for tank T-4Run closed with a transfer to T-4 and no level recorded. Material may be held there.Data gapBatch sheet, tank transfer logCheck opening level on the next run. May resolve part of the 480 kg without any process change.
4. Filler above declared weightCheckweigher average 0.4% over 12 kg, roughly 62 kg across the run if confirmed.WeakCheckweigher logVerify checkweigher against a certified reference weight.

These are statistical associations in historical records. None is established as the cause of this deviation until it has been checked on the plant floor.

Begin with the records you already have.

A processing facility does not need new sensors, a system integration or a change to its plant network to find out whether this analysis is useful. Historical records answer that question at low risk, and they show plainly which data would need to improve before anything more ambitious is worth considering.

  1. 1

    Choose one product family on one line

    A narrow scope makes it practical to understand the records properly and to review results with the people who ran those shifts.

  2. 2

    Gather what already exists

    Batch records, material receipts, quality results, finished-goods and byproduct records, and approximate prices. A season or more of history helps, and spreadsheets are acceptable.

  3. 3

    Assess the data honestly

    Which records can be linked to a run, which weights are measured, where the gaps are. Sometimes this assessment is itself the first useful finding.

  4. 4

    Reconstruct past runs

    Build balances and expected ranges for historical runs, then review them with plant engineers. Do the flagged runs match what people remember? Where they do not, find out why.

  5. 5

    Decide what comes next

    Only then is it worth discussing regular data flows or system interfaces, and only for the records that have proved their value.