Customize SciSure to work your way

Your sample sits in a freezer with a barcode on it. Your experiment sits in a notebook with a protocol in it. Somewhere between the two, a scientist types a sample ID into a text field, and from that moment the two records only agree because a human was careful.

That is the gap ELN and LIMS integration is supposed to close. It usually doesn't, because "integrated" gets used to describe three fairly different arrangements, and only one of them actually removes the retyping.

This post is about telling them apart. If you're still working out whether you need an electronic lab notebook (ELN), a laboratory information management system (LIMS), or both, start with ELN vs LIMS: What's the Difference and come back. SciSure Research combines both in one system, which is why we spend a lot of time on this question with buyers, and why the distinctions below matter to us as much as to you.

What ELN and LIMS integration actually means

ELN and LIMS integration means an experiment record and a sample record share the same identifiers, the same permission model, and the same audit trail. When a scientist pulls a vial for an assay, the sample's quantity drops, the experiment shows which vial was used, and the sample's history shows which experiment consumed it. Nobody keys anything twice.

Anything short of that is data transfer. Data transfer is often fine. It is not the same thing, and it fails differently: quietly, months later, when someone archives a sample and the link in the experiment turns into an orphaned string.

One system, one data model

Experiments, samples, storage, and equipment are records in the same environment. Using a sample in an experiment creates a real reference between two objects, not a copied string, and that reference behaves consistently through archiving, export, permission changes, and audit-trail review.

The trade-off is scope. A single system covers what its data model covers. If you need a capability outside it, you extend it through an application programming interface (API) or an add-on rather than swapping in a specialist tool.

Two products from one vendor, joined by a connector

Common in vendor portfolios assembled through acquisition. The notebook and the inventory system were built by different teams at different times, and a connector holds them together. This can work well, and one vendor to call is genuinely worth something.

Make sure to double-check:

• Is the connector included or separately licensed?
• Do both products share one permission model?
• Do they release on the same schedule?

A connector that ships a quarter behind the products it connects is a maintenance job, not a feature.

Two vendors, joined by middleware

Best-of-breed. You pick the strongest notebook and the strongest sample system and connect them yourself, usually through REST APIs and an integration layer.

Labs with real informatics staff do this well, and for some workflows there is no alternative. But you now own the integration: its testing, its validation evidence in a regulated environment, its behaviour when either vendor changes a schema, and its documentation when the person who built it moves on. Budget for it as a system, not a project.

Which vendors offer integrated ELN and LIMS

This is a summary of what each vendor publishes, not an evaluation, and it changes as products change. Make sure to verify against their public documentation before you build your shortlist.

Keep in mind that several platforms that read as "one system" are LIMS-first products that added notebook capability, or notebook-first products that added inventory. Neither origin is a problem. It does shape which side feels mature, so weight your evaluation toward whichever side your team lives in daily.

Also keep in mind that "the vendor offers both" and "the two are one system" are different claims. LabArchives is the clearest example: the ELN and the inventory product are genuinely connected, and they are also separately purchased products. That's a legitimate model. It just isn't the same as a shared data model, and the pricing page tells you more than the product page does.

What integration changes day to day

Sample lineage that survives the experiment

A sample generated in one experiment becomes the input to the next. In a single system, the lineage tree renders that chain without anyone maintaining it. Across two systems, lineage lives on the sample side and experiment context lives on the notebook side, and reconstructing the full picture is a manual job.

Reagent traceability during an investigation

‍When a lot goes bad, you need every experiment that touched it. That query is trivial when reagent records and experiment records are in one place and painful when they aren't.

Barcode actions that do more than look up

‍Scanning a vial can check it out, log the user and timestamp, decrement quantity, and attach it to the open experiment in one action. Chained actions like this need write access to both record types at once.

Audit trails that read as one story

‍Two separate audit trails, exported separately and correlated by timestamp, is an answer an auditor will accept and won't enjoy. One trail across samples, series, equipment, and experiments is a better afternoon for everyone.

How Food Brewer built traceability from tissue to bioreactor

Food Brewer produces cocoa from plant cell cultures, scaling selected tissues through multiple stages up to 2,500 litre bioreactors. Twenty-one people, about half in R&D and production, working on processes novel enough that regulatory approval and IP protection depend on documentation quality.

They built on SciSure from the start. Standardized naming and folder hierarchy across projects, experiments, and datasets. Barcoding across cell cultures, equipment, chemicals, and consumables, giving them traceability from the moment plant material enters the lab through scale-up, downstream processing, packaging, and delivery. Inventory thresholds with automated alerts. Substance exposure logged at every timepoint.

