WAPP
Science/IndustrialLIMS for interlaboratory proficiency testing2022

SPEKTROKHIM: LIMS for proficiency testing

250 laboratories submit proficiency testing results without email and spreadsheets. A custom LIMS replaced a legacy platform and made reporting 3× faster.

LaravelVue.jsMySQLlaboratories
SPEKTROKHIM: LIMS for proficiency testing
250+
active laboratories
600+
registered analysts
×3
faster reporting
×2
fewer corrections

Every few months an administrator at SPEKTROKHIM opened her inbox and started copying numbers. 250 laboratories, each with its own format: some wrote 0,00412, others 0.00412; some sent one file, others three. One mistyped digit in the master spreadsheet and the whole proficiency testing round loses credibility with accreditation bodies.

How SPEKTROKHIM worked before

SPEKTROKHIM runs interlaboratory comparisons, also called proficiency testing. The same sample of crude oil, bitumen or a food product goes to dozens of independent laboratories. Each lab measures it, submits a result and gets evaluated against the whole cohort. That is how a laboratory proves its competence to an accreditation body.

The legacy platform covered only part of the process: it was built for an in-house lab, not for coordinating an external network. Registration, participant management and the final report ran through email and Excel. One round took weeks, because every step needed manual work.

ApplicationsEmail and manual participant registration
ResultsFiles in different formats, collated in Excel
ReportWeeks of manual checks before release
With WAPPThe whole round, from setup to report, in one system

By 2022 the workarounds had become the process, and the platform had become expensive to keep: licences, slow updates, no control over the roadmap. The brief was not to adapt it, but to replace it.

What we built

What we did

A round from the library, not from scratch

Objects (crude oil, fuel oil, bitumen), analytes (ash content, water, sulphur) and thousands of national standards live in one library. Setting up a round takes minutes instead of hours.

Live participant status

The organizer sees who has submitted, who has not, and whose result needs a second look. No calls, no reminder emails, no checklists.

No format errors at the input

Results are entered to five decimal places. An incomplete form cannot be sent and the protocol scan is mandatory, so only confirmed data enters the round.

A report ready for audit

The Excel export keeps strict data types: numbers stay numbers, separators stay consistent. The audit trail is part of the export.

01

Organizer portal: a round without the spreadsheet

We designed the organizer portal around one question: what does an administrator actually do during a round? Set it up, track who has submitted, close it and produce the report. The portal removes everything else.

Rounds, participants and statuses on one screen, with no manual checklist.

Proficiency testing rounds and live participant statuses
02

Lab portal: precision at the input

An analyst should be able to submit results without reading a manual. After login they see only their own programs, open submission windows and required analytes.

Result entry

The system does not warn, it blocks: a result cannot be sent until every field is filled and the protocol scan is attached.

Lab portal: programs, submission windows and result entry

Why custom, not off-the-shelf

Packaged LIMS products are built for an in-house lab: one team, one sample flow, a predictable process. SPEKTROKHIM's job is different: coordinating 250 independent external participants against one statistical method. That is proficiency testing software, not in-lab sample tracking.

The closest packaged products would have covered about a third of the requirements. The rest would have been paid customisation on the vendor's timeline and architecture, paid for again every time requirements change. Custom development costs more at the start and less every year after: SPEKTROKHIM owns the system, pays no licence fees and adds new methods on its own.

Technology

The stack had to handle hundreds of participants submitting at once and export reports with thousands of rows without slowing down.

Laravel
the graph of objects, analytes, methods and standards
Vue.js
large tables without lag
MySQL
database

Rolling out a LIMS is also about people: lab staff have habits built around old processes. Why staff bypass new systems and how to prevent it is covered in Why lab staff bypass LIMS.

Result

Custom LIMS in production: 250+ labs, reports 3× faster, half as many corrections.

Report preparation that used to take weeks of manual collation now finishes when the organizer closes the round. There are fewer corrections not because analysts became more careful, but because the portal does not accept data that would need correcting.

What's next

If your team runs proficiency testing, interlaboratory comparisons or other regulated lab processes through spreadsheets and email because nothing off the shelf fits, that is the problem we solve. We start with how your rounds actually run, then design the system around it.