// Knowledge · FAIR data
Lab data in open formats, built for FAIR
FAIR means Findable, Accessible, Interoperable and Reusable. FAIR data is one of the founding ideas behind our products. Your data arrives in open formats that your own tools can read, now and later.
// Overview
What FAIR data means for your lab
Wilkinson and colleagues published the FAIR Guiding Principles in 2016 in the journal Scientific Data. The GO FAIR initiative helps research communities put them into practice.
The principles describe 15 properties of data and metadata. Metadata is the data about your data: the sample, the method, the instrument and the time. The focus is on machines. Software should find, read and combine your data with as little human help as possible.
FAIR describes how data is managed, and it fits open and restricted data alike. Your measurements can be FAIR and still be shared only inside your organisation.
In a lab, FAIR starts at the instrument. A value becomes useful when its context travels with it: which sample, which method, which instrument, and when. Context captured at the source is complete and consistent, and it saves your team the typing later.
What we deliver: our Gateways capture each measurement at the instrument, with a Gateway timestamp and the context your instrument provides, in open standards. Every principle below builds on that.
Source: Wilkinson, M. D. et al. (2016). The FAIR Guiding Principles for scientific data management and stewardship. Scientific Data 3, 160018. doi.org/10.1038/sdata.2016.18
// FAIR principles
Four principles, applied to lab data
The original paper numbers the principles from F1 to R1.3. Here is what each one asks for, what it means at the bench, and what our products deliver.
Findable
Your data can be found again
The principle. Data and metadata get a globally unique, persistent identifier (F1). Rich metadata describes the data (F2) and names the identifier of the data it describes (F3). Both are registered or indexed in a searchable resource (F4).
At the bench. Each run carries an ID and searchable fields: sample, method, instrument and time. Your LIMS, ELN or repository registers the record, so a colleague finds it by sample ID years later.
What we deliver. The Gateway timestamps every measurement at the source. Every connector describes the instrument and its results in a LADS model. Data Suite delivers each record with its metadata to the system that indexes it.
Accessible
Your systems can retrieve it
The principle. Data and metadata can be retrieved by their identifier over a standardised protocol (A1). The protocol is open, free and universally implementable (A1.1), with authentication and authorisation where needed (A1.2). The metadata stays accessible after the data itself is removed (A2).
At the bench. Your systems read results through an open protocol, with access rules per user and per system. Accessible means a clear, controlled route to the data, and open access is one option among several.
What we deliver. The Gateway serves your data over OPC UA, an open standard with authentication and encryption built in. It works inside your network, and you decide which systems may read it.
Interoperable
Software can combine it
The principle. Data uses a formal, shared language for knowledge representation (I1) and vocabularies that are FAIR themselves (I2). It holds qualified references to other data (I3), for example from a result to its sample.
At the bench. The same thing gets the same name across vendors and techniques: an absorbance, a mass, a sample role, a unit. Software can then combine results from different instruments directly.
What we deliver. Every connector labels data with terms from the Allotrope Foundation Ontologies (AFO), so it maps cleanly to ASM. LADS gives all your instruments one shared device model.
Reusable
Others can build on it
The principle. Data carries many accurate, relevant attributes (R1), a clear usage licence (R1.1) and detailed provenance (R1.2). It meets the community standards of its domain (R1.3).
At the bench. Someone can repeat or extend your analysis later. They see when it was measured, on which instrument, with which method and settings, and how the result was derived.
What we deliver. The Gateway audit trail records who did what, and when, and signed audit-trail exports let the recipient verify the file. AnIML and ASM carry provenance in the format itself.
// Example
How one measurement becomes FAIR
Take one absorbance reading from a benchtop UV-Vis spectrometer. Here is how it moves from the instrument to a FAIR record, step by step.
- Measure. The spectrometer finishes a run and reports the result in its own protocol.
- Capture. The connector on the Gateway reads the result, and the Gateway adds its own timestamp. That timestamp is independent of the instrument clock.
- Describe. The connector describes the result in the LADS model with AFO terms. It covers the instrument, the values and units, and the sample and method details your instrument or workflow provides. The Gateway audit trail logs every action with identity and time.
- Package. The result is available over OPC UA / LADS at once. Where your archive needs a file, we set up delivery as AnIML or ASM for your project.
- Deliver and register. Data Suite routes the record to your LIMS, ELN or repository. That system assigns the persistent identifier and indexes the metadata for search.
- Reuse. Months later, a colleague finds the run by its sample ID. They open the file in any tool that reads the format, see its provenance and use the data for a new question.
Example record
- Result: absorbance 0.482 at 260 nm
- Sample: S-2026-0412, with a link to the sample record
- Instrument: model and serial number
- Method: method name and version
- Time: Gateway timestamp
- Identifiers: the run ID, plus the persistent ID from your repository
- Terms of use: your licence, for data you share
Fields depend on what your instrument and workflow provide. Your LIMS or ELN adds the rest.
What we deliver: steps 2 to 4 and the delivery in step 5 run on our products. The Gateway and its connector capture and describe, Data Suite delivers, and your target system registers the record. You choose the target systems, and we set up the flow with you.
// Open formats
Method-agnostic and method-specific formats
Open formats for lab data come in two kinds. A method-agnostic format describes every instrument in the same way. A method-specific format defines exactly what the result of one technique contains. Both are open, and they answer different questions.
Method-agnostic: OPC UA / LADS
LADS, the Laboratory and Analytical Device Standard, is an OPC UA companion specification that the OPC Foundation developed with Spectaris and VDMA, published as OPC 30500-1. It is device-type agnostic: one information model describes balances, pH meters, spectrometers and centrifuges alike.
LADS describes a device through its functional units, their functions (sensors, controllers, timers), the programs it runs and the results of each run. A result set records the program template, the parameters, the samples and where the result data is provided. That data can be a file or a set of OPC UA variables.
This makes LADS strong for live data, device status, control and automation, with one interface for every vendor. The detailed content of a result follows the device, so a spectrum and a weighing look different inside.
Method-specific: AnIML and ASM
AnIML, the Analytical Information Markup Language, is an XML format developed under ASTM subcommittee E13.15. A generic core holds the sample, the instrument, the method, the result data and the events related to the data, with optional XML digital signatures. Technique definition documents then set what a file for one technique contains, for example UV-Vis or chromatography.
The Allotrope Simple Model (ASM) from the Allotrope Foundation is a JSON format. Its terms come from the Allotrope Foundation Ontologies (AFO), and its schemas are organised by technique and instrument type.
Both give you one complete, self-describing document per run, with technique-specific fields. That makes them strong for archives, data exchange and analytics across instruments of the same technique.
When to use which
- OPC UA / LADS when your systems need live values, device status or control, or one interface across many instrument types: automation, monitoring, orchestration, or a LIMS that reads results directly.
- AnIML when you archive or exchange complete analytical results as files, want XML with optional digital signatures, or your repository already works with AnIML.
- ASM when your data platform or analytics work in JSON and with the Allotrope ontologies.
What we deliver: every connector delivers OPC UA / LADS by default, with AFO terms on the data. Where you need files, we set up AnIML or ASM delivery for your project. Data Suite has AnIML converters that turn instrument data files into AnIML, and we confirm the formats for your instruments.
// At a glance
Three open formats at a glance
Method-agnostic
OPC UA / LADS
Body: OPC Foundation with Spectaris and VDMA, OPC 30500-1
Model: one device model for every instrument type
Best for: live data, device status, control and automation
With us: the default on every connector
Method-specific
AnIML
Body: ASTM subcommittee E13.15
Encoding: XML, with technique definitions
Best for: complete results as files, archives and exchange
With us: delivery set up per project, and AnIML converters in Data Suite
Method-specific
Allotrope Simple Model (ASM)
Body: Allotrope Foundation
Encoding: JSON, with terms from AFO
Best for: data platforms and analytics
With us: AFO terms on every connector, and ASM delivery set up per project
// FAIR in practice
How we support FAIR data in your lab
Our products are built around FAIR data principles, from the instrument to your target system. For your data, this means:
- Gateway 2 and Gateway Touch: capture each measurement at the instrument, with a Gateway timestamp and an audit trail of who did what, and when.
- Open standards: every connector delivers your data as OPC UA / LADS by default, labelled with AFO terms. Where you need them, we set up AnIML or ASM delivery for your project.
- Data Suite: orchestrates the flow to your LIMS, ELN, data platform or FHIR system, and converts instrument data files to AnIML.
- Standards: AnIML and ASM carry provenance in the format itself.
- AnIML Viewer: open and inspect AnIML files from your lab. Ask us for access.
- Node-RED Packages: our open-source LADS and SiLA 2 nodes on GitHub, npm and the Node-RED library, with working examples.
Want to see it with your own instruments? Book a walkthrough: we build a small device flow with you.
Learn it with us. Our Training & Onboarding enables your team to use OPC UA / LADS, SiLA 2, AnIML and ASM in your own lab.
// FAQ
Answers for labs planning FAIR data
Does FAIR data have to be open data?
FAIR describes how data is found, accessed and reused, and it fits open and restricted data alike. Principle A1.2 allows authentication and authorisation where needed. You decide who can read your data.
Where do the FAIR principles come from?
Wilkinson and colleagues published the FAIR Guiding Principles in 2016 in Scientific Data. They set out 15 principles under the four headings. The GO FAIR initiative supports communities that put them into practice.
Should we use OPC UA / LADS, AnIML or ASM?
Use OPC UA / LADS for live data, device status, control and one interface across instruments. Use AnIML or ASM for the complete result of each run, as a file for your archive or data platform. Many labs use both, and every connector of ours delivers LADS by default.
Do we need new instruments for FAIR data?
You keep the instruments you have. The Gateway connects them over USB, with cables and dongles for RS-232, Ethernet and analogue sensors. The connector translates the vendor protocol into OPC UA / LADS. Our Connector Library covers 80+ instruments. Send us your model, and we’ll confirm its status.
Who assigns the persistent identifier?
Usually the system that keeps the record: your LIMS, ELN or data repository. For published datasets, this is often a DOI. We deliver each record with its Gateway timestamp and the context your instrument and workflow provide, so that system can register and index it.
Can our own tools read the data?
Yes. Your data arrives in open formats that your own tools read and understand, now and later. Any OPC UA client reads LADS, and AnIML and ASM are open, documented formats.
How does FAIR data help analytics and AI?
FAIR is about data that machines can read. Shared terms and full context let analytics and AI tools combine results across instruments. Our MCP Server works on the same LADS device models. The LLM you trust can work with your instrument data, within the actions you allow.
// Read more
More on standards and lab data
Why us
Open standards
Open standards on the device side and on the data side keep your lab data readable in any tool that speaks them: OPC UA / LADS, AnIML and ASM.
Company · Standards
Standards we support
OPC UA / LADS, SiLA 2, AnIML and ASM: what each standard covers and where we use it in our products.
Tools
AnIML Viewer
Open and inspect AnIML files, the open format that keeps measurement data and its provenance together. Ask us for access.
Want open, reusable data from your instruments? Talk to us.
Tell us about your instruments, your LIMS and your lab. We’ll come back with a plan for your setup.