Then they went further, using the SciSure Software Development Kit to build automation applications. A single action now triggers experiment creation, generates or deletes samples, updates sample metadata, and launches downstream processes, with the remaining steps running in the background. They also built extract-transform-load pipelines to centralize screening assay results, bioprocess data, and experimental metadata in an internal database for modelling and company-wide KPIs.

Christopher Keim, Head of Process Automation, attributes a 60% productivity increase in R&D and 40% in upstream processing to those automation applications, because the team no longer tracks cultures, chemicals, consumables, and data integration by hand.

Questions to ask before you buy

1. Show me a sample record and an experiment record referencing each other.
   Not a slide. The actual screens, with the link clicked in both directions.
2. What happens to that link when the sample is archived?
   And when the experiment is signed and locked?
3. Are ELN and sample management one licence or two?
   If two, what does the connector cost and who supports it?
4. Do both sides share one permission model?
   Or can a user see a sample they can't see the experiment for, and vice versa?
5. Can I export one audit trail covering samples and experiments together?
   In what formats?
6. Which side came first?
   Every platform has a stronger half. Knowing which one tells you where you'll hit friction.

Where SciSure fits, and where it doesn't

SciSure Research combines ELN and LIMS capabilities in one system.

• Samples, sample series, storage units, equipment, protocols, and experiments reference each other directly.
• Barcode automation supports single-sample, multi-sample, and chained actions in one scan.
• Triggers and automations fire on events like sample creation or a field change, and can send notifications, call webhooks, or create tasks.
• Audit trails span samples, series, equipment, and experiments, exportable to PDF, Excel, and CSV.
• An open API, a software development kit, and a Marketplace of add-ons handle what sits outside the core.

We do want to emphasize, SciSure Health & Safety is a separate SciSure product covering chemical inventory, safety data sheets, inspections, incidents, and training compliance. It has its own records and its own workflows.

SciSure LIMS is also primarily built for research and R&D, where sample types evolve and workflows need to stay configurable. If you're running high-throughput QA/QC with fixed, enforced process pipelines, consider a traditional manufacturing LIMS instead.

FAQs

What does ELN and LIMS integration mean?‍

ELN and LIMS Integration means an experiment record and a sample record share the same identifiers, permission model, and audit trail, so using a sample in an experiment updates both records without manual re-entry. Vendors also apply the term to two separate products connected by a vendor-built connector or by middleware you maintain. Those arrangements transfer data between systems rather than removing the handoff, which is why the same word covers quite different architectures.

Can I integrate an ELN and a LIMS from different vendors?

‍Yes, usually through REST APIs and an integration layer. Labs with informatics staff do this successfully when they need best-of-breed capability on both sides. Plan for it as an ongoing system rather than a one-off project: you own the testing, the behaviour when either vendor changes a schema, and, in regulated environments, the validation evidence for the integration itself.

Do I need both an ELN and a LIMS?

‍It depends on how much of your work is documentation versus sample volume. Research-heavy teams with evolving experiments often start with an ELN. Labs registering, tracking, and dispatching large numbers of samples usually need LIMS capability first. Many labs eventually want both, which is why the question of how they connect matters at the point of purchase rather than two years later.

Does SciSure require middleware to connect ELN and LIMS?‍

No, SciSure Research provides ELN and sample and inventory management in one system, so samples link directly to experiments and equipment records connect to entries without a connector between them. Connecting SciSure to external systems such as instruments or data warehouses uses the open API, the SDK, or Marketplace add-ons, and those integrations do require configuration.

If this sounds like the kind of support you need, get in touch with us. We'll walk you through what ELN and LIMS Integration looks like in one connected platform using your real-life workflows as the base.

If you share equipment with colleagues, you already know where things tend to go wrong. For example, maybe the centrifuge is booked by someone who isn't using it, or the plate reader is out for service and nobody told the team downstairs.

Lab equipment is expensive, shared, and regulated, and most labs manage it with tools that were never built for the job. This post covers what lab equipment management software does, how to tell which type your lab needs, and what SciSure supports today across its Research and Health & Safety products.

Why spreadsheets and sign-up sheets stop working

Whether you're coordinating a single lab or a multi-site organization, managing a suite of instruments and their upkeep is genuinely hard. Here are some of the challenges we hear most often:

