Skip to content
Finance & Wealth

ATS Global Ownership of Software: IP Rights, Licensing Models, and Custom Code Guidance

In this article

ATS Global retains full intellectual property ownership of its proprietary software products, including ATS Inspect, ATS Bus, and the ATS ADOS suite. For custom integration projects, software ownership is governed by client contracts: clients typically own custom configurations and customer-specific code (Foreground IP), while ATS Global retains foundational platforms, pre-existing tools, and core libraries (Background IP).

Understanding software ownership in industrial automation and digital transformation is critical for enterprise procurement, information technology (IT) leaders, and operational technology (OT) teams. When working with global independent solution providers like ATS Global (ATS International B.V.), organizations encounter a dual model: proprietary software products owned outright by ATS Global, alongside complex implementation projects involving third-party software, customized scripts, and bespoke integration pipelines.

Disentangling software ownership requires analyzing intellectual property (IP) frameworks, contractual licensing agreements, Background versus Foreground IP definitions, and source code escrow practices. Clear contractual boundaries prevent legal disputes, ensure continuity in plant operations, and streamline long-term software asset management across global manufacturing sites.

Understanding ATS Global's Dual Role: Software Publisher vs. Systems Integrator

To evaluate software ownership accurately, enterprise buyers must recognize that ATS Global operates in two distinct capacities within the industrial technology ecosystem: as an Independent Software Vendor (ISV) publishing proprietary products, and as a Systems Integrator (SI) deploying enterprise platforms.

Independent Software Vendor (ISV) Systems Integrator (SI)
• Owns proprietary software (ATS Inspect, Bus)• Retains core IP, copyrights, and patents• Grants user licenses (Perpetual / SaaS) • Implements 3rd-party platforms• Authors custom integration• Manages Foreground IP rules

1. ATS Global as an Independent Software Vendor (ISV)

In its capacity as an ISV, ATS Global develops, copyrights, sells, and maintains its own standardized software products designed for smart manufacturing, quality management, and industrial integration.

  • Ownership Status: ATS Global owns 100% of the underlying source code, system architecture, trademarks, and documentation for its proprietary software solutions.
  • Client Status: Purchasing these tools grants the enterprise customer a non-exclusive, non-transferable license to execute the software. It does not grant ownership of the underlying IP or access to core source code.

2. ATS Global as a Systems Integrator (SI)

As a systems integration partner, ATS Global designs, installs, configures, and customizes software solutions across shop floors worldwide. In these projects, ATS Global frequently deploys third-party platforms from vendors such as Siemens, AVEVA, Rockwell Automation, Inductive Automation, and SAP.

  • Ownership Status: Third-party vendors retain full ownership of their commercial off-the-shelf (COTS) software.
  • Client Status: Software ownership for custom-written integration scripts, database schemas, and tailored Manufacturing Execution System (MES) workflows depends on the Master Services Agreement (MSA) established between the client and ATS Global.

Core Software Products Owned by ATS Global (Proprietary IP)

Over decades of engineering in industrial automation and quality control, ATS Global has developed a commercial portfolio of proprietary software applications. Enterprise deployment of these products relies on standard commercial software licensing agreements rather than custom development contracts.

ATS Inspect (Attribute Data Collection & Quality Inspection)

ATS Inspect is a commercial software package engineered to reduce defect costs in manufacturing through visual quality inspection, attribute data collection, and real-time defect tracking.

  • IP Ownership: Held exclusively by ATS Global.
  • Licensing Model: Available under per-station, per-user, or enterprise site licensing. Customers receive compiled binary deliverables; the source code remains protected proprietary asset of ATS Global.

ATS Bus (Manufacturing Service Bus / OT-IT Integration Platform)

ATS Bus serves as an industrial integration bridge between shop floor equipment (PLCs, SCADA, CNC machines) and upper-level enterprise software (MES, ERP, PLM).

  • IP Ownership: Fully owned by ATS Global.
  • Licensing Model: Licensed per gateway, connected channel, or site deployment. The software architecture utilizes standardized drivers and microservices, where ATS retains all rights to the core transport engines and connectivity adapters.

