SIEMENS

Teamcenter 11.2

NX Remote Manager
PLM00123 • 11.2.3
Contents

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
NX Remote Manager interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
NX Remote Manager buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Basic concepts about NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Export rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Analysis results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Batch export and file archival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Configuring NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Configuring NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Enable NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Enabling automatic archiving of exported files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Enable batch import/export on a personal workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Enable batch import/export on a remote workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Enable e-mail notification of batch import/export completion . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Guidelines for part naming when using NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Using NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Using NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Establish a remote export connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Remote connection behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Send data to an existing connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Adding datasets to a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Manually export data to a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Refresh files in a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Importing files from a remote connection to Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Import modified data in to Teamcenter from a remote connection . . . . . . . . . . . . . . . . . . 3-4
Prevent files in a remote connection from being imported to Teamcenter . . . . . . . . . . . . . . 3-5
Manually import data from a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Set connections options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Delete a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
View transaction logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Importing and exporting assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Importing and exporting assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
How Teamcenter imports and exports assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Connection export directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Exchange files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
High security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

PLM00123 11.2.3 NX Remote Manager 3

 Contents
Contents

Data manager tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Export assemblies with BOM information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Exporting without BOM information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Check out a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Importing data from a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Import data from a remote connection to Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Selecting item types during import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

NX Remote Manager administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

NX Remote Manager administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Register custom item types with NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Preferences and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

4 NX Remote Manager PLM00123 11.2.3

Chapter 1: Getting started

Getting started
NX Remote Manager provides the ability to share data between customers and suppliers using My
Teamcenter to import and export data to directories that can be accessed by users outside of the
Teamcenter environment. In addition, you can use NX Remote Manager to work offline and then
synchronize data with the Teamcenter database.

Before you begin

Prerequisites • NX Remote Manager only works in the Teamcenter two-tier architecture.
It does not work in the four-tier architecture.

• NX and Teamcenter Integration for NX must be installed on the same

machine as the Teamcenter server.
Enable NX Remote NX Remote Manager must be enabled before you use it.
Manager
For more information, see Enable NX Remote Manager.
Configure NX NX Remote Manager must be configured.
Remote Manager
For more information, see Configuring NX Remote Manager.

NX Remote Manager interface

There is no separate interface for NX Remote Manager. Features are accessed using NX Remote
Manager menus in My Teamcenter.

NX Remote Manager buttons

Button Description
Export to connection Exports datasets to an active application
encapsulation session.
Import from connection Imports datasets from an application
encapsulation session.
Delete failed connection Deletes failed connections from the Teamcenter
database.
Display connection log Displays the transaction log for a connection.

PLM00123 11.2.3 NX Remote Manager 1-1

 Chapter
Chapter 1: 1: Getting
Getting started
started

Basic concepts about NX Remote Manager

NX Remote Manager allows you to share files with remote users who have no access to the
Teamcenter database. Data is exported, and after modifications are made, the data is imported
back in to Teamcenter.

1 Teamcenter client

2 NX Remote Manager
3 Remote application users
4 Supplier site
5 Teamcenter server
6 Remote individual user

NX Remote Manager uses export directories to manage the connections used to import and export
data. Files that are explicitly checked out for the current connection are exported with read-write
permission. Files that are not explicitly checked out are exported as read-only reference files.

1-2 NX Remote Manager PLM00123 11.2.3

 Getting started

When you import files back in to Teamcenter, only those files that have been checked out can be
imported back in to the database. This is referred to as high security and it applies to all files that are
managed by a connection.

Export rules
Option Description
Add Exports the primary dataset file, its component files, and
any additional files to the connection.
If the primary file is already in the connection, the system
does not check if any of the component files or additional
files must be updated or replaced due to changes in the
system. It ignores the Add function for that file.
Resend Exports the selected file, its component files, and
any additional files to the connection export directory,
overwriting files that are already in the directory.
Any modifications you have made to the files in the
connection export directory are lost. Use Resend
only when you are sure that you want to discard file
modifications. Files not previously exported to the
connection are added.
Refresh Checks to see if the selected files have been modified
in the system since the last export to the connection.
If modified, the system exports the selected files, the
associated components, and any additional files to the
connection. Files previously exported to the connection
are treated as if the Add option was used.

Analysis results
After performing an analysis prior to import, the system displays any of the following results.

The check mark indicates that the dataset analysis was successful.

The error symbol indicates that the analysis failed.

The warning symbol indicates that an unusual condition was found during the analysis
of the dataset.

Double-click the warning or error icons to display an explanatory message.

Batch export and file archival

NX Remote Manager allows you to export files to a connection in batch mode and archives the files
in either .zip format (Windows) or .tar format (UNIX). The archive file is stored in the connection
directory along with the files that were selected for export. You can request notification of completion
of the batch import operation via e-mail. For more information, see Configuring NX Remote Manager.

PLM00123 11.2.3 NX Remote Manager 1-3

Chapter 2: Configuring NX Remote Manager

Configuring NX Remote Manager

NX Remote Manager functionality allows you to import and export NX data from Teamcenter to a
connection directory for use by remote users and suppliers. The NX Remote Manager is installed as
part of the Teamcenter installation; however, you must perform the configuration steps described in
this section to enable NX Remote Manager functionality.

Enable NX Remote Manager

In Teamcenter:
1. Choose Edit→Options.

2. Click Search at the bottom of the dialog box.

Teamcenter displays the Preferences By Search dialog box.

3. Type the preference name, AIE_installed, in the Search on Keywords box.

4. Set the value of the preference to Yes and click Save.

5. Type the preference name, AIE_EM_installed, in the Search on Keywords box.

6. Set the value of the preference to No and click Save.

Enabling NX Remote Manager causes the standard_type property in Teamcenter to be displayed

