Eliminate documents. The model is connected to the design process eliminating the need for document generation.
Model-Based Engineering (MBE) is the implementation phase of product development. The model artifacts and associated architecture must seamlessly transition to detailed design. The process must always preserve the connection between ADE and MBE. A disconnected model negatively impacts ROI.
Benefits of MBE
Design envelope. The model provides engineering with an implementation “design envelope,” providing freedom and guidance to the development team.
Eliminate errors. Verification events defined in the model assure the consistency between the design and implementation.
Traceability. The model history provides traceability eliminating the “how did we get here” experience.
Connecting to Detailed Design
The model provides a relationship approach to product definition that is not possible with documents. The more robust the product definition, the fewer design errors.
The model must be connected and utilized by the implementation and test teams. Model relevancy throughout the product life cycle is key to success.
As products become more complex, the risk of design intent and implementation divergence becomes more real. Verification events provide consistency checks throughout the product life cycle.
Transition to Detailed Design
The biggest challenge today for model-based design is transitioning to implementation or detailed design. The design envelope for each subsystem or component is directly transferred and exposed to the design teams for implementation. The model remains connected to the design process.
Connected Wire Harness Design
The GENESYS Connector provides a direct link between the model and E3.series for wire harness design. Model artifacts are directly transferred and exposed in E3.series creating a design envelope for the implementation team.
Connected 3D PCB Design
The GENESYS Connector will provide a direct link between the model and CR-8000. A PCB subsystem architecture model is transferred to CR-8000 while exposing other model artifacts. Upon architecture validation, the model enters a 3D multi-board PCB design process.
Design Verification Events
Verification gates or events are placed at critical design phase boundaries that include architecture, release to manufacturing, first article inspection, and subsystem test. Each gate contains verification requirements for evaluation and the model updated with a status. These gates ensure that the implementation is consistent with the model.
Digital Engineering eBook
This eBook describes an MBSE based process for Electrical and Electronic design. The eBook begins with model content and structure with the purpose of implementation and the need for a “design envelope”.
The biggest challenge in MBSE gaining broad adoption is making the model relevant through the product life cycle. Learn how you can overcome this daunting hurdle while maintaining the model as the single source of truth.
Digital Engineering Process
The Digital Transformation is being embraced by companies around the globe with the expectation of improving product development. Zuken’s mission is to deliver on that expectation with a Digital Engineering design process for electrical and electronic subsystems.
Model Creation Highlights
Model Based Design
The process is based on a model built upon relationships. The model replaces 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.
Unified Design Model
Relationships can be built textually or graphically. The model is stored so that views are generated from the model. Change the model and all the views will automatically incorporate the change. View synchronization is automatic.
Leverage SysML Views
GENESYS comes ready to deliver SysML representations out of the box. If you need to leverage the power of SysML but want the flexibility of an integrated approach, GENESYS brings these elements together so you don’t have to compromise.
The architecture for the electrical and electronic subsystem is defined in the model and provides the design team with an implementation structure.
The product must meet specific performance, safety, and design requirements. The requirements are contained in the model and associated to design elements.
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.
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.
Create verification events comprised of a series of verification requirements that can, in turn, contain multiple requirements. Verification events create approval gates in the design process.
The Excel Connector provides read/write access to the design information in the model such as requirements, structure, verification requirements, etc. For instance, requirements can be added to a design element through the Excel Connector.
Integration with DOORS
GENESYS provides a bidirectional connection to DOORS, a common requirement capture system. The bidirectional link allows for easy movement of requirements between GENESYS and DOORS.
Primer for Model-Based Systems Engineering
Systems exist wherever these three are present: parts, relationships, and a purpose.
The 2nd edition of "A Primer for Model-Based Systems Engineering" addresses the elementary principles of MBSE in the context of practical illustrations. The book addresses the foundational concepts in a manner designed to benefit the newcomer and experienced practitioner alike. The brief excerpts below are drawn from across the primer, providing a sense of the scope and flavor of the MBSE principles discussed
Webinar - Introduction to GENESYS 7.0
In releasing the latest version of our powerful model-based systems engineering software—GENESYS—Vitech enhances the capabilities of this robust tool. In this webinar, Mark Malinoski will highlight:
The enhanced connection of architecture and analytics with the new ModelCenter MBSE connector
New model management capabilities, including reuse of patterns and library components
An alert framework notifying users when their selected aspects of the model change...
The Digital Thread is a foundational element of a successful Digital Engineering implementation. Digital conversations involving procurement, design, manufacturing and field service replace email and paper documents. Decisions and rationale are captured and provide traceability.
Digital Engineering requires a model-based design process that begins in Systems Engineering. Zuken acquired Vitech Corporation, a leader in Systems Engineering practices and MBSE solutions, with the intent of implementing an E/E model-based design process.