Third-party software licenses are an important part of evaluating industrial software, particularly when a tool incorporates code, libraries, data, or development kits maintained by other organizations. The FME Desktop notices list a broad range of included components, from database and graphics libraries to engineering data formats and geospatial resources. For technical teams, the list is more than a collection of legal acknowledgments: it is a starting point for understanding software provenance and the conditions attached to particular components.
These notices do not describe the product’s operational capabilities or establish how a component is used in a specific deployment. They do, however, show why license review belongs alongside technical evaluation, procurement, and software lifecycle management.
What third-party software license notices tell you
A notice typically identifies a component, its copyright holder, and some or all of the terms that govern its use or distribution. The FME Desktop material names components such as PostgreSQL, OpenSSL, Eigen, GDAL-related plugins, Oracle JDBC drivers, and Autodesk libraries. It also references data sources, grid files, and formats such as IFC and LandXML.
The presence of a name in a notice does not, by itself, explain whether the component is used directly by a particular workflow, what version is active in a current release, or what features depend on it. The supplied notices refer to specific copyright years and versions, so they should be read as documentation for the software release they accompany—not as a current inventory of every later release.
For engineering and IT teams, this distinction matters. A license appendix can inform due diligence, but it is not a substitute for release-specific product documentation, a software bill of materials, or confirmation from the vendor when those details are needed.
License terms vary by component
The notices illustrate that there is no single set of terms covering every included component. Some entries identify permissive conditions, such as retaining copyright notices and disclaimers in redistributed copies. Other components are governed by specific license agreements or use restrictions. The Oracle JDBC notice, for example, describes limits on use and redistribution, while the Autodesk entries include component-specific terms and warranty disclaimers.
Open-source licenses also differ from one another. The notice includes references to the Mozilla Public License for components such as Eigen and libigl, and identifies other libraries with their own redistribution conditions. A label such as “open source” is not enough to determine what a user may do: the applicable license text and the way the software is being used or distributed are relevant.
Some entries concern data or other resources rather than conventional software libraries. The City of Vancouver data is identified as being under an open-government license, while certain coordinate transformation grids carry Creative Commons attribution terms. This makes it important to review the specific item involved instead of assuming that one license category applies to the whole product.
Practical review points for industrial teams
When assessing industrial software for an engineering environment, procurement and technical stakeholders can use component notices to structure a focused review. Useful questions include:
- Which release does the notice cover? Match the license information to the version being evaluated or deployed.
- Will the software be redistributed? Embedding or distributing software in a larger solution may raise different requirements from using it internally.
- Are attribution or notice requirements relevant? Some terms require copyright notices, license text, or acknowledgments to accompany redistributed copies or documentation.
- Are modifications involved? Certain licenses specify conditions for distributing modified components or derived works.
- Are there separately licensed drivers, data, or SDKs? Review these entries on their own terms rather than treating them as interchangeable with general-purpose libraries.
These questions help teams identify where further review may be needed. They are not a determination of whether a particular deployment is compliant; that depends on the applicable terms and circumstances.
Build license review into software governance
For system integrators and plant organizations, license information is most useful when it is handled as part of a repeatable governance process. Keep the notices supplied with software, associate them with the relevant product release, and make them accessible to the people responsible for procurement, deployment, security, and legal review. Where a project includes redistribution, custom packaging, or modifications, flag that context early so the relevant terms can be assessed.
Vendors may also be asked for release-specific component information when the available notices do not answer a project’s questions. The FME Desktop material itself provides component names and, for some entries, links to project or licensing information. Those references can help teams locate the governing terms, but the notice should not be read as a complete technical dependency map.
Conclusion: treat notices as a governance resource
Third-party software licenses reveal that industrial applications can rely on a diverse mix of external code, data, and development resources, each with its own conditions. For automation engineers, operations leaders, and integrators, the practical step is to connect license review to the exact software release and planned use. Careful recordkeeping and timely review can clarify attribution, redistribution, and modification questions before they become project issues.