
Many buyers assume ownership rights for a custom automatic assembly machine arrive with the crate. Then they need a PLC password and get stuck. Our Wenzhou team hears this often.
Ownership rights for a custom automatic assembly machine should be defined in the contract on three layers: who owns each piece of intellectual property, who may use it exclusively, and which technical documentation must be delivered. Separate physical title, IP ownership, and usage rights, then assign each category explicitly.
The rest of this article walks through those three layers. I will show you which contract terms to ask for, how to protect your own design, what happens to mid-project changes, and which files you should hold before you release the last payment.
Last year a German buyer sent our contract back with one request: list our Background IP before design review. That request made the project cleaner for both sides.
Your custom machine contract should include Background IP schedules for both parties, a Foreground IP definition with intellectual property assignment to you, a license for supplier technology embedded in the machine, source code ownership terms, confidentiality obligations, reuse limits, and a technical documentation delivery list.
A machine builder contract that only says "the buyer owns the machine" leaves most of the value undefined. The steel frame is the cheapest part. The engineering, the control logic, and the process knowledge 1 are where disputes start. So I recommend you split the contract into three layers, which is exactly how we structure our own confidentiality and IP supplementary agreement: IP division, exclusive use, and technical data delivery.
Ownership and usage are separate legal questions. You can hold title to an asset and still grant the other side a narrow license. You can also receive broad usage rights without ever receiving title. The contract should answer both questions for every category below.
| Category | Default owner | What the buyer should receive |
|---|---|---|
| Physical machine, fixtures, feeders, spare parts | Buyer, after title transfer | Clear transfer date and risk-of-loss terms |
| Customer Background IP (product data, tolerances, process) | Buyer | Confirmation it stays with the buyer |
| Supplier Background IP (standard modules, libraries, platform) | Supplier | Perpetual, royalty-free license to operate, maintain, repair, modify, replace |
| Foreground IP (project-specific designs, fixtures, code) | Buyer, if the buyer paid for it | Written assignment upon creation or payment |
| PLC, HMI, robot, vision, safety software | Split per above | Source files, not only runtime |
| Third-party software | Third-party vendor | Schedule of licenses and transfer rules |
| Confidential information and trade secrets | Originating party | Mutual NDA with deletion duties |
Background IP is anything a party owned before the project. For us, that includes our standard vibratory feeder designs 2 and our reusable PLC function blocks. Foreground IP is created during the project for your product. The supplier should list its Background IP before work starts. If it does not, it can later claim your product-specific nest was "part of the platform." Avoid joint ownership. It sounds fair, but it leaves both parties unable to act without the other.
Use an intellectual property assignment or work for hire agreement for customer-specific deliverables. That covers copyright in drawings and code and any patent rights 3 in new inventions tied to your product. Use a license for supplier platform technology. Every license should define field of use, territory, duration, exclusivity, transferability, sublicensing, affiliates, contractors, maintenance providers, modification rights, backup rights, and rights after resale or termination.
The integrator cannot give you rights it does not hold. PLC vendors, robot vendors, and vision software companies set their own software licensing terms. Ask for a schedule that names each third-party component, its owner, license type, permitted users, renewal fees, and what stops working if a license lapses.
There is a real tension here. We want to reuse our standard vibratory feeder modules; buyers want their product-specific nests kept off the market. We weigh this every quote.
Protect your proprietary design by signing a non-disclosure agreement before any technical exchange, listing your product data and process parameters as customer Background IP, prohibiting reuse of customer-specific designs for competitors, negotiating defined exclusivity, controlling machine data, and limiting supplier reuse to generalized concepts only.
Your product drawings, volumes, tolerances, and assembly sequence enter the supplier's building the moment you request a quote. Protection has to start before that moment, not after the machine ships.
We ask every serious buyer to sign a mutual NDA before our engineers open their CAD. It should cover product designs, manufacturing processes 4, quality data, and commercial terms. It should also state whether we may photograph the machine, publish a case study, or name you as a customer. The default answer should be no unless you approve.
Physical designs are easy to spot. Process know-how is not. It hides in torque strategies, leak-test methods, dispensing parameters, vision thresholds, reject logic, and cycle-time tuning. The contract should state that product-specific assembly sequences, test methods, tooling geometry, process parameters, inspection criteria, production recipes, failure-mode responses, and commissioning data belong to you. The supplier keeps its general expertise and receives only the rights needed to perform support.
Buyers often raise this. The honest answer is that full exclusivity on everything would raise our price, because we could never reuse a feeder or a function block. But that is not what you need. You need exclusivity on what is yours. The layered model below keeps our platform reusable and keeps your solution off a competitor's floor.
| Supplier may reuse | Supplier may not reuse |
|---|---|
| Generalized mechanical concepts | Your drawings, nests, or fixture geometry |
| Standard function blocks and HMI templates | Your PLC recipes and process parameters |
| Feeder and conveyor modules | Your product data or inspection criteria |
| Lessons about cycle-time methods in the abstract | Any component before customer-specific information is stripped out |
Where a solution is unusual, consider exclusivity for a defined period or industry segment, or a separate exclusivity fee.
Modern lines generate telemetry. The contract should say you own production, quality, and machine-generated operational data. Grant the supplier narrow rights for commissioning, warranty, and troubleshooting, and state whether aggregated data may feed its analytics or predictive-maintenance models. If the machine includes machine learning 5, separate the supplier's base model from site-specific trained weights, which should be yours. If a digital twin is built, secure your right to use it for future simulation and line changes.
One lesson from our chamfering machine projects: a mid-build change request is a new piece of engineering. If nobody writes down who owns it, both sides assume they do.
Modifications you request and pay for during production should be treated as Foreground IP and assigned to you, unless they only improve the supplier's generic platform. The contract should state this in the change-order process, cover derivative works, and keep supplier Background IP licensed to you.
Ownership disputes rarely start at signing. They start when a gripper is redesigned in week six, or when a service engineer rewrites a vision recipe two years later. So the change process itself needs an IP step.
We handle change requests the same way on every custom line, and I suggest you ask for the same:
Without step three, the supplier can later describe your paid redesign as "an improvement to our standard module."
| Type of improvement | Owner | Other party's right |
|---|---|---|
| Customer-specific fixture, recipe, or code change | Buyer | Supplier has no reuse right without permission |
| Generic improvement to supplier platform | Supplier | Buyer keeps a perpetual operational license |
| Improvement based on buyer confidential information | Buyer, exclusively | Supplier may use only for support |
| Supplier Background component embedded in the change | Supplier | Buyer's continuing license to operate, repair, modify |
Be careful with any clause reading "all improvements belong to the supplier." If you fund the engineering, that language hands over what you paid for. Also decide whether improvements are assigned or only licensed, and require the supplier to disclose improvements it creates during support.
You should hold a right to use independent contractors for maintenance and modifications. That right needs access: administrator credentials, safety-controller passwords, and editable project files. Suppliers will ask for a reverse-engineering restriction to protect their platform. A workable compromise lets you and your authorized contractors inspect, modify, or decompile software only as needed to operate, maintain, repair, improve, or replace the machine, while the supplier keeps a ban on reproducing its general-purpose technology for resale. Address corrective maintenance rights directly rather than relying on a reverse-engineering clause. Rules differ across the United States, Germany, Japan, and other markets we ship to, so have counsel review this in your governing jurisdiction.
Before a cable lug machine leaves our Wenzhou floor, we run a handover check: backup image, unlocked PLC project, native CAD, and signed FAT record. Then we book freight.
Before final payment, secure ownership rights for a custom automatic assembly machine with native CAD design files, 2D drawings, electrical and pneumatic schematics, PLC, HMI, robot and vision source files, administrator passwords, software licenses, backup images, bills of materials, as-built drawings, acceptance records, and a signed intellectual property assignment.
Title on paper means little if you hold only PDFs and a locked controller. Picture a buyer who owns the machine but cannot get the native CAD. Every new change part goes back to the original builder. That is dependence, not ownership.
Do not make every IP transfer wait for the last invoice, especially if you already paid for engineering at design approval. At the same time, a supplier can fairly condition assignment on payment of undisputed amounts. Spread the handover across milestones.
| Milestone | What should transfer or be delivered |
|---|---|
| Design approval | Approved concept drawings, Background IP schedules confirmed |
| Factory acceptance test | FAT records, preliminary schematics, draft manuals |
| Shipment | Title transfer or security-interest terms, risk-of-loss shift |
| Site acceptance test | SAT records, production-rate demonstration data |
| Final documentation handover | Native files, source code, credentials, backups, as-built set |
| Final payment | Signed assignment, training complete, retention released |
Withhold a defined portion of payment until the full technical documentation package arrives.
Mechanical: native 3D CAD design files, 2D manufacturing drawings, bill of materials, component specifications, spare-parts list, and design files for replacement parts.
Electrical and fluid: electrical schematics, pneumatic and hydraulic diagrams, safety-circuit documentation, network architecture.
Software: PLC and HMI source projects, robot programs and teach files, motion-control programs, vision recipes and inspection logic, safety PLC programs, servo and drive parameters, reporting scripts, passwords, license keys, development-environment details, version-control records, and a documented backup image.
Process and records: calibration procedures, maintenance manuals, troubleshooting guides, change logs, revision history, FAT and SAT records.
State file formats, revision levels, delivery dates, and that files must be unlocked and editable. "Documentation package" without a format list is not a deliverable.
If a supplier will not assign reusable code, ask for source-code escrow with release triggers: insolvency, non-support, breach, or end-of-life. Add a supplier-exit clause requiring current code, drawings, credentials, and records if support ends. Cover change of control too.
Product nests, grippers, jigs, change parts, gauges, and test equipment are often the most important parts of the line. Put asset tags on customer-funded tooling and attach a property schedule. State that these items are yours even while stored at the integrator's site, and that they may be transferred to another supplier.
Buying the machine is the easy part. Define IP allocation, exclusivity, and technical documentation delivery before the purchase order, and you will never beg for a password again.
Interested in sourcing the products mentioned in this article? See details and request a quote here:
1. Official US government resource explaining trade secret protections for proprietary industrial process knowledge. ↩︎
2. ISO develops international standards for industrial machinery and technical documentation requirements. ↩︎
3. WIPO provides the global legal framework for patent rights and intellectual property protection. ↩︎
4. Overview of manufacturing processes and their significance in industrial production and intellectual property. ↩︎
5. NIST provides technical standards and guidelines for implementing machine learning in industrial systems. ↩︎