UP↑SCALE › LABS, QUALITY & METROLOGY › AUDITORS & QA TEAMS › DEVICE QUALIFICATION
Computer system qualification: time sync and WORM storage for every device at your balance
Computer system qualification of a balance station shows that every connected device takes its time from a trusted source and stores the records where they cannot be deleted. No clock in the scale, no WORM disk? Close both in an afternoon. Every FDA, GMP or ISO audit asks two things about a connected balance: where does the time come from, and can the records be deleted? The answer is a short procedure of yours - and UP↑SCALE has the tools for it built in: templates for your IT, a qualification form that fills itself in, a sealed record for your binder that you sign electronically and a device register on the scale.
- Templates for your IT: a locked, synced clock
- A qualification form for every PC, tablet and phone
- Records sent to your write-protected storage
- A device register with due dates on the scale
In short
UP↑SCALE is one scale app for the balance you already have. For regulated labs it qualifies every PC, tablet or phone at the balance: templates for your IT, a form that fills itself in and a signed record that the clock is locked and the records go to write-protected storage. The form and the templates are free; the sealed PDF, signatures and device register need ENTERPRISE (from 13.00 EUR a month).
The two questions of every audit: time stamps and record retention
1Where does the time come from?
The scale has no battery-backed clock: the time of every record comes from the phone, tablet or PC that runs the app - the device. An auditor wants to see that this time comes from a time server and that operators can't change it to backdate a record. Your answer: the clocks of the devices are synchronized and locked, and you recorded it (time integrity, ALCOA+ "contemporaneous", 21 CFR 11.10(e)). On top, the scale can check them itself: with one click it takes the exact time signed by up-scales.com (from several public time servers) and logs every device that is more than 2 minutes off.
2Can the records be deleted?
Our records are tamper-evident: hash chain, record files linked by hash, the UP↑SCALE SEAL - a change or a gap shows up. But a file on a disk can still be deleted. Real write-once (WORM) is a feature of the storage, never of an app. Your answer: every record goes straight to write-protected storage, and you recorded it (record retention, 21 CFR 11.10(c), EU GMP Annex 11 point 7).
Both are the same for every connected balance and every software - not a gap of UP↑SCALE, but a part of every validation. The difference: here the tools to close them are in the app.
How to qualify a PC, tablet or phone in three steps ENTERPRISE
1Your IT applies the templates
The app writes ready-made settings, filled with your time server and your records folder: a Windows .reg file (browser policy, time server, the hidden Date & time page), Linux (chrony / timesyncd, Chrome policy), an Android MDM policy (automatic time enforced, developer options off), macOS, and the browser policy as JSON: developer tools off, the download folder = your records share, no incognito, no new profiles, no extensions. The app never changes your systems - they are templates for your IT, best rolled out by Group Policy or MDM. free
2The tester runs the form on every device
One form per device, with the tests of its system. Every test has its command with a COPY button; paste what the command printed, and the app proposes PASS or FAIL (it reads "Operation not permitted", "System clock synchronized: yes", a time source that is not the local CMOS clock - also the German and Spanish messages). Clock checks against the scale and a live reference clock, a test file for the records folder, and the storage tests (delete, overwrite, retention, second copy). The tester decides every result. free
3QA signs the record - the scale keeps the register
SAVE SEALED PDF makes a numbered PDF sealed by the scale, with lines for the printed name, signature and date of the tester and the QA reviewer - and both sign it electronically right after saving (performed / reviewed), with their password, which the scale checks every time and writes into its log. The scale enters the device in its device register with the due date of the next qualification. With strict audit, a device that is not qualified can't change settings or book sales. ENTERPRISE
Manual: station qualification, time per system, record storage, register, clock guard
The qualification checklist: Windows, Linux, Android, macOS, browser
What the form tests - run every test as the operator of the device, not as an administrator. ✓ = the app reads or proposes it, ✍ = the tester looks.
| System | Test | Expected | |
|---|---|---|---|
| Windows | operator is no administrator: whoami /groups | not in Administrators | ✓ |
| Windows | set the time / the time zone: time, tzutil /s | "A required privilege is not held" / access denied | ✓ |
| Windows | time source: w32tm /query /source | your time server - not "Local CMOS Clock" | ✓ |
| Windows | Date & time page, BIOS / UEFI password | hidden or locked; password set | ✍ |
| Linux | groups, date -s, timedatectl set-timezone, set-ntp false | no sudo / wheel; "Operation not permitted"; admin password asked | ✓ |
| Linux | timedatectl status, chronyc sources | synchronized: yes, NTP service: active, your server | ✓ |
| Android | Settings app, automatic time and time zone, developer options, restart offline | blocked or locked by the MDM; the time corrects itself | ✍ |
| macOS | groups, date 1200, Date & Time, startup security | no admin; "Operation not permitted"; automatic | ✓ |
| Browser | chrome://policy, F12, incognito / guest / extensions | DevTools off, download folder = records folder; blocked | ✓ |
| Clock | this device against the scale; against a reference clock; time zone; clock jumps since the last qualification | ≤ 5 s; ≤ 2 s (your limit); the site; none | ✓ |
| Storage | test file lands in the records folder; delete / overwrite as operator; retention lock; second copy | without a dialog; refused; set; present | ✍ |
| Storage | newest record file and its fingerprint; browser storage persistent | fingerprint in your binder; yes | ✓ |
The settings behind it, per system: time integrity in the manual and record storage. Check the steps against your own systems - names of policies and menus change between versions.
The qualification in the app
Each test with its command, the expected result, the pasted output and PASS - and the activity log of the scale.


