Frequently Asked Questions

SiLA

What is SiLA?

The SiLA organization promotes open standards to allow integration and exchange of intelligent systems in the lab in a cost effective way. It does this by bringing together industrial and academic lab users with technology providers such as vendors and startups in a collaborative and pre-competitive environment, since 2008.

SiLA’s mission is to establish international standards which create open connectivity in lab automation, to drive lab digitalization to the benefit of all lab users and operators.

SiLA’s vision is to create interoperability, flexibility and resource optimization for laboratory instruments integration and software services by providing standardized communication protocols and content specifications.

What is a SiLA Standard?

The SiLA standards define how information is packaged and communicated from one system to another. Setting the language, structure and data types required for seamless integration between systems, SiLA standards support good laboratory practice and the management, delivery and evaluation of laboratory services. SiLA 2 is recognized as the best established and most commonly used laboratory communication standard in the world.

SiLA 2

What is SiLA 2?

SiLA 2 is the new Standard in Lab Automation. It changes the future of lab technology providing outstanding and elegant concepts.

The SiLA Organization provides with the SiLA 2 Standard a framework for the exchange, integration, sharing and retrieval of electronic laboratory information.

The SiLA 2 specification specifies interoperability schemes that allow laboratory devices and services to communicate with each other. It is based on open communication protocols that are well established and defines a thin domain specific layer on top of these, consisting of common concepts and a vocabulary / taxonomy.

For an overview of SiLA 2 visit this page.

If you are interested in supporting SiLA 2, visit this page.

Why SiLA 2?

SiLA 2 is a complete redesign of a previously released standard from 2016. It embraces a modern, service oriented architecture (“micro services”). Using the SiLA 2 Feature Definition Language to describe services, SiLA 2 is a configurable and open standard which allows choosing based on functionality. Thanks to its self-describing functionality, SiLA 2 allows true plug & play. This allows users to break out of closed ecosystems. Reuse, change, adapt and configure already existing systems automatically. With its lean and intuitive specification, SiLA 2 is easily accessible for both end users and developers of new and cloud-enabled services.

SiLA 1.x and SiLA 2 are both addressing the same problems in lab automation. However, their solutions differ greatly. SiLA 1.x was based on XML SOAP, now a dated technology choice. SiLA 2, on the other hand, is based on a carefully selected handful of well-established web technologies and concepts, including HTTP/2 and “REST-like” communication paradigms.

While SiLA 1.x focused on devices and device classes, SiLA 2 focuses on systems offering services.

Where can I find more information about SiLA 2?

Apart from our web resources, the SiLA Consortium offers the SiLA 2 Specification:

Also, you can have a look at our GitLab Code Repository or in our download section.

Visit one of SiLA’s events or check out the training SiLA offers.

SiLA 1.x vs SiLA 2?

SiLA 1.x and SiLA 2 are both tackling the same problems in lab automation. Their solutions however differ greatly.

SiLA 1.x was based on XML Soap, an unpopular technology choice nowadays. SiLA 2 on the other hand is based on a handful of promising new technologies and concepts, including HTTP/2 and “REST-like” communication paradigms.

While SiLA 1.x focused on device types, SiLA 2 embraced a completely service oriented structure. Using Features, SiLA 2 is a configurable and open standard which enables users to choose devices independently of vendors and based on functionality.

Thanks to its self-propagating functionality, SiLA 2 allows true plug & play. Break out of closed ecosystems. Reuse, change, adapt and configure already existing systems automatically.

Is SiLA 2 compatible with SiLA 1.x?

No. SiLA 2 is not directly backwards compatible with SiLA 1.x. This has been a very specific design decision of the core working group. The working group decided early in the process of the SiLA 2 development not to include backwards compatibility in order not to sacrifice proper design. However, many learnings from SiLA 1.x made it into SiLA 2.

How is security implemented in SiLA 2?

Cyber security is an increasingly important question but is hard to answer as it’s based on risk assessment and risk tolerance.

