Teamcenter Integration for Solid Edge (SEEC) Guide for ... · SIEMENS Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators SEECAdminGuide • 2020

SIEMENSSIEMENSSIEMENS

TeamcenterIntegration for SolidEdge (SEEC)

Guide for Users andAdministrators

SEECAdminGuide • 2020

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Part I: Installation and configuration

System requirements for the Teamcenter Integration for Solid Edge (SEEC) . . . . . . . . . . . 1-1

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Preparing your Teamcenter environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Prepare your Teamcenter environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Applying the SEEC Feature Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Introduction to FMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Teamcenter Client Communication System (TCCS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Enable and configure TCCS after installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Teamcenter Security Services (TcSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Modify single sign-on Teamcenter environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Installing Solid Edge with the Teamcenter Integration for Solid Edge (SEEC) . . . . . . . . . . 3-1

Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Verifying your installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Configuring the Teamcenter-managed environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Defining Teamcenter preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Define a preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Property mapping definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Define the list of available Item Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Define default Item types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42-Tier and 4-Tier configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Prerequisites for 2-Tier configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Configuring Solid Edge Embedded Client as a 2-tier client . . . . . . . . . . . . . . . . . . . . . . . 4-6

Sizing 4–Tier Teamcenter deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Enabling image file generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Part, Sheet Metal, and Draft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

SEECAdminGuide 2020 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators 3

Contents

2D draft files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Defining site-level separator options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Add a site-level separator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Using display names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Using multifield keys in the Teamcenter managed environment . . . . . . . . . . . . . . . . . . . . . . 4-14

Part II: Working with Teamcenter-managed documents

Working with managed documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Understanding Teamcenter terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Connecting to Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Understanding the Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Using the Structure Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Managing document releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Changing the workflow of a document in Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . 5-3Viewing the process in the Workflow Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Viewing the document status in Solid Edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Revising documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Multi-CAD in the Teamcenter managed environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Multi-CAD in the Teamcenter managed environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Multi-CAD document workflow (SEEC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Take Ownership command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Take ownership of a foreign CAD document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Attribute mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Attribute synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Unidirectional and bidirectional synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2NULL value synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Attribute mapping syntax and examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Edit the attribute mapping file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Attribute mapping of physical properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Additional attribute mapping examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Preparing unmanaged documents for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Preparing unmanaged documents for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Importing non-Solid Edge documents into Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Add unmanaged documents to Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Overwriting documents using Add To Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7Output files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8

Using automated utilities to import unmanaged Solid Edge data into Teamcenter . . . . . . . . . . 8-10

Using the Data Preparation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Considerations before accessing the Data Preparation Utility . . . . . . . . . . . . . . . . . . . . . . . . 9-1Data Preparation Utility workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Perform a Solid Edge file analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

4 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators SEECAdminGuide 2020

Contents

Contents

Analysis report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5Fix links in Solid Edge files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9Modify Solid Edge files using the Data Preparation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11Import process checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

Add to Teamcenter - Interactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Add to Teamcenter - Interactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1Enable or disable the Add Document to Teamcenter command . . . . . . . . . . . . . . . . . . . . . . 10-2

Part III: Troubleshooting

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Display Start menu entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1Save weldment bodies to Teamcenter for visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1Run SEEC diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2Export attribute mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3BOM diagnostic log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3Teamcenter rich client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4Item is the only Item Type available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5Duplicate Item IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5BOM View Revision not created or updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6Missing Property for Synchronous file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6Troubleshooting Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

Solid Edge Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Solid Edge Embedded Client best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Assembly best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Use Hide All Components to efficiently work with large assemblies . . . . . . . . . . . . . . . . . . A-1Use Version from Cache to optimize performance with large assemblies . . . . . . . . . . . . . . A-2Configure Teamcenter structure expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Use Auto-Select when opening simplified assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Cache Management best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Provide a private cache for each user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Manually clear cache before redefining cache location . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Data Preparation Utility command line reference material . . . . . . . . . . . . . . . . . . . . . . . . B-1

Analyze Solid Edge files using command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Fix broken links using command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2Modify Solid Edge files using command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

PDM Integration tool command line reference material . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Run the PDM integration tool using command line options . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Teamcenter Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1


Contents

Preface

This manual describes installation, configuration, and administrative processes used to work withSolid Edge documents managed by Teamcenter.

Note

This document supplements the Solid Edge help installed with Solid Edge 2020.

Audience

This manual is intended for administrators, or users with administrator roles, who want to implementand support Solid Edge in a Teamcenter-managed environment. An understanding of Solid Edgeand Teamcenter concepts is required.

Conventions

The following conventions are used to emphasize information:

Tip

Indicates information that helps you apply the techniques and procedures described in thetext.

Note

Identifies general instructions or comments that need to be emphasized.

Caution

Identifies practices that can either produce results contrary to what you expect or resultin damage to software or data.

Warning

Identifies practices that could result in permanent loss of data or software.

Teamcenter documentation

Teamcenter documentation is provided outside the context of this document as help and as printablemanuals:


Preface

• You can access help from the menu bar of a Teamcenter rich client application or by clicking oneof the links under the Help icon in the Teamcenter thin client user interface.

• You can access the printable manuals from the Teamcenter Documentation CD-ROM. To viewthe PDF-formatted manuals, use Adobe Acrobat Reader.

Submitting comments

Please feel free to give us your opinion of the usability of this manual. To suggest specificimprovements, and to report errors, submit your comments online using the support tools athttps://www.plm.automation.siemens.com/global/en/support.

8 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators SEECAdminGuide 2020

Preface

https://www.plm.automation.siemens.com/global/en/support/

Part I: Installation and configuration

The Teamcenter Integration for Solid Edge, also known as Solid Edge Embedded Client, providesseamless connectivity between Solid Edge and Teamcenter. As you work in Solid Edge, you usecommands and supporting tools to interact with the Teamcenter data structure to manage yourdocuments.

To begin using Solid Edge with the Teamcenter integration:

• Ensure system requirements are met.

• Prepare your Teamcenter environment on both the server and clients.

• Install Solid Edge with the Teamcenter Integration for Solid Edge (SEEC) on the clients.

• Configure the Teamcenter-managed environment.

SEECAdminGuide 2020 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators

Chapter 1: System requirements for the TeamcenterIntegration for Solid Edge (SEEC)

The following are the hardware, operating system, software, and licensing requirements for installingSolid Edge with the Teamcenter Integration for Solid Edge, also known as Solid Edge EmbeddedClient (SEEC).

HardwareThe hardware running Solid Edge and the Teamcenter integration must meet the minimumrequirements for Solid Edge and Teamcenter as stated in their respective documentation.

Hardware recommendations for Solid Edge are available both in the readme.htm file delivered withthe product and on the web at http://www.plm.automation.siemens.com/. In the web page:

• Choose Products→View by Product Lines→Solid Edge.

• Choose Resources→System Requirements.

The recommended hardware configuration for systems importing large amounts of unmanageddata into Teamcenter is:

• 64-bit (x64) processor

• 8 GB RAM (Minimum)

• True Color (32–bit) or 16 million colors (24–bit)

• Screen resolution set to 1280 x 1024 or higher

• 6+ GB disk space (required for installation)

Unmanaged data being imported into Teamcenter is copied to the local drive (SEEC cache). Theamount of free disk space on your disk must be greater than the size of unmanaged data beingimported into Teamcenter.

Note

Refer to the Considerations before accessing the Solid Edge to Teamcenter utilitiesportion of this document for additional information.

For additional information, be sure to consult the Solid Edge readme.htm and SEEC_Readme.htmfiles.

SEECAdminGuide 2020 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators 1-1

http://www.plm.automation.siemens.com/en_us

Chapter 1: System requirements for the Teamcenter Integration for Solid Edge (SEEC)

Operating SystemSupported operating systems and other information is available both in the Solid Edge readme.htmfile delivered with the product and on the web at http://www.plm.automation.siemens.com/. In theweb page:

• Choose Products→View by Product Lines→Solid Edge.

• Choose Resources→System Requirements.

This release of Solid Edge has been certified to run on the following:

• Windows 7 Enterprise, Ultimate, or Professional (64-bit only) with Service Pack 1

• Windows 8.1 Professional or Enterprise (64-bit only)

• Windows 10 Enterprise or Professional (64-bit only) version 1511 or later

• Internet Explorer 11

Be sure to consult the Solid Edge readme.htm file for the latest information available.

1-2 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators SEECAdminGuide 2020


http://www.plm.automation.siemens.com/en_us

System requirements for the Teamcenter Integration for Solid Edge (SEEC)

SoftwareTo use Solid Edge with Teamcenter for document management, the following software is required:

• Solid Edge 2020 and a license for the Teamcenter Integration for Solid Edge (SEEC)

• SEEC Feature Package

Installed on the Teamcenter corporate server.

Solid Edge 2020 with the Teamcenter integration is compatible with the following:

Solid Edge Teamcenter 11.2 Teamcenter 12 Active Workspace - Hosted

2020

11.3.0.1

11.4

11.5

11.6

12.1

12.2

3.4

4.0

4.1

4.2Windows 10 (10587.0 or higher) is supported on ST8MP3, Teamcenter 10.1.6, 11.2.2 or higher

SEEC Feature packages for Tc11.x and 12 are compatible with Deployment Center 2.0+

Solid Edge ST9 was the first release integrating a hosted Active Workspace client.

Solid Edge ST10 was the last release supporting Windows 7.

Solid Edge Embedded Client 2020 does not support:

• Teamcenter 8.x, 9.x, 10.0, 11.1

Solid Edge ST8 was the last release supporting Teamcenter 9.1.

• Any Teamcenter release prior to 8.x.

• Teamcenter Express

Support for Smart Codes reached end-of-life with Teamcenter Express. Solid Edge does notsupport Smart Codes.

• The Windows 10 browser, Microsoft Edge.

Note

Consult the SEEC_readme.htm file for specific software compatibility information as wellas maintenance pack and patch information.

LicensingWhen you purchase Solid Edge or Solid Edge Premium with the Teamcenter integration (SEEC), youreceive the license file SElicense.lic customized for your installation.

The license for running Solid Edge Embedded Client as an integration of Solid Edge and Teamcenterincludes the entry:


System requirements for the Teamcenter Integration for Solid Edge (SEEC)


FEATURE seembeddedclient

The prerequisite for using Solid Edge in a Teamcenter managed environment is a Teamcenter Authorlicense. Additional configurations may include:

Solid Edge License Type Support for Solid Edge Embedded Client

Premium License can be purchased for Solid EdgeEmbedded Client support

Classic License can be purchased for Solid EdgeEmbedded Client support

Foundation License can be purchased for Solid EdgeEmbedded Client support

Design and Draft License can be purchased for Solid EdgeEmbedded Client support

Solid Edge 2D Drafting (with maintenance) Includes support for Solid Edge Embedded ClientSolid Edge Free 2D Drafting No support for Solid Edge Embedded Client

Licensing information for Solid Edge can be found in the Solid Edge Installation and Licensing guide.

Note

For assistance with licensing, please contact your Siemens PLM Software Solution Partner.



Chapter 2: Preparing your Teamcenter environment

Prepare your Teamcenter environmentBefore installing Solid Edge with the Teamcenter Integration (SEEC), ensure your Teamcenterenvironment is ready on both the server and client:

• Apply the SEEC Feature Package on your Teamcenter server.

• Configure File Management System (FMS) on the Teamcenter server and client.

• Enable and configure Teamcenter Client Communication System (TCCS) on your server.

• (Optional) Configure Teamcenter Security Services (TcSS) on your sever.

Applying the SEEC Feature PackageThe Solid Edge Embedded Client Feature Package contains the SEEC schema that is required forTeamcenter. The template is used by the Teamcenter Environment Manager (TEM) and is requiredfor new installations of Teamcenter or upgrades to Teamcenter. You should review Teamcenterdocumentation when upgrading an existing Teamcenter installation. This is critical to a successfulupgrade.

Note

• Feature packages are available for download from Siemens PLM Download Serverunder the Solid Edge folder structure. A WebKey is required.

• Business Modeler IDE (BMIDE) is not required to install the SEEC Feature Packages.

1. On the Teamcenter server, start the Teamcenter Environment Manager (TEM).

2. On the Select Features dialog box, click Browse and locate the \SEEC Administrator\SEECFeature Packages\SEECFeaturePackageTc<version> folder, where Tc<version> represents yourinstallation of Teamcenter. Select feature_seec.xml.

3. On the Select Features dialog box, under Extensions, select Teamcenter Integration for SolidEdge Feature Package from the feature list.

Caution

Do not browse for the SEEC Feature Package in the Business Modeler IDE Templatesdialog box.


https://download.industrysoftware.automation.siemens.com/


4. In the Database Template Summary dialog box, you should see the template named Solid EdgeEmbedded Client Feature Package, and the template file seec_template.xml.

If the Solid Edge Embedded Client Feature Package was previously applied to your Teamcenterinstallation, your Teamcenter upgrade plan should consider impacts to your Solid EdgeEmbedded Client Feature Package. See Teamcenter documentation for details.

Updating the Solid Edge Embedded Client Feature Package

When the Solid Edge Embedded Client Feature Package needs to be updated, you should:

• Follow Teamcenter documented procedures for updating a feature package. This must include afull backup of Teamcenter.

Note

This procedure does not capture every possible Teamcenter deployment scenario.

• Start Teamcenter Environment Manager (TEM).

• Perform maintenance on an existing configuration.

• Update the database by choosing Full Model – System downtime required.

1. Select Solid Edge Embedded Feature Package (seec).

2. Browse and select feature_seec.xml.

The row associated with the template name Solid Edge Embedded Client Feature Packageshould update to indicate a template refresh.

3. Select the Apply check box for Solid Edge Embedded Client Feature Package.

4. Confirm your selections. You should see the Solid Edge Embedded Client Feature Package(seec) in the list.

5. Click Next to install.

6. Restart your 4-tier configuration.



Preparing your Teamcenter environment

Introduction to FMSFile Management System (FMS) is a file storage, caching, distribution, and access system deliveredwith the Teamcenter rich client as part of TCCS. Solid Edge Embedded Client uses FMS to exchangefiles with Teamcenter.

FMS consists of two components:

• FMS server cache (FSC)

Provides a shared, secure, server-level cache. It uploads and downloads files to other FSCsand to client caches.

• FMS client cache (FCC)

Provides a private user-level cache on your computer. The FCC provides a high-performancecache for both downloaded and uploaded files. The FCC provides proxy interfaces to clientprograms and connectivity to the server caches and volumes.

Managing the FCC

File Management System is configured using Teamcenter Environment Manager (TEM). Duringinstallation, TEM prompts for the appropriate parameters, creates the .xml configuration files, andinstalls and starts the FSC.

The FMS client configuration file (fcc.xml) is installed for each client. This file identifies the file serverused to download the FCC configuration, contains FCC routing information, and default parametervalues. Occasionally, the FCC process executing in memory must be restarted if it is not respondingto pipe connection attempts. For example, when any of the following events occur:

• The %FMS_HOME%/bin/fccstat –status command reports that the FCC is offline.

• The %FMS_HOME%/bin/fccstat –start command cannot start the FCC.

• The %FMS_HOME%/startfcc.bat reports that the FCC cache is locked.

To restart a FCC process:

1. Close all client applications.

2. Wait 10 seconds.

3. From a command prompt, run %FMS_HOME%/bin/fccstat –restart.

Alternately, you can stop and then restart the FCC process:

1. Close all client applications

2. Wait 10 seconds.

3. From a command prompt, run %FMS_HOME%/bin/fccstat –stop.

4. Wait 10 seconds.

5. Run %FMS_HOME%/bin/fccstat –start.




Use the –status option to verify the Teamcenter server you are connected to:

1. From a command prompt, run %FMS_HOME%/bin/fccstat –status.

2. Note the assigned FSC in the Servers section of the response.

If you are having trouble starting FMS, verify that the values of the following environment variablesare properly defined:

• JAVA_HOME

Set the JAVA_HOME environment variable to the location of the Java software development kit.

• JRE_HOME

Set the JRE_HOME environment variable to the location of the 32–bit Java JRE on your system.

For more information about required versions of Java for Teamcenter, see the Teamcenter SoftwareCertifications certification database:

http://support.industrysoftware.automation.siemens.com/certification/teamcenter.shtml

You can download and install the appropriate Java version from http://java.com.

Configuring FMS for HTTPS

You can configure File Management System (FMS) to use either the hypertext transfer (HTTP)protocol or a secure server layer (HTTPS) protocol. HTTPS creates a secure channel over aninsecure network. This protection method uses verified and trusted server certificates, private keys,and public keys. You set the protocol during installation from Teamcenter Environment Manager(TEM), using the FSC Non-Master Settings panel and the Proxy tab in the File Client Cache panel.

If you chose the HTTP protocol for FMS during installation and want to use the HTTPS protocol,you must:

• Modify the FMS master file to reflect the HTTPS address.

• Add the URL of the local HTTPS host to the list of servers defined in the Fms_BootStart_UrlsTeamcenter preference.

• Update any installed FCCs by changing the parentfsc address in the fcc.xml file to use thehttps protocol.

Note

For complete information about File Management System (FMS), refer to the SystemAdministration Guide in the Teamcenter help collection.




http://java.com


Teamcenter Client Communication System (TCCS)The Teamcenter Client Communication System (TCCS) manages communication and file transfersbetween Teamcenter clients and servers. TCCS contains the File Management System (FMS)Client Cache (FCC) which uploads files from your workstation to Teamcenter and also downloadsrequested files from Teamcenter to your workstation.

TCCS is installed:

• When you install the Teamcenter rich client.

This is the most common method when Solid Edge is used with Teamcenter.

• Using the standalone installation wizard.

• By using the over-the-web installer.

Note

TCCS installation or configuration requires that Java is installed on your client. Forinformation regarding minimum required versions of Java, see the Teamcenter SoftwareCertifications database:


Enable and configure TCCS during rich client installation

While the use of TCCS is not required, it is recommended. To use TCCS you must enable andconfigure it using the Teamcenter Environment Manager (TEM). To enable TCCS during rich clientinstallation:

1. Click Advanced in the File Client Cache (FCC) panel.

2. Select the Use Configuration and Environments check box in the Client CommunicationSystem Switch panel.

Note

For complete information about Teamcenter Client Communication System (TCCS), referto the System Administration Guide in Teamcenter help.

Enable and configure TCCS after installation

To enable and configure TCCS after rich client installation:

1. Start Teamcenter Environment Manager (TEM).

2. Choose Start → Teamcenter Environment Manager.

3. In the Maintenance panel, choose Configuration Manager.

4. In the Configuration Maintenance panel, select Perform maintenance on an existingconfiguration.





5. In the Old Configuration panel, select the configuration you want to modify.

6. In the Feature maintenance panel, under Client Communication System, select UseConfigurations and Environments.

7. In the Client Communication System Switch panel, select the Use Configuration andEnvironments check box.

8. In the Configuration Selection for Client Communication System panel, select Shared.

Selecting Shared allows accounts other than the installation account to use it.

9. In the Forward Proxy Settings panel, specify whether to use a forward proxy.

10. In the Environment Settings for Client Communication System panel, click Add, and then typethe required information to create the TCCS environment.

11. In the Reverse Proxy Settings panel, accept the default values.

12. Proceed to the Kerberos Authentication Settings panel. If you use Kerberos authentication, enterKerberos authentication settings.

Note

For more information about Kerberos authentication in Teamcenter and using SecurityServices, see the Teamcenter Security Services Installation/Customization guide.

13. Proceed to the Secure Socket Layer (SSL) Settings panel. If you use SSL, specify SSL settings.

Note

For more information about configuring SSL for Teamcenter, see the TeamcenterSecurity Services Installation/Customization guide.

14. In the Client Tag Filter panel, accept the default value or type a different value.

The Client Tag Filter specifies a pattern to apply when filtering TCCS environments. Wildcardcharacters (*) are allowed.

15. In the Confirmation panel, review the settings you entered and click Start to apply theconfiguration changes.

Note

Solid Edge Embedded Client supports multiple Teamcenter releases. The instructionsfor each release may differ slightly. Consult release specific Teamcenter documentationfor details.




Teamcenter Security Services (TcSS)While its use is optional, any Solid Edge application that requires a Teamcenter logon (such as SolidEdge with Embedded Client, Structure Editor, Add to Teamcenter) can take advantage of TeamcenterSecurity Services using single sign-on (SSO), provided that an SSO enabled database is activated.When you use single sign-on, you log onto a Teamcenter enabled single sign-on application. Thedefault group and role are assigned. Then the next application uses those credentials and submitsthem to the authentication authority. You are not required to log on again. A background windowholds the token while you are authenticated. Dismissing the window deletes the token.

Teamcenter Security Services is available to both 2-tier and 4-tier connections. In Solid EdgeEmbedded Client, defining a single sign-on enabled environment is accomplished in the same way asdefining any other Teamcenter environment, except that you must enter the corresponding applicationID and logon service URL for the Teamcenter Security Service enabled environment you specified.The Teamcenter database URL you specify is added to the list and is displayed in green for easyidentification. Only one Teamcenter environment URL that is single sign-on enabled can be active ata time. Choose the URL from the list and select Activate to make an environment active.

Note

For complete information about Teamcenter Security Services, including installation, referto Security Services Installation/Customization in the Teamcenter help collection.

Modify single sign-on Teamcenter environments

Configure Teamcenter Client Communication System (TCCS) and Teamcenter Security Services(TcSS) before running Solid Edge.

1. Access the Define Teamcenter Environments dialog box by selecting Start→Siemens SolidEdge 2020→Choose PDM Integration→Define Teamcenter Environments.

2. Click the TCCS button to retrieve information regarding servers that have Teamcenter ClientCommunication System enabled.

Server information is returned to the table.

Note

If no server information displays, either there are no servers configured for singlesign-on, or TCCS is not configured properly. Ensure that TCCS starts and then confirmyour configuration through the Teamcenter Environment Manager (TEM).

3. Specify an environment description for the URL you specified.

Note

At least one Teamcenter environment must be defined with a correspondingenvironment description.

4. In the Teamcenter Security Services (SSO) section of the dialog box, select the Enable check box.




The Teamcenter environment URL you specified is added to the list and is displayed in greenfor easy identification.

Note

Only one Teamcenter environment URL that is single sign-on enabled can be active at atime. Choose the URL from the list and select Activate to make an environment active.

5. (Optional) Use Move Up or Move Down to rearrange the order of display of the registeredenvironments in the Current Teamcenter Environment Selection list.



Chapter 3: Installing Solid Edge with the TeamcenterIntegration for Solid Edge (SEEC)

Once you have met the system and software requirements, and have your Teamcenter environmentprepared, you can choose to install Solid Edge with the Teamcenter integration (SEEC) interactivelyor silently. Review the prerequisites and checklist before starting either method of installation.

Preparing for installationReview the information in this chapter before installing Solid Edge for use with the TeamcenterIntegration for Solid Edge (SEEC).

Prerequisites

The prerequisites for installing Solid Edge with the Teamcenter Integration for Solid Edge (SEEC)include:

□ Teamcenter is installed and configured.

□ The Teamcenter rich client, 2-tier or 4-tier, is installed on your computer.

The Teamcenter rich client delivers and configures FMS. Installation of the Teamcenter rich clientmust be complete before attempting to run Solid Edge with the Teamcenter Integration (SEEC).

Note

Prior to Teamcenter 10.1, Teamcenter included Java as part of the installationpackage. Java is no longer provided with Teamcenter and you must install Java onyour computer (from http://java.com).

□ Your license file includes the Teamcenter Integration for Solid Edge (SEEC).

□ You are logged in to an account belonging to the Windows Administrator group.

Installation instructions for Teamcenter can be found on the Support Center website athttp://support.industrysoftware.automation.siemens.com/html/documentation.shtml. A WebKey isrequired to access the website.

Installation checklist

Review this checklist before starting your installation:

□ If you have an existing installation of the Teamcenter Integration for Solid Edge (SEEC), ensurethat your documents have been checked in and the cache has been reset.


http://support.industrysoftware.automation.siemens.com/html/documentation.shtml

Chapter 3: Installing Solid Edge with the Teamcenter Integration for Solid Edge (SEEC)

□ All Solid Edge and Teamcenter sessions are closed.

□ Previous versions of Solid Edge Embedded Client are removed before beginning the SolidEdge 2020 installation.

□ Teamcenter is installed and configured.

□ A Teamcenter rich client is installed to support the activities of an Author. The rich clientinstallation delivers and configures the Teamcenter FMS client.

□ Teamcenter Client Communication System (TCCS) is enabled and configured.

□ If you are using Solid Edge Standard Parts with Teamcenter, you have configured theSEEC_StandardParts_SAC preference with the location of your Standard Parts configurationfile (example: \\myteamcenter\Siemens PLM\Solid Edge Standard Parts\SMAPINIfile.sac).

Note

Solid Edge Standard Parts installations must be maintained and managed with onlyone Teamcenter database.

□ For Teamcenter Rapid Start users, you have validated your server configurationusing your Teamcenter web client. You can test your Teamcenter URL by typinghttp://myteamcenter.siemens.com:8080/tc/webclient where you substitute your server namefor myteamcenter.siemens.com.



Installing Solid Edge with the Teamcenter Integration for Solid Edge (SEEC)

Interactive installationTo interactively install Solid Edge for use with the Teamcenter Integration for Solid Edge (SEEC):

1. Exit all Solid Edge and Teamcenter sessions.

2. Remove any existing Solid Edge installation.

From your operating system's Control Panel, select Uninstall a Program. Then select SiemensSolid Edge 2020, and click Remove.

3. Access Solid Edge online download athttps://download.industrysoftware.automation.siemens.com.

Note

To access the download, you must have a WebKey account username and password.If you do not have a WebKey account, instructions for creating the account can befound at https://plmapps.industrysoftware.automation.siemens.com/webkey.

4. Follow the Solid Edge InstallShield Wizard prompts to:

• Accept the terms in the license agreement.

• Define installation settings.

Selecting the modeling standard determines the default templates used to create newdocuments. Specifying a license file and options file at this point is optional.

5. Click Install.

All product data management (PDM) clients are installed with Solid Edge. Access is basedon your license.

6. Click Finish.

7. To deliver Start menu entries, on your desktop click Start→ Siemens Solid Edge 2020→ChoosePDM Integration and select the Home tab. Then click SEEC and Apply .

Tip

• You can use the Choose PDM Integration dialog box to change active PDMclients at any time, provided you are licensed for the additional client. However,only one PDM client is active at a time.

• Appendix C contains command line options for running the PDM Integration tool.

8. (Optional) If you did not specify a license file earlier in the process, you can run the Solid EdgeLicense Utility by choosing Start→ Siemens Solid Edge 2020→License Utility and then specifyyour license option.



https://download.industrysoftware.automation.siemens.com

https://plmapps.industrysoftware.automation.siemens.com/webkey


Silent installationThe following example contains information for silently installing Solid Edge for use with theTeamcenter Integration for Solid Edge (SEEC). All arguments containing spaces should be enclosedin double quotation marks.

Note

Keyshot is not installed as part of the silent installation of Solid Edge. Install Keyshotbefore installing Solid Edge. Additional information regarding Solid Edge installation isavailable in the Solid Edge Readme.htm file.

C:\>msiexec /i”<DVD>\Solid Edge\Siemens Solid Edge 2020.msi"MYTEMPLATE=3USERFILESPEC="C:\workdir\selicense\SELicense.lic"INSTALLDIR=”C:\Program Files\Siemens\Solid Edge 2020”SETPDMCLIENT=2ADDPDMCLIENTMENUS=2USERFILESPECXML="C:\workdir\options\Options.xml"/qn+ /l*v "C:\temp\mysilentsetup.log"

<DVD> Drive letter of your DVD or location of the fully qualified path to the SolidEdge MSI file.

MYTEMPLATE

Determines the templates installed with Solid Edge. If no value isspecified, Solid Edge uses the setting from the Standard.ini file which bydefault uses Auto. For Auto, the templates are set based on the currentuser's Region and Language Format setting.

1=Metric

2=JIS Metric

3=ISO Metric

4=ANSI Inch

5=DIN Metric

6=UNI Metric

7=ESKD Metric

8=GB Metric

9=ANSI MetricUSERFILESPEC (Optional) Defines the location of the Solid Edge license file.

INSTALLDIR Installation location for Solid Edge 2020 and PDM client. The pathshould be enclosed by quotes.

SETPDMCLIENT

Defines the PDM client installed with Solid Edge.

1=Solid Edge data management

2=Teamcenter Integration for Solid Edge (SEEC)




ADDPDMCLIENTMENUS

Defines the PDM client menus installed with Solid Edge.

1=All

2=Teamcenter Integration for Solid Edge (SEEC)

USERFILESPECXML (Optional) Defines the fully qualified path and file name of the SE Adminfile.

TRANSFORMS

(Optional) Determines the language used for program group namesdisplayed in the Solid Edge Windows Start menu. The argument mustuse the fully qualified path to the .mst file. If no value is specified,English is used.

2052.mst = Chinese-Simplified

1028.mst = Chinese-Traditional

1029.mst = Czech

1031.mst = German

1033.mst = English

1034.mst = Spanish

1036.mst = French

1038.mst = Hungarian

1040.mst = Italian

1041.mst = Japanese

1042.mst = Korean

1045.mst = Polish

1046.mst = Portuguese-Brazil

1049.mst = RussianINSTALLENGLISH Yes = Instructs setup to install SE English on a non-English operating

system. This option is case-sensitive.

/qn+ Instructs the Windows installer to provide no user interface and alertat the completion of setup.

/l*v Creates a log file at the location specified. The path should be enclosedby quotes.

For additional information on options for the msiexec command, at a command prompt, type:C:>msiexec.

Verifying your installationOnce Solid Edge is successfully installed, you are ready to use the Teamcenter Integration for SolidEdge (SEEC) to manage your documents in a 4-tier implementation. If a 2–tier configuration isrequired, refer to the Configuring Solid Edge Embedded Client for a 2–Tier Deployment section ofthis document.




You can verify your installation of Solid Edge with the Teamcenter Integration for Solid Edge (SEEC)by starting Solid Edge and looking at the application title.

1. On the Start menu, choose Siemens Solid Edge 2020→Solid Edge 2020.

2. Notice the window title bar indicates Solid Edge 2020 – Teamcenter.

The Teamcenter Integration for Solid Edge (SEEC) is enabled and you are working in a managedenvironment.

Note

If your window title bar indicates Solid Edge 2020, you are not working in aTeamcenter-managed environment.

3. In the Application menu, click Open and sign in to Teamcenter.

With a successful login, the Open File dialog box is displayed showing the contents of yourTeamcenter Home folder.



Chapter 4: Configuring the Teamcenter-managed environment

When you work with Solid Edge documents managed by Teamcenter, you have many options forconfiguring the environment, including:

• Defining Teamcenter preferences.

• Limiting item types for each Solid Edge dataset type.

• Defining default Item types.

• Configuring a 2-tier architecture.

• Enabling image file generation.

• Defining site-level separator options.

• Using display names.

• Using multifield keys.

Defining Teamcenter preferencesPreferences are environment variables stored in Teamcenter and used to control thebehavior of the Teamcenter Integration for Solid Edge (SEEC). Preferences are read from theSEEC_preferences.xml file when you work in Solid Edge.

You can view the values for your Teamcenter preferences in Solid Edge by selectingSettings→Options→Manage→General tab→Preferences. You can view and modify preferencedefinitions in Teamcenter rich client after you sign in by choosing Edit→Options and then clickingSearch.

Appendix D lists the Teamcenter preferences that impact the Teamcenter Integration for Solid Edge.



Define a preference

1. In the Teamcenter rich client, choose Edit→Options→Search.

2. Click New.

3. Type the name of the preference in the Name input box.

4. Set the scope to Site.

5. Set Multiple Values to False.

6. Define the value for the preference.

7. Click Create.

Property mapping definitions

The Teamcenter preferences used to identify specific property mapping definitions where the scopeequals the site are:

Teamcenter preferenceSolid EdgeCustomproperty name

Value or default Notes

SEEC_Default_Item_TypeUsed on commonproperty dialogboxes

Item Default Item Typefor Solid Edge

SEEC_Property_Item_Type Item Type Teamcenter ItemType

Localizedproperty.Example: English

SEEC_Property_UOM Unit of Measure None

Value is basedon what youdefine in AttributeMapping. SolidEdge displays alocalized string.

SEEC_Property_DatasetName Dataset Name Dataset Name

English value.Solid Edgedisplays alocalized string.

SEEC_Property_Dataset_Description DatasetDescription

TC EngineeringDescription

Localizedproperty.Example: English

Define the list of available Item TypesDefine the following Teamcenter preferences to limit the list of available Item Types displayed on thecommon property dialog boxes to only those you want to display for that dataset type.



Configuring the Teamcenter-managed environment

Note

The default value for each preference is Undefined which provides Item as the only ItemType displayed.

• SEEC_ItemTypeList_SE Part• SEEC_ItemTypeList_SE Assembly• SEEC_ItemTypeList_SE Draft• SEEC_ItemTypeList_SE SheetMetal• SEEC_ItemTypeList_SE Weldment• SEEC_ItemTypeList_SE Component• SEEC_ItemTypeList_SE Connection• SEEC_ItemTypeList_DirectModel• SEEC_ItemTypeList_Image• SEEC_ItemTypeList_MSExcel• SEEC_ItemTypeList_MSExcelX• SEEC_ItemTypeList_MSWord• SEEC_ItemTypeList_MSWordX• SEEC_ItemTypeList_PDF• SEEC_ItemTypeList_StructureEditor• SEEC_ItemTypeList_UGMASTER

For each preference, use the following instructions to limit the list of Item Types for each Solid Edgedataset type.

1. Start the Teamcenter rich client and log in with database administrator privileges.

2. Choose Edit→Options→Search.

There are several preferences related to the list of available Item Types. The easiest way tolocate them is by searching using the keyword SEEC_ItemTypeList.

3. In the Search by Keywords box, type SEEC_ItemTypeList.

Each of the preferences has a default value of Undefined which provides only Item as anavailable Item type.

4. For each SEEC_ItemTypeList preference, edit the preference value to include only the ItemTypes you want to display for that dataset type.

For example, select SEEC_ItemTypeList_SE Part to define the Item Types you want available inthe Solid Edge Part environment. Some examples of Item Types are Item, Design, Document,and Drawing.

Caution

Item Type definition is case sensitive.

5. Click Save to save the edited values.

6. Click Close to exit the Options dialog box.




Refer to the Teamcenter Preferences section of this document for additional information on eachpreference.

Define default Item typesYou can define the default Item type for a Solid Edge document type by editing the value of theSEEC_Default_Item_Type preference. Some examples of most commonly used Item types are:Item, Design, Document, and Drawing.

For a full description of the preference, see the Teamcenter Preferences section of this guide.

1. Start the Teamcenter rich client and log in with database administrator privileges.

2. Choose Edit→Options→Search.

3. In the Search On Keywords box, type SEEC_Default_Item_Type, and then select it from the list.

The preference has a default value of:

Item

Item

The preference must contain a value. If only the first row exists, it defines the default Item type forall document types used in Solid Edge (3D Solid Edge documents, Solid Edge Draft, and linkednon-Solid Edge document types such as Word, Excel and images).

If the first and second rows exist, the value specified on the first row defines the default Item typefor 3D Solid Edge documents and non-Solid Edge documents. The value specified on the secondrow defines the default Item type for draft documents.

If Item is used after the first two rows, it is ignored.

4. For a Solid Edge document type, edit the SEEC_Default_Item_Type preference and specifyexceptions to the default value by setting the Solid Edge document type equal to the real Itemtype name as seen in BMIDE.

Example

Item

Item

asm=Design

par=custom_item_type1

psm=custom_item_type2

pwd=Item

If all document types are explicitly defined, the first row defines non-Solid Edge documents, andthe second row is ignored. If an Item type is defined more than once, only the first occurrence isused. Item type definition is case sensitive.




Note

The Item type you specify must exist in the preference, SEEC_ItemTypeList_ for thatdocument type. In this example, SEEC_ItemTypeList_SE Assembly must containDesign.

5. To save the edited values, click Save.

6. Close the Options dialog box.

7. Restart Solid Edge to reread the preference values.

Note

When you import unmanaged documents to Teamcenter using Add to Teamcenter, and thedocument you are importing has an Item type that is defined with a custom property, thevalue of the custom property is used during import.

2-Tier and 4-Tier configurationsThe Teamcenter Integration for Solid Edge (SEEC) implements Teamcenter's Service-OrientedArchitecture (SOA) and File Management System (FMS). This implementation can be used withTeamcenter's 4-Tier deployment, combining the resource tier, enterprise tier, and web tier with a clienttier, or it can be configured to be used with a Teamcenter 2-Tier deployment where Teamcenterexecutes on the user’s workstation with the client application.

Note

Setup delivers Solid Edge with the Teamcenter Integration as a 4-tier configuration.

Installation of Solid Edge with the Teamcenter Integration requires you to enter a 4-tier Teamcenterdefinition. In a 4-Tier deployment, only the client application executes on the user's workstation; theEnterprise tier, database, volume, and other resource tier components are executed on the serverproviding improved performance for customers working in a high-latency WAN environment. ThenSolid Edge Teamcenter Client only requires Teamcenter FMS, which is installed on the workstation bya 2-tier or a 4-tier Teamcenter rich client installation.

If a high-latency WAN is not a factor, but rather a larger number of users, you should use a 2-tierconfiguration. In a 2-tier configuration, Teamcenter executes on the user’s workstation with theclient application, and provides separation between Solid Edge, the Teamcenter Client and theTeamcenter server processes. This provides the maximum in available memory for the TeamcenterClient application. This configuration adds scalability because each client workstation is responsiblefor the Teamcenter server process and this process communicates with the Resource tier.

If a Solid Edge Teamcenter Client 2-tier deployment is required, the client should be configured aftersetup completes using the Define Teamcenter Environments application.




Prerequisites for 2-Tier configuration

In preparation for configuring a 2-tier environment:

• Install a Teamcenter 2-tier rich client. This installation delivers the required Teamcenterapplication support for a SEEC 2-tier deployment and it delivers and configures FMS.

• Apply all Teamcenter patches to the workstation to meet the minimum Teamcenter applicationrequirements.

As future patches are applied to the server, they must be deployed to all 2-tier Teamcenter clients.

• Verify your rich client installation: My Navigator, FMS, and Portal Visualization.

Note

You cannot deliver a Teamcenter 4-tier rich client client for a SEEC 2-tier deployment.

Configuring Solid Edge Embedded Client as a 2-tier client

1. Add a 2-tier connection using the Define Teamcenter Environments application.

□ Select Start→Siemens Solid Edge 2020→Choose PDM Integration→Define TeamcenterEnvironments.

2. Select the 2-Tier check box under Teamcenter Environments URL and enter a databasedescription.

□ Click Add.

The Define Teamcenter 2-Tier Server dialog box is displayed.

3. Enter the location of your Teamcenter 2-tier rich client Application folder (TC_ROOT).

□ Enter the location of your Teamcenter data folder (TC_DATA).

□ Click OK.

A new row is added to the table.

Note

You are limited to one 2-tier database definition.

□ Click OK to save the changes.

When you are prompted to log on to Teamcenter, select the 2-tier connection from the databaselist box.




Note

Solid Edge Embedded Client can run as either a 4-tier or 2-tier client. However, thecache is on the selected Teamcenter environment URL. Therefore, a 4-tier connectiondoes not use the same physical cache as a 2-tier connection for the same Teamcenterenvironment and user id.

Sizing 4–Tier Teamcenter deploymentWhile using Solid Edge Embedded Client as a 4-tier application, you must configure the Teamcentermiddle tier with enough Teamcenter Business Logic Server processes to handle the incomingrequests. You cannot arbitrarily set these numbers, as this will adversely impact reliability andperformance. If the specified numbers are set too low, you will see reliability issues with Solid Edgeoperations that interact with Teamcenter, such Open and Save. If the numbers are set too high, thenperformance is impacted. The following information is provided to help educate and guide you inconfiguring your server processes.

Teamcenter

In Teamcenter, the Server Manager configuration is managed in the%TC_ROOT%\pool_manager\confs\<config directory>\serverPool*.properties file. Thefile entries in which you are most interested are PROCESS_MAX, PROCESS_WARM, andPROCESS_TARGET.

• PROCESS_MAX – Specifies the maximum number of Teamcenter Business Logic Serverprocesses allowed to run in the pool. The total number of servers will never exceed this number.

Example

PROCESS_MAX=30

In this example, the total number of servers will never exceed 30.

Caution

The value for PROCESS_MAX should always be larger than the value forPROCESS_TARGET and PROCESS_WARM.

• PROCESS_WARM – Specifies the minimum number of Business Logic Server processes in thepool that are started, but not logged into. The server manager always tries to maintain thisminimum number of servers ready (warm). The Server Manager may time out servers in use, inorder to ensure that there are at least the required number of minimum warm servers at all times.

Example

PROCESS_WARM=1




This ensures that one server is always ready (warm), in addition to those being used.

• PROCESS_TARGET– Specifies the target number of server processes to be available in this poolduring specified times. Specify these values as time and integer pairs separated by commas.

Example

PROCESS_TARGET=0700 3, 1700 2

This value sets the target number of server processes as 3 between 7:00 a.m. and 5:00 p.m.and as 2 between 5:00 p.m. and 7:00 a.m.

If the number of server processes is below the specified target, then warm servers are added toreach this number. In this case, the number of warm servers exceeds the minimum, so none areadded. If the number of server processes exceeds the specified target, only the minimum numberof warm servers is maintained and servers are terminated as they time out.

If you expect 10 concurrent users, you would want to configure to keep 10 servers running and 1ready (warm) at all times.

Example

PROCESS_WARM=1PROCESS_TARGET=0000 11

Depending on the server load and activity, these values should be modified. However, this must beconsidered with respect to the amount of physical memory and the other work this server is expectedto perform. You should also consider the following:

• Number of concurrent Teamcenter logins from all 4-tier enabled clients (SEEC, rich client,WebClient, etc.)

• If you are in the data migration phase of the project, more servers may be needed.

Teamcenter Rapid Start

In Teamcenter Rapid Start, the Server Manager configuration can be managed via a web page,for example, http://myteamcenter.ugs.com:8080/tc/admin, where you would substitute your serverin the URL.

After a successful login, the Global Configuration page is displayed. Select the Server Manager poolin the Server Manager Instances section. (State should be running.) The Pool Configuration isdisplayed and can be updated using Edit. The Process Target is the parameter of interest.

Note

Consult Teamcenter documentation for additional details and information regarding otherparameters.




Enabling image file generationImage files are representations of Solid Edge models that can be easily distributed on the internet ase-mail attachments, or used to enable quick rendering in the rich client application.

Part, Sheet Metal, and Draft

The Teamcenter Preference SEEC_Image_Generate_3D enables image file generation for viewing3D model types (part, sheet metal, and weldment). Preference settings are either always on oralways off. JT is the default file format for 3D data, and it is saved to the item when you save the partin Solid Edge. For more information, see Teamcenter Preferences.

Note

This does not include PMI.

2D draft files

You can generate image files when saving draft files to Teamcenter using the Save As command.You can use the Save As Image command to save 2D images in the following formats:

• None

• Enhanced Metafile (*.emf)

• JPEG (*.jpg)

• TIFF Image (*.tif)

• Windows Bitmap (*.bmp)

• DXF (*.dxf)

The Teamcenter Preferences SEEC_Image_Generate_Draft andSEEC_Image_Generate_PDF_for_Draft enable 2D draft image file generation. The image is savedin the draft dataset. The .pdf is saved into a separate dataset.

Tip

The Enhanced Metafile (*.emf) format provides the best data fidelity for viewing purposes.

Assemblies

You can generate image files when saving assembly files to Teamcenter using the Save As command.You can use the Save As Image command to save assembly images in the JPEG (*.jpg) format.

The Teamcenter Preference SEEC_Image_Generate_Assembly creates an image file using theoptions you define, and checks it in to Teamcenter as part of the assembly dataset reference. Theoptions for the preference are:




Option Description ValueThe first line of the preferencedefinition determines if the imageis created. When set to True, theimage is created.

/Create=True

/Create=False

SizeWidth

Defines the width of the image.The default of 1024 pixels isused when /Units=1.

Note

The /Units optiondetermines the unit ofmeasure used.

/SizeWidth=1024

/SizeWidth=10.24

/SizeWidth=4.0315

SizeHeight

Defines the height of the image.The default of 768 pixels is usedif the /Units=1.

Note

The /Units optiondetermines the unit ofmeasure used.

/SizeHeight=768

/SizeHeight=7.68

/SizeHeight=3.02362

RevisionRuleShow

Adds a watermark (PMI) to theimage to indicate the revisionrule and variant rule used toopen the assembly.

/RevisionRuleShow=True

DisplayConfigShow

Adds a watermark (PMI) to theimage to indicate the displayconfiguration active at the timethe image was created.

/DisplayConfigShow=True

Autofit

Fits the view before savingand uploading the file intoTeamcenter. The default is falseif the line is not set.

/Autofit=True

/Autofit=False

ImageQuality

Specifies the quality settingapplied to the .jpg files.

1=medium image quality

2=high image quality

Medium image quality is thedefault if not specified.

/ImageQuality=1

/ImageQuality=2




Option Description Value

WaterMarkOrigin

Defines the corner of thewatermark to use as the origin.Default is bottom left.

1=bottom left

2=bottom right

Note

The watermark iscontrolled using theRevisionRuleShow orDisplayConfigShowoptions.

/WaterMarkOrigin=1

/WaterMarkOrigin=2

Defining site-level separator optionsSolid Edge Embedded Client supports the definition of separator options at the Teamcenter site level.Separators are used between the Item ID and Item Revision as well as between the Item ID, ItemRevision, and the Item Name in many of the common property dialog boxes you see when you workin a managed environment.

The values for Teamcenter preferences FLColumnCatIVFSeparatorPref andFLColumnCatObjSeparatorPref are read at startup. Any changes you specify are not recognizeduntil after you start a new application session. The preferences only apply to combined informationobtained from Teamcenter. The preferences are not used to modify the Document Name Formula.Some examples of where you can see the implementation of separator options is in the Identifiercolumn on the Open File dialog box and anywhere the Dataset Name is displayed.

Note

If the separator options are not defined at the site level or are blank in Teamcenter, thesystem default of “/” and “-” are used.

Add a site-level separator

1. In the rich client, choose Edit→Options.

2. From the list of General items, click Item.

3. On the General page, type a separator to divide the Item and ItemRevision.

4. From the list of General options, click Item Revision.




5. Define the separator to use between the Item/Item Revision and name and the Item/ItemRevision and sequence id.

Using display namesWhen Solid Edge transacts data with Teamcenter, it uses an object’s name that is unaffected bylocalization. This is referred to as the real name. The real name is also used for the display of theobject’s name in the user interface: for example, Color. However, the BMIDE templates require aunique prefix for each name. The prefix is added to all new business objects to guarantee uniqueness:for example, SE99_Color. The resulting name is often not desirable for display in the user interface.

Support for the use of a display name addresses this issue and brings consistency in what you see inSolid Edge when compared to Teamcenter rich client. Consider the example:

Real Name Real ValueSE99_ColorDisplay name (Base)ColorDisplay name (Localized)Farbe

Red

What is transacted with Teamcenter continues to be the real name, however, what you see in theuser interface is the displayable (display) name. Therefore, a value has a real name and can havemultiple display names.

You can control whether you view real or display names in the Solid Edge user interface. TheTeamcenter preference, TC_display_real_prop_names, determines which is used. The preferenceis delivered by Teamcenter and controlled in the rich client’s Options dialog box.

There is no change to the process an administrator uses to define the property mappings betweenTeamcenter and Solid Edge. Mandatory properties such as Item Type, Item ID, Revision, DatasetName, Dataset Description, Project ID, and Folder continue to be managed by Solid Edge. Metamodel and mapped attributes use the displayable name returned by Teamcenter.

An additional read-only row is displayed in common property dialog boxes that lists the displayableproperty name of mapped properties.

• The column headers show Solid Edge property names.

• The first row is a read-only row showing the display name.

• The second row provides a description.

• The third row displays details for range and interdependent lists of values.




Using the information presented in the common property dialog boxes, you can learn what Solid Edgeproperty name is used and what Teamcenter property it is mapped to.

The preference, SEEC_Item_Type_DisplayableName determines whether the real name ordisplayable name is written to Solid Edge for Item Types. By default, it is set to 0 to use the real name.

Caution

If you set the SEEC_Item_Type_DisplayableName preference to 1 to write the displayableItem Type name to the custom properties value, opening legacy documents in Solid Edgeresults in the Item Type property being out-of-date and the displayable property name iswritten into the custom property. This impacts the time it takes to open an assembly ordraft. Additionally, if this property is used in an annotation, it is also out-of-date.

Other things to be aware of:

• The column headers on common property dialog boxes and the property information on theOpen dialog box remain the same for all mandatory properties. Column headers for mandatoryproperties are based on the localized version of Solid Edge.

• There are no changes to the column order of common property dialog boxes. Mandatoryproperties are followed by meta model properties, and then mapped properties which aredisplayed in alphabetical order.

• Add to Teamcenter supports Item Type display names as input.

• The Teamcenter rich client presents both the Property Display Name and the Property DisplayValue. With system administrator privileges, you can configure the rich client to display realnames by changing your options in the general folder. Once the option is set, you can log on tothe rich client and see real property names.




Using multifield keys in the Teamcenter managed environmentIn Teamcenter, the Item ID uniquely identifies an Item. Beginning with Teamcenter 10, the propertyused to make an Item business object unique can be extended to include more than just the Item ID(for example, Item ID and Type). When this new Teamcenter functionality is deployed, Solid Edge isable to reuse the Item ID for instances of different Item business objects (including Item, Design,Drawing, and Document). This functionality enables you to create multiple related items using thesame Item ID, for example, when you want to refer to a design and drawing using the same Item ID.

Prior to Teamcenter 10, this was not possible because both design and drawing types are children ofthe Item type and are both considered items. Now, using the Business Modeler IDE in Teamcenter,you can create multifield key definitions per domain or object type.

Multifield keys define what makes an object unique in the database. The default multifield keydefinition for Item business objects is:

Item{item_id}

The value of the item_id property is the object’s unique ID.

In the case of design and drawing, you can define the unique key for design business objects and theirchildren as Design{item_id} and for drawing business objects and their children as Drawing{item_id}.When these definitions are applied, it results in a unique key identifier for each instance of an objecttype in the database, even though the different object types can share the same Item ID. You canalso create a unique key by adding a property in addition to the item_id property, such as object_type.For example, Design{item_id,object_type}.

You create a business object’s unique key definition using the MultiFieldKey business object constantin Teamcenter. A list of properties available for each business object type is provided in the AvailableProperties dialog box when you create a multifield key. For more information about creating multifieldkey definitions, refer to the Configuring business object identifiers with multifield keys portion ofthe Teamcenter Business Modeler IDE Guide.

Multifield key domains

The multifield key is composed of a domain name (the name of the business object type) and acombination of one or more of the business object’s properties:

domain{properties}

For example, in the Design{item_id} key, Design is the domain.

All business object types with the same multifield definition constitute a domain. Because childrenbusiness object types (design, drawing) inherit the key definition from their parent (Item), they belongto the same domain as the parent business object unless a different multifield key definition is createdfor a child type. Custom business objects also inherit the key from their parents.

For more information about multifield key domains, refer to the Multifield key domains portion ofthe Teamcenter Business Modeler IDE Guide.

Multifield keys in Solid Edge

Prior to Teamcenter 10, only the Item ID could be used to uniquely identify an item. By using multifieldkey definitions, instances of different Item business object types (such as items, designs, drawings,documents, and specifications) can use the same item ID. When these definitions are applied, it




results in a unique key for each instance of an object type in the database, even though the differentobject types can use the same item ID.

Redefining what makes an object unique in Teamcenter impacts what is required to create an objectthough Solid Edge Embedded Client. Properties that comprise the multifield key are identified in

common property dialog boxes such as the New Document dialog box with a gold asterisk . Thegold asterisk indicates the property (cell) is an input to the multifield key and the property is required.

When using multifield keys, your experience with Solid Edge can change from the default in thefollowing ways:

• Common property dialog boxes such as the New Document dialog box may require additional

property definition (as indicated by the gold asterisk ).

• The Filename is now the Item ID with a unique system-generated number appended to it.

<item ID>-<unique number>.extension

• Searches based on the item ID can now return more than one result. If you search for an item IDthat is used by multiple objects, the Search dialog box displays more than one result so that youcan choose the desired object from the list of all objects with the same item ID.

Tip

As a best practice, do not map the keys that make an object unique when you use themapped properties functionality in Solid Edge Embedded Client.



Part II: Working with Teamcenter-managed documents

Solid Edge documents store project designs, and most often complete projects are comprised ofmany Solid Edge documents. The relationships that exist among these documents must be trackedand maintained. Because project designs change over time, document versions must also betracked and controlled. A well-controlled system provides easy access for those with permissionsfor reviewing, printing, editing, and approving documents, and protects documents from access bythose without proper authority.

This section includes information about:

• Working with managed documents

• Multi-CAD in the Teamcenter-managed environment

• Attribute mapping

• Preparing unmanaged documents for Teamcenter

• Using the Data Preparation Utility

• Add to Teamcenter-Interactive


Chapter 5: Working with managed documents

Understanding Teamcenter termsTeamcenter uses objects to store information that describes each Solid Edge document, in addition tostoring the document or file itself. An Item is a commonly used workspace object that captures themetadata describing all the associated revisions. An Item Revision captures the revision-specificmetadata. A Dataset captures the document specific metadata and it holds the physical document(s).Datasets can capture unique document types such as .asm, .doc, and .pdf.

It is metadata that is useful in data retrieval and reuse. The Item, Item Revision and Dataset combineto fully describe the associated document.

Note

Datasets have the ability to capture versions of a document.

If you want to think of these objects in terms of hierarchy, from top to bottom, it would be Item,Item Revision, Dataset. You can view this hierarchy from the Teamcenter client. Each object isrepresented by a unique image, and as you expand each level, you can see the structure. Once youreach the Item Revision, you may see more than one Dataset. When your business process requiresthe Solid Edge draft file to have the same Document Number as its 3D part (.par), assembly (.asm),sheet metal (.psm) or weldment (.pwd) file, you may have a draft (.dft) file with the correspondingnumber under the Item Revision. This practice impacts how a company manages Revisions.

Each object must have a unique identifier (ID). For Items, this is called an Item ID. In the followingexample, the Item ID for the Item (A) is 000130. The Item Revision (B) for this item is A, which adds aunique Revision designation, followed by the Dataset (C) and its Item Name.

Note

The use of multifield keys (MFK) can change the unique identifier from Item ID to acombination of fields. To learn more about multifield keys, see Using multifield keys in theTeamcenter-managed environment.



The attributes that describe these objects are often the same, but when applied to the Item, ItemRevision or Dataset, they provide uniqueness. For example, since the Name attribute is used bythese three objects, to get a specific piece of information you can specify the Item ID, Item Revision,and Item Name. These three properties are considered the mandatory properties that must bedefined for each managed document.

Connecting to TeamcenterWhen you work with Teamcenter-managed data, you use the same commands that you normallywould in Solid Edge. When Teamcenter is enabled in the Applications menu, Solid Edge automaticallyadjusts the user interface as needed to provide you access to Teamcenter functions.

This normally changes the user interface in the following ways:

• When browsing for Solid Edge files you are presented with the data from Teamcenter. Youwill see a similar presentation in the Teamcenter Parts Library tab and in most other placeswhere you need to access data. If you want to change the behavior so that you are no longeraccessing Teamcenter, but accessing the local file system instead, you must close all Solid Edgedocuments. You can then deselect Teamcenter.

• When new documents are created you are prompted to upload them to Teamcenter. This isaccomplished through a variety of common properties dialog boxes, such as the New Documentor Upload dialog boxes.

• When you save files, they are only saved locally to your cache. But when you close thedocument, it is checked into Teamcenter.

Understanding the CacheTo optimize performance, documents from Teamcenter are downloaded once to the local machinewhen accessed and then only downloaded again if they are out-of-date. The local download area iscalled a cache. The cache is a folder in the Windows file system where a copy of each file is kept.The cache location is predefined as %APPDATA%\Siemens\Solid Edge\SEEC.

Note

The location of the cache should be on the physical disk of the local machine. This is apersonal cache and must not be shared with other users.

The Cache Assistant, located on the Manage menu, provides many functions for managing thecache. In most instances you do not need to use this command. However, if you need to update orchange the cache in some way, make sure you use Cache Assistant and do not attempt to modifythe cache by manually changing data in the Windows folder on disk.



Working with managed documents

Using the Structure ManagerFormerly known as Product Structure Editor (PSE), the Structure Manager is delivered withTeamcenter and used to view and change BOM structure. For example, when a Solid Edge assemblyis saved to Teamcenter, the assembly occurrence structure is written to Teamcenter and viewed withStructure Manager. You can use revision rules and variant rules to control the configuration of theinformation displayed in the editor. Additionally, Solid Edge users can configure a product structure inStructure Manager, and sent it to Solid Edge. The fully qualified product structure can be used bySolid Edge to construct the product design. This feature includes support for basic and advancedproduct structure configuration.

For detailed information about Structure Manager, see the Structure Manager Guide in theTeamcenter help Collection.

Before creating or modifying product structure, you should also read Getting Started with ProductStructure, which describes the basic concepts behind product structure and includes advancedinformation on how to use and administer it.

Managing document releasesTeamcenter has a number of tools designed to enable administrators and users to work together tomanage document releases.

Administrative tools allow the administrator to design workflow process templates that definepractices and procedures that meet their business needs. End users use these templates to takedocuments through the release cycle.

This chapter shows a few examples of the many workflow tools Teamcenter offers. For moreinformation, see Teamcenter documentation.

Changing the workflow of a document in Teamcenter Rapid Start

The following example describes the steps used to change the workflow of a document in TeamcenterRapid Start.

1. While working in Teamcenter Rapid Start, click an Item Revision.

2. Choose File→New →Workflow Process.

The New Process dialog box is displayed, which provides options for changing the workflowfor an Item Revision.




3. In the New Process dialog box, select Status Change from the Process Template list.

Tip

You can click the Process Templates tab to display a list of statuses. This exampleuses Status Change, which provides a single-step release process.

4. In the New Process dialog box, click OK.

A Tasks to Perform entry is added to the Inboxes page.




5. In the Signoff Team pane, from the Profiles list, select the appropriate role needed to makethe change.

In this example, the profile is */Checker/1. The “1” indicates that there is one user needed in the“Checker” role.

Click the Plus button to assign a user to the role.

6. Click Apply to change the status and move the Item Revision to the next state, which is shownin this example.




The Signoff Decision dialog box is displayed.

7. In the Decision column, click No Decision.

This displays the Signoff Decision dialog box, which enables you make a decision on the statuschange and includes comments about the change.

8. In the Signoff Decision dialog box, select a Decision, type any comments, and then click OK.

The status value is added adjacent to the Item Revision in the tree structure.




Viewing the process in the Workflow Viewer

The Workflow Viewer creates a graphical view of the status of an Item Revision within the workflow.You can track the progress of an Item Revision and determine the other users involved in therelease process.

To view the process:

1. Right-click the Item Revision.

2. On the shortcut menu, choose Send To→ Workflow Viewer. The Item Revision is displayed inthe Workflow Viewer.

For more information on managing document releases, see the Workflow section of the Teamcenterhelp Collection.




Viewing the document status in Solid Edge

Changes made in Teamcenter to the status of a document are displayed when you open thedocument in Solid Edge.

Status is displayed in the Release Status column of the Open File dialog box.




Revising documentsYou have two options for revising Teamcenter-managed documents:

• The Revisions command displays the Revisions dialog box so that you can view the revisionsof the document and specify a new revision.

• The Revise command displays the Revise Document dialog box with the next revisionautomatically presented for you.

Note

The Revisions command is also accessible from Application menu→Manage as well asthe shortcut menu.

1. In PathFinder, right-click the document.

2. On the shortcut menu, choose Manage→Revisions.

The Revisions dialog box is displayed.

3. Click New.

Notice that the new revision is calculated for you. The Revision cell contains a red asteriskdenoting it is a required attribute. You can also define the folder for the revision.

4. Click OK.

When you close the document, it is uploaded to Teamcenter.



Chapter 6: Multi-CAD in the Teamcenter managed environment

Multi-CAD in the Teamcenter managed environmentIn today's collaborative working environment, it is rare that an entire product is designed in onlyone CAD system. The term multi-CAD describes the ability for Solid Edge assemblies to includemodels in Teamcenter that were not created or owned by Solid Edge. Using the multi-CAD capability,you can manage content from multiple CAD sources and then create an integrated single designusing content from more than one CAD authoring system without a translation. Assembly structuresare resolved through Bill of Materials (BOM) or BOM View Revisions in Teamcenter. Geometry iscommunicated through DirectModel datasets, using JT, and is updated automatically providing up todate assembly structures and models.

An example of working in a multi-CAD environment is designing a vehicle in Solid Edge usingan engine designed in another CAD application where the structure is defined and managed inTeamcenter, the components are defined by JT, and Solid Edge Draft documents the product.The engine is placed in the vehicle in Solid Edge and assembled into position. The non-SolidEdge authoring system owns the content placed in the native Solid Edge design. The Teamcenterpreference, SEEC_Foreign_Datasets is used to define the foreign data source.This workflow introduces the concept of a driven reference where a document's geometry is definedby a non-Solid Edge source. The driven reference is read-only whether opened or in-place activated.The Save As command is available if you want to create a new item and then edit that contentwith Solid Edge.

Driven references go through an out-of-date check. If the foreign source changes, the change issynchronized the next time the file is opened. Driven references are uniquely identified in AssemblyPathFinder by .

Working with multi-CAD documents

Product structure is obtained from Teamcenter BOM View and configured per Revision Rule. Theconfigured structure is evaluated where the BOM lines provide position data and each uniqueitem revision is queried for geometric information (Dataset). When the Teamcenter preference formulti-CAD is enabled, Solid Edge considers geometric content in the following order:

• Native Solid Edge content

• Driven references (foreign data containing a geometric representation)

• Non–modeled content (no geometric representation exists)

Use Solid Edge Assembly commands to position the content. Use the Open command to searchfor the Solid Edge assembly and open the document, synchronize structure changes and checkout the assemblies. Use the Assemble command or the Move command to position the foreignassembly in the context of its parent. Then you can save the Solid Edge assembly to Teamcenterand create a drawing saving the drawing to the same item revision with the Solid Edge assemblyor saving the drawing to a new item.



Save driven references to Teamcenter

Since foreign data is expected to change, an ability to track if it is out-of-date and synchronizeproduct design is required. The Solid Edge option to save Solid Edge content back toTeamcenter is Save driven references to Teamcenter. The option is available in Solid EdgeOptions→Manage→General tab when a document is open in Solid Edge. The option is enabled ona per user basis. Using this option, when an assembly is saved to Teamcenter, Solid Edge createsa Solid Edge Dataset under the source Item Revision and then uploads the Solid Edge documentinto Teamcenter as a driven reference. This option also saves a Solid Edge part file as a drivenreference when the JT file is opened.

There are two things to keep in mind:

• Solid Edge Embedded Client requires the structure to configure only one item revision. There isno support for multiple revisions from the same Item.

• Solid Edge Embedded Client does not support foreign CAD assembly features.

Enabling multi-CAD in Solid Edge

Teamcenter captures JT content in a dataset called DirectModel. The relation that connects aDirectModel Dataset to an Item Revision is IMAN_Rendering. The JT file is connected with anamed reference JTPART.

To use foreign CAD data in Solid Edge, two preferences must be enabled:

• SEEC_Foreign_Datasets

• SEEC_BOM_Synchronize

The Teamcenter site preference SEEC_Foreign_Datasets determines what datasets to considerwhen a Solid Edge 3D dataset is not saved to the item revision. The preference is False (0) bydefault. Currently, Solid Edge supports DirectModel (JT) only.

Teamcenter provides the product structure or BOM view for documents created outside theSolid Edge environment. BOM synchronization is controlled by the Teamcenter preferenceSEEC_BOM_Synchronize. Enabling this preference allows Solid Edge to compare the BOM inTeamcenter with its own BOM and add or remove based on changes seen in Teamcenter. To enableBOM synchronization, set the SEEC_BOM_Synchronize preference to true.

The Teamcenter preference SEEC_BOM_Synchronize supports the following search order:

• Search for Solid Edge 3D managed content.

• If the item revision does not include Solid Edge 3D content, then search for an alternate 3Drepresentation, DirectModel (JT).

• If there is no DirectModel, then consider the item a non-modeled occurrence.

Preference syntax details are available in the Teamcenter Preferences chapter of this guide.



Multi-CAD in the Teamcenter managed environment

Tip

If your environment has the preference, SEEC_Synchronize_ItemNumbers set to true,we recommend that you create the preference PS_new_seqno_mode and set it toexisting. By default, Teamcenter assigns a new Find Number for each item added to theBOM View Revision. When the same item is added to Structure Manager multiple times,this preference will cause all entries to be packed or have the same Find Number. Notsetting this preference will cause a conflict with item numbers in Solid Edge resulting in awarning message.

Multi-CAD document workflow (SEEC)The structure of a multi-CAD document is built using the Teamcenter rich client and Teamcenter’sStructure Manager or Teamcenter Structure Editor. To add a foreign assembly or non-modeledassembly to an existing Solid Edge assembly:

• Find the foreign assembly or non-modeled assembly in the Teamcenter rich client.

• Select the item revision and copy it to the Clipboard.

• Using either Teamcenter rich client Structure Manager or Solid Edge Structure Editor, paste theitem revision into the top level assembly of an open Solid Edge assembly.

• Save the structure changes to complete the edit of the Solid Edge assembly.

• Open the Solid Edge assembly in Solid Edge.

The placement of driven references in the Solid Edge assembly is based on the TransformationMatrix in the BOM View Revision. Grounded assembly relationships are applied to the drivenreferences. The components can be positioned once the grounded relationship has beenremoved from the foreign subassembly.

Take Ownership commandThe Take Ownership command is used when the product being designed in Solid Edge usesgeometric content authored in another CAD system. Taking ownership removes the driven referencestatus from the Solid Edge document and enables the user to add geometric value. The commandcreates a new revision and Solid Edge is the CAD author of the new revision.

Note

Use of the command requires the following Teamcenter preference settings:

SEEC_BOM_Synchronize=True

SEEC_Foreign_Datasets=True

When these preferences are set, the Take Ownership command is available in:




• Application menu→Manage→Take Ownership.

• Assembly PathFinder shortcut menu.

• Read-Only Assistant when the document is determined to be driven.

The number of objects that can be selected for a single take ownership transaction is determined bythe Teamcenter preference:

SEEC_TakeOwnership_Limit

If the number of objects selected exceeds the limit defined by the preference, a message is displayedto reduce the number of objects selected and rerun the command.

The Take Ownership command uses additional Teamcenter preferences to govern how datasetsare processed. The preferences contain lists of dataset types that should not be copied to the newrevision, giving the administrator the ability to override deep copy rules. Each preference is specific tothe take ownership workflow and design reuse of geometry using multi-CAD.

• SEEC_DrivenReference_DoNotCopy_Revise

• SEEC_DrivenReference_DoNotCopy_SaveAs

If either preference is empty or all entries are in error, Teamcenter Deep Copy Rules are responsiblefor all the datasets except the ones being transacted.

Once Solid Edge has ownership of the item revision (it is no longer a driven reference), Solid Edgegenerates JT and writes it to the DirectModel dataset when the document is saved or uploadedto Teamcenter.

Caution

This command is not intended to be used as a bulk migration tool. Its focus is on foreigngeometry reuse in the context of an assembly.

Take ownership of a foreign CAD documentIn order to take ownership of non-Solid Edge CAD documents the following prerequisites must be met:

• The Teamcenter Preferences SEEC_BOM_Synchronize and SEEC_Foreign_Datasets mustbe set to True.

• The non-Solid Edge data must be added to the document structure in the Teamcenter rich client.

• BOM Synchronization must be set to Yes so that structures are synchronized.

• The direct document must be a Solid Edge assembly document.

1. Open the Solid Edge Assembly that uses the non-Solid Edge data.

2. In PathFinder, select the foreign CAD documents for taking ownership.




If you select a subassembly, you do not have to take ownership of each subassembly betweenthe component and the direct document. Solid Edge Embedded Client is capable of managingand addressing soft edits so the intermediate subassemblies stay up to date.

3. Right-click and select Manage→Take Ownership.

Status messages indicate the command is validating input and verifying business rules. If at leastone object fails validation, details are presented in the Take Ownership Validation dialog box.You must decide whether to continue with the objects that passed validation or exit the command.

4. Select continue to display the Take Ownership dialog box.

This dialog box combines the capability of the Revise command with processing multiple objectssimultaneously. Objects are displayed with property values from Teamcenter and the new revisioncell populated. The default action is to upload the documents into Teamcenter.

5. Click Perform Actions to upload the new revision of the selected documents into Teamcenter.

PathFinder indicates the new revision is checked out to you, and you can edit the document.



Chapter 7: Attribute mapping

Attribute mapping defines what Solid Edge document properties you exchange between Solid Edgeand Teamcenter. Using mapping definition files, Solid Edge attributes are stored in Teamcenter anddisplayed and modified both in Solid Edge and Teamcenter.

Each mapping definition has a title and description that is used when displaying the attribute value.There are also optional qualifiers that affect the behavior of the mapping, such as whether a defaultvalue is created for an attribute if none exists in Teamcenter. The syntax of attribute mapping iscovered later in this chapter.

There are a number of property mapping definitions that are delivered for you. The properties areshown on common property dialog boxes such as the New Document dialog box and the UploadDocument dialog box.

Solid Edgeproperty

Teamcenterattribute

Required/Optional File Property Maximum

character lengthTeamcenter ItemType Item Type Required Custom

(Localized) 32

Document Number Item ID Required Project 128Revision Number Revision Required Project 128Project Name Item Name Required Project 128Dataset Name Dataset Name Required Custom (English) 128TC EngineeringDescription Dataset Description Optional Custom

(Localized) 140

The Dataset Name is not required on common property dialog boxes. However, if no Dataset nameis specified, one will be computed from the Item ID and Revision. This system generated value issynchronized so that it updates when you choose Save As or Revise.

Existing Dataset Names are evaluated to determine if they are system generated or user defined.If the Dataset Name has only two strings on either side of the separator between the Item ID andthe Item Revision, then it is assumed to be system generated and not user defined, and it will trackwith the Item ID and Item Revision.

Attribute synchronizationSynchronization enables an attribute in one application to be updated automatically when amodification is made to the corresponding attribute in another application. The synchronization ofattributes between Solid Edge and Teamcenter occurs when a document is checked in or uploadedinto Teamcenter. A Reverse Property Synchronization (RPS) occurs when a document is downloadedfrom Teamcenter.



Unidirectional and bidirectional synchronization

Synchronization is usually thought of as being unidirectional or bidirectional. In unidirectionalsynchronization, synchronization only occurs from one application to another. For example,synchronization of physical properties such as Volume and Surface Area only occurs from the SolidEdge document to Teamcenter. A change to the property in Solid Edge is recorded in Teamcenter.

In bidirectional synchronization, synchronization occurs both from the Solid Edge file to Teamcenterand from Teamcenter to the Solid Edge file. For example, the value of physical property Accuracy canbe changed in Teamcenter and the change is reflected in Solid Edge. The value for Accuracy canalso be changed in Solid Edge and the value is recorded in Teamcenter.

Using the qualifier /master=iman sets Teamcenter as the property owner and prevents bidirectionalsynchronization. Using the qualifier /master=both, or specifying no qualifier establishes a sharedproperty ownership. The property can be authored in Solid Edge or another Teamcenter application.The use of qualifiers is discussed later in the section Attribute mapping syntax and examples.

NULL value synchronization

By default, the synchronization of null values is prevented. Therefore, overwriting an existing valuewith a null value is not supported by default. This restriction helps maintain the integrity of your data.

However, there are cases in which a null value is recorded. In the event that you use /master=iman,null values are written to Solid Edge properties. In the event that you use /master=CAD, null valuesare written to Teamcenter.

The following table describes the behavior when a property is null and /master=both. It is important toconsider the direction of the transaction (whether you are uploading documents from Solid Edge toTeamcenter or downloading documents from Teamcenter to Solid Edge).

Case CAD Teamcenter Preference/master=both on upload1 Non-Null Non-Null CAD2 Non-Null Null CAD3 Null Non-Null CAD4 Null Null CAD/master=both on download5 Non-Null Non-Null TC6 Null Non-Null TC7 Non-Null Null CAD8 Null Null TC

Attribute mapping syntax and examplesThe syntactical form for the specification of Teamcenter attribute mapping is:

Part-Attr-Name : Path Teamcenter-Property [Qualifier]

Use English in the mapping definitions. The syntax is defined as follows:



Attribute mapping

Part-Attr-NameSpecifies the name of a Solid Edge attribute.

Example

Material

PathSpecifies a series of Teamcenter objects denoting a path starting from the dataset object thatrepresents the corresponding Solid Edge part file. It is further defined as Path=[Teamcenter-Step.]* where Teamcenter-Step is one of the following:

GRM (relationship-type[,object-type])Specifies a GRM relation whose type is relation-type, whose primary object is the currentobject, and whose secondary object gives the next object. In the case that more than onerelation of the given type is associated with the current object, the optional second argumentobject-type is used to identify the type of the referenced object.

Item revisionSpecifies the item revision object that owns the current object. That is, the item revision towhich the current object is associated via a GRM link.

ItemSpecifies the item object corresponding to the current owning item revision object.

JobSpecifies the job in which the current object is included; or, if there is no current job, then themost recent job that the object was in (assuming the job has not been deleted).

PropertySpecifies the name of a Teamcenter property, representing a named property of the currentobject in the object path.

Teamcenter-PropertySpecifies the name of the Teamcenter property to be synchronized with the Solid Edge partattributes.

QualifierSpecifies various controls or conditions for the particular attribute synchronization and can be anyone of the following:

/master=cad the property owner is the CAD application Solid Edge. The property isauthored in the CAD application and changes are saved to Teamcenter.

/master=iman The property owner is Teamcenter. The property is authored by anapplication other than Solid Edge. The property value cannot be changedin Solid Edge.

/master=both Property ownership is shared and can be authored in CAD (Solid Edge)or another Teamcenter application.


Attribute mapping


/description=“note” Displays the content of note, a character string enclosed in single or doublequotation marks, in the first row of the Solid Edge common property dialogboxes such as the New Document dialog box and the Upload Documentdialog box.

/required Sets the attribute as a required field when you create a new file. The NewFile dialog in Solid Edge displays a red asterisk (*) indicating that theattribute is required.

/write_once Enables you to assign a value for the attribute once if the value does nothave an existing value. After a value exists for the attribute, it becomesread-only.

/default Defines a default value for the attribute. The default value appears inthe common property dialog box.

Edit the attribute mapping file

Mappings of Solid Edge properties to Teamcenter attributes are stored in Teamcenter. Additionalmappings can be added by importing a modified mapping definition file into Teamcenter. The existingfile is overwritten each time a new file is imported so the new file must include all your definitions.

Caution

Be sure to export your existing mappings before adding new ones. The existing file isoverwritten each time a new file is imported.

The following steps describe the procedure for exporting the attr.map file on the Teamcenter Serverand then importing the file back into Teamcenter. It is important to note that only the full path syntaxmethod can be used. The abbreviated path is not supported.

Note

The Solid Edge standard property names used in the mapping should be in English. SolidEdge custom properties are displayed as they are defined according to your businesspractice and must consider deployment logistics such as the character set.

1. Export the attribute mapping file by typing the following command in a Teamcenter commandprompt window:

%TC_ROOT%\bin\export_attr_mappings—u=<username> —p=<password> —g=<group>—file=c:\temp\attr.map

The path you specify for the file option is the location for the exported attr.map file.

2. Once exported, open attr.map using your text editor.

3. Edit the attr.map file.

4. Save the attr.map file, and import the mapping into Teamcenter by entering the followingcommand at the Teamcenter Command prompt:



Attribute mapping

%TC_ROOT%\bin\import_attr_mappings—u=<username> —p=<password> —g=<group>-file=c:\temp\attr.map

The mappings are imported into the database. Attribute values are updated on the forms whenfiles are saved in Teamcenter.

5. Restart your services.

Attribute mapping of physical properties

Use the Solid Edge Material Library to distribute a consistent set of materials and associated physicalproperties to all designers. Physical properties such as mass, volume, surface area, material,accuracy, and density can be defined for use in the Teamcenter-managed environment.

Tip

The best practice for implementing the exchange of the material, density, and accuracyproperties in a managed environment is to set the property as owned by CAD, driving thedesign from CAD.

Synchronization of physical properties occurs from Solid Edge to Teamcenter. Physical propertiesare not synchronized from Teamcenter to Solid Edge. The only exception to this is are the Materialand Accuracy properties. Mapping the material, density, and accuracy properties as owned by CAD(/master=cad) is especially important when two physical properties such as material and densityare used in the Teamcenter-managed environment. Density is a dependent property of Material.Changing the material type affects the density, so the density is automatically updated for you. Thisupdate results in physical properties becoming out of date in the Solid Edge document. In this case,when you open a document that is out of date, you are notified that you need to open and check outthe document to update the physical properties and then save the changes. The same conditionsapply for Accuracy. When the accuracy is changed in Teamcenter, and you open the document, youare notified that the physical properties are out of date.

Note

All physical properties are presented as a read-only value on the common property dialogboxes with the exception of Material and Accuracy.

The following is a sample attribute mapping for Material:

TeamcenterMaterial : ItemRevision.GRM(IMAN_master_form,ItemRevision Master).user_data_1 /master=cad/description=”Material”

Teamcenter Rapid StartMaterial : ItemRevision.GRM(IMAN_master_form,ItemRevision Master).TCX_Matl /master=cad/description=”Material”

The Material property is an English-only attribute for mapping, but is presented in the languageused by Solid Edge on the dialog box entries.


Attribute mapping


Solid Edge physical properties such as mass, volume, and density can also be mapped. Thefollowing example specifies a Teamcenter Item Type of Document.

Material : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).SE_Material /master=cad/description=”Material”

Mass : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).SE_Mass /master=cad /description=”Mass, Physical Properties”

Volume : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).SE_Volume /master=cad /description=”Volume, Physical Properties”

Density : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).SE_Density /master=cad /description=”Density, Physical Properties”

