Open and Connected. Models constructed with the goal of an optimal and realizable architecture transition more easily to implementation.
A New Approach
Architecture-Driven Engineering (ADE) is a new term, but a descriptive one as product ecosystems become more complex. An optimized and validated architecture is critical before detailed design. This approach supports expanded product boundaries, rigorous product definition and sets the stage for a transition to implementation.
Benefits of Architecture-Driven Engineering
Extended product boundaries. Products today typically involve an ecosystem. Expand product boundaries and define the entire product ecosystem.
Model validation. The model offers a more rigorous product definition that enables validation through simulation and trade-off studies.
Traceability. The model history provides traceability eliminating the “how did we get here” experience.
Architecture-Driven Engineering Fundamentals
The model is created to achieve a robust and viable architecture that is analyzed and optimized with trade-off studies.
The model language based on SysML provides a relationship approach to product definition that is not possible with documents.
Open and Connected
Model development collaboration across team members and third-party ecosystem solutions are necessary.
Consider the Complete Product Ecosystem
When designing today’s complex products, the entire product ecosystem or system context must be considered. In the case of the video drone, the system context would include the drone, remote control, phone app, GPS satellite, and the operating environment. ADE delivers a product architecture model encompassing the product ecosystem.
Creating the Design Envelope
The product ecosystem requirements are decomposed into functions, requirements, and architecture. After decomposition, the model must provide engineering with a design “envelope” for each electrical and electronic subsystem or component. Based on the assigned envelope, the design team proceeds with implementation.
Architecture Creation and Validation
As the product ecosystem definition progresses, a physical architecture is needed to allocate functions and requirements. As the architecture is analyzed and trade-off studies are conducted, an optimal architecture will emerge for detailed design.
Connecting the Model to Detailed Design
Today’s biggest process challenge is to connect the model to detailed design without a manual translation of the model into documents. Zuken’s solution is to transfer the architecture to detailed design while other aspects of the model are exposed for viewing. The model becomes part of the product life cycle.
Features and Benefits
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.
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.
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.
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.
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.
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 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
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.
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.
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.
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.
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.