Gamma Technologies TUTORIALS GT-ISE

(1)

GT-ISE

TUTORIALS

VERSION 7.4

by

Gamma Technologies

(2)

GTI SUPPORT

TEL: (630) 325-5848

FAX: (630) 325-5849

E-MAIL: support@gtisoft.com

Web Address: www.gtisoft.com

Address: 601 Oakmont Lane, Suite 220 Westmont, IL 60559

USA Telephone Support Hours

8:00 A.M. to 5:30 P.M. Central Time Monday - Friday

(3)

TUTORIAL 1: Map Operations

This tutorial has been prepared to assist GT-ISE users in becoming more familiar with the graphical interface. This tutorial includes several helpful tasks that are not included in the model building tutorials.

These tasks will give the user more control over the project map and let them add or remove features to customize the look of their models

1.1 Formatting the Project Map

There are a number of different formatting options available to make the look and feel of the map in GT- ISE change. Some of these will be useful to the model when building and editing the file as a means of displaying the map in a way that makes certain types of information more visible. Other operations may be helpful when preparing the map for use in a presentation or document for non-models.

Other details on the map such as settings for which parts name display, grid points, and options to dim icons of certain types may be seen by right-clicking on an empty spot on the map and selecting "Map Display Settings…".

Zoom Options

Options to tile internal subassemblies (multiple

files may be tiled from the Window Menu)

Right-click on an empty spot on map

(6)

1.2 Manipulating Part Icons

1.2.1 Inverting and Rotating Part Icons

Parts may optionally have their icons rotated or inverted to make the map appear more pleasing and accurate in terms of flow direction. This has no function on the model other than cosmetic. Select one or more parts on the map, and then choose the right-click options "Rotate Part Icon(s)" or "Invert Part Icon(s)". The figure below shows the default icons on the left and rotated icons on the right that coincide with the natural direction of flow. Because this feature must often be used more than once to achieve the desired orientation, "Ctrl+I" may also be used to reduce the number of mouse clicks.

1.2.2 Inverting and Rotating Groups of Parts

When building models of V engines, the two sides of the engine are often identical but inverted, assuming that the cylinders are the same. The typical procedure is to (1) Build 1 cylinder completely, including attached parts like injector, valves, and pipes. (2) Copy and paste as necessary to build one side of the V completely. (3) Copy the completed side of the V and paste a copy to make the opposite side. (4) Invert the parts so that they face the opposite direction.

To invert a group of parts, simply select them as described above, and select "Invert Group of Parts (Horizontal)" from the right-click menu.

Similarly, a "Rotate Parts" is available in both clockwise and counter-clockwise directions from the right- click menu.

(7)

1.2.3 Changing Part Icons

Some templates, most typically the more interesting components, offer a choice of several different icons.

When icon choices are available, a right-click option "Choose Part Icon…" will be available by right- clicking on the part:

(8)

3) Associating your own .bmp, .jpg, or .gif file with the icon 4) Choosing from a library of images provided within GT-SUITE

GT-SUITE Library of Subassembly Images

(9)

1.3 Naming of Parts or Objects

1.3.1 Default Naming Convention for New Parts

When an object is dragged into the Project Map area, a new unique part is created. One may notice that there is a convention for how these parts are named, as no two parts may have the same name. This convention is defined in "Tools" -> "Options" under the "View" tab. Notice the four options under the section "Automatic Part Naming Convention". Choosing different options will allow the user to specify how each newly created part will be named.

1.3.2 Renaming Parts

Parts are given a name automatically when they are created, but it is sometimes desirable to give customized names to the parts. Part names may be up to 50 characters long, maybe not include spaces, but may include characters letters, numbers, and many special characters (e.g. - _ .). There are several methods available to rename parts to accommodate different needs depending on the number of parts to be modified and what is convenient:

1. Double-click on a part or right-click and choose "Edit Properties".

2. Right-click on a part in the Project Map or in the model tree and hit "rename". The F2 shortcut is also available to reduce mouse clicking.

3. Use the Sequential Part Renaming Tool, found in the Edit menu under "Map Edit Mode" or on the toolbar in GT-ISE. This tool allows many parts to be given sequentially numbered names very quickly and easily, for example Cylinder01, Cylinder02, Cylinder03, etc.

To use the Sequential Part Renaming Tool, it will be useful to describe the full step-by-step process so that it is clear to the user. Begin by opening up the example model

"Diesel_6cyl_TC.gtm" by clicking "File" -> "Open Examples" and choosing "Engine Performance". Once the file is open, save it to

%GTIHOME%\GTI\v7.x.0\tutorials\Graphical_Applications\GT-ISE_Features\Map_Operations directory with the name "Rename.gtm" by selecting "File" -> "Save As".

(10)

Where it asks for Part Name, type in "int_valve_##". Then, starting with the intake valve corresponding to Cylinder01, click each valve in order until all six valves have been sequentially named. Click "Done" and the valves should be labeled as seen below.

4. The Global Selected Parts Rename … feature allows a string to be prepended to, appended to, or replaced in all or selected parts. After the parts to be renamed are selected, this feature will be available under the right-click menu. This option is identical in design to the Global Rename feature described below, but only works for the currently selected parts on the map.

First, highlight the entire exhaust system from the valves to the turbine inlets.

(11)

Next, right-click on one of the highlighted parts and select "Rename Parts…", which will open the Global Rename Wizard.

(12)

Click "Add a suffix:" and type in "_exhst". Click "Next" to view the parts that are to be renamed. Then click "Finish" to complete the process. Notice how each part of the exhaust manifold now has "_exhst" appended to it.

5. Use the Global Rename … feature, found in the Edit menu. This option allows a string to be prepended to, appended to, or replaced in all or selected parts. This option is commonly used for external subassembly files when it is often convenient to add some identifying string to the start or end of all of the part names. It should also be noted that this feature can be used to change object names globally as well. Note that this option is most convenient for renaming all parts on the map. Selecting a subset of parts may require many checkboxes to be selected/unselected.

1.3.3 Renaming Objects

Objects must be given a name by the user when they are created. However, it is sometimes desirable to change these given names. Only characters, letters, numbers, -, or _ (spaces are not allowed) are allowed for object names. Object names are also limited to 20 characters. There are several methods available to rename objects to accommodate different needs depending on the number of objects to be modified and what is convenient.

1. The object name may be changed in the object window by double-clicking on the object from the model tree or by right-clicking on a part and selecting "Edit Parent Object…".

2. Click once on an object in the model tree and press the F2 key.