Additional attribute mapping examples

Author mapped to Teamcenter Item Name

In the following example, the Solid Edge standard property, Author is mapped to the Teamcenterstandard attribute Item Revision, and the owning user's name (the person who created the object).

Author : ItemRevision.owning_user.user_name /master=iman /write_once/description=”Owning User”

Unit of Measure mapped to Teamcenter standard attribute, Unit of Measure

Teamcenter does not deliver a list of values for Item Unit of Measure. You can add values withBMIDE using the New Unit of Measure command. To map the symbol in Solid Edge EmbeddedClient, set the Teamcenter preference SEEC_UOM_Name_or_Symbol=1. Then map the symbolsimilar to the following example:

{ Dataset type="SE Part"UOM : Item.uom_tag /default=”ea” /mater=both /description=”Unit of Measure”}

This passes the value ea to the common property dialog boxes in Solid Edge Embedded Client as thedefault value when saving a Solid Edge Part document.

Custom property mapped to Teamcenter standard attribute Item Revision, created date

In the following example, the Solid Edge custom property is mapped to the Teamcenter standardattribute Item Revision, create date.

Item_Rev_Creation_Date : ItemRevision.creation_date /master=iman/description=”ItemRevsion date created”

Custom property mapped to Teamcenter standard attribute, Dataset, status