ATS ADOS (Advanced Digital Operation Solutions Suite)

ATS ADOS is an integrated software platform that encompasses modules for statistical process control (SPC), maintenance management, data analytics, and operational efficiency tracking (OEE).

  • IP Ownership: Retained by ATS Global across all modules.
  • Licensing Model: Enterprise subscription or perpetual server licensing with annual software maintenance agreements (SMA).

For these products, enterprise clients acquire rights to use the software within designated operational parameters, but ATS Global maintains absolute ownership of the intellectual property, including all updates, patches, bug fixes, and derivative extensions developed by its core engineering teams.

ATS and Faro Announce Partnership - ATS Global
ATS and Faro Announce Partnership - ATS Global

Ownership and IP Rights in Custom Software and Integration Projects

When ATS Global performs custom consulting, software development, or complex Manufacturing Execution System (MES/MOM) implementations, the legal framework shifts from simple software licensing to contractual IP allocation. Standard industrial engineering contracts divide intellectual property into Background IP and Foreground IP.

BACKGROUND IP (Owned by ATS Global) FOREGROUND IP (Owned by Client)
• Pre-existing integration libraries• Reusable communication drivers• Core platform engines & frameworks • Client-specific business logic• Tailored user interfaces / dashboards• Proprietary production algorithms

Background IP (Retained by ATS Global)

Background IP includes all pre-existing technologies, software code, algorithms, framework templates, design patterns, and domain knowledge that ATS Global possessed prior to starting the customer engagement.

  • Ownership: Retained entirely by ATS Global.
  • Usage Rights: The client is typically granted a perpetual, royalty-free, non-exclusive license to use any ATS Background IP embedded within the deliverable, strictly for operating the specific system installed.
  • Rationale: Systems integrators rely on reusable code libraries to keep project costs manageable. Retaining Background IP allows ATS Global to reuse foundational tools across multiple client environments without infringing on contract terms.

Foreground IP (Assigned to the Client)

Foreground IP consists of new software, custom code scripts, unique database procedures, workflow logic, and technical documentation created specifically for the client during the execution of the contract.

  • Ownership: Granted to the client upon full payment of project invoices, provided the contract specifies a "work-for-hire" or explicit IP assignment clause.
  • Scope: Foreground IP includes proprietary business rules, custom plant algorithms, proprietary recipe handling scripts, and custom user interface layouts tailored to the client's manufacturing process.
  • Protective Restrictions: While the client owns the unique application layer, they generally cannot extract embedded ATS Background IP to resell as an independent commercial product.

Software Licensing Models and Enterprise Asset Management

Managing ATS Global software assets requires understanding the commercial options, operational maintenance requirements, and software lifecycle commitments available to manufacturing enterprises.

1. Perpetual Licensing Model

Under a perpetual license structure, an organization pays a one-time upfront fee to use a specific version of ATS software indefinitely.

  • Capital vs. Operational Expense: Recorded as a Capital Expenditure (CapEx).
  • Maintenance & Support: Software Maintenance Agreements (SMA) are billed annually (typically 15% to 25% of initial license costs). The SMA guarantees access to minor updates, security patches, system bug fixes, and technical helpdesk support.
  • Operational Risk: If an organization lets its SMA lapse, it retains the right to run the existing software version, but forfeits upgrade rights to newer operating systems, database engines, or security compliance patches.

2. Subscription and SaaS Licensing Models

Modern industrial deployments increasingly favor subscription-based or cloud-hosted Software-as-a-Service (SaaS) structures.

  • Capital vs. Operational Expense: Billed periodically as an Operational Expenditure (OpEx).
  • Continuous Updates: Subscriptions automatically include active updates, feature enhancements, and cloud infra maintenance.
  • Ownership Distinction: The client acquires zero equity or permanent rights; access to the software ceases if the subscription contract is terminated.

Comparative Analysis: Software Ownership Models in Industrial Automation

