SIEMENS

What's new in
Teamcenter 12
whats_new • 12
Contents

What's new in Teamcenter 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Version updates for JT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Support for ULP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Teamcenter Rapid Start data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Teamcenter supports Oracle container databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
How you can help make Teamcenter better . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Administering Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Strengthen security through centralized key management . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Sharing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Improved Multi-Site Collaboration performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Teamcenter Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Use Eclipse 4.6 for rich client customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

whats_new 12 What's new in Teamcenter 12 3

Chapter 1: What's new in Teamcenter 12

Lifecycle Visualization

Version updates for JT

Teamcenter 12 lifecycle visualization provides support for the following improvements to the JT format:
• JT 10.3 includes XT segments containing facet B-REP data.

• JT 10.4 includes ULP2 and per-face-group attributes.

Support for ULP2

ULP is a geometry component in JT designed to have a small file size and good data accuracy. The
first generation ULP was introduced in JT v9.0. The second generation ULP (ULP2) is introduced in
JT v10.4. ULP2 supports dynamic level of detail (LOD) ability.
Teamcenter 12 lifecycle visualization supports ULP2, except for the following features:
• Export of JT files containing ULP2

Note
This applies to all file format types except .plmxml.
Also, the export of non-ULP2 files to ULP2 is not supported.

• Modification of materials (Concept/Appearance) for ULP2 JT files

• Visual reports

• Part edit

• Surface analysis

• True shading

Teamcenter Rapid Start

Teamcenter Rapid Start data model

Teamcenter Rapid Start now has a new data model that is aligned with the Teamcenter data model.

whats_new 12 What's new in Teamcenter 12 1-1

 Chapter
Chapter 1: 1: What's
What's new
new in in Teamcenter
Teamcenter 12 12

All the instances of TCX_IMaster and TCX_IRMaster, except standalone instances, will undergo
data migration when you upgrade to Teamcenter Rapid Start 12.0. The data migration process is
inbuilt in the standard upgrade process. There is no manual intervention required.

Template migration

Before upgrading, you must migrate all the custom templates dependent on the tcx template to the
new version. You can do this through the standalone BMIDE.

Multisite collaboration

As the data models are now aligned, multisite collaboration between Teamcenter Rapid Start and
Teamcenter site for OOTB objects is possible.

Note
• Teamcenter deployments not involving the tcx template are not impacted.

• If indexing is configured based on form storage class properties, you must index the
data after the upgrade.

• Multisite collaboration for OOTB objects between Teamcenter Rapid Start 12.x, and
any version of Teamcenter or Teamcenter Rapid Start prior to 12.x, is not possible.

Installing

Teamcenter supports Oracle container databases

Teamcenter supports Oracle's multitenant database architecture if you use Oracle 12c or later. A
multitenant architecture is deployed as a Container Database (CDB) with one or more Pluggable
Databases (PDB).
A Container Database (CDB) is similar to a conventional (non-CDB) Oracle database, with familiar
concepts like control files, data files, undo, temp files, redo logs, and so on. It also houses the data
dictionary for objects owned by the root container and those that are visible to databases in the
container.
A Pluggable Database (PDB) contains information specific to the database itself, relying on the
container database for its control files, redo logs and so on. The PDB contains data files and temp
files for its own objects, plus its own data dictionary that contains information about objects specific to
the PDB. From Oracle 12.2 onward a PDB can and should have a local undo tablespace.
You can migrate a non-CDB database to a CDB database using Oracle tools.

1-2 What's new in Teamcenter 12 whats_new 12

 What's new in Teamcenter 12

The following illustration shows where files and tablespaces reside in a multitenant architecture. You
can install the CDB and PDBs using the Oracle DBCA tool. After the databases are in place, you
can manually create/define the IDATA, ILOG, INDX and MMV (as needed) tablespaces and their
data files to fit your required sizing and specifications or allow them to be created by Teamcenter
during installation through TEM.

whats_new 12 What's new in Teamcenter 12 1-3

 Chapter
Chapter 1: 1: What's
What's new
new in in Teamcenter
Teamcenter 12 12

Teamcenter 12 supports CDB and non-CDB databases. Be aware that Oracle has deprecated support
for non-CDB databases and may discontinue support after Oracle 12c Release 2 (Oracle 12.2).
If you migrate your non-CDB Teamcenter database to a CDB database, you must perform the
migration after you upgrade to Teamcenter 12.
For information about Oracle's multitenant architecture, see Oracle documentation.
For more information about using a container database with Teamcenter, see Oracle installation and
configuration in the appropriate server installation guide for Windows or UNIX/Linux.
For information about migrating Teamcenter to a multitenant database architecture, see Migrate a
non-CDB database to a CDB database.

How you can help make Teamcenter better

An option during Teamcenter installation allows you to participate in the Siemens PLM Software
Product Excellence Program.

1-4 What's new in Teamcenter 12 whats_new 12

 What's new in Teamcenter 12

Privacy statement

