First, the most important things
A strong implementation partner for PLC software delivers not only code, but a robust overall package consisting of functional logic, safety concepts, HMI, testing and documentation. What counts is whether the provider accompanies machines and systems cleanly up to commissioning and secures technical decisions in a traceable way. Those who can only program but cannot handle integration and traceability usually cause more effort than benefit later on.
Especially during selection, the good solution quickly distinguishes itself from the convenient one. For you, it is not about who promises a few functions fastest, but who delivers stably under real conditions in your project and handles changes cleanly.
What PLC software services should be covered?
At automation GmbH PLC software is not considered in isolation. The company develops functional and safety software for machines and plants and links them with electrical design, fluid technology, HMI design, drive technology, robotics, integration, testing and documentation. This breadth is important because errors at the interface are often more expensive later than the actual programming.
| Area | What to look for | Why it matters in the project |
|---|---|---|
| PLC programming | Clear functional logic, structured code, clean handovers | Facilitates changes, testing and later expansions |
| HMI design | Usability must fit the machine and the operators | Reduces user errors and training effort |
| Safety concept | Safety functions must be addressed early | Prevents late modifications and release problems |
| Testing and documentation | Traceable tests and complete documents | Speeds up approvals and service deployments |
What many underestimate: a technically strong team does not stand out by presenting the most elegant programming solution, but by identifying side effects early. In our projects, the actual quality often does not lie in the first draft, but in the clean coordination between control, operation and execution.
How do you recognize implementation strength in practice?
- The partner asks early about boundary conditions, not just the specification.
- They can explain how PLC, HMI, safety functions and drive technology work together.
- They think about testing, documentation and commissioning before the first program is written.
- They name clear responsibilities for changes, approvals and support.
- They also openly say what is not in their scope.
We do not create functional and safety software as a standalone solution, but in a way that it really works in daily project life.
A good sign is also when the engineering partner does not retreat to a single discipline. With automational GmbH this is exactly the point: the combination of electrical design, PLC, HMI, safety concepts and assembly is more relevant for many machine projects than a pure software service. In practice, projects rarely fail due to an idea, but due to handovers that no one truly takes responsibility for.
When is a partner for machine software the wrong choice?
A partner is often unsuitable when they sell IT software development but have no proximity to controls engineering. Automational GmbH explicitly does not list IT software development as a service, and that is an advantage for this type of project: for machines and plants, no generic app thinking is needed, but technical understanding of signal paths, safety logic, HMI behavior and commissioning. Those who blur these differences usually create unnecessary friction in the project.
- Does the provider ask about machine behavior, not just functions?
- Is the team able to combine electrical and software topics?
- Are there clear statements on testing, documentation and handover?
- Are safety requirements treated concretely, rather than just mentioned?
- Is the communication precise enough to be viable in day-to-day project life?
What role do topics like data, remote control and hydraulic engineering play?
A strong implementation partner is often recognizable by how well they cover special cases. For example, automational offers a data long-term storage system with analysis and alerting, IEC 104 remote server, as well as control technology know-how in hydraulic engineering. Such topics show whether a provider knows not only standard projects but also how to handle operation-critical requirements.
This is relevant for you if your plant must document, alert or connect to external systems beyond pure machine operation. Then it is no longer just about function, but about traceability, availability and clear response paths in operation.
Frequently asked questions
How can I tell in the first interview whether an engineering partner is really implementation-strong?
Should I focus more on software or on overall capability when choosing?
When is a supplier too IT-focused for my automation project?
Why is documentation in PLC projects so important?
If you are looking for a partner, pay attention to evidence and clear responsibilities. At automational GmbH in Glarus, this pragmatic approach is the core: building solutions so that they prove themselves in operation and not just look good on paper.
Möchten Sie Ihre SPS-Software mit einem belastbaren Engineering-Partner umsetzen?
automational GmbH, Glarus