The definition of the SiLA 2 standard is secure: The SiLA 2 Specification Part A requires that all communication between a SiLA Client and a SiLA Server must be encrypted. Additionally, SiLA recommends the use of Authentication and Authorization Features. The encryption is realised through Transport Level Security (TLS), as specified in SiLA 2 Specification Part B.

Implementation and operation depends on many factors which are outside of SiLA’s control.

What do you see as the future of lab automation, and how do you believe standards like SiLA 2 will shape that future?

The future of lab automation lies in leveraging AI and standards like SiLA 2 to enable closed-loop laboratories, where data analysis, decision-making, and planning are seamlessly integrated with control and execution. AI is rapidly advancing in both data processing and laboratory robotics, such as pipetting robots like Goodbot (full disclosure: I am an investor) and automation solutions from Yaskawa, ABB, and others. Standards like SiLA 2 are critical in ensuring interoperability between devices, driving innovation, and unlocking the full potential of AI-powered automation in research and development.

https://arxiv.org/abs/2501.06847

https://www.labo.de/dosier-und-vakuumtechnik/pipettierroboter-goodbot-fuer-forschungslabore.htm

https://www.yaskawa.eu.com/application/case/robot-based-laboratory-automation-at-celisca_u20445

https://www.kevinrobot.com/

https://mrk-blog.de/en/bahead-cobot-automatisiert-das-labor-investor-willkommen/

How are vendors and industry stakeholders collaborating to ensure the interoperability and continued evolution of SiLA 2?

SiLA serves as both a standard-setting organization and a business network, fostering collaborations across the industry. Partnerships such as those between Roche and Biosero, Unitelabs and Labforward, or Unilever and AST showcase the strength of this network in driving innovation and interoperability.

SiLA aligns the interests of five key stakeholder groups: users, hardware and software vendors, integrators, startups, and academics. Core members play a vital role in shaping SiLA 2’s evolution by establishing working groups to address specific needs. For instance, Takeda has led efforts on robotics, while Unilever has focused on cybersecurity.

To ensure interoperability, SiLA facilitates interaction through hackathons and proof-of-concept projects. These initiatives enable stakeholders to collaboratively test and refine implementations of SiLA 2. In response to user demands, SiLA has also developed tools like the Cloud Connector and the Universal SiLA Client, ensuring the standard remains adaptive to the needs of modern laboratories.

Other Standards

How does SiLA 2 compare to REST?

REST is an acronym for Representational State Transfer, which is based on the HTTP protocol and corresponds to a paradigm and not to a defined standard. This implies that two semantically identical REST-Services do not have per se an identical representation. This results in the need for individual implementation and adoption of specific REST-APIs.

SiLA is based on HTTP/2 and Protocol Buffers for communication. The Feature Definition Language allows semantical identical services to have the identical representation. The SiLA 2 Standard specifies security models, data compression, feature and service discovery.

How does SiLA 2 compare to OPC?

OPC Unified Architecture (OPC UA) is a machine-to-machine communication protocol for industrial automation developed by the OPC Foundation.

While SiLA has been explicitly designed with the lab automation needs in mind, OPC-UA has been designed for industrial automation. OPC UA is very well suited to monitor a plant with thousands of sensors delivering simple data values, and where large and expensive assets have to be protected. However, it would be difficult to orchestrate a workflow in a lab, e.g. control and handle the complex data of a mass spectrometer with OPC. SiLA, however, has been specifically designed for such applications. SiLA 2 features and commands also tend to be at a higher level of abstraction and are more verbose than OPC-UA, which makes SiLA 2 easier to understand and simpler to implement.

In addition, OPC-UA’s complex specifications have led to some incomplete and heterogeneous implementations, which makes it hard to develop generic applications independent from the specific OPC-UA implementation. This heterogeneity of implementations, requires custom applications support appropriate for large manufacturing systems but limiting the seamless interoperability of different systems – Both obstacles SiLA 2 overcomes with its lean and intuitive specification.

How does SiLA 2 compare to AnIML?

