You’ve been actively involved in open source for a long time. How did it all start for you?

Quite traditionally, through projects. We’ve been using open source software and libraries in our projects for many years now. One project that had a particularly strong impact on me was one that required extensive work with the Apache-Jena library. I immersed myself deeply into the technical aspects of it and at some point I’ve realised: when you use Open Source, you can and should give something back.

Since 2022 I’ve been more actively involved in the community and made more significant contributions myself. This has not only helped me with our projects, but also changed my overall understanding of open source.

Why is it important to you that SOPTIM continues taking open source seriously?

Because we’re already heavily dependent on it. Our developers work with open source libraries every single day. If you encounter a bug or notice that a feature is missing, the first step is often to create a ticket in the relevant community. The next logical step is: if we solved the problem for ourselves, we might as well share the solution with the rest of the community.

This has two effects. Firstly, our teams can develop an in-depth expertise in the technologies we use. Secondly, we become more independent. Communities can’t always respond quickly – if we need something urgently, we have to be able to take action ourselves.

That’s why we made a conscious decision to actively support open source and encourage the developers to get involved. Not out of idealism, but because it makes sense from a business perspective.

Does SOPTIM’s unique role in the TSO and KRITIS sectors also play a part in this?

Definitely. Our situation is particularly unique in the field of power system control technology: we frequently develop software for our customers and the code then belongs to them. We have hardly any “product assets” of our own there, and yet we are successful.

At the same time, initiatives such as the Linux Foundation Energy are giving rise to an increasing number of open source projects led by transmission system operators, distribution system operators, research institutions, and universities that are highly relevant to our field. This allows us to utilize tools we don’t have “on the shelf” – such as those for network calculations – and supplement them with our expertise in a targeted manner, rather than developing everything from scratch ourselves.

It’s efficient that way – everyone befenits at the end.

How open are customers to open source?

From our experience: very open. Some customers even explicitly state they prefer open source. A common reason is trust. All users benefit from the advancements and improvements of software that’s already widely used and tested.

It’s a common misconception that open source is unsafe. That is not the case for established, widely used projects – on the contrary.  Open source code, careful review by multiple parties and professional security programs often ensure a very high level of security.

In your opinion, what are the biggest benefits for customers?

A key issue is vendor lock-in. With open source, no one feels “trapped.” In theory, the customer can switch service providers or take over operations themselves at any time. This builds trust and fosters a different kind of collaboration—one based on voluntary participation.

Transparency is another important aspect, especially in KRITIS environments. Often, the source code belongs to the client, which is entirely understandable. At the same time, however, this results in the creation of many basic technical components within projects that cannot be reused outside of that project—even though they do not contain any client-specific information. If you design such building blocks as open source from the very beginning, you can continue to develop, reuse, and improve them. To me, that is sustainable software development.

Where does SOPTIM currently stand on the topic of open source?

We’re currently using open source libraries, components and applications in nearly all of our projects and also contribute to them. So far we haven’t implemented any large, productive core projects based on open source yet. But we are deliberately gaining experience, building expertise and laying organisational groundwork.

In 2025 we began sharing our first smaller open source libraries and projects on our GitHub page. This year we’re planning to share even more.

An important issue here is also responsibility: open course software needs care, maintenance and support. That’s something we can and want to continuously provide. Open source doesn’t replace professional guidance, it complements it.

For our first open-source project (LF Energy’s Power Grid Model), we are now offering commercial support — something no one else has offered before.

Are there any risks or things you need to pay close attention to?

Of course. Small, new open source projects with limited adoption must be chosen very cautiously, especially in security critical environments.

Then there is the risk of license changes, as manufacturers of key components have switched from open-source licenses to commercial licenses in the past. That is why organisations like the Apache Foundation and the Linux Foundation are so important. Projects hosted there cannot simply be converted to “closed source.” This assurance is crucial when dependencies arise.

When chosing the components we prefer those that are already housed at foundations. We are considering transferring our own open source projects to a suitable foundation as well, though we are still in the very early stages of that process.

What developments will continue to drive open source in the energy sector?

We see this issue as particularly relevant in transmission and distribution networks, but also at the political level. At the EU level, we can envision open-source solutions being given greater consideration in future tenders. In Germany, local governments already have a policy of giving preference to such solutions.

I expect the Federal Network Agency to establish similar requirements for the regulated market, particularly with regard to standardized components.

What does that mean for SOPTIM?

For us, that means sticking to it. Building expertise, gaining experience—even on smaller projects. When larger projects come along, we need to be able to demonstrate that we understand open source, know the communities, and can work with them confidently.

The market still faces a massive digital transformation backlog. Efficient, sustainable development is becoming increasingly important. Open source is a key component of this. Not the only one, but a very significant one.

Last but not least, this topic is appealing and motivating for our employees. It attracts new talent and fosters collaboration and professional growth.

To conlcude: Why should we take open source seriously today?

Because the challenges the energy sector is facing aren’t getting any smaller. Open source helps to share knowledge, reduce dependencies and develop sustainable solutions. Those who engage with this early are better prepared – technically, organisationally and culturally. And that is exactly what we strive for at SOPTIM.

Check out our blog post on CGMES2PGM Converter