with the properties dialog box.
In NX:
Perform the following step to enable native NX to update the IXF files:
• Copy the ug_base.dtd and ugxmlgen.dll/.so/.sl files from the
%UGII_BASE_DIR%\UGALLIANCE\vendor\application directory to the
%UGII_BASE_DIR%\UGALLIANCE\vendor\startup directory.

Enabling automatic archiving of exported files

Use the 7-Zip wza.exe command line utility to archive exported files on Windows platforms. This
utility is not part of the Teamcenter installation and must be downloaded from the following location:
http://7-zip.org/
After the utility is downloaded and installed, you must add the path to the wza.exe utility to the
PATH system variable.

PLM00123 11.2.3 NX Remote Manager 2-1

 Chapter
Chapter 2: 2: Configuring
Configuring NX Remote
NX Remote Manager
Manager

For more information about using the wza.exe utility, see the 7-Zip product documentation.

Enable batch import/export on a personal workstation

Windows systems:
1. Schedule a the tasks in Windows Task Scheduler to run as a specific user with the proper
privileges.

2. Ensure that the Task Scheduler service is running.

This service enables you to configure and schedule automated tasks on the computer. If the
service is stopped, the tasks are not run at their scheduled times. If the service is disabled,
any services that explicitly depend on it fail.

UNIX systems:
• Use the UNIX at command.
To use the at command, your name must appear in the usr/lib/cron/at.allow file. If that file
does not exist, the usr/lib/cron/at.deny file is checked to determine whether you should be
denied access.
If the at.deny file exists and is empty, global usage is permitted.
If neither file exists, only users with superuser authorization can submit a job.

Enable batch import/export on a remote workstation

1. Modify the values of the AIE_batch_servers preference to include the host names of the remote
machines to be used for import/export operations.

2. Ensure that the user has the same login credentials on the remote system that they do on their
local system.

3. Ensure that the values of the TC_ROOT and TC_DATA environment variables are identical on
all computers.

4. Ensure that the connection directory is accessible using exactly the same path information on
all computers.

Enable e-mail notification of batch import/export completion

• Set the value of the Mail_server_name preference to specify the names of the remote machines
used for import/export operations.

2-2 NX Remote Manager PLM00123 11.2.3

 Configuring NX Remote Manager

Guidelines for part naming when using NX Remote Manager

The following naming guidelines must be followed when importing and exporting data using NX
Remote Manager:
• Naming guidelines for import
Part file names matching ItemId_RevId_NonMasterTypeCode_DatasetName become
Non-Master-Parts-ItemId/RevId/NonMasterType/DatasetName upon import.
Part file names matching ItemId_RevId become Master-Parts-ItemId/RevId upon import.
If neither of the previous conventions are used, the entire part file name is used as the ItemId and
a RevId of A is arbitrarily applied.

Note
Underscores in generated part numbers are converted to spaces.

• Naming guidelines for export

Master parts (ItemId/RevId) become ItemID_RevID upon export.
Nonmaster parts (ItemId/RevId/NonMasterType/DatasetName) become
ItemID_RevID_NonMasterTypeCode_DatasetName upon export, where NonMasterTypeCode
is a single letter code for the type of the nonmaster part (for example, m for manifestation and
s for specification).
To create the following hierarchy:
Top Assy (with an associated drawing using manifestation relation)
- A1 (with an associated drawing using manifestation relation)
- D1 (with an associated drawing using manifestation relation)
- D2
Name the parts/drawings as follows:
123001_A.prt (UGMASTER dataset)
123001_A_m_TopAssyDwg.prt (UGPART with manifestation relation)
123002_A.prt (UGMASTER dataset)
123002_A_m_A1Dwg.prt (UGPART with manifestation relation)
123003_A.prt (UGMASTER dataset)
123003_A_m_D1Dwg.prt (UGPART with manifestation relation)
123004_A.prt (UGMASTER dataset)

Note
Spaces in generated names are converted to underscores.

PLM00123 11.2.3 NX Remote Manager 2-3

Chapter 3: Using NX Remote Manager

Using NX Remote Manager

NX Remote Manager shares files with remote users who have no access to the Teamcenter
database. Data is exported, and after modifications are made the data is imported back in to
Teamcenter. This works well for suppliers or for users who want to work independently with a laptop
computer and then synchronize their data with the Teamcenter database.
Remote connections manage files and associated information that is transferred back and forth
between Teamcenter and the connection. The remote connection list shows all active and failed
connections for the current user.
A remote connection is independent of both the Teamcenter session and the application session. The
connection keeps a history of data sent to the connection and the data received from the connection.
You can have more than one connection open at any time to send data to multiple suppliers. This
allows you to track what has been sent to and received from each supplier and also allows suppliers
to work on multiple projects.

Note
The UGII_BASE_DIR and UGII_ROOT_DIR environment variables must be set to export
item revisions containing UGMASTER datasets. If NX is installed locally, these variables
are set automatically. However, if you access the NX network from a mapped drive, you
must manually set these environment variables.

Establish a remote export connection

1. Log on to Teamcenter.

2. Select one or more datasets in My Teamcenter.

3. Add the files to the connection by choosing Tools→Export→To connection.

The system displays the Export Root(s) to Connection dialog box.

4. Create a new export/import connection.

You can have more than one connection open at any time to send data to multiple suppliers.

5. Select the components in the assembly that you want to download or check out.
You can force all items in a selected branch to default to Download Only, Download and
Checkout, or neither, in which case the component is not exported. If the component is already
checked out, or if you do not have write privileges to the dataset, you are not allowed to select
the checkout option.

PLM00123 11.2.3 NX Remote Manager 3-1

 Chapter
Chapter 3: 3: UsingUsing NX Remote
NX Remote Manager
Manager

