NX CMM Inspection Teamcenter Integration Guide NX11 and Higher

NX CMM Inspection / Teamcenter
Integration Guide
For NX11 and higher
Version 7
7 December 2018
NX CMM Teamcenter Integration Configuration Guide
TABLE OF CONTENTS
1. Proprietary Rights Notice .................................................................................................................................................................. 3
2. Revision History................................................................................................................................................................................ 4
3. Document Purpose ............................................................................................................................................................................ 5
4. Configuration Steps ........................................................................................................................................................................... 6
5. MFK (Multi Field Key) Information ............................................................................................................................................... 21
6. CloneCmmItemToCmmMeop.exe utility........................................................................................................................................ 23
7. Support Information (GTAC) .......................................................................................................................................................... 25
Page 2 of 25
1. Proprietary Rights Notice

Siemens and the Siemens logo are registered trademarks of Siemens AG.
Teamcenter is a registered trademark of Siemens Product Lifecycle
Management Software Inc.
This software and related documentation are proprietary to Siemens

Product Lifecycle Management Software Inc. Copyright 2017 Siemens
Product Lifecycle Management Software Inc.
All Rights Reserved.
All trademarks belong to their respective holders.
Page 3 of 25
2. Revision History
Rev Author Date Comment

1.0 Thomas Gigear 14-Dec-2017 Initial version cloned from
NX_CMM_Inspection_Teamcenter_Integration-
Configuration_Guide_for NX10_and_TC10_v1.2
2.0 Thomas Gigear 30-Jan-2018 Update versions supported and steps 2-J, 4-B and 17
3.0 Thomas Gigear 31-Jan-2018 Update step 8 to account for difference between NX versions
4.0 Thomas Gigear 29-Mar-2018 Make changes based on experience with Vulcan VM
5.0 Thomas Gigear 5-Apr-2018 Name change for use in .xml file.
6.0 Thomas Gigear 13-Nov-2018 Update classification instructions to classify item revisions
7.0 Thomas Gigear 6-Dec-2018 Various improvements for PR8981036
Page 4 of 25
3. Document Purpose
The purpose of this document is to outline the steps necessary to setup an existing Teamcenter 10.1.1+
installation for use with the NX CMM Inspection application in NX11+. It is expected that the user have a
basic knowledge of Teamcenter Application Administration, and that the procedures will be performed with
administrator or DBA permissions for Teamcenter and the host operating system.
Table 3.1 Versions supported by this guide:
NX Version Teamcenter Version Tested

12.0 MP3 11.5 Yes
12.0.1 11.3 Yes
12.0.1 11.4 Yes
11.0 and higher 10.1.1 and higher No
Page 5 of 25
4. Configuration Steps
This document is to be used when integrating NX 11 or later with Teamcenter 10.1 or later.
If you are integrating using NX prior to NX11 then please refer to the document
NX_CMM_Inspection_Teamcenter_Integration-Configuration_Guide_for NX10_and_TC10_v2.pdf.
If you are integrating a combination of versions where either NX is a version prior to NX 10 or Teamcenter is a
version prior to Teamcenter 10.1 then please refer to the document
NX_CMM_Inspection_Teamcenter_Integration-Configuration_Guide_v5.4.pdf.
Step Action
1 Create the Classification Tree Structure.
The TC database must have a classification tree structure that has storage classes for at least these three
items: Coordinate Measuring Machines, Head Devices, and Probe Tools.
You may use the classification structure from the MRL (Manufacturing Resource Library) without the
need for a Resource Management license. This will not require using any part of the MRL other than
the installation executable in the TC advanced_installations folder. This classification tree structure is
complete and thorough. It is also the easiest tree to use since the cmm_inspection kit files are set up to
use this structure by default. But if you would prefer to use your own custom classification tree
structure that is also possible.
The MRL classification tree will have these storage classes:
Page 6 of 25
To use the MRL classification tree structure:

Do step 1-1 and then proceed to step 2.
Or to use a custom classification tree structure
1-1 Populate Resource Manager with library data from TC advanced_installations.
Note: this does not require a Resource Manager license.
A. Find the Teamcenter installation data.

