Highlights
HVVH is a new framework developed for Verification, Validation of HyperWorks products. This will help end users to quickly evaluate the software quality, performance, reliability, scalability, robustness and gain more confidence in HyperWorks products.
Main objective of this module is to accelerate customer’s process of software procurement, migration from one version of the HyperWorks to another version, quick identification and resolution of issues even at customer site.
This is an integrated end to end solution spanning across Pre-processor > Solver > Post-processor > Manufacturing covering most of HyperWorks products. With a single click user could look at the dash board reports decide on quality and further accept the product based on their own acceptance criteria. It can also quickly identify if there are any problems with any of these suite of HyperWorks products.
Working closely with many big OEMs’ and customers it is observed that while accepting new software products for production stringent guidelines are followed internally to certify the product. On many occasions time consuming process is followed in extracting such information to meet internal standards. Sometimes customer issues are difficult to reproduce, the main bottle neck is access to their confidential data and processes. With this framework we plan to overcome these situations and accelerate the approval process working with customers at their locations and also by mapping their workflow as required.
The key benefit is its direct impact on engineer’s productivity and drastic changes in production time. Early adoption of required technology and software products would lead to huge savings in terms of time and money. We continue to work with all the major customers in gathering real time application data and workflow information to enhance this process.
• | GUI and batch mode: HVVH is available as an end to end solution both in GUI and batch mode across pre-solve-post-manufacturing for HyperWorks suite of products |
• | CAE process flow: Simple CAE process flow is followed and users can use all or part of the module depending on the requirement at different stages of product development. |
• | Session file: Session file can be created for reuse from the details entered in the GUI. Session files can be saved, retrieved, appended and used for running in batch mode. |
• | Dash board reporting: HTML reports are published with HyperView Player (HVP) in place activation along with graphical display and validation, this will help end user for quick evaluation. |
• | Early design-FE data: From CAD data Finite Element (FE) model built in Inspire can be checked for solver compatibility (OptiStruct) by using solver check run. In addition actual solver results can be compared across different Inspire versions. |
• | CAD modeling and meshing HyperMesh: Identify loss of geometry information, comparison of CAD-CAD, CAD-FE, FE-FE at entity level, matched/unmatched, overlapped, intersected areas, with topo line including surface metadata. Consistency and accuracy of meshed geometry based on qualitative and quantitative assessment. Visualization of area difference through embedded HyperView Player (HVP). |
• | Solver compatibility HyperMesh/HyperCrash: It is important to determine the FE model built in HyperMesh/HyperCrash, and solver decks generated in the pre-processors are solver runnable before running huge jobs. This eventually saves lot of computational time in case of failure with solver runs. |
- | Compare the basic solver outputs accurately to identify the regions of failure. |
- | Ensure model integrity and accuracy of the data by suitable OUT file comparison (for RADIOSS and OptiStruct). |
• | Consistency of HyperMesh/HyperCrash interactive operations: This key feature could quickly assess the repeatability of model building (CAD modeling, meshing, model building etc.,) operations in HyperMesh, capture errors including segmentation errors and locate problematic area for quick debugging. |
- | This helps in quick assessment of new functionalities, features, APIS’ and work flow related activities. For HyperCrash the session file recording is extended to capture consistency of data, operation on entities, and functionalities of different APIs’ to limited extent. |
• | Model quality: Assessment is based on solver model check run, HyperMesh model checker, Quality Index for HyperMesh, default or customer specific model checker, and penetration checks for HyperCrash. |
• | Extent of solver coverage: Degree of keywords coverage in HyperMesh based on customer models, type of analyses are obtained. This is to identify most used keywords, unsupported and partially supported ones to enable faster prioritization of customer requirements. |
• | Data loss or deprecation of model data: Identify issue with import and export of solver data (Basic IO), and locate the problematic areas even at all include file levels for same version or across different HyperMesh/HyperCrash versions. Even identify the problems while comparing the pre-certified reference data. |
|
• | Solver result comparison: Solver result comparison at different levels starting at entity level, region, component or model level for different scalar, vector, tensor datatypes. User can use default or user defined tolerance values |
• | Reporting: Graphical display in HVP to identify different regions of failure, actual magnitude difference in values, difference contour, and difference curve. |
• | Interactive HyperView session: API’s are published that help assess the difference in results directly inside HyperView through the module including identifying the difference in contour values, plotting difference curve at entity/component level or any region (area of interest). |
• | Comparison of Time history: Across different solver version results (RADIOSS or OptiStruct) comparing plots all statistical details are published – supported post HyperWorks 14.0.120 - for PCH/A01 files and also for files converted to H3D using HvTrans |
• | Justification for discrepancy in results: In case of any difference in results to understand any discrepancy in results, model robustness and sensitivity analysis are available with an integrated approach. This could be due to software and hardware parameter changes. |
• | Model robustness and sensitivity analysis |
- | First we can qualify a model as reference model for sensitivity analysis and it can be used for further studies. |
- | Sensitivity analysis – base solver runs with different seed values for both RADIOSS and OptiStruct solvers are used in this analysis. |
- | Creation of sensitivity corridor for solver result comparison across different solver versions for RADIOSS and Optistruct. |
- | Detailed Response history analysis and Time History data comparison |
- | Statistical analysis with inference for product validation. |
- | Facility to study effect of different physical parameters and understand the shift in response and changes on the model/physical behaviour. |
• | Important NVH parameter evaluation: Modal Assurance Criterion (MAC) for any range of frequencies, MAC threshold are reported with correlation matrix and histograms. This can be used for result comparison across OS solver versions for NVH related analysis. |
|
• | Comparison of solver results: For any solver result of the whole model any datatype (tensor, vector, scalar) can be compared for different HyperView versions. All solver results supported in HyperView can be used. |
• | Comparison of Time history curves: Solver result time history data can be compared for different HyperGraph versions. Data files, template and session files are supported for all HyperGraph supported solver results. |
|
• | HyperForm: Full FE model setup, Basic IO, solver (incremental and one step) analysis and result comparison along with comparison across HyperView and HyperGraph versions are available. |
• | HyperExtrude: Full FE model setup, Basic IO, Solver (HyperExtrude and Tool deflection) analysis and result comparison along with comparison across HyperView versions are available. |
|
• | Packaged solution: It can be used for evaluation of HyperWorks suite of products and subsequently cut down product validation time from weeks to days or hours |
• | Quick decision making: Faster migration and/or acceptance of new HyperWorks products/versions: Currently long validation time is spent at customer end to meet internal standards/process for approval of new software/version this module will cut down this time significantly. |
• | Responsiveness to customer request and issues: To reproduce the problems that the customers face many times the difficulty is to access their confidential data and processes. These issues can be addressed with this module at customer end for faster issue resolution. |
• | Faster Design decisions: This will complement the effort of engineers with right combination of model building, simulation, analysis and data interpretation leading to faster design decisions. |
• | Future product evaluation: This helps users quickly batch run HyperWorks product(s), assess quality reports, results comparison and check overall quality of products. |
• | Automated system: Solver, platform and HyperWorks version independent system without any maintenance of scripts. |
• | HVVH currently supports following HyperWorks products: |
• | Platforms: Windows, Linux |
|