# Presentation: 577616

## Vehicle Simulation ManagementIndustry Examples

***Dr. Michael Schlenkrich***
***MSC.Software***
***March 31, 2004***

## Industry Challenges

**Normally in place and established:**
**PLM strategies**
**Relatively mature PDM for CAD**
**Advanced simulation technologies**
**Generally ****not**** in place, but recognised as needs:**
**Repeatable, standardised processes for simulation**
**Ready, structured access to all simulation data, enterprise-wide**
**Seamless integration between “islands” of existing systems and disciplines**
**Systematic means of comparing numerical simulation and physical simulation (test) results**

## CAE: Trends and Impacts

***CAE: Trends and Impacts***

***Industry Trends***
- Product Variant
- Style & Comfort
- Boundary Conditions
- Government Regulation
- Statistical Verification
- Stochastic Simulation
- Discipline Combination
- Multi Disciplinary Optimization
***IT Trends***
- Price
- Performance
- Maturity
- Functionality
***Impacts***
- Number of Simulations and Variants
- Complexity of Simulation Models
- Communication and Synchronization
- Data Volume

**Requirements:**
** **_**consistent**_** data management**
** ****easy transparent access to data**
** ****efficient management of **_**huge amounts**_** of data**

**Not only**
**Storage**

****

****

****

****

****

****

****

****

****

****

****

****

## Focus

**Management of the Processes and Data for Functional Data generated by physical test and simulations in the VPD**
**Goal:**
**Streamline the processes, increase the efficiency**
**Provide more impact of simulation on design:****Enable: Function Driven Design**
**Establish a knowledge base for functional data**

## SDM Initiative

**MSC has an initiative to create an integrated solution for managing functional processes and data.****It is referred to as Simulation Data Management (SDM) initiative**
**Goal:****Help customers achieve an functional driven design environment for VPD**

## Creation of Functional Data

**Physical Simulation**
**(Test) Process**

***Creation of Functional Data***

**Numerical Simulation Process**

**Pre-Process**

**Solve**

**Post-Process**

**Notes:**
This slide should state as clear as possible the main goals of SDM.

The order 1. .. 3. Then final, should already hint to the staging (phasing) of our approach.

Comment on Physical Test:
While our focus will not be (at least for now) to address process improvement in physical testing, we do want to capture and address the consistent storage of the physical test data in our SDM Knowledge Base! We also want to facilitate the effective communication of functional data (both from simulation and test) into the PLM.

Comment Product Life Cycle versus Product Development Process:
While the main focus, contribution of simulation and test data will be in the development process, we should (in the general positioning) restrict ourselves to just that phase in the product life cycle. Specially as respond to product warranty issues  
Improve infrastructure support for the simulation process and avoid loosing (bleeding) simulation knowledge
Improve integration with the rest of the product development process and positively affect production and post production support. In short: Simulation-Based PLM

1. Enhance the Simulation Process:
Ensures consistent use of auditable data
Enables experimentation-based innovation
Enables process integration

2. Create a consistent functional knowledge database
Actually, this is the central point of SDM, but it partially follows, the simulation process improvement.The emphasize here is, that we focus on functional knowledge management, which is a more broader scope than the management of the PLM functional data 

3. SDM enhances Product Development Process:
Enables faster, easier access to simulation results
Creates simulation knowledge base

Final Goal: Enables Function-Driven Product Development
Taking all what it needs into account, this is a very ambitious long-term goal.
It doesn’t imply, that we recommend at totally function-driven design, but that we want to build an environment, which provides as immediately as possible the functional information.

## Automotive Simulation Data

- Crash

- Noise
- Vibration
- Harshness

- Occupant
- Safety

- Computational
- Fluid Dynamics

- Ride &
- Handling

***CAD/VPM***
***Database***

***Test***
***Database***

## Key SDM References

**3 years in production**
**10,000’s of simulations imported / 10’s of TB of Data**
**Supports a 1000 CPU compute environment**
**Accessed and used by suppliers (on-site and remote)**
**Includes Batch Assembly Process**
**Includes Integration with PDM System (PDM-SDM-PDM)**

**2 years in production**
**Combines occupancy (rigid-body) and Crash (FEM) (incl. head-impact FMVSS201) simulation**

## SDM Complements PDM 

***SDM Complements PDM ***
***The Inner and Outer Loop***

**Materials Models**
**Templates**
**Loads**
**Boundary Conditions**
**Other External Parameters**
**Requirements**

**SDM Environment**

