Is open source a viable path in systems engineering?

To anticipate the answer right away: Yes, but... - there are now several open source solutions, all of which are also used industrially. But being successful with them is not easy. Below we take a look at three tools that all take different approaches: Papyrus, Capella and Aras.
What is success?
First of all: Many open source projects, and certainly the three mentioned, are success stories in themselves. The tools have an acceptable distribution. Many open source projects can be found in teaching in particular. Students do not have to deal with licenses and can get started immediately. These projects therefore make a valuable contribution.
Open source SE tools make a valuable contribution to training and teaching and are an absolute success there
But what about industrial use? It's not about how widespread the tools are. For one thing, this is difficult to measure, as registration is not usually required. Secondly, many tools are only used once, or by a single person.
Success" is more about whether the use of open source creates added value compared to the alternative closed source solution.
Papyrus
Papyrus is an Eclipse-based modeling environment that cleanly maps the SysML standard. Papyrus can also be integrated as part of an Eclipse application and is therefore part of many other Eclipse applications, such as the SysML standard. openETCSwhich I had worked on myself.
Papyrus can be very frustrating without proper customization or maintenance. It is therefore essential to plan an appropriate budget for these activities. After all, nothing comes for free - the license costs saved must be invested elsewhere. Three years ago, Papyrus also aligned itself accordingly as a platformwhich requires a corresponding investment in order to present itself as a finished tool.
Eclipse has also recognized this and has therefore introduced the Eclipse Papyrus Industry Consortium has created an industry-friendly framework. This also helps industry to assess the effort required for successful productive use.
Capella
Capella follows a similar approach to Papyrus. However, while Papyrus has no clear industrial leadership, Capella is primarily driven by Thales. This in turn means that the added value for the user is much clearer, as Thales itself uses Capella. As a result, Capella is much more driven by use cases. This is also reflected in the fact that Capella was developed for a specific method, ARCADIA.
This makes Capella more interesting for the industry than Papyrus, at least in my eyes. With Capella, you can get started almost immediately with tools and a corresponding development approach. With Papyrus, you have to make a substantial investment before you can implement successful projects.
Aras
About Aras I had not yet written. One of the reasons for this is that Aras positions itself more as a PLM solution. However, Aras does have a systems engineering component.
But Aras is interesting in this article because the company relies on a (semi-)open platform. Similar to Red Hat with Linux, for example, the company earns money with service and support. However, the free software also contains proprietary parts. Aras calls this "Enterprise Open Source" and is called explained here (registration required).
Nevertheless, the model is so successful for Aras that Goldman Sachs invested $70 million in Aras last year - for less than 20% of the company's shares.
Conclusion
As is so often the case in life, nothing comes for free. However, the good thing is that there are options. In addition to proprietary solutions for systems engineering, there are also semi-open and fully open solutions. However, the more "open" a tool is, the more investment is required in the form of training and customization. In this respect, interested parties should definitely keep the total costs in mind and not underestimate the customization effort.
Photo by ian dooley on Unsplash