The Analytical Information Markup Language (AnIML) is the emerging XML-based standard for analytical chemistry and biological data developed under governance from ASTM. AnIML is a data standard, while SiLA 2 is a communication standard. Both standards enable the digitalized lab.

In general, the SiLA 2 standard recommends using existing, open data formats. For example, it would be useless to invent a new image format to transport an image over SiLA 2. However, one of the existing formats (like PNG, JPEG, etc) would be used.

Likewise, for analytical or process data in the lab, SiLA 2 recommends referring to existing open and free-to-use standards like AnIML.

How does SiLA 2 compare to Allotrope?

The Allotrope Foundation is not a standardization organization as such. It is an international consortium of pharmaceutical, biopharmaceutical, and other scientific research-intensive industries. Its first initiative is the development of the Allotrope Framework for analytical data, consisting of a standard data format, class libraries for interfacing with applications, and semantic capabilities to support standardized, structured metadata.

As such, it is comparable to AnIML, with the difference of being not open and not free-to-use.

What is the difference between ROS and SiLA 2?

The Robot Operating System (ROS) is a collection of software frameworks for robot software development. Although there is some overlap between ROS and SiLA, there are quite some differences (e.g. network topology and communication protocols). ROS is not a standard, but rather a philosophy of how to develop robotic applications with open-source in mind.

Whereas SiLA 2 standardizes “what” functionality a device offers (i.e. the SiLA 2 Features offered) and how a client can access it, ROS focuses on “how” the functionality is implemented.

How does SiLA 2 copmpare to Module Type Package (MTP)?

MTP is used in process automation of production processes to describe modules. It can be compared to a SiLA 2 Feature, however, its focus is in industrial automation and not on life science lab’s connectivity and data needs. In a nutshell, an MTP includes the following information: Description of the data objects, Description of the control image, and in the future: Description of services, etc., which allows industrial integrators a faster way to solve challenges in adaptable production processes.

GxP

Is SiLA ready to be used in regulated (GxP) environments?

Of course. The use of a standard like SiLA 2 even simplifies the implementation of data integrity requirements and reduces the validation efforts.

What are the advantages of using SiLA in a regulated environment (GxP) for instrument connection and system integration?

  • SiLA is superior to sharing plain files (which is a compliance risk according to data integrity best practices)
  • SiLA reduces implementation effort as a certain interface needs only to be implemented once e.g. on the LIMS side
  • SiLA enables type based qualification of interfaces to save validation effort
  • SiLA Feature Definitions replace functional specifications (FS, FDS) in a structured and well defined way. Specifying Features by the Feature Definition Language (FDL) both saves effort and reduces ambiguities, as it actually results in a complete, unambiguous and even machine readable functional specification. The FS/DS of the interface itself is completely specified by a combination of the SiLA specification Part A, B and the FDL.
  • SiLA also ensures the availability of meta information, when it comes to managing parameters and results of scientific experiments, quality control, etc. In combination with AnIML audit trail and even digital signatures are covered as well.

How does SiLA 2 impact the operational efficiency and scalability of laboratories, particularly in the context of integration with other industry standards, including MTP (Module Type Package)?

Impact on Operational Efficiency:

  • Modular Integration: SiLA 2’s microservices architecture allows laboratories to integrate and control various instruments and devices in a standardized manner. This reduces the need for custom integration efforts, thereby enhancing operational efficiency.
  • Data Consistency and Integrity: By providing a standardized way to communicate and exchange data between devices, SiLA 2 ensures that data is consistent and readily available, which reduces errors and manual intervention.
  • Automated Workflows: SiLA 2 facilitates the automation of laboratory workflows, from sample handling to data analysis, which can drastically reduce turnaround times and human error.

 

Scalability:

  • Flexible Integration: SiLA 2’s modular approach allows labs to easily add new devices or scale operations by integrating additional systems without reworking the entire infrastructure.
  • Interoperability with MTP: The Module Type Package (MTP) standard, which is used in modular production, can complement SiLA 2 in scenarios where laboratory processes need to scale up from R&D to manufacturing. MTP provides standardized interfaces for process modules, making it easier to scale laboratory automation systems into production environments.