The Product Excellence Program helps Siemens PLM Software understand how customers use our
products and assists us in improving our products. The program is anonymous and participation is
voluntary.
The Product Excellence Program is designed to protect the privacy of the user and the intellectual
property created through the use of Siemens PLM Software products.

How does it work?

The Product Excellence Program is used to collect data about your installation, the features you use
and how you use them. The data is sent to Siemens PLM Software for analysis. By examining usage
patterns from a large number of people, we gain insight into how the products are used and how to
improve the software in future releases. Data collection occurs in the background as you use the
software and does not affect performance or functionality.

What data is sent?

The data collected can vary by product and by release as we gain more insight or add new
capabilities. The Product Excellence Program may collect information on the functions utilized, the
operating environment (for example, OS, RAM, graphics, etc.), product version, or other indications of
user interactions. This data is solely used by Siemens PLM Software to improve our products and
is never shared with any third party.
There is no contact information in the data and Siemens PLM Software will not contact you by phone
or email as a result of the data collected. Absolutely no information about the data you create or
manage is collected.

Participation is optional.

You can review and control your participation at any time.

A Teamcenter administrator can opt out of the Product Excellence Program during installation, or
after installation by modifying the TC_ProductExcellenceProgram site preference in Teamcenter.

What does this mean for Teamcenter?

The following table provides examples of the type of usage data that is collected by Siemens PLM
Software and, as equally important, clarifies what data is not collected by Siemens PLM Software.

whats_new 12 What's new in Teamcenter 12 1-5

 Chapter
Chapter 1: 1: What's
What's new
new in in Teamcenter
Teamcenter 12 12

What we collect What we do not collect

The data The data collected does not
collected contains contain user information
information about or intellectual property,
how Teamcenter including:
is deployed
and used, for • Contact information
example: • Information about data
created or managed in
• Teamcenter Active Workspace
server • IT infrastructure
platform identifiable information,
version, including server IP
platform, and addresses and host
architecture names
• Database
engine
• Client page
visits
• Command
events
executed
(for example,
Open) in the
client.

Participation in the program is enabled by default in the Product Excellent Program panel in both
Teamcenter Environment Manager (TEM) and Deployment Center. A Teamcenter administrator can
opt out of the program during installation through this panel, or after installation by modifying the
TC_ProductExcellenceProgram site preference in Teamcenter.

1-6 What's new in Teamcenter 12 whats_new 12

 What's new in Teamcenter 12

Administering Teamcenter

Strengthen security through centralized key management

Teamcenter Key Manager helps you strengthen security for Teamcenter deployment by managing
encryption keys safely and securely from a central location. Trusted Teamcenter satellites
communicate with a key manager server using two-way SSL to share keys and perform cryptography
functions. With Teamcenter Key Manager, you can:
• Easily define component-specific key policies governing key strength, encryption algorithm,
and key lifetime.

• Use keys with different policies for different Teamcenter components such as Teamcenter
Foundation and Dispatcher.

• Define the hashing policies to use, such as SHA512, SHA384, and SHA256.

• Manage keys, certificates, and policies using a web-based key manager application.

Sites using Teamcenter Key Manager must install Teamcenter Key Manager before installing
Teamcenter. For information on managing encryption keys, policies, and certificates, see Teamcenter
Key Manager.

Sharing Data

Improved Multi-Site Collaboration performance

Multi-Site Collaboration performance is significantly improved in this release, including now leveraging
TC XML as the underlying data exchange mechanism for all data models. This approach provides

whats_new 12 What's new in Teamcenter 12 1-7

 Chapter
Chapter 1: 1: What's
What's new
new in in Teamcenter
Teamcenter 12 12

significant performance improvements over previous versions of Multi-Site Collaboration which

exchanged non-4GD data in binary payloads. Performance improvements include:
• High throughput during replication.

• Parallelized operations.

• Linear replication times resulting is smaller time increases as the number of BOM lines increases.

• Synchronization performance is now proportional to the number of changes, not the overall
amount of data.

• Codeless coverage of new data models.

New Multi-Site Collaboration installations use TC XML-based Multi-Site Collaboration by default.

However, sites upgrading from earlier versions of Multi-Site Collaboration (referred to as "legacy
Multi-Site Collaboration") are not automatically transitioned to using TC XML-based Multi-Site
Collaboration. After upgrading to Teamcenter 12.0, these sites will continue to use legacy Multi-Site
Collaboration by default until they manually transition their sites to use TC XML-based Multi-Site
Collaboration.

Teamcenter Customization

Use Eclipse 4.6 for rich client customization

The rich client has completed enough refactoring that it now runs on Eclipse 4.6.
• You now have access to E4 application model services.

• Rich client extension points have not changed. You do not have to refactor your existing
extension point customizations.

• The Eclipse compatibility layer helps make your migration easier.

• Enhanced CSS capability allows access to theming.

1-8 What's new in Teamcenter 12 whats_new 12

Siemens Industry Software

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

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

About Siemens PLM Software

© 2018 Siemens Product Lifecycle Management

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