3. Use the Global Rename … feature, found in the Edit menu. This option allows a string to be prepended to, appended to, or replaced in all or selected objects. This option is commonly used for external subassembly files when it is often convenient to add some identifying string to the start or end of all of the object names. It should also be noted that this feature can be used to change part names globally as well.

1.4 Internal Subassemblies

Internal subassemblies are extremely useful for reducing clutter on the Project Map of large *.gtm files.

Creating an internal subassembly is simply for cosmetic purposes and does not change the function of the model. Internal subassemblies appear as separate sheets in the project map that can be renamed or rearranged by the user.

To create an internal subassembly, first select the parts to be included in the subassembly. After selecting the parts, click the Create Subassembly icon from the Tool Bar or right click on the selected parts and choose “Create Subassembly”. Each subassembly may be renamed by either right-clicking on the subassembly tab and choosing "Rename Assembly", or by simply double clicking on the tab.

Tiered (also known as "nested") subassemblies are also allowed, so one subassembly may be created from parts within another subassembly. The tabs located in the upper left corner of the project map indicate the subassembly name and level (main – 1, secondary – 2, etc.). As shown in the figure below, a special subassembly component icon in the Main assembly points to the internal subassembly, which then points to a nested internal subassembly. The tabs are used to toggle between these subassembly sheets and can be rearranged by clicking and dragging a tab to the desired location or by clicking "Assembly" at the top and choosing "Rearrange Assembly Tabs…".

(13)

Notice that when subassemblies are present, parts in the tree appear as grey if they are not present in the particular subassembly sheet which is open. They will appear as normal once the sheet in which they are located is selected.

Internal subassemblies can be reabsorbed into the parent assembly by right-clicking on the subassembly component and choosing "Absorb Subassembly". Also, they can be made into external subassemblies by right-clicking on the subassembly component and choosing "Export Subassembly". For more details on external subassemblies, refer to Tutorial 3 below.

1.5 Adding Notes or Images to the Map

(14)

Images can be added similarly. Right-click, choose "Add Image to Map" and select an image from the browser. You can then drag the crosshairs to the desired image size. This allows users to add any image to the project map, such as an image of the engine or vehicle being modeled, images of data or power curves, or any other picture the user may want to include. To lock images in place, so they are not able to be selected or moved by a single click or with a selection box, right-click on the image, select "Edit Properties…" and select "Lock for Movements". You may right-click or double-click on the image to get back into the image properties.

1.6 Viewing Flow Components Scaled Proportionally

An additional view for Pipes and FlowSplits is available which sizes the objects proportionally to one another based on the user-defined dimensions. To open this, select a group of parts that contain at least one pipe or flowsplit, and choose the

Scale View

toolbar button. The new window will be opened and the selected parts will be displayed in scale (see figure below). The total volume is calculated for the selected components and displayed in the status bar. This feature is only a viewer and cannot be used for editing objects. To return to Map View, either right-click on the project map and choose "Map View" or click on the Map View toolbar button.

(15)

(16)

TUTORIAL 2: Data Management

This tutorial is designed to provide information on advanced features within the GT-ISE interface that assist with data management and manipulation. It includes tasks that offer significant time saving opportunities when large amounts of data need to be modified or entered into an existing model. It also includes features for searching for and editing various object or part properties.

2.1 Template Library, Objects Library, and Implicit Objects

Please see the on-line help in GT-ISE for more information about the template library, object library files (.gto), and source control management via implicit objects. This help can be accessed from the general help browser in GT-ISE (on the Help menu) or by clicking on the "Help for Libraries…" button at the top of the Template/Object library window.

2.2 "Find Attribute Values" Feature

The "Find Attribute Values" feature is a great way to view a list of parts, objects, and parameters that contain a particular value. This value could be any type (i.e. numerical, reference object name, text, filename, etc.). For the specified value, it will return the Template Name, Object Name, Attribute Name, and unit for each attribute assigned that particular value.

To activate the "Find Attribute Values" feature, go to the Edit menu "Find Attribute Values" or click on the icon in the toolbar. This will open the dialog box shown below, prompting the user to enter the value he or she is looking for. Once the value is entered, the box will show all of the Objects, Parts, and Parameters that contain the specified value.

Figure 2.a "Find Attribute Values…" Dialog Box

(17)

2.3 Using Data in External ASCII or Excel Files

2.3.1 Import Multiple Arrays from ASC/Excel

This feature allows multiple arrays of data to be imported into a *.gtm file in a single operation, creating new objects with populated arrays. The user defines rules to place the data arrays from Excel/ ASCII into array attributes in each new object. This feature is typically used when there are a series of profiles to be imported, such as several valve lift profiles or injection pressure profiles (It is not rare for companies to import 50 such profiles at a time). To enable this feature, choose Tools  ASC/.Excel DataCreate New Objects prefilled with imported array data…". Navigate and choose the appropriate Excel or ASC file to be imported. You will then be prompted with the window shown below. From here, choose the data you wish to import and click "Next".

Figure 2.b Window to Choose Data to be Imported

You will then choose which template in your *.gtm model file the data will be imported into. Click next and it will open the window shown below, where you are able to specify how many parts are to be created and designate the appropriate data accordingly.

(18)

Figure 2.c Window to Specify New Object and their Corresponding Data Arrays 2.3.2 Objects with Implicit Data Arrays

Data from Excel and ASCII (.txt) files may be implicitly linked to any attribute array, so that before the simulation is run, it will look to that file and used the data specified. This is a very useful and time saving way to keep array data up to date. This data can be changed outside of GT-ISE and the model will always look to the specified file before running to get the latest data. To create this implicit link, first go into the object and find the array you wish to link to. Click the value selector and choose "<File Name>". You will then be able to specify which file to use. Note that you may break this link by importing the data using the "Explicit Import (Copy data from file)" option. Below is a short exercise which goes through the process of creating this implicit link to a *.txt file and eventually importing the data to make it explicit.

Begin by opening the example model "SI_4cyl.gtm" by clicking File -> Open Examples -> Engine_

Performance and choosing "SI_4cyl". Once the file is open, save it to %GTIHOME%\GTI\

v7.x.0\tutorials\Graphical_Applications\GT-ISE\Data_Management directory with the name

"Import_Lift_Data.gtm" by selecting File -> Save As. In this file, we will replace the entered valve lift data with links to *.txt files which contain the same values.

(19)

Edit the properties of the intake valve object either by double-clicking on one of the intake valves and choosing "Edit Object", or by right clicking on an intake valve and choosing "Edit Parent Object".

