Purpose
To provide details about the necessary steps to implement the Cytiva Biacore Insight connector for use with the Benchling Connect platform.
Introduction
The Cytiva Biacore Insight connector is a component used in the context of the Benchling Connect platform to parse data from Cytiva's SPR systems including, Biacore T200, Biacore S200, Biacore 1 series, and Biacore 8 series to an Allotrope Simple Model (ASM) and make those data available within the Benchling UI in the context of a Run.
The Benchling Connect, Cytiva Biacore Insight connector is a ‘file-based’ based connector, meaning that it processes .XLSX processed data exports generated by the Biacore Insight software. The data within the file export is then accessed by Benchling Connect through the use of a ‘watched’ file directory on the local computer hosting a Benchling Gateway, which has been configured via a Connection from within Benchling.
In order to successfully implement the Cytiva Biacore Insight connector for use with the Benchling platform, there are several steps that need to be followed across both the Biacore Insight software and Benchling user interfaces.
This guide details the steps to be taken in both applications in order to configure the integration.
Steps within Biacore Insight
From within Cytiva Biacore Insight, a user must:
- Configure a .XLSX export compatible with the Benchling Connect, Cytiva Biacore Insight connector.
- Execute the export of that file from their Biacore Insight session.
- Ensure that the file is placed within the watched directory.
Configuring .XLSX export from Biacore Insight
- Go to the Home workspace and select Spreadsheet -- this will open the Export to Spreadsheet workspace
- Remove the checkmark from components that you do not wish to export.
- Select Export and provide a file name -- file should be saved in the directory configured as the file watched directory.
Below are known limitations of the connector currently. These limitations can be eliminated with your help! If you would like to see any additional functionality to this connector, or other connectors, please reach out to your Benchling rep. and let them know you would like to see a specific feature(s) added to the connector!
Types of analyses offered by Biacore Insight Evaluation
- Kinetics and Affinity Characterization – currently supported
- Steady-State Affinity Analysis
- Concentration and Potency Analysis
- Screening Campaigns
- Epitope Binning and Mapping
The connector currently requires the following sheets from Kinetics and Affinity Characterization experiments:
Properties
Report Point Table
Evaluation - Kinetics
Steps within Benchling
From within Benchling, a user must:
-
Enable the Cytiva Biacore Insight connector on the tenant [internal admin console]
-
Configure a Cytiva Biacore Insight Connection
-
Create a Result schema to structure the data to be recorded
- Configure a Run schema to accept data from Cytiva Biacore Insight and records Results
For steps 1 and 2, please reference the Benchling Connect Installation Guide for details related to creating and installing a Gateway and configuring a Connection.
Creation of Result schema for Cytiva Biacore Insight data
In order to record results returned via the integration a Result schema must be created. This can be done prior to configuration of the Run schema, or within the context of the Run schema Output File configuration.
The Benchling Connect - Cytiva Biacore Insight connector uses the Allotrope Simple Model (ASM) to structure the information parsed from the Cytiva Biacore Insight file export. The data is handled in a two step process; step one from Cytiva Biacore Insight export to the .json based ASM, and step two from the ASM .json to a .csv file available for ingest to Benchling.
These data are structured using the Allotrope Binding Affinity Analyzer ASM data model. Details about this ASM schema can be found here:
The connector then converts the ASM to one of:
sample file .csv - structured such that each row of the file represents a sample, including metadata of the sample
measurement file .csv - structured such that each row of the file represents a measurements (Channel), including metadata of the measurement
report point data file .csv - structured such that each row of the file represents report point data, including metadata of a sensorgram
sample data file can contain the following columns (if available within the data):
- Device ID
- Model #
- Equipment Serial Number
- Product Manufacturer
- ASM File Identifier
- Data System Instance Identifier
- File Name
- UNC Path
- ASM Converter Name
- ASM Converter Version
- Software Name
- Software Version
- Analyst
- Measurement Time
- Analytical Method ID
- Number of Cycles
- Data Collection Rate (Hz)
- Running Buffer
- Measurement End Time
- Sensor Chip Identifier
- Sensor Chip Type
- Product Manufacturer [Sensor Chip]
- Lot Number
- Measurement ID*
- Detection Type
- Method Name
- Sample ID
- Run
- Cycle
- Channel*
- Analyte n Solution -- n based on number of analytes used within experiment
- Analyte n Plate id -- n based on number of analytes used within experiment
- Analyte n Position* -- n based on number of analytes used within experiment
- Analyte n Control type -- n based on number of analytes used within experiment
- Analyte n Concentration (nM) -- n based on number of analytes used within experiment
- Analyte n Molecular Weight (Da) -- n based on number of analytes used within experiment
- Regeneration n Solution -- n based on number of regeneration solutions used within experiment
- Regeneration n Plate id -- n based on number of regeneration solutions used within experiment
- Regeneration n Position* -- n based on number of regeneration solutions used within experiment
- Regeneration n Control type -- n based on number of regeneration solutions used within experiment
- Capture n Solution -- n based on number of capture solutions used within experiment
- Capture n Plate id -- n based on number of capture solutions used within experiment
- Capture n Position* -- n based on number of capture solutions used within experiment
- Capture n Control type -- n based on number of capture solutions used within experiment
* To account for cases of multiple measurements per sample (sample files only), these fields will include an index (e.g. [Channel 1], [Channel 2], [Channel 3],...) corresponding to the number of channels.
measurement data file can contain the following columns (if available within the data):
- Device ID
- Model #
- Equipment Serial Number
- Product Manufacturer
- Asm File Identifier
- Data System Instance ID
- File Name
- Unc Path
- ASM Converter Name
- ASM Converter Version
- Software Name
- Software Version
- Analyst
- Measurement Time
- Analytical Method ID
- Number Of Cycles
- Data Collection Rate (Hz)
- Running Buffer
- Measurement End Time
- Sample ID
- Run
- Cycle
- Channel
- Analyte 1 Solution
- Analyte 1 Plate Id
- Analyte 1 Position
- Analyte 1 Control Type
- Regeneration 1 Solution
- Regeneration 1 Plate Id
- Regeneration 1 Position
- Regeneration 1 Control Type
- Capture 1 Solution
- Capture 1 Plate Id
- Capture 1 Position
- Capture 1 Control Type
- Sensor Chip Identifier
- Sensor Chip Type
- Product Manufacturer [Sensor Chip]
- Lot Number
- Measurement ID
- Detection Type
- Method Name
- Binding On Rate Measurement Datum (Kon) (M-1s-1)
- Binding Off Rate Measurement Datum (Koff) (s^-1)
- Equilibrium Dissociation Constant (Kd) (M)
- Maximum Binding Capacity (Rmax) (RU)
- Blank Subtraction
- Molecular Weight Adjustment
- Capture/Ligand Adjustment
- Adjustment For Controls
- Curve Analysis
- Device Type
- Sample Temperature Setting (degC)
- Flow Cell Identifier*
- Analyte 1 Contact Time (s)
- Analyte 1 Dissociation Time (s)
- Analyte 1 Flow Rate (µL/min)
- Regeneration 1 Contact Time (s)
- Regeneration 1 Flow Rate (µL/min)
- Included
- Sensorgram Type*
- Level (RU)*
- Analyte 1 Concentration (nM)
- Analyte 1 Molecular Weight (Da)
- Kinetics Chi Squared (RU^2)
- Tc
- Kinetics Model
* To account for cases of multiple flow cells per measurement (measurement files only), these fields will include an index (e.g. [Flow Cell 1], [Flow Cell 2], [Flow Cell 3],...) corresponding to the number of flow cells.
report point data file can contain the following columns (if available within the data):
- Measurement Time
- Analytical Method ID
- Number Of Cycles
- Data Collection Rate (Hz)
- Running Buffer
- Measurement End Time
- Device Type
- Sample Temperature Setting (degC)
- Flow Cell Identifier [Flow Cell 1]
- Flow Cell Identifier [Flow Cell 2]
- Flow Cell Identifier [Flow Cell 2-1]
- Analyte 1 Contact Time (s)
- Analyte 1 Dissociation Time (s)
- Analyte 1 Flow Rate (µL/min)
- Regeneration 1 Contact Time (s)
- Regeneration 1 Flow Rate (µL/min)
- Included
- Sensorgram Type [Flow Cell 1]
- Sensorgram Type [Flow Cell 2]
- Sensorgram Type [Flow Cell 2-1]
- Level (RU) [Flow Cell 1]
- Level (RU) [Flow Cell 2]
- Measurement ID
- Detection Type
- Method Name
- Sample ID
- Run
- Cycle
- Channel
- Analyte 1 Solution
- Analyte 1 Plate Id
- Analyte 1 Position
- Analyte 1 Control Type
- Regeneration 1 Solution
- Regeneration 1 Plate Id
- Regeneration 1 Position
- Regeneration 1 Control Type
- Capture 1 Solution
- Capture 1 Plate Id
- Capture 1 Position
- Capture 1 Control Type
- Absolute Resonance (RU)
- Report Point Identifier
- Identifier Role
- Relative Resonance (RU)
- Time Setting (s)
- Step Name
- Step Purpose
- Window (s)
- Baseline
- LRSD
- Slope (RU/s)
- Standard Deviation
- Analyte 1 Concentration (nM)
-
Analyte 1 Molecular Weight (Da)
Cytiva Biacore Insight Connector System Requirements
| Item | Specification |
| Cytiva Biacore Insight | v5.0.18.22102*, v6.0.7.1750* |
| Operating System |
64-bit Microsoft Windows 10 Enterprise or Professional 64-bit Microsoft Windows 11 Enterprise or Professional |
| Memory |
At least 16 GB internal memory At least 200 GB free hard disk space |
| Processor | CPU with at least four cores, 2 GHz or faster |
| Gateway | Benchling Gateway installed on PC, able to communicate on port 443 |
Revision History
2025-07-31
Initial Version