Block 06 DE MBSE

Digital Engineering and Model Based
Systems Engineering
Antonio Moschitta
Outline
• Definition of Digital Engineering (DE) and Model Based Systems
Engineering (MBSE)
• Models and Modeling
• Characteristics of MBSE Languages
Definitions
• Digital Engineering (DE): first defined by USA DoD in 2018 [2]
• “Digital Engineering is an integrated digital approach using
authoritative sources of system data and models as a continuum
throughout the development and life of a system.”
• “Digital Engineering updates traditional systems engineering practices
to take advantage of computational technology, modeling, analytics,
and data sciences.” [2]
• INCOSE (see SEBoK 2023) imports the DoD definition
Definitions
• “Digital Engineering describes a holistic approach to the design of a complex

system: Design using models/data instead of documents, integration of data
across models, and the culture change across project teams to realize significant
risk reduction on construction cost and schedule.” [31]
• “ Digital engineering (DE) embodies a deliberate approach to integrating
information for the life cycle of a megaproject. DE uses digital information
management systems to design, engineer, build, operate and maintain complex
megaprojects. ” [31]
• See also [32] (BAE Systems) and [33] for relationships between DE and DevSecOps
Definitions
• Advantages of DE [32]:
• “Formalize the development, integration, and use of models to inform
enterprise and program decision-making
• Provide an enduring, authoritative source of truth
• Incorporate technological innovation to improve the engineering practice
• Establish a supporting infrastructure and environment to perform activities,
collaborate and communicate across stakeholders
• Transform the culture and workforce to adopt and support digital engineering
across the lifecycle”
MDAO: Multidisciplinary Design Analysis and Optimization CDD: Capability Development Document
CDRL: Contract Data Requirement List KPP: Key Performance Parameter Image source: [3]
Definitions
• Single Source of Truth (SSOT) [23]: ensuring the all the involved
stakeholders use the same data to make decisions
• A concept related to the Business Intelligence paradigm [24]
• Using SSOT prevents data duplication and reduces the effort spent on
ensuring data correctness
Main concepts associated to DE
• Digital System Model, Digital Twin (simulation), Digital Thread [4-7]
• AI, Machine Learning (example: machines understand human
language)
• Big Data and Data Analytics
• Use of more sophisticated models (A3 Thunderbolt 2D->3D)

• Model Based Systems Engineering (MBSE) is now considered a part of
DE, even if MBSE is older than DE
• A related paradigm is the Model Centered Engineering (MCE)
Digital System Model, Digital Twin, Digital Thread
• Digital System Model:
• A Digital System Model is a virtual representation of a physical object,
system, or process [21].
• Examples: CAD assisted 3D representation of a product [5], a simulation, or
a mathematical algorithm
• NB: a model expectedly represents a guess as to how a physical object,
system, or process might operate in the future or in a particular
environment [21].
• A Digital Shadow (often obtained using laser scanning) is a virtual copy of
an item (data flow is unidirectional) that evolves with the item, mirroring it
• Digital Twin
• “An integrated multiphysics, multiscale, probabilistic simulation of an as-built
system, enabled by Digital Thread, that uses the best available models, sensor
information, and input data to mirror and predict activities/performance over the
life of its corresponding physical twin.” [8]
• “a physics-based dynamic computer representation of a physical object that
exploits distributed information management and virtual-to-augmented reality
technologies to monitor the object, and to share and update discrete data
dynamically between the virtual and real products” [9]
• “While we see many definitions of “Digital Twin,” LMS Research keeps it simple: A
Digital Twin is an executable virtual model of a physical thing or system.” [10]
• Provides an accurate description of an object that changes over time
• Related to the concept of cyber-physical systems
• Digital Twin
• “(the) digital twin refers to a digital replica of physical assets,
processes and systems that can be used for various purposes. The
digital representation provides both the elements and the dynamics of
how an Internet of Things (IoT) device operates and lives throughout
its lifecycle. Digital twins integrate artificial intelligence, machine
learning and software analytics with data to create living digital
simulation models that update and change as their physical
counterparts change” [Wikipedia]
• With respect to the Digital Shadow, the Digital Twin features a
bidirectional and real time connection with the real-life item [22].
• Digital Twin
• IBM: “A digital twin is a digital replica of a physical object or system,
complete with all the design and operational data of the physical
object, including geometry, performance data and behavior models.
The purpose of a digital twin is to simulate the behavior of equipment
in real-time, allowing engineers and operators to monitor
performance and identify system issues/anomalies.” [30]
• Digital Twin
• A Digital Twin of an object includes:
• A model
• A dataset related to the object
• Means to dynamically update the model in accordance with the data (A digital twin
involves data transfer between the real object and its digital representation)
• “The model used in a digital twin need not be a data-driven model, but it
should produce results that are directly equivalent to a measured quantity
(so that the model updating process is data-driven), and it is likely that the
model will take in other measured quantities as boundary conditions,
loads, or material properties.” [11]
• Requirement: the Digital Twin is coupled to an object that exists
(prototypes…)!
• Digital Twin
• How accurate does the model need to be?
• Physical based (also used to tune a metamodel)
• Surrogate model/metamodel (data driven rather than physics based)
• Requirements:
• Updating with measurement data must be useful
• Updated parameters are useful for the considered applications
• Quick enough for the required timescale
• Uncertainty should be assessed (e.g.: add metadata to sensors’ reading,
ensure data curation [12-13])
Digital System Model, Digital Twin (simulation),
Digital Thread
• Digital Twin
• NB: a Digital Twin model may require a linked chain of different
physical models!
• Example: a Micro-Electro-Mechanical-System (MEMS)
Image source: [14] Image source: [15]