What are the key factors driving the decision to choose SiLA 2 over other standards in laboratory automation, and how does MTP play into this decision when considering modular automation.

Key Factors:

  • Interoperability: One of the primary reasons to choose SiLA 2 is its ability to facilitate interoperability between a wide range of laboratory devices from different manufacturers. This is crucial in R&D environments where flexibility is key.
  • Ease of Integration: SiLA 2’s reliance on web technologies (RESTful APIs, JSON) makes it easier for IT teams to integrate and manage compared to more complex industrial standards like OPC UA.
  • Ecosystem Support: SiLA 2 has a strong following in the laboratory space, which means better support from vendors and a growing ecosystem of compatible devices.

Role of MTP:

  • Modular Automation: MTP enables modular and flexible automation, which is particularly beneficial when transitioning from R&D to production. When combined with SiLA 2, MTP can help laboratories scale processes developed in R&D into fully automated manufacturing systems.
  • Decision-Making: Laboratories may choose SiLA 2 when the focus is on R&D and experimental flexibility. MTP becomes relevant when considering how these processes will eventually need to scale into modular production environments.

How does the adoption of SiLA 2 affect the cost of laboratory automation, both in terms of initial implementation and ongoing maintenance?

Initial Implementation Costs:

  • Reduced Integration Costs: SiLA 2 can lower initial costs by reducing the need for custom coding and integration. The use of standardized protocols simplifies the setup and connection of devices.
  • Training and Setup: While SiLA 2 is relatively easy to implement, there are still costs associated with training personnel and setting up the system, especially if the lab is transitioning from a more manual process.

Ongoing Maintenance Costs:

  • Lower Maintenance: Once implemented, SiLA 2 can reduce ongoing maintenance costs by simplifying the process of adding or updating devices and systems.
  • Vendor Support: The growing SiLA 2 ecosystem means that laboratories can benefit from better vendor support, which can further reduce maintenance costs.

What are the biggest technical and non-technical challenges labs face when adopting SiLA 2, and how can these challenges be mitigated?

Technical Challenges:

  • Compatibility with Legacy Systems: Integrating SiLA 2 with older, non-compliant systems can be challenging. This can be mitigated by using middleware or gateways that translate between SiLA 2 and older protocols.
  • Scalability Issues: While SiLA 2 is designed for scalability, ensuring that all parts of the system can scale in unison (e.g., network infrastructure, data storage) requires careful planning.

Non-Technical Challenges:

  • Change Management: Transitioning to a new standard requires changes in workflows and retraining staff, which can meet resistance. Effective change management strategies, including clear communication and phased rollouts, can mitigate this.
  • Vendor Lock-in Concerns: Although SiLA 2 promotes interoperability, laboratories must ensure they are not locked into specific vendors or products that could limit future flexibility.

How does SiLA 2 handle the scalability, and flexibility needs of modern laboratories, especially those transitioning from simple to complex systems? (Regarding scale up from a process in R&D to manufacturing and increasing organizational size when there are suddenly 10x more users/devices)

organizational size when there are suddenly 10x more users/devices)

Scalability:

  • From R&D to Manufacturing: SiLA 2 allows for the seamless scaling of processes from R&D environments to more complex manufacturing setups. The modular nature of SiLA 2 means that components can be individually scaled without overhauling the entire system.
  • Handling Increased Users/Devices: SiLA 2’s microservices architecture can handle an increase in the number of users or devices by distributing workloads across multiple services. Additionally, its compatibility with cloud-based services can help manage this scalability by leveraging cloud computing resources.

Flexibility:

  • Adapting to New Technologies: As new laboratory technologies emerge, SiLA 2’s open, modular architecture allows these technologies to be integrated with minimal disruption.
  • Customizability: Laboratories can customize their automation workflows within the SiLA 2 framework, making it easier to adapt to changing research needs or regulatory requirements.

Can SiLA share any real-world examples or case studies where SiLA 2 was successfully implemented? What were the key factors that contributed to their success?