The table below outlines how software ownership, source code access, and operational risks differ across project types when engaging with ATS Global and third-party software ecosystems.

Software Model Primary IP Owner Client Ownership Rights Source Code Access Maintenance Responsibility Exit & Migration Flexibility
ATS Proprietary Products (e.g., ATS Inspect, ATS Bus) ATS Global Non-exclusive user license Compiled binaries only (Source code withheld) ATS Global (via annual SMA / Subscription) Moderate; data can be exported, but runtime software cannot be transferred
Custom Integration Code (Work-for-Hire) Client Enterprise Full ownership of Foreground IP Full access to custom scripts and configuration files Client internal team or contracted SI High; internal IT or new SI can maintain custom scripts
Third-Party COTS (e.g., Siemens, AVEVA) Third-Party Software Publisher End-User License Agreement (EULA) Compiled binaries only Third-Party Vendor (assisted by ATS Global as SI) Depends on vendor ecosystem and open interface availability
Hybrid OT/IT Architecture Shared / Layered Model Foreground IP owned by Client; Background IP retained by Vendors Access limited to open APIs and customized scripts Split responsibility between internal team, ATS, and software vendors High architectural complexity; requires strict interface documentation

Key Operational Risks and Mitigation Strategies for Enterprise Buyers

When procuring industrial software or commission-based integration services from ATS Global, enterprise IT and legal teams should implement proactive risk management protocols to protect long-term plant operations.

  1. IP Boundary Definition: Clear separation of Background vs. Foreground IP
  2. Source Code Escrow: Deposit critical source code with neutral 3rd party
  3. Vendor Lock-In Relief: Require open REST/OPC UA APIs & documentation
  4. Software Asset Auditing: Maintain centralized register of licenses & SMAs

1. Mitigating Vendor Lock-In

Vendor lock-in occurs when an enterprise becomes dependent on a single systems integrator to modify, update, or expand its shop floor software due to proprietary coding methods or missing technical documentation.

  • Mitigation Strategy: Mandate that all custom code written by ATS Global adheres to open, documented standards (such as OPC UA, REST APIs, and ISA-95 guidelines). Ensure that Master Services Agreements require ATS Global to deliver complete, readable source code and clear technical documentation for all customized Foreground IP modules.

2. Implementing Source Code Escrow Agreements

For mission-critical installations running proprietary ATS software solutions, enterprise buyers may worry about long-term software continuity if vendor business structures or product roadmaps change.

  • Mitigation Strategy: Establish a formal Source Code Escrow Agreement with an independent escrow agent (such as NCC Group or Iron Mountain). Under this agreement, ATS Global deposits a copy of the proprietary software source code, build instructions, and compiler configurations into an escrow vault. The source code is released to the client only under specific, predefined conditions—such as vendor insolvency or failure to uphold contractual support obligations.

3. Securing Data Ownership and Portability

While software logic ownership can be divided between vendors and clients, manufacturing operational data must always remain 100% client property.

  • Mitigation Strategy: Verify that ATS software architectures store production data in standard relational databases (e.g., Microsoft SQL Server, PostgreSQL) or open time-series stores without proprietary encryption mechanisms that block direct client access. Confirm data export features (JSON, CSV, SQL queries) are standard native functions.

Step-by-Step Guide: Negotiating Software Ownership in ATS Contracts

To ensure complete legal and operational clarity, procurement teams should follow this structured sequence when negotiating software development and deployment contracts with ATS Global.

  1. Step 1: Conduct Software & IP Audit
    • Identify all software components, licenses, and custom code modules
  2. Step 2: Establish Background vs. Foreground IP Definitions
    • Document proprietary elements vs. work-for-hire deliverables
  3. Step 3: Formalize Source Code Escrow & API Access Terms
    • Establish third-party deposit terms for mission-critical core products
  4. Step 4: Align Annual SLAs with Manufacturing Lifecycles
    • Lock in update schedules, bug fix response times, and patch policies

Step 1: Conduct a Pre-Contract Software Audit

