andrea petri

32
SIMULATION LIFECYCLE MANAGMENT Andrea Buda Petri Makkonen

Upload: pedro-parraguez

Post on 11-Mar-2016

235 views

Category:

Documents


1 download

DESCRIPTION

SIMULATION LIFECYCLE MANAGMENT

TRANSCRIPT

Page 1: Andrea Petri

SIMULATIONLIFECYCLEMANAGMENT

Andrea BudaPetri Makkonen

Page 2: Andrea Petri

Why SDM is an Hot Topic ?

06/21/10

….10-15 years ago

NOW

Page 3: Andrea Petri

Considerations

06/21/10

SIMULATION CAPABILITY

DATA GENERATED > Very High Volume!

WILLING TO SIMULATE (CAE like CAD 30 yeas ago)

LACK of METHODS to handle this avalanche of dataAnd even more important….

Simulation RESULTS HIGHLY DEPENDS ON SMART ANALYST

Page 4: Andrea Petri

Considerations

PROCESS and METHODS variability

- Inconsistent use of methods and tools- Inability to share methods and process in “managed” way- Lack of audit trail for simulation

Simulation RESULTS > HIGHLY DEPENDS ON SMART ANALYST

Page 5: Andrea Petri

Manually intense and ripetitive tasks- Load case and simulation setup- Post-processing and reporting

Considerations

WRONG TIME INVESTMENT

Page 6: Andrea Petri

This situation has lead to….

Simulation is essentially used to VERIFY PROPERTYBut the its real potential can achieve:

Simulation Driven Product Development

Product Optimization

Page 7: Andrea Petri

SERVER SIDESUPPORT FOR DATA MANAGMENT

Vendor independentSOLUTION FOR APPLICATION INTEGRATION

Vendor independentCONFIGURATION of PDM(Windchill / Teamcenter)

BEST PRACTICE IN CAE

REUSE

STORE

Scripting

SimulationProcess

WorkflowLifecycle

Users Roles

SimulationTaskSimulationTask Data Model

CAE Resources Library

Documentation Templates

Page 8: Andrea Petri

SERVER SIDE SUPPORT FOR

DATA MANAGMENT

Page 9: Andrea Petri

Architecture

?Really Necessary

Page 10: Andrea Petri

Any system managing simulation information must show NOT only the final answer, but show the CONTEXT

that is used to get that answer.

Capturing the CONTEXT

Page 11: Andrea Petri

Capturing the CONTEXT: METHODS

Capture the analyst/company BEST PRACTICE To achieve a certain output given a certain input given a certain CAE tool

Page 12: Andrea Petri

Capturing the CONTEXT: PROCESS

STORE, DISTRIBUTE and MANAGE these “best practices”allow others designers, analysts, enterprise stakeholders toREUSE IT assuring the QUALITY OF RESULTS they deliver.

Page 13: Andrea Petri

SDM

Con

text

PDM

Con

text PRODUCT LIBRARY

-CAD Parts-CAD Assembly

-CAD Parts-CAD Assembly-Templates (any kind)

Geo

met

ry In

form

atio

n So

urce

Simulation ProcessSimulationTaskN

SimulationTask2SimulationTask

Analyst

CAE Catalogue

FEM MBS CFD

- Models- SolverConfig- Else

Domain Indipendent

-Materials-Else

Chief AnalystSimulationTask Request

SimulationTask Approval

Publish

Page 14: Andrea Petri

1 to N

SAVE ALL the necessaryFor the calculation

SAVE ALL the necessaryTo ReRun the complete Analysis

After a PurgeAllRun()

ATTRIBUTES

BEHAVIOR

Page 15: Andrea Petri

Gen

eric

Sim

ulat

ionT

ask

Model.inpNodesLoadsBoundary ConditionMaterial

Geometry.stp

Results.res- Script- Configuartion- Commands

- Excel- .DOC-.PDF- Else …- Else …

- Else …

Page 16: Andrea Petri

…Future (not so far hopefully)…

KEEP AN AUDIT TRACE OF DEVELOPMENT PATH OF THE PRODUCT (what-if data)

Decision Point

Dead Brach

Page 17: Andrea Petri

…Future (not so far hopefully)…

KEEP AN AUDIT TRACE OF DEVELOPMENT PATH OF THE PRODUCT (what-if data)

Decision Point

