Non-Standard Doesn't Mean Unmanageable: Standardization in Custom Automation Equipment in China

Every manufacturing facility that uses non-standard automation equipment eventually faces the same problem.

The equipment works. But there are ten different suppliers, fifteen different PLC brands, twenty different pneumatic fitting specifications, and no two machines that share a spare part. When something breaks, the maintenance team spends half their time figuring out what they’re looking at before they can start fixing it.

This is not inevitable. It is the result of procurement decisions that optimized for individual projects instead of the facility as a whole.

How Suppliers Think About Batch Equipment

A batch order — three or more identical units — is one of the more revealing windows into how a supplier actually operates.

For most non-standard equipment suppliers in China, the engineering team works from templates. Sometimes those templates are company-issued standards. More often they are personal libraries that individual engineers have built up over years — preferred component brands, familiar electrical layouts, mechanical configurations that have worked before. When a new project arrives, the engineer reaches for what they know.

This isn’t laziness. It’s efficiency, and within a single company it usually produces consistent results. As suppliers grow, the better ones formalize this instinct into actual standards — standardized mechanical modules, standardized electrical cabinets, standardized PLC configurations, standardized HMI layouts. The machines they produce start to look and feel like a family.

The problem, from a foreign buyer’s perspective, is that each supplier’s standards are their own. When you buy equipment from five different suppliers, you get five different families of machines — each internally consistent, but collectively a maintenance challenge.

What Happens When the Buyer Sets the Standards

The alternative is for the buyer to set the standards.

Large manufacturers — particularly those with multiple production lines and significant equipment inventories — eventually develop their own equipment specifications. Not just functional requirements, but hardware standards: approved PLC brands, approved sensor brands, approved pneumatic and electrical component specifications, cabinet layout requirements, labeling conventions, documentation formats.

The benefits show up immediately.

Spare parts consolidation: when every machine in a facility uses the same PLC brand, the same servo drives, the same sensor families, inventory becomes manageable. One set of components covers multiple machines. Carrying costs drop. Emergency sourcing becomes faster.

Maintenance efficiency: a technician who knows one machine in a standardized fleet effectively knows all of them. Fault-finding is faster because the logic is familiar. Repair times are shorter because the components are the same. Training new staff is more straightforward because there is less to learn.

Supplier management: when your equipment specifications define approved components, your relationships with component vendors become an asset. Volume purchasing, technical support, and warranty claims all become simpler when you’re dealing with a smaller set of suppliers across a larger equipment base.

The Part You Can’t See: Software Standardization

The hardware case for standardization is easy to make. The software case is less visible but equally important.

In non-standard automation equipment, the PLC program is often written from scratch for each machine — or adapted from whatever template the engineer happened to use. The result is programs that work but don’t resemble each other. Variable naming conventions differ. Function block structures differ. Fault handling logic differs. A technician diagnosing a fault on an unfamiliar machine has to understand the program from the beginning before they can find anything.

Software standardization changes this. Modular program architecture — consistent naming conventions, standardized function blocks for common operations, standardized fault handling and alarm structures — means that a technician familiar with one machine can navigate any machine in the fleet. The structure is the same even when the application is different.

This is harder to specify in a procurement contract than hardware standards, and harder to verify during acceptance testing. But it is the difference between a maintenance team that can handle problems independently and one that needs the original supplier on-site every time something goes wrong.

Standardization Doesn’t Mean Identical

None of this requires that all machines be the same. Non-standard equipment is non-standard precisely because different processes require different solutions.

What standardization means here is that the building blocks are consistent even when the configurations are different. The same PLC platform running different programs. The same cabinet layout hosting different I/O configurations. The same mechanical modules combined in different ways.

The non-standard part — the part that addresses the specific process requirement — sits on top of a standardized foundation. That foundation is what makes the fleet manageable.

When to Establish Standards: Before the First RFQ, Not After

For a foreign manufacturer building out or expanding an equipment base in China, the time to establish these standards is before the procurement begins, not after.

Once equipment is in the field, retrofitting standards onto an existing fleet is expensive and disruptive. The machines that already exist will remain non-standard for the rest of their operational lives, because nobody is going to rebuild them.

Equipment specifications established before the first RFQ goes out become the foundation for everything that follows. Every supplier who bids knows the requirements. Every machine that is delivered meets them. The maintenance team that takes delivery of the tenth machine works from the same knowledge base as the maintenance team that took delivery of the first.

This is also where multi-supplier strategy matters. Spreading procurement across multiple suppliers reduces dependency on any single vendor — but only if those suppliers are all working to the same standards. Without common standards, multi-supplier procurement replaces single-vendor dependency with a fragmented equipment base that’s harder to maintain than either alternative.

The Procurement Benefit Nobody Mentions

There is one more benefit that rarely comes up in conversations about standardization, but that procurement teams notice immediately once they experience it.

When equipment specifications are standardized, costs become predictable.

A supplier quoting against a known standard — defined component brands, defined cabinet specifications, defined documentation requirements — is quoting a known scope. The variables are the application-specific elements. Everything else is calculable.

This makes budget estimation more accurate, commercial comparisons more meaningful, and negotiation more straightforward. The supplier who quotes high on standardized components is visible. The supplier who substitutes cheaper alternatives against an undefined specification is not.

Non-standard automation equipment in China doesn’t have to mean unpredictable procurement. With the right specifications in place, it can be as manageable as any other capital equipment category.

I have spent over a decade managing non-standard automation projects in China — from the supplier side and the project management side — watching how equipment fleets develop over time in facilities that did and didn’t plan for standardization.

Now I work exclusively for the buyer, providing independent technical risk advisory for foreign manufacturers procuring custom equipment in China.

Honzer Industrial & Independent Risk Consulting Suzhou, China

#NonStandardAutomation #EquipmentProcurement #ManufacturinginChina #EquipmentStandardization #ForeignManufacturers #MaintenanceManagement #RiskManagement #IndependentRiskAdvisory #FactoryAutomation #ChinaManufacturing