Splashlake connects thousands of lab instruments to IDBS E-WorkBook, so readings flow straight into your experiments and spreadsheet tables, mapped to the catalog terms your templates already use. Our productized platform goes live in days rather than months, with no orchestrations to design or maintain, and keeps the controls your regulated workflows depend on intact.
IDBS E-WorkBook is where biopharma scientists run structured experiments from controlled templates, calculate results in the E-WorkBook spreadsheet, track samples in E-WorkBook Inventory, and sign off work for GxP review. Those experiments are only as good as the instrument data that goes into them.
Too often that data still arrives by hand. Scientists export a file, copy values into a spreadsheet table, check they match the right sample IDs, and attach the raw output for reviewers. In a validated template that is the weakest link: each manual step invites transcription errors, slows sign-off, and adds work for QA during data integrity review.
Splashlake closes that gap with a productized, bi-directional integration. Jobs and sample lists from E-WorkBook Request go straight to the instrument as worklists. Results come back into the right experiment, written to spreadsheet tables and mapped to your catalog terms, with the raw file and its metadata attached. Scientists move straight to analysis and sign-off, and the Data Mart gets clean, structured data every time.
E-WorkBook is highly configurable, and IDBS gives IT teams several routes for bringing in instrument data. The challenge is scale. Every new instrument usually means another parser or watched folder, another set of mappings in Spreadsheet Designer, and another round of validation each time a template version changes or an instrument vendor updates its software.
Splashlake replaces that per-instrument effort with one productized connection, based on convention over configuration. Instruments plug into Splashlake once, using standard data conventions instead of custom scripts, mapping tables or parsing rules. Splashlake then delivers data to E-WorkBook in the structure your templates expect, so your administrators keep full control of templates, catalog terms and the Advance ontology.

Many IDBS customers add an orchestration or integration platform-as-a-service (iPaaS) layer to move data between instruments and their notebook. That approach is flexible, but each data flow is an orchestration someone has to design, validate and maintain. Splashlake takes a different route: integration delivered as product, plus the data management to go with it. AnIML (Analytical Information Markup Language) is an open, royalty-free XML standard designed to hold data from any analytical technique. Each file is self-contained and human-readable, keeping raw data and metadata together, which makes it well suited to GxP archiving and long-term retention. QA can review the original data years after the instrument software has been retired, and your data stays FAIR, portable and AI-ready.
Most integrations stop at dropping a file into an experiment. Splashlake handles six types of scientific data and puts each one where E-WorkBook users expect to find it:
Files – Raw instrument files attached to the right experiment, with acquisition metadata preserved, so reviewers can trace every result back to its source before sign-off.
Simple instrument data – Balance, pH meter and pipette readings written straight into spreadsheet tables, ready for the calculations your template already performs.
Time series data – Bioreactor, fermenter and environmental sensor streams captured with timestamps, so process development teams can trend runs without manual exports.
Metadata – Instrument, method, operator and timestamp captured automatically, or added manually, and mapped to catalog terms to support GxP review and Data Mart reporting.
Relational data – Every result linked to its sample, batch and parent experiment, keeping sample lineage intact across E-WorkBook Inventory and your experiments.
Chemical structures – Molecular and structural information carried through with the result, so chemistry and analytical data stay connected.
The outcome is an experiment with full scientific context, ready for sign-off, and data that is ready for analytics, AI models and long-term archive.
See how Splashlake sends E-WorkBook requests to your instruments and brings structured results back into your experiments, from thousands of supported instruments and with no orchestrations to build. Integration time drops from months to days, and every result is kept in open AnIML, so your data stays readable and audit-ready for the long term.
Contact us to discuss how your own E-WorkBook solution can be connected to your complete lab ecosystem.
We'll only use your details to respond to your inquiry.