The Solid Edge custom property is mapped to the Teamcenter standard attribute Dataset, status.Dataset_Status : last_release_status.name /master=iman /description=”Dataset Status”

Dataset_Status_Date : date_released /master=iman /description=”Dataset Status Date”

Custom property mapped to Teamcenter standard attribute, Item Revision, status

The Solid Edge custom property is mapped to the Teamcenter standard attribute Item Revision, status.



Attribute mapping

ItemRev_Status : ItemRevision.last_release_status.name /master=iman/description=”ItemRevision Status”

ItemRev_Status_Date : ItemRevision.date_released /master=iman/description=”ItemRevision Status Date”

Custom property mapped to Teamcenter standard attribute, Item Revision, description

ItemRev_Name : ItemRevision.object_name /master=both /write_once/description=”ItemRevision Name”

Custom property mapped to Teamcenter standard attribute, Item Revision, description

ItemRev_Desc : ItemRevision.object_desc /master=both/description=”ItemRevision Description”

Sample Sheet Metal attribute mapping definition using List of Values

Any mapping definition exercise must use an explicit mapping definition.{ Dataset type="SE SheetMetal"

Author : ItemRevision.owning_user.user_name /master=iman /write_once/description="Owning User ID"

ITEM_REV_CREATION_DATE : ItemRevision.creation_date /master=iman/description="ItemRevision Date Created"

{ Item type="Item"Title : ItemRevision.object_desc /master=cad /description="IR Description"IR_Name: ItemRevision.object_name /master=cad /description="IR Name"ID_01 : Item.GRM(IMAN_master_form,Item Master).user_data_1 /master=cad

/description="Interdependent, 1"ID_02 : Item.GRM(IMAN_master_form,Item Master).user_data_2 /master=cad

/description="Interdependent, 2"CAS_01 : Item.GRM(IMAN_master_form,Item Master).user_data_3 /master=cad

/description="Cascading LOV"EXH_01 : ItemRevision.GRM(IMAN_master_form,ItemRevision Master).user_data_1

/master=cad /description="Exhaustive"SUG_01 : ItemRevision.GRM(IMAN_master_form,ItemRevision Master).user_data_2

/master=cad /description="Suggestive"RAN_01 : ItemRevision.GRM(IMAN_master_form,ItemRevision Master).user_data_3

/master=cad /description="Range"}{ Item type="Document"

EXH_S01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).EXH_S01 /master=cad /description="Exhaustive, Str"

EXH_I01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).EXH_I01 /master=cad /description="Exhaustive, Int"

