Access Official Technical PDF

Share Summary:LinkedInEmail

Industrial software licensing can be more complex than a single agreement between a buyer and equipment supplier. Network management systems and transport platforms may incorporate commercial software, open-source components and code from multiple third-party licensors. For industrial automation engineers, system integrators and technical decision-makers, understanding how those terms fit together is part of managing deployment, support and compliance risk.

Product-specific terms published by Infinera in May 2019 illustrate the issue: licensing conditions vary by product and, in some cases, by software release. The document is not a universal guide to current terms, but it highlights practical questions buyers should ask whenever a network or automation product includes embedded or bundled software.

Why industrial software licensing is product- and release-specific

A supplier’s standard terms may be supplemented by conditions that apply only to named products, software packages or firmware releases. The Infinera terms, for example, list different software licenses across MetroWatch, 6300, 7100, 8000, 8600 and other product families. Some entries also distinguish between firmware packages or releases, so a product name alone may not identify every applicable obligation.

This matters during system design and lifecycle planning. A hardware platform can be delivered with software components governed by different terms, and a later software release may have a different license inventory. Procurement, engineering and operations teams should therefore verify the precise product configuration and release covered by their order and license documents, rather than assuming that one product-family description answers every licensing question.

Open-source components still have license conditions

Open-source software is not necessarily covered by the supplier’s standard software license. The cited terms say such components are provided under their own applicable licenses. The product listings reference licenses including the GNU General Public License (GPL), GNU Lesser General Public License (LGPL), BSD, Apache, MIT, Mozilla Public License and others.

These licenses are not interchangeable. Their conditions can address matters such as notices, redistribution, source-code availability, modification or use of names and trademarks. The specific obligations depend on the relevant license and how the software is used or distributed. A list of component licenses is therefore a starting point for review, not a substitute for checking the license text that applies to each component.

The document also states that source code for files covered by a license requiring source-code provision upon request can be requested from the seller. That is a specific process described in those terms; it should not be read as a general promise that source code for every component is available. Buyers assessing maintenance, security review or redistribution needs should identify which files and licenses are relevant and confirm the applicable process.

Check third-party software and usage limits

Some product entries describe software supplied by third parties, with additional conditions layered onto the seller’s terms. Oracle software, for example, is described as limited to the end user and the seller product with which it was provided, for the end user’s internal business operations. The terms also address copying, transfer, reverse engineering, benchmarking, export compliance and termination of use when a license expires or ends.

Other provisions establish limits tied to the licensed deployment. In the section concerning Information Builders software, the permitted use may be restricted by the licensed number of CPUs, servers, physical or virtual cores, or named users. The terms define a named user as a specific individual and describe a virtual core as limited to a subset of physical cores on the same computer. If the deployment exceeds the stated allowance, the document requires notification and additional applicable license and software update fees.

These details can affect decisions about virtualization, server replacement, workload consolidation and access management. Before changing a system architecture, teams should compare the proposed deployment with the actual license metrics and confirm any uncertain interpretation with the supplier or qualified legal counsel.

Build license checks into procurement and operations

License management is easier when it is included in normal equipment and software controls. Practical steps include:

  • Record product and release details: Keep the model, software or firmware release, order documents and applicable product-specific terms together.
  • Maintain a component and license inventory: Capture disclosed third-party and open-source components, their license identifiers and any required notices or source-code request details.
  • Track deployment metrics: Where terms specify users, servers, processors or cores, document the licensed quantity and review it before expansion or migration.
  • Control copying and distribution: Check whether backup, archival, internal transfer or onward distribution is allowed under the relevant terms.
  • Review change and exit plans: Confirm what happens to software, copies and documentation if a license ends, a product is replaced or a system is transferred.

Some licenses also give third-party licensors beneficiary rights or specify audit-related obligations. The cited terms, for example, authorize audits in certain circumstances and require reasonable assistance and access to information. Keeping accurate deployment records can help an organization respond to a license review without relying on informal assumptions.

Conclusion: treat licensing as part of system governance

Industrial software licensing is a technical and operational concern as well as a procurement matter. Embedded software can carry distinct terms for each product, release and third-party component, with restrictions that may affect deployment scale, copying, access and lifecycle decisions. Organizations should preserve the relevant documentation, maintain a clear inventory and review license conditions before changing configurations or redistributing software. Because terms differ and the cited document dates from 2019, buyers should confirm the current agreement and obtain qualified advice where interpretation or compliance is uncertain.

Access Official Technical PDF

About The Author