More about the app, with all screenshots →Screenshots of the real app with demo values - a screenshot may show the look of an older app version.
Filled in for you
Most of a qualification record is typing what is already known. The app does it, read at the moment of the test:
- The device: its ID, browser and mode (installed app, tab, offline file), time zone, app version, the logged-in user - and a system proposed from the browser.
- The scale: name, firmware, Device ID, serial number, licence, certificate data, last calibration, the calibration and configuration counters, the last passed routine check.
- Its data-integrity setup: users and roles (and whether everybody has a password), strict audit, the protections, the device register, heartbeat lock, tare guard, EXACT WEIGHT, the seal key and its certificate.
- The clock: this device minus the scale, clock jumps since the start of the scale, and every jump the scale logged since the last qualification (from the archived activity log).
- The archive: the state of the activity-log archive, the newest record file with its SHA-256 fingerprint, persistent browser storage and its use.
- Remembered per device: asset ID, location, time server, records folder, kind of storage, retention - a re-qualification only needs the tests again.
- People: tester and QA reviewer picked from the users of the scale (name and title).
What the auditor gets: the signed qualification record
| Part | Content |
|---|---|
| Header | your company and logo, report number counted by the scale, date, user |
| 1 Device | asset ID, location, system and version, time server, records folder, kind of storage, retention, second copy, linked scale with serial number |
| 2 Read by the app | device, scale, data-integrity setup, archive and storage - as listed above |
| 3 Tests | per group: number, action and command, expected, observed (the pasted output), result |
| 4 Result | QUALIFIED / NOT QUALIFIED, the deviations with the action taken, the next qualification |
| 5 Signatures | lines for the printed name, signature and date of the tester and the QA reviewer, and their electronic signatures (performed / reviewed: name, time, meaning, checked by the scale) in the signed report file |
| Footer | integrity code, the UP↑SCALE SEAL, the address of the public check |
| Attached | the HTML report, all pasted outputs as text, the form as JSON |
The PDF is sealed by the scale: anybody checks it on up-scales.com/check, in the browser. The blank paper form (all systems, tick boxes) is free - for a site that wants to start on paper.
Many devices? One register
A scale is often run from several devices - the PC in the lab, a tablet at the bench, the phone of the QA. Each is a device and gets its own record. The UP↑SCALE keeps the device register: the same list for every app, up to 50 devices, with system, state, date, due date, report number and who saved it.
- Add a device: run the form on it - the signed PDF enters it.
- Re-qualify: every 3, 6, 12 or 24 months; a due device is marked due.
- Remove a device: RETIRE with a reason (replaced, broken, lost, not used any more) - it stays listed, because older records were made on it. Nothing is ever deleted.
- Enforced with strict audit: a device that is not qualified (or due) can weigh and print, but the UP↑SCALE refuses its changes and sales; a sale is kept and sent again after the qualification.
- The register as a signed PDF with all devices and the device events and clock jumps from the archived log - one page for the binder.
- The clock guard of the scale: a time that differs by more than 2 minutes from the running time of the scale is written to the activity log - with strict audit the scale keeps its own time. 🕒 EXACT TIME FROM UP-SCALES.COM gives the scale a reference of its own: the signed exact time, set with one click (or automatically at every connect of an online device) and logged with how far the clock was off.
Effort and costs
| Usual way | UP↑SCALE | |
|---|---|---|
| Validation documents for the devices | written by hand or bought as a package | form, templates and record in the app |
| Typing the system data | by hand, per device | read by the app |
| Judging the command outputs | by eye | proposed by the app, decided by the tester |
| List of qualified devices | a spreadsheet | the register on the scale, the same for every app |
| Costs | consulting days, often per seat | 144.00 EUR a year or 599.00 EUR once per scale - the form, the blank paper form and the templates are free |
What it saves in hours and subscriptions for a whole lab: the cost table of the QA guide.
Still your part: your IT applies the settings and runs the storage, your QA signs and keeps the SOP. Less work - not none.
The limits - for your validation
- Tamper-evident, not WORM: the app can't make a disk write-once. The WORM part is your storage (WORM folder, immutable snapshots, object lock); a folder that is only write-protected by rights can be changed by an administrator.
- The time still comes from the devices: the qualification shows that they are locked and synchronized; the clock guard of the scale shows big jumps (more than 2 minutes), not small ones. After a restart of the scale the first app that connects sets its time again - with the signed exact time ticked for every connect, an online device corrects it a few seconds later and the log shows by how much. That needs the internet for a moment; a site without internet relies on the qualified devices alone.
- A device is a browser profile with a random ID, not a hardware ID - the asset ID on the record and your SOP tie it to the device; block new browser profiles with the policy.
- Templates are templates: names of policies and menus change with the versions of the systems - your IT checks them. The app proposes results; the tester decides and signs.
- The register holds 50 devices per scale (the oldest retired one is reused when it is full). A retired device can be taken off the list to keep it clean - at once while the scale has no users, with users by an ADMIN or QM 12 months after the retirement. The removal is logged in the chained activity log.
UP↑SCALE gives you tools and records - it makes no claim that you comply with a rule or that an auditor accepts them; the record is your own qualification, not a certificate. All details: device qualification in the manual. Audit trail & data integrity → The page for laboratories →
Clock and record storage: questions and answers
Why do auditors ask about the clock of a connected balance?
Because the time of every record must be right and nobody may backdate it (ALCOA+ "contemporaneous", 21 CFR 11.10(e)). The scale has no battery-backed clock - the time comes from the phone, tablet or PC that runs the app - so you show that those clocks come from a time server and that operators can not change them.
How do I prevent users from changing the date and time in Windows?
Run them without admin rights and give the rights Change the system time and Change the time zone only to Administrators (group policy, User Rights Assignment - standard users may change the time zone by default). Set the time source to your time server (w32tm /query /source must not say "Local CMOS Clock") and hide the Date & time page by policy. The app writes a ready-made .reg file with your time server and checks the result: setting the time must answer "A required privilege is not held".
What does "Local CMOS Clock" mean in w32tm /query /source?
That Windows takes its time from the hardware clock of the PC, not from a time server. For a qualified device the source must name your time server - not "Local CMOS Clock" or "Free-running System Clock". The Windows template of the app sets the NTP client to your server, and the form reads the pasted output and proposes PASS or FAIL; the tester decides.
How do I check that a Linux PC syncs its time (timedatectl, chrony)?
timedatectl status must show "System clock synchronized: yes" and "NTP service: active", and chronyc sources lists your time server. As the operator, date -s must answer "Operation not permitted", and timedatectl set-timezone and set-ntp false must ask for an administrator password. Paste the outputs into the form - the app proposes PASS or FAIL.
How do I enforce automatic date and time on Android tablets?
With an MDM (Android Enterprise): set automatic date and time zone to enforced, switch the developer options off and use kiosk mode or a work profile without the Settings app. Android takes its time from the mobile network or time.android.com, not from the time server of your Wi-Fi - a company time server needs an option of your MDM or of the maker. The test: Wi-Fi off, restart, Wi-Fi on - the time must correct itself.
How do I disable the developer tools in Chrome by group policy?
With the browser policy DeveloperToolsAvailability = 2, rolled out by Group Policy or MDM - with the developer tools a page could be given another time. The browser policy template of the app contains it, together with the download folder = your records folder, no incognito, no new profiles and no extensions. The test: paste the list of chrome://policy into the form.
What is WORM storage?
Write once, read many: storage on which files can be added, but not changed or deleted - a NAS or server with a WORM folder or read-only snapshots, or cloud storage with an object lock in compliance mode. It is a feature of the storage, never of an app, and a folder that is only write-protected by rights can still be changed by an administrator. The records of UP↑SCALE are tamper-evident and go straight to that storage; the device qualification tests it and records it.
Do I need WORM storage for balance records?
For record retention (21 CFR 11.10(c), EU GMP Annex 11 point 7) the records must be protected for as long as you keep them. Write-once is a feature of the storage, never of an app: send every record straight to a WORM folder, immutable snapshots or object-locked storage, and record it in the device qualification.
What is a device qualification?
A short record per PC, tablet or phone that shows its clock is locked and synchronized and its records go to write-protected storage. In UP↑SCALE the form fills itself in, proposes PASS or FAIL from the pasted command outputs and becomes a PDF sealed by the scale, signed by tester and QA (ENTERPRISE).
How often must a device be re-qualified?
At the interval you set: every 3, 6, 12 or 24 months. The device register on the scale marks a device as due; with strict audit a device that is not qualified (or due) can weigh and print, but its changes and sales are refused.
What does the clock guard of the scale do?
It writes every time that differs by more than 2 minutes from the running time of the scale to the activity log - with strict audit the scale keeps its own time. With one click it also takes the exact time signed by up-scales.com and logs how far its clock was off.
Is there a free device qualification form?
Yes. The form, the blank paper form for all systems (with tick boxes) and the templates for your IT are free. The sealed PDF, the electronic signatures and the device register on the scale need ENTERPRISE.
Who else uses it
Auditors & QA teams
Labs, quality & metrologyCheck the records of many scales in minutes instead of days: every file checks itself, the reviews and signatures are in the records, and the documents for the binder come out of the app.
Read →Business & production
Business & productionWeighing scale software for shops, packers, kitchens and workshops: weigh, price, label, count, check and book on the scale you have - pay once.
Read →Laboratories & pharmacies
Labs, quality & metrologyThe compounding assistant from master formula to signed batch record, routine checks before use, a full test suite and records you can prove: users, roles, reasons, a hash-chained audit trail and sealed reports.
Read →Tamper-evident records
Labs, quality & metrologyAudit trail, hash chain, numbered records, the LEGAL MODE store - and the controls an audit expects.
Read →LIMS, ELN & sensors
Labs, quality & metrologyEvery weighing to your LIMS or ELN, room values next to it, air buoyancy corrected.
Read →Records & validation: more pages
21 CFR Part 11 audit trail
Labs, quality & metrologyWho, when, what and why in the scale - mapped to Part 11, EU GMP Annex 11 and ALCOA+, point by point, with the limits.
Read →QA guide: validation (IQ/OQ/PQ)
Labs, quality & metrologyIntroducing it in a regulated lab: the QA tasks, what the app takes over, IQ / OQ / PQ, an estimate of the effort and the steps to the sign-off.
Read →The same app, for other work
Every function is in the same app - at home, in business and in the lab. All functions at a glance.