When companies launch an automation project, software is rarely the first topic on the agenda.
The equipment. Performance. The timeline.
Software is often discussed only after the major decisions have already been made.
I understand why.
But my years working in software taught me that successful projects should not postpone software considerations until the end.
Not because software is more important than the equipment, but because software prompts the right questions.
How do the processes work today? What data is actually available? Where will interfaces be needed? The sooner we answer these questions together, the more stable the overall system will be.
For me, software therefore belongs at the beginning of an automation project, not at the end—not as a product, but as a way of thinking. What is your view?