Figure 2.d Right-click or Double-click options for Editing the Object

Next, click on the "Lift Arrays" tab at the bottom, and clear all cells by clicking within a data cell, pressing "Ctrl+A" and then "Delete". We are now able to link this array to the *.txt file containing the desired data. The file Intake_Valve_Profile.txt has been prepared for this exercise. Click on the Value Selector icon in the first cell under "Cam Angle". This will prompt the dialog box shown below.

(20)

Figure 2.f Array Attribute Import Wizard Dialog Box for Cam Angle Array

Click "Next" and choose the appropriate delimiters for the file. The default is tab or space delimited, but the wizard supports a wide range of delimiters using the check boxes for semicolon, comma, and "Other".

The "Other" field will accept any single character as a delimiter. Multi-character delimiters are not supported.

Figure 2.h Select Data Delimiter Dialog for Lift Array

(21)

Click "Next" and select the values to import from the Select Data dialog. In this case, we are interested in the first column, which represents the data for Cam Angle. Click column A to highlight the whole column and then click "Finish". Click OK to close the Value Selector dialog. You should now see a string in the first row for Cam Angle that says <Intake_Valve_Profile.txt#0#0#0#-100>. This string tells the software the filename that the data is in as well as which rows and columns to take data from.

To define the Lift Array profile, follow the same steps as above but select column B from the Select Data screen. The Lift Arrays folder for the intake valve should now look like the figure below.

Figure 2.i Lift Arrays folder fully defined using Import Wizard

To convert the link between the object and data from implicit to explicit, edit the properties of the object, click on the Lift Arrays folder, right-click on the text linking the object to the file, and click "Import External Data" as seen below. Alternatively you can click the Value Selector, click <File Name> and then in the Import Wizard change from "Implicit File Pointer (Link to external file)" to "Explicit Import (Copy data from file)" and then click "Finish".

(22)

Figure 2.j Right-click Menu to Import External Data

Repeat this step for the Lift Array of the intake valve and both arrays of the intake valve. This will break the link between the objects and the external files.

Figure 2.k Lift Array Data after Importing the Data from the External File 2.3.3 Objects with Implicit Data Maps (XYZ data)

XYZ data can also be implicitly referenced from objects that use such data, such as 'XYZMap' template.

The wizard is analogous to that of arrays and guides one through the operation,. Getting started is the one somewhat tricky part; see the Figure below to see how to launch the wizard:

(23)

2.3.4 Case Setup Data from an External File

Case Setup allows you to define parameter values based on an existing Excel spreadsheet or ASCII file.

To do this, simply right click on a parameter, choose "Move to parameter folder" and select Excel DATA or ASCII Data. This will create a new folder in Case Setup that will allow you to specify the file name, as well as the worksheet, start cell and end cell for an Excel file, or the column and rows for an ASCII file.

A "Selection Wizard" is available by clicking the value selector of a cell or by clicking the wizard icon in the toolbar to make it easier to select this information.

Click on this Value- Selector Button to reference external 3D

(24)

**2.4 Comparing *.gtm Files**

It is often useful and/or necessary to compare similar *.gtm files. The user may be constantly changing model attributes during the course of creating and running models, and forget exactly what they changed from the original model or from one modified file to another. The "Compare files" tool displays all of the parts (common to both *.gtm files) that have dissimilar attributes.

After selecting "Compare Files…" from the Tools menu the user selects a second *.gtm file for comparison. GT-ISE allows the user to select another *.gtm currently open or to browse for one. Once the second *.gtm file is selected, a dialog box pops up with a tree displaying all of the parts that are different between the two models (see Figure 2.m). The user can select a specific part and the difference between the two similar parts will be listed in the table at the bottom of the dialog box. The user then has the option of printing out the results in ASCII (*.txt) or HTML (*.html) format or exiting the dialog box.

Figure 2.m The "Compare Files" feature, which targets differences between models

2.5 Edit Objects / Parts in Table

The option "Edit Objects / Parts in Table", formerly known as Table Edit view (see Figure 2.n), displays in a spreadsheet-type table information about specific objects or parts derived from the same template or object, respectively, in a project map. This options is the best way to audit and edit data from many objects at one time.

To use the Table editor:

1) Right click on an empty place on the map or in the tree (at the template or object level) 2) Select "Edit Objects/Parts in Table"

3) Click on template or objects in the tree to view the children objects/parts derived from these templates or objects together with their attribute data.

Note that only data in "regular" folders maybe seen in the table; array, multi-line, and XYZ folder data does not display.

(25)

Table edit mode is also a convenient way to turn on or off many plot requests at once. For example, it is easy to turn on a plot for "Pressure" in all parts made from the 'PipeRound' template by clicking in the 'PipeRound' template in the tree, and then clicking the appropriate check-box at the top of the plot folder.

Figure 2.n Table Edit View showing a plot folder listing all parts derived from the selected template Single-click turns on/off pressure plot in all parts associated with a given

template or object.

Support for both Data and Plot folders

(26)

TUTORIAL 3: Subassemblies and Encryption

This tutorial has been prepared to teach users how to create external subassemblies, as well as the option of encrypting of a subassembly. Encryption

can be used to ensure confidential transfer of models between OEMs, suppliers, and consultants. For instance, an OEM might want to send a model to a muffler supplier without letting the supplier view any details about the engine.

3.1 Background on External Subassemblies

External subassemblies allow the user to divide a model into several models. There are two main benefits to this. One is to break a big model into smaller, more manageable pieces, and the other, more important benefit is to isolate a part of the model so that it can be shared or reused in different projects. External subassemblies have the added benefit that they can be encrypted so that the contents may be used, but hidden, for secure sharing of sub-models between different companies (i.e. OEMs and suppliers).

External subassemblies differ from internal subassemblies in that the subassembly data is located in a separate *.gtm file from the main model. They have two distinct advantages over internal subassemblies:

1) They can be easily shared between several different "parent models and groups of users (e.g. on a network drive). For example, a group of muffler external subassemblies can be maintained on a common network location within a company, and then many different engine models (i.e. the main

*.gtm) may point to this collection of mufflers.

2) They may be parameterized allowing the contents of the subassembly to vary from case to case. For example, one subassembly part could refer to several .gtm files, each of which represents a different muffler configuration or geometry.

3) External subassemblies can be encrypted, so that they operate as a "black box" for external parties.