SUG_S01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).SUG_S01 /master=cad /description="Suggestive, Str"

RAN_I01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).RAN_I01 /master=cad /description="Range, Int"

RAN_D01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).RAN_D01 /master=cad /description="Range Double"

CAS_EXH_S01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).CAS_EXH_S01 /master=cad /description="Cascading LOV, exhaustive"

CAS_SUG_S01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).CAS_SUG_S01 /master=cad /description="Cascading LOV, suggestive"

CAS_SUG_C01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).


Attribute mapping


CAS_SUG_C01 /master=cad /description="Cascading LOV, suggestive"CAS_SUG_T01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).

CAS_SUG_T01 /master=cad /description="Cascading LOV, suggestive"ID_EXH_S01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).

ID_EXH_S01 /master=cad /description="Interdependent, 1, exh"ID_EXH_S02 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).

ID_EXH_S02 /master=cad /description="Interdependent, 2, exh"ID_SUG_S01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).

ID_SUG_S01 /master=cad /description="Interdependent, 1, sug"ID_SUG_S02 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).

ID_SUG_S02 /master=cad /description="Interdependent, 2, sug"DPA_SUG_S01 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).

DPA_SUG_S01 /master=cad /description="Added Prop Desc Attachment, Value"DPA_SUG_S02 : ItemRevision.GRM(IMAN_master_form,DocumentRevision Master).

DPA_SUG_S02 /master=cad /description="Added Prop Desc Attachment, desc"}

}



Chapter 8: Preparing unmanaged documents for Teamcenter

Importing thousands of unmanaged Solid Edge documents into Teamcenter can be a time-consumingprocess. Careful attention is needed to analyze existing documents, modify file properties based onyour desired managed structure, and correct broken links and duplicate filenames discovered duringanalysis. The Data Preparation Utility is available to help you prepare your unmanaged data andimport it into a Teamcenter-managed environment.

You can import unmanaged, properly prepared files into Teamcenter using the Add to Teamcenterapplication. Successful use of the Add to Teamcenter application requires that all property informationis defined correctly in the unmanaged files. Typical problem areas requiring correction include:broken links, duplicate filenames, undefined property information, and property values which exceedthe maximum character length as defined by Teamcenter.

Preparing unmanaged documents for TeamcenterDocument preparation

To prepare your unmanaged documents for Teamcenter, you should:

• Remove documents you do not want to manage.

• Find duplicate document names.

• Scan for invalid document names.

• Map Solid Edge properties to Teamcenter attributes.

• Create custom properties to define the Item Revision for non-Solid Edge documents (image files,.pdf documents, and Microsoft Office documents) and to define the properties for non-graphicparts (grease, paint, etc.).

• Use the Data Preparation Utility to analyze files, fix broken links, and modify properties in yourunmanaged data.

Remove unwanted files

When you select a folder to add to Teamcenter, every document in the folder is added to Teamcenter,regardless of whether or not you want to manage them. You should remove any documents that youdo not want to manage before adding the folder to Teamcenter. These documents might include textor log files that reside in the folder you want to import.

Find duplicate document names

You can add duplicate documents to Teamcenter, but duplicate document names cannot exist in thesame folder. If duplicate document names are found, you should ensure that you are adding thecorrect document to the Teamcenter.



Find invalid document names

Teamcenter supports the same conventions that the file system supports for naming folders anddocuments. Folder and document names can consist of all Unicode characters except the followingcharacters: # : \ ? * < > % / | " ~ !

Search your local folder for invalid document names before adding them to Teamcenter.

Map Solid Edge properties to Teamcenter attributes

In Teamcenter, the key attributes used to track part numbers and revisions are Item ID, Revision, andItem Name. In an unmanaged document, the corresponding Solid Edge properties are displayedon the Project page of the File Properties dialog box. You can access the File Properties dialogbox by choosing Application button→Info→File Properties. Defining these properties in SolidEdge before adding the documents to Teamcenter minimizes your future efforts and Teamcenter willbe more accurately populated from the start.

Some things to consider regarding Solid Edge property mapping:

• If the Solid Edge Document Number property is left blank, an Item ID is automatically generatedand assigned for you when you import the data into Teamcenter. You should define the DocumentNumber, Revision Number, and Project Name before loading your data into Teamcenter.

• If any of the Solid Edge properties contain more than the maximum character length,or if the Document Number plus the Revision is greater than the maximum characterlength, you are notified of an error on import into Teamcenter. The error is recorded inthe log file generated by the import application. The default location for the log file is\Users\<username>\AppData\Roaming\Siemens\Solid Edge\Version 220\Log Files.

• In the Teamcenter-managed environment, only one Solid Edge 3D dataset is allowed per Item.However, multiple Drafts can be associated with each item as item revisions. When unmanaged3D datasets using the same Document Number property are imported into Teamcenter, you mustdecide to save your Solid Edge Draft documents to the same Item Revision as the Solid Edge 3Dcontent or save your Solid Edge Draft documents to a separate Item.

• Solid Edge Properties and Teamcenter Attributes should match Type (For example: String withString, Date with Date and Numeric with Numeric).

• When Solid Edge transacts data with Teamcenter, it uses a name that is unaffected by localization.This is referred to as the real name. The real name has also been used for the display in the userinterface. Beginning with Teamcenter 8.3, a unique prefix is added to all new business objects toguarantee uniqueness. The resulting name is often not desirable for display in the user interface.The use of a display name addresses this issue. The display name is used for column headers incommon property dialog boxes for mapped properties other than the mandatory properties.

• Mapping the Project ID is not supported. Use the Teamcenter preference,SEEC_Property_AssignToProject_Name, to determine the project for documents beingimported.

• The Item Type and Dataset Description are localized, while the Dataset Name is English-only.



Preparing unmanaged documents for Teamcenter

Note

The Solid Edge property to Teamcenter attribute mapping is case sensitive.

Create custom properties

You can create custom Solid Edge properties to map to Teamcenter attributes. For example, you cancreate custom properties to define the Item Revision for non-Solid Edge documents including imagefiles, .pdf documents, and Microsoft Office documents (MS Word, MS Excel, MS PowerPoint). Youcan also create custom properties to define the properties for non-graphic parts.

There are three basic steps to creating custom properties:

• Provide a name for the custom property.

• Select the type of property you are creating.

• Type a value for the property.

For more information regarding custom properties, refer to the Solid Edge Help topic Creating customdocument properties.

Adding non-graphic parts into Teamcenter

Before you add non-graphic parts (grease, paint, etc.) to Teamcenter using Add to Teamcenter,create the custom properties:

• SE_ASSEMBLY_QUANTITY_OVERRIDE

• SE_ASSEMBLY QUANTITY_STRING