B. cd to the advanced_installations directory.
C. Unzip the advanced_installations.zip file.
D. cd to advanced_installations\resource_management\.
E. Click on setup.exe.
F. Select Next twice to get to the ‘Setup Type Selection’ screen.
G. When asked to select the type of installation you want, choose ‘Manufacturing Resources –
Database Population’ and select Next.
H. Browse to the correct directory for tcRoot and select Next.
I. Browse to the tcData directory and select Next.
J. For the ‘Resource Management – ADMINISTRATIVE ACCOUNT’ use an administrative user
and password in the dba group and select Next.
K. For the ‘Resource Management – APPLICATION OWNER account’ use an appropriate user
and password. The wizard describes any limitations caused by the group selected for this
account. Read it carefully.
L. In the Content Selection page select at least Tools, Machines, Fixtures, and Templates. You
may also select any additional items you wish to configure. Select Next.
M. In the ‘Load CLASS HIERARCHY for Modules(s)’ page select at least Tools, Machines, and
Fixtures. These are the important items that we are installing. It is probably best to select all
items that appear here. Select Next.
N. It is optional to import GCS data or not. Select Yes or No.
O. In the ‘Load SAMPLE DATA for Module(s) page all selections are optional. Make your
choices and select Next.
P. In the ‘Support GRAPHICS BUILDER’ page it is optional to support graphics builder or not.
Make a selection and select Next.
Q. In the ‘Set ITEM TYPE’ pages use the default Types for all Items unless you have special types
you want to use. Select Next.
R. It is optional to check ‘Overwrite Existing Data’ or not. Select Next.
S. Confirm: Select Next.
T. When done you will be asked if you would like to return to the main menu to select another
setup type. Click No.
U. Click Finish.
V. Proceed to step 2.
Page 7 of 25
1-2 Create a custom classification tree
A. Using the Classification Admin application in Teamcenter, create a tree structure, consisting of
Groups, Classes, and Storage Classes, that has Storage Classes for these three types of items:
a. Coordinate Measuring Machines
b. Head Devices
c. Probe Tools.
B. You are free to use any Name and ID etc. when creating the Storage Classes.
C. See Teamcenter documentation for instructions on how to create the Classification Tree
structure and its Groups, Classes, and Storage Classes.
D. Modify the file cmm_inspection\resource\library\machine\inclass\dbc_inclass_mach_insp.def to
define the custom classification structure for Coordinate Measuring Machines. Use the existing
file as an example.
E. Modify the file cmm_inspection\resource\library\machine\inclass\dbc_inclass_mach_insp.tcl to
match.
F. Modify the file cmm_inspection\resource\library\device\inclass\dbc_inclass_device.def to define
the custom classification structure for head devices. Use the existing file as an example.
G. Modify the file cmm_inspection\resource\library\device\inclass\dbc_inclass_device.tcl to match.
H. Modify the file cmm_inspection\resource\library\tool\inclass\dbc_inclass_tlas.def to define the
custom classification structure for probe tools. Use the existing file and
dbc_mrl_tooling_library_tlas_en.def as examples.
I. Modify the file cmm_inspection\resource\library\tool\inclass\dbc_inclass_tlas.tcl to match.
2 Create CMM Machine classification in TC server.

A. Start Teamcenter.
B. Start Classification Admin App.
C. RMB on Classification Root -> Resource Management -> Machines and Devices -> Machine
Tools and select Add Class to create the CMM Machines class.
D. Enter the New Class ID as MDM0501 and select OK. Do NOT select Assign.
E. Set name to CMM Machines.
F. Uncheck “Abstract” option .
G. Select both (metric and non-metric) for System of measurement.
H. Save the new CMM Machines class.
I. RMB on the CMM Machines class, and select Add View to add a default view for this class, and
enter the name as Default View.
J. Select each of the default attributes to include in the default view.
a. -12500 Manufacturer
b. -12513 Controller Type
c. -12502 Year of Construction
d. -12501 Description
e. -12520 PP config filename
f. Plus any other default attributes that may be in the TC DB
K. Save the Default View.
Page 8 of 25
3 MFK specific setup information
Most Teamcenter installations will not be using MFK (Multi Feature Key). This means that when
running import scripts described in the following steps the –m and -i parameters do not need to be added
to the command line.
If you believe that your Teamcenter installation may be using MFK, which can be confirmed by your
Teamcenter administrator, then you will need to follow the directions described later in this document
In section 5. MFK (Multi Field Key) Information. This section will help you determine what text to use
for the –m and -i parameters when running import scripts described in steps 5, 6, 7, & 8.
4 Prepare to Import resources and templates.
When templates are imported, a new nxdm_ugs_inspection_template.pax file and a new
inspection_teamcenter_general.opt file may be created. This is done when either of the types is in
an MFK domain. The .pax and .opt files are created using the MFK ID’s of the files that are used
when importing them into Teamcenter. So that these files can be copied to the correct location the
‘Read Only’ attribute of the directories they are in must be de-selected.
A. Uncheck the ‘Read Only’ attribute for the following directories and their contents. This step is
not required to import Machines, Devices, and Tools, but is required to import Templates:
Note: If you don’t have permissions to do this, the scripts will still run. You may have to run
one of them from a different working directory and you may be prompted to copy any spinoff
pax and opt files to their appropriate directory afterwards.
a. \UGII_BASE_DIR\cmm_inspection\templates
b. \UGII_BASE_DIR\cmm_inspection\resource\template_set
c. \UGII_BASE_DIR\ugii\templates\sample
B. Check to see if you have the Teamcenter Preference ‘TC_part_types_display_filter’ in the list of
TC preferences. Certain settings for this preference can cause problems importing files. Check
and change this preference as follows:
a. In Teamcenter select the Menu item ‘Edit->Options’.
b. In the Options dialog select ‘Search’ from the bottom left of the dialog.
c. In the ‘Search On Keywords’ field, enter ‘TC_part’.
d. If ‘TC_part_types_display_filter’ does not appear in the list of preferences, then that is
good. You can exit the dialog and proceed to step C.
e. If ‘TC_part_types_dialog_filter’ appears in the list select it.
f. If the ‘Value’ field is empty then that is good. You can exit the dialog and proceed to
step C.
g. If the ‘Value’ field is not empty then it should contain both ‘Item and either
‘Mfg0CMMInspect’ (If using Tc11.3 or earlier) or ‘Mfg0CMMInspMEOP’ (If using
Tc11.4 or newer).
h. To change the value of the preference:
i. you will need to be logged in as an admin such as infodba.
ii. Click ‘Edit’
iii. Add ‘Item’ and either ‘Mfg0CMMInspect’ (If using Tc11.3 or earlier) or
‘Mfg0CMMInspMEOP’ (If using Tc11.4 or newer) to the list of values.
iv. Click ‘Save’.
Page 9 of 25
v. Exit the dialog and proceed to step C.

