Twitter

Towards Digital Enterprise

 

If you work in product development, you may have come across model-based engineering or model-based systems engineering. But do you grasp the true idea behind these concepts? They are not actually brand-new concepts but have gained new momentum over the past few years. The driving force has been the need to design ever more complex systems of mechatronic products, and simultaneously making the products lighter, safer, more optimized, and more environmentally friendly. Technological advancements in engineering applications have acted as a catalyst.

In this blog post, I try to clarify the idea of model-based engineering and model-based systems engineering, and why every company developing, and manufacturing products should adopt some or all of these practices. 

What is Model-Based Engineering and Model-Based Systems Engineering?

International Council on Systems Engineering (INCOSE) is a widely recognized not-for-profit organization with the objective of developing and spreading interdisciplinary principles and practices that enable successful systems. 

INCOSE further defines model-based engineering as:INCOSE

"An approach to engineering that uses models as an integral part of the technical baseline that includes the requirements, analysis, design, implementation, and verification of a capability, system, and/or product throughout the acquisition life cycle."

INCOSE further defines model-based systems engineering as:

"The formalized application of modeling to support system requirements, design, analysis, verification, and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases."

So, what do these definitions really mean? To answer this, we first need to look at one more definition – the definition of model. And as always, there are multiple definitions available in the literature, some of which I’ve listed below

  • A model is a physical, mathematical, or otherwise logical representation of a system, entity, phenomenon, or process. (US DoD 1998)
  • A model is an abstraction of a system, aimed at understanding, communicating, explaining or designing aspects of interest of that system (Dori 2002)
  • A model is a simplified representation of a system at some particular point in time or space intended to promote understanding of the real system (Bellinger 2004)
  • A model is a representation of one or more concepts that may be realized in the physical world (Fredendall, Moore, and Steiner 2009)

In short, a model is a representation of something that can be realized in the real world, and a model is intended to help us understand the real-world object, system, or phenomenon. A model can represent a small entity or an extensive system of systems. Models are generally considered abstractions of the real world, but the more accurate a model is the more value you get from using it.

So, model-based engineering and model-based systems engineering are practices that aim at developing highly accurate models of even complex systems of systems, and thus enabling the use of these accurate models for downstream business operations to push the quality and efficiency of systems and operations to a new level.

If you feel like diving deeper into the theory and practices, I recommend taking a look at chapter Representing Systems with Models in the Guide to the Systems Engineering Body of Knowledge (SEBoK). 

undefined 300w" alt="" width="525" height="203" class="attachment-large size-large" loading="lazy" />

Why are our current practices insufficient in the new era of complex products?

Engineering drawings have been around for thousands of years, with the earliest known building plans dating back to circa 4000 BC. Descriptive geometry and projection techniques were invented already during the industrial revolution of the 18th century. Likewise, written specifications have been around for quite some time. Even though the introduction of three-dimensional modeling software in the late 1960s brought engineering one step closer to the model-based approach, downstream processes have continued to rely heavily on information carried by traditional drawings.

So why not continue trusting good and well-known practices? The fact that the engineering community has grown used to drawings is not really a good enough reason. There are severe flaws with these practices even when describing relatively simple products, let alone complex mechatronic systems:

  • When someone needs to use a drawing as a source for information for designing interconnected parts, or for manufacturing parts, they need to interpret the drawings. Visualizing the actual part in one's mind based on 2D views is something many people struggle with.
  • Engineers are capable of interpreting drawings because they undergo training in creating and interpreting drawings, but even they don't always get it right.
  • Understanding engineering drawings is a talent not widely shared outside the engineering community. If clarification is not sought for, drawings are often misinterpreted by sourcing, manufacturing, and maintenance which results in costly errors, the need to rework parts, the need to correct drawings, and in some cases redesign the parts or products. And if clarification is sought for, it always ties up more than one person.

If you have never come across any of these issues, congratulations. But it is more than likely that drawings from your engineering department are plagued by many of the problems commonly seen in the manufacturing industry. If you don’t think so, take a random sampling of manufacturing and/or assembly drawings from your company and see if they are truly unambiguous in defining the products. 

So what is the deal with drawings and written specifications not being sufficient to define more complex systems?

Well, engineering drawings are geared towards representing the geometry of parts and how these parts come together as assemblies. But what if electronics, electrics, and software are involved? The answer is more drawings and some documents, this time called schematics, or diagrams, and datasheets. Each of these individually tries to represent one specific aspect of a part or a product, but when you combine parts to a product the different systems interact, and this is where traditional engineering documentation fails. Even though engineers do their best to describe all aspects of a complex mechatronic system, drawings, schematics, diagrams, and all the other documents do not form an easily understandable and coherent definition of the entire system.

If it is hard for the engineers creating the system to document it fully, imagine how hard it is for anyone downstream to interpret such documentation! And everything needs to be kept together even if some small detail changes. When someone gets some small detail wrong, millions of Euros or even lives might be at stake. 

Why are models a better way to describe systems?

Simply because models make systems and their behavior easier to understand and simulate. Beginning with understanding what a product or part is like. State-of-the-art engineering applications with virtual reality support allow for life-like experience of seeing parts and assemblies. Making it far easier to understand what they are like and what it is like to interact with them, than interpreting 2D views. 

Interconnected, and computer interpretable models, which together can represent all aspects of real-world systems with the desired level of accuracy further improve the capability to understand how a given system will behave under different circumstances. Combining behavior models with 3D models allows for comprehensive and realistic MIL/SIL/HIL simulation of all aspects of a system. By throwing in design exploration tools, companies can further enhance their capability to find optimal solutions within given constraints. In the best case without having to build a single prototype for the analysis.

The benefits of a model-based approach are not limited to engineering. 3D models that include product and manufacturing information (PMI) make life in the downstream much easier. PMI can be consumed by downstream applications for tooling design and analysis, part planning and CAM programming, plus automated inspection planning and programming.

Models of manufacturing infrastructure are crucial for production optimization. Process simulation tools make use of the models and help remove bottlenecks in production and logistics, while detailed models of production lines and automation systems combined with detailed models of products allow for fully virtual production engineering and virtual commissioning, making lot size one a reality in production.

Savings of transforming your business to a model-driven digital enterprise are potentially huge. These savings come from improved efficiency of manual processes, increased automation of routine tasks, improved quality of operations and products, and optimized use of resources like energy and materials.

Check out the case story with Varjo “Taking the design process from days, hours, to minutes“, conducted by Siemens.

Are you ready to take the leap? 

Get in touch:

 

Teppo Salmia
Chief Business Architect, Digital Business Solution
+358 40 5534566
This email address is being protected from spambots. You need JavaScript enabled to view it. 

 

Håvard Gundersen
Director, Digital Business Solutions
+358 40 5534566
This email address is being protected from spambots. You need JavaScript enabled to view it.

Give us a few minutes! We would love to tell you more about our solutions.

Send us your details and we will contact you. Thanks!

Invalid Input
Invalid Input
Invalid Input
Invalid Input
Invalid Input

Selection of Customer CASES

  • Harju Elekter Groups
  • Laitila Tooling
  • SeAMK
  • Hesplan Oy
  • Suhmuran Metalli
  • Miror – Creating emotional engagement
  • Konecranes
  • Logset Oy
  • TAMK
  • Jucat
  • Seco Tools
  • SeAMK
  • TAMK
  • Turku AMK
  • Bronto Skylift
  • Jucat
  • University of Oulu
  • Streamlined work for Tooltec Trestad
  • Bronto Skylift
  • Bronto Skylift
  • Polar Electro
  • Toijala Works