Between Detective Work and Team Spirit

It is just past eight o’clock when Felix Kremen opens his laptop. A fresh cup of coffee is within reach as the computer boots up. “The first few minutes are always the same,” he says. “Check emails, open Teams, and see what’s most urgent today.”

But his responsibilities extend far beyond that. He supports ongoing system projects, handles migrations independently, and acts as a technical advisor to the sales team during customer meetings. In addition, he manages the administration of DXQcontrol and is on call—even outside regular working hours—for production-critical incidents.

All these situations demonstrate just how deeply DXQcontrol is embedded in the plant. The system does not just detect individual signals; it understands the interconnections between processes, components, and workflows. When something goes off track, this digital nervous system kicks in, making it clear: Now we need someone who understands the system and can read the software language. Especially in critical cases, the tension in conversations becomes palpable. “And that’s exactly when you notice it slowly easing up again,” says Felix. “When you find a solution together and even end up laughing again—that’s always a very liberating moment.” It is precisely these moments that are the highlights of his job. When a production-critical problem is solved and customer satisfaction noticeably returns. What Felix finds particularly appealing about his work is the mix of technology, analysis, and teamwork. “Sometimes a complex project really feels like detective work,” he says. “You follow clues, rule out possibilities, and when you untangle the knot, it’s very rewarding.”

Situations like these are particularly challenging—especially when they happen in the middle of the night. Support calls outside of regular business hours are always critical; otherwise, they would not come in. “You have to be fully present from one minute to the next and grasp complex issues,” says Felix. At the same time, you must assess whether a problem can be solved on your own or whether other colleagues need to be brought in—even if that means waking them up.

Felix can usually identify minor error patterns right away. He quickly recognizes typical causes and knows where to start. For more complex cases, he works closely with his team. Everyone has different strengths and different modules they know particularly well, and by working together, they usually find a solution.

If a problem turns out to be a software bug, he documents it thoroughly and passes it on to the development team. Felix handles many tasks on his own, and he also spends the entire day communicating with customers and colleagues. It is precisely this collaboration that he believes is a major part of their success.