_***Bill of Design***_
_***(BOD)***_

_***Bill of Analysis***_
_***(BOA)***_

**Technology****Process Oriented Modeling**

## Sample CAE Process

**Models**

**Meshes**

**Load Cases**

**Pre-Processing**
**Applications**

**Plots**
**Cross sections**
**Movies**
**Images**
**Values**

**Individual****Files**

**Input **
**Decks**

**Compute**
**Applications**

**Simulations**

**Output **
**Decks**

**Post-Processing**
**Applications**

**Solver**

**Pre-Processing**

**Solving**

**Post-Processing**

-  **Reporting**

**Assemble report**
**Compare and annotate****Post-processing results**
**Movie-merges**

## Associated SDM Process Map

**Models**

**Meshes**

**Load Cases**

**Pre-Processing**
**Applications**

**Plots**
**Cross sections**
**Movies**
**Images**
**Values**

**Individual****Files**

**Input **
**Decks**

**Compute**
**Applications**

**Simulations**

**Output **
**Decks**

**Post-Processing**
**Applications**

**Solver**

**Pre-Processing**

**Solving**

**Post-Processing**

-  **Reporting**

**Assemble report**
**Compare and annotate****Post-processing results**
**Movie-merges**

- Meshes

- Assemble

- Model

- Combine

- Loadcase

- InputDeck

- Solver

- Output

- Extract(Postprocessor)

- Cross-Section

- Curve

- ReportCreation

- Report

## Audit Trail Viewer

## Prepared for Data Mining

***Prepared for Data Mining***

*Transformation from operational Knowledge Base:*
-  Direct extraction, mapping and cleaning steps
-  SDM data model inherently carries all the information required for data mining
-  The data model has the critical information on:
-  Association (what belongs in one row)
-  Equivalence (what belongs into a column)
*Detailed Research and Analysis*
- Find Clusters and Association
- Analyze Dependencies and Impacts

**Transformation**

- SDM- Knowledge Base

**Data Mining**

**Clustering**

## Conclusion

**Manage Data and Processes together**
**Ensure consistent use of the ‘best practices’**
**Establish a knowledge base of consistent data**
**Create standardized interface into the PLM **

***Thank You***

## Architecture of a Large Deployment

***Architecture of a Large Deployment***

**NQS**
**NFS**
**RCP**

**Application Server**
- CAE Post-Processing

**Storage System**
-   File Server
-   Backup Server
-   Archive System

**Compute Server**
- CAE Solving

**Database Server**
- CAE Data Mgmt.

**Web Server**
- CAE Portal

**Dedicated**
**CAE Server**
- e.g. Visualization, PDM, Legacy Systems

- Enterprise Simulation Portal

**HTTP, FTP, RCP**

## WIP

***In More Detail...***

**Materials Models**
**Templates**
**Loads**
**Boundary Conditions**
**Other External Parameters**
**Requirements**

**SDM Environment**

**Bill of Design**
**(BOD)**

**Bill of Analysis**
**(BOA)**

**Virtual Product Definitions in PDM Vault**

**WIP**
**(work in progress)**
**>80% will never be released:**
**   ****- method/model validation runs**
**   ****- false ‘what if’ attempts**
**   ****- intermediate optimization results**

**Compile the product relevant data from simulation**
**Create a Bill of Analysis:**
**   ****- BoA for design validation simulations**
**   ****- BoA for design trade-off studies **
**   ****- BoA design improvements suggestions**

## Returns on Investment: Example from the Automotive Industry 

**Efficiency: Inner Loop**
**Make the analyst more efficient:**
**Increase simulation throughput**
**Reduce turn-around time**
**Increase quality and reduce errors**
**Consolidate and automate****best practice procedures**

**Example:**
- Time-Saving per Simulation = ~ 2 hours
- 150 Simulations per Engineer per Year
- 		**Efficiency Increase: ~15%**
- 50 Engineers (loaded costs $200k/year)
- 		**Return: $1.5M / year**

**Example:**
- Reduce the turn-around of an assessment study from 3 weeks to 1 week:
-      **Product brought to market faster -** **$$$**

## Pedigree and Context Management

***Pedigree and Context Management***

- Powerful queries enabled on **all **simulation data and pedigree

## Engineering Core Competency

**What is ****Engineering**** **_**Core Competency**_**?**

**Actual Data?**
**Available Storage?**
**Right Software Application?**
**Best Compute Performance?**

**Correlation to Target?**
**Fit Form Function?**
**Technology Performance?**
**Best Product Integration?**