As product complexity grows, so does the risk of divergence and the need for design verification events. The product implementation may have strayed from the original product model specifications lowering the business value. The in-process design must be verified against the product model at each design phase to lower risk and maximize business value.
Design verification is built upon verification events that check the consistency before moving to the next phase. For instance, an architecture design review should be successfully completed before a detailed design. The review activity should be captured by digital conversations as part of the Digital Thread.
Product requirements have a time or design phase consideration. For instance, a weight requirement needs to be checked during the architecture phase, the design phase, and the release to the manufacturing phase. The requirement test may use a different method at each phase, but it must be done.
In some cases, requirements can not be met. For instance, a PCB subsystem may not be able to hit a cost constraint because of the functionality requirements. This would require the model owner to re-allocate more dollars to the PCB Subsystem or reduce functionality.
As requirements are verified at each design phase, a record is created, providing traceability for each requirement. If a PCB subsystem or wire harness is too heavy or costs too much in the final product, a requirement verification history will provide traceability to where the model and implementation diverged.
The product model tends to become disconnected from the development process and ultimately the product life cycle. As the model becomes disconnected so does the risk of divergence. Design verification gates keep the model relevant throughout the product life cycle. The result is delivering the intended product business value.
Maintaining business value throughout the design process is always challenging. Design decisions increasing variance will impact business value. Strong product compliance with the model maintains business value.
GENESYS supports Verification Events which can be assigned to process milestones. The event is comprised of verification requirements that must be passed to proceed.
Verification requirements can consist of one or many requirements. The Verification Requirement is associated to a test activity. A test activity for a design review is very different than an inspection of a first article PCB. Test activities are defined to support the event and the requirements.
The Digital Thread will capture the historical record of each verification event. The event is decomposed into activities (e.g., PCB Design Review) and each activity is decomposed into multiple conversations (e.g., BOM review, power review, mechanical review, etc).
Product compliance preserves the product model as the single source of truth. As verification requirement tests pass or fail, that status is updated to the model. The product model can provide a history of the design verification history.
Deploying a Digital Thread product like Anark provides the conversation and decision history needed to understand any variance to the product model. Any variance to the product model impacts business value and should be thoroughly understood.
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.
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.
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.