Page 18: Andrea Petri

BEST PRACTICE IN CAE

06/21/10

Page 19: Andrea Petri

Development of CAE-toolsFirst generation (1970-1995)

* Ascii command file based modeling* Vector graphics (Textronix terminals), later X11* No parametrisation

Second generation (1990-2005)* Interactive use and modeling* Parametric models inside application* Connection to generic graphic formats (e.g. IGES)* Programmability of command language* Inhouse libraries

Third generation (2005-)* Metamodeling software: SimXpert, CoMet, HyperWorks* Integration of several CAE-software and CADin in to

Multi View models* Support for CAE-prosesses and workflows* Support data management

• straw0001.avi•

Page 20: Andrea Petri

Simulation tools• Native tools

– E.g. ADAMS, Abaqus, ANSYS, Nastran...– Work only in one domain of

CAD, FEM, MBS, CFD...– Native basic modeling– May contain own special models: e.g.

ADAMS/Hydraulics– Automation (programming on tool level)

• Metatools– E.g. SimXpert, Altair Hyperworks, CoMet– CAE-Application integration: Transformation of data

from one model to another CAD=>FEM => MBS– Interface to several native tools (CAD, FEM, MBS...)– Development of best integrated processes

• Process and data management– E.g. SimManager, Altair Data Manager, CoMet – Even some PDM-software may be applicable

Page 21: Andrea Petri

Application integrationFor a human, managing engineering information, requires several viewpoints toreality. The views must show for each specialist their own view point to design object.

Build MULTIDOMAIN VIRTUAL PROTOTYPES with“HIGH” (Industrial value) FIDELITY:

1 single general multi domain environment does not exist (Modelica, Matlab vs despite of years of coding)!The actual approach is to connect different simulation environment (CAE SW) that deal with different aspect of the product (Transparent

Multi View Models)

06/21/10

APPLICATION INTEGRATION IS FUNDAMENTAL

CAD FEM

MBSCALC

Page 22: Andrea Petri

Application integration: The commercial way

Direct convertersEasy to acquireCommercially available (if lucky)Direct to use

BUT!Dependent of BOTH applications => Application dependent(x 2)Version dependentAlmost never convert 100%Short and very unsure future support!

A BA2B

Page 23: Andrea Petri

Light weight A2A integration definition

In A’s code In B’s codeCommon metadefinition

CAEApplication

A(e.g. Pro/E)

Inputinter-face

Macro

Outputinter-face

Macro

CAE-Application

B(e.g. Abaqus)

Inputinter-face

Macro

Outputinter-face

Macro

JACAX

A Model DataBlock

(Gen. CAD)

B Model DataBlock

(Gener. FEM)

A Native model

B Native model

Page 24: Andrea Petri

JACAX – Open Application Integration environment

ApplicationView

JACAX Metamodel

CALC CAD FEM MBS

Excel Pro/E Abaqus MSC.ADAMS

ParametrisationOptimisation

DesignConfiguration

MNF-analysisPost-MBS Durability

KinematicsFMBS

CAX

...

XXX

Applicationlevel

Domainlevel

Metalevel

Page 25: Andrea Petri

JACAX – Open Application Integration Environment Data Model

Page 26: Andrea Petri

JACAX Model propagationJACAX:

Parameter.txt! Design variable vector!Name,value,comment.....

Assembly.csv! Assembly metadata

Part.csv x n! Part metadata

Part.igs x n!Part Iges geometry

Model_build.mac!ADAMS_Macro$Model$Kinematic_model$Dynamic_model

Page 27: Andrea Petri

JACAX Properties

SimpleOpen independent definition > No SW vendor involvedExpandable according needsEasy and fast to implementCan be created by each users own toolsLong life cycle (native scripting language property)

YOU (the company) own the format !

Page 28: Andrea Petri

Diesel Engine Conceptual DesignCase study with so called “street credibility”

Page 29: Andrea Petri

VBA Exploring Loop-Piston Diameter-Stroke-Compression Ratio

PHYSICSBOUNDARY Pro/ENGINEER

CAD Parametric Model

88 GeometricDesign Parameters

LoadsMN

F

Page 30: Andrea Petri

Videos

Page 31: Andrea Petri

MBS test

Page 32: Andrea Petri

HEAVY DUTY COMPUTATION

BATCH EXECUTION