Industries and Applications
Splashlake connects every instrument in your lab to Signals Notebook, so readings flow straight into your experiments, sample tables, plates and Stoichiometry grid instead of being typed in by hand. Our productized, convention-over-configuration platform goes live in days rather than months, with no custom External Actions to write or maintain.
Signals Notebook, part of Revvity’s Signals Research Suite, is where chemists, biologists and formulators plan experiments, draw reactions in ChemDraw, track samples and containers, and pull reagents from the Materials Library. But the data that completes those experiments still lives on the instruments.
Today that gap is usually bridged by hand. Scientists retype balance weights into the Stoichiometry grid, copy plate reader output into a plate, attach exported PDFs and Excel files, then key the numbers into admin-defined tables so they can be searched. Each step costs bench time, invites transcription errors, and leaves an audit trail that shows the typing, not the measurement.
Splashlake closes that gap with a productized, bi-directional integration. Worklists built from your experiments, requests and samples go straight to the instrument. Results come back into the right experiment, already structured in its sample tables, plates and materials tables, with the raw file and its metadata attached. The experiment becomes a complete record you can close with confidence.
Signals Notebook is open by design. Its REST API, External Actions, External Data Sources and External Lists let IT teams wire almost anything into an experiment. The catch is that every instrument becomes its own project: a parser for each file format, an External Data Source endpoint to host, field mappings to maintain, and retesting after every update.
Splashlake replaces that per-instrument build with one productized connection, based on convention over configuration. We connect to Signals Notebook as a single API system user, so every write is attributed and permissioned correctly. Instruments plug into Splashlake once, using standard data conventions instead of custom scripts, mapping tables or parsing rules. Your Signals administrators keep control of material types, admin-defined objects and worksheets in Signals Configuration; Splashlake fits around them.
The result: new instruments are added to Signals Notebook in days, and your integration estate stops growing with every bench you automate.
Most integrations stop at dropping a file into an experiment. Splashlake handles six types of scientific data and puts each one where Signals Notebook users expect to find it:
Files – Raw instrument files attached to the right experiment, with their acquisition metadata preserved, so reviewers never have to chase the original export.
Simple instrument data – Balance, pH meter and pipette readings written straight into the Stoichiometry grid, sample tables or materials tables, with no retyping of actual masses or volumes.
Time series data – Bioreactor, sensor and environmental monitoring streams summarized into the experiment, with the full series kept searchable for later analysis.
Metadata – Instrument, method, operator and timestamp captured automatically, or added manually, and mapped to experiment properties and admin-defined objects to support GxP review.
Relational data – Links between samples, containers, plates, requests and parent experiments maintained, so the Related section of each record shows how results connect.
Chemical structures – Structures matched to compound and reagent records in the Materials Library and to your ChemDraw drawings, so analytical results sit alongside the reaction they characterize.
The outcome is an experiment with full scientific context, and data that is ready for Spotfire analysis, AI models and long-term archive.
See how Splashlake sends work from Signals Notebook to your instruments and brings structured results back into your experiments, without a backlog of custom External Actions. Integration time drops from months to days, and your data stays readable long after any single instrument or software version is retired.
Contact us to discuss connecting your Revvity Signals system with your instrument fleet to support research decisions with superior data confidence.
We'll only use your details to respond to your inquiry.