• Equipment is spread across different rooms, floors, and sometimes buildings.
• Validation and preventive maintenance schedules vary from instrument to instrument.
• When something breaks, the information you need (a faded serial number, a missing manual, the service engineer's contact) turns out to be unavailable.
• Users with different schedules collide over the same instrument.
• Different users run different protocols on the same machine, so every handover involves a setup transition that takes time and invites error.

Most labs try to head this off with a shared spreadsheet or a paper log. Those approaches share one design flaw: they sit outside the work. Updating them is optional, so eventually they stop matching reality. A missed revalidation can produce unusable or non-compliant data, and then weeks of downtime waiting on parts or a field service engineer.

The consequence is the same in every version of this story: an instrument you can't use, when you need it.

Which type of system do you actually need?

"Lab equipment management software" describes at least three different categories of product, and buyers often shortlist across all three without realizing it. Here's how they differ.

A biotech scheduling a shared confocal microscope and a university EHS office certifying 400 fume hoods are both searching the same phrase. They should end up with different products.

What to look for in lab equipment management software

Once you know which category you're in, these are the capabilities worth pressure-testing during a demo:

Booking and availability

‍A shared calendar showing real-time availability, with the ability to book in advance. Ask specifically what happens when equipment goes out of service. If the system lets people keep booking a broken instrument, it hasn't solved anything.

Calibration and validation tracking

‍Scheduled dates with automated reminders before they expire, not after. This is the single feature that most often justifies the purchase, because the cost of a missed revalidation is measured in weeks.

Equipment records with the details attached

‍Serial numbers, specifications, manuals, service contacts, and location, on the record itself. When something fails at 4pm on a Friday, the difference between a two-hour delay and a two-day one is whether the manual is findable.

Usage logs

‍Who used the instrument, when, and for what. This matters for troubleshooting (which run preceded the fault?), for chargeback models in core facilities, and for audit evidence.

Issue and repair history that doesn't overwrite

‍New service records should append, not replace. A pattern of the same fault every eight months is only visible if the history survives.

Permissions

‍Not everyone should be able to edit every record. Look for role-based access down to individual equipment where you need it.

How SciSure handles equipment management

SciSure covers equipment across two separate products, and it's worth being clear about which does what, because they solve different problems for different teams.

SciSure Research: Equipment your experiments run on

Within SciSure Research, equipment sits alongside samples, inventory, and experiment records. Teams can:

• Create equipment records with type, location, managers, custom specification fields, and attached files.
• Book equipment through a reservation planner that shows availability and prevents scheduling conflicts.
• Track validation and calibration schedules, with automated alerts ahead of expiry.
• Log usage including user, date, time, and purpose.
• Record issues and repairs, and change status so equipment out for service can't be reserved.
• Export audit trails for compliance and data integrity requirements.
• Connect instruments and third-party tools through Marketplace add-ons, the API, or the SDK, where those integrations exist or are built.

Arctic Therapeutics, an Icelandic biotech running drug development programs across Alzheimer's, Parkinson's, and rare-disease research, consolidated equipment logs together with samples, inventory, and experiments after previously managing them across spreadsheets, paper, and a mix of digital tools. The 10-person lab team reports saving around two hours a week on registration and inventory tasks.

Explore SciSure's equipment management capabilities or read more about the LIMS side of the platform.

SciSure Health & Safety: Equipment your safety program has to certify

SciSure Health & Safety takes a different angle. It's built around safety-critical and regulated equipment: biosafety cabinets, fume hoods, eyewash stations and safety showers, fire extinguishers, autoclaves, lasers, X-ray devices, survey meters, freezers, and similar institutional equipment.

Where configured, EHS teams can:

• Add equipment to a group or space with location, ownership, type-specific details, and current status.
• Attach audits, certifications, and service records without overwriting earlier history.
• Configure audit types, define which equipment they apply to, and set who is authorized to perform them.
• Create recurring audit requirements so certifications don't quietly lapse.
• Run bulk audit tools and history reports across large equipment populations.
• Filter and export institutional equipment lists.

SmartLabs, which operates multi-site shared lab facilities, implemented SciSure for chemical inventory, SDS (safety data sheet) management, inspections, equipment management, biosafety, and medical surveillance. This helped the EHS team cut inventory search from 15 minutes to 1-2 minutes, reduced reconciliation for an entire research center from an all-day job to as little as 20 minutes, and brought inventory reporting down from about 30 minutes to roughly one. One manager reports halving the time she spends pulling reports and running inspections, and the team can now break safety requirements down suite by suite across 729 lab spaces rather than treating every space the same.

Just keep in mind: SciSure Research and SciSure Health & Safety are separate products with separate licensing. Labs that need both sides license both. If you're only solving one of these problems right now, you only need one.

Frequently asked questions

What is lab equipment management software?‍

Software that maintains a record for each instrument in a lab, covering location, availability and bookings, calibration and validation dates, usage history, and service records, so that information lives in one place rather than across spreadsheets, calendars, and folders.

Is equipment management part of a LIMS?‍

Often, yes. Research-focused LIMS platforms typically include equipment records, booking, and validation tracking because equipment is part of the same operational picture as samples and inventory. Traditional manufacturing-oriented LIMS platforms vary more. Ask directly rather than assuming it's included.

What's the difference between equipment management in a LIMS and in an EHS system?

‍A LIMS manages equipment as a research resource: who can use it, when it's free, when it was last calibrated, what experiments it was used for. An EHS system manages equipment as a compliance obligation: which safety-critical devices exist, which certifications apply, when the next audit is due, and what evidence exists that it was done.

Can it help with GxP or ISO audits?‍

It can support them. Calibration records, usage logs, audit trails, and permission controls are the evidence auditors ask for. The software supports compliant practice; your organization still owns validation, SOPs, training, retention, and change control.

Can lab equipment management software connect to instruments directly?

‍Sometimes, and it depends heavily on the instrument. Some connections are native, some come through add-ons, and some require custom work via an API or SDK. Treat a vendor's integration list as a starting point and verify your specific instruments before signing.

If this sounds like the kind of support you need, get in touch with us. We'll walk you through how SciSure Research and SciSure Health & Safety adapt to your workflows, not the other way round.

Plasmids are small circular DNA molecules that replicate independently of chromosomal DNA. They carry a gene of interest, a promoter to control its expression, a selection marker, and an origin of replication, which together give you control over what gets expressed, where, and how much. That combination is why they sit at the start of so much work in genetic engineering, recombinant protein production, vaccine development, and gene therapy.

The problem shows up later. Sequences shift during cloning, passaging through a bacterial or mammalian host, or optimization for better expression. Quality drops with repeated freeze-thaw cycles or contamination. And as a library grows past a few dozen constructs, the informal system that worked at the bench (a shared spreadsheet, a notebook page, a labelled box someone maintains) stops holding.

What replaces it is record-keeping: unique identifiers, scheduled QC checks, and a database that other people can actually search. A mistake in the recorded backbone, resistance marker, or host strain is not a small mistake. It costs a week of cloning and a batch of reagents before anyone notices.

This post covers the plasmids most labs keep on hand, the techniques used to build a library, and what a plasmid database needs to hold to stay useful. For deeper coverage of naming conventions, storage protocols and sequence analysis tools, our full whitepaper goes further on each. If you're comparing systems to hold the records themselves, SciSure LIMS is built for sample and inventory work in research settings.

How are plasmids used in genetic engineering?

Plasmids are the delivery vehicle. A gene or fragment gets inserted into a vector backbone, the vector is introduced into a host cell, and the host replicates it. Depending on the vector, that gene is then expressed as protein, integrated into the host genome, or simply amplified so you have more of it. Different vectors are built for different points in that chain.

Most R&D labs keep a set of parental plasmids and their derivatives on hand, ready for whatever is planned. To study a gene's role in a disease model, for example, you might build a library of constructs covering different functional domains, plus variants missing specific domains or carrying targeted mutations. What makes that library reusable a year later is the record attached to each one: backbone, cloning strategy, purification method, and QC history.

The most widely-used plasmids in R&D

• pUC19.
  A high-copy cloning and expression vector for E. coli, with a lac promoter, selectable markers and a multiple cloning site. Used in the DNA sequencing methods that fed into the Human Genome Project, in recombinant protein work, in crop engineering, and in bacterial genetics.
  ‍
• pET vectors.
  Built for high-level protein expression in E. coli. The T7 promoter drives strong transcription, fusion tags such as hexahistidine or GST simplify purification, and inducible promoters let you control when expression starts.
  ‍
• pGEX vectors.
  Express recombinant proteins fused to glutathione S-transferase in E. coli. The GST tag makes purification straightforward by glutathione-affinity chromatography and can be cleaved off afterwards.
  ‍
• pBABE vectors.
  Retroviral transfer and stable expression in mammalian cells. The construct integrates into the host genome, which suits functional assays, overexpression studies and stem cell work.
  ‍
• Lentiviral vectors.
  Gene transfer and gene therapy in mammalian cells, including cells that resist transfection. Derived from HIV but replication-defective, and widely used to deliver CRISPR/Cas9 components.

Lentiviral and other viral vector work usually carries institutional biosafety obligations that plain bacterial cloning does not. Worth confirming what your committee requires before the construct exists, not after.

Molecular biology techniques for working with plasmids

Which techniques you use depends on library size, vector type, and what happens downstream. Here are some common ones:

• PCR amplification to copy a gene or fragment before it goes into a vector.
• Restriction digestion and ligation to cut at defined sites and insert the fragment.
• Transformation to introduce the plasmid into bacterial cells for replication and maintenance.
• Selection, using antibiotics or fluorescence, to keep only the cells that took up the plasmid.
• DNA extraction and purification by alkaline lysis, precipitation, or column- and bead-based methods.
• Sequencing to confirm identity and catch drift.
• Gibson and Golden Gate assembly for scarless, multi-fragment construction where restriction sites are inconvenient.

Each of these steps produces a construct that needs a record. The transformation that worked, the colony that was picked, the sequencing result that confirmed it. If that chain is captured as you go, the plasmid record answers questions later. If it is reconstructed from memory afterwards, it usually does not.

What your plasmid database needs to hold

Most plasmid libraries start in a spreadsheet, and for a small library a spreadsheet is fine. It stops being fine at the point where more than one person edits it, or where someone needs to find every construct carrying a particular resistance marker.

Whatever system you use, these are the fields worth having:

Where SciSure LIMS comes in

With SciSure LIMS, you can define a plasmid sample type with exactly these fields, including required fields, dropdowns for host strain or marker, file attachments for sequence maps, and auto-numbered identifiers.

• Storage units model your freezers down to individual box positions, so "where is it" has an answer rather than a search.
• Quantity thresholds can notify the owner when a stock runs low, and every sample record carries an audit trail of who changed what and when.
• Parent-child relationships let you record that a construct came from a specific backbone, so lineage across a library of derivatives stays visible.
• Sample lineage, check-out tracking and barcode workflows are available as marketplace add-ons, and available fields and permissions depend on how your group is configured.

If you're weighing options, our comparison of sample management and tracking software covers what to look for.

Why plasmid libraries fall apart

Libraries rarely fail all at once. They degrade in ways that are obvious in hindsight:

• ‍Someone leaves.
  A postdoc finishes, and the constructs they built are still in the freezer with names only they understood. The tubes survive. The knowledge does not.
  ‍‍
• Two things share a name.
  Two people independently call something pCMV-GFP2. Six months later nobody can tell which box holds which.‍
  ‍
• The master stock becomes the working stock.
  Nobody meant for it to happen. The convenient tube got used repeatedly, freeze-thaw cycles accumulated, and the backup that was supposed to protect the library is now the degraded one.‍
  ‍
• The spreadsheet forks.
  Someone downloads a copy to work offline, edits it, and now there are two versions with no way to tell which is current.

Each of these is a records problem rather than a science problem, which is why the fix is a records system: one place everyone works from, permissions so the master stock cannot be consumed without anyone noticing, and a history that shows what changed.

Go deeper on building and storing your plasmid library

This post covers what to track and why. Our whitepaper, "The Ultimate Guide to Building, Managing, and Analyzing Your Plasmid Library" covers how, in more detail than fits here:

• Building a sustainable library, from vector selection through QC scheduling
• Naming conventions that hold up past a few thousand constructs
• Storage practices: containers, temperatures, buffers, backups, master stock separation
• Software tools for in silico sequence work and plasmid mapping

FAQs

What is a plasmid library?

‍A plasmid library is the collection of plasmid constructs a lab maintains, usually a set of parental backbones plus derivatives carrying different inserts, mutations or tags. It exists physically as glycerol stocks or purified DNA in a freezer, and digitally as the records describing what each construct is.

What information should a plasmid database contain?

‍At minimum: a unique identifier, plasmid name, backbone, insert, selection marker, host strain, source, sequence file, QC status and date, concentration, storage position, whether the tube is master or working stock, and who owns it.

How are plasmids used in genetic engineering?‍

A gene or fragment is inserted into a vector backbone, the vector is introduced into a host cell, and the host replicates it. Depending on the vector, the gene is then expressed as protein, integrated into the host genome, or amplified for downstream use.

Is a spreadsheet enough for tracking plasmids?

‍For a small single-person library, often yes. Spreadsheets break down once several people edit them, once you need to search by attributes such as resistance marker, or once you need to know who changed a record and when. A LIMS (Laboratory Information Management System) handles those cases with permissions, audit trails and structured search.

What is the difference between master stock and working stock?‍

Master stock is the archived reference copy, stored at -80°C and used only to generate new working stock. Working stock is what the bench draws on day to day. Keeping them separate means repeated freeze-thaw cycles do not degrade the copy you would need to rebuild from.