• Data flow associated to a Digital Twin [Image source: 11]
• Digital Twin
• Potential applications (high-value or safety-critical): [11]
• “enhanced in-line measurement processes, using the model to identify the data that
will most improve physical understanding”;
• “smart assembly, ensuring that individual parts are chosen for optimal performance
and scrap rates are reduced”;
• “assembly verification, so that complex multi-component structures whose internal
details are not easily accessible can use measurements of the outer surface of an
assembly to provide confidence that the internal structure has been correctly
deployed”;
• “performance assurance, to check that any measured deviations from the product
specification do not compromise performance to an unacceptable degree”;
• “maintenance scheduling and smart maintenance, by using the twin to update
parameters related to known possible faults and thus identifying problems before
they become catastrophic”;
• “lifetime prediction, including the ability to revise component or system lifetime
estimate in service”.
• Digital Twin
• Potential applications [11]
• Manufacturing and testing of complex objects
• Medicine (tailored drugs, prosthetics)
• Fundamental science (Reliable interpretation of results, enhanced by
modeling instruments and their contribution to uncertainty)
• Extensive tests of autonomous systems (e.g. vehicles), where experiments
would be unpractical
• Modeling and managing a supply chain: «digitally enabled supply chain that
can feed supplier data, in-house testing results, and on-line and off-line
measurement results into a digital twin of products to obtain rapid
performance predictions based on the latest data» [11]
• Plant Lifecycle Management (virtual plant…[21])
• Digital Twin
• An example [17]: the Digital Twin of a battery pack
Parameters may include:

• Temperature
• State of charge
• State of health
• Impedance spectroscopy
• Polarization (current versus
voltage curves)
• Image source: [18]



• A word (picture actually) of advice (see also [25])…

• Digital Thread:
• “The digital thread meanwhile is a record of a product or systems lifetime, from
its creation to its removal”
• IBM: “a digital representation of a product’s lifecycle, from design to
manufacturing to maintenance and beyond, providing a seamless flow of data
that connects all aspects of the lifecycle. The purpose of a digital thread is to
provide a complete and transparent view of manufacturing systems, enabling
efficient collaboration and decision-making across all stages of the process.” [30]
• “Digital threads aim is to signify the digitization and traceability throughout a
product’s lifespan” [26]
• Siemens: “the sequence of virtual activities across business processes that can
enhance and expand the digital twin” [29]
• Keyword: traceability
• Digital Thread:
•…
Image source: [27]

