Batch Life Cycle |
Content |
||||||||||||||||||||||
|
State | Description | Notes | ||||||||
Initial | Initial status for a Raw Material Batch. | The initial status is specified in the Batch Template. | ||||||||
Received | Indicates that the Batch has been Received at the facility (such as when a Raw Material arrives at the loading dock). | Note that is not the same as "Sample Receipt",
which occurs when the Sample is already in the laboratory.
|
||||||||
Active | Indicates that Samples are Received or being tested in the Lab. |
|
||||||||
Pending Release |
Indicates that all testing is Finished. |
|
||||||||
Preliminary Release |
An optional state to allow certain Samples to be Released prior to completing their required testing. "Preliminary Release" is typically followed by an official release. | Transition to this state is a manual operation using the "Preliminary Release" button in Active and Pending Batch List pages. | ||||||||
Released | Final completion point for a Batch, indicating satisfactory completion of all operations. |
|
||||||||
Rejected | Indicates that the Batch was not Released. | A Batch is Rejected by failing the Approval during the Release process, or by manually setting status to "Rejected" using the "Reject" button on the relevant List page. | ||||||||
OnHold | Indicates that the Batch has been placed On Hold. | A Batch can be manually put On Hold using the "Hold" button on the relevant Batch List page. Sample testing continues even if a Batch is On Hold. |
Automatic Status Transitions |
|
|
"Automatic Status Transitions" describe automatic transition of Batch Status statrting from the "Received" State.
Transition | Occurs when... |
Received → Active | Any sample in the Batch is Received or InProgress. |
Active → PendingRelease | All Samples in the Batch are finished (see Finished Samples below). |
PendingRelease → Active | Any finished Sample is UnReleased or UnReviewed, i.e., InProgress. |
Active → Released | Auto Release is enabled in the Product associated with the Batch. In this case, when all Samples in the Batch are finished, the Batch is released by (system). |
Finished Samples |
|
|
In the context of Samples, the word "Finished" is not a status. "Finished" means "Samples are done", based on whether or not Samples require Review. This is controlled by the s_sample.ReviewRequiredFlag, and is typically specified in the Sample Template.
• | If Sample Review is not required, the Sample is considered "Finished" when Sample status is "Completed" (Completed = Finished). |
• | If Sample Review is required, the Sample is considered "Finished" when Sample status is "Reviewed" (Completed → Reviewed = Finished). |
This is summarized in the table below:
ReviewRequiredFlag | Last Sample status transition | Batch Status | Notes |
No | Goes to Completed | Transitions to Pending Release | |
Yes | Goes to Completed | Stays at Active | Sample is not finished until Reviewed |
Yes | Goes to Reviewed | Transitions to Pending Release |
Batch Disposition Status |
|
|
The "Batch Disposition" indicates whether or not a Batch was successfully tested. Many Skip Lot and Reduced Testing rules (controlled by the Product Variant Rule) are based on the Batch Disposition.
• | During Auto Release, "Batch Disposition Status" is automatically set to "Passed" or "Failed" based on the Approval status of the Batch when it is Released. |
• | During Manual Release, "Batch Disposition Status" is manually set by the user. |
• | "Batch Disposition Status" is used by the Transition Rules associated with the Sampling Plan. |
Batch Auto Release |
|
|
Batches can be automatically Released by specifying this behavior in the Product associated with the Batch.
Batch Auto Release controls when a Batch transitions to "Pending Release". Batch status transitions to "Released" if all Samples have passed their Specifications.
In the Batch SDC, the ReleasedDt and ReleasedBy columns store the "who" and "when" for the "Release" operation. When a Batch is Auto Released, these are set to "now" and "(system)".
This is summarized in the table below:
Auto Release Flag | When Batch transitions to Pending Release | Batch Status |
No | All Sample Specifications Pass | Stays at Pending Release, waiting for Manual Release |
At least one Specification does not Pass | Stays at Pending Release, waiting for Manual Release | |
Yes | All Sample Specifications Pass | Transitions to Released |
At least one Specification does not Pass | Stays at Pending Release, waiting for Manual Release |
Open Incidents |
|
|
The Batch Life Cycle considers any open incidents on the Batch, Stage or Samples under them. Your BatchSamplePolicy defines how the Batch Life Cycle handles open incidents:
Policy Option | Result |
Block | Prevents the Batch from Finishing when there are open incidents for the Batch. |
Warn | Confirm whether or not to proceed with Finishing the Batch when open incidents are found. |
Allow | Batches will continue to Finished whether or not there are open incidents. |
Note: Decisions you make in BatchSamplePolicy determine how the Stage Life Cycle impacts the Batch Life Cycle. Your BatchSamplePolicy decision determines whether or not Stages must be released before a Batch can be released.