6. Click Archive to create a compressed file of the exported files. (Optional)

7. Click Interactive to set up an import/export operation to be run at a later time. (Optional)

8. After you make your selections, click OK.

Remote connection behavior

When working with remote connections, the system automatically:
• Creates the remote connection directory, as specified by your preferences.
The remote connection directory is a single directory where the separate export directories reside
for each connection. All files for a connection are exported to and imported from its export
directory. If the connection export directory already exists when the system attempts to create it,
the directory is preserved and any files in the directory are preserved and are not overwritten.

• Exports the primary named reference file(s) of the corresponding dataset to the connection
export directory.
If the dataset is the root of an assembly, the selected component files are exported.

• Creates a connection and adds it to your connection list.

A remote connection is a database object used internally by the system. It manages all files and
associated information that is transferred back and forth between the system and the connection.
The remote connection list is the list of all connections (regardless of the application). The list
contains all connections for active remote connections as well as all connections for remote
connections that may have failed.

Send data to an existing connection

1. Select a dataset in My Teamcenter.

2. Choose Tools→Export→To Connection.

The system displays the Connection dialog box.

You can export, add, resend, or refresh the connection from this dialog box.

3-2 NX Remote Manager PLM00123 11.2.3

 Using NX Remote Manager

Adding datasets to a remote connection

1. In My Teamcenter, select the dataset.

2. Choose Tools→Export→To connection.

The system displays the Export Root(s) to Connection dialog box.

3. Click OK.
The system begins the analysis process to determine what files to export and to check for errors.
Before exporting any files, the system analyzes each dataset. When the analysis is complete, the
dialog box shows the list of datasets and the results for each.

4. Click OK.
The system exports the selected files to the connection export directory. If all files export
successfully, the system displays the Transaction Log File dialog box. If one or more files do not
export successfully, the system displays the log.

Manually export data to a connection

1. In the Connections dialog box, select a connection.

2. Click the Export to Connection button.

PLM00123 11.2.3 NX Remote Manager 3-3

 Chapter
Chapter 3: 3: UsingUsing NX Remote
NX Remote Manager
Manager

Refresh files in a remote connection

1. Select the dataset in My Teamcenter.

2. Choose Tools→Export→To Connection.

The system displays the Connection dialog box.

3. Click Refresh.
The system checks to see if the selected file has been modified in Teamcenter since the last
export to the connection. If the file has been modified in Teamcenter but has not been modified in
the connection, the system re-exports the selected file, its components, and its related files.

4. Click OK.
The system updates the connection directory with all changes made in Teamcenter since the
last export operation, including adding new components to the assembly, removing deleted
components from the assembly, exporting new item revisions, and exporting new dataset
revisions.

Importing files from a remote connection to Teamcenter

While working with a remote connection, you can send (import) modified data from the connection
export directory back to Teamcenter.
The following actions occur when you import modified files from a remote connection to Teamcenter:
• Files that have been modified in the connection export directory are imported as new file versions.

• Files that have not been modified in the connection export directory are skipped and not imported.

• Soft links in the connection export directory are not supported. Attempting to import soft links can
cause unpredictable results.

Import modified data in to Teamcenter from a remote connection

1. Move all files that need to be imported to the connection export directory.

2. In My Teamcenter, choose Tools→Import→From Connection.

3-4 NX Remote Manager PLM00123 11.2.3

 Using NX Remote Manager

The system displays the Connections dialog box.

3. Click the Import button .

The system displays the File(s) to Import dialog box dialog box.

4. Select any files that you do not want to import and choose Skip in the Action column.

5. Click OK.

The system imports the files from the connection export directory. After the files have been
imported, the system displays the Transaction Log dialog box.

6. Click Close to dismiss the dialog box.

Prevent files in a remote connection from being imported to Teamcenter

1. Select a connection in the Connection Name column of the Connections dialog box.

2. Select Yes in the Export Only column corresponding to the selected connection.

PLM00123 11.2.3 NX Remote Manager 3-5

 Chapter
Chapter 3: 3: UsingUsing NX Remote
NX Remote Manager
Manager

Manually import data from a connection

1. Select a connection in the Connection Name column of the Connections dialog box.

2. Click the Import from Connection button.

Set connections options

Options for specifying the behavior of NX Remote Manager connections are listed under AIE in
the Teamcenter Options dialog box.
1. In the Teamcenter rich client, choose Edit→Options.

2. Select AIE from the tree on the left side of the Options dialog box.
The system displays the AIE options in the dialog box.

3. Set the NX Remote Manager options as described in the following table.

General tab
Save log from deleted connections Directs the system to save the transaction log file
for each connection after the connection is deleted.
The log file is saved in the top-level NX Remote
Manager connection directory. The name of the file is
the name of the connection followed by a number to
make it unique. For example, a connection named
UG-RM_001 has a corresponding transaction log file
named UG-RM_001_6671.log.

3-6 NX Remote Manager PLM00123 11.2.3


Export tab
Export Directory
Export read only files as read only
Named References to Export
Check out new components during Specifies that all items that can be checked out are
refresh connection
Import tab
File types to ignore
Import Details Master
NX tab
PLM00123 11.2.3
Using NX Remote Manager
Allows you to define the top-level NX Remote Manager
connection directory. This is the main directory where
the system creates the export directory for each
connection.
Specifies how files associated with datasets to which
you do not have write permission are exported. If
this option is selected, those files are written in the
connection export directory with read-only privileges. If
not checked, all files are written to the export directory
with read/write privileges.
Specifies the named references to export to a
connection. Valid values are:
All
Exports all named references of the dataset.
Select
Displays a dialog box for selecting specific named
references to export.
Primary
Exports the primary named reference for the
dataset.
checked out when the connection is refreshed.
Defines the file types to ignore during import, such as
backup files.
Indicates if the user has permissions to modify import
information in the XML files when importing them back
to Teamcenter. Valid values are:
Application
User is not allowed to change the import information
from Teamcenter.
Both
User is allowed to modify import information from
Teamcenter.
NX Remote Manager 3-7
 Chapter