• Unit of Measure (UOM)

If one or more of these properties are missing when you add the document to Teamcenter, the item isadded to the assembly without the non-graphic information.

Tip

Use the Add to Teamcenter Dry Run prior to adding your document to Teamcenter in orderto be notified of any condition that should be resolved.

The value of unit of measure must be considered with regard to what is defined as geometric units ofmeasure. The Teamcenter preference SEEC_UOM_List_as_Geometric defines the unit of measurevalues that represent geometric components. (Example: each)

Note

For more information on the SEEC_UOM_List_as_Geometric preference, refer to theTeamcenter Preferences section of the Teamcenter Integration for Solid Edge (SEEC)Guide for Users and Administrators.




Importing non-Solid Edge documents into TeamcenterWhen non-Solid Edge documents are added to Teamcenter using Add to Teamcenter, the customproperties that map Solid Edge properties to Teamcenter attributes is used. If the Item Type, Item ID,and Item Revision are defined, the non-Solid Edge document is uploaded into Teamcenter using thedefined property mappings. However, if any defining properties are missing, the Teamcenter attributeis automatically assigned as with any other document type.

Caution

If the Solid Edge property that defines the Teamcenter Item ID/Item Revision is not defined,the values will be auto-assigned upon import. The non-Solid Edge document may notreceive the same Item Revision number as its parent document. Create custom propertiesto map Solid Edge properties to Teamcenter attributes defining the Item Revision beforeadding the non-Solid Edge document to Teamcenter.

To set properties in groups of files:

1. Start Solid Edge.

2. Click the Application button and choose Info→ Property Manager.

3. In the Select dialog box, navigate to and select a folder containing the files whose propertiesyou want to edit.

4. Click Add to add the file folder to the list of files to process.

5. Click OK.

6. In the Property Manager dialog box, expand the list by clicking the + beside the folder name.

Warning

A warning dialog box may be displayed indicating that some files cannot be processed.This happens if there are files in the folder that do not support properties. If thiswarning message is displayed, click OK on the dialog box to dismiss the warning.

7. Type the values for the various properties.

Tip

You can click the right mouse button to display a list of commands that assist in makingthis process quicker.




Add unmanaged documents to Teamcenter1. In Windows 10, choose Start→Siemens Solid Edge 2020→Add to Teamcenter.

Caution

Running Add to Teamcenter while Solid Edge documents are open can causeinterference with documents that exist in the cache. As a best practice, close all SolidEdge documents before running Add to Teamcenter.

Optionally, you can clear existing cache content prior to running Add to Teamcenter.

□ In the Add to Teamcenter dialog box, click Cache.

□ Log on to Teamcenter by entering your User ID and Password.

□ In Cache Assistant, clear your cache by choosing Workspace group→Clear Cache.

□ Click Yes to confirm that you want to delete all the documents from the project.

□ Close the Cache Assistant dialog box.

2. In the Add to Teamcenter dialog box, select the folder or documents you want to add to themanaged library.

3. Click Add and your selection is added to the Folders and Documents To Be Added list.

4. To link the files that are added to Teamcenter to a specific folder, select the Add Documentsto This Folder check box.

Use Browse for Library Folder to choose a folder from the Select Folder dialog box orcreate a new folder.

Note

Leaving the Add Documents to This Folder check box cleared adds thefiles to Teamcenter, but the folder is determined by the Teamcenter preferenceWsoInsertNoSelectionsPref. By default, they are linked to the Newstuff folder.

5. Click Dry Run to examine the selected unmanaged files for broken links or missing informationand generate an ordered list of your documents.

The documents are not added to the library. The documents remain in the queue for you tomake any necessary corrections using the Data Preparation Utility, and then return to Add toTeamcenter.

6. (Optional) Select the Update Status On All Documents to Checked-In check box to check thedocuments into Teamcenter.

7. Determine how you would like the software to handle an overwrite condition by setting theOverwrite option.




The Add to Teamcenter program compares the Teamcenter import date with the date the fileswere last modified to see if the files have already been loaded into Teamcenter. You can setthe overwrite option to prompt you, to overwrite all documents it finds, or to not overwriteany documents. This option is particularly helpful if you are loading unmanaged documentsunattended.

Note

You can load files over files that already exist in Teamcenter. Add to Teamcenterchecks the item, revision, and dataset against those already in the database and givesyou the option to check out the document and overwrite it, check out all files that existand overwrite them, leave the file and use the file already in the database, leave allfiles and use the ones that already exist in the database or cancel the import process.

8. Set the Revision Rule for use with the documents.

Your choice specifies the revision rule used to create the BOM. If this is the first time you have runAdd to Teamcenter, the Teamcenter default Revision Rule is used. The Teamcenter PreferenceTC_config_rule_name defines the default Revision Rule.

9. (Optional) Set the Automatically Retry Documents That Fail to Load check box to retry theload of any documents that failed to load on the previous attempt.

10. Click OK to perform the Dry Run.

While the dry run is processing, you can monitor its progress on the Add to Teamcenter Statusdialog box. The files in a dry run are not validated against what is in Teamcenter.

Caution

Repair any broken links before proceeding with adding your unmanaged documentsinto Teamcenter.

You can suspend Add to Teamcenter and use the Data Preparation Utility to correct reportedproblems in your unmanaged files.

Once any broken links or other problems have been corrected, restart Add to Teamcenter tocomplete any unfinished actions.

11. If no broken links or missing information were found, respond to the Validations Complete dialogbox by clicking View Log, Summary, Continue, Cancel, or Suspend.

Clicking Continue loads the documents into Teamcenter.

12. When your selected documents successfully load into Teamcenter, you are notified that the Addto Teamcenter process is complete.

13. (Optional) Click Cache to view your documents in the cache.




Overwriting documents using Add To Teamcenter

The Add to Teamcenter application compares the item number, revision, and dataset values of adocument with those existing in Teamcenter. As a result, you can import files over files that alreadyexist in Teamcenter. Add to Teamcenter adds the import time to the original file, and on subsequentloads, it checks to see if the modified date is after the import date. If the document being importedhas not been modified since the last import, it is recognized as already being in the database and isnot re-added to Teamcenter on subsequent imports. However, if the unmanaged file is modified afterits initial import into the database, on subsequent imports you are given the options to:

• Check out the document and overwrite it.

• Check out all files that exist and overwrite them.

• Leave the file and use the file already in the database.

• Leave all files and use the ones that already exist in the database.

• Cancel the import process.

In the event the Add to Teamcenter comparison discovers an item number that already exists in thedatabase, it compares the file being imported to all revisions, datasets, and files that comprise thedataset. If a match is found, you are given the opportunity to determine the action on the file beingimported. If no match is found, the file is assigned a new item number and a record of the action isplaced in the log file.

For example, if the following information exists in Teamcenter:

Item ID 000100Revision ADataset SE Part 000100/ANamed Reference part1_04112007.parRevision BDataset SE part 000100/BNamed Reference 000100.par

Then when you import a file with 000100 as the document number, a comparison is made betweenthe file name of the file being imported against all named references (ie., part1_04112007.par and000100.par in this example). If it matches, you are given the option to overwrite the file. If you choosenot to overwrite, the file is assigned a new item ID, which is recorded in the log file.

Log files

When you run the Add to Teamcenter process, log files are generated that contain errors or warningsoccurring during the file upload transaction. The default location for log files is determined on the FileLocations page of the Solid Edge Options dialog box.You can use log files to monitor the success or failure of your documents loading into Teamcenter.The log files you will interact with most often are grouped in the subfolder \Add to Teamcenter thatis created when you run Add to Teamcenter. Each file uses a naming convention consisting of adescription, timestamp, and file extension. For example, AddToTeamcenter_20180514131232.log.The timestamp is a 14 digit unique identifier using the format YYYYMMDDHHmmss where:

• YYYY is the year. In the example, 2018.




• MM is the month. In the example, 05 is May.

• DD is the day. In the example, 14 is the 14th.

• HH is the hour using a 24-hour clock beginning at midnight which is 00 and going through 23,which is 11:00pm. In the example, 13 is 1:00pm.

• mm is the minute. In the example, 12 is 12 minutes past the hour.

• ss is the seconds. In the example, 32 is 32 seconds past the minute.

Log File Description

AddToTeamcenter_<timestamp>.logContains all Add to Teamcenter optionsettings. The setting names are notlocalized for this development log file.

ATTHistory_<timestamp>.xml

Contains information regarding the blocksof data being added to Teamcenter, thenumber of links within the block, and howlong each block took to load. The historyis only reset and cleared if you start anew Add to Teamcenter process.

SEEC User Log <unique id>.xml

Contains a summary of actions taken bythe Add to Teamcenter process to correctthe data and load it into the database.These actions are logged as warningswith messages specific to why thecorrective action was taken. If a file failsto load, an error is shown in the summarylog with a message explaining why thefile failed to load. The contents of this logfile displays in the SEEC Summary dialogbox when you are importing files usingAdd to Teamcenter.

TALLog_<timestamp>.xmlThe Teamcenter Application Layer logfile. Includes a timer so the total time forinput is measured accurately.

Note

All log files persist from one Add to Teamcenter session to another. Work withyour system administrator to develop a schedule to archive the contents of the\Users\<username>\AppData\Roaming\Siemens\Solid Edge\Version 220\Log Filesfolder and free space on your computer.

Output files

When you run the Add To Teamcenter process, files are generated as output of theprocess. All output files created from one input list have the same timestamp so it is easy




to identify which output file is related to another. The default location for output files is,C:\Users\<username>\AppData\Roaming\Siemens\Solid Edge\Version 220\Log Files.

Output File Description

BrokenLinkLog_<timestamp>.xml Contains information regarding the broken linkand the parent document.

Unordered_<timestamp>.CSV

Lists input files after the completion of the scanfor broken links. You must have Microsoft Excelor another .csv editor installed to open this file.

Caution

This file cannot be used as input to theAdd to Teamcenter process.

Ordered_<timestamp>.CSV

Contains an ordered list of your input files alongwith their reverse links. If a file has a reverse link,it is listed twice with two order numbers and alsolisted twice in the pass/fail log. The ordered listis generated by either the output from a dry runor as a result of the pass/fail log.

Note

You can rename theOrdered_<timestamp>.csv fileand use it as an input file to Addto Teamcenter; however the formatmust match the expected input. Youcan only submit one .CSV file forprocessing at a time.

SuccessFailureLog_<timestamp>.CSV

Lists the documents you are importing andprovides a summary of success or failure of theimport process for each file. The log is writtenonce per Add to Teamcenter session even if youelect to suspend or retry the upload process.The order number in this file matches the ordernumber from the Ordered_<timestamp>.CSVfile so you can match up entries between the twofiles during troubleshooting.

Note

Each of the output files persist from one Add to Teamcenter session to another, so youneed to work with your system administrator to develop a schedule to archive the contentsof the C:\Users\<username>\AppData\Roaming\Siemens\Solid Edge\Version 220\LogFiles folder and free up space on your computer.




Using automated utilities to import unmanaged Solid Edge data intoTeamcenterThe Data Preparation Utility is available to assist you with analyzing your data prior to importing itinto Teamcenter. The program is delivered when Solid Edge is installed.

Choose Start→Siemens Solid Edge 2020→Data Preparation Utility to access the program.

By utilizing the Data Preparation Utility to prepare your data to properly map existing Solid Edgeproperties to Teamcenter attributes before adding them to Teamcenter, you can minimize future efforts.



Chapter 9: Using the Data Preparation Utility

The Data Preparation Utility is designed to assist you with preparing large batches of unmanageddata using an automated process. The program is available to you when Solid Edge is installed.Included in this section is information about how to:

• Access the Data Preparation Utility.

• Use the program to perform an analysis of your existing data. The program:

o Evaluates Solid Edge files for duplicate document number values, duplicate file names,empty revision entries, empty project names, and broken links.

o Performs a file name length analysis.

o Evaluates the Solid Edge to Teamcenter property mapping.

• Fine-tune the data generated by the analysis through the use of the analysis report,PropertyList_<timestamp>.xlsm so that it correctly represents the data that will be importedinto Teamcenter.

Caution

It is imperative for your unmanaged data to be evaluated and corrected prior to importso Teamcenter is correctly populated from the start which minimizes future efforts.

If you use custom Solid Edge data properties, you must define the custom properties for usein Teamcenter using the spreadsheet datapreputilitiestemplate.xlsm located in \ProgramFiles\Siemens\Solid Edge 2020 \Program.

• Repair broken links.

• Update the unmanaged files with changes identified.

Considerations before accessing the Data Preparation UtilityThe processing of unmanaged documents by the Data Preparation Utility takes place on the clientsystem running the utility. Considerations prior to running the utility are:

• A minimum of 4gb of memory is recommended on the client system.

• Available disk space 1.5 times the size of the dataset being processed is recommended forthe client system.

• Microsoft Office Professional 2010 or Microsoft Office Professional 2013 must be installed for youto run the Data Preparation Utility.



Note

The input file must be in .xlsm document format.

• Perform a backup of your data prior to using the utility.

• The computer containing data being analyzed or imported should be on an isolated network andinaccessible by users actively modifying the documents in a production environment.

• Identify the non-Solid Edge files you want to import before running the utility. If the non-SolidEdge files are not linked to Solid Edge files, they should be imported into Teamcenter outsidethis environment. Consult Teamcenter documentation for importing the non-linked, non-SolidEdge files into Teamcenter.

• Identifying a target data set (mass of data that has been broken down into logical pieces) forimporting, such as a specific folder of data, is recommended over a mass importation of data intoa Teamcenter-managed environment.

• A significant amount of time is required to analyze, prepare, and import your Solid Edge datainto Teamcenter. An estimate for analyzing and preparing your files is one week per 15,000 filesbeing imported, depending on the state of your existing data.

While actual import rates vary, you can assume approximately 250 files per hour. There areseveral factors that affect this estimate including, but not limited to the following:

o Available system memory.

o Number of unmanaged files being imported.

o Size of unmanaged files.

o Number of top level assemblies.

o Network bandwidth.

Data Preparation Utility workflow

Basic workflow

A general overview of the steps for preparing the data are:

• Determine the document management application for which you are preparing your data.

• Set your working folder if you want to use a folder other than the default folder for log files.

• Select files or folders for analysis, or use an exising ordered or unordered list of documents.

• Analyze your unmanaged files to identify many of the document preparation tasks necessary forimporting your data to the managed environment. The Generate Import List option:



Using the Data Preparation Utility

o Evaluates Solid Edge files for duplicate document number values, duplicate file names,empty revision entries, empty project names, and broken links.

o Performs a file name length analysis.

o Evaluates the Solid Edge property mapping.

o Reports the results in spreadsheet form in an analysis report.

Caution

If you use custom Solid Edge data properties, you must define the custom propertiesfor use in Teamcenter using the spreadsheet datapreputilitiestemplate.xlsm locatedin \Program Files\Siemens\Solid Edge 2020 \Program. For instructions, see Definecustom properties prior to analysis.

• Repair broken links in Solid Edge files before you import them into the managed environmentusing options in the Fix Broken Links tab.

• Update unmanaged Solid Edge files based on entries in the analysis report and Modify Propertiesof the unmanaged Solid Edge files.

• Use the Add to Teamcenter program to import your properly prepared unmanaged document tothe managed environment.

The following section of this document contains procedures for completing the file analysis, fixinglinks and modifying files. Use the checklist provided at the end of this section to assist you withmoving through the process.

Perform a Solid Edge file analysisUse this procedure to analyze your files and prepare the master list of files for import into themanaged environment.

Note

If your Solid Edge files contain custom properties, define those properties before runningthe Data Preparation Utility. For details, see Define custom properties prior to analysis.

1. Choose Start→Siemens Solid Edge 2020→Choose PDM Integration.

2. On the ribbon, click Utility.

3. Select the document management application for which you are preparing your data:

• Teamcenter

• Unmanaged




4. (Optional) To change the default location for the log files generated as output of the analysis,click Set Working Folder.

Note

By default, the utility saves log files in\Users\<username>\AppData\Roaming\Siemens\Solid Edge\Version 220\LogFiles\Data Preparation.

5. (Optional) To view the contents of the working folder click, Open Working Folder.

6. In the Generate Import List tab, click Select Files/Folders.

7. Select whether the files to be analyzed are located in a file or in a system folder.

Use this option To do this

Add Files Identify individual files for analysis or define the location of either theordered or unordered CSV file containing the list of files for analysis.

Add Folders Identify the location of the system folders containing the files foranalysis.

8. Browse for the files or folders specified in the previous step.

Tip

• When you choose to Add Folders, you can select the Include Subfolders checkbox so that any subfolders are included for you.

• You can click Types to filter your selection by file types (.dft, .asm, .par, .psm, .pwdor All documents including non-Solid Edge documents).

• You can click Remove or Remove All to modify the list of files or folders.

9. To start the analysis, click Generate Import List.

The length of time required for processing depends on the number of files analyzed. Whenprocessing is finished, several files are generated for you:

• AnalysisOfSolid Edgefiles_<timestamp>.txt

Contains a summary of the file analysis.

• DataPrep_Links_<timestamp>.xlsx

Lists relation types if the relation type is a reverse link.

• OrderedList_<timestamp>.CSV

Contains the master list of files to be imported into the managed environment in the orderin which they are to be imported.




• PropertyList_<timestamp>.xlsm

Displays the results of the data analysis in a separate window. For more information, seeAnalysis report.

• Unordered_<timestamp>.CSV

Contains a list of files to be imported into the managed environment.

10. To add property data or correct problems identified during the analysis, use the tools in theanalysis report to apply corrections to the files listed.

Examples of the type of corrections you might need to apply include changing the Project ID,changing revisions, or renaming existing unmanaged files.

Tip

• If broken links are identified in the file analysis, use the options in the Fix BrokenLinks tab to repair them. To learn how to do this, see Fix Links in Solid Edge Files.

• To modify the properties of your unmanaged Solid Edge files with the changes youspecify in the analysis report, click the Modify Properties tab.

11. Exit the analysis report, PropertyList_<timestamp>.xlsm.

Note

The commands for making changes to your Solid Edge files rely on macros. If youclose and reopen the spreadsheet, macros may be disabled due to your MicrosoftOffice security settings. Discuss your security policy with your system administratorbefore making changes to your security settings.

Analysis reportThe analysis report displays the results of data analysis in a spreadsheet,PropertyList_<timestamp>.xlsm. The analysis report utilizes the commands at the top of thespreadsheet for correcting or confirming data prior to importing into a managed environment.

You can use the analysis report to:

• Define or correct property data prior to importing into the managed environment.

• Rename unmanaged files.

• Separate the file name and revision number in an existing file name.

• Mark documents to delete from disk.




The commands for manipulating your Solid Edge files are dependent on macros being enabled. If

you notice the warning, macros may be disabled due toyour Microsoft Office security settings.

Caution

Discuss your security policy with your system administrator before making changesto your security settings.

The analysis report user interface has a horizontal, tabbed command ribbon making all commandsvisible and accessible. On each tab, functions are organized by group to help you locate them.

Using tabs in the spreadsheet

The tabs containing functions you will use most frequently to define or correct property data beforeimporting your documents into the managed environment are:

SE Data PrepMark Previous RevisionsSearches the files listed as a result of the analysis and finds the latest revision of the filesbased on the document number. All revisions preceding the latest revision are markedfor deletion with an X in the Delete column.

Remove Custom PropertiesRemoves the specified custom properties from the documents listed in the spreadsheet.

Delete MarkedScans the Delete column of the spreadsheet for those marked with an X. When processed,these files are immediately deleted from disk.

Caution

Deleting files from disk can create broken links. Use care when marking filesfor deletion.

Remove TimestampDeletes the timestamp from each listed file so the same data can be imported more thanonce into the database.

Set File StatusImmediately resets the Solid Edge status property of selected files to Available.

Get SE VersionSearches the files listed and locates the latest saved version.

Set Write AccessSets the files with Write access.




Set Read Only AccessSets the files with Read Only access.

Split FilenameSearches for a delimiter defined in the ribbon and divides the file name into two portions.Data to the left of the delimiter is used in the Document Number property definition. Data tothe right of the delimiter is used in the Revision property definition.

Copy Filename to Doc NumCopies the existing file name of a document without its extension to the Document Numberproperty. As a result, once the data is imported into Teamcenter, the file name is used forthe Item ID.

Copy Filename to ProjectCopies the existing file name of a document without its extension to the Project nameproperty. As a result, once the data is imported into Teamcenter, the file name is used forthe Item Name.

Copy Doc Num to FilenameCopies existing document numbers to new file names. Existing data is not modified.

Append DFT to Doc NumAppends -DFT to the existing document number for draft files only.

Increment Doc NumIncrements the existing document number with the prefix and starting value you specify.

Parse FilenameSorts the data by the value you specify. You supply the Start and To information along withthe Column where you want the results displayed.

Note

The value for the column is the numerical value as counted left to right on thespreadsheet.

Append Doc NumAdds the string you specify to either the beginning or end of the document number.

String in FilenameFinds files with the string you specify, and then places another string you specify in thecolumn you specify.

Tip

Standard parts usually have something unique in the file name. This function canbe used to add the word Standard in the Teamcenter Item Type column for that file.

Multiple 3DFinds Draft (.dft) documents with links to multiple 3D Solid Edge documents.




From Linked 3DPopulates Draft (.dft) document numbers from the linked 3D Solid Edge document.

From Linked DraftPopulates 3D document numbers from the Draft (.dft) document with the same file name.

SE Final CheckRemove Cell Background ColorRemoves the color coding of cells in the spreadsheet. This command should be performedbefore rechecking for duplicates in the document number and file name.

Compute LongestCalculates the total character length of each column and reports it for evaluation.

Note

There is no logic applied to compare the values reported to the maximum characterlimit of fields within Teamcenter. You must manually verify the maximum characterlimit which varies depending on the version of Teamcenter you are running.

DuplicatesEvaluates modified data to ensure the property information is correct and contains noduplicate data before importing into Teamcenter. Duplicate file names are shown in red, andduplicate document numbers are shown in yellow.

If duplicates are found, the cell is colored red and a message indicates Duplicate Filenameor Duplicate Document Number.

Check RevisionDetermines the linked 3D file for each draft file found, then marks the files where there isa mismatch between the revision of the draft and 3D files. This command is helpful foridentifying situations where the draft and 3D files will be imported into separate TeamcenterItem Revisions when the intention is to import them into the same item revision.