C. Make sure Teamcenter is running and then open a Teamcenter dos command window, which
will be used for all of the following steps.
D. In the command window set the following environment variables:
a. UGII_BASE_DIR=<valid NX Location>
b. UGII_INSPECTION_CONFIG=%UGII_BASE_DIR%\cmm_inspection\resource\config
uration\inspection_teamcenter_general.dat
c. UGII_UGMGR_ITEMID_IS_OSFILE_NAME=true
d. UGII_TMP_DIR=<a temporary directory> (This directory will be used for syslogs and
clone files that specify what is to be imported.)
e. UGII_CMM_DIR=%UGII_BASE_DIR% OR <a custom directory>
E. You can import directly from the cmm_inspection directory or from a custom temporary
location. You will want to use a custom temporary location for any of these reasons:
a. You want to import items that are not in the native library.
b. You don’t want to import all of the items that are in the native library.
c. There are spaces in the directory path of the native library.
F. To import directly from the existing cmm_inspection directory:
a. set UGII_CMM_DIR=%UGII_BASE_DIR%.
OR To import from a custom directory:
a. Create a new directory that has no spaces in the path and set UGII_CMM_DIR to it. All
the files to be imported to Teamcenter will be copied here to do the import from.
b. In the UGII_CMM_DIR directory, create a folder ‘cmm_inspection’.
c. Inside cmm_inspection create a folder ‘resource’.
d. Go to UGII_BASE_DIR\cmm_inspection\resource.
e. Copy the folder template_part and all of its contents to
UGII_CMM_DIR\cmm_inspection\resource.
f. Copy the folder library and all of its contents to
UGII_CMM_DIR\cmm_inspection\resource.
g. Delete any resources that you don’t want to import from the custom folders under
UGII_CMM_DIR
h. Add any additional resources that you want to import to the custom folders under
UGII_CMM_DIR. Resources must go into the appropriate folders for Templates,
Machines, Devices, and Tools.
5 Import CMM Machines.

A. In the Tc DOS command window opened in step 4, CD to
‘UGII_BASE_DIR\ugii\templates\sample’.
B. Make sure that all the environment variables specified in step 4 have been set before attempting
to run the following command.
C. In the command window run the following command:
inspection_cmm_import_setup –u=infodba –p=<password>
a. In NX12.0.2-MP5 and newer, by default the command will use the action
‘overwrite’. If for some reason you want to keep old cmm versions and import the
cmms as a new revision you should specify “–a=new_revision”
b. For NX versions prior to NX12.0.2-MP5 add “-a=overwrite” to the command.
Page 10 of 25
c. This command will import all of the CMM machines under

%UGII_CMM_DIR%\resource\library\machine\installed_machines directory.
d. The list of machines is also contained in the
…\machine\ascii\insp_machine_database.dat file.
e. The machines listed in the .dat file should match the contents of the
installed_machines directory.
f. The machines must be manually classified after import as described in Step 9.
D. After the command has completed, verify that it completed successfully. It will say so. If it did
not, then attempt to determine why not using any available logs. Fix any issues found and re-try
to import the CMMs.
E. If it did succeed, verify that the CMMs were imported. In the Teamcenter Rich Client select
home, select RMB->Refresh and verify that the ‘CMM Inspection Machines’ container exists.
Expand it and verify that it contains the CMMs and their components. If not then attempt to
determine why not using any available logs. Fix any issues found and re-try to import the
CMMs.
F. Note that CMMs and their parts will import as type ‘Item’.
G. If no cmms were imported then check to see if you have the Teamcenter preference
‘TC_part_types_display_filter’ in the list of TC preferences. See step 4B for instructions on
how to do this.
6 Import Devices (Heads).

A. Make sure that all the environment variables specified in step 4 have been set before attempting
B. In the Tc DOS command window opened in step 4, run the following command:
inspection_device_import_setup –u=infodba –p=<password>
a. In NX12.0.2-MP5 and newer, by default the command will use the action ‘overwrite’. If
for some reason you want to keep old device versions and import the devices as a new
revision you should specify “–a=new_revision”
c. This command will import all of the devices under
%UGII_CMM_DIR%\resource\library\device\graphics directory.
d. The list of devices is also contained in the
…library\device\ascii\insp_device_database.dat file.
e. The devices listed in the .dat file should match the contents of the graphics directory.
f. The devices must be manually classified after import as described in step 10.
C. After the command has completed, verify that it completed successfully. It will say so. If it did
to import the Devices.
D. If it did succeed, verify that the Devices were imported. In the Teamcenter Rich Client select
home, select RMB->Refresh and verify that the ‘CMM Inspection Devices’ container exists.
Expand it and verify that it contains the Devices and their components. If not then attempt to
determine why not using any available logs. Fix any issues found and re-try to import the
Devices.
E. Note that Devices and their parts will import as type ‘Item’.
Page 11 of 25
F. If no devices were imported then check to see if you have the Teamcenter preference
how to do this.
7 Import Tools (Probes).