Chapter 3: 3: UsingUsing NX Remote
NX Remote Manager
Manager

Copy non-master Enables the export of manifestation, specification and

other nonmaster items.

Part Family Members Specifies how to process part family members during
import/export.
Autotranslate Mode Specifies whether autotranslate mode is the default
behavior or whether import should be legacy compatible.

4. Click Apply or OK.

Delete a remote connection

1. In My Teamcenter, choose Tools→Connection.

2. Select the connection, and click Delete Connection.

The connection export directory is deleted, and the persistent connection is removed from your
connection list and from the Teamcenter database.

View transaction logs

1. In My Teamcenter, choose Tools→Connection.

2. Select the connection, and click the Reports button.

The transaction log for the selected connection is displayed. The transaction log viewer allows
you to print the log file or save it as a text or HTML file.

3-8 NX Remote Manager PLM00123 11.2.3

 Using NX Remote Manager

PLM00123 11.2.3 NX Remote Manager 3-9

Chapter 4: Importing and exporting assemblies

Importing and exporting assemblies

NX Remote Manager enables you to import, export, check in, and check out datasets controlled from
one location. When a top-level assembly is imported or exported, all subassemblies and components
can be managed as well.

How Teamcenter imports and exports assemblies

To understand how Teamcenter imports and exports assemblies, you must understand the following
concepts:

• Connection export directory

• Exchange files

• High security

Connection export directory

NX Remote Manager maintains an export directory to manage the export and import operations
of a connection. All files that are exported are accounted for in this directory, which is accessed
by appending the connection export directory to a root directory (default or user specified). The
connection directory allows a subdirectory structure if your application can support it.

Exchange files
NX Remote Manager writes and reads XML exchange files in the connection export directory. An XML
file is written for each file that is exported. These files contain metadata such as product structure,
attribute information, and timestamp information. NX Remote Manager uses this information to
determine which files must be updated when a subsequent export or import operation is performed.
These XML files must reside in the connection export directory for the duration of the connection. If
the contents of the connection directory get moved or copied, the XML files must be moved or
copied along with the application files.

High security
NX Remote Manager exports files with read and write permissions. Those files that are not explicitly
checked out are exported as read-only reference files. On import, only files that have been checked
out can be reimported. This security behavior is referred to as high security and applies to all files
that are managed by a connection.

PLM00123 11.2.3 NX Remote Manager 4-1

 Chapter
Chapter 4: 4: Importing
Importing and exporting
and exporting assemblies
assemblies

Data manager tasks

A connection is created to support offline work or to manage a supplier data sharing environment.
Certain functions, such as creating a new connection or deciding what data needs to be sent through
the connection can only be done if you are a Teamcenter data manager.
The following tasks are performed by a data manager:
• Log on to Teamcenter.

• Select the data to be exported, single items (My Teamcenter) or a BOM line (Structure Manager).

• Check out the data to be modified by the supplier.

• Create a new connection, if required.

Note
Connections keep a history of the data sent to the connection and the data received
from the connection. You can have more than one connection open at any time. This
enables a single data manager to send data to multiple suppliers and keep track of
what has been sent to and received from each supplier.
Every connection has only one owner. The data manager that creates the remote
connection is the connection owner.

• Export the data.

• Import data that has been modified by suppliers.

• Export new data as it becomes available in Teamcenter.

Export assemblies with BOM information

1. In Structure Manager, open the assembly to be exported.

2. Configure the assembly by applying revision rules, variants, and effectivity.

When working with NX assemblies, this configuration is limited to the functionality available in the
ug_clone command line utility. Variants and other configuration options are not supported.

3. After the assembly is configured, choose Tools→Export to Connection.

The system opens the Export Root(s) to Connection dialog box, which is initially empty.

4-2 NX Remote Manager PLM00123 11.2.3

 Importing and exporting assemblies

4. Select an existing connection or create a new connection.

The root directory is populated based on the NX Remote Manager preference setting for the
root directory location.

Note
The system does not validate whether the connection name is unique; however, you
must specify a unique connection name.

5. Select an export rule. For more information, see Export rules.

6. Select the dataset type to be exported from the Dataset Type list.
The list includes all registered NX Remote Manager dataset types that can be exported if found
in the assembly structure.
You can:
• Select a single dataset type to be exported.

• Select multiple dataset types to be exported.

• Select all dataset types to be exported.

• Export all registered dataset types.

After the dataset types are selected, the system displays the top BOM line.

PLM00123 11.2.3 NX Remote Manager 4-3

 Chapter
Chapter 4: 4: Importing
Importing and exporting
and exporting assemblies
assemblies

7. (Optional) Apply export or checkout selections to an entire branch of the assembly by

right-clicking the root node of the assembly and choosing an option.

8. (Optional) Apply one of the following export or checkout selections to single components:
• Skip (None of the boxes are checked.)
The selected datasets under the BOM line are not exported.

• Export (Only the Export box is checked.)

The selected datasets under the BOM line are exported but not checked out (read-only copy).

• Export+CO (Both the Export and Check Out boxes are checked.)
The selected datasets under the BOM line are exported and checked out.

4-4 NX Remote Manager PLM00123 11.2.3

 Importing and exporting assemblies

Note
You can only check out datasets to which you have write access. In addition, if
you attempt to check out datasets that are currently checked out, the system
automatically changes the status from Export+CO to Export.

9. When your selections are complete, click OK.

