Teamcenter Scripted Customization - Simpler, faster & easy to deploy

Teamcenter customization has never been so easy, faster and easy to deploy with no downtime required!

Enterprise software like Siemens Teamcenter PLM often requires extensions to meet various business requirements such as functional, performance, security, and compliance.

Most times these can be achieved & recommended through codeless customizations (configurations). But there are certain business requirements which call for Codefull customizations (such as workflow handlers, utilities, runtime property, operation, extension to property, POM enquiry and so on), where we need to customize Teamcenter server to extend the behaviour or add new functionalities.

Traditionally, Teamcenter server components are customized using C/C++. Deployment of these server customizations to Teamcenter environment require system downtime and sanity check. More the customization more the deployments and hence the downtimes. With the nature of C/C++, it is always a difficult and time-consuming activity to customize Teamcenter server that called for skilled resources.

To overcome above challenges, Siemens has introduced Scripted Customization in Teamcenter 2312 release, a new way of customizing Teamcenter

Scripted customization does support writing code in C# which is lot easier compared to C/C++, for which human resources are easily available. One of the major features, that offer dynamic code compilation and thereby functionality gets immediately available without any downtime (restart) of Teamcenter environment.

How Scripted Customization Works?

Scripted Customization is used?to make changes to the core behavior of Teamcenter without requiring downtime. Unlike traditional approach, where creating new server-side functionality like service operations, runtime properties, object operations, POM queries, or workflow handlers require coding with Teamcenter's C/C++ APIs or using the Business Modeler IDE, or both. Whereas scripted customization uses C# API to create these extensions dynamically.

Where Scripted Customization can be employed?

Scripted Customization can be used in various scenarios based on the use-cases and the requirements.

1.???? Workflow Handlers

2.???? Custom SOA Service

3.???? Metamodel Customization

• Add Custom Runtime property.
• Custom Extension to property
• Custom Operation Customization
• Custom extension to operation

4. POM Enquiry

Let's see the Business Use Case to understand the value add of scripted customization

Customer had requirement to show BOM weight rollup in Active Workspace client and as part of solution, a new runtime property was introduced to show assembly weight.

Below table shows implementation process of runtime property customization in both conventional C++/ITK and scripted customization approach

What benefits it brings?

• Reduced cost and time to customize Teamcenter Server with C#
• No downtime required for code deployment with dynamic code compilation.
• Simplified and accelerated code development lifecycle
• Compliant with cloud deployment paradigm

We are committed to be your trusted source of knowledge and support throughout your PLM journey. Our team of experts and thought leaders will bring you actionable insights, best practices, case studies, and the latest trends in PLM, through most insightful and advanced training.

For any of you Teamcenter training needs feel free to reach out to us!

Warm regards,

Akshay Kothe

Teamcenter & Active Workspace Customization Specialist

+91- 7350886857

FaithPLM Solutions LLP

Most insightful and advanced Teamcenter Training Provider

www.faithplm.com