Simulation Data Management – an Integration of Database and Pre-processor
Upcoming SlideShare
Loading in...5
×
 

Simulation Data Management – an Integration of Database and Pre-processor

on

  • 812 views

 

Statistics

Views

Total Views
812
Views on SlideShare
767
Embed Views
45

Actions

Likes
0
Downloads
16
Comments
0

3 Embeds 45

http://www.altairhtc.com 35
http://altairatc.com 8
http://www.altairatc.com 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Simulation Data Management – an Integration of Database and Pre-processor Simulation Data Management – an Integration of Database and Pre-processor Presentation Transcript

  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Simulation Data Management –an Integration of Database and Pre-processorCong WangScott LarsenThorsten PohlGeneral Motors Engineering
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 20131) Challenges for CAE2) Data Management Strategy3) System Development Strategy4) Pre-Processor Integration5) ConclusionsOverview
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Challenges for CAEIncreasing number of vehicle variantsLarge increase of number of models andresultsIncreasing number of LoadcasesUS NCAPChina NCAPPedProComfort• N&V• Ride…
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Challenges for CAEStrategy to share parts and componentsto leverage economics of scaleBase VehicleRe-use of parts Re-use of CAE Modelsas complex as the part share strategy itself
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Challenges for CAEReduced development timeDocumentation required of CAE- Data Input Models ResultsReduction / eliminationof hardware prototypesQuick response to trendsFast to MarketAnalytical design validation
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Challenges for CAEPLMSystemLists???One WayThese challenges are too complex to handle on traditional share drivesCAE workstationCAE share driveCAE workstationCAE share drive
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013SDMSystemPLMSystemListsData Management StrategySimulation DataManagement Systemrequired Closely liked toPLM (CAD) System Open to link otherdata sourcesBi-directionalIntegrated
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Data Management StrategySelection of System for Simulation Data ManagementKey Requirements A B C D ERevision and Release Yes - Limited Yes - Limited Yes Yes - Limited YesLinks to CAD No No Yes No YesCAE Data Query Yes – Limited Yes - Limited Yes Yes Yes - LimitedCAE Project Management Yes - Limited Yes - Limited Yes Yes - Limited NoExternal Application Integration Yes No Yes - Limited No Yes - LimitedLink to Requirements & Targets No No No No YesJob Submission Yes - Limited No Yes - Limited Yes - Limited Yes - Limited(Example)Initial pre-selection showed the most promising partner
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Data Management StrategyTeamcenter Items, Item Revisions and DatasetsCAD assembly structureItemItem Revision / 001Dataset (.hm)Dataset (.jt)Item Revision / 002Dataset (.hm)Dataset (.jt)New data statusCAE assembly structure
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Data Management StrategyLinks show the relation between CAD items and CAE itemsCAD – StructureNX and JTPart 1CAD MasterAssembly 1Part 2Assembly 11Assembly 12Part 3Sub-assembly 1Assembly 2Part 4Part 5 NX JT NX JT NX JT NX JT NX JTLink between CAD and CAECAE StructurePre-processor + Solver formatsStructure MapCAE item Part 1CAE MasterCAE Assembly 1CAE item Part 2CAE Assembly 11CAE Assembly 12CAE item Part 3CAE Sub-assembly 1CAE Assembly 2CAE item Part 4CAE item Part 5 Hypermesh / Ansa monolithic Dyna monolithic Nastran monolithic Hypermesh / Ansa monolithic Hypermesh / Ansa part Hypermesh / Ansa part Hypermesh / Ansa part Hypermesh / Ansa part Hypermesh / Ansa part
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Data Management StrategyProperties of CAE data are stored as attributes of the CAE Item RevisionThese attributes are the master for all subsequent processes and tools
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Data Management StrategyTeamcenter© Siemens, Altair, EATC 2011Launch: exportLaunch: open in HM,Run toolsEtc.SaveRe-importCommunication between TC and CAE tools via PLMXML formatAllows CAE tool maintenance cycles to be independent from rigid and formal PLM/CADprocess
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Data Management StrategyGM engineering siteIntroduction of a data management system will change the workflowsand behaviour for all CAE engineers in the global organisationGood training will be required
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Traditional IT development:System Development StrategyRequirementsdocumentIT Development &SolutionTesting andImplementationStrategy??StrategyUse Cases Initial ITDevelopment TestingImplementationIterations and constantFeedback LoopsAgile Development: project divided into manageable phases, feedback loops
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013System Development StrategyPhase 1 Phase 2 Phase 3 Phase 4Agile Development: each phase containing iterative approach Close link between IT and User community, close involvement of users required Tailored Tools addressing the Real needs
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Pre-Processor IntegrationNew feature in Hypermesh – Assembly browser tab: Read in assembly structure as in .plmxml Import CAD data or existing Hypermesh files Attributes (e.g. PID, thickness, material, MID, …)taken from .plmxml file, not from inside CAD data file=> new hierarchy of information Export of meshes on part level (i.e. several HM files) Write new .plmxml file (for import into TC)
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Pre-Processor IntegrationSingle Part Meshes  Monolithic Mesh ModelsHM file containing Part MeshHM file containing all parts of the assemblyWhy?• Certain mesh modification (e.g. removal of penetrations)might not be good to give to ‘clean’ part mesh• Some connections (rigids, bars) might share nodes of the partmeshes => where to store these?Vision: work on part level meshes only, and generate connectionsandfull model in solver format ‘on the fly’ for job submission only
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Pre-Processor IntegrationGeneration of new generic workflows for CAE model buildsMore work done in SDM-System (TC) to prepare work in the pre-processorDetailed description for the user required
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Pre-Processor IntegrationHypermesh Integration StrategyBackground:1. In tandem with a top-down implementation in CAE model quality and organization standards2. Emphasis on batch/automatic operations to take burden out of users3. Joint development among Altair, Siemens PLM, GM CAE SMEs, and GM IT4. Full GM IT support for rapid prototype and deployment (as compared to more rigid production CADPDM process)5. Be sensitive to the strengths and gaps in end users’ skill setsSpecifics to HM4SDM:1. Set a realistic expectation thatHM4SDM is a new development not yet always aligned with progression in other key HM corefunctionalityMust keep doors open to apply non-TC integrated HM functionality and other ‘tried-and-true’ 3rdparity tools to complete required CAE modelling tasks2. Develop HM4SDM mainly as an integration layer, instead of a TC-encapsulated vertical application3. Interim solution to bridge the gaps in assembly/instance hierarchy between TC/CAD and HM core4. Added the WIP-parking capability as protection to guard again undesired loss of HM session5. Must conduct more proactive QA of HM4SDM deployment candidates
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Pre-Processor IntegrationIssues in Hypermesh development and resolution strategyTo obtain quick common understanding of issues and agreed direction:weekly telephone conference between Altair and GM (IT and user community)Example: Naming ConventionOriginal proposal for part and module naming by Altair / SiemensFeedback from GM users: more description requiredNew proposal from Altair, plus question on strategy of multi-instance partsDirection from GM on multi-instance partsImplementation by Altair, included in a new versionInstallation of new version at GM sitesTest and Approval by GM
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Pre-Processor IntegrationFurther / required enhancements Align development of HM-4-TC with core functionality development Formalize functionality to expose, isolate and resolve discrepancy betweenHypermesh FE properties and Teamcenter item attributes Rapid part / sub-assembly replacement capability in assembled monolithicmodel Capability to initialize creation of Teamcenter CAE modules from insideHypermesh with proper relations Address gaps in assembly and instance hierarchy between Teamcenter CAEand Hypermesh corePriorities will be given depending on the feedback of the initial productive use
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Conclusions Simulation Data Management required to address future challengesfor CAE Close integration of SDM system and CAE tools needed An Agile IT Development Strategy will give the users a systemaddressing their needs Close involvement of experts from the user community is required A cross-functional core team must guide the development A successful productive use is possible within areasonable timeframe
  • Cong WangScott LarsenThorsten PohlGM EngineeringEuropean Altair Technology ConferenceTurin, April 22nd – 24th 2013Thank you for your attention