External subassemblies can optionally be encrypted in order to ensure confidential transfer of models between OEMs, suppliers, and consultants. For instance, an OEM might want to send a model to a muffler supplier without letting the supplier view any details about the engine or vice-versa. The process of encrypting a subassembly and limitations are explained in the section below "Example: Creating an Encrypted External Subassembly".

An external subassembly may be created in two different ways. An intuitive way of creating an external subassembly is to first create an internal subassembly by choosing the desired portion of the model. Then by using the right click menu on the special subassembly icon and by using the option Export Subassembly the external subassembly can be created. The subassembly will be saved in the same directory as the main model. The other method is to create the subassembly model in a separate project map. The main file should have a 'SubAssemblyExternal' component and the subassembly files must each possess at least one 'SubAssExternalConn' connection. Figure 3.a shows a main *.gtm file and subassembly file to which it refers. Subassembly *.gtm files are the same as any other *.gtm file, except that they contain 'SubAssExternalConn' connections, and they lack Run Setup information.

(27)

Figure 3.a External Subassembly and the 'SubAssExternalConn' connection Restrictions: There are certain restrictions regarding external subassemblies:

1) The External Subassembly component must connect exclusively to connections and cannot connect directly to components.

2) If the Main file and any subassembly have reference objects of the same name and type, they will be checked to ensure that the data is identical. If the data is not identical, the user will be prompted to choose one or the other, or to cancel.

3) If the Main file and any subassembly have parts of the same name, the subassembly parts will automatically be renamed so that there are never two parts of the same name. If there are any

"dependencies" on the part name in the subassembly (for example an 'RLTSensor' object using the same name), they too will also be renamed.

4) Case Setup in External Subassembly files must have exactly one case.

(28)

ii. Right-click on the * character in the Subassembly Case Setup, select "Attribute Properties", and take note of the unit.

iii. Go to Case Setup of the main model and add the parameter using the Declared Parameters button.

iv. Use Case Setup in the main model to assign values to the parameter---all values must be in the unit noted in the Attribute Properties in Step ii above

3.2 Example: Creating an Encrypted External Subassembly

This tutorial starts with the file %GTIHOME%\v7.2.0\tutorials\Graphical_Applications\GT- ISE_Features\Encryption\encrypt-begin.gtm. In this example, the engine ports, valves, cylinders, and cranktrain will be saved in an encrypted external subassembly. This example may be similar to a case when an engine manufacturer would like to send an engine model to an exhaust manifold supplier but would like to prevent the supplier from viewing any engine details.

To encrypt a certain part of the model, the user must first create an external subassembly. Only external subassemblies can be encrypted (internal subassemblies CANNOT be encrypted).

3.2.1 Data Within Encrypted Subassemblies That Is NOT Hidden

The encryption should guard against all knowledge from the sub-assembly with the following exceptions:

1) Check the main model for any left-over objects, parameter data in Case Setup, and comments (including those in the comment log) that you wish not to be exposed.

2) Plots that are requested within pre-process plots. These plots must be manually turned off prior to encrypting the file for them not to show. Example of preprocess plots include: Valve* objects, TurbineMap, TurbineMapSAE, CompressorMap, HxNuMap, PumpMap, FanMap, 'EngineState', 'EngBurnRate', and Dependency Reference Objects (i.e. 'XYTable', 'ProfileTransient', etc.). It is recommended that the model be run after encryption, and that the .gdx file be inspected for all plots that are visible prior to distributing the encrypted file.

3) Some messages and/or data from preprocessing objects (see list above) is written to the *.out file when the simulation is run, even when pre-process plots are turned off. For example, some information about fluid properties is always given in the .out file, even if the 'Fluid*' reference object is contained in an encrypted subassembly. In some other situations, the amount of output may be changed by modifying some values in the subassembly. Please inspect the .out file prior to distributing to ensure that no critical data is being exposed.

4) Any monitors ('Monitor*' templates in the Control library) that are present and active will continue to come out on the screen. This may be desirable if you wish to expose some results. If not, delete the monitor parts or use their "Hide" feature to suppress output.

5) Parameters in the external subassembly resolving at runtime (e.g. parameters containing formulas using parameters from the main model) will be available as result in GT-POST.

.

3.2.2 Creating an Internal Subassembly

The simplest way of creating an external subassembly is by first creating an internal subassembly and exporting it to an external subassembly. First, create an internal subassembly by selecting the parts to be included in the subassembly. In this example, select all parts from the intake ports to the exhaust ports.

(29)

(Note: Do not select the OrificeConn connections that will connect the subassembly to the other model parts.) After desired parts are selected, right click on the selected parts and choose Create Subassembly (see Figure 3.b below).

Figure 3.b Right-Click menu to Create Subassembly

Note that the user can "undo" the subassembly creation and reabsorb the internal subassembly into the parent assembly by right-clicking on the subassembly part and choosing Absorb Subassembly. This may be helpful if an error is made while selecting parts or creating the subassembly.

Next, right click on the subassembly icon and select "Rename Part" to rename the part to

"Engine_Subassembly". You may also want to re-size the subassembly part on the map. When you are finished, you will have a model similar to that shown below in Figure 3.c.

(30)

Figure 3.c New Subassembly Icon Viewed from the Main Assembly 3.2.3 Creating an External Subassembly

Next, the internal subassembly can be exported to an external subassembly by right-clicking on the subassembly part and choosing Export Subassembly (See Figure 3.d).

(31)

Figure 3.d Right-click menu to Export Subassembly

After the subassembly is exported, the subassembly is now a separate *.gtm model file (Note that the subassembly part icon color is gray and the internal subassembly tab is no longer displayed in the upper left corner of the main model project map). The new external subassembly may be viewed by selecting Open External Subassembly on the right-click menu of the new the external subassembly part that was just created. (Note that you can also open the external subassembly from the File>Open menu).

When the internal subassembly is exported, subassembly templates and objects remain in the main model tree. To remove these templates and objects from the main model, go to the Edit menu and select Delete Unused… Templates and Objects. This will remove templates and objects that are not used in the main model and will prevent a user from viewing object values that may be in the encrypted subassembly. The user should check the main model tree to confirm that all necessary templates and objects were

(32)

1) They may either have a single, constant value, which will be used for all cases.

2) They maybe be "promoted" to the main model's Case Setup by placing an asterisk (*) in the cell.

When a subassembly is created via the means described above, all parameters will be in this state. If additional parameters are added and given a * value, they will show up in Case Setup of the main model the next time that the file is opened or anytime that the "Subassembly Parameters" button is hit in the toolbar of the main model Case Setup.

