Safety Tools for Crash Interface

Post Processing:

1. Pedestrian Impact

Implementation of HIC for adult/child impact types for different regulation

Report generation for impact points

Loading of result files asynchronously to improve the performance

2. IIHS

Intrusion calculation with front 40% offset, narrow offset, and side

Report generation – multiple iterations [overlay]

Support of additional points to study the intrusion

3. MPDB (mobile offset progressively deformable barrier )and Door intrusion

Support of OLC (occupant load criteria) calculation and Standard Deviation

Intrusion calculation for the side door after crash using displacement values

Roles and Responsibilities:

Getting the specification from AE’s/PM’s for the tool, use cases and workflow

Design of UI using TCL/TK and core functionalities using C++

Bug fix and unit tests

Collecting feedback from filed engineers to feature usability

Guiding a team member on this tool

Hyper view/ hyper graph apis to get the result data

Safety tools are the tools which are used to study safety of The vehicle, occupant, and pedestrian.

First we need to setup the vehicle and impacts to study different types of crash. After completing the model setup, solver will run the job and dump the requested output in respective solver format. These are all very huge file size and needs to interpreted using post tools such as hyper view (data with animation) and hypergraph (only result information). From here we have to start interpreting The results based on regulation to get the final rating card for the test.

Safety Tools for Crash Interface

1. Pedestrian Impact

Model setup of getting the impact points on hood, side bumper, windshield.

Positioning the impact at impact location to study injury criteria in post result data

Workflow design and user interface implementation

Support of different regulation such as Euro 8.0, Euro 8.2, UNR-127

For different impacts such as Adult/Child, Lower/Upper Leg

2. FMVSS201

Positioning of adult/child dummy on impact points by contact method/target method

Workflow design and user interface development

Setup the model to study head injury criteria on the panel area of the vehicle

Roles and Responsibilities:

Getting the specification from AE’s/PM’s for the tool, use cases and workflow

Design of UI using TCL/TK and core functionalities using C++

Bug fix and unit tests

Collecting feedback from filed engineers to feature usability

Guiding a team member on this tool

Abaqus solver has developed a new modelling technology based on part and instancing.

This will help the engineers to develop the product at very fast and more structured.

Hypermesh was having this feature, and was introduced later.

For complex models such as aircraft structure will have many duplicate components.

By this technique we will only one component development.

Duplicate will have the same design parameters, with different transformation.

Support of Reader and export template for parts and instance in Hypermeh.

We made the engineering view as a common browser across all the engineer developers.

So that all the entities will be represented in a engineering terms and not by solver terms.

This browser became standard across all the solver such as lsdyna, radioss, nastran, etc.

Roles and Responsibility:

Development of legacy reader and export for part instance

Co-ordination with different teams for support of various other infrastructures to support part and instance

Such as browser team, assembly model team, core team, graphics team

Performance improvement in legacy export

Using c/c++, design patterns for implementation

Hyper mesh supports many solvers data, and is used extensively for fe model setup on solver basis.

Abaqus is one of the interface which is used for most of the non crash related analysis.

· Support of many keywords into hypermesh for Abaqus interface

· Enhancement of Step Manager and Contact tool for Abaqus

· Conversion from one solver to other solver without losing data

With this same model setup can be used to get results in different solver.

Reader interface was developed using inter process communication.

Roles and Responsibility:

Unit tests coverage for changes in reader and export

Mentor team of 3 developers on development of reader and export mechanism.

Inter team dependent development co ordination

Co ordination with Program management, data mapping in hyper mesh

Using skill set of c programming for legacy support

The shortest distance between concept and reality for wire harness design is

Altair's HarnessLink, an integrated suite of wiring harness and system design

tools that accelerates the wiring process from functional design through to

physical build. With the competitive pressures for greater system complexity,

lower costs and shorter development times, schematic capture tools can no

longer support users in satisfying the demands of the marketplace. Text entry

with schematic viewer integration enables instant generation of logical and

physical schematics within the Altair HarnessLink environment, without man-

ual drawing.

A single tool set now provides a place for the collaboration of systems, wiring

and component engineers. It means that HarnessLink can give users a more

effective way to cascade system and subsystem specifications from project

requirements HarnessLink can also helps users choose components, gener-

ate schematics, develop 3D wire routing and create 2D harness prints.

Roles and Responsibility:

Implemented symbol diagrams/library for schematic viewer

Migration of MS-Aceess DB to PostgreSQL – new process

Integrating Schematic viewer and PostgreSQL Database

New design and implementation of UI, with tcl/postgress and tk library