Visualizing Production Data: Why Many Companies Fail to Unlock Its Full Potential
When people think of custom machine building, they think of custom-built machines. Every system is unique, and every customer has their own requirements. But how can projects be completed faster and more cost-effectively while maintaining consistently high quality?
We spoke with our Software Engineer, Christoph Kaufmann.
When was the Strama Standard introduced, and why was it developed?
Christoph Kaufmann: We began developing the Strama Standard back in 2012.
Back then, we asked ourselves a simple question: Why do we keep reinventing so many things in every project, even though they’ve already proven themselves?
It quickly became clear to us that standardization has to be much more than just a library of PLC blocks or design guidelines. That’s why we’ve taken a mechatronic approach from the very beginning, with the software department playing a pioneering role in standardization.
For us, mechanical engineering, electrical design, pneumatics, robotics, vision, PLC software, HMI, and data technology are inextricably linked. Only when all disciplines are built on the same structure can a truly end-to-end engineering process be achieved.
Today, the Strama Standard is continuously being further developed by an interdisciplinary team. Colleagues from all areas contribute their experience from ongoing projects directly to the standard.
To date, the Strama standard has served as the basis for more than 550 control systems and over 600 HMIs that have been delivered.
What exactly does the Strama Standard encompass?
Christoph Kaufmann: Today, the Strama Standard provides a common foundation for key areas of mechatronics engineering.
In the mechanical engineering domain, we define preferred components, system functions, and modular machine concepts—for example, through our ProMoCell platform. Electrical design utilizes standardized BMK structures and ePLAN macros. For control technology, standard PLC modules, a defined software structure, and a style guide are available. In addition, there is a standardized HMI concept, data technology, documentation, and interconnected engineering tools.
A central element is our structure consisting of CL (Control Level), FM (Function Module), FG (Function Group), and FU (Function Unit). This structure is consistently applied throughout the electrical design and software. As a result, the circuit diagram, PLC software, HMI, and documentation all follow the same logical organization. This allows an installed cylinder to be uniquely identified and located in the circuit diagram, the PLC software, the HMI, and the associated documentation.
This facilitates collaboration between electrical design and software development and simplifies commissioning, service, and future expansions. Parts of recurring work steps—from the project structure to PLC software and HMI to documentation—can be generated automatically. Whether Siemens or Beckhoff is used, the module source code remains largely identical.
This facilitates collaboration between electrical design and software development and simplifies commissioning, maintenance, and future expansions. Parts of recurring tasks—from the project structure to PLC software and HMI to documentation—can be generated automatically.
What exactly does the Strama Standard encompass?
Christoph Kaufmann: Many standards focus on individual disciplines. Our approach coordinates multiple trades through defined structures, interfaces, and system functions. This allows the foundation to be used for both individual machines and more complex production lines.
Furthermore, the standard is not limited to a single industry. What matters most is not that every system is structured the same way, but that recurring functions and engineering processes remain traceable and can be reused across projects.
With so much standardization, is there still any room left for customized customer solutions?
Christoph Kaufmann: Yes. The standard defines the common foundation, not the finished machine. It provides interfaces, proven functions, engineering processes, and the safety concept. We build the customer-specific solution on top of that.
The advantage is that a project doesn’t start from scratch. This creates more room for the processes and requirements that are truly unique to each customer.
How do you ensure that the standard remains up to date?
Christoph Kaufmann: We view the standard as an ongoing development. Our guiding principle, “Moving the limits. Together. Constantly,” describes this direction. New technologies and feedback from engineering, commissioning, and service are evaluated, tested, and gradually incorporated.
We set up our test lab back in 2017. That was one of my first projects in the area of standardization. There, we test new technologies and standard functions under realistic conditions before they are used in customer projects.
For suitable system modules, we also use virtual commissioning before the actual machine is assembled. It is an essential part of professional and efficient project management.
How do you introduce new employees and customers to the Strama Standard?
Christoph Kaufmann: Through our STRAMACADEMY, we offer a comprehensive training program.
I am one of several trainers and provide training to both new colleagues and external staff and clients.
As a result, participants are later exposed to familiar concepts, structures, and documentation in their projects, allowing them to get up to speed more quickly. The consistent system architecture also helps in our service operations: Our experts are familiar with the basic structure and can locate information more efficiently. For customers, this simplifies the operation, maintenance, expansion, and modernization of the systems throughout their entire lifecycle.