Mold Design and Casting > Catalogs > Creating the Layout > To Create the Final Level Layout File
  
To Create the Final Level Layout File
1. The Controlling Dimension of the Final level Dimension layouts is already determined by the name of the (Desired name for next level ) _Lay_File values in the dimension layout file before this level, for example, the ejector pin length.
2. Create Layout files for each instance in the Last (Size in this case )_Layout_File, using the exact name as the values for (Desired name for next level)_Lay_File (Len_Layout_File in the test case) parameter. In the test case, Hasco Inch has 25 diameter sizes, so create 25 Len Layout files.
3. When creating the parameter in the new layout file (for example purposes use Len as an example for the desired name for the final level ) since the length of the ejector pin is the dimension on which you want to search.
4. Create the first parameter Len_Lay_Descr in Len Layout.
5. The second parameter created in the new Layout should be the name of the parameter for the dimension you are using to control this level of Layouts. To Control the final level by the length, create a parameter named Length. This Parameter should also exist in the template model, and should be related to the dimension that drives the dimension you want to control by selection. In this case, this dimension is the Length dimension of the universal ejector pin model.
6. Create a parameter Order_Number in the Final Layout files. This Parameter should also be included in your universal model.
7. Create Dimension Parameters for any dimensions controlled by the dimension you select to lead this level of layouts.
For example: In the test case of ejector pins, the dimension I want to search with is the length of the ejector pin. Based on catalog pages, there are no other dimensions driven by the length for the regular size. However, if I were working with a Shouldered type ejector pin, the overall length of the ejector pin would control the shoulder length. Thus, I would add the Shoulder Length Parameter to the len layout file.
These Parameter names must also exist in the universal model.
Name these parameters exactly as they are written in the universal model.
These parameters should be related to their corresponding dimensions in the universal model. This is how the catalog knows what dimensions to change in the universal model according to the layouts.
8. Add all Parameters to the Param Table.
9. Edit the Param Table and add instances. Create an instance for every different dimension that changes in the type of part you are working on. For Example: ZI 41 type. 5/32 diameter pin has 5 length. So, in my ejpin_hasco_in_zi41_5_32_len Layout file, add 5 instances, one for each ejector pin length that Hasco makes for the ZI 41 Type, 5/32-diameter ejector pin.
10. The name of the instance should correspond to the dimension you would like to finally select by (in this case Length). Since the name of the instance is a dimension, and decimals, spaces or slashes cannot be entered as the instance name, a convention of underscores and dashes should be created to recognize decimal and fractional values. For inch fractional values, I recommend using underscores in place of slashes and dashes in place of spaces. For example: 1/16 would be 1_16. 1 ½ would be 1-1_2. For Decimal and metric values I recommend using zeros for spaces and underscores for decimals. For example: 0.117 would be 0_117, or 3.3 millimeters would be 3_3.
11. Set the Len_Lay_Descr to the desired Title name for the Length option in the dialog box. Type this name in the Param Table for all instances, for example, Length.
12. Enter values for dimension parameters. These values are the actual values that will drive the model, along with the values you will see in the dialog box. Make sure you enter real numbers for the second parameter you created (Dimension) rather than the instance name. The instance name is what you will use to select, but the second parameter actually drives the universal model.
13. Enter the part number under the parameter Order_Number for each instance in the last level layout file.