Multiple Mixing batches

This process will gather all sample data from the parent batches associated with the child batch, average it, then enter it into the system.  It will also release the data entered.  Calculations and params used for those calculations will also be removed.

Adding parent batches to the child batch

To associate the new batch to the mixing batches, they must be added as parent batches.  This is done inside the batch edit screen that can be opened either by clicking the batch id (red arrow) or ticking the check box and clicking the edit button while on the Active Batch List.

After navigating to the edit batch page, you’ll see a Parent Batch section at the bottom with Add and Remove buttons.

Click the Add button to find the parent batches to associate to this batch.  There are a few different ways to lookup the parent batches.   It can be done by any of the batch lookups (by Kemin Lot #, Product, Released, Business Unit, etc) or by scanning barcodes of the Kemin Lot Numbers to be added.  If there are no barcodes, the lot numbers can also be hand entered.   After entering the lot number (green arrow), you can press enter or click add (barcode scanning with carriage return will automatically enter the value after scanning), then click the search button (blue arrow).  The list will be populated and you can tick the checkboxes of the batches you want to associate.  After selecting the batches, click the Select & Return button at the top.

You’ll be returned to the Edit Batch page with the parent batches added.  Save it then return to the batch list.

Bringing in the averaged data from the parent batches

If you checked the data on the new batch now, it would be empty.

To import the data from the other batches, you would select the new child batch on the Active Batch List page and then click the Genealogy > Multiple Mixings button.   After clicking the button, you should see the Operation Successful message.  If you went in to check the data, you would find the average of all the parent batch results and the results would be locked/released.  You would also find that all the calculations were removed as well as any parameter that either doesn’t have a spec or doesn’t get printed on the COA.

After the import is complete

After importing the averaged data from the parent batches/samples, the non-reportable parameters will be removed.  Any tests and datasets that did not have results copied into the child sample will be removed.  The tests and datasets still connected to the sample will be updated to released status and the sample will be pending review.

After these steps are completed, the sample will need to go through the approval and review process before the batch can be approved and released.

Potential Issues

• The Multiple Mixing step can only be done once on the batch.  It is triggered from an event when the batch mode status is changed to MultipleMixing.  Clicking the button more than once will not perform the action again.
• Parameters typically used for calculations are missing.
  1. This is by design.  The way the averaging works would cause rounding errors due to averaging all the results needed for calculations and then calculating based off those averaged results (example: sample weights).  The results that are copied into the fields that are typically calculated are the average of all the parent results in that field, which would calculate differently if doing the calculation with the results showing for the sample.
• Error message saying it “Failed to evaluate event ‘Sample Data Averaging’ in event plan ‘Kemin_MultipleMixing’
  1. This usually means there are no parent batches attached to this batch.  Double check that the parent batches were assigned during the Adding parent batches to the child batch process.
• Error message saying “Parent batches have to be released before proceeding...”
  1. The parent batches need to be released.  If they aren’t the child batch cannot be released.
• Versions of test methods or paramlists do not match what the new batch expects
  • This will cause and error that prevents the calculations to work.  There is currently no way around this and it will be very common.  This would make it so the results will need to be averaged outside the system and manually entered, the same way it has been done historically.

Changes made to the system