Model-Based Product Development

MBSE: Working with Digital Models
Menu

MBSE for Electrical and Electronic Design

The digital transformation of engineering and production promises a sustainable improvement of business efficiency and profitability. A recent IDC study showed that 90% of small and medium-size businesses are budgeting for the digital transformation and 73% have begun the process.

The Benefits of Model Based Engineering

Increased Confidence

Design data and decisions are traceable providing history and documented variance to plan. Minimize risk

Better Understanding

The model-based design offers multi-discipline requirements, behavior, and architecture defined in a single source of truth

Informed Decisions

Through communication tools, conversations can be associated with technical data packages for signoff and traceability.

Better Communications

A key function of the Digital Thread is to enhance communication through online conversations spanning internal and external organizations.

Model Relevance Through The Product Life Cycle

The model must remain relevant throughout the product life cycle. This is one of today’s biggest challenges. The model typically becomes a Systems Engineering artifact and has limited use through the development and manufacturing process.  A Digital Engineering process keeps the model relevant through the product life cycle providing ROI benefit.

MBSE transition to detailed design

Creating The Design Envelope

The system-level model is decomposed into electrical and electronic subsystems for implementation.  Each subsystem is composed of sensors, ECU’s, interconnects, etc.  Each of these design elements must be defined in terms of a design envelope which provides the design teams with the implementation parameters.  Verification requirements are made against the design envelope to assure that the implementation fulfills the intent of the model.

Design Verification Gates

The model-based design has verification gates to ensure that the implementation reflects the model definition.  The verification gates are comprised of design reviews, trade-offs, changes and ultimately approval.  The digital conversations behind those activities and approvals become part of the digital thread. Verification gates are placed at critical design phases that include architecture, design, first article, and subsystem.  Each gate requires a status update in the model.

Anark digital thread communication

Digital Thread Communication

Digital Engineering requires a digital communication mechanism to replace paper trails and documentation.  A robust digital thread implementation provides a browser-based communication built on activities, conversations, groups, and data.  All digital activity that can span the product life cycle is captured and can provide traceability.

The Digital Engineering Process

Model Based Design

The process is based on a model built upon relationships. The model replaces a document-based design. The model is typically created by the Systems Engineering team who converts system purpose into structure, behavior, and requirements.  The model is considered the single source of truth.

Model Relevancy

The model must remain relevant throughout the product life cycle. This is one of today’s biggest challenges. The model typically becomes a Systems Engineering artifact and has limited use through the development and manufacturing process.  A Digital Engineering process keeps the model relevant through the product life cycle and operates as a single source of truth.

Model Decomposition

For the purpose of realizing the model in the electrical and electronic domains, the model must be decomposed into E/E subsystems. These subsystems are further decomposed into functional elements as Electronic Control Units (ECU), sensors, busses, and connections.

Model Creation and Content

Realizing the model in the electrical and electronic domain requires a logical structure of design elements with the associated behavior and requirements. Model creation can be done with Vitech’s GENESYS product with the appropriate guidelines for model content.  For instance, the model does not typically contain specific component identification such as part numbers.

Design Envelope

When the design transitions from System Engineering to the implementation team, a design envelope must be clearly defined. The design team then knows what are the acceptable parameters in terms of cost, weight, size, power, etc.

Architecture Verification

Architecture verification is a design step prior to a detailed design where a partial detailed design is used to verify model requirements that can be met at high confidence. If a requirement can not be met at this phase, Systems Engineering must alter the model in the context of the entire system to enable a realizable implementation of the mode.

Transitioning to Detailed Design

Once the design is verified at the architecture level meaning the verification requirements are met with high confidence, the design can move to detailed design. At this point domain-specific electronic and electrical design practices and tools are used to design a manufacturable product.  Learn more about transitioning to electrical design.

Design Verification Gates

The model must remain relevant through the product development process. This is accomplished through verification gates which are comprised of a set of verification requirements. The design can not proceed to the next development phase until the gate requirements are satisfied.  This ensures the product is consistent with the model.

Model Verification Status

As the design moves through each verification gate, the model must be updated to reflect the verification requirement status. This allows Systems Engineering to monitor the design progress in terms of meeting verification requirements. As the design progresses through the implementation process, Systems Engineering has a window into its model consistency.

Digital Thread

Throughout the Digital Engineering process, discussions that lead to decisions must be recorded and retained for traceability. The Digital Thread provides the mechanism to hold those critical digital conversations.

Related Resources

  • Blog
October 15, 2020
Requirements Traceability in an MBSE Environment

The complexity of electrical and electronic (E/E) systems is accelerating across multiple industries and sectors. Manufacturers are adapting their design and development approaches to meet the changing requirements of advancing electrification.

Read now
  • Blog
September 24, 2020
Is Your Product Development Process Infected?

COVID has not only been disruptive to our daily lives but now we’re seeing the effects on our work lives as well. Company operations have had to adapt to accommodate a workforce suddenly no longer in the office. Companies are facing new challenges, from remote tool access to the purchase and distribution of new online tools.

Read now
  • Webinar
September 23, 2020
MBSE for Wire Harness Design

This webinar will discuss the challenges and best practices of creating a MBSE model for the purpose of wire harness and Electronic Control Units (ECU’s) implementation.

Read now
  • Blog
September 17, 2020
Validating Systems Architectures from the Bottom Up

Thanks to advancing technology, products are becoming more feature-rich and in turn, more complex. They must incorporate sophisticated electronic and electrical systems to provide the interconnectivity and user experience modern consumers demand. As a result, many organizations increasingly rely on systems engineering.

Read now
  • Blog
August 13, 2020
Two Design Approaches – Will MBSE Design Prevail?

Products are increasing in complexity at an astonishing rate. Smartphones are just one example: today’s devices combine the functionality of yesterday’s phones, cameras, calculators, and pagers and place desktop applications and internet browsers in the palms of our hands. Advancing electrification, mass miniaturization, and IoT-driven digitization are making a vast range of devices smarter and smaller. To cope with these changes, manufacturers must transform the way they develop complex systems. This post compares and contrasts the traditional and modern approaches to developing and verifying products.

Read now
  • Blog
July 30, 2020
Systems Engineering Enables Traceability for Electrical and Electronic Design

There’s no doubt about it: products are getting smarter. And that translates to increasing complexity for manufacturers. Traditional mechanical products suddenly require cabling and wiring, internet connectivity, and embedded software to function.

Read now

Got a Question? - Contact Zuken today

For more information on how Zuken can help your design process, contact Zuken today.
Contact us today