Exporting without BOM information

When exporting an assembly without BOM information, you must first select an item or item revision.
If you choose an item, the default revision rule specified by the preferences file is used to determine
the appropriate item revision.

Check out a file

1. Choose Tools→Export→To Connection.
The system displays the Connections dialog box.

2. Select an existing connection or create a connection.

The root directory populated in the dialog box is based on the NX Remote Manager preference
setting for the root directory location. You must specify a unique connection name.

3. Click Export.
The system displays the Export Root(s) to Connection dialog box.

The checkout ID displays comments that are applied to all datasets selected for checkout, and
the existing connection is displayed (if applicable).

4. If you do not have an existing connection, check the Create New Connection box.

5. Specify a unique connection name.

PLM00123 11.2.3 NX Remote Manager 4-5

 Chapter
Chapter 4: 4: Importing
Importing and exporting
and exporting assemblies
assemblies

6. Specify the change ID and comments.

These are applied to all datasets for the selected checkout action.

7. Choose an action for each dataset, as follows:

• Skip
Files under this dataset are not exported.

• Export
Files under this dataset are exported but not checked out (read-only copy).

• Export+CO
Files under this dataset are exported and checked out (read/write copy).

Note
You can only check out datasets to which you have write access. In addition, if
you attempt to check out datasets that are currently checked out, the system
automatically changes the status from Export+CO to Export.

8. After you enter all the necessary information, click OK.

Any errors that occur during export are logged in the transaction log for the connection.

Importing data from a remote connection

While working with a remote connection, you can import modified data from the connection export
directory back to the Teamcenter database.
When you import modified files from a remote connection:
• Files that have been modified in the connection export directory are imported as new file versions.

• Files that have not been modified in the connection export directory are skipped and not imported.

Import data from a remote connection to Teamcenter

1. Move all files that need to be imported into the connection export directory.

2. In My Teamcenter, choose Tools→Import→From Connection.

The system displays the Connection dialog box, including the existing ItemID/Rev-ItemName
information for each primary file to be imported.

3. If you have more than one remote connection running, select a connection from the table.

4. Click Import in the Connection dialog box.

4-6 NX Remote Manager PLM00123 11.2.3

 Importing and exporting assemblies

The system analyzes the files to be imported. If no files have been modified or created, the
system detects this and the import operation stops. The system displays the analysis results
in the Comments column of the File(s) to Import dialog box.

5. Apply import options to the individual files using the Action list. The following options are
available:
• Skip
Excludes the file from the import operation.

Note
Skip is the only option available if you do not have write access to the selected
dataset.

• Import–Implicit CO
Implicitly checks out the dataset if it was not checked out at export and imports it to
Teamcenter.

• Import–Overwrite
Imports the dataset and overwrites the existing dataset in Teamcenter.

• Import–Next Rev
Imports the dataset in to the next revision of the item and cancels checkout on the previous
revision of the item.

6. After selecting the files to skip, click OK to import the selected files or Cancel to stop the import
operation.
If you selected Retain checkout, the connection directory is updated with the new item
ID/revision and item type values.

Note
In the case of an NX dataset, this implies an internal call to ug_clone (export – dry
run + actual export).

NX Remote Manager imports the files from the connection’s export directory. After the files have
been imported, the import results display. For import errors from the ug_clone utility, refer to
the syslog file.

7. Click OK to dismiss the dialog box.

Selecting item types during import

If a connection directory contains newly created files, you are given an option to select the item type
to create within Teamcenter for storing the files.

PLM00123 11.2.3 NX Remote Manager 4-7

 Chapter
Chapter 4: 4: Importing
Importing and exporting
and exporting assemblies
assemblies

The list of item types displayed depends on the dataset type specified in the XML file for the new file
and the item types defined in the DMS (data model service) for the dataset type.

Support of subdirectories within the connection directory

If files exist in subdirectories under the main connection directory, the subdirectory information
corresponding to the files is stored in Teamcenter using a relative path. Subsequent exports of this
file use the relative path information to place the file in a subdirectory under the (new) connection
directory.
If a file is found more than once in the connection directory structure, only the first occurrence is
imported and subsequent occurrences are ignored. This is captured in the transaction log file.

4-8 NX Remote Manager PLM00123 11.2.3

Chapter 5: NX Remote Manager administration

NX Remote Manager administration

The NX Remote Manager requires ongoing administration which is performed using utilities and
preferences. In addition, custom item types must be registered with NX Remote Manager before
they can be used with integrated applications.

Register custom item types with NX Remote Manager

Note
Custom item types must be registered with NX Remote Manager before they can be used
with integrated applications. The following example registers custom item types for the NX
Remote Manager.

1. Edit the accaddwg_dms.xml and acadtmpl_dms.xml files located in the ACAD_EM\Data

directory by changing the existing item type to reflect the item type you want to use when new
items are created.
The following example illustrates the changes required to modify the item type from Item to
CORP_Tool in the XML file.

<Info Datasettype="ACADDWG">

<Create>
<!-- <Value>[<itemtype>:<iMANrelation>:<viewtype>]</Value> -->
<Value>Item:Specification:view</Value>
<Value>Document:Manifestation</Value>
<Value>Item:Manifestation:view</Value>

</Create>
…

<Info Datasettype="ACADDWG">

<Create>
<!-- <Value>[<itemtype>:<iMANrelation>:<viewtype>]</Value> -->
<Value>CORP_Tool:Specification:view</Value>
<Value>Document:Manifestation</Value>
<Value>CORP_Tool:Manifestation:view</Value>

</Create>
…

PLM00123 11.2.3 NX Remote Manager 5-1

 Chapter
Chapter 5: 5: NX Remote
NX Remote Manager
Manager administration
administration