MBSE: definitions
• “ MBSE: 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.” [34]
• “MBSE supports the systems engineering activities of requirements,
architecture, design, verification, and validation. These models would
have to be connected to the physics-based models used by other
engineering disciplines such as mechanical and electrical engineering.
One challenge remaining for Digital Engineering is the integration of
MBSE with physics-based models.” [34]
MBSE: definitions
• “In MBSE, the models of the system are primary artifacts of the
systems engineering process, and are managed, controlled, and
integrated with other parts of the system technical baseline. This
contrasts with the traditional document-centric approach to systems
engineering, where text-based documentation and specifications are
managed and controlled.” [34]
Definitions
• A System can be described in terms of properties [35]:
• Entities - Parts of a system
• Attributes - Perceivable and measurable characteristics of an entity (size,
color, quantity, temperature…)
• Relationships – Associations between entities and attributed, based on cause
and effect
• The system properties should be described using a proper language
An example
• ERA Diagram
ERA: Entity-Relationships-Attributes
NB: the figure is actually an ER diagram, since Attributes are not shown
Image source: [1]
What is a model?
• A few definitions from [34] and [35]:
• A physical representation of an abstract idea (toys, mockup)
• Physical/mathematical/logical model: representation of a system, entity,
phenomenon, or process (DoD 1998);
• Conceptual model: a representation of one or more concepts that may be realized in
the physical world (Friedenthal, Moore, and Steiner 2009);
• A simplified representation of a system at some particular point in time or space
intended to promote understanding of the real system (Bellinger 2004);
• An abstraction of a system, aimed at understanding, communicating, explaining, or
designing aspects of interest of that system (Dori 2002);
• A selective representation of some system whose form and content are chosen based
on a specific set of concerns; the model is related to the system by an explicit or
implicit mapping (Object Management Group 2010);
Why to use models?
• Through modeling we can [34][35]
• Characterize an existing system
• Document system functions and requirements
• Assess the mission performance, costs, and tradeoffs
• Provide insights to improve performance, reduce risk, and manage costs
• Support training
• Capture knowledge and support system evolution
• Especially useful in the initial stages, where verifications and
validations are not available, or where verifications and validation is
not possible
Why to use models?
• Model are widely used in Engineering [34]
• Electrical engineering uses electrical circuit design models and simulators
• Mechanical and Civil engineering use three-dimensional computer-aided
design models and simulators
• Software engineering uses software design and architecture models.
Some properties [34]
• Scope: the types of models and associated languages should address the
identified needs
• Example [34]: aircraft development needs at least
• A system architecture model (aircraft parts and their interconnections)
• A trajectory analysis model
• A fault tree analysis
• Depth: coverage of system decomposition from the system context
(airplane, control tower, physical environment) down to the components
(navigation sub-systems like the Inertial Measurement Unit)
• Fidelity: level of detail (interface description: logical information content ->
encoding, bit streams, waveforms and modulations). Can be related to the
precision of a computational model (es: time step of a discrete time
simulation)
Some properties [34]
• Quality:
• Adherence to modeling guidelines (naming conventions, application of
appropriate model annotations, proper use of modeling constructs, and
applying model reuse considerations.)
• Metrics: information provided by the model, useful for both technical
and management purposes. Metric enable the model to fulfil its
purpose [34]
• Assess progress
• Estimate effort and cost
• Assess technical quality and risk
• Assess model quality
Model Classification and characteristics [34]
• Formal vs Informal
• A formal representation makes use of a modeling language, with a defined syntax and
semantics
• Physical vs Abstract
• A Physical model is a concrete representation (e.g. a mockup)
• Mathematical and logical models are abstract representations
• Descriptive, analytical, hybrid
• Domain-Specific
• Driven by
• System Properties
• Design and technology implementation
• Subsystems and products
• System applications
• Order – allows a design team to attack the problems at hand in a coherent
and consistent manner
• Power to demonstrate and persuade – Enabled by capturing the relevant
behavior
• Integrity and Consistency – ambiguity and inconsistency lead to design flaws
and undermine the argument [36] that the modeled/developed system fulfills
the stakeholders needs
• Insight – A good representation of system behavior and relationships gives
insight and permits comparing different approaches (example: Laplace vs
Fourier analysis)
• What is the difference between a model and a simulation?

