In this blog series, we highlight the customers who have chosen to utilize Camunda Platform 8 and explore the challenges those companies are attempting to overcome using process orchestration. For the latest installment of Why Camunda 8, we spoke with R-KOM, a telecommunications company based in Regensburg, Germany.
When R-KOM was founded in 1997, its shareholders pooled their telecommunications infrastructure, which had evolved over decades with utility networks for water, electricity, and gas. Initially, R-KOM’s services were limited to business and the public sector, but now it has developed further in line with demand. Over the years, the company’s high-performance infrastructure and a broad range of products have grown.
Today, R-KOM has a number of city networks in Eastern Bavaria (Germany), which are connected to form a regional network. These networks consist of fiber optic cables for high-speed transmission and a large number of connection points to national/international fixed networks. R-KOM focuses on long-term success and continuously invests in the expansion of its own telecommunications infrastructure.
R-KOM has been utilizing Camunda since the beginning of 2021, and at the beginning of 2022, the team decided to migrate from Camunda 7 to Camunda 8. We spoke with R-KOM’s head of process management, Thomas Kiefer, to learn more about the motivations behind the migration.
Tell us about your use case. What is the problem you’re hoping to solve with Camunda 8?
Thomas Kiefer: “We are trying to automate the service production of our internet, telephony, and television products as much as possible in order to achieve full automation.
“We have a colorful bouquet of use cases, with a total of 200-250 different workflows. A few examples are customer onboarding, i.e. the setup of different products, and the coordination of service calls or additional services such as address changes. In the future, we also want to be able to automate services for problem-solving in the event of outages.
“The biggest challenge from a process perspective that all these use cases have in common is that many different systems, and also many people, are involved in the processes. Additionally, the event that triggers the process can come in from different systems and at very different times.”
Which options did you evaluate to solve your problem?
Thomas Kiefer: “First, in 2020, we looked for replacements for our in-house developed workflow engine, as it was 20 years old and could no longer meet today’s automation requirements.
“In total, four options were evaluated. In the end, the decision was between Activiti and Camunda. We already had Activiti on our radar, as some interfaces were already running on it and we had experience with it.”
What were the key decision criteria you had when evaluating options, and why did you choose Camunda 8?
Thomas Kiefer: “We chose Camunda for many reasons. Firstly, because of the BPMN standard, but also because of the proximity to Activiti, as our developers were already familiar with it. However, for user interventions, i.e. for user tasks, Activiti did not work as well as we would have liked. and since it was very important for us to be able to include manual interventions in our workflows, Camunda was a natural fit.
“We then started to develop in Camunda 7, but soon after we received the news that Camunda 8 will be introduced. Truthfully, we didn’t know what to think about Camunda 8 at first. But since we were still quite early in our development cycle – we had only rolled out three processes – it was a very practical decision to migrate. If we continued to build architecture in Camunda 7, we would migrate it to Camunda 8 sooner or later anyway. To minimize the effort in the coming years, we thought it would be better to go right along and develop in Camunda 8.”
Why did you decide to go SaaS? What are the benefits compared to self-management?
Thomas Kiefer: “Actually, we never wanted to switch to SaaS because it is company policy to have the critical infrastructure in-house. But since we couldn’t have managed our own Kubernetes administration due to limited resources, we first considered buying in support. But then we would have another service provider on board. With Camunda, we get everything from a single provider, and since they have a vested interest in keeping things running, we don’t have to worry about the SaaS infrastructure and administration ourselves.
“After more detailed evaluations, the technical department at our company was very enthusiastic, and from an architectural point of view, we didn’t find any potential issues. After further risk assessment, there were also no more objections from a data protection point of view. Another advantage was that it would have taken much more time to set up our own infrastructure. With Camunda 8 SaaS, we could start right away.
“And so, we decided to go the SaaS path together with Camunda. As far as we can tell, it’s been the right decision, simply because it simplifies a lot of things.”
What’s your advice for anyone evaluating Camunda? Any helpful lessons you’ve learned and would like to share?
Thomas Kiefer: “We are very satisfied with Camunda in general, with Camunda 8 we are currently in the migration and implementation process. Camunda is a super partner in this process, we always have friendly contact persons and fast support. Also, the trainings have helped us a lot.
“One thing we underestimated a bit is the effort it has taken to implement Camunda. But that is more due to internal structures that play into the overall project than to the software itself.”