MBSE for Electrical Subsystems

Transitioning from the Model to Implementation

MBSE for Electrical Subsystem Design

MBSE for electrical subsystem design will be one of the cornerstones for the adoption of Digital Engineering practices.  The model must be decomposed into electrical subsystems that can be realized through implementation.  Programmatically moving the subsystem to detailed design is a vital step for success.  Maintaining model relevance through the product life cycle enhances MBSE ROI.

Model Realization

Model Relevance

The model is programmatically transferred and exposed to the design team.

Design Envelope

The model provides a design envelope for the design team.

Model Changes

Model changes are sourced from Systems Engineering.

Single Source of Truth

This methodology preserves the model as the single source of truth.

Model Content Guidance

The optimal model content for electrical subsystem design is a reflection of your design process.  The model is used to define the design envelope and not the implementation.  Manufacturing part numbers and wire gauge are not typically not part of the model. Weight, cost and other requirements create the design envelope.

Model content

MBSE transition to detailed design

Transitioning to Detailed Design

The design envelope moves from GENESYS to E3.series through a model importer.  The import programmatically moves the logical architecture into E3.series to begin implementation.  The model interfaces will be converted to wire harnesses by the design team.

E3.series has a connection back to the model so the design team can see requirements, diagrams, and parameters.  This information is only exposed to the design team and not transferred to preserve the model’s integrity and a single source of truth.

Any design verification requirements that can not be met are communicated back to Systems Engineering via a requirement status.

Architecture Design and Verification

The model presented to the design team contains requirements and structure.  The design team must verify that the design envelope can be realized through implementation and that it is not over-constrained.  The architecture must be verified against the model prior to going into detailed design.  If a weight, power or cost requirement can not be met at the architecture phase, the discrepancies must be resolved with Systems Engineering before proceeding.

Design and Verification for MBSE

updating the digital engineering model for MBSE

Updating the Model

A Digital Engineering process requires that the model remain relevant throughout the product life cycle.  Making the model relevant involves recording the verification requirement status at each design phase or verification gate.  Systems Engineering or management can review the verification requirement status at each gate to determine the progress of the development process.

MBSE Data Management

Digital Engineering requires the elimination of paper documentation and a data management ecosystem.  Maintaining a single source of truth and minimizing the duplication of data across systems is paramount to a successful Digital Engineering process. The MBSE data management ecosystem consists of the MBSE tool, an Engineering Data Management (EDM) system, a PLM system and a Digital Tread backbone for digital communications.  Each data thread serves a specific purpose and should remain separate.

data mangement threads for MBSE

Features and Benefits

Model Creation

Model creation using GENESYS from Vitech provides the ability to connect to Zuken’s E3.series solution for wire harness design and manufacturing.  Following design guidelines, while utilizing GENESYS provides a programmatic path to implementation while maintaining model relevance through the product life cycle.

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 Content

Realizing the model in the electrical and electronic domain requires a logical structure of design elements with the associated behavior and requirements. 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.

Transitioning to Detailed Design

Once the design envelope is defined for the cables, the architecture composed of blocks and interfaces transfers to E3.series. The requirements, constraints, and diagrams are exposed and viewable from E3.series.

Exposing the Model to Design Team

The design team will be able to see diagrams, requirements and parameters from E3.series.  The data is not transferred to E3.series to preserves the single source of truth of the model.

Architecture Verification

Architecture verification is a design step prior to detailed design where a partial detailed design is used to verify model requirements can be met at a 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.

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 insures 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