But what if you have a parameter used in the external subassembly, it needs to change case-to-case, and it needs to be unexposed (i.e. encrypted)? In this situation, use an 'RLTDependence*' reference object in the attribute(s) that are using the parameter in question. For example, an RLTDependenceXY object can be created in place of the intake cam timing angle parameter [In-cam-timing-angle] that changes from case to case. This will allow the cam timing angle to change without another user seeing this in the main model. The Input RLT Variable can be defined as the case number "icase" (or better yet, something more physical like engine speed) and a dependence object can be set up to indicate the value for each case number. After RLTDependenceXY is created in the subassembly, the parameter should be gone from Case Setup of the subassembly file, but you must manually go to the Case Setup of the main model, and use the "Delete Parameter" button. This will remove this parameter from Case Setup of the main model. For an example of using RLTDependence in the subassembly, please see the model

%GTIHOME%\v7.2.0\tutorials\Graphical_Applications\GT-ISE_Features\Encryption\01- Encryption\encrypt-final.gtm.

3.2.5 Before Encrypting the External Subassembly - VERY IMPORTANT

As mentioned above in the section titled: "Data Within Encrypted Subassemblies That Is NOT Hidden", not everything in an encrypted subassembly is automatically suppressed, and so care must be taken when preparing a model to minimize the exposure and to be informed as to what will be visible. Please review every item in the check-list and make changes to your subassembly file as necessary.

In this particular example file, preprocess plots to show the valve lift curve are turned on. Edit the "inval"

and "exval" objects, and uncheck the attribute "Preprocess Plot Request".

3.2.6 Encrypting the External Subassembly

Open the external subassembly .gtm file and save it as an encrypted file by selecting "File" -> "Save As Encrypted…"

(33)

Figure 3.e File Menu to Save as Encrypted

This will open a dialog to prompt the user to enter a Run Simulation Password and Administrator Password. In this example, the Run-Simulation Password is "MyRunPassword" and the Administrator Password is "MyAdminPassword". Note that the user also has the capability to enter an expiration date for the encrypted subassembly. After this date, the subassembly cannot be used. In this example, an expiration date will not be used.

(34)

must be input into the "Run-Simulation Password for Encrypted Files" attribute in the 'SubAssemblyExternal' part in the main model (as shown in the figure below). On the other hand, the Administrator Password is only used to fully open and gain full access to the encrypted file, however is not needed to run the model. Typically this password should NOT be provided to the end user.

Figure 3.g Edit Subassembly from Main Model 3.2.7 Running a Confirmation Test

It is suggested to run a quick test to confirm that no sensitive data or results can be viewed after running the model with the encrypted subassembly. Run one case in the main model, and then open the resultant .gdx file in GT-POST. Confirm that no plots or tables exist that contain sensitive data. Remember that the encryption should guard against all knowledge from the sub-assembly except for requested preprocess plots. These plots must be manually turned off in each object within the encrypted subassembly.

Also check the .out file messages for any critical results that should not be exposed.

3.2.8 Sending the Encrypted Model to the Final User

At this point, the encryption of the engine subassembly is complete and ready to send to the final user.

The final main model and encrypted subassembly created in this tutorial is located in the folder

%GTIHOME%\v7.2.0\tutorials\Graphical_Applications\GT-ISE_Features\Encryption\Encryption. When sending, remember to send both the main model *.gtm and the encrypted subassembly *.gtm. Other tips include:

- Remember to save any changes to the external encrypted subassembly before sending. Saving the main model will not save changes to the external encrypted subassembly

- With the Administrator Password, a user can decrypt the external subassembly by selecting File>Save As… and saving the external subassembly with a new filename. A dialog will prompt the user to choose "Save Only" or "Save and Encrypt". Select the "Save Only" option and be sure to change the external file name in the main model SubAssemblyExternal part.

3.2.9 Advanced Feature: Retrieving signals and plots from an encrypted subassembly If desired, individual results from the encrypted subassembly can be selectively passed into the main model for the user to view or use in the controls domain. This is done using 'SensorConn' objects for instantaneous results or 'RLTSensor' objects for RLT values. After sensing a value in the encrypted subassembly, it must be connected to a 'SendSignal' object. Next, a 'ReceiveSignal' object is placed in the main model to receive the result. These results can then be connected to 'MonitorSignal',

(35)

'SampledOutput', 'MonitorCaseRLT', or 'RLTCreator' objects for display or storage in the main model.

Now a user will be able to view selected subassembly results in the main model output files. A graphical representation of this procedure is show in Figure 3.h below. For an example of passing signals, please see the model %GTIHOME%\v7.2.0\tutorials\Graphical_Applications\GT- ISE_Features\Encryption\Encryption.

Figure 3.h View linking Main Assembly to Subassembly

(36)

TUTORIAL 4: User-Created Compound Templates

This tutorial discusses modifying an existing compound template, a relatively advanced topic in GT-ISE.

A general knowledge and understanding of GT-ISE is required to complete this tutorial. For a tutorial on general use of GT-ISE, please refer to a tutorial for the specific modeling application of interest (Engine Performance, Fuel Injection, etc.). A compound template can be thought of as a super object or super template. It is a template created from multiple primitive parts (i.e. pipes, control parts, flow splits, masses, etc.). Some compound templates are provided by GTI (i.e. 'CheckValve', 'PumpPlungerDyn', 'Vehicle2WD', etc.). These compound templates can be modified to create derivatives. Users can also create their own compound templates from scratch. All compound templates can be identified by the fact that their template name will show up with blue text in template library and in the model tree. A GTI supplied compound will have a small red GTI logo in the top right corner of the template's icon.

In this tutorial, we will modify a compound template that is provided with the GT-SUITE installation.

Specifically, we will add a new plot, RLT, sensed quantity, actuated quantity, and a new attribute to the compound template. Once the user has completed this tutorial, he/she should be able to extend the lessons learned to create a new compound template from scratch. The steps discussed in this tutorial are no different when creating a new compound template.

4.1 Detailed Tasks to be Completed

The compound template 'CheckValve' will be modified. Specifically we will do the following:

• Add a plot for pressure drop across the valve

• Add an RLT for maximum velocity of the valve mass

• Add an attribute for surface roughness of the upstream valve chamber

• Add the ability to sense the acceleration of the valve mass

• Add the ability to actuate the friction multiplier in the upstream valve chamber

Once these steps are done, the changes are saved and the compound template must be "published". The publish step converts the map of objects (the .gtc file) into a template, which will be available in the template library. This compound template can then be used in exactly the same was as any other template available in the template library.

