BenchToLIMS

Email guillem@benchtolims.com Phone +1-505-985-7510

Send one WinLab32 export. See it as a LIMS-ready file in 3 business days.

I build LIMS connections for used PerkinElmer AA and ICP-OES systems: the link from the WinLab32 results export to the buyer’s LIMS, with the validation record an ISO 17025 lab needs to sign off the interface. I do the software; your technician keeps any on-site work.

I’m Guillem Soler Suetta. BenchToLIMS is part of Orbitcheck LLC, my New Mexico company.

For used-equipment dealers and service companies that sell or install PerkinElmer AAnalyst (AA) and Optima (ICP-OES) systems.

A test run is fine; no customer data needed. In WinLab32, results are exported from Data Manager, normally as a comma-delimited text file. Not sure which file? Email me the instrument model.

  1. Your WinLab32 results exportA test run is fine.
  2. Field mapping and value checksEvery field mapped, every value checked.
  3. LIMS import file and validation recordIn the format your buyer’s LIMS expects.

The offer in three steps

  1. Free preview. Send one WinLab32 export. Within 3 business days I send back what the LIMS-ready file looks like, at no charge.

  2. Feasibility check: $1,500 USD, fixed. A working sample connection, a field-mapping sheet and a validation record, within 5 business days of payment and files. Credited in full against the first installation ordered for that instrument model. If I can’t connect your files reliably, I explain why in writing and refund the $1,500 in full.

  3. Installation: about $6,000 USD per instrument connection. Validation record for that lab included. After the check you get a fixed price for your buyer’s LIMS. Support is about $1,200 USD a year per connection, and I handle it directly with the lab.

You can offer “LIMS-ready” as a line item on the sale. Your margin is agreed per deal: quote the add-on to your buyer at your price.

Who I am

Guillem Soler Suetta

Guillem Soler Suetta

I build every connection myself, from the free preview to the validation record, and I handle the support with the lab afterwards. I’m independent of PerkinElmer and of every LIMS vendor.

BenchToLIMS is new, so there are no installations to point to yet. Judge it on your own file: send one export and see it converted before you spend anything.

Which instruments

PerkinElmer instruments on WinLab32 only. Instruments set up with Syngistix aren’t covered yet.

Models in scope, by the software the unit runs
ModelSoftwareStatus
AAnalyst 200, 400, 600, 800 (AA)WinLab32In scope
Optima 4300 DV / V, 7000 DV, 7300 DV (ICP-OES)WinLab32In scope
Optima 8000, 8300 (ICP-OES)WinLab32In scope when the unit runs WinLab32
Optima 8000, 8300 set up with SyngistixSyngistixNot covered yet
Optima 7300 V, Avio, PinAAcle set up with SyngistixSyngistixNot covered yet
Optima 2000, 2100, 5300Probably WinLab32 (unconfirmed)After a sample file confirms the export

For an Optima 8000 or 8300, check whether it runs WinLab32 or Syngistix.

An AAnalyst 200 or 400 sold without the WinLab32 PC may have no results file to export. If you’re not sure, email me the model.

  • I don’t change the instrument or WinLab32.
  • During the check I work from export files, so I need no live remote access to your buyer’s network.

The feasibility check: $1,500 USD, fixed

You send

  • 2–3 WinLab32 results exports from one instrument model (test runs are fine; no customer data needed).
  • The name of a LIMS one of your buyers uses, and its import template if you have it. If not, a generic CSV import format is used.
  • 30 minutes for a kick-off call.

You get, within 5 business days of payment and files

  1. A working sample connection: your exports in, a LIMS import file out.
  2. A field-mapping sheet: every WinLab32 field and where it lands.
  3. A validation record: a test protocol plus the executed results, checking every value, unit and sample ID in the output against the source export.
  4. A short note on what an installation at a buyer’s lab would involve for that LIMS.
Acceptance
You accept the sample when the output file matches the source exports value for value and the validation record is complete.
If it doesn’t work
If I can’t connect your files reliably, I explain why in writing and refund the $1,500 in full.
Credit
The $1,500 is credited in full against the first installation ordered for the instrument model that was checked.
Payment
Orders are confirmed in writing: an invoice from Orbitcheck LLC by email, paid by ACH or wire and due before work starts.
Timing
The 5-business-day clock starts when the payment and the files have both arrived.
Capacity
I have room for two feasibility checks before Friday, December 4 (Thanksgiving week, November 23–27, excluded). For the sample to reach you before then, payment and files need to arrive by Tuesday, November 17. ACH can take a few business days, so a wire is quicker.

Already seen your preview? Email me to book the $1,500 feasibility check.

What the paperwork looks like

Excerpts from two of the deliverables. The real ones are built from your own file.

Format sample. Illustrative, not customer data.
Field-mapping sheet, excerpt
WinLab32 fieldLIMS import fieldRule
Sample IDsample_idCopied exactly
Analyte NameanalyteElement and wavelength (ICP) or element (AA)
ConcentrationresultCopied value for value

Built from your export and your buyer’s LIMS template; real field names are confirmed from the file. Without a template, the target is a generic CSV import.

Format sample. Illustrative, not customer data.
Validation record, excerpt
CheckResult
Sample ID carried overPASS or FAIL
Value matches the exportPASS or FAIL
Unit matches the exportPASS or FAIL
Row count matches the exportPASS or FAIL

Each row ends in PASS or FAIL against your own file. The full record is a test protocol plus the executed results for every value, unit and sample ID.

Questions

“The lab’s LIMS vendor can do this.”

They can. With me, the check has a fixed price and a delivery date: $1,500 USD, within 5 business days of payment and files. After it, the installation gets a fixed price for that LIMS, validation record included.

“WinLab32 already has a LIMS export.”

It does, and that’s what I read. The export alone doesn’t map WinLab32’s fields to the buyer’s LIMS, or show the auditor that every value arrived intact. ISO/IEC 17025:2017 (clause 7.11.2) asks labs to validate interfaces before use. That mapping and evidence is the work.

“We don’t sell software or want support calls.”

You wouldn’t support it. I do the software remotely and handle support directly with the lab; you offer it as a line item and your technician keeps the on-site part.

“$1,500 is a lot for a test.”

It’s credited in full against the first installation ordered for that instrument model, and you get a working sample to show buyers. If I can’t connect your files reliably, I explain why in writing and refund the $1,500 in full.

“Labs won’t allow remote access.”

The check works from the export files, so I don’t need access to the lab’s network. Your technician can install the connector on site.

Contact

Guillem Soler Suetta, BenchToLIMS

Email
guillem@benchtolims.com
Phone
+1-505-985-7510If I miss your call, leave a message and I’ll call back within one business day.
Mailing address
1209 Mountain Road Pl NE, Ste N, Albuquerque, NM 87110

If you’d rather not hear from me, reply “no thanks” and I won’t email you again.

Save my contact card