• One includes the other!
• Visualization
• View (representation of a system from a given perspective, like that of a
Stakeholder) and Viewpoint (conventions necessary to construct and use a given
view), see also IEEE Std 1471.
• Some standard views: requirements, functional, structural, and parametric
System Modeling Concepts
• Abstraction: focusing on essential characteristics, keeping the model
computationally and intellectually tractable
• Black-box and White-Box
• Conceptual Model;
• Also called meta-model or schema
• Can drive the definition of the specifications of the syntax of a modeling language
• A Conceptual Model describes various aspects of a system using one or more
diagram types (e.g.: Systems Modeling Language, SysML)
• Elements of a formal Model [35]
• Language – Should be clear, unambiguous, and descriptive
• Structure – Structure helps capturing System behavior and the interrelationships of its
parts
• Argumentation – “the model must be capable of making the critical argument that the
system fulfills the stakeholders’ requirements” [35]
• Presentation – The model must include some way to show or presenting the argument in
an understandable fashion. (views)
• Further notes [35]
• A model is more than graphical representations
• Example: safety and security issues, that can be related to emergent properties
Image source: [34]

Systems Modeling languages
• Why Systems Modeling Languages (SMLs)? [37]
• Artifacts are usually described using natural language and graphical tools
(drawings), aggregated in documents (Technical Data Packages [37])
• The natural language has many ways to describe things, which is familiar to the
creator of a description and fosters creativity, but can also we
• Ambiguous
• Difficult to update when responding to changes (a change in a description does not
automatically propagate to other descriptions)
• See discontinuities in propagating the descriptions through the SE Lifecycle
• Uneven level of abstraction (different parts of the system described with very different levels
of detail)
• “Modeling languages are generally intended to be both human-interpretable and
computer-interpretable”[34] and are specified in terms of both syntax, semantics,
and ontology.” [34/OCW]
• Ontology: a description of the entities that are allowed to exist in the language,
(i.e.: subjects, nouns, adverbs), and how they are grouped and related to a
hierarchy. Constrains the universe of things that the language can describe [OCW]
• Semantics: assigns meaning to the objects described by the ontology
• Syntax: rules by which the objects can be combined to build higher levels of
information (example: a sentence)
• See also Wikipedia descriptions as a starter ☺
• Where in the V-diagram are we using a SML?
Image source: https://www.slideshare.net/galleman/incose-vee-and-the-imp

Characteristics of a System Modeling Language (SML) [35]
• A SML language should be general-purpose (“domain agnostic”), but applicable to
specific domains
• A SML is inherently connected to the model concept, describing objects,
relationships, and capturing time dependencies
• Consequently, a SML should be at least capable of describing the structure and
the behavior of a system
• A SML should support “views”, suitable to the various stakeholders
Systems Modeling Languages
• The behavioral description should be [35]:

• Capable of capturing process flow and control (a process can be seen as a
function that transforms objects)
• Capable of capturing observables
• Understandable
• Executable
• Capable of preserving behavior across
• Aggregation
• Decomposition
• Allocation
• A SML must possess:
• “nouns” to describe objects (actually “noun classes” to define Components, Functions, and
Requirements)
• “adjectives”/”attributes” to refine the description of the objects
• “verbs” to define relationships
• “adverbs” to refine the description of the relationships
• The behavior is usually described in graphical forms (diagrams)
Image source: [35]