inspection_probe_import_setup –u=infodba –p=<password>
a. In NX12.0.2-MP5 and newer, by default the command will use the action ‘overwrite’. If
for some reason you want to keep old probe versions and import the probes as a new
revision you should specify “–a=new_revision”
c. This command will import all of the tools under
%UGII_CMM_DIR%\resource\library\tool\graphics directory.
d. The list of tools is also contained in the …library\tool\english\insp_tool_database.dat
and …library\tool\metric\insp_tool_database.dat files.
e. The tools listed in the .dat files should match the contents of the graphics directory. Only
the metric tools need to be in the …metric\insp_tool_database.dat file and only the
english tools need to be in the …english\insp_tool_database.dat file..
f. The tools must be manually classified after import as described in step 11.
to import the Tools.
D. If it did succeed, verify that the Tools were imported. In the Teamcenter Rich Client select
home, select RMB->Refresh and verify that the ‘CMM Inspection Tools’ container exists.
Expand it and verify that it contains the Tools and their components. If not then attempt to
determine why not using any available logs. Fix any issues found and re-try to import the Tools.
E. Note that Tools and their parts will import as type ‘Item’.
F. If no tools were imported then check to see if you have the Teamcenter preference
how to do this.
8 Import CMM Inspection Templates.

A. If the configuration you are setting up has Tc11.4 or later and also NX12.0.1 or later:
Do Step 8-1 and then proceed to step 9.
Otherwise:
Page 12 of 25
8-1 Import New CMM Inspection Templates for use with the New Business Object Type.
A. Determine if this is an upgrade of an existing CMM integration. If it is then determine if the

existing templates are the old business object type.
a. See if there are already CMM Inspection Setup Templates in this database.
b. View the properties of one of the templates.
c. If the Multifield Key Information property shows ‘object_type=Mfg0CMMInspect then
the templates are the old business object type.
d. The new business object type would show ‘object_type=Mfg0CMMInspMEOP.
B. If the Tc DB has existing templates of the old type then delete them all now.
C. Make sure that all the environment variables specified in step 4 have been set before attempting
D. In the Tc DOS command window opened in step 4, run the following command:
tcin_inspection_new_template_setup –u=infodba –p=<password>
a. If the command fails because it cannot write to the working directory then the command
must be run from a different directory that the user has permissions to write in.
i. Choose a directory, such as the UGII_TMP_DIR, to use as the working directory.
ii. Change to the working directory using the ‘cd’ command. For example:
cd /d %UGII_TMP_DIR%
iii. Run the command using the full path of the script. For example:
%UGII_BASE_DIR%\ugii\templates\sample\tcin_inspection_new_template
_setup –u=infodba –p=<password>
iv. Then, when done, change back to the original directory using the ‘cd’ command:
cd /d %UGII_BASE_DIR%\ugii\templates\sample
b. In NX12.0.2-MP5 and newer, by default the command will use the action ‘overwrite’. If
for some reason you want to keep old template versions and import the templates as a
new revision you should specify “–a=new_revision”
c. For NX versions prior to NX12.0.2-MP5 add “-a=overwrite” to the command.
d. This command will import all CMM template files from
%UGII_CMM_DIR%\cmm_inspection\resource\template_part\english and metric
directories.
e. If you want to create new paxfiles add –n=autogen or –n=spinoff to the command. You
will need to do this if you are importing any custom templates.
f. Verify that the template part names in the nxdm pax file match the names of the imported
templates. Note that the _metric will be appended to the file names from the metric
directory and _inch will be appended to the file names from the english directory.
g. Note that there are some expected warning messages that will occur when importing
templates that contain resources such as Machines, Devices, and Tools. The expected
warnings are: “Component not found” showing the part names of machines, devices, or
tools. These warnings can be safely ignored. This is due to the way ug_clone works and
cannot be avoided. Step 15 to ‘Refresh Teamcenter information for Templates’ will
resolve any issues caused by these errors.
E. After the command has completed, verify that it completed successfully. It will say so. If it did
to import the Templates.
Page 13 of 25
F. If it did succeed, verify that the Templates were imported. In the Teamcenter Rich Client select
home, select RMB->Refresh and verify that the ‘CMM Inspection Setup Templates’ container
exists. Expand it and verify that it contains the Templates and the Target parts. If not then
attempt to determine why not using any available logs. Fix any issues found and re-try to import
the Templates.
G. If no templates were imported then check to see if you have the Teamcenter preference
how to do this.
H. If the script told you that pax or opt files need to be copied to their proper directories, you should
do so now. If this happened then the user that ran the script may not have write permissions in
the required directories. A user with proper permissions will need to copy the pax and/or opt
files as specified by the script message.
I. If you have a custom pax file with entries that aren’t in native NX then you should edit it now so
that it will work with the new templates.
a. Copy all of the custom pallet entries
b. Paste them back into the pax file below the existing entries.
c. For each of the copies of the pallet entries modify the following
i. Change the PalleteEntry ID so that the new items use new ID’s and no ID’s are
reused within the file. ( For example: “d2” becomes “d102”, “d10” becomes
“d110”, etc.)
ii. Change the <ItemType> from Mfg0CMMInspect to Mfg0CMMInspMEOP
d. Save the file.
J. Test that the pax file is correct and that the templates imported properly.
a. Launch NX in managed mode.
b. Open a part.
c. Click File->New
d. Verify that you see an Inspection tab
e. Click on the Inspection tab
f. Verify that a complete list of the CMM Templates is shown.
K. Proceed to step 9.
8-2 Import CMM Inspection Templates.