2. Open the AdditionalInfo.xml file located in the AcadMgr_DIR\Support directory in a text editor
and add the item types to the file. This file lists the item types that appear in the Boundary
dialog boxes.
The following example shows the AdditionalInfo.xml file.

<?xml version="1.0" encoding="ISO-8859-1"?>

<!--
Copyright (c) 2005 Unigraphics Solutions
Unpublished - All rights reserved
THIS PROGRAM IS AN UNPUBLISHED WORK FULLY PROTECTED BY THE UNITED STATES
COPYRIGHT LAWS AND IS CONSIDERED A TRADE SECRET BELONGING TO THE
COPYRIGHT HOLDER.
The Item Types that will appear in the Boundary Dialogs that can be
accessed from NX Remote Manager.
Update this file if new Item types, which are known to Teamcenter
Engineering, need to be supported by the Boundary Dialogs
This is the GM Overlay version of this file.
28-Jun-2005 aputhenp Initial creation
28-Jun-2005 aputhenp The first line has to be ?xml....
$HISTORY$
-->

<BoundaryTypes>
<Type>MEStation</Type>
<Type>MEWorkarea</Type>
<Type>MELine</Type>
<Type>MEDepartment</Type>
<Type>MESite</Type>
<Type>MEPlant</Type>
<Type>CORP_Facility</Type>
<Type>CORP_Tool</Type>
<Type>CORP_Part</Type>
<Type>CORP_Vehicle</Type>
<Type>CORP_Criteria</Type>
<Type>CORP_Proc_Plan</Type>
<Type>CORP_Simulation</Type>
<Type>CORP_Analysis</Type>
<Type>CORP_Process</Type>
<Type>CORP_Equipment</Type>
<Type>CORP_Install</Type>

</BoundaryTypes>

3. After modifying the XML files, open an MS-DOS window in the Teamcenter environment, and
enter the following command on a single line:
aie_install_datamodel_objs -u=user-name
-p=password -g=dba —file=acaddwg_dms.xml -modify=yes

For more information about the aie_install_datamodel_objs utility, see

aie_install_datamodel_objs.

5-2 NX Remote Manager PLM00123 11.2.3

 NX Remote Manager administration

Note
When modifying the XML files, consider the following guidelines:
• Do not modify the xName element of the existing xRelation. You can add new
XRelation elements, but they must be constant between versions of XML.

• If you do not specify the -modify argument for the aie_install_datamodel_objs

utility, no modifications are performed.

4. If you do not have access to the XML files used to initially install the data model objects, run the
following program to delete existing instances of the dataset types:
aie_clean_datamodel_objs -dstype=all

Note
You can selectively delete instances corresponding to a particular dataset type by
specifying a dataset type name for the -dstype= argument.

For more information about the aie_clean_datamodel_objs utility, see

aie_clean_datamodel_objs.

5. After deleting the dataset type instances by running the aie_clean_datamodel_objs utility,
run the aie_install_datamodel_objs utility without the -modify argument to populate the data
model instances.

Preferences and utilities

Preferences and utilities are used to set up and configure NX Remote Manager.

Preferences
Preferences are used to configure NX Remote Manager. Preferences are environment variables
stored in the database and are read when a Teamcenter session or a session of an integrated
application is initiated. For more information about preferences, see the Preferences and Environment
Variables Reference.

PLM00123 11.2.3 NX Remote Manager 5-3

 Chapter
Chapter 5: 5: NX Remote
NX Remote Manager
Manager administration
administration

AIE_EM_installed

DESCRIPTION
Specifies whether or not a site has AIE (Application Integration Environment)
Encapsulation Manager installed.
VALID
VALUES
YES AIE Encapsulation Manager is installed.
NO AIE Encapsulation Manager is not installed.
DEFAULT
VALUE
NO
DEFAULT
PROTECTION
SCOPE
Site preference.

5-4 NX Remote Manager PLM00123 11.2.3

 NX Remote Manager administration

AIE_installed

DESCRIPTION
Indicates whether or not a site has AIE (Application Integration Environment) installed.
VALID
VALUES
YES AIE (Application Integration Environment) is installed.
NO AIE (Application Integration Environment) is not installed.
DEFAULT
VALUE
NO
DEFAULT
PROTECTION
SCOPE
Site preference.

PLM00123 11.2.3 NX Remote Manager 5-5

 Chapter
Chapter 5: 5: NX Remote
NX Remote Manager
Manager administration
administration

AIE_named_refs_to_export

DESCRIPTION
Allows you to specify the named references to export to a connection.
VALID
VALUES
all Exports all named references of the dataset.
select Displays a dialog box allowing you to select the named references to
export.
primary Exports the primary named reference of the dataset.
DEFAULT
VALUE
primary
DEFAULT
PROTECTION
SCOPE
Site preference.

5-6 NX Remote Manager PLM00123 11.2.3

 NX Remote Manager administration

AIE_overwrite_default_import_item_types

DESCRIPTION
Controls whether the default item types can be overwritten during import using NX
Remote Manager.
VALID
VALUES
on Allows the user to choose from all item types listed in the DMS when
importing new or previously exported files.
off Disables item type selection when importing files. Files that were
previously exported from Engineering Process Management are imported
using the item type assigned when they were exported, and new files are
imported using the default item type.
DEFAULT
VALUE
on
DEFAULT
PROTECTION
SCOPE
Site preference.

PLM00123 11.2.3 NX Remote Manager 5-7

 Chapter
Chapter 5: 5: NX Remote
NX Remote Manager
Manager administration
administration

AIE_skip_class_types_for_save

