The problem with building a machine across separate vendors

Most machine projects work the same way. A mechanical engineering firm designs the machine. An electrical engineering firm does the cabinet and the wiring. An automation company writes the PLC software. Each works from the previous discipline’s outputs, on their own timeline, with their own assumptions about what the interfaces look like.

The automation software - the part that has to understand everything - goes in last. It inherits whatever decisions were made upstream, adapts around them, and gets blamed when commissioning runs over time.

This is not a vendor quality problem. It is a coordination structure problem. And it produces the same result every time: interface rework, schedule pressure, and a machine that nobody fully owns.

A different structure

Together with Plötzeneder GmbH and Hinstech GmbH, we take on complete machine and automation system projects as a single coordinated team. Mechanical, electrical, and software are scoped together from the start - not handed off sequentially.

The three disciplines work from a shared project definition. Mechanical interfaces are agreed before electrical routing begins. Electrical topology is defined before software I/O lists are written. When something changes - and it always does - it propagates through one team, not across three separate contract relationships.

The result is a machine with coherent engineering across all disciplines, delivered by people who have worked together before and know how to divide the scope without losing anything at the interfaces.

What each partner brings

Automation software & control systems

PLC programming on TwinCAT 3.1, HMI development, motion control, and system integration. Every machine we deliver runs structured, documented software built on the Zeugwerk Framework - not throwaway project code. Your service team can read it, extend it, and maintain it after handover without calling us.

Mechanical engineering & process development

Machine design, process engineering, and Pharma & Medtech specialisation since 1977. They own the mechanical scope from the first concept sketch through to finished manufacturing documentation.

ploetzeneder.com →Opens in a new tab
Electrical engineering & CE compliance

Hardware design, electrical schematics, cabinet engineering, and conformity assessment. CE is handled inside the project team - the delivered machine is regulatory-ready from day one.

hinstech.at →Opens in a new tab

Why this over three separate vendors

No interface rework

The people defining the mechanical interfaces are in the same project conversation as the people writing the I/O lists. Assumptions get surfaced early, not discovered at commissioning.

Software from day one, not day last

Automation requirements shape the mechanical and electrical design - not the other way around. Sensor positions, cable routing, and cabinet layout are informed by the software architecture before metal is cut.

One accountability

One project. One set of deliverables. No gap between what the mechanical scope includes and what the electrical scope assumes. No disagreement about who owns the commissioning overrun.

Regulatory handled inside

CE conformity assessment sits inside the project team - not outsourced to a consultancy after the machine is built. The documentation is complete, accurate, and produced by engineers who understand what they are certifying.

What we build

We work across industries and project sizes. Most of our machines fall into one of these categories - but the structure is the same regardless of scope.

Pharma and Medtech - Special-purpose assembly, testing, and packaging machines for regulated environments. Plötzeneder's background in pharmaceutical machine building runs deep here. Validation-ready documentation, GMP-compatible design, and software built with traceability in mind.

Industrial automation - Production cells, handling systems, end-of-line automation. Custom scope, defined throughput, integrated into existing lines or delivered as standalone systems.

We predominantly build on the Zeugwerk Framework, but we work with customers who have their own PLC architecture, and we partner with Beckhoff where standards like MTP make sense. The right tool for the right machine.

Projects start with a conversation about the process, not a quote request form. Tell us what the machine needs to do, what the constraints are, and where you are in the development process. We will tell you quickly whether we are the right fit and what the next step looks like.
Talk to us about your project