Values in the lab folder
The readings exist, but in a file nobody outside the lab opens.
Industries Lab and quality
Readings belong to the transaction they describe.
A lab value helps little if it sits in its own spreadsheet and is laid next to production data days later. I build capture and reporting so that test values hang directly on the batch, shift or delivery.
Typical situations
When a conversation makes sense.
Deviation seen too late
Only the monthly report shows that a value drifted. The affected goods have long been shipped.
No link to the batch
Which sample belongs to which batch or delivery is only written on the sample label.
Building blocks
What I build for it
Capture on the transaction
Test values are posted to the batch, shift or delivery they belong to.
History and reports
Values over time, with print and PDF for reports and audits.
Device integration
Readings can come from devices or control systems via a REST API.
What already runs
Built for the glass industry: W-Make Batch.
Features from W-Make Batch. Demo access is available on request.
See details →- Lab values as part of the production flow
- Energy and emission values
- Reports, print and PDF
- REST API for machine data
State of references
Lab values are captured in W-Make Batch for glass production. It is not a standalone LIMS. There is no public reference for pure lab software yet.
Other industries
First call · 30 minutes · free
Tell me where your process gets stuck.
Describe in a few sentences where things get stuck today. You get a reply and an honest assessment within two working days.
Discuss a process in this industry