Of describing and showing in product development

“I notice you don’t really understand what I’m talking about. Wait a minute, I’ll show you.” Often communication fails when people are forced to describe things instead of showing them. Because they are either out of reach or because they simply don’t exist in real life. Like products that are still in the development stage. That’s why designers are downright DIY experts. With a product idea in mind, they quickly build a prototype with cardboard and glue. In this way, they succeed in showing what is difficult to put into words. This is exactly what efficient product development processes need and can be achieved through deeper integration of 3D visualization functions into the PLM system.

A picture is worth a thousand words

The value added by images over pure text is something we take for granted these days in a multimedia world. On Instagram and elsewhere, text only underscores what has already been captured in the image. But how much of this self-evidence has arrived in the IT systems that support the work of manufacturing companies? In my perception, describing is still more important than showing: The majority of the screens contain characters, words, tables and sentences.

Since the spread of CAD systems, especially in PLM applications, there has been no shortage of images. Hardly any product is manufactured before it has been designed in advance as a (3D) image. The 3D model is a natural tool in product development and in times of increasing product individualization an ideal tool for communication around the product. From chairs to electric cars: across all industries, products can be individually configured online and viewed in 3D before they are ordered and produced.

Why does enterprise software still remain so text-heavy?

CAD software licenses are expensive. Companies therefore often only equip a few workstations with it. In addition, CAD software as proprietary file formats cannot be easily opened by other programs. Thus, access to 3D geometries remains limited to an exclusive club.

If this hurdle is overcome, for example with neutral 3D viewers, the question of how 3D geometry and text can best be combined with the operating UIs of the enterprise software still remains. Beyond the fanciful visions of the future concerning data handling with VR/AR à la Minority Report, there is still a lack of concepts in reality for combining information from 3D models and databases in a uniform operating pattern.

So, where do we go next?

The first step is to bring 3D geometries into the UI alongside the usual textual content. In addition to displaying and rotating, a basic function is the ability to navigate inside the model in order to view individual components in detail by selectively showing and hiding them. Functions such as entering, saving and sharing annotations on the 3D model are also helpful for effective communication within the team. Furthermore, additional Digital Mock Up (DMU) calculation functions can support certain decision-making processes. Such as a neighborhood search to analyze the impact of an engineering change. Or a model comparison to subsequently understand the scope of this change.

In the second step, geometric and textual information must be combined in the UI. This creates an integrated user interface that offers added value in terms of content. Moreover, how would it be if the 3D model in PLM applications no longer served as an illustration of the parts list but, conversely, the parts master data enriched the 3D geometries? Or if tables and textual hyperlinks are abolished and a real geometric or spatial navigation is available? Or if users can visually browse the parts inventory like in a warehouse instead of tracking down numbers in a list? Or, or, or.

We have become so accustomed to working with strings in information technology (I’m thinking of command lines, relational databases, hyperlinks and so on) that other operating patterns seem unthinkable. Here it is time to rethink and unleash the visual power of 3D geometry to communicate quickly and accurately in business processes.

MBSE is too important not to have a podcast

It’s September 2020 – a lazy late summer evening: Tim Weilkiens and I are holding a virtual meeting to discuss what we would like to present in our joint contribution to Systems Engineering 2020. It will boil down to an example from the current development status of SysMLv2 – something new – a live demo would be great – hardly anyone in Germany knows this yet. But why? You should actually start a podcast!

That’ s how you can summarize the birth of our podcast idea “The MBSE Podcast – Trust us we are Systems Engineers”

Why choose MBSE?

But what is it all about? Tim, author and board member of oose e.G. and I, MBSE & PLM consultant and team leader at CONTACT Software, are both passionate about systems engineering. With this podcast we set out on a mission to spread the word about MBSE (Model-based Systems Engineering). MBSE has gained momentum in Germany over the last ten years. This means that it has arrived in many industries or at least the awareness that systems engineering is a key competence for mastering the increasing complexity of interdisciplinary product systems.

However, finding a solution to a complexity problem is certainly not easy in itself. This applies very well to the topic MBSE. MBSE is very multifaceted and not very easy for newcomers to grasp: Methods, processes, languages, roles, architectures, frameworks, tools and training – to name just a few.

MBSE from A to Z – for beginners and advanced

This is where we start to explore the topic piece by piece in a relaxed atmosphere. There are plenty of books, training courses and tools available. But in our podcast we would also like to take a look behind the scenes and pass on our knowledge between the lines of specifications. We benefit from our private and professional engagement with the Gesellschaft für Systems Engineering (GfSE), the International Council on Systems Engineering (INCOSE) and the Object Management Group (OMG). Thus, we are very close to current developments in the (MB)SE field and are in close exchange with national and international key players from application, consulting, research and tools.

The start of the continuous podcast

On October 30, 2020 the podcast started with a teaser on YouTube. The first content episode entitled “The History of SysML” followed on November 5, 2020. We plan to publish one or two episodes per month.

Why on YouTube?
The platform offers extensive infrastructure for us and very easy access for viewers.

Why live?
Tim and I run the podcast in our spare time. We simply do not have the time to cut episodes for evenings. The live stream and the recording available afterwards are as they are: 100 percent authentic. In the future, we plan to include interaction with the listeners via live chat.

For those who prefer to listen to a podcast, we publish in addition to YouTube the audio track on Spotify and Apple Podcasts.

Risks and safety – (just) an issue in times of crisis?

Germany and almost all other countries are facing a crisis! Within a very short time we had to realize that an infectious organic structure with a size of a few nanometers is causing gigantic damage worldwide and is turning our lives upside down. We suddenly realize how vulnerable our existence is and how our own need for security always comes to the fore when everything around us can no longer be taken for granted.

History teaches us that it doesn’t matter what the name of a disaster is – COVID-19, 9/11, Fukushima or Tsunami, safety and risks have to be reconsidered and reassessed in each case. Because too much security makes any system slow and cumbersome. By contrast, too many risks, however, entail a high degree of danger – not only for the individual, but also for society as a whole.

The consideration and evaluation of product risks is a familiar topic in the PLM world. Risk management is often perceived as an annoying accessory, which essentially causes a lot of paper to be filled. However, the concrete added value is not always immediately apparent. This is where the change of perspective from producer to consumer helps: Countless test and quality seals in every area of daily life ensure that products are safe to use, for example the TÜV for the car, the CE mark on the notebook or the GS seal on the office chair. Nobody wants to do without the fact that the product he uses is sufficiently safe and that he can use it without major risks.

Three fundamental insights have become apparent for my consulting work:

  1. Think the unthinkable
    Science and technology make us feel more and more that nothing can happen to us. But this certainty can be deceptive. Sometimes we only feel safe because we are not (yet) aware of risks or because we misjudge them.
  2. You cannot think as stupidly as it may come
    It will never be possible to anticipate every risk and to be prepared for all eventualities or even be insured against them. Nevertheless, risk management trains the eye for possible dangers and effective countermeasures. Regularly thinking about risks and sounding out parameters for security in times of no crisis trains thought structures and action patterns. These consequently form a solid basis for sound crisis management.
  3. Necessity is the mother of invention
    Unknown situations paralyze one’s own thinking and acting at first, but as a consequence they stimulate creativity in particular. There is enormous potential here for innovative and efficient ideas on how to achieve great things with existing onboard resources. So every crisis also offers the chance for change and improvement.

Corona ensures that the golden mean between safety and risk in all areas of life can once again be balanced under the given parameters. Perhaps the changed perspectives will even make it possible to take a more positive view of risk management in PLM and give free rein to one’s own creativity both in assessing risks and developing safe products?