4.2 Preparing to Modify the Template

The first step in this process is to open the template library in GT-ISE. This can be done by clicking the Libraries tab near the lower left corner of the screen or on the blue and green icon on the tool bar (Tile with Libraries). In the flow tab, expand Hydraulics and Pneumatics and then Components. You should see something like the following:

(37)

Figure 4.a Template library showing some GTI-supplied compound templates

Note that the templates displayed in this tab will change depending on the license selected at the top of the window (GT-SUITE is selected in the image above). You may notice that the GTI logo (containing a red square) is displayed in the upper right hand corner of the compound template icons shown in the figure above. This indicates that these compound templates are provided by GTI. Icons for compound templates created by the user will appear differently as discussed later in the tutorial.

To modify the existing compound template, find the template 'CheckValve' in the template library, right- click on it and select "Edit Compound Template."

(38)

Figure 4.b Select "Edit Compound Template" after right clicking on the template to be modified

This will "explode" the compound template into the primitive parts used to create it as shown in the figure below. The corresponding file opened will be named CheckValve.gtc. Before the file is actually opened GT-ISE will display a message instructing the user that this is a GTI supplied compound and therefore cannot be overwritten. That is not a problem. After we make the changes in this tutorial we will publish the template under a new name, and the GTI supplied compound template 'CheckValve' will be unchanged.

(39)

Figure 4.c "Exploded" compound template displayed after selecting "Edit Compound Template"

Now that the internal components of the compound template are displayed, in the form of a .gtc file, it is possible to make changes to the file and then publish the modified template. Each of the modifications to be made will be discussed in a separate section below.

4.3 Adding a Plot

In this section we will add a plot to the compound template for the pressure drop across the valve. First, edit the part "FlowAreaCV" by double-clicking on it. Then go the plots tab and turn on the check box for

"Pressure Drop Between Adjacent Volumes" as shown below.

(40)

Figure 4.d Plot Options folder after modification

All plots that have a check mark will be available in the compound template. Note that placing a check mark in the box here does not mean that this plot will be turned on for any model which uses the compound template. The check box here only indicates that this plot will be available to be turned on/off for any parts created from the compound template.

We have now added the plot "Pressure Drop Between Adjacent Volumes," but there is still one final step to complete. We need to provide a name for the plot in the compound template. Many times the name of the plot in the primitive part ('Pipe', 'Valve*Conn', etc.) may not be as descriptive/helpful to the end-user as it could be. Imagine that in some compounds there may be many parts with the plot "Static Pressure".

If all those plots had the name "Static Pressure" in the compound template, this would be very confusing to the end-user.

The name that will be displayed for this plot in the compound template is chosen in the Plot Setup menu item available from the Compound menu. After selecting Plot Setup, the dialog shown below will be displayed. Find the plot that was just added and change the "New Plot Name" column to say "Pressure Drop Across Valve". Note that the order of the plots in this dialog will be exactly the order of the plots as they are listed in the compound template. To change the order of the plots use the Move Up/Move Down buttons in the upper right hand corner of the Plot Setup dialog. For this tutorial, we will leave the new plot as last in the list. Note that the order of plots in a template can be changed at any time by dragging

(41)

and dropping to re-arrange or by right-clicking and selecting "Move Up" or "Move Down". The plots can also be sorted into folders. New folders can be added by clicking the green "+" next to the Plots folder tab. The name of any folder can be renamed by right-clicking on the folder tab and selecting rename.

There is no risk in changing the order of plots or sorting plots into folders.

Figure 4.e Plot Setup Dialog after specifying the New Plot Name for the added plot

The "Short Name (Advanced)" column should only be filled out when the compound may be parameterized in a model with other compound templates. Please refer to the help document for Plot Setup for more detailed information on usage.

Click OK to save the changes. This completes the steps necessary to add a plot to the compound template.

(42)

4.4 Adding an RLT

In this section we will add an RLT to the compound template for maximum velocity of the valve mass.

All operations on RLTs (addition, deletion, organization) are done by selecting the RLT setup menu option from the Compound menu in GT-ISE. Go to the Compound menu and select RLT setup. The dialog below will be displayed (note some RLTs have been cutoff in the image to reduce the image size).

Figure 4.f Portion of RLT setup dialog before adding RLT

To add an RLT, click the "Add RLT(s)" button at the top of the dialog box. It will open another dialog that will be used to select the RLT(s) to add. Expand the tree for the 'Mass' template, then expand for the part "ValveMass", and then click on the "Velocities" item under the "ValveMass" part. In the middle section of the dialog there is a list of all RLTs available for this part. Select the RLT to be added (Maximum Velocity) and click the >> button in the dialog. The "Selected RLT(s)" list on the right hand side will show all RLTs that have been selected to be added to the RLT list.

(43)

Figure 4.g RLT selector dialog after adding the RLT for Maximum Velocity of Valve Mass

Click OK to the dialog to save the changes. Now the RLT Setup dialog is back in focus. We will work in this dialog for the final step.

The final step is to provide a new name for the RLT that will be displayed in the compound template. In the column "New RLT Display Name", change the value to "Maximum Velocity of Valve Mass". The order of RLTs in this dialog is the order in which they will be displayed for the compound. It would make sense to group this new RLT with the other RLTs for the valve mass. Click on the row for the new RLT to select it and then drag the row up until the RLT is below Maximum Valve Lift. In the future, if you wish to change the order of RLTs in the compound template, this can be done without any risk. It will not cause any changes in results or behavior for models which already made use of the compound template.

Note that RLTs can also be sorted into multiple folders

(44)

Figure 4.h RLT Setup dialog after adding and moving RLT

The "Short Name (Advanced)" column should only be filled out when the compound may be parameterized in a model with other compound templates. Please refer to the help document for RLT Setup for more detailed information on usage.

Click OK to save the changes. This completes the steps necessary to add an RLT to the compound template. Next we will add an attribute.

(45)

4.5 Adding an Attribute

In this section we will add an attribute to the compound template for surface roughness of the upstream valve chamber. First edit the part "USchamber" by double-clicking on it. The "Edit Part" dialog will be opened. In that dialog click the "Edit Object" button. This is the dialog where we will make the change.

Note that some of the attributes, such as Volume, Wall Temperature, and Initial State Name, have words enclosed in square brackets []. This indicates that these attributes will either be an attribute of the compound template or they will be evaluated as a function of attributes of the compound template. All attributes that are not enclosed in square brackets will be hard-wired in the template, meaning that the user cannot change these values. For example, prior to the change we are making, all parts created from the compound template assumed that the surface roughness of the valve chamber was "def" (no roughness). The end-user of the template could not change the value. After the change made in this section, the end user of the compound template will be able to specify a surface roughness in the compound template through the new attribute that is being added.

