Several diagrams are shown below to indicate how these files and programs fit into the MSC Patran environment. In some cases, site customization of some of these files is indicated. Please see the Patran Installation and Operations Guide for more information on this topic.

Figure 1‑1 shows the process of running an analysis. The SAMCEF.plb library defines the various Execution Parameters, Solution Type, Solution Parameter, Specific Options, Select Loads Cases and Output Request forms called by the Analysis form. When the Apply button is selected on the Analyze form, a.jba file is created, and the script samcefSubmit is started. This script may need to be modified for your site installation. The script, in turn, starts the PAT3SAM forward translation. MSC Patran operation is suspended at this time. PAT3SAM reads data from the database and creates a BACON input file, or Banque file. BACON and then analysis modules are executed in series after successful translation, if the user has requested that action. A message file is created to record any translation messages

Figure below shows the process of reading information from an analysis results file. When the Apply button is selected on the Read Results form, either a .jbm  or .jbr file is created, depending on whether model or results data is to be read. A process is then spawned to start the SAMPAT3 results translation. The MSC Patran database is closed while this translation occurs. A message file is created to record any translation messages. SAMPAT3 reads the data from the SAMCEF results file. If SAMPAT3 can find the desired database, the results will be loaded directly into it. If, however, it cannot find the database SAMPAT3 will create a new MSC Patran model database before loading the results. SAMPAT3 is also used to create a “query” file, used when recovering a summary of available results. Then, the user may also request generation of a MSC Patran 2.4 Neutral (topology) file.