Long-term Software Development Partnership With Systems Engineering

Systems Engineering A/S had a prototype application for helping other companies develop technical systems of any kind. With Ruby on the backend, the prototype fulfilled the business requirements but turned out to be not scalable enough. It was possible to design an engineering system with it but it couldn’t handle the magnitude required by their clients. The goal was to handle billions of elements, whereas the prototype could handle tens of thousands.

The goal we started with was to rewrite the existing prototype for efficiency and scalability. To handle the required amount of elements, the new app was connected to an efficient Neo4J graph database and Vue.js on the frontend. Over time, we also worked on their mobile application, and helped migrate the web platform from Vue 2 to Vue 3.

The mobile app allows users to quickly pull up key information from the web app, including details about the elements that underpin a system’s design. The interface of the mobile app needed a redesign to improve User Experience. The technology that it was using also required changing for security and future extendibility reasons (from React Native JavaScript to React Native TypeScript).

Although the core functionality was to stay the same, some new features were needed (like the ability to switch between workspaces), as well as an integration with a new API that the main web service had.

Later on, one of our front-end developers also worked on the migration of Systems Engineering web platform from Vue 2 to Vue 3.

We collaborated with Systems Engineering to break the requirements and ideas into smaller, tangible tasks.

We repeated this process iteratively throughout each stage: web prototype development, mobile app refactoring, and Vue 2 to Vue 3 migration. Working in this way, we’ve carried out a number of technical and functional improvements such as implementing end-to-end tests or figuring out the best way to add functionality where users can join workspaces.

To rewrite and scale the PoC, we started from scratch by creating an architecture for the Neo4J backend database, and building the frontend part. The PoC redevelopment lasted 2 months. Then we proceeded to build new features.

We built two core modules: one that deals with designing electrical systems, and another that allows combining this aspect with two other elements of an entire engineering system. We also created a module that enables comparison of two similar versions of an engineering component and accepts or rejects the differences. We also designed and developed a version of the app for individual, non-corporate engineers.

Later on, we supported the migration of the web platform’s front-end from Vue 2 to Vue 3. This enabled greater code reuse, the removal of several external dependencies, and an opportunity to thoroughly debug every detail of the interface.

• Regularly discussing priorities and plans between Systems Engineering stakeholders and developers.

• Translating the requirements into technical solutions and implementing an iterative approach to drafting solutions.

• Collaborating in an agile way and scaling our team of developers up and down based on the client’s needs.

• Always focusing on the client’s business context, and maintaining close collaboration between our team in Poland and their team in Copenhagen.

Although the underlying web service has changed significantly, the mobile app stayed functional and continued to facilitate communication around the systems being designed. The workspace functionality that we’ve implemented allows the users to have different viewpoints and discussion angles.

We were able to deliver software that handles billions of elements in engineering systems while staying scalable and performant. One of the updates we included improved the speed of the app by up to 20x. We also created a mobile companion app for the main software and supported the web platform’s migration from Vue 2 to Vue 3.

Over time, Systems Engineering built out their in-house development team. Throughout this process, we’ve supported them at every step to ensure a smooth knowledge transfer from our team to their internal developers. As of 2025, one back-end developer still supports the Systems Engineering team.

• Finding creative technical solutions for the complex challenges of a platform meant for developing large-scale systems.

• Understanding the business context and working in an agile way to propose solutions that address the client's evolving needs.

• Iteratively working with Systems Engineering to find the best solutions possible for the mobile app.

• Supporting the platform’s migration from Vue 2 to Vue 3 in a way that satisfied changing requirements.

• Building strong international collaboration between teams based in Poland and Copenhagen.