tcin_inspection_template_setup –u=infodba –p=<password>
a. If the command fails because it cannot write to the working directory then the command
must be run from a different directory that the user has permissions to write in.
i. Choose a directory, such as the UGII_TMP_DIR, to use as the working directory.
ii. Change to the working directory using the ‘cd’ command. For example:
cd /d %UGII_TMP_DIR%
iii. Run the command using the full path of the script. For example:
%UGII_BASE_DIR%\ugii\templates\sample\tcin_inspection_new_template
_setup –u=infodba –p=<password>
Page 14 of 25
iv. Then, when done, change back to the original directory using the ‘cd’ command:
cd /d %UGII_BASE_DIR%\ugii\templates\sample
b. In NX12.0.2-MP5 and newer, by default the command will use the action ‘overwrite’. If
for some reason you want to keep old template versions and import the templates as a
new revision you should specify “–a=new_revision”
c. For NX versions prior to NX12.0.2-MP5 add “-a=overwrite” to the command.
d. This command will import all CMM template files from
%UGII_CMM_DIR%\cmm_inspection\resource\template_part\english and metric
directories.
e. If you want to create new paxfiles add –n=autogen or –n=spinoff to the command. You
will need to do this if you are importing any custom templates.
f. Verify that the template part names in the nxdm pax file match the names of the imported
templates. Note that the _metric will be appended to the file names from the metric
directory and _inch will be appended to the file names from the english directory.
g. Note that there are some expected warning messages that will occur when importing
templates that contain resources such as Machines, Devices, and Tools. The expected
warnings are: “Component not found” showing the part names of machines, devices, or
tools. These warnings can be safely ignored. This is due to the way ug_clone works and
cannot be avoided. Step 15 to ‘Refresh Teamcenter information for Templates’ will
resolve any issues caused by these errors.
to import the Templates.
D. If it did succeed, verify that the Templates were imported. In the Teamcenter Rich Client select
home, select RMB->Refresh and verify that the ‘CMM Inspection Setup Templates’ container
exists. Expand it and verify that it contains the Templates and the Target parts. If not then
attempt to determine why not using any available logs. Fix any issues found and re-try to import
the Templates.
E. If no templates were imported then check to see if you have the Teamcenter preference
how to do this.
F. If the script told you that pax or opt files need to be copied to their proper directories, you should
do so now. If this happened then the user that ran the script may not have write permissions in
the required directories. A user with proper permissions will need to copy the pax and/or opt
files as specified by the script message.
G. If you have a custom pax file with entries that aren’t in native NX then you should edit it now so
that it will work with the new templates.
a. Copy all of the custom pallet entries
b. Paste them back into the pax file below the existing entries.
c. For each of the copies of the pallet entries modify the following
i. Change the PalleteEntry ID so that the new items use new ID’s and no ID’s are
reused within the file. ( For example: “d2” becomes “d102”, “d10” becomes
“d110”, etc.)
ii. Change the <ItemType> from Mfg0CMMInspect to Mfg0CMMInspMEOP
d. Save the file.
Page 15 of 25
H. Test that the pax file is correct and that the templates imported properly.
a. Launch NX in managed mode.
b. Open a part.
c. Click File->New
d. Verify that you see an Inspection tab
e. Click on the Inspection tab
f. Verify that a complete list of the CMM Templates is shown.
9 Classify CMM Machines.

A. First you will need to obtain a current list of all the top level part names of the CMM Machines
imported from Native as follows.
B. Open Windows Explorer and Navigate to the NX installations
UGII_BASE_DIR\cmm_inspection\resource\library\machine\installed_machines directory.
C. The list of directories under installed_machines is the list of top level CMM Machine names.
These are the names of the CMM Machines that need to be classified in Teamcenter.
D. In Teamcenter Rich Client Select ‘Home’.
E. Expand the ‘CMM Inspection Machines’ folder.
F. Expand the top level item of the first CMM Machine and select the item revision
G. RMB on the item revision and choose -> Send to -> Classification.
H. A ‘Classify Object’ message box will come up with the text “The object “xxx” is not classified –
there is no ICO for it. Do you want to classify it?” Select Yes.
I. In the classification tree, Double Click on Classification Root -> Resource Management ->
Machines and Devices -> Machine Tools -> CMM Machine.
J. Set the ‘PP config filename’ attribute to <machine_name>.dat (for example for the
‘Zeiss_Prismo’ machine set PP config filename to ‘Zeiss_Prismo.dat’).
K. It is not necessary to enter data in the other attributes, but you may enter whatever data you like
in those other attributes, which will be usable by Teamcenter for doing searches.
L. Save the machine classification.
M. Select Home.
N. Repeat steps F through M for the top level item of each CMM Machine from the list obtained
from the native directory.
Page 16 of 25
10 Classify Devices (Heads).

A. First you will need to obtain a current list of all the top level part names of the Devices imported
from Native as follows.
UGII_BASE_DIR\cmm_inspection\resource\library\device\graphics directory.
C. The list of directories under graphics is the list of top level Device names. These are the names
of the Devices that need to be classified in Teamcenter.
D. In the Teamcenter Rich Client Select Home.
E. Expand the ‘CMM Inspection Devices’ folder.
F. Expand the top level item of the first device and select the item revision.
G. RMB on the item revision and choose -> Send To -> Classification.
Machines and Devices -> Devices -> Head.
J. Set the ‘Holding System HS’ attribute to HEAD.
K. Enter a description for the ‘Description CD’ attribute. You may use the description from the
UGII_BASE_DIR\cmm_inspection\resource\library\device\ascii\insp_device_database.dat file.
L. Save the Device classification.
M. Select Home.
N. Repeat steps F through M for the top level item of each of the other Devices from the list
obtained from the native directory.
11 Classify Probes.
A. First you will need to obtain a current list of all the top level part names of the Probes imported
from Native as follows.
UGII_BASE_DIR\cmm_inspection\resource\library\tool\graphics directory.
C. The list of directories under graphics is the list of top level probe names. These are the names of
the Probes that need to be classified in Teamcenter.
D. In the Teamcenter Rich Client Select Home.
E. Expand the ‘CMM Inspection Tools’ folder.
F. Expand the top level item of the first probe tool and select the item revision.
G. RMB on the item revision and choose -> Send To -> Classification.
Tools -> Assemblies -> Probing -> Probe classification.
J. Save the Tool classification.
K. Select Home.
L. Repeat steps F through K for the top level item of each of the other Probe Tools in the list
obtained from the native directory.
Page 17 of 25
12 Set the UGII_INSPECTION_CONFIG environment variable.

