Mapping the Functional Physical Classes

atarget.gif (1372 bytes)


This task shows you how to add new Function and Physical subclasses to the Function Physical Mapping table.

Examples from the Piping Design workbench are used here. Substitute the appropriate resource or directory when working in another workbench, i.e. CATWaveguideSample feature dictionary.

When new object classes (subclasses) are added to the Feature Dictionary they must be "mapped" in the FunctionalPhysicalMapping tables - the subclasses must be mapped to the physical part types. Only by mapping the new classes will they become available in the Browser during parts placement. This is also true when you add a function. When you create a function you also need to create a design table - see Knowledgeware documentation for information on how to do this.

In the following paragraphs the term 'NewSubclass' is used for illustrative purposes only. In actual practice substitute the class you are adding, e.g., 'Drain_Valve' for NewSubclass.

ascenari.gif (1364 bytes) 1. While in the Piping Design workbench, click File - Open.  Navigate to ..\intel_a\startup\EquipmentAndSystems\Piping\DesignRules, remove the Read Only status and open Piping-FunctionalPhysicalMapping.CATProduct. 

From Release 13 you have the capability of modifying the text table directly, instead of going through the CATProduct. To do so, open the XXXFunctionPhysical.txt file and make your changes. Go to Step 4 if you are changing the text file.

2. Expand Relations in the tree and double click the FunctionPhysicalMapping node.  The Knowledge Advisor workbench is activated. Double click the same node again to bring up the Design Table for FunctionPhysicalMapping.

3. Click the Edit Table button. The Piping-FunctionPhysicalMapping.txt file will open in Notepad. You can now add, delete and modify entries in the table.
4. Start on a new line at the bottom of the table and enter NewSubclassFunction in the Function Name column. 

Note: The column headings in the .txt file are Function Name and Physical Part and represent the columns Function and Part Type, respectively, in the design table.

You must enter 'internal' function and part type names. To obtain the internal names open the feature dictionary in the feature dictionary editor and click the Generate Report button. Specify a location for the file. In the report, the name shown against 'Object Key' - under each function or part type - is the internal name that you need to use.
5. Use the tab key to separate the columns. In the PhysicalPart column, enter NewSubclassPhysical. File and Save the txt file.
6. Now when you reopen the FunctionPhysicalMapping Design Table, the new line is added.

aendtask.gif (1477 bytes)