Remove StringDeletes the defined string from each of the cells in the spreadsheet.

AllCreates a text file for exporting. The file contains all documents in the list.

SE MiscSynchronizeSynchronizes legacy standard parts with generated Teamcenter standard parts. You havethe option to indicate if you have CAD partner standard parts installed.

Help AboutDisplays Solid Edge help.




Fix links in Solid Edge filesUse this procedure to analyze your unmanaged Solid Edge files, and then fix broken links in the filesbefore you import them into the managed environment.

Warning

Failure to repair broken links before proceeding with the data preparation and importprocess can result in an improperly populated database.



3. Select the document management application for which you are preparing your data:

• Teamcenter

• Unmanaged

4. (Optional) To change the default location for the log files generated as output of the analysis,click Set Working Folder.

Note

By default, the utility saves log files in\Users\<username>\AppData\Roaming\Siemens\Solid Edge\Version 220\LogFiles\Data Preparation.

To view the contents of the working folder click, Open Working Folder.

5. In the Generate Import List tab, click Select Files/Folders.

6. Select whether the files to be analyzed are located in a file or in a system folder.

Use this option To do this

Add Files Identify individual files for analysis or define the location of either theordered or unordered CSV file containing the list of files for analysis.

Add Folders Identify the location of the system folders containing the files for analysis.

7. Browse for the files or folders specified in the previous step.




Tip

• When you choose to Add Folders, you can select the Include Subfolders checkbox so that any subfolders are included for you.

• You can click Types to filter your selection by file types (.dft, .asm, .par, .psm, .pwdor All documents including non-Solid Edge documents).

• You can click Remove or Remove All to modify the list of files or folders.

8. To start the analysis, click Generate Import List.The length of time required for processing depends on the number of files analyzed. Whenbroken links are found, a message is displayed. You have the option to:

• View Broken LinksProvides details about the broken links along with alternate paths for the link.

• ContinueProceeds with the analysis.

• CancelStops the analysis.

9. Click View Broken Links.You are provided details about the broken link and alternate paths.

10. Choose the View Properties tab.The path to the broken links file, BrokenLinkLog_<timestamp>.xml, is provided for you.

11. Verify the path to your Unordered_<timestamp>.CSV file is correct.

Both the BrokenLinkLog_<timestamp>.xml and the Unordered_<timestamp>.CSV weregenerated by the file analysis.

12. Click Analyze.

13. Your analysis information can be spread across multiple datasheets inPropertyList_<timestamp>.xlsm. Select the datasheet that contains the linkreplacement information.

14. For each broken link, provide both the broken link path and broken link file name as well as thereplacement path and replacement file name.

15. Save the spreadsheet and click Fix Broken Links.After the status indicates Finished processing, you can continue modifying properties or useDesign Manager to verify that the broken links are fixed.

16. In the Data Preparation Utility, select the Modify Properties tab and click Modify Properties.




Modify Solid Edge files using the Data Preparation UtilityUse this procedure to modify the properties of unmanaged Solid Edge files according to thespecifications you enter in the analysis report, PropertyList<timestamp>.xlsm. You must have writeaccess to the unmanaged files to save the properties.



3. Click the Modify Properties tab.

4. Verify that the analysis report displayed in the dialog box contains the unmanaged Solid Edgefiles to be modified along with the new property information.

This file was generated with the Generate Import List option. The default location for the reportis \Users\<username>\AppData\Roaming\Siemens\Solid Edge\Version 220\Log Files\DataPreparation\PropertyList_<timestamp>.xlsm.

5. Click Modify Properties.

The length of time required for processing depends on the number of files to process. A statusnotification is displayed to let you know when processing is complete. The results of processingthe data are also written to the log file FileRename_<timestamp>.log.

6. (Optional) Click View Log to view the contents of the log generated during modification of theunmanaged file properties.

You can now add your unmanaged files into Teamcenter.

Import process checklist□ Use the Data Preparation Utility to check for duplicate document number values, duplicate

filenames, and to evaluate the Solid Edge to Teamcenter property mapping in yourunmanaged files.

□ Repair any problems identified during the analysis using the tools in the Analysis Report.Apply corrections to the files listed in the Analysis Report.

□ Use the Modify Properties option to modify the unmanaged Solid Edge files with the changesyou specified in the analysis spreadsheet.

□ If you rename files, use Fix Broken Links to correct any broken links that were the result ofrenaming the files.



Chapter 10: Add to Teamcenter - Interactive

Add to Teamcenter - InteractiveAdd to Teamcenter - Interactive is an application used to add unmanaged Solid Edge design datato Teamcenter. The interactive process is aimed at importing previously managed design data thathas been exported from Teamcenter, given to an external collaboration partner, and then must bereimported into Teamcenter. The primary focus is data that is of a project-related size. It is particularlysuited for supply chain collaboration.

Tip

For large amounts of data, or migrations to the Teamcenter managed environment, use theData Preparation Utility and Add to Teamcenter.

Starting Add to Teamcenter - Interactive

To start Add to Teamcenter - Interactive, choose Start→Siemens Solid Edge 2020→Add toTeamcenter - Interactive.

You can also access Add to Teamcenter - Interactive from within Solid Edge. From the Solid EdgeApplication menu, click Manage→Add Document to Teamcenter.

Note

Access to the Add Document to Teamcenter command from Solid Edge is determined inSolid Edge Administrator.

The start-up screen

The Add to Teamcenter Interactive start-up screen provides a product description, access to help,as well as the commands to login or start a new session. You can access a list of recently useddocuments from the File menu.

Working with Add to Teamcenter - Interactive involves working in sessions. Each session has sessionsettings that apply to all documents selected for import. Using the Session Settings dialog box, youcan define various behavior including the Teamcenter Revision Rule used.

The Add to Teamcenter - Interactive window

The Add to Teamcenter - Interactive window consists of four window panes:

• The upper-left pane of the window contains the list of your unmnaged documents.

• The upper-right pane displays content from Teamcenter much like common property dialogboxes in Solid Edge Embedded Client. This gives you a side-by-side comparison of unmanagedand managed data.



• The lower-left pane contain the Progress Log

• The lower-right pane contain the Error Assistant.

The slider beneath the top two window panes lets you scroll to view additional columns of information.

The Preview for both unamanged and managed documents display in a free floating window.

For more information, see Add to Teamcenter - Interactive help.

Tip

To experience selecting, validating, and adding unmanaged design data into aTeamcenter-managed environment, watch the Using Add to Teamcenter - Interactivevideo accessible from the Self-paced and classroom courses link on the web-basedSolid Edge Help and Training home page.

Enable or disable the Add Document to Teamcenter commandYou can use the Display Add to Teamcenter commands in Solid Edge Application Menu optionin Solid Edge Administrator to enable or disable access to the Add Document to Teamcentercommand in Solid Edge.

Note

The Add Document to Teamcenter command starts the Add to Teamcenter - Interactiveprogram.

Enable the Add Document to Teamcenter command

1. Run SEAdmin.exe.



Add to Teamcenter - Interactive

2. Locate the entry for Display Add to Teamcenter commands in Solid Edge Application Menu.

3. To enable access to the command, set the Value field to Yes.

A message box displays stating the command has been enabled.

4. Log off and back on to Solid Edge.

5. From the Solid Edge Application menu, click Manage→Add Document to Teamcenter.

The Add Document to Teamcenter command is enabled and accessible.

Disable the Add Document to Teamcenter command

1. Run SEAdmin.exe.

2. Locate the entry for Display Add to Teamcenter commands in Solid Edge Application Menu.

3. To disable access to the command, set the Value field to No.

The Add Document to Teamcenter command is shown but disabled in the next Solid Edgesession.


Add to Teamcenter - Interactive

Part III: Troubleshooting

This section includes information to assist you with assessing and correcting problems you mayencounter while running the Teamcenter Integration for Solid Edge (SEEC).


Chapter 11: Troubleshooting

Display Start menu entriesBeginning with Solid Edge ST10, use the following steps to add start menu entries for PDMapplications.

1. Choose Start menu→Siemens Solid Edge 2020→Choose PDM Integration.

The program determines the available PDM integration clients based on your license.

2. Click the Home tab, and from the Start Menu group, select the PDM integration for which youwant Start menu entries, and click Apply .

You can choose to perform other functions, including starting applications, using the optionsin the command ribbon. For more details, see PMD Client - Application Launcher dialog boxin Solid Edge help.

3. Click Exit.

Save weldment bodies to Teamcenter for visualizationWeldments can be visualized with Solid Edge weld beads in both Teamcenter and TeamcenterRapid Start (TcRS).

1. In Teamcenter, create a unique Item Element Type.

2. Set the preference SEEC_Asm_Weldment_Feature_Type to the real name of the Item ElementType you created in step 1.

Tip

For testing purposes, you can use a delivered Item Element Type such asProductInterface, however, this is not recommended for production use.

3. Restart Solid Edge to load the preference.

Weldments subsequently uploaded to Teamcenter include weld beads.

4. Teamcenter Rapid Start (TcRS) users must edit the preference Hide_Types_For_Create andremove the following entries from the preference list.

• parproductinterface

• productinterface

• interfaces



• GeneralDesignElement

Run SEEC diagnosticsThe SEEC Diagnostic Application is designed to provide the information you need to diagnose anyproblems that might arise when you work with Solid Edge in the Teamcenter-managed environment.The application can be used to:

• Set the level of information being logged when Solid Edge is in use in the Teamcenter-managedenvironment.

All log files are saved to the C:\Users\<username>\AppData\Roaming\Siemens\SolidEdge\Version 220\Log Files folder with the exception of soaclient*.txt which is saved to%TEMP%.

• Perform a diagnostic scan that enables you to easily create a collection of information regardingthe configuration of your Teamcenter integration.

Run a SEEC diagnostics scan

1. In Windows 10, start the SEEC Diagnostic Application by choosing Start→Siemens SolidEdge 2020→ Diagnostic Application.

Caution

You should exit Solid Edge, Structure Editor, and Add to Teamcenter before runningdiagnostics.

2. In the SEEC Diagnostics dialog box, verify the selection of the 2-tier or 4-tier button identifyingyour Teamcenter connection type.

If you are not sure about your configuration, see the Help topic Determine your Teamcenterclient configuration.

3. Supply the location of information associated with your specific configuration.

For a 2-tier configuration, browse for the location of your TC_ROOT and TC_DATA information.

For a 4-tier configuration, supply the URL of your server.

4. In the Diagnostic package location, define a folder where the files created by the scan willbe stored.

5. Click Scan.

6. Sign in to Teamcenter when prompted.

The scan begins and you are notified when it completes.

7. To dismiss the Scan Complete message box, click OK.



Troubleshooting

The SEECDiagnostic_timestamp.txt log file is created in the folder you defined in the DiagnosticPackage Location. The folder also contains the log files and other files generated by runningthe diagnostics application.

8. Click Close.

Export attribute mappingAttribute mapping defines what document properties you will exchange between Solid Edge andTeamcenter. Having a list of the attributes you have mapped on the server is significant whentroubleshooting problems. A user with system administrator privileges can obtain this informationby performing an export of the data using the export_attr_mappings command and arguments. Theoutput of the export is created in the file you specify. The following example if for a server runningTeamcenter Rapid Start.

Example

%TC_ROOT%\bin>export_attr_mappings –file=c:\temp\attr.txt –u=myuserid –p=mypassword

–g=mygroup

The arguments used are:

–file=the mapping file being created locally

–u=userid for Teamcenter

–p=password for Teamcenter

–g=Teamcenter group

BOM diagnostic log fileUse the SEECDiagnostics_<timestamp>.csv log file to determine corrective actions when youexperience any of the following conditions:

• Assembly files with Teamcenter Virtual Components are present and theSEEC_Synchronize_VirtualComponents is False (0).

• Assemblies with duplicate Teamcenter virtual components exist where a Solid Edge virtualcomponent is also placed as a real occurrence.

• Results of BOM validation indicates a BOM mismatch.

• Duplicate BOM lines exist.

• There is a mismatch in quantity per occurrence.

• Files are missing.

The log contains the following columns and rows of information to assist you:


Troubleshooting


Header DescriptionIssue Describes the condition. For example, BOM Mismatch.Type Displays the item type of the object associated with the condition.Item ID Displays the Item ID of the object associated with the condition.Revision Displays the revision of the object associated with the condition.Item Revision Display Name Presents the Teamcenter displayed value of the object associated

with the condition.

Message Provides additional information about the condition and itsresolution.

The default location for log files is determined on the File Locations page of the Solid EdgeOptions dialog box.

Example

C:\Users\<username>\AppData\Roaming\Siemens\Solid Edge\Version 220\Log Files

A new SEECDiagnostics_<timestamp>.csv file is created for each session of Solid Edge andpersists until you delete it. Each file uses a naming convention consisting of a description, timestamp, and file extension. For example, SEECDiagnostics_20180514131232.csv. The time stampis a 14 digit unique identifier using the format YYYYMMDDHHmmss where:

• YYYY is the year. In the example, 2018.

• MM is the month. In the example, 05 is May.

• DD is the day. In the example, 14 is the 14th.

• HH is the hour using a 24-hour clock beginning at midnight which is 00 and going through 23,which is 11:00pm. In the example, 13 is 1:00pm.

• mm is the minute. In the example, 12 is 12 minutes past the hour.

• ss is the seconds. In the example, 32 is 32 seconds past the minute.

Work with your system administrator to develop a schedule to archive the contents of theC:\Users\<username>\AppData\Roaming\Siemens\Solid Edge\Version 220\Log Files folder.

Teamcenter rich client installationThe following table describes solutions to problems you may encounter during rich client installation.

Problem Possible cause Solution

TEM does not start, reports JREnot found.

JRE is not set in the systemenvironment.

Set the JRE_HOME orJRE64_HOME environmentvariable to specify the pathto the required Java RuntimeEnvironment (JRE).



Troubleshooting

Problem Possible cause Solution

FCC does not start on Windows Incorrect Internet Explorerbrowser setting

Ensure that scripting of Javaapplets is enabled. In InternetExplorer, select Tools→InternetOptions→Security→CustomLevel→Scripting of Java applets

Errors when uploading ordownloading files

FMS_HOME environmentvariable does not point to thelocation of the File ManagementSystem (FMS) client executable.

Uninstall, then reinstall the richclient.

Refer to Teamcenter documentation for additional information.

Item is the only Item Type availableFor each of the following preferences, define the list of Item Types used to manage the Solid EdgeDataset type displayed on the common property dialog boxes.

The default is Undefined which returns only Item as an Item type.

• SEEC_ItemTypeList_SE Part• SEEC_ItemTypeList_SE Assembly• SEEC_ItemTypeList_SE Draft• SEEC_ItemTypeList_SE SheetMetal• SEEC_ItemTypeList_SE Weldment• SEEC_ItemTypeList_SE Component• SEEC_ItemTypeList_SE Connection• SEEC_ItemTypeList_DirectModel• SEEC_ItemTypeList_Image• SEEC_ItemTypeList_MSExcel• SEEC_ItemTypeList_MSExcelX• SEEC_ItemTypeList_MSWord• SEEC_ItemTypeList_MSWordX• SEEC_ItemTypeList_PDF• SEEC_ItemTypeList_StructureEditor• SEEC_ItemTypeList_UGMASTER

Refer to the Solid Edge help topic Limit the list of available Item Types for specific instructions.

Refer to the Teamcenter Preferences portion of this guide for more information on each preference.

Duplicate Item IDsDuplicate Item IDs can occur when a BOM line is added using Structure Editor while the assembly issimultaneously open in Solid Edge Embedded Client. Only a single application on a single computershould load a product structure for modification. An assembly should be closed and uploaded beforeit is opened by another application.


Troubleshooting


BOM View Revision not created or updatedIn the event the BOM View Revision is not created or updated on your server, check to make sure theout-of-the box revision rules have not been edited. It is vital that revision rules are not changed fromtheir designed behavior. This is especially true for the revision rule, Latest Working.

Missing Property for Synchronous fileIn releases of Solid Edge Embedded Client prior to ST3, a property mapping to capture Model_Typemust be defined in Teamcenter for you to open and save Solid Edge Synchronous files in aTeamcenter-managed environment. If you are working with a version of Solid Edge prior to the ST3release, and the property is not mapped, you will see the error message:

If you encounter this error message while working with a pre-ST3 Solid Edge Synchronous file:

1. Save the Solid Edge Synchronous file to an unmanaged location.

2. Contact your Teamcenter administrator to add the Model_Type property to Teamcenter using theinstructions found in the Attribute mapping for Synchronous content portion of this guide.

3. Add the Solid Edge Synchronous file you saved to the unmanaged location to the documentlibrary using Add to Teamcenter.

Troubleshooting TeamcenterThe following information is provided to assist you with troubleshooting your Teamcenter installation.

Error Description Corrective Action

Document preview does notdisplay

Document selected from theOpen dialog box does not displaya document preview.

Verify FMS is installed andconfigured properly.

From a command prompt type:cd %FMS_HOME%\bin

fccstat —status

Unexpected http response – 100 Observed when working withlarge assemblies.

Increase the number of serversin the pool.

EJB Exception: nested exceptionis java.lang.OutOfMemoryError

Application server ran out ofmemory (J2EE only).

Increase application servermemory. Example: Xms 1024mand Xmx1024m



Troubleshooting

Login requested for <UserID> to<Description>

The user name, password, groupand role combination you usedis not valid.

Verify your cap lock key is not on.

Verify you correctly entered yourlogin.

Verify you entered a correctgroup.

Verify you entered a correct role.


FMS failed to start during%TC_ROOT%\fcc\fcc.xml

Verify environmentvariable FMS_HOME%FMS_HOME%\fcc.xml.

From a command prompt type%FMS_HOME%\bin\fccstat.exe

–status


Teamcenter returned 8004A0A0which SEEC does not recognizeas a known error. Review the logfiles for further information.

For 2-tier, verify you have accessto TC_DATA.

Partial Error on Checkin/Save Unable to save new content onTcE 2005SR1 MP8

For Teamcenter Engineering:

From a command prompt typeinstall —priv CICO infodba

[IMAN_USER_PASSWD] dba

For Teamcenter:

From a command prompt typeinstall_am_privilege [-h]

—u=<username> —p=<password>

—g=<groupname> —n=CICO


Troubleshooting

Chapter 12: Solid Edge Technical Support

The Global Customer Support & Success (GCS&S) team provides technical support for Solid Edgecustomers.

Contacting Support

In the USA and Canada, call 1-800-955-0000 or 1-714-952-5444. Outside North America, contactyour local Siemens PLM Software office. For more information or the telephone number of an officenear you, call 800-807-2200.

You can also access GCS&S on the Web:

https://www.plm.automation.siemens.com/global/en/support/.

For problems relating to Microsoft, contact Microsoft support on the Web:

http://support.microsoft.com


https://www.plm.automation.siemens.com/global/en/support/

http://support.microsoft.com

Appendix A: Solid Edge Embedded Client best practices

With any application, there are techniques that are considered to be recommended or bestpractices for accomplishing tasks. This portion of the document describes practices and processesrecommended to you.

Assembly best practicesOpening large, managed assembly documents can be time-consuming. The application spendstime running a query to determine the assembly structure based on the Teamcenter RevisionRule, checking versions, validating permissions, and transferring the files to your system. You canactively control how some of this time is spent to make working with large assembly documentson a day-to-day basis as efficient as possible.

Use Hide All Components to efficiently work with large assemblies

Depending on your circumstances, you might need to work with all of the files referenced by anassembly, or you might only need to work with a few of them.

When working with a portion of a large assembly, you can control how much of the assembly isdownloaded to cache by hiding the components you do not need.

Note

Solid Edge Draft requires the entire Assembly structure. This workflow is not supportedwhen you detail assemblies in the Draft environment.

You should open the assembly with all components hidden, and then use PathFinder to navigate,expand, and show only the components you need. Opening the assembly with all componentshidden, only the direct first-level children of the assembly being opened are downloaded to cache.

Read the PathFinder structure to decide which components you need next, and select the Expandcommand or click the + symbol to download the next level of the assembly to the cache as needed.Once you expand the levels of the assembly you want to work with, you can then show the partsand subassemblies with optimum performance.

If the entire subassembly branch is required, you can select Expand All, resulting in a downloadof all required documents.

1. Start Solid Edge with Teamcenter enabled.

2. From the Application menu, choose Open.

3. Select an assembly and from the Load Options pane, set Hide All to Yes.

4. Click Open and PathFinder displays the first level of the assembly.

SEECAdminGuide 2020 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators A-1


5. Right-click a subassembly, and then choose Expand on the shortcut menu.

The next level of that branch is downloaded to cache, enabling navigation at that level.

To open all of the components within a subassembly, click the Expand All command on itsshortcut menu.

When you have expanded the assembly structure, you can then show the components in themost efficient manner.

Use Version from Cache to optimize performance with large assemblies

When you know you need to work with all or most files in a large assembly, you should use theversions of files in your cache to optimize performance.

Solid Edge Embedded Client utilizes a local cache when working with managed Teamcenterdocuments. The performance cost of running a query to determine an assembly structure basedon the Teamcenter Revision Rule, checking the versions, validating permissions and transferringdocuments increase as the assembly size increases. When you work with the same data all dayand you know the information is up-to-date, you can improve performance by using the Solid EdgeRevision Rule Version from Cache. With this option, the version information is validated and thedocuments are checked out, but no file transfers take place. With Solid Edge Embedded Client, thecache is persistent between sessions. Using the data in the cache optimizes performance.


2. From the Application menu, choose Open and select the assembly.

3. In the Open Options pane, set the Revision Rule to Latest Working and click Open.

This will open the document and populate the cache for your working session.

4. In a subsequent working session, in the Open Options pane, set the Version from Cachecheck box.

All subassemblies will be configured to use what is already downloaded to cache, minimizingthe impact to performance.

5. Click Open.

Configure Teamcenter structure expansion

In the Teamcenter-managed environment, the Teamcenter preference SEEC_ExpandStructuredetermines how product structures are expanded. When you use simplified subassemblies, set thepreference value to 1 to expand product structures level-by-level. The simplified subassembly acts asa firewall and structure expansion stops at a subassembly that is simplified.

Use Auto-Select when opening simplified assemblies

When you want to work with large assemblies that contain simplified subassemblies, use theAuto-Select option on the Open dialog box to open the assembly.