DESCRIPTION
Specifies item types that must not be displayed as options in the Item Type list in the
Save dialog box when saving a file in an integrated application. For example, business
rules in the GM Overlay prevent items of type Item from being created. Adding Item
as a value for this preference prevents the item type from being a choice when items
are saved in NX Remote Manager.
VALID
VALUES
Any valid item type for which creation is disallowed.
DEFAULT
VALUE
This preference is unset in the Engineering Process Management environment. In the
Teamcenter Automotive Edition–GM Overlay environment, the default value is Item.
DEFAULT
PROTECTION
SCOPE
Site preference.

5-8 NX Remote Manager PLM00123 11.2.3

 NX Remote Manager administration

AIE_POST_EXPORT_SCRIPT

DESCRIPTION
Specifies a fully qualified path to an executable script that are executed after the
completion of NX Remote Manager export operation.
VALID
VALUES
Path to the script. This path must not contain special characters or spaces. In addition,
the path separator must be in accordance with the platform on which the script runs,
for example:
UNIX systems:
AIE_POST_EXPORT_SCRIPT=/usr/bin/my_export.sh

Windows systems:
AIE_POST_EXPORT_SCRIPT=C:\Utilities\my_export.bat
DEFAULT
VALUE
By default, this preference is not set.
DEFAULT
PROTECTION
SCOPE
Site preference.

PLM00123 11.2.3 NX Remote Manager 5-9

 Chapter
Chapter 5: 5: NX Remote
NX Remote Manager
Manager administration
administration

AIE_PRE_IMPORT_SCRIPT

DESCRIPTION
Specifies a fully qualified path to an executable script that will be executed before the
NX Remote Manager import operation begins.
VALID
VALUES
Path to the script.
DEFAULT
VALUE
By default, this preference is not set.
DEFAULT
PROTECTION
SCOPE
Site preference.

Utilities
Command line utilities are used to install and maintain the NX Remote Manager data model and to
import files in batch mode. For more information about utilities, see the Utilities Reference.

5-10 NX Remote Manager PLM00123 11.2.3

 NX Remote Manager administration

aie_clean_datamodel_objs

DESCRIPTION
Deletes instances of a specific dataset type or instances of all dataset types from the
NX Remote Manager data model.
SYNTAX
aie_clean_datamodel_objs -u=user-id -p=password -g=group
-dstype=all | datasettype-name
ARGUMENTS
-dstype Specifies the dataset type for which instances will be deleted.
ENVIRONMENT
As specified in Configuring utilities.
FILES
As specified in Log files.
RESTRICTIONS
None.
EXAMPLES
• The following example unregisters all dataset types that are registered in the NX
Remote Manager data model:
aie_clean_datamodel_objs -u=infodba -p=password -g=dba
-dstype=all

• The following example unregisters the NX Remote Manager data model for the
UGMASTER dataset type:
aie_clean_datamodel_objs -u=infodba -p=password -g=dba
-dstype=UGMASTER

PLM00123 11.2.3 NX Remote Manager 5-11

 Chapter
Chapter 5: 5: NX Remote
NX Remote Manager
Manager administration
administration

aie_install_datamodel_objs

DESCRIPTION
Adds, modifies, and deletes data model definitions based on customer-defined item
types.
SYNTAX
aie_install_datamodel_objs -u=user-id -p=password -g=group
-file=dms_definition_file [-modify=yes]
ARGUMENTS
-file Specifies the name of the file containing the NX Remote Manager
data model definition. The NX Remote Manager data model file is
written using XML syntax, which must follow the document type
definition in the dms.dtd file.
-modify Specifies whether the NX Remote Manager data model is
overwritten. The value yes overwrites the data model.
ENVIRONMENT
As specified in Configuring utilities.
FILES
As specified in Log files and the aie_install_datamodel_objs183e5050.log and
aie_install_datamodel_objs183e5050.jnl files.
RESTRICTIONS
The -modify argument must only be used with the value yes. If the
aie_clean_datamodel utility was previously run for the same dataset type, you do not
need to specify the -modify argument.
EXAMPLES
The following example registers the UGMASTER dataset with NX Remote Manager by
providing an NX Remote Manager data model definition for the dataset type:
aie_install_datamodel_objs -u=infodba -password=password -g=dba
-file=ugmaster_dms.xml -modify=yes

5-12 NX Remote Manager PLM00123 11.2.3

 NX Remote Manager administration

BatchImp

DESCRIPTION
Imports multiple files in to the Teamcenter database without starting the integrated
CAD application.
SYNTAX
BatchImp [-r] [-q] [-n] input-file-name -u=user-id -p=password -g=group
[-f=Teamcenter folder] [-n ] [-x] [-xml] [-d=dataset-type] [-dryrun]
ARGUMENTS
input file Specifies the input map file containing the list of drawings with item
ID, item type, and specified attributes.
-r Specifies that if the drawing was previously imported in to
Teamcenter, it should be imported under a new item revision. This
argument is optional.
-q Specifies whether the user should be prompted for each previously
imported drawing to be reimported. If the drawing is to be imported
as specified by the user, the -r option is used to determine whether
a new item revision is created. This argument is optional.
-n Specifies that only those drawings that have not previously been
imported in to Teamcenter are imported. This argument is optional.
-x Specifies that the batch import only creates the according IXF files
and uses the aie_batch_import.exe utility to perform the import
operation. If this argument is not specified, the batch import .arx file
performs the import without creating the .ixf files.
-xml Generates the IXF file for a specific drawing.
This option does not import the drawing files in to the Teamcenter
database. It is intended to create the IXF files that are required
when importing drawings in NX Remote Manager mode.
-u Specifies the user ID used to log in to the Teamcenter database.
This argument is required unless single sign-on (SSO) in Security
Services is enabled. If SSO is enabled, this argument is not
necessary and is ignored if provided.
-p Specifies the password used to log in to the Teamcenter database.
This argument is required unless single sign-on (SSO) in Security
Services is enabled. If SSO is enabled, this argument is not
necessary and is ignored if provided.
-g Specifies the group of the user logging in to the Teamcenter
database. This argument is required.
-f Specifies the Teamcenter folder in which items or item revisions
are created for the imported files. If not specified, the default is the
Newstuff folder. This argument is optional.
-d Specifies the dataset type of the Teamcenter dataset object to which
the imported files are attached.

