New Features

1. QC - Previous Jobs, QC History and Testing table indicators

‍

1. QC - Previous Jobs, QC History and Testing Table Indicators

The Quality Control process in Alchemy is enriched with several key features:

• Previous Jobs

QC technicians assigned to a new QC production job can see important information related to previous QC jobs for the tested material. Reviewing previous QC jobs can be essential, especially in the following cases:

• Examining past QC jobs ensures consistency in testing procedures and methodologies. It is crucial for maintaining reliable and comparable results over time.
•  Previous QC data serve as benchmarks for evaluating the current performance. Comparing current results to historical data helps identify trends, deviations, or unexpected changes that may require attention.
• If issues arise in current QC testing, referencing past jobs can aid in troubleshooting. Understanding how challenges were addressed in the past can provide insights into potential solutions.
• QC jobs often involve specific analytical methods. Reviewing previous jobs helps ensure that these methods have been appropriately validated and verified, contributing to the overall reliability of the testing process.

‍

• QC History

QC technicians assigned to a QC production job can see the status change history of a QC process. Tracking the status of the QC process is essential for several reasons:

• Real-time monitoring of ongoing testing activities enables laboratory managers and personnel to stay informed about the progress of analyses and respond promptly to any issues or delays.
• By knowing the status of each QC test, laboratories can optimize workflow management, including scheduling, resource allocation, and ensuring that analyses proceed in a logical and timely sequence.
• Tracking QC statuses helps identify bottlenecks or areas where the workflow may be slowed down. 
• Monitoring the QC process ensures that all steps follow established protocols and standards.

‍

• Testing table indicators

QC technicians assigned can quickly identify measured values which stop the process if they fall out of range, with the possibility to take appropriate next steps.
If the values are within required range, they can identify and choose which of the eligible values will be included in the certificate of analysis. 

‍Other Improvements

• DOE generated trials will now have values pre-filled for actuals (samples) with the values from theoreticals (materials)
• Architecture improvements on the Workspace testing tables
• Flexibility to create conditions and properties in the UAT system, enabling you to test and verify their functionality before deploying them to production. While this option doesn't prevent you from creating them directly in production, it aligns with your company's best practices, offering you the choice of where to implement them.
• Mathematical calculations will now be able to use decimal numbers as the exponent
• Resolved an issue with adding multiple property rows with descending condition values in a range
• Resolved an issue on apply property action while another property is being applied
• Resolved an issue with missing names on conditions popup on Study Overview when property name is changed
• Resolved an issue when creating a Sample from a standalone Material if the Material has properties with conditions
• Resolved an issue with using a standalone Material as a starting formulation in a Workspace
• Resolved an issue with using a Material with no ingredients as a starting formulating in a Workspace
• Resolved an issue with opening multiple measurements drawer on a Phase
• Resolved an issue with missing material constraints table on the Screening Design page
• Resolved the issue where Scan and Score would report wrong number of matching formulations
• Resolved an issue where conditions of test methods were not editable in certain cases