Some SMLs:
• Object Process Methodology (OPM), adopted as an ISO standard
(OPCAT)
• Modelica
• Unified Modeling Language (UML)
• Systems Modeling Language (SysML)
Modeling languages
• In the following: SysML
References
1) James N. Martin, “The Seven Samurai of Systems Engineering: Dealing with the Complexity of 7 Interrelated Systems,” Proc. Of INCOSE 2004 – 14th Annual International Symposium Proceedings,
https://incose.onlinelibrary.wiley.com/doi/epdf/10.1002/j.2334-5837.2004.tb00509.x
2) https://sercuarc.org/wp-content/uploads/2018/06/Digital-Engineering-Strategy_Approved.pdf
3) https://journals.sagepub.com/doi/full/10.1177/1548512917751873
4) INCOSE HANDBOOK
5) https://www.wizata.com/knowledge-base/difference-between-digital-twin-digital-model-and-digital-shadow
6) https://www.oxfordinsights.com/insights/2023/7/19/exploring-the-concepts-of-digital-twin-digital-shadow-and-digital-model
7) https://www.challenge.org/insights/digital-twin-and-digital-thread/
8) Defence Acquisition University, cited by https://amses-journal.springeropen.com/articles/10.1186/s40323-020-00147-4
9) Digital Twin—looking behind the buzzwords, April 2018 edition of benchmark magazine. https://www.nafems.org/publications/benchmark/archive/april-2018/. Accessed 19 Feb 2020.
10) [eBook] Forging the digital twin in discrete manufacturing: a vision for unity in the virtual and real worlds. https://www.lnsresearch.com/research-library/research-articles/ebook-forging-the-digital-twin-in-discrete-
manufacturing-a-vision-for-unity-in-the-virtual-and-real-worlds. Accessed 19 Feb 2020.
11) https://amses-journal.springeropen.com/articles/10.1186/s40323-020-00147-4
12) https://www.techtarget.com/searchbusinessanalytics/definition/data-curation
13) https://www.dataversity.net/what-is-data-curation/
14) https://www.strumentazioneelettronica.it/tecnologie/analog-test/milano-capitale-dei-sensori-mems-20120622895/?start=2
15) https://cdn.comsol.com/product-new/mems-module/full/mems-module-social.png
16) https://www.appliedmaterials.com/il/en/semiconductor/semiconductor-technologies/mems.html
17) https://www.comsol.com/blogs/digital-twins-and-model-based-battery-design/
18) https://cdn.comsol.com/wordpress/sites/1/2019/02/digital-twin-concept-battery-pack.png
19) https://cdn.comsol.com/wordpress/sites/1/2019/02/digital-twin-deployment-example.png
20) https://cdn.comsol.com/wordpress/sites/1/2019/02/real-system-digital-twin-network.png
21) https://virtualdutchman.com/2018/07/02/model-based-the-digital-twin/
22) https://www.oxfordinsights.com/insights/2023/7/19/exploring-the-concepts-of-digital-twin-digital-shadow-and-digital-model
23) https://www.talend.com/resources/single-source-truth/
24) https://www.talend.com/resources/what-is-business-intelligence/
25) https://digitaltwinhub.co.uk/articles/articles/beyond-buzzwords-the-true-meaning-and-value-of-%E2%80%9Cdigital-twins%E2%80%9D-r62/
References
26) https://www.challenge.org/insights/digital-twin-and-digital-thread/
27) https://www.challenge.org/wp-content/uploads/2019/01/Digital-Thread.png
28) https://www.ibaset.com/expertise/digital-thread/
29) https://blogs.sw.siemens.com/xcelerator/2021/04/29/the-role-of-the-digital-thread-and-digital-twin-in-digital-transformation/
30) https://www.ibm.com/blog/digital-thread-vs-digital-twin/
31) https://inl.gov/digital-engineering/
32) https://www.baesystems.com/en-us/definition/digital-engineering
33) https://insights.sei.cmu.edu/blog/what-digital-engineering-and-how-it-related-devsecops/
34) Guide to SEBOK, version 2.8
35) David Long, Zane Scott, A Primer for Model-Based Systems Engineering, 2nd Edition, Vitech Corporation, ISBN 978-1-105-58810-5
36) https://en.wikipedia.org/wiki/Argument
37) https://ocw.mit.edu/courses/16-842-fundamentals-of-systems-engineering-fall-2015/resources/session-3-systems-modeling-languages/

Block 06 DE MBSE

Uploaded by

Copyright:

Available Formats

Block 06 DE MBSE

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Block 06 DE MBSE

Uploaded by

Copyright:

Available Formats

Digital Engineering and Model Based

• “Digital Engineering describes a holistic approach to the design of a complex

• Use of more sophisticated models (A3 Thunderbolt 2D->3D)

Image source: [14] Image source: [15]

Parameters may include:

• Image source: [18]

• Image source: [19]

• Image source: [20]

• Image source: [11]

Image source: [27]

• What is the difference between a model and a simulation?

Image source: [34]

Image source: https://www.slideshare.net/galleman/incose-vee-and-the-imp

• The behavioral description should be [35]:

Image source: [35]

34) Guide to SEBOK, version 2.8

You might also like