In the edit object dialog change the value for Surface Roughness from "def" to [SurfRough]. The name of the attribute inside the square brackets is up to the user developing the compound template and will not be used by anyone else. Click OK to the Edit Object dialog to save the changes. Then click OK to the Edit Part dialog.

Figure 4.i Edit Object Dialog after changing the Surface Roughness attribute

Next go to the Compound menu in GT-ISE and select Attribute Setup. This dialog displays the attributes from all parts in the model that are enclosed in square brackets []. The dialog will appear as shown in the

(46)

Figure 4.j Attribute Setup dialog before changes

Now, we will continue on to filling in the columns for the new attribute. Find the attribute that was just created, called SURFROUGH. It will be listed at the top. The column "Attribute Description" is used to define the name of the attribute as it will appear in the compound template. In this column type the name

"Upstream Chamber Surface Roughness." Turn on the check box for "Compound Attribute?" to indicate that this quantity should be an attribute of the compound template. Leave the object value empty. In the published compound template, the attributes will be separated into the various tabs (folders) seen below the attributes. Folders can be added by clicking the green "+" button at the end of the folder tabs.

Additionally, folders can be renamed or deleted by right-clicking on the folder tab.

The order of attributes in this dialog will be the same as the order they are listed in the compound template. It would make sense to move this attribute next to the other attributes for the upstream chamber.

To do so, select any cell in the row for the attribute SURFROUGH and then drag the attribute down until it is just below the attribute "Upstream Chamber Diameter." The dialog should now look something like this.

(47)

Figure 4.k Attribute Setup dialog after changes

Click OK to save the changes. This completes the steps necessary to add an attribute to the compound template. Next we will add the ability to sense a quantity of the compound template.

Note that occasionally the user may want a compound to have an attribute that does not exist explicitly in any of the templates used in the .gtc. For example, assume that your .gtc file contains a flowsplit which requires the volume as one of its inputs. Let's also assume that the end-user of the compound template will typically have a drawing which provides the cross-sectional area and length of the flow volume. We could very easily make the flowsplit volume an attribute of the compound template, and require the user to calculate the volume. However, it would be more convenient for the end-user if the compound template asked the user for "Cross-Sectional Area" and "Flowsplit Length" and then internally calculated the volume. Because the flowsplit does not directly ask for these quantities, we need to create two new attributes. This can be done easily using the "Add Attribute(s)" button on the Attribute Setup toolbar.

From here, the appropriate units can be assigned and the desired attributes can be sorted into folders.

If the attribute has been added after the compound template has been published and used in model (.gtm) files, it is strongly recommended to use the "Evolution pre-fill" value which is available only when the

"Show Advanced" button is clicked. This allows the newly promoted attribute to be automatically prefilled so that existing models, which did not have this attribute, will not fail.

(48)

template. Their use is not strictly isolated to sensing/actuating quantities in the compound template.

However, that is the most common use and what is discussed in this tutorial.

The direction of the linking arrow for sensed quantities should be from the primitive part to the 'CompoundSignalConn' part. The quantities which may be sensed are specified by double-clicking on the link between the primitive part and the 'CompoundSignalConn' part. Note that to allow multiple quantities to be sensed from the same primitive part, it is only necessary to create a single 'CompoundSignalConn' part. In fact, GT-ISE only allows one 'CompoundSignalConn' part to be connected to each primitive in each direction (i.e. one for sensed quantities and one for actuated quantities).

We wish to allow the end user of the compound template to be able to sense the acceleration of the valve mass. There is already a link from the part "ValveMass" to a 'CompoundSignalConn' part, so it is not necessary to add a 'CompoundSignalConn' to the map. Double click on the link connecting these two parts and it will bring up a dialog like this

Figure 4.l Output Signal Editor before changes

Currently the displacement, speed, and sum of forces can be sensed. To allow the acceleration of the valve mass to be sensed, turn on the check box for "Acceleration" and click OK to save the changes.

The next step is to give a name to this sensed quantity that will be used for the compound template. To do this, open the Output Signal Setup dialog from the Compound menu in GT-ISE. Find the quantity that was just added in the table. The column "Compound Signal Label" is the name of the signal that will be displayed when the end user is selecting which quantity of the compound template will be sensed. Change the value from "Acceleration" to "Valve Acceleration".

(49)

Figure 4.m Output Signal Setup after changes

Set the Compound Signal # to 11, because it is the next highest number available (10 is used for Net Force on Valve). Click OK to save the changes. The order of the signals here, not the Compound Signal

#, is used to determine the order in which the signals will appear in the dialog launched when the end user of a template chooses to connect a sensor to the compound template. The signals can be re-arranged or organized into multiple folders.

Note that we could have given this new signal the number 4 so that it was numbered just after "Valve Velocity", and then we would have had to renumber the signals that were previously 4-10. However, please be very cautious when renumbering signals! If you or any other user has models which already use this compound template, changing the signal numbering will change the quantities which are sensed in their model and may cause a change in results. When adding a new signal, the safest method is to assign it the next highest signal number so that previously existing signals are not affected.

4.7 Adding an Actuated Quantity (Input Signal)

In this section, we will add the ability to actuate the friction multiplier in the upstream valve chamber for

(50)

between the primitive part and the 'CompoundSignalConn' part. Note that to allow multiple quantities to be actuated from the same primitive part, it is only necessary to create a single 'CompoundSignalConn' part. In fact, GT-ISE only allows one 'CompoundSignalConn' part to be connected to each primitive for each direction (i.e. one for sensed quantities and one for actuated quantities).

We wish to allow the end user of the compound template to be able to actuate the "Friction Multiplier" of the upstream valve chamber. There is currently no 'CompoundSignalConn' connected to the part

"USchamber" with the link going into the part, as is necessary for actuated quantities (i.e. input signals).

Therefore, we need to add a 'CompoundSignalConn' part to the map. Create this new part on the map and place it as shown in the figure below.

Figure 4.n Project map after adding CompoundSignalConn above "USchamber" part

Now create a link from the 'CompoundSignalConn' part to the part "USchamber." A dialog like the one shown below will be displayed. To allow the friction multiplier of the upstream valve chamber to be actuated, turn on the check box for "Friction Multiplier" in the Pressure Drop tab. By default signal 1 (Wall Temperature) was turned on when the link was created. Turn it off by clicking on the check box for Wall Temperature in the Thermal Tab and click OK to save the changes.