The Auto-Select option evaluates the size of the assembly and determines whether it is small,medium, or large based on the ranges defined on the Assembly Open As page of the Solid Edge

A-2 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators SEECAdminGuide 2020


Solid Edge Embedded Client best practices

Options dialog box. If the assembly size is determined to be either small or medium, the entiredesign is downloaded to cache and the product structure is expanded to all levels. However, if theassembly size is determined to be large, the product structure is expanded level-by-level until itreaches a simplified subassembly. Product expansion stops at that point.

Cache Management best practicesTo optimize performance, documents from Teamcenter are downloaded once to the local machinewhen accessed and then only downloaded again if they are out-of-date. The local download area iscalled a cache.

Provide a private cache for each user

When you use Solid Edge with the Teamcenter Integration (SEEC), each user should have accessto an assigned computer and individual cache.

Caution

The location of the cache should be on the physical disk of the local machine. This is apersonal cache and must not be shared by multiple users.

However, when this is not possible, you can use shared computers which have individually assignedcache configurations. In this instance, you should set up private caches for each user in a networklocation that can be accessed from any work location.

The following steps describe the procedure for implementing a remote-mounted cache configuration:

1. Log on to the operating system of the computer.

2. Create a mapped network drive utilizing the method recommended by your specific operatingsystem.


4. Create a new part file and login to Teamcenter when prompted.

Tip

If Teamcenter is not enabled, ensure that Teamcenter is installed and licensed.

5. From the Application menu, choose Settings→Options and then click the File Locations tab onthe Solid Edge Options dialog box.

6. Select SEEC Cache and click Modify.

7. Browse to the mapped drive and select the cache root folder.

If this is the first time, this will result in the creation of an SEEC sub-folder.

8. Click OK to exit each dialog box.




Follow the process for each system to create the same mapped drive and set the SEEC cacheusing the File Locations tab.

Tip

If the mapped drive changes, you will need to reconfigure the mapped drive on eachcomputer that uses the remote-mounted cache configuration.

Manually clear cache before redefining cache location

The cache exists as a folder in the Windows file system where a copy of the files is kept. The cachelocation is predefined as C:\Users\<username>\AppData\Roaming\Siemens\Solid Edge\SEEC.

When you need to change the predefined location for cache, you should:

• Schedule the change at the beginning of a project.

• Use Cache Assistant to check in all files you want to keep in Teamcenter.

• Manually clear your cache using the Delete All button in the Cache Assistant.

Caution

Changing the predefined cache location removes the existing contents of the cache.


2. From the Application menu, choose Manage→Cache Assistant. Connect to Teamcenter ifprompted.

3. Evaluate the contents of the cache. Check in all items that are currently checked out. If youhave items checked out that you do not want in Teamcenter, use the shortcut menu optionCancel Check Out.

Tip

Repeat this process for each cache folder in the Project field of the Cache Assistantdialog box.

4. Click Delete All.

You are notified that deleting all projects from the cache will perform several tasks.

A-4 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators SEECAdminGuide 2020



5. Click OK, and then verify your intention to reset the cache by clicking Yes. Close the CacheAssistant dialog box.

6. From the Startup screen, under Create, open a new document in any environment.

7. From the Application menu, choose Solid Edge Options→File Locations.

8. Highlight the SEEC Cache entry and click Modify.

The Browse For Folder dialog box displays.

9. Define the new location for the cache.

Tip

It is recommended that the location of the cache be on the physical disk of the localmachine. This is a personal cache and must have exclusive permission for access.It is not to be shared with other users.

10. Click OK on the Browse For Folder dialog box and Reset Connections dialog box.

11. Click OK on the Options dialog box.

12. Close the document.



Appendix B: Data Preparation Utility commandline reference material

Analyze Solid Edge files using command line optionsSolid Edge file analysis can be performed from within the Data Preparation Utility or from thecommand line by typing \Program Files\Siemens\Solid Edge 2020\Program\DataPrepUtility.exe/viewproperties and applying the following options:

Example

DataPrepUtility.exe /viewproperties /tc /folder "D:\folder path" /Sort /ShowCSVFile/viewLog

Option Use Comments

/tc Prepare data forTeamcenter.

Choose /tc. If no option is specified, data isprepared for the unmanaged environment.

/folder <folder path> Specify the path ofthe folder to analyze.

By default, the option to analyze files from aspecified folder is selected and folder path isconsidered.

If <folder path> is the only argument specified,then /folder option is not necessary.

/DryrunXML <xmlfile>Analyze data fromAdd to Teamcenterdry run.

/DryrunCSV <csv/textfile>

Analyze data fromAdd to Teamcenterdry run output CSVfile path.

Specify either /DryrunXML or /DryrunCsvOrTextfollowed by the file path.

In the case of a conflicting parameter, theprogram uses the second parameter.

/BrokenLinkAnalysis Performs broken linkanalysis.

Applicable only if analyzing from a folder path.This option is ignored when used with otheroptions.

/CrawlLinks

Crawl links to builda complete list ofSolid Edge files to beimported.

Applicable only if analyzing from a folder path.

/SortSpecifies that youwant the Excelspreadsheet sorted.

SEECAdminGuide 2020 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators B-1

Appendix B: Data Preparation Utility command line reference material

Option Use Comments

/report <reportfile> Specifies the nameof the report file.

If name is not specified, the default report fileAnalyisOfSolidEdgefiles.txt is created in thefolder path specified with /folder option.

/ShowDialog Displays AnalyzeFiles dialog box.

Use this option when you want to see theAnalyze Files dialog box with all specified optionsselected. You must manually start the analysisby clicking OK in the dialog box.

/ShowCSVFile Opens output CSVfile.

/saveCSVfile <outputfile>

Saves output file in tothe specified location.

Provide full path with name where you want tosave the output CSV file.

If no file is specified, the file dataPrepUtility.xlsmis created in the folder path specified with /folderoption.

/viewreport Opens log file. Report file is opened when processingcompletes.

/?Displays help forcommand lineoptions.

Note

Any error messages encountered while processing display in the command window.

Fix broken links using command line optionsThe Fix Broken Links program repairs links in Solid Edge files before you import them into themanaged environment. The program locates the Excel spreadsheet produced from the file analysisprocess and defines the parameters used for repairing broken links.

Warning

Failure to repair broken links before proceeding with the data preparation and importprocess can result in an improperly populated database.

The Fix Broken Links program can be run from within the Data Preparation Utility or from thecommand line by typing DataPrepUtility.exe /FixBrokenLinks and applying the following options:

Note

The default location for the DataPrepUtility.exe program is \Program Files\Siemens\SolidEdge 2020\Program.

B-2 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators SEECAdminGuide 2020


Data Preparation Utility command line reference material

Example

DataPrepUtility.exe /FixBrokenLinks /File "D:\new folder\dataPrepUtility.xlsm" /sheet"BrokenLinks" /viewlog

Option Use Comments

/preST

Activates link fix-up forfiles created in versionsof Solid Edge prior toSolid Edge ST.

Applicable only for pre-Solid Edge ST link fix-up.

If used, this should be the first option specified.

/File<spreadsheetfile>

Specifies the Excelspreadsheet file to useas input.

Enclose the path in quotations.

Example: /File "D:\new folder\datapreputilities.xlsm"

/sheet<sheetname>

Specifies the sheetin the specifiedspreadsheet thatcontains thelink replacementinformation.

Applicable only for Solid Edge ST link fix-up.

/folder<folder path>

Specifies the foldercontaining Solid Edgefiles.

Applicable only for pre-Solid Edge ST link fix-up. You mustspecify either a folder path or report summary file.

/report <filepath>

Specifies reportsummary file.

Applicable only for pre-Solid Edge ST link fix-up. You mustspecify either a folder path or report summary file.

/chkPart Processes partdocuments. Applicable only for pre-Solid Edge ST link fix-up.

/chkAssy Processes assemblydocuments. Applicable only for pre-Solid Edge ST link fix-up.

/chkDraft Processes draftdocuments. Applicable only for pre-Solid Edge ST link fix-up.

/chkWeld Processes weldmentdocuments. Applicable only for pre-Solid Edge ST link fix-up.

/onlyfilename Excel Search based onfile name only. Applicable only for pre-Solid Edge ST link fix-up.

/fullpathname Excel Search based onfull path name. Excel Search based on file name only.

/ShowDialog Displays Link Fix-Updialog box.

Specify this option when you want to view the Link Fix-Updialog box with all specified options selected. You mustmanually start Link Fix-Up by clicking OK in the dialog box.

/? Displays help forcommand line options.

/viewlog Opens log file. Log file is opened once processing completes.

SEECAdminGuide 2020 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators B-3

Data Preparation Utility command line reference material


Modify Solid Edge files using command line optionsThe Modify program updates Solid Edge files based on entries in the analysis report spreadsheet.New property values are saved in the unmanaged Solid Edge files.

You can modify files using options in the Data Preparation Utility or from the command line by typingDataPrepUtility.exe /ModifyProperties and applying the following options:

Note

The default location for the DataPrepUtility.exe program is \Program Files\Siemens\SolidEdge 2020\Program.

Example

DataPrepUtility.exe /ModifyProperties /file "D:\new folder\dataPrepUtility.xlsm"/viewlog

Option Use/file<spreadsheetfile>

Specifies the path of the spreadsheet file used as input.

/ShowDialog

Displays the Modify Files dialog box.

Specify this option when you want to see the Modify Solid Edge Files dialog box.The dialog box is displayed with all specified options selected. You must manuallystart the process by clicking OK in the dialog box.

/? Displays help for command line options.

/viewlogOptions log file.

Log file is opened when processing completes.

B-4 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators SEECAdminGuide 2020


Appendix C: PDM Integration tool command linereference material

Run the PDM integration tool using command line optionsYou can run the PDM integration tool from the Start menu in Solid Edge or from the commandline. To run the tool from the command line, type \Program Files\Siemens\Solid Edge2020\Program\EdgePDM.exe with your choice of the following options:

Example

EdgePDM.exe -setPDMClient=2 -addPDMClientMenus=2

Option Use Values

setPDMClientDefines the PDMclient that is activewith Solid Edge.

1=Built-in document management

2=SEEC

addPDMClientMenusDefines the PDMclient Start menusentries.

1=ALL

2=SEEC

removePDMClientMenusRemoves the PDMclient Start menuentries.

1=ALL

2=SEEC

Note

The options, addPDMClientMenus and removePDMClientMenus support the use of acomma to separate multiple values. For example, addPDMClientMenus=1,2

SEECAdminGuide 2020 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators C-1

Appendix D: Teamcenter Preferences

The following tables provide information regarding Teamcenter preferences that impact theTeamcenter Integration for Solid Edge (SEEC).

Caution

Always export your preferences before running Teamcenter Environment Manager (TEM),then validate multi-line values.

appbar_title_contents

Description Specifies values to be displayed in the user session information on theSolid Edge startup screen and within the User Session Info docking pane.Each value must be on its own line.

Valid Values user

userid

group

role

site

curr_proj

prev_login_time

prev_session_ip

current_login_time

locationcode

change_notice

version

SEECAdminGuide 2020 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators D-1


Default Values (user(userid)-group/role-[site][curr_proj][locationcode])

ActiveWorkspaceHosting.SEEC.URL

Description Specifies the URL used by Solid Edge when hosting an ActiveWorkspace client. Solid Edge evaluates this preference beforeActiveWorkspaceHosting.URL.

Valid Values URL

Default Values <empty>

Scope Site

Comment If this preference is not defined, the value of ActiveWorkspaceHosting.URLis queried. When ActiveWorkspaceHosting.URL is not defined, hostedactive workspace is off (no docking pane displays).

AWC_SEEC_OpenSupportedTypes

Description Enables the specified object types to be opened in Solid Edge whenselected in Active Workspace. Only Item, Item Revision, subtypes of Itemand Item Revision and Solid Edge dataset types are supported.

Valid Values Only Item, Item Revision, subtypes of Item and Item Revision and SolidEdge dataset types are supported. Us ethe business object's real name.

Default Values Solid Edge dataset types

Scope Site

D-2 Teamcenter Integration for Solid Edge (SEEC) Guide for Users and Administrators SEECAdminGuide 2020


Teamcenter Preferences

Comment If this preference is not specified, the Active Workspace Client does notdisplay the Open in Solid Edge command. The Teamcenter Administratormust add the Item and Item Revision types they use to manage Solid Edgecontent. Add only the types used with Solid Edge.

SE Draft_DefaultChildProperties

Description Lists properties that can be used as children for the indicated type.Double-click in the Teamcenter rich client is expand.

Scope Role

SE Part_DefaultChildProperties

Description List of properties that can be used as children for the indicated type.

Scope System

SEEC_Asm_Weldment_Feature_Type

Description Creates a Solid Edge Assembly Weldment Feature with the TeamcenterItem Element Type you define, and attaches the corresponding geometryas JT. If this value is not defined, or it is not set to a valid TeamcenterItem Element type, the weldment features are not written to Teamcenter'sproduct structure.

Valid Values A single valid item element type.

Default Value Null

Scope Site

Comment

SEEC_ATT_Merge_BOM

Description Used with Add to Teamcenter to merge BOM entries in the case where theBOM was previously created by a different process.

Valid Values True, False

Default Value False

Scope All




SEEC_BOM_Precision_Override

Description Specifies the BOM precision used during the creation of a new Solid EdgeAssembly. Valid values are 0, 1, or 2. Set to 0 to use the same settingas Teamcenter Rich Client. Set to 1 to override to Imprecise. Set to 2 tooverride to Precise.

Valid Values 0, 1, or 2

Default Value 0

Scope Site, Group, Role, User

Comment The system default is to use the value defined by the Teamcenterpreference. If there are any issues parsing this new preference, you mustdefault to current behavior. Use current behavior if the new preferencehas a value that is empty or <null>.

SEEC_BOM_Synchronize

Description Synchronizes the Bill of Materials (BOM) in Teamcenter with the BOM inSolid Edge for Item Revisions that contain 3D content. This results in aSolid Edge assembly structure that is equivalent to the BOM in Teamcenter.

Set BOM synchronization to true if part of your workflow is to create ormodify product structures in an application other than Solid Edge. Forexample, when you modify the structure in Teamcenter Structure Manageror Solid Edge Structure Editor and add or remove Item Revisions that mayor may not contain Solid Edge models.

Set BOM synchronization to false if Solid Edge is the only application youuse to create or modify product structures.

When BOM synchronization is set to false and Item Revisions with no SolidEdge models are added to the structure with another application, SolidEdge synchronizes the structure creating Teamcenter virtual components.

Valid Values False, True

Default Value False

Scope Site




SEEC_CreateFormType_SE Draft

Description Creates a single Form and attaches it to the SE Draft Dataset during New,Revise, and Save As. The operation must be executed from Solid Edge,the Form Type must exist, and both the Form Type Name and Relationare required in the syntax.

Syntax <Form Type Name>:<Relation>

Default Value Null

Scope Site

SEEC_Date_Format

Description Specifies the date format recorded in Teamcenter and used by the Searchcommand in SEEC. The value is %d-%b-%Y where %d is day, %b is month,%Y is year.

Note

If you do not specify this option, or its value is blank, the defaultdate format (English) is used.

Scope Site

SEEC_Default_Item_Type

Description Specifies the default Item type for each document type saved toTeamcenter. The value specified on the first row defines the default Itemtype for 3D documents. The value specified on the second row defines thedefault Item type for draft documents. Specify exceptions to the default3D Item type by setting the document type equal to its Item type. If alldocument types are explicitly defined, the first two rows are ignored. If Itemis used after rows one and two, it is ignored.

Note

Add to Teamcenter uses this preference during import when adocument has no custom property that defines the Item type.




Valid Values Document type= Real Item type name as seen in BMIDE

Example

Item

Item

asm=Design

par=custom_item_type1

psm=custom_item_type2

pwd=Item

dft=Drawing

Default Value Item

Item

Scope User

Comment Item type syntax is case-sensitive.

If an Item type is defined more than once, only the first occurrence is used.

SEEC_Default_View_Type

Description Site preference that specifies the default BOM View Revision type tobe used by SEEC. The BOM View Revision type must be defined inTeamcenter. If not defined, the default BOM View Revision view is used.

For Teamcenter product structure expansions, this preference must havea scope of site.




SEEC_Diagnostics_BOMDuplicateIDs

Description Checks and optionally removes duplicate Solid Edge Assembly occurrenceIDs found in the Teamcenter BOM.

Valid Values 0 = Disable logging.

1 = Enable logging.

2 = Enable logging and remove duplicate occurrences.

Default Value 0 = Logging disabled.


Comment Delivered with SEEC Feature Template

SEEC_Diagnostics_BOMValidation

Description Checks for BOM mismatches when a Solid Edge Assembly is opened oruploaded. Set to 1 to enable BOM validations.

Valid Values True (1), False (0)

Default Value False (0)



SEEC_Draft_GRM_Rule

Description Determines the maximum number of Solid Edge Draft datasets that can beattached to the revision. A value of -1 indicates no limit.

Valid Values -1 or a positive integer

Default Value -1

Scope Site

Comment The value for this preference should be equal to the value defined in BMIDEfor GRM Rule for SE Draft.




SEEC_DrivenReference_DoNotCopy_Revise

Description Provides for an override of deep copy rules. Specifies a list of dataset typesthat should not be copied to a new revision. This preference is specific toTake Ownership workflow and design reuse of geometry using multi-CAD.

Valid Values Real property names. For example: UGMASTER, UGPART, ProPart,ProASM, MSWordX

Default Value <empty>

Scope All

Comment Any files created prior to a change in the preference value do not follow thenew value.

Preference value is case sensitive.

SEEC_DrivenReference_DoNotCopy_SaveAs

Description Provides for an override of deep copy rules. Specifies a list of dataset typesthat should not be copied to a new revision. This preference is specific toTake Ownership workflow and design reuse of geometry using multi-CAD.

Valid Values Real property names. For example: UGMASTER, UGPART, ProPart,ProASM, MSWordX


Scope All

Comment Any files created prior to a change in the preference value do not follow thenew value.

Preference value is case sensitive.




SEEC_Enable_AssemblyConstructions

Description Determines if an assembly occurrence marked as a construction is addedto the Teamcenter BOM View Revision. When all occurrences are markedas constructions, the Item Revision is connected to the assembly using arelation.

Valid Values False (0), True (1)


Scope Site

Comment Default value retains ST8 behavior.

SEEC_Enable_CreatePackage

Description When set to 1 (True), adds Create Package command to the Solid EdgeCache Assistant toolbar. Default is 0 (False).

Valid Values 1 (True), 0 (False)

Default Value 0 (False)





SEEC_Enable_MultipleRevisions

Description When set to 1 (True), Solid Edge works with multiple revisions in a singleSolid Edge session. Default is 0 (False).


Default Value 0 (False)


Comment To compare two revisions of the same document using 3D Compare, thispreference must be set to True.

SEEC_Enable_WorkOffline

Description Enables the display of the Work Offline command. When set to 1, theWorking Mode group is added to the Solid Edge Cache Assistant toolbar.When set to 0, the group is not displayed. Default is 1.


Default Value 1 (True)

Scope Role

Comment The Teamcenter Administrator should set this value to 0 (False) to removethe command from the toolbar of a select group of users.




SEEC_ExpandStructure

Description Determines how product structures are expanded. Enter 0 to expand alllevels. Enter 1 to expand the structure level-by-level.

Structure Editor uses an additional parameter when assembly documentsare opened. The value of <Count> defines the unique component countfor large assemblies. When the assembly’s unique component count isgreater than the value of <Count>, the assembly is considered large, andthe document is expanded level-by-level.

Note

This preference is of value only if you are opening assemblieswith simplified subassemblies.

Syntax <Value>space<Count>

Example: 1 10,000

Valid Values 0 or 1

Default Value 0

Scope All




SEEC_Foreign_Datasets

Description Specifies the non-Solid Edge dataset types to use when a Solid Edge 3Ddataset is not saved to the Item Revision. This is a multi-line preference.The first line determines whether the functionality is disabled or enabled.The subsequent lines contain the definition.

DatasetType=”DirectModel” NamedReference=”JTPART”

NamedReferenceFormat=”BINARY” NamedReferenceTemplate=”jt”

Note

Only JT is supported at this time.



Scope All


SEEC_Image_Generate_3D

Description Generates the JT file for Solid Edge part (.par), sheet metal (.psm) andlegacy weldments (.pwd).

Geometry that is created in an assembly in the context of a feature isgoverned by the preference SEEC_Image_Generate_Asm_3D.


Default Value True (1)

Scope Site

SEEC_Image_Generate_Asm_3D

Description Generates the JT override files for geometry that is created in an assemblyin the context of a feature, such as assembly features, frame/pipe, andadjustable parts. Both the preference SEEC_Image_Generate_3D andSEEC_Image_Generate_Asm_3D must be set to True.



Scope Site




SEEC_Image_Generate_Assembly

Description Defines the options for generating an image file of type JPG for Solid Edgeassemblies. This image file is then checked into Teamcenter as part ofthe assembly dataset. This preference enables you to view the assemblyfrom the rich client without having to open it in Structure Manager (formerlyProduct Structure Editor). Scope=Site

Note

This is a multi-line preference. The first line of the preferencedefinition must contain either True or False. The remaining linesof the preference definition can be in any order. See the Enablingimage file generation portion of this chapter for details.

SEEC_Image_Generate_Assembly_ModelViews

Description Determines whether model views are extracted from assemblies and loadedinto Teamcenter as non-body JTs.

Valid Values 0-False

1-True

Default Value 1-True

Scope Site




SEEC_Image_Generate_Draft

Description Generate an Image file of type: EMF, BMP, TIF, JPG or DXF; None if one isnot required. This image file is then checked in as a Named Reference toSE Draft Dataset and intended to be rendered by Embedded Visualization.

Default Value None

Scope Role

SEEC_Image_Generate_PDF_for_Draft

Description Generate a PDF for each Draft and attach it to the Item Revision as aseparate Dataset. This PDF would be the 2D neutral file and would includeall draft sheets. This file could then be used by Portal Visualization forMarkup and Reviews.

Default Value True

Scope Role

Comment This preference is superceded when SEEC_Save_Translation is definedfor PDF.

SEEC_Item_Type_DisplayableName

Description Captures the Item Type’s display name. Determines whether to write thereal name or displayable name when the Item Type name is written toSolid Edge. The preference TC_display_real_prop_names controls thepresentation of real property name or displayable name for other objects.

