// ARCHITECTURE
Applications, instruments and laboratory records
OnLIMS uses Windows applications and Microsoft SQL Server. OnLAB manages jobs and published results; OnWSH brings together instrument readings, preparation values and formulas; OnConfig controls application users and permissions. For your IT team, that is a known stack: the applications run from one shared folder, so a new release is installed once on the share, not on every workstation.
Applications and database
Applications run from a shared network folder; each Windows workstation needs access to the share, the SQL Server ODBC driver and its permissions. SQL Server stores jobs, samples, worksheet results and QC records.
C++ and .NET applications
OnLAB, OnWSH, OnQC, LabData and OnConfig are developed in C++ and .NET. Native modules connect to SQL Server through ODBC and managed modules through the .NET SQL Server data layer, and installation checks cover each module’s dependencies and database access.
Microsoft SQL Server
Jobs, samples, worksheets and QC records are stored in SQL Server, where stored procedures do the heavy data work while the client handles the screens and instrument parsing. Native applications can select among the configured database connections.
Shared application deployment
Executables and libraries sit on a central network share governed by Active Directory, with the application folder read/execute for users. Administrators provide the shortcuts, ODBC drivers and .NET runtimes, and Citrix Virtual Apps or Microsoft RDS deployments are confirmed against the release, drivers and instrument connections.
// Instrument readings, jobs and published exports
Review deployment requirements, interfaces and sizing in the technical specification sheet. OnLIMS technical specification sheet
Connectivity
Readings into OnWSH
Readings reach the worksheet without retyping: the instrument export is imported, each value lands in the column of its sample, element and unit, and the results are calculated on the same sheet.
Hardware Interfaces
OnLIMS connects 150+ instruments from about 40 brands, including Agilent, PerkinElmer, LECO, Thermo Scientific, Malvern Panalytical, Bruker, Rigaku and Chrysos (PhotonAssay), across AAS, ICP-OES/MS, XRF, carbon/sulfur, calorimeters, titrators and balances, by file import or RS232 on-line reading.
Worksheet formulas
Working columns hold readings, weights, volumes and dilutions; result columns calculate the value reported to the OnLAB test; @ columns hold intermediate calculations. Each result column carries its own formula, rounding format and detection limit.
QC records and control charts
OnQC keeps reference-material records with Shewhart, X-Control and CUSUM charts to show bias and drift. When results are locked, a standard, blank or duplicate outside its limits opens the Control Chart window, and the analyst’s decision is recorded with a note.
Control & Compliance
Permissions, review and publication
Who can do what is controlled by role, QC is reviewed on the worksheet, and results are released only by publication. Changes to results leave recorded events in the OnLAB job audit.
Result auditing
Recorded changes include the previous value, new value, user and time. The job’s Audit Viewer filters the events by sample and test and exports the list to Excel.
Roles and access layers
OnConfig defines roles (Administrator, Manager, Supervisor, Chemist, Technician and Client) and a permission matrix for actions such as deleting batches, editing sample dates and publishing results. Windows file access, SQL Server authentication and the OnLIMS login are separate checks.
Worksheet approval and publication
Result cells are locked with the chemist’s password, the worksheet is locked and becomes Approved and read-only, and the results go to OnLAB. Publishing directly from the worksheet requires its own permission.
Configured database connections
Native applications let the user choose among the configured databases, and SQL access and application permissions are set for each database by the administrator.
Template revisions
Worksheet templates are kept as named revisions (for example, “Routine metals rev 02”), so a change to columns, units or formulas becomes a new revision that is checked in a test worksheet before release.
Laboratory records
Evidence available to the reviewer
When an assessor asks where a record is, the answer is in one of these places: worksheet templates, instrument logs, QC charts, user permissions and job audits.
| Record or control | OnLIMS capability |
|---|---|
| Technical records | OnWSH templates define columns, units and formulas. Working columns retain readings and preparation values; result columns link the calculation to the OnLAB test. |
| Instrument records | The worksheet instrument log records the run and the calibration and service expiry dates stored for that instrument, and expired dates are shown before an on-line reading starts. |
| QC review | At result locking, a QC value outside its limits opens the Control Chart. The analyst cancels and repeats, or accepts it with a note; an accepted value is locked and marked red, bold and underlined. |
| Access control | Windows permissions control application files; SQL authentication controls database access; OnConfig roles control application actions. |
| Result corrections | An authorised user unpublishes the result with a password, edits it (for example, from 10.00 to 12.50) and republishes it after review, while the other results stay published. The job audit lists the recorded events with previous and new values. |
For accreditation records beyond the LIMS, see OnQMS, our accreditation product.
Review your deployment and instrument list
Bring the Windows environment, SQL Server requirements and instrument export formats to a technical walkthrough.
Architecture
Frequently Asked Questions
Application access, instrument imports, worksheet approval and result corrections.
What is OnLIMS built on?
OnLIMS uses C++ and .NET applications with Microsoft SQL Server. Native modules connect through ODBC; managed modules use the .NET SQL Server data layer. Applications run from a shared folder with the required workstation dependencies.
How does OnLIMS connect to analytical instruments?
OnLIMS connects 150+ instruments, including AAS, ICP-OES/MS, XRF, carbon/sulfur analyzers and balances. Instrument files are imported into the OnWSH worksheet by sample, element and unit, and RS232 balances write weights straight into the worksheet cell.
Where can OnLIMS be deployed?
The applications run from a Windows network share and connect to Microsoft SQL Server, on Windows workstations or through Citrix Virtual Apps or Microsoft RDS. Each installation is checked against the release, drivers and instrument connections.
How is an out-of-range QC result reviewed?
When results are locked, OnWSH opens the Control Chart for any standard, blank or duplicate outside its limits. The analyst cancels and repeats, or accepts the value with a written note; accepted values appear red, bold and underlined.
How is a published result corrected?
An authorised user unpublishes the result with a password, edits it and publishes it again after review; the other results stay published. The job audit lists the recorded events with previous and new values.