Identify every software component included in the project proposal. Categorize items into ATS proprietary products, third-party commercial applications, open-source libraries, and custom project code.

Step 2: Explicitly Define IP Allocation in the Statement of Work (SOW)

Insert unambiguous clauses in the SOW stating that all custom business logic, plant-specific workflows, data transformations, and custom user interface configurations built during the project constitute Foreground IP owned exclusively by the client upon final payment.

Step 3: Formalize Source Code Access and Escrow Terms

Require compiled and editable copies of all custom scripts to be delivered directly to the client's internal repository (e.g., Git, Azure DevOps) upon project milestone acceptance. For core ATS software products (like ATS Inspect or ATS Bus), negotiate source code escrow rights if the application is deemed critical to factory operations.

Step 4: Structuring Long-Term Service Level Agreements (SLAs)

Ensure the software maintenance agreement defines clear terms for version upgrades, patch installations, cybersecurity compliance updates, and emergency onsite support. Confirm that software updates will not break custom Foreground IP scripts written during previous integrations.

Frequently Asked Questions

Who owns custom software code created by ATS Global during an MES project?

Custom software code developed specifically for a client during an integration project is generally classified as Foreground IP and owned by the client, provided the contract contains an explicit IP assignment or work-for-hire clause. However, ATS Global retains ownership of its pre-existing tools, core integration frameworks, and background libraries utilized to build that custom application.

Can a client buy the source code of proprietary ATS products like ATS Inspect or ATS Bus?

No, ATS Global does not sell the underlying source code or intellectual property rights for its proprietary software packages. Clients purchase compiled commercial software licenses (perpetual or subscription). To manage business continuity risks, large enterprises can negotiate a source code escrow agreement that releases code only under contractually specified emergency trigger events.

How are third-party software licenses managed when ATS Global acts as systems integrator?

When ATS Global integrates third-party systems like Siemens Opcenter, AVEVA MES, or Rockwell FactoryTalk, the intellectual property of those platforms remains with the respective third-party software vendors. The enterprise client must procure or maintain appropriate End-User License Agreements (EULAs) from those vendors, either directly or re-sold through ATS Global's reseller channels.

Does ATS Global claim ownership over plant data generated by its software?

No. All operational technology (OT) data, manufacturing metrics, quality inspection records, and telemetry collected by ATS software or integration layers belong exclusively to the client enterprise. ATS Global provides the software tools to process and visualize data, but makes no proprietary claim over the customer's data assets.

What happens to custom code support if an enterprise terminates its maintenance contract with ATS Global?

If a client terminates its maintenance agreement, it retains ownership of its customized Foreground IP and can maintain, edit, or modify that custom code using internal IT resources or third-party engineering consultants. However, the client loses access to technical support, official software upgrades, and patch releases for the underlying proprietary ATS background software or third-party platforms.

Practical Recommendations for Industrial IT and Procurement Teams

When negotiating software deployment contracts with ATS Global, enterprise teams should focus on clear contractual boundaries, open technical interfaces, and proactive risk management:

  1. Clearly Separate Background and Foreground IP: Ensure that the Master Services Agreement explicitly assigns full ownership of custom scripts, business rules, and plant integration code (Foreground IP) to your enterprise upon project completion.
  2. Mandate Open Architectural Standards: Require all integrations, custom modules, and data layers to expose documented REST APIs or OPC UA endpoints. This guarantees system interoperability and reduces reliance on proprietary access pathways.
  3. Formalize Source Code Escrow for Core Assets: If your manufacturing plants rely heavily on proprietary ATS software products for continuous production, establish a third-party source code escrow agreement to safeguard plant operation continuity.
  4. Maintain a Centralized Software Asset Register: Audit software licenses, annual Maintenance Agreements (SMAs), version lifecycles, and escrow deposits regularly across all operational sites to prevent unplanned software obsolescence.

By structuring contracts with clear IP definitions and open system standards, industrial organizations can build robust software ecosystems that leverage ATS Global's integration expertise while safeguarding intellectual property control and long-term operational autonomy.