OEM Protocol Licensing for CNC Data Collection: A Guide for System Integrators

Most CNC data integration project disputes end up being about software licensing rather than technical capability. The technical work was done. The customer's audit found undeclared library dependencies. The renewal quote came in 3× higher than expected because someone added a per-machine option fee. This guide walks through what each major OEM's CNC protocol actually requires, who pays, and where integrators get caught.

This is a starting framework, not legal advice. Always verify current terms with the OEM or your software vendor before quoting.

Quick Answer: What Licenses You Need for Each Brand

Why OEM Licensing Matters for Integrators

Legal Exposure if You Skip This Step

Distributing OEM libraries (Focas binaries, Heidenhain APIs) without a redistribution license is a contract violation. Most OEMs don't actively police small integrators, but enterprise customers do - IT and legal audits in defense, aerospace, automotive, and pharma will check what's running on their network.

Why Customers Are Starting to Ask

Customer-side procurement increasingly asks: "Confirm all third-party libraries are properly licensed for use in our environment." If you can't answer with documentation, the deal stalls.

How OEM Coverage Affects Your Win Rate

Customers shopping connectivity solutions ask which controllers are covered. "We'd need to develop that" means you've lost. "We have native support, properly licensed" means you've moved to the next stage.

Fanuc Focas Licensing

What the Focas Library Actually Is

Focas (Fanuc Open CNC API Specification) is Fanuc's official C/C++ library for accessing data from Fanuc controllers over Ethernet (Focas 2) or HSSB (Focas 1). It's the only sanctioned way to read structured data from Fanuc CNCs at the depth needed for monitoring. See Focas tech guide.

Who Can Get a License

Fanuc distributes Focas to: - Direct customers (machine purchasers) for in-house use. - Software developers and integrators through Fanuc developer programs. - Commercial vendors with redistribution agreements.

The right path for an integrator depends on whether you're using Focas for one customer's deployment (developer kit may be sufficient) or distributing connector binaries to many customers (need redistribution agreement).

Distribution and Redistribution Rules

Without redistribution rights, you cannot legally: - Ship Focas DLLs/binaries with your software product. - Embed Focas inside a connector you sell or license to a third party. - Distribute compiled Focas-based tools through public channels.

You can: - Use Focas for in-house projects you deliver to a Fanuc-customer (within scope of your developer agreement). - Compile against Focas with no commercial redistribution.

Common Compliance Mistakes

• Engineer downloaded Focas from forum or older partner site, and assumed continued use is licensed (it isn't).
• Connector deployed at customer with Focas DLL bundled, no documentation of license origin.
• Reuse of Focas code from previous employer without IP transfer.
• Github wrappers built from leaked Focas headers - entirely outside any license.

If any of these apply to your current deployments, get them remediated before the next customer audit.

Heidenhain DNC and TNC Option Licensing

DNC Option (Option 18)

Heidenhain TNC controllers (TNC 530, TNC 640, iTNC 530, TNC7) require Option 18 (DNC) on the controller side to expose data over Heidenhain DNC API. This is a per-machine controller option - purchased and activated on the machine itself.

Per-Machine Option Codes

Cost varies by region and machine age, generally a few hundred to a few thousand euros per machine. Some Heidenhain controllers come with Option 18 enabled from the factory; many do not. Always verify per-machine before scoping.

Who Pays - Integrator or Customer?

Conventionally the customer pays Heidenhain directly for option codes. Integrators often forget to flag this in scoping, leading to surprise bills and project delays. Add explicit line items to your quote: "Customer to procure Heidenhain Option 18 for X machines."

See Heidenhain monitoring guide.

Siemens SINUMERIK Access Licensing

OPC UA Server License

Siemens SINUMERIK 828D, 840D sl, ONE controllers expose data via OPC UA, but the OPC UA server is a paid option per controller. The customer pays Siemens. Integrators should verify which controllers in scope already have it activated.

SINUMERIK Integrate / Run MyHMI

For deeper Siemens integration (custom HMI, app frameworks), additional Siemens SINUMERIK Integrate licenses apply. Most CNC monitoring projects don't need these - they only matter if you're customizing the controller HMI.

SINUMERIK ONE Specifics

The newer SINUMERIK ONE platform extends OPC UA access patterns and adds new options. Verify per-controller as the platform evolves.

See Siemens OPC UA integration.

Mitsubishi MELSEC Licensing

Mitsubishi MELSEC protocol is implemented across MELSOFT tools and PLC/CNC products. Commercial vendors typically have redistribution rights for MELSEC-aware drivers via their relationship with Mitsubishi. For in-house use directly with MELSEC libraries, license terms vary by product (CC-Link, MX Component, etc.) - verify with Mitsubishi distributor.

Mazak SmoothX, Okuma THINC, Brother CNC Net

Mazak: Modern Mazak controllers expose MTConnect (open standard, no licensing on the standard itself). SmartBox hardware (where required for older controllers) is a one-time per-machine purchase from Mazak.

Okuma: THINC API access requires Okuma THINC Developer Partner program enrollment for software vendors. End-customers using a vendor's THINC integration don't typically pay Okuma directly.

Brother: Brother CNC Net protocol access is via Brother developer agreements. Vendors handle this; in-house builds need direct Brother engagement.

Open Protocols: MTConnect, OPC UA, Modbus

MTConnect's Open Standard Status

MTConnect specifications are openly published by MTConnect Institute. No fee to use the standard, no fee to implement an agent or adapter. Vendors may charge for their MTConnect implementation, but the standard itself is free.

OPC UA Foundation Membership

OPC UA specification is open. OPC Foundation membership ($) gives access to compliance testing, certification, and working groups. Not required to implement OPC UA in a product.

When "Open" Still Has Costs

The standard is open; the controller-side server is often a paid option. Siemens OPC UA option, Mazak SmartBox, Okuma THINC API are examples - open protocols on the wire, paid components to make the wire actually carry data.

See MTConnect Protocol Manufacturing.

How Connectivity Vendors Bundle These Licenses

Reputable CNC connectivity software vendors (MDCplus, MachineMetrics, Predator, etc.) handle: - Fanuc Focas redistribution - Mitsubishi MELSEC drivers - Okuma THINC API access - Brother CNC Net

Customer-paid options that vendors don't handle (because they're per-machine controller options): - Heidenhain Option 18 - Siemens OPC UA option - Some Mazak hardware (SmartBox)