A. Open the batch file, which will be run when starting NX in managed mode, for editing.
a. If starting from the rich client open
‘<Teamcenter_install_location>\portal\start_nxmanager.bat’.
b. In some cases this will be found in
<Teamcenter_install_location>\RAC\start_nxmanager.bat’.
c. If a batch file is run to start NX in managed mode, then open that batch file for editing.
B. Add the line ‘set
UGII_INSPECTION_CONFIG=%UGII_BASE_DIR%\cmm_inspection\resource\configuration\
inspection_teamcenter_general.dat’.
13 Set the UGII_INSPECTION_MANAGED_PROBE_CLASS_OVERRIDE if a non-standard

classification structure was used.
This step will not normally be required. This is only required if you have a custom classification
setup.
If the standard classification structure was setup using step 1 of this guide then skip this step and go to
step 14.
If a non-standard classification structure, other than the one populated by step 1, is used, then override
the probe class structure as follows:
A. Open the batch file that will be run when starting NX in managed mode, for editing.
B. Add the line ‘set UGII_INSPECTION_MANAGED_PROBE_CLASS_OVERRIDE=’<The
custom probe structure>’.
a. The custom probe structure string is created from the storage classes of the structure
elements separated by ‘;’ The default probe structure string is
‘TOOL;TAG600_PROBE;TA_PROBE_10_10’.
If it is desired that the tool class selection dialog is displayed so that any tool type can be selected from
the structure then the environment variable should be set as follows:
A. Open the batch file that will be run when starting NX in managed mode, for editing.
B. Add the line ‘set
UGII_INSPECTION_MANAGED_PROBE_CLASS_OVERRIDE=SHOW_CLASS_SELECTI
ON_DIALOG.
Page 18 of 25
14 Reset ‘Read Only’ attribute of kit directories.

A. If you un-set the ‘Read Only’ attribute of kit directories in step 4A, now is the time to reset the
‘Read Only’ attribute of the directories in the kits that the .pax and .opt files were written to.
B. Set the ‘Read Only attribute on the following directories and their contents:
a. \UGII_BASE_DIR\cmm_inspection\templates
b. \UGII_BASE_DIR\cmm_inspection\resource\template_set
c. \UGII_BASE_DIR\ugii\templates\sample
15 Refresh Teamcenter Information for templates

A. Start an NX session in managed mode connected to the server being configured.
B. Select File->Open and Browse to Home\CMM Inspection Setup Templates
C. Open the insp_general_assy_BSRotary_english_inch template file.
D. If an ‘Out of Date Machine’ message box is presented stating that the machine part file has
changed since the last time the machine was retrieved and asking “Do you want to update the
machine in this setup?” Select ‘No’. This is important. Do not select ‘Yes’ because that would
cause problems with this template.
E. Select Yes for Load on demand messages.
F. Go to the Assembly Navigator Tab
G. Select the top level template part in the Assembly Navigator.
H. RMB->Refresh Teamcenter Information
I. Save the template file.
J. Repeat steps B through I for all other templates that contain resources such as Machines,
Devices, and Probes. This would include:
a. insp_general_assy_BSRotary_mm_metric
b. insp_general_assy_Renishaw_Equator_300_english_inch
c. insp_general_assy_Renishaw_Equator_300_mm_metric
d. insp_general_assy_Wenzel_LH65_english_inch
e. insp_general_assy_Wenzel_LH65_mm_metric
Repeat steps B through I for any additional custom templates containing resources that have been
created in native and imported.
Page 19 of 25
16 Refresh Teamcenter information for resources as required:
If, at any time when an inspection setup file is being loaded, a message is shown stating that one of the
resources in the setup file is a read only file that has been modified and will not be able to be saved, then
that resource file should have its Teamcenter information refreshed. Refreshing its Teamcenter
information will stop that message from being output for that resource when a setup containing it is
loaded.
A. Note the name of the resource specified in the message.
B. Log in as a user that can see the resources (infodba for example)
C. Open the specified file
D. Select the top level part in the assembly navigator
E. RMB->Refresh Teamcenter Information
F. Save the template file.
Note 1: The resource files are not really read only when loaded directly, rather than as part of a setup,
and you will be able to save them after refreshing the Teamcenter information.
17 Convert Old ‘Coordinate Measuring Machine Inspection’ items to new MEOP based items
If you are using an NX version prior to 12.0.1

OR you are using a Teamcenter version prior to Tc11.4
OR you do not have any existing ‘Coordinate Measuring Machine Inspection’ items in the Teamcenter
database then you may skip this step.
But if you have NX version 12.0.1 or newer,