PLM00123 11.2.3 NX Remote Manager 5-13

 Chapter
Chapter 5: 5: NX Remote
NX Remote Manager
Manager administration
administration

-dryrun Specifies a dry run that generates a new output file named by
appending _dryrun to the original input map file name. For each
drawing file specified in the input map file, the dryrun option
traverses the drawing and transcribes the original input line along
with the file names of every component file, if inputting an assembly,
to the output file in bottom-up fashion. The output file gives the
user a clear view of the files involved in the import operation. The
output file also serves as a new input map file to the batch import
program. When the dryrun option is specified, only the input map
file must be specified.
ENVIRONMENT
This utility must be run from the command line in an MS-DOS shell with all Teamcenter
environment variables set appropriately.
FILES
None.
RESTRICTIONS
None.
NOTES
• All drawings imported to Teamcenter without using the -x option have the item ID
and item revision stored as attributes in the Teamcenter data directory.

• If the batch import finds the attributes for item ID and item revision in the
Teamcenter data dictionary and values are assigned to them, the file is imported
by default unless the -n argument is used.

• If the -r argument is not used, the drawing is imported in to the existing item
revision.

• Automatic assignment of new item revision identifiers is supported for item

revisions identified by alphabetic characters and numbers.

• When specifying attribute names for general attribute batch import, names must
reflect the Teamcenter attribute name rather than the CAD application attribute
name.

• Errors appear in the batch import log file when importing multilevel assemblies.

• During batch import, BOM view revisions are not updated when an assembly is
reimported in to the current item revision. After importing the assembly using the
batch import utility, create the BOM view revision in the two-tier rich client by
sending the parent component to Structure Manager, adding the child items in
Structure Manager, and saving the structure.

EXAMPLES
In this example, the user imports two drawings, as follows:
test_batch_1.dwg
\
test_batch_3.dwg
test_batch_2.dwg

5-14 NX Remote Manager PLM00123 11.2.3

 NX Remote Manager administration

test_batch_1.dwg and test_batch_2.dwg are independent drawings.

test_batch_3.dwg is attached as an external reference (attachment or overlay) to
test_batch_1.dwg.
The following input file is used to import the drawings.
Attributes,itemID,itemtype,MachNum
D:\IMANConnection\connection1\test_batch_1.dwg,000123,Item,23
D:\IMANConnection\connection1\test_batch_2.dwg,000124,Item,24
D:\IMANConnection\connection1\test_batch_3.dwg,,,25

The first line in the file is mandatory. The entries Attributes, itemID, and itemtype
are required. The MachNum entry represents the name of an attribute to be input
during import.
The first entry in the second line of the file specifies the full path to the drawing being
imported. The other entries in this line are the item ID, item type, and the value of
the MachNum attribute.
The fourth line contains entries for the item ID and type. These can be left blank, in
which case the item ID are generated automatically, and the item type defaults to Item.

Warning
This file must be edited using a text editor, such as Notepad. In addition, the
file must end with a new-line character.

PLM00123 11.2.3 NX Remote Manager 5-15

Appendix A: Glossary

access control list (ACL)

Access Manager component that contains a list of accessors and, for each accessor, the privileges
granted, denied, and not set.

BOM view revision (BVR)

Workspace object that stores the single-level assembly structure of an item revision. Access can be
controlled on the structure (BOM view revision) independently of other data. BOM view revisions are
meaningful only in the context of the item revisions for which they are created.

connection name
Automatically generated or user-provided name that identifies the connection between Teamcenter
and Teamcenter Integration for AutoCAD.

NX Remote Manager
Teamcenter component for managing the import and export of documents into Teamcenter. NX
Remote Manager is a common component across integrations that include applications in fields
such as CAE and ME.

PLM00123 11.2.3 NX Remote Manager A-1

Siemens Industry Software

Headquarters
Europe
Granite Park One
Stephenson House
5800 Granite Parkway
Sir William Siemens Square
Suite 600
Frimley, Camberley
Plano, TX 75024
Surrey, GU16 8QD
USA
+44 (0) 1276 413200
+1 972 987 3000

Asia-Pacific
Americas
Suites 4301-4302, 43/F
Granite Park One
AIA Kowloon Tower, Landmark East
5800 Granite Parkway
100 How Ming Street
Suite 600
Kwun Tong, Kowloon
Plano, TX 75024
Hong Kong
USA
+852 2230 3308
+1 314 264 8499

About Siemens PLM Software

© 2016 Siemens Product Lifecycle Management

Siemens PLM Software, a business unit of the Siemens
Software Inc. Siemens and the Siemens logo are
Industry Automation Division, is a leading global provider
registered trademarks of Siemens AG. D-Cubed,
of product lifecycle management (PLM) software and
Femap, Geolus, GO PLM, I-deas, Insight, JT, NX,
services with 7 million licensed seats and 71,000 customers
Parasolid, Solid Edge, Teamcenter, Tecnomatix and
worldwide. Headquartered in Plano, Texas, Siemens
Velocity Series are trademarks or registered trademarks
PLM Software works collaboratively with companies
of Siemens Product Lifecycle Management Software
to deliver open solutions that help them turn more
Inc. or its subsidiaries in the United States and in other
ideas into successful products. For more information
countries. All other trademarks, registered trademarks
on Siemens PLM Software products and services, visit
or service marks belong to their respective holders.
www.siemens.com/plm.