A clean integrator quote separates "software platform license (vendor handles)" from "controller-side options (customer procures)" so nothing is hidden.

Licensing Compliance Checklist for Your Next CNC Project

1. List every brand and controller series in scope.
2. For each, identify which side licenses what (vendor / customer / your in-house build).
3. Confirm in writing with your software vendor that their license covers your customer's deployment scenario.
4. Include controller-side options as customer-procured line items in your quote.
5. Document Focas/MELSEC/etc. binaries deployed at customer with origin and license proof.
6. Save vendor agreements where customer audit teams can find them on request.
7. Renewal cycle: re-check OEM licensing terms annually - they shift.

Frequently Asked Questions

Do I need a Focas license if my software vendor already has one?

If you're deploying their licensed software, no separate license. If you're modifying or wrapping their Focas distribution, that's a different question - read your reseller agreement.

Does the customer need to pay for Focas?

Not directly. Focas redistribution is the vendor's responsibility (or yours if you built it).

Does the customer need to pay for Heidenhain Option 18?

Yes, per machine if not already activated. This is a controller-side hardware option, not a software cost you can absorb.

Is Focas free if I use MTConnect on Fanuc?

The MTConnect adapter still uses Focas underneath. The standard is free; the underlying library is not. If using the official FANUC MTConnect Adapter, Fanuc has handled the licensing. Third-party MTConnect adapters for Fanuc may or may not be properly licensed - verify.

Can I use Focas headers from GitHub?

Headers without a Focas license from Fanuc are unauthorized. Don't.

What's the audit risk?

Defense, aerospace, automotive, pharma - high. Job shops and SMB manufacturers - low but non-zero. Treat any deployment as if it could be audited.

Does MDCplus include all OEM licenses?

MDCplus's license covers software-side OEM redistribution (Focas, MELSEC, THINC, Brother CNC Net). Controller-side options (Heidenhain Option 18, Siemens OPC UA option) are still customer-procured.

What if I inherited an undocumented deployment?

Document what's installed, contact your software vendor for license confirmation, remediate or replace anything that can't be cleared. Better to discover it before an audit than during one.

Skip the Licensing Maze with MDCplus

Request a demo and we'll provide license clarity per controller in scope, in writing, before quoting. No surprises in the customer audit two years later.

• CNC Connectivity Software for Integrators (Hub)
• Build vs Buy Fanuc Connector
• Focas Tech Guide for Fanuc
• MTConnect Protocol
• Siemens OPC UA Integration
• Open-Source vs Commercial

About MDCplus

Our key features are real-time machine monitoring for swift issue resolution, power consumption tracking to promote sustainability, computerized maintenance management to reduce downtime, and vibration diagnostics for predictive maintenance. MDCplus's solutions are tailored for diverse industries, including aerospace, automotive, precision machining, and heavy industry. By delivering actionable insights and fostering seamless integration, we empower manufacturers to boost Overall Equipment Effectiveness (OEE), reduce operational costs, and achieve sustainable growth along with future planning.