AND you have Teamcenter version Tc 11.4 or newer,
AND you have existing ‘Coordinate Measuring Machine Inspection’ items stored in the Teamcenter
database
AND those items were created using an NX version prior to NX12.0.1 and/or a Teamcenter version
prior to Tc11.4:
THEN those existing ‘Coordinate Measuring Machine Inspection’ items will be based on the old
Mfg0CMMInspect Business Object type. This can be verified by looking at the ‘Multifield Key
Information’ property of the items. They will need to be converted to the new ‘Coordinate Measuring
Machine Inspection’ items based on the Mfg0CMMInspMEOP Business Object type.
In this case use the CloneCmmItemToCmmMeop utility to convert the existing ‘Coordinate Measuring
Machine Inspection’ items to the new MEOP based items.
The advantages of doing this are that the MEOP based items can be used in Part Planner and the DMIS
files for the new type are stored under activities. In addition all new ‘Coordinate Measuring Machine
Inspection’ items created in Teamcenter will be the new MEOP based items so the old items must be
converted to be consistent with the new items.
See Section 6 for CloneCmmItemToCmmMeop utility usage:
Page 20 of 25
5. MFK (Multi Field Key) Information

Determine MFK Configuration for ‘Coordinate Measuring Machine Inspection’ and ‘Item’ types.
Performing these steps will not usually be necessary. You can check with your Teamcenter administrator
to determine if you have Multi Field Keys enabled. You will only need to perform the steps in this section
if your Teamcenter installation has Multi Field Keys enabled.
When importing files you must specify whether the ‘Coordinate Measuring Machine Inspection’ or ‘Item’ types
are in an MFK domain, whether or not they have additional keys, and if so what those keys are and what their
values should be for the imported files. If you know this information you may proceed to step 4. If not you will
have to determine what it is as follows.
A. In the Teamcenter Rich Client select Home.
B. In the tree, Select an object of type Item.
C. If none exists create one using the File->New->Item dialog and then select the item you have created.
D. In the Summary tab of the item, select ‘More Properties’.
E. In the properties window select ‘All’.
F. Scroll to the ‘Part Identifier’ field.
G. If the ‘Part Identifier’ is a simple number or name that does NOT include the text %#MFK#% at the
front then the Item type is in the default domain. Note that. Go to step 3M.
H. If the ‘Part Identifier’ starts with %#MFK#% then the Item type is in an MFK domain. Note that.
I. Look closely at the ‘Part Identifier’. It will have at least three parts. It will start with %#MFK#%,=
Then it will have item_id=xxxxxx,. At the end it will have object_type=Item.
J. If this is all it has, then it does not have any extra keys. Note that. Go to step M.
K. If there is more text in the form label=value, between the item_id key and the object_type key then it
has additional keys. It may have more than one additional keys separated by commas.
L. Note what additional keys are present for the Item type, what their label is, what their initial value is,
and their order if there are multiple keys.
M. Now do the same check for the type ‘Coordinate Measuring Machine Inspection’ which is also known
internally as ‘Mfg0CMMInspect’ or ‘Mfg0CMMInspMEOP’. There may not be an object of this type
created yet, so you will have to create one using File->New->Item. Select the object type ‘Coordinate
Measuring Machine Inspection’. Assign or enter a name and all other required information.
N. Select the new ‘Coordinate Measuring Machine Inspection’ item that you created and use steps D
through L to determine if this type is in the MFK domain and what extra keys it has if any. Note that
information.
When you are done, delete the ‘Coordinate Measuring Machine Inspection’ item that you created. If you
created an object of ‘Item’ type you may delete that as well.
When running the import scripts described in steps 5, 6, & 7 in Section 4 of this document add the –m
parameter to the end of the command line as follows:
A. If ‘Item’ is in the default domain (not MFK) then you may leave off the –m parameter OR you may
specify –m=NONE.
B. If ‘Item’ is in an MFK domain without any extra keys you will specify –m=NOKEY.
C. If ‘Item’ is in an MFK domain with one extra key you will specify –m=key1_label=key1_value.
Page 21 of 25
D. If ‘Item’ is in an MFK domain with multiple extra keys then specify all the keys in the same order they
appeared in the Teamcenter properties with commas between them. You will specify –
m=key1_label=key1_value,key2_label=key2_value[,keyN_label=keyN_value].
Note: If the MFK keys are entered such that they do not produce a valid MFK ID for the current configuration
then nothing will be imported.
When running the import script in step 8 in Section 4 of this document add the –m and –i parameters to the end
of the command line as follows:
A. If ‘Coordinate Measuring Machine Inspection’ is in the default domain (not MFK) then you may leave
off the –m parameter OR you may specify –m=NONE.
B. If ‘Coordinate Measuring Machine Inspection’ is in an MFK domain without any extra keys you will
specify –m=NOKEY.
C. If ‘Coordinate Measuring Machine Inspection’ is in an MFK domain with one extra key you will specify
–m=key1_label=key1_value.
D. If ‘Coordinate Measuring Machine Inspection’ is an MFK domain with multiple extra keys then specify
all the keys in the same order that they appear in the Teamcenter properties with commas between them.
You will specify –m=key1_label=key1_value,key2_label=key2_value[,keyN_label=keyN_value].
E. If ‘Item’ is in the default domain (not MFK) then you may leave off the –i parameter. OR you may
specify –i=NONE.
F. If ‘Item’ is in an MFK domain without any extra keys you will specify –i=NOKEY.
G. If ‘Item’ is in an MFK domain with one extra key you will specify –i=key1_label=key1_value.
H. If ‘Item’ is an MFK domain with multiple extra keys then specify all the keys in order with commas
between them. You will specify –
i=key1_label=key1_value,key2_label=key2_value[,keyN_label=keyN_value].
I. If either ‘Coordinate Measuring Machine Inspection’ or ‘Item’ is in an MFK domain then you should
also add the parameter -n=autogen to the end of the command line.
After running the import script:
J. In an explorer window find the
\UGII_BASE_DIR\cmm_inspection\templates\nxdm_ugs_inspection_templates.pax file. Check the
modified date to verify that it was modified. Open it for editing to verify that the ID’s match the
expected format as determined for the “Coordinate Measuring Machine Inspection” type.
K. In an explorer window find the
\UGII_BASE_DIR\cmm_inspection\resource\template_set\inspection_teamcenter_general.opt file.
Check the modified date to verify that it was modified. Open it for editing to verify that the ID’s match
the expected format as determined for the “Coordinate Measuring Machine Inspection” type.
Note: If you do not include the –n=autogen parameter, new .pax and .opt files will not be created. If either of
the types ‘Item’ or ‘Coordinate Measuring Machine Inspection’ is in an MFK domain you must generate new
.pax and .opt files. The only time you would not specify –n=autogen is either if MFK is not being used or if
you wish to create the new .pax and .opt files by hand.
Note: If the MFK keys are entered such that they do not produce a valid MFK ID for the current configuration
then nothing will be imported.
Page 22 of 25
6. CloneCmmItemToCmmMeop.exe utility
The utility CloneCmmItemToCmmMeop.exe in directory %UGII_INSPECTION_BASE_DIR%\auxiliary
clones CMM Item Business Objects (Mfg0CMMInspect) to CMM MEOP Business Objects
(Mfg0CMMInspMEOP).
This utility exists in NX version 12.0.1 and newer.
Location:
%UGII_INSPECTION_BASE_DIR%\auxiliary
This is the same as:
%UGII_BASE_DIR%\cmm_inspection\auxiliary
Utility Specifics:
 All CMM Item objects except item ID containing “inch” or “metric” will be cloned.
 The objects without “READ” permission will be ignored.
 If there are more than one revision of a CMM Item, the latest revision will be cloned.
 All new CMM MEOP Business Objects will be saved in the default folder (stated below) and the default