For a new implementation of Solid Edge Embedded Client, setting thepreference to 1 is recommended so the displayable name is written toSolid Edge.

Valid Values 0=Real Name. 1=Displayable Name

Default Value 0

Scope Site





SEEC_Item_Type_Sort

Description Determines the order in which item types are listed in common propertydialog boxes. Set to 0 to use the order defined by each SEEC_ItemTypepreference. Set to 1 to build a hierarchical and sorted list. Default is 1.




SEEC_ItemTypeList_ExcludedTypes

Description Item types listed in this preference are removed from the list of availableitem types when saving a new document to Teamcenter.

Valid Values Real Item type name

Default Value Default values in this list are based on what is delivered by Teamcenter andwhich are expected to be used with Solid Edge. For the current list, reviewthe preference in Teamcenter.


Comment This preference must be accounted for by the Teamcenter administrator.

SEEC_ItemTypeList_SE Assembly

Description List of available Item Types for specified Dataset Type. This list drives theCommon Property Dialog, CPD. Requires real Item Type Names.

Default Value Undefined

Comment A single value of Undefined provides Item as the only Item Type.

SEEC_ItemTypeList_SE Component







SEEC_ItemTypeList_SE Connection




SEEC_ItemTypeList_SE Draft




SEEC_ItemTypeList_SE Part




SEEC_ItemTypeList_SE SheetMetal




SEEC_ItemTypeList_SE Weldment







SEEC_ItemTypeList_StructureEditor

Description List of available Item Types for use by Structure Editor. Edit this preferenceto include only the item types needed.


Scope All


A single value of Undefined provides Item as the only Item Type.

SEEC_JT_Priority_Refsets

Description Determines the reference set load order for a DirectModel dataset in aSolid Edge multi-CAD workflow. Enter one reference set name per linein priority order.

Valid Values MODEL

Entire Part

Default Value MODEL, Entire Part

Scope All

SEEC_MakeReadOnly_ItemID

Description Assigning a value of True sets the Item ID to read-only and the user mustuse the Assign or Assign All command to obtain the value from Teamcenter.

Scope Site

Type String

Valid Values True or False

Default Value False




SEEC_MakeReadOnly_Revision

Description Assigning a value of True sets the Revision to read-only and the user mustuse the Assign or Assign All command to obtain the value from Teamcenter.

Scope Site

Type String

Valid Values True or False

Default Value False

SEEC_Object_Images

Description Specifies a Zip Dataset UID containing customized icons used to displaythe status of documents within Teamcenter workflows (for example, inPathFinder, Read-Only Assistant, Cache Assistant, Open File dialog boxand File Properties dialog box), or workspace object images. To define thecustomization, pair the real object name with the associated image (.png)one per line.

Scope Site

Valid Values The first line must contain a case-sensitive Dataset UID. Each additionalline must contain the pairing of the real object name to the filename of thecustom .png image.

Example

DatasetUID=wCMAAAmRofPWZA

Mse1_Dev=Mse1mse1Dev1.png

Mse2_Test=Mse2mse2Test2.png

Released=custom_released.png

Obsolete=custom_obsolete.png

Design=Design.png

Folder=Folder.png

Default Value DatasetUID=

Comment If the preference is not defined or DatasetUID is empty, default icons areused.

Image format must be PNG and 16x16 pixels to properly display inPathFinder.




SEEC_PDF_Dataset_Type

Description Prerequisite: SEEC_Image_Generate_PDF_for_Draft = TRUE.

Defines the dataset type and the reference used to attache the file to thedataset for the active drawing. This does not define how you connect thedataset to the Item Revision.

Syntax Dataset Type:Reference

Scope Site

Example PDF:PDF_Reference

Comment If the preference does not exist, the system continues to use DatasetType=PDF and Reference=PDF_Reference

SEEC_Property_AssemblyFamilyMember_Name

Description Specifies the pattern used to generate the initial value of the Item Namewhen a new Family of Assembly member is published.

Scope Role

Valid Values 0=Initial value is empty. Use Assign All to define the Item Name or pickfrom a list of values.

1=Member Name is equal to <Master's Item Name>

2=Member Name is equal to <Master's Item Name>-<Solid Edge MemberName>

3=Member Name is equal to <Master's ID>-<Solid Edge Member Name>

Default Value 2

Comment The Teamcenter preference, FLColumnCatObjSeparatorPref can be used todefine the character that separates the Master and Member information.




SEEC_Property_AssignToProject_Name

Description Defines a list of assigned projects. This list displays on the commonproperty dialog boxes.

Note

The custom property will only be used to get projects from filesduring Add to Teamcenter or while adding unmanaged content.

Scope Site

SEEC_Property_ClearValue

Description Defines a list of properties whose values are emptied or made null when thedocument is copied using Save As or Revise. To define the preference, adda row for each property and include: type of operation, Item type, documenttype and the Solid Edge property name. Optionally, you can determine ifyou would like an empty or null value sent to Teamcenter. Separate eachoption with a colon.

Syntax <Operation>:<Item Type>:<Document Type>:<PropertyName>:<SendEmpty?>

Valid ValuesOperation

0=No operation (comments out the row)

1=Revise and Save As

2=Revise

3=Save As

Item type

Real Item type name

Document type

par=part

asm=assembly

dft=draft

psm=sheet metal

pwd=weldment




doc=Microsoft Word documents

xls=Microsoft Excel documents

All=all supported document types

Property Name

Solid Edge property name

SendEmpty?

0=No, do not send an empty or null value to Teamcenter.

1=Yes, send an empty or null value to Teamcenter. (Default)

Example <Operation>:<Item Type>:<Document Type>:<PropertyName>:<SendEmpty?>

1:Item:All:Title

1:Item:All:Title:1

1:Item:dft:MyDatasetCreateDate:0

2:Item:dft:MyDatasetReleaseDate:0

3:Item:dft:MyDatasetOriginationDate:0

Default Value <Empty>

Scope Site

Comment Use an English property name for Standard properties (Title, Subject,Project,Name, and so on).

The use of only the property name (for example, Type) applies to Save Asand Revise for all Item Types and all Document Types.

You can use the syntax <Property Name>:<SendEmpty?> when you onlywant to determine whether the empty value goes to Teamcenter.




SEEC_Property_Dataset_Description

Description Solid Edge Custom Property for Dataset Description displayed in English.Do not define for default behavior. The preference supports multiple values.

SEEC_Property_DatasetName

Description Defines the Solid Edge property used to synchronize Dataset Name. Whenthe value is defined as a Standard Property, the preference must be set inEnglish. If a custom property is used, include the property name in thepreference.

Scope Site

Comment Do not define for default behavior.

SEEC_Property_Item_Name

Description Specifies the Solid Edge property name that defines the Item Name. Thepreference supports multiple values. The first value indicates the Solid Edgeproperty to be used (example, Title) and the remaining values define optionssuch as /write_once and /description. The Solid Edge property name is inEnglish, however Solid Edge manages displays the appropriate resourcebased on the localized version of Solid Edge.

Note

If the SEEC_Property_Item_Name is <null>, missing, orincorrectly defined, the Item Name is mapped to Project Name.

Default Value Project Name

SEEC_Property_Item_Type

Description Solid Edge Custom Property for Item Type displayed in English. Do notdefine for default behavior.




SEEC_Property_Mapping_AsmOcc

Description Pairs a Solid Edge custom occurrence property name to a TeamcenterNote type name. The custom occurrence property name is defined in…\Preferences\CustomOccurrenceProperty.xml and Note type name isdefined in your BMIDE project.

Set the SEEC_Property_Synchronize_AsmOcc preference to True, so thatcustom occurrence property values are written to the corresponing Notetype for that BOM line. Use the real name for the Note type.

Valid Value <Solid Edge custom occurrence property name>: <Teamcenter real Notetype name>

Example:

Notes:SE99NOTES

Reference ID:SE99REFID

Defalut Value <Empty>

Scope Role

Dependentpreference SEEC_Property_Synchronize_AsmOcc




SEEC_Property_Physical_Units

Description Defines the units when saving physical properties of Part or Sheet Metaldocuments to Teamcenter and the attribute is defined as a number. Defaultis MKS (meter, kilogram, second).

Scope Site

Valid Values MKS | MMKS | CGS | IPS | FPS

Length=m

Mass=kg

Area=M^2

Volume=m^3

Density=kg/m^3

Default Value MKS

Comment If the preference is not defined or is in error, the default is MKS. Legacycontent is not changed until it is opened, physical properties are recomputed,the document is subsequently saved, and checked in to Teamcenter.

SEEC_Property_Synchronize

Description Enables document property synchronization when a linked documentis downloaded to local user cache. If a linked document is in the localuser cache and cache status is up-to-date, property synchronization isdetermined by the preference SEEC_Property_Synchronize_FullCache.The selected document for open or download is always synchronizedregardless of this setting.

Scope User

Default Value True

Related preference SEEC_Property_Synchronize_FullCache




SEEC_Property_Synchronize_AsmOcc

Description Controls assembly occurrence property synchronization. When True, SolidEdge assembly occurrence properties are written to the Teamcenter productstructure to the predefined Note types delivered by the SEEC Featurepackage.

To extend this functionality to include custom occurrence properties, definethe corresponding Note types in the SEEC_Property_Mapping_AsmOccpreference.

Valid Values 0=False, 1=True

Default Value False

Scope Role

Related preference SEEC_Property_Mapping_AsmOcc

SEEC_Property_Synchronize_FullCache

Description Enables document property synchronization for linked documents alreadyin local user cache where cache status is up-to-date. This preferenceis dependent upon SEEC_Property_Synchronize equal to TRUE. Theselected document for open or download is always synchronized regardlessof this setting.

Default Value True

Related preference SEEC_Property_Synchronize




SEEC_Property_Sync_PDM_Master

Description Enables document property synchronization during the save to Teamcenterprocess. This should only be set to TRUE if you have attribute mappingswhere the master is Teamcenter and the properties change when theTeamcenter object is created or modified.

Default value True

SEEC_Revision_MaxWorkRev

Description Determines the maximum number of working revisions. Thevalue should be equal to the value defined in BMIDE forMaxAllowedWorkRevsForItemCopyRev.

A preference value of –1 indicates no limit.

A preference value of 0 indicates the Item Type cannot be revised.

A positive integer value indicates the number of working revisions permitted.

Valid Values -1, 0, or any positive integer.

Default Value -1

Scope Site

SEEC_SaveAs_New_ItemType_SESE

Description Enables the capability to use Save As to save to a new Item Type in SolidEdge Structure Editor.


Default Value False

Scope Site




SEEC_Save_Translation

Description Defines the behavior for managing translated files. Add a row for eachspecific translation file type.

Syntax <Action>:<Export Type>:<Relation>:<Dataset Type>:<Reference>:<IncludeRevision in Name?>:<User specified identifier>

Separate each option with a colon.

Valid ValuesAction

0=Disables the entry for translation and leaves the definition forextraction filters

1=Enables the option for translation.

2=Enables automatic translation of flat patterns in Part or Sheet Metalfiles when a flat pattern is present (DXF only).

Note

This option is not supported with Add to Teamcenter or Addto Teamcenter-Interactive.

3=Enables automatic translation of Draft files (DXF, DWG, and PDFonly).

Export Type

Specify file type using the extension:

X_T, X_B

SAT

XGL

IFC

iges, igs

step, stp

3MF

STL

XML (plmxml)

U3D

PDF

3DPDF




DWG

DXF

All image formats (Example: png, jpg)

Relation

IMAN_manifestation

Allows attachment of a Dataset to an Item Revision that has status.

IMAN_specification

Others as defined by BMIDE

Dataset Type

The container for files and forms as defined in rich client. For example,Image, 3DImage, DXF, PDF.

Reference

Associates the file with the Dataset as defined in rich client.

Tip

To see a list of available Datasets and references, createa file on disk and then drag the file onto the item revisionin the rich client.

Include Revision in name?

0=No, do not append revision. (Example: 000100_par.x_t)

1=Yes, append revision. (Example: 000100_A_par.x_t)

User specified identifier (optional)

:stringvalue

Example <Action>:<Export Type>:<Relation>:<Dataset Type>:<Reference>:<IncludeRevision in Name?>:<User specified identifier>

1:stp:IMAN_manifestation:Image:image:1:STP_File00100_A_PAR_STP_File.stp

0:stp:IMAN_manifestation:Image:image:1:STP_FileTranslation disabled

2:dxf:IMAN_specification:DXF:DXF:0:Flat_Pattern00100_PSM_Flat_Pattern.dxf




Default Value 0:stp:IMAN_Manifestation:Image:image

0:dxf:IMAN_Manifestation:Image:image:1:CustomString

0:dwg:IMAN_Manifestation:Image:image:0:CustomString

0:x_t:IMAN_Manifestation:Image:image

Scope Role

Comment Teamcenter relations, dataset types, and reference are case sensitive.

Multiple entries allow multiple datasets.

Setting this preference for automatic generation of PDF supersedesSEEC_Image_Generate_PDF_for_Draft and SEEC_PDF_Dataset_Type.

SEEC_Search_Limit

Description Determines the number of objects that are returned as a result of a search.When the objects found exceed the number specified, you are prompted toshow the results equal to the number defined in the preference, return allresults, modify the search criteria, or cancel the search. A positive integer isaccepted as the value.

Default Value 30

SEEC_Search_NamedQueries

Description Defines the named searches available in Advanced Search. Enter onenamed search per line. The default value, All, displays all the namedsearches returned by Teamcenter. If the preference is missing or determinedto be in error, all named queries are shown.

Scope User

Valid Values All predefined named queries

Default Value All


SEEC_Search_SearchQueries

Description Defines the list of queries available in the Search pane. Enter one namedquery per line. The query must have only one defined criteria. A defaultlist of queries is delivered by SEEC.

Scope User




Valid Values Each line must contain a single query name. That query implements a singlecriteria, where the criteria accepts a user defined string. There is no supportfor a list of values. Solid Edge delivers localized display names for thepredefined named queries. For custom queries, the display name is shownin the control. Queries are displayed in the order defined in the preference

Default Value _SEEC_STD_SIMPLE_ITEM_QUERY

_SEEC_STD_SIMPLE_ITEMNAME_QUERY

_SEEC_STD_SIMPLE_ITEMDESC_QUERY

SEEC_StandardParts_SAC

Description Defines the fully qualified path to the Solid Edge Standard Partsconfiguration file (.sac).

Scope Role

Valid Value Fully qualified path to the Standard Parts SAC file (.sac).


Comment This location was previously defined in the Define Teamcenter Databasesutility.

SEEC_Status_Working

Description Defines the string written to Solid Edge properties when there is noTeamcenter Status. When a new file is created in Solid Edge and theTeamcenter Status property is mapped to a Solid Edge custom property,the custom property is created and the value is the value of this preference.The status is obtained from the dataset, however, another option is theItem Revision.

SEEC_Synchronize_ItemNumbers

Description Enables the integration of Solid Edge Assembly Item Numbers withTeamcenter Find Numbers. This preference controls the Item Numberoptions. View the settings on the Solid Edge Options - Item Numbers page.

Valid Values /Method=1-4

Default Values /Method=1

/Master=Both

Determines the application responsible for item number generation. When/Master=Both, item numbers are generated in the application that creates thenew occurrence. When /Master=Teamcenter, items numbers are generatedin Teamcenter.




/Method=1

Maintain Item Numbers, Top Level Only.

/Method=2

Maintain Item Numbers, Atomic - top down

/Method=3

Maintain Item Numbers, Exploded - top down

/Method=4

Maintain Item Numbers, Use level based numbers

/ExpandWeldment=0

Do not expand weldments.

/Start=10

Start item numbers with 10.

/Increment=10

Increment item number by 10.

/UniqueBasedOnCutLength=1

Create unique item numbers based on cut length.

/UniqueBasedOnMass=0

Do not create unique item numbers based on mass.

/UniqueBasedOnMiter=0

Create unique item numbers based on miter.

/AtT=1 (Default)

Save Solid Edge Item Numbers to Teamcenter.

Scope Role

Comment Delivered with SEEC Feature Template. The first instance of each option isused. Subsequent entries are ignored.




SEEC_Synchronize_VirtualComponents

Description When set to True (1), adds Item Revisions with no Solid Edge datasets tothe Solid Edge Assembly as virtual components.



Scope Site, Group, Role


SEEC_TakeOwnership_Limit

Description Determines the number of objects that can be selected for a singlemulti-CAD Take Ownership transaction.

Default Value 10

Scope All


SEEC_TcClient_Enable_Open_Cmd

Description Enables or disables the Open in Solid Edge command in Teamcenter richclient 10.1.4, 11.2 or higher.

Valid Values 0=False-command is disabled

1=True-command is enabled

Default Value 1

Scope User





SEEC_Template_Folder_Name

Description Defines the Teamcenter folder name containing the Solid Edge templates.There is no requirment to attach this folder to Home(UserID). A query isused to find the folder using the folder name and the UserID defined by thepreference SEEC_Template_Username.

Valid Values String

Default Value Solid Edge Templates

Scope User

Comment The folder name must be unique.

SEEC_Template_Username

Description Defines the Teamcenter User ID that owns the folder defined by thepreference SEEC_Template_Folder_Name.

Valid Values Valid UserID of type String

Default Value infodba

Scope User




SEEC_UOM_List_as_Geometric

Description Lists the unit of measure values that represent geometric components.This preference is dependent on mapping between Solid Edge par or psmdocuments and unit of measure. When configured, unit of measure isprocessed during BOM synchronization. The preference is delivered with novalues and is hard-coded with the default of each, ea, or “ “.

Note

The default values are always processed. The Administratorcan add each unit of measure value, one per line. An Item withan empty of <Null> unit of measure is considered a geometriccomponent.

Valid Values each, ea or <Null>

Default Value empty

Scope Site


SEEC_UOM_Name_or_Symbol

Description Defines the property value written to the Solid Edge document when Unitof Measure (UOM) is mapped to Solid Edge. The valid value is either thename or symbol.

Note

If the property does not exist or does not contain a valid value,the Name is used.

Valid Values 0 Name, 1 Symbol

Default Value 0

Scope Site




FLColumnCatIVFSeparatorPref

Description Specifies the character used to separate the ItemID from the Item Revision.

FLColumnCatObjSeparatorPref

Description Specifies the character used in the Object column to separate the ItemIDand the Item Revision from the Item Name.

GeolusServer

Description Specifies the URL for the Geolus server when you use Shape Search withTeamcenter.

Default Value null

Scope Site

LOV_hide_desc

Description Determines whether side-by-side List of Values value/descriptions display.By default, Lists of Values are configured to display the value alongside itsdescription in the user interface. Use this preference to specify specific Listsof Values whose descriptions you do not want to display.

Scope User

LOV_user_id_display

Description Integer value that specifies how the User ID is displayed within a List ofValues.

Valid Values 0 = Person name

Default Value 0

Scope User




LOV_value_desc_seperator

Description Defines the character used to separate LOV values from their descriptions.Siemens PLM Software recommends using one of the following characters:dash (-), at sign (@), pound sign (#), or ampersand (&).

Default Value ,

Scope User

PS_new_seqno_mode

Description Determines how new find numbers are allocated when items are insertedinto a BOM view or BOM view revision. Find numbers are computed inthe context of the immediate parent.

Valid Values New, Existing, None

New

Causes the behavior of Sequence Number, not Item Number. Every item isgiven a new find number within the current BOM view, starting with 10, andincrementing by 10.

Existing

If an item of the same ID already exists in the BOM view, the inserted item isgiven the same find number. If not, the item is given a new find number asabove. Recommended value for synchronizing Solid Edge Item Numberswith Teamcenter Find Numbers.

None

No find number is allocated to items inserted into a BOM view; users canadd their own later.

Default Value New

Scope Site

SS1_DASS_enable

Description Enables the Shape Search application in the Active Workspace client(AWC).


Default Value False

Scope Site




TC_Allow_Longer_ID_Name

Description Used to enable the 128 character length for Item ID and Name attributes.

TC_BOM_Precision_Preference

Description Specifies the BOM precision to be used during the creation of newBOMViews/BOM View Revisions.

TC_config_rule_name

Description Defines the default revision rule used when opening Imprecise BOMView orBOMViewRevisions.

TC_display_real_prop_names

Description Determines the presentation of the real property name or displayable(display) name in Solid Edge user interface.

Scope All

Comment Delivered by Teamcenter and controlled in rich client options

TC_truncate_file_name

Description Preference used by Teamcenter Unified Architecture to decide if truncationof original file name is necessary.

WsoInsertNoSelectionsPref

Description Defines the behavior when an Item is saved to Teamcenter with no folderdefined. The item can be placed in Teamcenter and referenced by the(1)Newstuff folder, the (2)root folder, or (3)none. In the case where noneis selected, the Item is placed in the database with no references to it. Bydefault the item is saved to the (1)Newstuff folder.



Siemens Industry Software

HeadquartersGranite Park One5800 Granite ParkwaySuite 600Plano, TX 75024USA+1 972 987 3000

AmericasGranite Park One5800 Granite ParkwaySuite 600Plano, TX 75024USA+1 314 264 8499

EuropeStephenson HouseSir William Siemens SquareFrimley, CamberleySurrey, GU16 8QD+44 (0) 1276 413200

Asia-PacificSuites 4301-4302, 43/FAIA Kowloon Tower, Landmark East100 How Ming StreetKwun Tong, KowloonHong Kong+852 2230 3308

About Siemens PLM Software

Siemens PLM Software, a business unit of the SiemensIndustry Automation Division, is a leading global providerof product lifecycle management (PLM) software andservices with 7 million licensed seats and 71,000 customersworldwide. Headquartered in Plano, Texas, SiemensPLM Software works collaboratively with companiesto deliver open solutions that help them turn moreideas into successful products. For more informationon Siemens PLM Software products and services, visitwww.siemens.com/plm.

© 2019 Siemens Product Lifecycle ManagementSoftware Inc. Siemens and the Siemens logo areregistered trademarks of Siemens AG. D-Cubed,Femap, Geolus, GO PLM, I-deas, Insight, JT, NX,Parasolid, Solid Edge, Teamcenter, Tecnomatix andVelocity Series are trademarks or registered trademarksof Siemens Product Lifecycle Management SoftwareInc. or its subsidiaries in the United States and in othercountries. All other trademarks, registered trademarksor service marks belong to their respective holders.