TEAMCENTER RESOURCES

This PDF download provides solutions for Teamcenter Architects for a number of issues they face today. It is an architecture level description of business situations and possible solutions using Over-the-Web (OTW.)

Please contact Applied CAx for more information on our Teamcenter services, or on the ICDs referenced herein.

Siemens suggests using Configurations to run multiple clients on the same machine. However, that can cause an issue when you want to upgrade or patch. For instance, let’s say that your Production client is at 10.1.3 and you patch the Test environment to Tc10.1.4. How do you upgrade the Test client without affecting the Production client installation?

Let’s look at another way of doing things...

This document describes where to find the Manufacturing Resource Library (MRL) import procedure in the Teamcenter 10.1.3 service pack.

Since the release of Teamcenter 8.3 and through Teamcenter 10.1.4, Siemens has provided a license usage script that reads the FlexLM license server log file and converts its usage information into a more readable format that can be imported into Microsoft Excel.

Figure 01 below shows the resulting report after it has been imported into a spreadsheet and the primary entries that are retrieved from the log file. Other entries that are not displayed in this window can be imported from the utility’s output and displayed as you choose.

As custom release status icons have not been incorporated into BMIDE, they must be maintained at the client level. Most companies use a combination of TEM and batch scripting to deliver custom status icons.

A better method is to create a custom ICD that controls the delivery during an Over-the-Web (OTW) installation. Teamcenter expert Randy Ellsworth presented on the topic at PLM World 2016 in Orlando, May 16-19, 2016.

This PDF covers the ICD content and INSWEB configuration for custom status icon delivery.

DOWNLOAD PDF: Delivering Custom Status Icons

All Teamcenter clients and users should know of SFB-Teamcenter-8568. Due to a problem involving concurrent use of generating and accessing shared memory, the use of shared memory can cause memory corruption in certain cases. This is more evident in the UNIX/Linux platform. These shared memory issues will be completely resolved in Teamcenter 11.2, slated to be released in late July 2015, where shared memory will be fully robust with enhancements.

Affected Software: Teamcenter 8.3 and MPs or patches up to TC11.2
Associated PR Number(s): 1792150, 2241061
Associated document: SFB-Teamcenter-8568
Associated document: Steps for disabling preferences in shared memory (download or view)

Teamcenter is the top competitor in the PLM market, capable of managing much of an enterprise’s business data and processes. Teamcenter standardizes the way business data and processes relate to each other through the use of a data model that defines the structure of a relational database, like Microsoft SQL Server or Oracle.

The Teamcenter data model is a structured, hierarchical organization of abstract objects designed to represent business data. A data model represents documents, part designs, design documents, and the relationships between them, as well as the business processes applied to them. Teamcenter has a data model that can be extended using the Business Modeler IDE (BMIDE).

BMIDE is a tool for adding custom data model objects on top of the default Teamcenter data model objects. The BMIDE accomplishes this by separating your data model into its own set of XML files that are kept apart from the standard data model, known as the commercial off-the-shelf (COTS) data model.

Teamcenter expert Randy Ellsworth recently dove into the Siemens help forum to give advice to a domain architect looking to consolidate 4 servers spread across the US, Netherlands, and Taiwan. The goal was to achieve Global Change management while providing the benefit of NX user connections.

As Randy puts it in the forum, the site consolidation tools are your best friend in this situation. He advocates for employing low-level tcxml, which includes cvs2tcxml. His other advice includes:

• You probably want to have a distributed "NX Custom" folder structure, with the main at the central location - synced to remotes (scheduled task or cron) - allowing unique remote content, to maintain corporate standards and files. The benefit is the administration is simpler and nothing special needs to be installed on clients.
• You can use a similar concept for distributing TC/NX help and other static content via the remote File Management Systems (FMS).
• You want location specific rich client flavors (differing parent FSC) which point to the remote FSC's (delineated by IP range is best).
• You may want to add more rich client flavors for Minimum, NX, NX+MSO, MSO and SuperSet[Admin] feature sets.

Please visit the full thread for other, ongoing tips and tricks.

The following software notification has been issued by Siemens PLM Software.

Affected Software: Solid Edge
 
End of Maintenance dates for the Solid Edge suite of products are listed below. These dates represent when Siemens PLM Software will discontinue Maintenance Pack support along with the last Teamcenter release supported.

Affected Software: NX, Teamcenter (TC)
Associated PR Number(s): 7912475, 7884777, 7941876
Scope: TC 11.2.1.x, TC 11.2.2.x, TC 10.1.7.x

PROBLEM:

Following refile the ownership on some forms (e.g. NX0Application-Info form) is being changed from the original owner to the user running the refile. If the original owner then loads the part into NX and tries to save the part, the Save fails.

REMEDY:

The following TC versions contain the needed patches:  
Patch = 11.2.2.1_a01_3
Patch = Tc 10.1.7.1_a01_1