Traditional simulation and modeling workflows for products and systems design often use a manual steady-state analysis approach and require extensive time for model library development, are often dependent on a single user, and do not support modern shift-left collaboration workflows. When model simulation workflows are siloed, they not only extend design cycles but also deprive …
Dassault Systèmes’ 3DEXPERIENCE: A Progressive Approach to Modeling and Simulation
In a recent post, we discussed the challenges associated with a traditional approach to simulation where engineers and analysts work in silos using unintegrated tools. When team members can’t collaborate effectively, companies must contend with inaccurate or incomplete data that cause delays and increased costs. In order to address these issues, companies need to take …
Aras Innovator: The Advantages of Accessing Simulation Data in Your Product Lifecycle Management Solution
As part of technology-led initiatives, many engineering organizations have adopted both simulation and product lifecycle management (PLM) to help drive and optimize product development efforts. Today, these companies often must rely on a variety of simulation products to meet their needs. Yet, engineering change orders (ECOs), which can come from any step in the product …
The Lifecycle of Systems Simulation
Manufacturers are using systems engineering approaches to mitigate the complexity of developing increasingly sophisticated products. Systems simulation is a key component of such efforts.
Engineering Co-Design Across Domains
As products get smarter and more interconnected, engineering co-design is more critical than ever. How can you improve your organization’s capacity for co-design?
What is Modelon Impact?
What is Modelon Impact and how is it different? If you’ve been working on system simulations for any amount of time, you’re probably familiar with Modelon. They’ve offered this library of components that you can use for system simulations for quite some time. They’re really well known for the accuracy of those components, which obviously …
Validating Systems Architectures from the Bottom Up
Products are becoming more feature-rich and more complex. Many organizations increasingly rely on systems engineering. In this post, I’ll dive into some common issues with developing systems architectures. I will focus on how to increase collaboration between detailed design and systems engineering teams through a validation step right before detailed design starts.
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.
Systems Engineering Enables Traceability for Electrical and Electronic Design
Systems engineering practices help organizations mitigate and manage product complexity. When applied to electronics and electrical systems, systems engineering takes on a whole new meaning. Using this approach, teams break down a product’s requirements and functions with a high degree of granularity and allocate them to functions, logical architectures, and physical items. In doing so, they gain traceability that enables them to explore the impact of any design changes on requirements and make the best decisions possible.
This post explores some of the different areas where systems engineering makes a difference and how systems engineering enables traceability.