Cytiva, Biacore T200 Evaluation Configuration Guide

Purpose 

To provide details about the necessary steps to implement the Cytiva, Biacore T200 Evaluation connector for use with the Benchling Connect platform.

Introduction

The Cytiva, Biacore T200 Evaluation connector is a component used in the context of the Benchling Connect platform to parse data from Cytiva Biacore T200 SPR System 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 T200 Evaluation connector is a ‘file-based’ based connector, meaning that it processes .bme exports generated by the Cytiva, Biacore T200 Evaluation 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 T200 Evaluation connector for use with the Benchling platform, there are several steps that need to be followed across both the Cytiva, Biacore T200 Evaluation software and Benchling user interfaces. 

This guide details the steps to be taken in both applications in order to configure the integration. 

Steps within Cytiva Biacore T200 Evaluation Software

From within Cytiva Biacore T200 Evaluation, a user must:

1. Configure a .bme export compatible with the Benchling Connect, Cytiva Biacore T200 Evaluation connector.
2. Execute the export of that file from their Cytiva Biacore T200 Evaluation session.
3. Ensure that the file is placed with the watched directory.

Generating .bme Biacore T200 Evaluation file

Following execution of an analysis within the software utilizing either an evaluation method/manually, users should:

- Open the File menu from the Menu and toolbar

- Select Save As...

- Save the .bme results file with their appropriate experiment name and select the file saved in the watched file directory configured via their Benchling Connection

Current Limitations:

- The Cytiva Biacore T200 Evaluation connector has to-date only been tested with example data from the Kinetics/Affinity evaluation method. Additional evaluation method may be compatible with the connector but must be verified by the user.

- The Cytiva Biacore T200 Evaluation connector only is compatible with the .bme file extension for processed data capture from SPR experiments, support from the Biacore T200 Control and/or Biacore Insight Software can be found in Benchling's Connector guides for Biacore T200 Control and Biacore Insight.

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 representative and let them know you would like to see a specific feature(s) added to the connector! 

Steps within Benchling

From within Benchling, a user must:

1. Enable the Cytiva Biacore T200 Evaluation connector on the tenant [internal admin console]
    
2. Configure a Cytiva Biacore T200 Evaluation Connection
    
3. Create a Result schema to structure the data to be recorded
    
4. Configure a Run schema to accept data from Cytiva Biacore T200 Evaluation 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 T200 Evaluation 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 T200 Evaluation connector uses the Allotrope Simple Model (ASM) to structure the information parsed from the Cytiva Biacore T200 Evaluation file export. The data is handled in a two step process; step one from Cytiva Biacore T200 Evaluation 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:

https://github.com/Benchling-Open-Source/allotropy/blob/main/src/allotropy/allotrope/schemas/adm/binding-affinity-analyzer/WD/2024/12/binding-affinity-analyzer.schema.json 

The connector then converts the ASM to one of:

sample file .csv - structured such that each row of the file represents a sample

measurement file .csv - structured such that each row of the file represents a measurements

datacube file .csv - structured such that each row of the file represents a datacube data point, specifically for sensorgram data

sample file .csv files can contain the following columns (if available within the data):

• Device ID
• Model #
• Product Manufacturer
• ASM File Identifier
• ASM Converter Name
• ASM Converter Version
• Data System Instance ID
• File Name
• UNC Path
• Software Name
• Software Version
• Analyst
• Measurement Time
• Experiment Type
• Experimental Data ID
• Sample ID
• Well Plate ID
• Sensor Chip Identifier
• Sensor Chip Type
• Product Manufacturer [Sensor Chip]
• Ifc Identifier
• Last Modified Time
• Last Use Time
• First Dock Date
• Measurement ID*
• Detection Type
• Method Name
• Ligand Identifier*
• Data Collection Rate (Hz)
• Device Type
• Flow Cell Identifier*
• Flow Rate (µL/min)*
• Flow Path*
• Dilution Factor (%)*
• Contact Time (s)*

* To account for cases of multiple measurements per sample (sample & sample-separate-unit-column files only), these fields will include an index 
(e.g. _1, _2, _3,...) corresponding to the number of measurement.

measurement file .csv files can contain the following columns (if available within the data):

• Device ID
• Model #
• Product Manufacturer
• Asm File Identifier
• Data System Instance ID
• File Name
• Unc Path
• ASM Converter Name
• ASM Converter Version
• Software Name
• Software Version
• Account Identifier
• Operating System Type
• Operating System Version
• Analyst
• Measurement Time
• Data Collection Rate (Hz)
• Templateextension
• Evaluationmethodisoptional
• Typename
• Allowpublish
• Experimental Data ID
• Sample ID
• Well Plate ID
• Rack2
• Sensor Chip Identifier
• Sensor Chip Type
• Product Manufacturer [Sensor Chip]
• Lot Number
• Display Name
• Ifc
• Ifc Description
• First Dock Date
• Last Use Time
• Last Modified Time
• Number Of Flow Cells
• Number Of Spots
• Measurement ID
• Detection Type
• Ligand Identifier
• Device Type
• Flow Cell Identifier
• Flow Rate (¬µL/min)
• Buffer Volume (mL)
• Detection
• Detectiondual
• Detectionmulti
• Flowcellsingle
• Flowcelldual
• Flowcellmulti
• Maximum Operating Temperature (degC)
• Minimum Operating Temperature (degC)
• Analysis Temperature (degC)
• Prime
• Normalize
• Level (RU)
• 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)
• Kinetics Chi Squared
• Ka Error (M-1s-1)
• Kd Error (s^-1)
• Rmax Error (RU)

datacube file .csv files can contain the following columns (if available within the data):

• Measurement Time
• Data Collection Rate (Hz)
• Templateextension
• Evaluationmethodisoptional
• Typename
• Allowpublish
• Experimental Data ID
• Device Type
• Flow Cell Identifier
• Flow Rate (µL/min)
• Buffer Volume (mL)
• Detection
• Detectiondual
• Detectionmulti
• Flowcellsingle
• Flowcelldual
• Flowcellmulti
• Maximum Operating Temperature (degC)
• Minimum Operating Temperature (degC)
• Analysis Temperature (degC)
• Prime
• Normalize
• Ligand Identifier
• Level (RU)
• Sample ID
• Well Plate ID
• Rack2
• Measurement ID
• Detection Type
• Ligand Identifier
• data cube label
• Elapsed Time (s)
• Resonance (RU)

Cytiva Biacore T200 Evaluation Connector Requirements

* This is the version of Biacore T200 Evaluation with which the connector has been developed and tested. The connector may work with other versions of Biacore T200 Evaluation, but that must be verified by the user.

Revision History

10/20/2025

Initial Version