Weighing application software
Weighing application software: digitising weighing processes without losing data integrity
"We still document dispensing on paper" is not a deficiency – GMP requires evidence, not digitisation. Moving to weighing and dosing software pays off for other reasons: auditability, error rate, trending, less dependence on individuals. This page describes what a digital weighing process must deliver, where digitisation projects typically fail, and how d-dispensing covers the requirements.
Part 1 · The weighing process as a data process
What paper does well – and what it doesn't
Paper is robust, needs no power and every inspector accepts it. It fails in three places: container identification (handwritten lot numbers are the most common traceability gap), tolerance enforcement (a form cannot prevent an overshoot) and analysis (trends, deviation clusters and operator errors are practically invisible on paper). Add the transfer to the ERP – a second manual step with its own error rate.
ALCOA+: what a digital weighing record must satisfy
| Principle | Meaning for weighing | Typical violation |
|---|---|---|
| Attributable | Operator and scale per record | Shared login, "shift 2" |
| Legible | Readable for years | Proprietary format without export |
| Contemporaneous | System timestamp at the moment of weighing | Time entered afterwards |
| Original | First record or verified copy | Excel transcript treated as the "original" |
| Accurate | Value straight from the scale, not typed | Manual weight entry |
| Complete | Refusals and aborts logged too | Only successful weighings stored |
| Consistent | Event order traceable | Label printed before booking |
| Enduring | Retained for the retention period, tamper-protected | Rotating log files |
| Available | Retrievable for review and inspection | "A colleague has the export" |
Where digitisation projects for weighing fail
The software manages its own recipes, which drift away from the ERP (two truths – see recipe weighing software). The ERP interface is sold as "available" and turns out to be a project. Tolerances are only checked in the UI. A network outage stops production or causes double bookings. Validation is underestimated because the vendor says "validated", while it is the operator who has to qualify the system. And the old system is switched off before the new one has been checked against its behaviour – operators no longer recognise "their" workflow.
Planning the transition
- 01Document the as-is workflow – including the unwritten rules at the bench.
- 02Prioritise requirements – container check, tolerance enforcement, audit trail, ERP booking, failure behaviour.
- 03Check master data – material master, GHS data and container identifiers in the ERP must be clean; the software won't clean them.
- 04Pilot bench – one scale, one product family, a defined period, the leading record clearly named.
- 05Risk-based qualification (Annex 15 / GAMP 5) – use the vendor's system description and test evidence, and check your own requirements against them.
- 06Cutover with a rollback plan. If a legacy terminal is being replaced, see weighing terminal software for the migration path.
Part 2 · What d-dispensing brings
What d-dispensing brings
d-dispensing is weighing application software for manual dispensing against a bill of materials – a dispensing system in the sense used in pharma. Measured against the ALCOA+ table:
- Attributable: operator, bench and timestamp per weighing; weight straight from the scale, never typed.
- Contemporaneous and original: the record is created at the bench at the moment of finishing and stored durably first – before label and booking.
- Complete: refusals (wrong container, tolerance breach), licence checks and software updates sit in the same audit trail as weighings.
- Consistent: fixed order store → label → book; the label barcode is the record ID.
- Enduring: hash-chained audit trail; changes become detectable.
- Available: QA export built in; stock lives in the ERP (myfactory or weclapp) and WMS (xstorage) anyway.
Tolerances (104 % of remaining per weighing, 98–102 % position closure, warnings at 50 %/95 %) are checked on the site server. Dosing in partial quantities is counted cumulatively per position. GHS pictograms sit next to the live weight. Proof of charging belongs to the same record. On network loss the weighing in progress finishes and is booked idempotently later.
FAQ
Frequently asked questions
Next step
Where to read next
- QA: Dispensing under GMP – requirements and 12-point checklist.
- Production: Try the live terminal.
- Management: A demo on your own orders; ten-question list in the FAQ.