folder needs to exist in database before executing this utility.
Usage of the utility:

CloneCmmItemToCmmMeop –pim=yes -u=<user_id> -p=<password> -pf=<password_filename> [-
g=<group>] [-defaultFolder=<user_id>:Newstuff] [-report=stdout|stderr|<report_file_name>] [-h]
Where
-u - Teamcenter user ID
-p - Teamcenter password associated with the -u=<user_id>.\n"
-pf - File containing Teamcenter password associated with the -u=<user_id>
-g - Teamcenter group associated with the <user_id>. If this option is not
specified, then the default Teamcenter group is used as user group.
-defaultFolder - The folder contains newly created CMM MEOP objects.
If this option is not specified, then <user_id>:Newstuff
will be used
-report - An additional report. This is optional.
-h - Display this help message.
Example:
CloneCmmItemToCmmMeop –pim=yes -u=infodba –p=<infodba password> -defaultFolder
=infodba:NewCMMFolder
This utility should be run from an NX command window with Teamcenter environment variables set:
1. Open an NX command window.
2. Set the following Teamcenter environment variables.
a. TC_ROOT
Page 23 of 25
b. TC_DATA
c. FMS_HOME
3. Run the CloneCmmItemToCmmMeop utility as shown in the example above.
Page 24 of 25
7. Support Information (GTAC)

Global Technical Access Center (GTAC)
To report any serious problems please contact the Global Technical Access Center:
Website:
http://support.ugs.com/
Phone:
United States and Canada: 800-955-0000 or 714-952-5444
Outside the United States and Canada: Contact your local support office
Page 25 of 25

NX CMM Inspection Teamcenter Integration Guide NX11 and Higher

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

NX CMM Inspection Teamcenter Integration Guide NX11 and Higher

Caricato da

Copyright:

Formati disponibili

NX CMM Inspection / Teamcenter

1. Proprietary Rights Notice

This software and related documentation are proprietary to Siemens

All Rights Reserved.

All trademarks belong to their respective holders.

Rev Author Date Comment

Table 3.1 Versions supported by this guide:

NX Version Teamcenter Version Tested

The MRL classification tree will have these storage classes:

To use the MRL classification tree structure:

1-1 Populate Resource Manager with library data from TC advanced_installations.

Note: this does not require a Resource Manager license.

A. Find the Teamcenter installation data.

1-2 Create a custom classification tree

2 Create CMM Machine classification in TC server.

3 MFK specific setup information

v. Exit the dialog and proceed to step C.

5 Import CMM Machines.

c. This command will import all of the CMM machines under

6 Import Devices (Heads).

7 Import Tools (Probes).

8 Import CMM Inspection Templates.

A. Determine if this is an upgrade of an existing CMM integration. If it is then determine if the

8-2 Import CMM Inspection Templates.

9 Classify CMM Machines.

10 Classify Devices (Heads).

12 Set the UGII_INSPECTION_CONFIG environment variable.

13 Set the UGII_INSPECTION_MANAGED_PROBE_CLASS_OVERRIDE if a non-standard

14 Reset ‘Read Only’ attribute of kit directories.

15 Refresh Teamcenter Information for templates

16 Refresh Teamcenter information for resources as required:

If you are using an NX version prior to 12.0.1

But if you have NX version 12.0.1 or newer,

See Section 6 for CloneCmmItemToCmmMeop utility usage:

5. MFK (Multi Field Key) Information

This utility exists in NX version 12.0.1 and newer.

Usage of the utility:

7. Support Information (GTAC)

Potrebbero piacerti anche