(51)

Figure 4.o Input Signal Editor after changes

The next step is to give a name to this actuated quantity that will be used for the compound template. To do this, open the Input Signal Setup dialog from the Compound menu in GT-ISE. Find the quantity that was just added in the table. The column "Compound Signal Label" is the name of the signal that will be displayed when the end user is selecting which quantity of the compound template will be actuated.

Change the value from "Friction Multiplier" to "Friction Multiplier in Upstream Chamber".

Figure 4.p Input Signal Setup after changes

Set the Compound Signal # to 2, because it is the next highest number available (1 is used for Wall Temperature). Click OK to save the changes. The signal order here, not the Compound Signal #, is used to determine the order in which the signals will appear in the dialog launched when the end user of a template chooses to send a control signal into the template (in this case an actuator). The signals can be re-arranged or organized into multiple folders.

(52)

4.8 Publishing the Template

Now that all the desired modifications are complete, the final step is to convert the modified .gtc file into a compound template. This step is called "publishing" the compound template. There are two options when publishing: "Republish" or "Publish New Template." The republish option will apply the changes to the original template that was edited. The Publish New Template option will create an entirely new template. Note that the Republish option will never be available when the original template being edited is a GTI-supplied compound template, because GTI compound templates should never be overwritten.

From the Compound menu in GT-ISE select "Publish New Template". It will bring up a dialog like the one shown below. In the name field, type the name of the new template "CheckValveTutorial". At the bottom of this dialogue select "User" as the library that this compound will be placed after publishing.

The user created template will be placed in a "User Compounds" group in the "User" library.

If desired, the user can choose an image file(s) (.jpg or .gif) to be used as the icon. Please see the help for the "Manage Icons" dialog for more details. In short, the user can specify an icon for the tree (16x16 pixels in size) and additional icons, which may be any size. The end user of the template can then choose between any of the available icons. Icons may be created in almost any photo editing software. On Windows the icon can be created in the Windows-supplied program Paint. For now, leave the icons as their default values.

The user can also add a help file to the compound by selecting a .txt, .html, .htm, or .pdf which has previously been created by the user. When the end user of the compound clicks on the help button in the template dialog it will open this help file, just like any other template in GT-SUITE. For the tutorial, we will not create a help file, so leave the field blank.

The user may also choose to encrypt the template by turning on the check box Encrypt Template. Once published, an encrypted compound template will require a password to view the internal contents. End- users will be able to run models containing encrypted templates and view any results that were made available in the compound template. For now leave this option turned off.

IMPORTANT!! To modify to the template after it has been published, do NOT open the .gtc file directly. Instead, find the template in the template library, and use the "Edit Compound Template" option available from the right click menu.

(53)

Figure 4.q Publish New Template dialog

With the name of the new template entered in the dialog, click OK to publish the template. A message will appear indicating that the template CheckValveTutorial has been published and the database for the template library needs to be reloaded to reflect this new template. The message also indicates that the

"Edit Compound Template" option should be used to make changes to the template in the future as discussed above.

From the Window menu in GT-ISE, select "Tile With Libraries" and go to the User tab. The new compound template that has just been created will be located here in the User Compounds group. The template may now be used in the same manner as any other template in the template library. Note that the icon is slightly different than the icon for 'CheckValve' in that it does not have the GTI logo superimposed in the right hand corner. This indicates that the 'CheckValveTutorial' template is not a GTI compound template, but rather it is a compound template created by the user, termed a "user compound template."

When a compound template is first published, it is only available to the current user. In order to make it available to other users, the compound developer has two options, which will be discussed in the next section. The next section also discusses the implications/responsibilities associated with providing the compound template to other users.

(54)

4.9 Sharing Compound Templates to Other Users and its Implications

As mentioned in the previous section, when a template is first published it is only available to the user who published it. That user has the option to allow other users to use the compound template also.

However, this brings an added responsibility, and any user who will provide the compound template to other users should read this entire section very carefully!

There are two methods available to make the compound template available to other users, and they are both described below:

• Export Compound - This option should be used to send the compound template to users outside your company. If you wish to share the compound with users in your company, the share template option (discussed next) should be used. To export a compound, locate the template in the Template Library and from the right-click menu choose "Export Template." The .zip file created from this operation should be sent to user at the other company. That user must go to GT-ISE, right-click on any of the groups in the Template Library, and then choose "Import Compound Template(s)" from the Compound menu on the GT-ISE toolbar. Alternatively, if you wish to send a model that contains a compound template, use the "Send Model" feature available from the File menu. The .zip file created by that operation will include the files for the compound along with all other files necessary to run the model. The person receiving the model can use the "Import Sent Model" feature on the file menu in GT-ISE. It will automatically publish the compound(s) and open the model. Please read the comments immediately below regarding the consequences of modifying a compound template after it has been shared with other users.

• Share compound: "Corporate Compound" - This option should be used to share the compound with all users who share a GT-SUITE installation (Note that if users at a company do not share the same installation, they will have to configure each installation in order to allow all users to have access to the shared compound templates. For details on how to do this, please see the next section).

To share the template to other users in your company, locate the template in the Template Library and from the right-click menu choose "Share Template".

In some cases it may be desirable to have different shared compound directories for different groups.

For example, people working in an engine simulation group may need to work with compounds of the cooling system developed by the cooling group, but perhaps they should not be able to modify these compounds. This can be accomplished through setting up multiple shared compound directories and setting the proper file permissions on those directories through the operating system (i.e. the engine group would have read permissions on the cooling group's compound directory but not write permissions). If multiple shared compound directory locations are available, the user will be asked to choose which directory during the share operation.

Note that after the share operation completes, an image of a hand is superimposed at the bottom of the template icon in the template library indicating that this is now a shared template. The next time another user opens GT-ISE, they will be able to see this shared compound. Please read the comments immediately below regarding the consequences of modifying a compound template after it has been shared with other users.

IMPORTANT!!! Please note that once a template has been shared with other users, one should be very cautious when making changes to the template. Changing the definition of a template (adding or deleting attributes, changing signal numbers for input/output signals, etc.) can cause changes in results or even cause a model not to run. As an example, assume you shared your compound to all users in your company using the Share Template option discussed above, and some users have already created models with this compound. As the developer of the compound, you decide to remove an attribute that you feel should be hard-wired and does not need to be modified. The next time a user opens a model containing this