Third-party software licenses are part of the technical and procurement picture for industrial automation systems. Software and firmware may incorporate components maintained by external developers, including open-source libraries. Knowing which components are included, which products use them, and which license terms apply helps engineering, integration, and compliance teams make informed decisions about software use and redistribution.
A third-party software notice published by Physik Instrumente (PI) illustrates how this information can be organized. Issued in December 2021, it identifies software components, versions, license types, copyright holders, and the PI software or firmware in which components are incorporated. It also provides license texts or notes. The notice is specific to the products and software it lists; it should not be treated as a general statement about every industrial control product or as confirmation of the licensing status of later releases.
What a third-party software inventory tells you
A component inventory connects software dependencies to the products and applications that use them. In the PI notice, examples include Expat XML Parser and Firebird components used in PI C++ libraries or software tools, and libusb listed for certain C-884, C-885, and C-886 firmware. Other entries include libcurl in PI Firmware Manager and OpenSSL in the same application. The inventory also names the component version and its license, where specified.
For an automation team, this detail is more useful than a bare list of library names. Product mapping can help identify whether a license question applies to a particular controller firmware, programming library, or engineering application. Version information can also help distinguish the listed component from another version that may be present in a different software release.
Such records support practical activities including:
- Software procurement: Review component and license information as part of vendor and product documentation.
- System integration: Track dependencies in the applications and libraries used to communicate with or configure automation equipment.
- Change management: Check the relevant product documentation when evaluating a software or firmware update.
- Distribution planning: Identify license conditions that may matter when software is redistributed or combined with other code.
Why license terms matter in automation projects
Open-source and third-party licenses are not interchangeable. The inventory names, among others, MIT, BSD 3-Clause, LGPL, Apache 2.0, MPL 1.1, and project-specific licenses. Their terms can differ, including requirements related to preserving notices, providing license text, describing modifications, or making source code available in particular circumstances.
For example, the BSD 3-Clause terms reproduced in the notice address retention of copyright and license information in source distributions and reproduction of notices for binary distributions. The Apache 2.0 text describes conditions for redistribution and notices, among other provisions. These examples are not a substitute for checking the specific license that applies to a component and the way it is being used. The fact that a component is open source does not mean every use, modification, or redistribution has identical requirements.
Teams should also distinguish the license for a third-party component from the terms governing a vendor’s overall software package. A license may apply to a component incorporated in a larger application without replacing the agreements or conditions that apply to the complete vendor product. Where an integration involves modifying or redistributing software, legal or software-compliance review may be appropriate.
Source-code access: check the applicable terms
The PI notice describes a process for requests where an applicable open-source license requires source code and/or object code for software or parts of it to be provided. It says PI will make the relevant code available to the customer within a reasonable period following a legitimate email request to [email protected], for a charge limited to the expenses of fulfilling the request. It also states that PI may reject requests made after the third anniversary of the software delivery date.
The notice further directs readers to links in its component table or to the same support address when a particular source code is delivered in executable form and must be made available under the applicable license. These details are tied to the notice and its stated process. Customers should consult the relevant documentation and license terms for the software they have received rather than assume the same process or deadlines apply to other products or suppliers.
How engineering teams can use the information
When reviewing a supplier’s software disclosures, organize the information around the actual system and its lifecycle. Start by identifying the exact software or firmware release in use, then match it to the component list. Record component names, versions, license identifiers, and any product mapping provided. If software is being modified, bundled, or redistributed, note that separately and check which obligations are relevant to that activity.
It is also useful to keep the license notice with project records and to revisit it when a product version changes. A notice dated 2021 is a dated disclosure, not a guarantee that an earlier or later release contains the same components. For questions about source availability or the interpretation of license terms, use the supplier’s stated contact route and seek qualified advice where needed.
Conclusion
Third-party software disclosures help industrial automation teams understand the dependencies behind vendor software and firmware. Component inventories, version details, product mappings, and license texts give engineers and decision-makers a basis for checking integration and redistribution plans. The practical next step is to match the notice to the exact software release, review the applicable license conditions, and retain that information as part of the system’s technical and compliance records.