embraer solution to integrate simmanager with pre-processors...

MSC Software Confidential MSC Software Confidential

Embraer Solution to Integrate SimManager

with Pre-processors and Solver 2013 Users Conference

Presented By: Edgard Sousa Junior

May 14, 2013

MSC Software Confidential

• Introduction

• Embraer Solution for Engineering Data Management

– Deployment sequence

– Solver Integration

– Pre-processors Integration

– Next Steps

• Conclusion

Agenda

2


• Previous Scenario

– In-house Job Scheduler (JobBatch)

– Shared network directory (Drive G:\)

• Lack of traceability;

• Data loss and security issues;

• Rework and difficulty in reproducing the results

of previous reports.

– In-house SDM solution (EAD – Engineering

Analysis Data)

• Embraer decides to use a commercial

solution for SPDM.

Introduction

3


Embraer Solution for Engineering

Data Management

4


• Deployment sequence

– Capability 1: CAE Content Management - MSC SimManager 2010

– Capability 2: Tool Management - MSC SimManager 2012

• Solver Integration

– Example of the configuration of the Nastran Integration

• Pre-processors Integration

– Example of the configuration of a pre-processor

• Next Steps

Embraer Solution for Engineering Data Management

5


Deployment sequence

6


Deployment sequence

7

Suggested by MSC

Adopted by Embraer


• Not integrated with solver, neither pre and post-processor

• A family of commercial aircraft was chosen

• MSC SimManager 2010

• Some customizations were developed by MSC

• These customizations became part of the next versions

• Comparing to EAD (in-house solution)

– powerful search tool

– traceability among files

– better user management

Capability 1: CAE Content Management

8


• MSC SimManager 2012

• Central point of data storage

– No need of extracting the data from SimManager and copying it

elsewhere in order to use it, ensuring the data integrity.

• Transition of JobBatch to PBS, from Altair

– submission of Nastran jobs

– scripts to launch the pre-processors

Capability 2: Tool Management

9


Solver Integration

10

Configuration and Example


• Runtime of Nastran jobs

– some minutes

– several hours

• Nastran Queue Policies

– Short duration jobs: high priority

– Long duration jobs: low priority

– Huge jobs: run only after the COB

• Two Queues

– Nastran Jobs (PAS)

– Pre-processors scripts (QSUB)

Solver Integration

11


• The Configuration of the Nastran Integration:

– Application

– Object Types

– Application Contexts

– Application Parameters

– Queues

Solver Integration

12


Configuration of the Nastran Integration

13

Application



14

Application Context



15

Application Parameter



16

Queues


Example of a Nastran running

17


Pre-processors Integration

18

Configuration and Example


• SimManager functionality “ToPreprocessor”

• The configuration of “ToPreprocessor”:

– Application

– Object Types

– Application Contexts

– Application Parameters

– Scripts used to run the pre-processors

Pre-processors Integration

19


Configuration of “ToPreprocessor”

20

Application



21

Object Types



22

Application Contexts



23

Application Parameters



24

Scripts used to run the pre-processors

LaunchHM.bat



25

Scripts used to run

the pre-processors

LaunchHM.vbs



26

Scripts used to run

the pre-processors

LaunchHM.vbs



27

Scripts used to run

the pre-processors

LaunchHM.vbs


Example of the configuration of a pre-processor

28


Next Steps Deployment sequence

29


• Embraer use KBE in its aircraft development process. One

example of Embraer KBE Application is WSDS

(Wing Structural Design System).

• Embraer aims at deploying

this KBE application in

SimManager, to allow the

engineers to run WSDS

and manage all the data

generated by it inside

SimManager.

Next Steps

30


Conclusion

31


• Adoption of SPDM, in order to ensure the competitiveness

• These systems must be fully integrated with the engineers work

environment and tools, otherwise resulting in:

– data inconsistency,

– lack of traceability,

– security issues and data loss,

– rework and sometimes making it difficult to reproduce the results of

previous engineering reports.

Conclusion

32


• SPDM systems are very complex engineering processes

• Each engineering company has its own way of working

– All companies have the same tools available for their work, but…

– It is the particular way each one uses them that makes the difference

Conclusion

33


• Due to this complexity, it is impossible for SPDM systems to

have standard configuration procedures, which would work

“out-of-the-box” for every company that adopts them.

• A lot of energy is consumed and the huge amount of work

needed to configure a SPDM system must not go unnoticed

Conclusion

34

MSC Software Confidential 35

embraer solution to integrate simmanager with pre-processors...

Documents