Gerencialab
Results by file, no retyping

Import from equipment and spreadsheets

Typing 100 readings off the instrument display is where the decimal place slips and the right number becomes the wrong one. Here you export the result to a file, upload it and the system loads everything. The reading comes in tied to the right sample and to the instrument that measured it.

Export from the instrument, import into the system, done.

You export the instrument's result to a file, upload it here and the system loads everything. No typing it 100 times, no missing a decimal place.

A typed-in reading calculates automatically via the method spreadsheet.

If the reading is typed by hand, the calculation comes out automatically from the formulas of your Excel spreadsheet. No new formula to build in the system, no confusion.

The system knows which instrument produced each result.

The instrument that produced the result is recorded in the traceability. If later you need to review because the instrument had a problem, you have that information.

The reading lands on the right sample, not a loose list.

The imported file ties each result to its matching sample. You do not check, line by line, whether the value ended up on the right vial.

Imported or typed, the calculation is the same.

Whether the reading came from the instrument or the analyst's hand, the result runs through the method spreadsheet's formulas. One logic, with no second path to maintain.

Less typing is less room for error to enter.

Every number you do not retype is a transcription error that does not happen. On a big campaign, that is the difference between trusting the batch and rechecking it all.

Ever notice that the hardest result error to catch is the transcription one? The value is right on the instrument and right on the report, it only went wrong on the way between the two. Importing by file simply erases that path.
To be straight: it is import by file and spreadsheet, not live serial interfacing. Anyone needing continuous capture straight from the instrument port will not find that in the current version.

Where import by file already solves your day

It is not real-time serial capture, and we are clear about that. But for much of the routine, the file already kills the problem.

The instrument's batch at once.

A whole run of readings uploads in a single file, instead of landing digit by digit on the keyboard.

Your method spreadsheet reused.

The calculation uses your already validated Excel. You do not rebuild the formula inside the system.

Instrument tied to the result.

Each value knows which instrument it came from, so a review over an equipment problem has somewhere to start.

Frequently asked questions

Does the system read the instrument in real time, over the serial port?

Not in the current version. What exists is import by file: you export from the instrument and upload here. We would rather be clear about that than promise serial capture we do not deliver.

And when the reading is typed by hand?

The calculation comes out automatically from your Excel method spreadsheet's formulas. Imported or typed, the reading goes through the same calculation logic.

Does the system keep which instrument produced each result?

It does, in the traceability. If you later need to review because an instrument had a problem, you know exactly which results to look at.

What file format does the system accept?

Files exported from equipment and spreadsheets. In the demo we test with the format your instrument generates, so you see it loading with your own data.

Want to see the LIMS running with your lab's routine?

Book a demo and see it with your own data: the sample comes in by scanner, the QC comes back evaluated, the report comes out signed. No promises, you watch it work.

Import from equipment and spreadsheets · Laboratório · Gerencialab