CACrown ArchivesHistory · sources · collections
Menu
Research dossier · Science & Nature

OSADL

Association concerned with developing open source software for industrial products

Specimen drawers, botanical folios and brass scientific instruments under study light
Science and natureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionJun 21, 2026
Entity authorityQ1502951
Source-derived summary

The Open Source Automation Development Lab eG (OSADL) is a German organization intended to promote and coordinate the development of open source software for the machine, machine tool, and automation industry. As of March 2013, it has more than 40 member companies from around the world, including machine manufacturers, manufacturers of automation hardware and software, semiconductor companies, user associations and open source software service providers. Membership fees are used for the most part to fund development of the software.

OSADL was founded on December 8, 2005. It was assigned the cooperative register number 440085 at the Stuttgart, Germany, District Court in August 2006.

OSADL is a member of OPC Foundation which governs the OPC UA industrial automation standard, in which the lab is also involved.

Preamble of the articles of incorporation of the cooperative

"The automation industry and its suppliers are profiting greatly from Open Source operating systems such as Linux since they guarantee long production cycles, rapid troubleshooting and the independence of individual software manufacturers. However, this branch requires specific expansions of the operating system such as real-time capabilities, the compatibility with these expansions must be certifiable, and standardized software interfaces must be available. The development of these requirements is the goal of the Open Source Automation Development Lab (OSADL)."

Working groups and projects

Over time a number of working groups has been established and projects participated in, this lists some of the more prominent:

Ingo Molnár's and Thomas Gleixner's Linux Real-time Preempt Patches (a.k.a. PREEMPT_RT)

Kernel-based Virtual Machine and Real-time Preempt Patches

Critical Safety Linux

Universal industrial I/O framework

Upstream submission of kernel components to Mainline Linux

Conformance tests of board support packages

Tools and libraries to facilitate the migration to Linux

Quality assurance of the Linux kernel and its real-time capabilities in a "QA Farm"

License Compliance Audit to help companies follow the obligations of Open Source licenses

Adding TSN and publish/subscribe capabilities to open62541 (implements OPC UA industrial automation)

Feedback

The relevance of the Linux operating system for embedded systems and OSADL's role to foster its real-time capabilities are recognized.

Editorial summary

The public source identifies “OSADL” as association concerned with developing open source software for industrial products. This brief keeps that definition visible, then builds a research path around OSADL, Association and concerned.

Editorial reviewUseful for establishing the present vocabulary of the subject while preserving a route back to the evidence on which that vocabulary rests. The current lead gives the account dated anchors—2013, 2005, 2006—that can be checked directly. The linked authority record independently contributes the date 2005-12-08. Its value is orientation rather than verdict, with OSADL, Association and concerned providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “OSADL”, the useful work is to connect “association concerned with developing open source software for industrial products” to the records capable of establishing context and consequence.

Evidence profile

Stable identifiers, scientific names and standards terminology offer the best bridge between this overview and specialist evidence. The source revision retrieved here is dated Jun 21, 2026. The linked authority identifier is Q1502951. Authority coordinates are 49.423, 8.675. 1 of 3 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2013, 2005 and 2006.

Critical limits

Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.

Best used for
  • Current terminology
  • Classification context
  • Finding cited technical literature
Verify next

Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.

Three-step research path

  1. Establish the record: confirm the title “OSADL”, its source revision and the description used here.
  2. Expand the search: follow OSADL primary sources, OSADL archive and OSADL research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “OSADL”?
  2. Has classification or technical consensus changed since the cited source?
  3. Which observation, specimen, dataset or publication supports the account?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from OSADL” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.