Example 1: Pharmaceutical Research Lab:

  • Context: A large pharmaceutical company implemented SiLA 2 across its R&D labs to standardize device communication and automate workflows.
  • Success Factors: The key to success was the modular approach of SiLA 2, which allowed the lab to integrate devices from multiple vendors. This streamlined their drug discovery process, significantly reducing the time required for data collection and analysis.

Example 2: Academic Research Facility:

  • Context: An academic research institution adopted SiLA 2 to improve the interoperability of its diverse range of laboratory equipment.
  • Success Factors: The flexibility and ease of integration provided by SiLA 2 were critical. Researchers could easily connect and control devices, allowing them to focus on experiments rather than troubleshooting technical issues. This led to higher productivity and more consistent results.

Example 3: Biotechnology Startup:

  • Context: A biotech startup used SiLA 2 to automate its laboratory workflows, enabling rapid scaling as the company grew.

Success Factors: The startup benefited from the scalable architecture of SiLA 2, which allowed them to quickly add new instruments and automate new processes without significant downtime or additional

Get Involved

How do I get involved?

We provide different ways to get involved with SiLA:

Why should I get involved?

  • SiLA is superior to sharing plain files (which is a compliance risk according to data integrity best practices)
  • SiLA reduces implementation effort as a certain interface needs only to be implemented once e.g. on the LIMS side
  • SiLA enables type based qualification of interfaces to save validation effort
  • SiLA Feature Definitions replace functional specifications (FS, FDS) in a structured and well defined way. Specifying Features by the Feature Definition Language (FDL) both saves effort and reduces ambiguities, as it actually results in a complete, unambiguous and even machine readable functional specification. The FS/DS of the interface itself is completely specified by a combination of the SiLA specification Part A, B and the FDL.
  • SiLA also ensures the availability of meta information, when it comes to managing parameters and results of scientific experiments, quality control, etc. In combination with AnIML audit trail and even digital signatures are covered as well.

How can I help with the SiLA Standard?

Simply contact us or see what you can do on our GitLab repository – We are looking forward to working with you! Also check out the SiLA 2 wiki on GitLab.

Membership

How do I become a SiLA Member?

How do I become a SiLA member?

There exist different forms of SiLA Memberships:

  • Personal Member (Free)
  • Observing Member (NEW)
  • Academic Contributing Member
  • Academic Member
  • Start-up Members
  • Supporting Member
  • Core Member

If you want to become a Personal Member, all there is to do is sign up here.

You can also find more detailed information here.

A membership application form is available here.

Why should I become a SiLA Member?

SiLA currently counts over 1700 members from all over the world that contribute to the success of SiLA.

Members help shape and guide SiLA 2’s development. They are paramount to its existence and continued amelioration.

To find out more see Membership or just register directly.

Will Membership increase my sales?

Let’s put this question into a different context: Will buying a gym membership improve your fitness?

Clearly, just paying a membership doesn’t translate into results. However, using your membership typically does! Just like a gym membership gives you access to equipment to help get you in shape, SiLA membership grants Members access to promotional tools to increase company visibility.

These tools include free Member advertising wherever SiLA advertises – tradeshows, press releases, websites, newsletters, and conferences.

Use SiLA as part of your company’s marketing and promotional plan. The more you use your SiLA membership, the more visibility your company will get which will translate into more sales opportunities for your products.

Where does the Membership go?

Nearly half of SiLA membership fees are used to promote SiLA standards and SiLA compliant products in publications, tradeshows and conferences. Through these activities, SiLA increases the adoption and popularity of the standard and brings new business opportunities to our members.

The other half is split more or less equally between our Operation fund, Administration fund and direct work into the standard. This ensures the persistent existence of SiLA as an organization.

Certification

What does certification mean regarding SiLA 2?

There will be two types of certification processes to guarantee stable and well functioning SiLA Servers, Features and SiLA Clients: Self-Certification and Accredited Certification.

See Certification for more information.

Any more questions?

Don’t hesitate!