TATA CONSULTANCY SERVICES

HIRE AND TRAIN MODEL

STUDENT INTERNSHIP
REPORT
 Prepared By
Praveen.j
(DT20234224918)
R.M.K Engineering College
Designation: Intern
Product Lifecycle Management

April 2024
 5.14 Life Cycle Template Administration 25

6 Certifications completed and undergoing status 27

7 Feedback on internship 28
1. About the Program:

1|Page
 This internship program has provided invaluable real-world experience for students,
offering a condensed yet comprehensive glimpse into the company's operational
procedures. Spanning from February to April 2024, I had the opportunity to delve into
the realm of PLM (Product Lifecycle Management) alongside fellow interns. Under
the guidance of professionals in my field, I swiftly grasped essential concepts and
procedures. The program was structured into various segments, each offering hands-on
learning experiences and direct mentorship in utilizing relevant software tools.
What is plm?
PLM deals with every stage a product goes through, from initial concept to retirement.

Explore PLM solutions

Product lifecycle management overview
Product lifecycle management (PLM) deals with every stage across a product’s
lifetime. From the creative thinking of the product designer, to the valuable data being
sent and received by your IoT network, and finally, to the frank and timely feedback
you get from your customers – every piece of information across a product’s lifecycle
is part of a bigger story.
And with today’s circular economies and more transparent supply chains, that story
extends back to the raw materials used in production, and forward to the end-of-life
stages of that product such as recycling and repurposing. The trick to a good PLM
strategy is to listen to all those stories — and be able to act on them. This means
integrating and analysing them so that you can make meaningful improvements and
innovations, quickly.

2|Page
 2. ACKNOWLEDGEMENT:

3|Page
 I would like to thank Mr. Muruganantham Madan Veluchamy, Operation Head at
TCS, for providing us continues support and engagement.

I express my sincere thanks to Mr. Lakshman Prakash, Head HR at TCS, for granting
permission to undertake the Internship.

I express my sincere thanks to Mr. Mr.Seetharama gullapalli, Lead – Strategic

Workforce Management, Digital Thread Subunit, IoT DE. for effectively orient the
programme and facilitate the SMEs.

I wish to thank Ms. Gayathri R P, Project Lead at TCS for the support and guidance
given to us.

I wish to thank Mr. Gokulnath Ramakrishnan, Assistant System Engineer at TCS, for
the support and encouragement given to us.
I thank R.M.K. Engineering College Management for providing this chance to express
my talents and knowledge.

I would express my gratitude to our beloved

Chairman Shri. R.S. Munirathinam, R.M.K. Group of Institutions for
having arranged to do this Internship.

I would express our gratitude to our beloved Vice Chairman Shri. R.M.
Kishore, R.M.K. Group of Institutions for having arranged to do this Internship.

I wish to express our sincere thanks to our

beloved Principal Dr. K.A. Mohamed Junaid for granting
permission to undertake the Internship.
I also thank our Head of the Department of Mechanical Engineering
Prof. Dr. K.R. Senthil Kumar, M.E, Ph.D. for his kind encouragement.

I wish to thank my Co-ordinator Ms. Praveena B., IoT SPOC., Assistant

4|Page
 Professor at R.M.K. Engineering College for guiding and connecting us to
professionals in the TCS.

I wish to thank my PLM Domain Co-ordinators Mr. K. Sengottaiyan, PLM

SPOC, Assistant Professor at R.M.K. Engineering College and Dr. K. Vinoth
Kumar, Associate Professor at R.M.K. College of Engineering and
Technology for supporting us throughout the training program.

3. Objective of the Internship:

 The primary objective of this internship is to enhance student skills in alignment with
current software and technologies.
 Serving as a practical platform, this internship empowers students to apply their
academic learnings in a real-world setting.
 Through mentorship, the internship aims to equip students with comprehensive
knowledge and expertise.
 Students are encouraged to develop essential social skills, including effective
communication, active listening, confident presentation, and meaningful interaction
with peers and professionals.

5|Page
4. Summary of sessions during the Internship:
S.No. Date Session Topic Inputs from the Session

1. 08-02-2024 Introduction session  Introduction to the Internship

Program.
 Introduction on windchill
software.

2. 15-02-2024 Types and attribute  Demonstration on how to create a

management windchill part.
 Demonstration on how to create
and manage the attribute.

3. 22-02-2024 Form processor  Explained about the form

processor and the different
methods of Form processor.
 Demonstration of creating an
exception in Do operation
method.

4.- 04-03-2024 Preference management  Creating Attributes, Doing

Validation, Changing container
name without changing in
backend using preference.
 Explained how to create a
custom preference in site level.

5. 07-03-2024 Types of Preference  Explained about the Types of

management Preference management.
Boolean type and String Type.

 Explained about creating a

Boolean type attribute in site
level, organization level and
container level

6|Page
7|Page
6. 14-03-2024 Validators in Windchill  Explained how to create User
Interface (UI) validator in
Windchill.
 Explained how to create and
register an action Validator in
Windchill.

7. 25-03-2024 Workflow management  Demonstration on Creating a

Workflow template.
 Explanation on the Workflow
Robots.

8. 28-03-2024 Participant Administration  Demonstration on how to Create

a new User, Group
(organization).
 Demonstration on how to assign
role to a user.

9. 04-04-2024 Life cycle management  Demonstration on how to create

a new container in the
organization level.
 Explained about the life cycle
phases.

10. 16-04-2024 Final Report Review  Internship report was reviewed.

8|Page
5. Program Outcome:

File Menu Selections

Add allows you to add objects to your workspace. Remove

allows you to remove selected objects from the workspace. New
allows you to create a new CAD document, graphics dynamic
document, or part; or to create a new revision of a selected
object.
Open allows you to open a selected CAD document’s Creo
Parametric le or to open a Creo View representation of a
selected object.
Check In begins the check-in process for selected objects.
Check Out begins the check-out process for selected objects.
Undo Check Out removes the check-out status on a selected
object and discards any local modifications.
Lock allows you to make a selected workspace object read only.
Unlock removes the read-only status from a selected object.
Rename allows you to change the name of selected workspace
objects (only if the object has never been checked in).
Save As allows you to save a copy of a selected object as a
new workspace object (not committed to common space until
checked in).
Upload places a selected local object in the server-side
workspace.
Update compares workspace objects with the workspace
configuration specification and replaces the workspace version
with a version available on the server, if appropriate.
Export List to File allows you to export the workspace Object
List to a le in one of the following formats: CSV, HTML, TEXT,
XLS, XLSX, XLS Report, XML.

9|Page
5.1 Quick Reference for Menus, Icons, and Symbols:

The following tables is a quick reference for menu commands, action icons, and status
symbols used in Creo Parametric with Windchill.

10 | P a g e
 Edit Menu Selections

Attributes begins the process of editing attributes for

checked out, selected objects.

Edit Association allows you to manually edit the

association of objects.

Auto Associate begins the process of automatically

finding or creating parts to be associated with
selected CAD documents.

Set State allows you to set a life cycle state for a

selected object.

11 | P a g e
5.2 Working with the Type and Attribute Management:

12 | P a g e
The Type and Attribute Management utility, accessed by clicking the Type and
Attribute Management link from Site > Utilities or Organizations > Utilities, allows
site and organization administrators to manage type definitions, attribute definitions,
measurement systems, and quantities of measure. Users with the appropriate
permissions can create, edit, or remove types or attributes. Additionally, administrators
can configure display units for attributes, associate attribute definitions with type
definitions, and constrain the values of those attributes.

Type and Attribute Management window provides access to the following components:

• Manage Types - Allows you to create new subtypes of those parts, documents, change
objects, and other objects installed with your solution.

• Manage Global Enumerations - Allows you to create, edit, and delete value lists for
use by attributes.

• Customize Modeled Enumerations - Allows you to customize the value list of a

Windchill enumerated type, such as life cycle state or work ow role.

• Manage Reusable Attributes - Allows you to create new attributes that can be used by
multiple Windchill objects, and associated with different values.

13 | P a g e
• Manage Measurement Systems - Allows you to define your own measurement
systems and override the default display units for the four standard measurement
systems.

14 | P a g e
 • Manage Quantities of Measure - Allows you to define your own quantities of
measure and override existing display units.

5.3 Form Processor:

When the data is to be submitted to the Windchill server, the form processor is responsible
for generating the response to be returned to the client.

Types of Form processor methods:

• Pre-process method

• Do operation method

• Post processor method

5.4 Preference Management:

The Preference Management utility allows users to view and set preferences, such as
display and search options, to enhance their Windchill experience, and allows
administrators to view and set preferences for various application contexts, such as

projects, products, or organizations.

15 | P a g e
The Context field at the top of the Preference Management utility identifies the
user or context from which the Preference Management utility was opened; only
the preferences for that user or context are displayed.

When the Preference Management utility is launched from a particular

application context, the complete list of available preferences for that context is
displayed.

The Find in tree field allows you to search for keywords in the preference names
and descriptions displayed in the Preference Management utility for the current
context. Click the next match and previous match arrows to navigate through
the matches.

Preferences are grouped by category and subcategory according to the type of

functionality they impact, such as Display or Search. The expand icon and
collapse icon next to the category names can be used to view and hide the
preferences in each category.

Within a category, each preference is named and a short description of the

preference is provided. The current value of the preference is also displayed. A
locked icon next to the preference indicates that the preference value cannot be
changed below the level at which it is locked.

The following actions may be available for individual preferences from the
rightclick actions menu:

• Set Preference – allows you to view more detailed preference

information and change preference settings. This action is available if the
preference is not locked at a higher level.

16 | P a g e
• Delete Child Instances – allows site and organization administrators to
remove any preference values set at levels lower than their current context. This
action is available to site and organization administrators only.

5.5 Types of Preference Management:

1. String

out-of-the-box (OOTB) method.

2. Boolean

Radio Button method

5.6 Preference Value Hierarchy:

Preference values set at one level are inherited by the application contexts
below. For example, preference values set at the site level are inherited by the
organization; application contexts within the organization inherit preference
values from the organization, as shown in the following figure:

17 | P a g e
 5.7 Creating a Preference:

The creation of a preference is done through an XML load file.

When creating a Preference the following information need to be determined:

1. Unique preference name

2. Visibility: if the preference will appear in the preference manager UI and
visible at what contexts: SITE, ORGANIZATION, CONTAINER or
USER.
3. Preference category: The category the new preference will appear under
in the Preference Management utility.
4. Display name: This is the Name column in the Preference Management
utility – string in the form <RBINFO>:< RBINFO key>

5. Description: This is the Description column in the Preference

Management utility – string in the form:<RBINFO>:<RBINFO key>

6. Long Description: This description is displayed in the Edit Preference UI,
gives a more detailed description including the expected values.

7. string in the form <RBINFO>:<RBINFO key>

18 | P a g e
 8. Default value
9. Value header

In the example below, we will create a new preference named

/com/mycompany/MyNewPreference along with an associated preference
category to appear in the Preference Manager UI.

Create a resource bundle for labels used for your new preference. Labels are
needed for display name and description of preference category which the new
preference will be visible under in Preference Management UI. Labels are also
needed for the display name, description and long description of your
preference.
Create the file mycompanyPreferenceResource.rbInfo in
package com.mycompany.pref. In this example, this file would be added to the
<Windchill>/src/mycompany/pref directory.

ResourceInfo.class=wt.tools.resource.StringResourceInfo

ResourceInfo.customizable=true

ResourceInfo.deprecated=false

# Preference Category labels

MyNewPreferenceCategory.displayName.value=My Preference Category

MyNewPreferenceCategory.description.value=Preference Category for my

custom preferences.

19 | P a g e
# Preference Definition labels

MyNewPreference.displayName.value=Display name of preference /com/mycompany/

MyNewPreference

MyNewPreference.description.value=Description of preference /com/mycompany/

MyNewPreference.

MyNewPreference.longDescription.value=Long description of preference

/com/mycompany/MyNewPreference.

1. Build the resource bundle by executing the following command from a

windchill shell:

ResourceBuild com.mycompany.pref.mycompanyPreferenceResource
2. Restart the servlet engine and the MethodServer.

3. Create Preference load file: createMyNewPreference.xml. It will contain a

definition for the new preference category and new preference definition.

<?xml version="1.0"?><!DOCTYPE NmLoader SYSTEM "standardX10.dtd">

<NmLoader>

<csvPreferenceCategory handler="wt.preference.LoadPreference.createPref erenceCategory">

<csvname>CUSTOM_PREFERENCE_CATEGORY</csvname>

<csvparentName></csvparentName>

<csvdisplayName> com.mycompany.pref.mycompanyPreferenceResource:

20 | P a g e
MyNewPreferenceCategory.displayName

</csvdisplayName> <csvdescription>

com.mycompany.pref.mycompanyPreferenceResource:MyNewPreferenceCategory.descripti on

</csvdescription>

</csvPreferenceCategory>

<csvPreferenceDefinition

handler="wt.preference.LoadPreference.createPreferenceDefinition">

<csvname>/com/mycompany/MyNewPreference</csvname>

<csvvisibility>USER</csvvisibility>

<csvcategoryName>CUSTOM_PREFERENCE_CATEGORY</csvcategoryName>

<csvdisplayName>com.mycompany.pref.mycompanyPreferenceResource:MyNew
Preference.displayName</csvdisplayName>

<csvdescription>com.mycompany.pref.mycompanyPreferenceResource:MyNew

Preference.description</csvdescription>
<csvlongDescription>com.mycompany.pref.mycompanyPreferenceResource:

MyNewPreference.longDescription</csvlongDescription>

<csvdefaultValue>Default Value</csvdefaultValue>

<csvhandler>com.ptc.windchill.enterprise.preference.handler.

StringPreferenceValue

Handler:4000</csvhandler>

</csvPreferenceDefinition>

<csvLinkPreferenceClientDefinition

handler="wt.preference.LoadPreference.setClientDefinitionLink">

<csvname>/com/mycompany/MyNewPreference</csvname>

21 | P a g e
<csvclientName>WINDCHILL</csvclientName>

</csvLinkPreferenceClientDefinition>

</NmLoader>

4. Load the preference category and preference definition using the following
command:

windchill wt.load.LoadFromFile -d <full path>/createMyNewPreference.xml

5.8 Deleting a Preference:

The deletion of a preference is also done through the use of an XML load file.
Using the example from the Creating a Preference topic, we will delete the
preference /com/mycompany/MyNewPreference. The deletion of
the preference will also remove any preference instances which may have been set
for this preference in the UI.

1. Create an XML file, deleteMyNewPreference.xml, containing the

following definition to specify the deletion of the preference.

<?xml version="1.0"?><!DOCTYPE NmLoader SYSTEM

"standardX10.dtd">

<NmLoader>

<csvDeletePreferenceDefinition

handler="wt.preference.LoadPreference.deletePreferenceDefinition">

22 | P a g e
<csvname>/com/mycompany/MyNewPreference</csvname>

</csvDeletePreferenceDefinition>

</NmLoader>

2. Delete the preference definition using the following command: windchill

wt.load.LoadFromFile -d <full path>/deleteMyNewPreference.xml

5.9 Workflow Management:

A workflow system gives you the ability to automate procedures in which

information, tasks, and documents are passed among participants. This
procedure is based on a process composed of well-defined rules designed to
efficiently accomplish your business goals.
This reference information provides details about creating and editing workflow
templates, importing and exporting templates, and viewing workflow history.
Detailed information concerning configuring worklist fields and object
subscription code is also available.

The Windchill workflow system consists of the following components:

1. The Workflow Template Editor, which allows you to define a workflow

process and save your definition as a process template. This graphical
editor and its use are the focus of this chapter.

23 | P a g e
 2. The workflow runtime system, which executes a defined workflow
process within the context of a specific business object. Process execution
includes delivering work assignments to users participating in the process,
opening applications initiating subprocesses, and so on.
3. The Workflow Process Manager, a graphical tool for monitoring and
reporting on workflow processes. For access control information, see
Process Manager Toolbar Access Control.
4. The Workflow History Viewer, which provides a simple ASCII interface
used to access recorded workflow events, such as state changes, data
transfers, or process start. Viewing Workflow History can assist you in
optimizing or streamlining a workflow process.
5. The Workflow Process Administration utility, which provides a centralized
area to manage executing workflow processes and diagnose any warnings
or errors that may occur.

5.10 Workflow Robots:

Activity nodes rely on assigned users to complete workflow tasks. Workflow
robots complete workflow tasks without requiring user interaction.

24 | P a g e
5.11 Participant Administration:

You can access the Participant Administrator utility from Site > Utilities or from
Organizations > Utilities

• The Participant Administration utility link from Site > Utilities

provides the site administrator with access to users and to the user-
defined groups and organizations created in the site context.

25 | P a g e
 • The link from Organizations > Utilities provides access to only those
participants that belong to the organization context from which you
launched the Participant Administration utility and to those that belong
to the site context (which is its ancestor context). If the organization
was set up so that it allows entire user and user-defined group
directory selection, then you can see all users and groups (except for
the system groups maintained by your solution). However, access
control rules may be set to prohibit you from seeing some users and
user-defined groups.

• The Participant Administration utility creates only organization objects

(also referred to as the organization) and not organization contexts.

Creating a User

Creating a new Windchill user involves creating both a user object in the
Windchill database and a user entry in a directory server.
If the user already exists in a user directory server, Windchill automatically
creates the corresponding Windchill user object in the Windchill database when
someone searches for the user and adds them to a table.
If all directory servers are read-only, the New User action is not available.

To create a new user, you must have write permission to the directory server in
which you want the user directory entry to reside. For information about setting
up user directory servers, see more about LDAP installation settings for your
Windchill solution.

26 | P a g e
Basic Administration > Managing User Participation > Participant Administration
> Working with Participants > Managing Users > Creating a New User.

To create a new Windchill user, use the following procedure:

1. From the Participant Administration table, select the new user icon or
select New User from the Actions menu.
2. The New User window opens.
3. Enter information in each step in the New User window. You can
navigate between the steps by clicking the step name or clicking Next.
4. The following steps make up the New User window: Set Attributes,
Assign to Groups, Assign to Profiles, Assign Picture, and Assign
Signature.
5. Click Finish to create the new user and close the window.
Or
Click Apply to create the new user, but leave the window open so that you
can create another user.

Creating a New Group

Groups created using the Participant Administration utility are used in Windchill
utilities that allow administrators to select participants as part of setting up
context teams, access control, indexing, and notification policies or as part of
setting up workflow processes or life cycle templates.

27 | P a g e
Groups can be members of other groups, and groups are associated with the
context in which they are created. After you have created a group, you can edit
the group but you cannot change the context associated with the group.

Creating a new user–defined group involves creating both a group object in the
Windchill database and a group entry in a directory service.
To create a new user–defined group, use the following procedure:

1. From the Participant Administration table, select New Group from the
Actions menu or select the new group icon.
2. The New Group window opens.
3. Enter information on each tab in the New Group window. Navigate
between the tabs by clicking the tab name or clicking Next.
4. The following steps make up the New Group window: Set Attributes,
Add Members, Assign to Groups, and Assign to Profiles.
5. Click Finish to create the new group.
Or
Click Apply to create the new group, and leave the window open so that
you can create another group.

Creating a New Organization Participant

Creating a new organization using the Participant Administration utility creates

an organization object in the Windchill database and creates a directory server
entry.

28 | P a g e
To create an organization through the Participant Administration utility, you

must have write permission to the directory server in which you want the

organization participant entry to reside.

To allow members of an organization to create products and libraries or to create

programs and projects, an administrator must create a site administrator and an
organization context for an organization participant.
Creating an organization context can be done from Organizations > View all
organizations. From that tab, click the Organizations link and then click New
Organization.

To create a new organization participant, use the following procedure:

1. From the Participant Administration table, select New Organization

from the Actions menu or select the new organization icon.
2. The New Organization window opens.
3. Enter the initial information in the New Organization window. Required
fields are preceded by an asterisk (*).
4. Click Apply to create the organization and keep the window open so
that you can create another organization.
Or
Click Next to move to the next step.
Or
Click Finish to create the organization and close the window.
5.12 Life Cycle Management:

29 | P a g e
Business information and objects become more mature throughout the product
development cycle. During this cycle, circumstances change, such as who can
access data, what processes are related, and where an object can mature to next.

Life cycles define the way in which business objects mature, providing a model
for the commercialization process.

A Windchill user in the life cycle administrator role can create a variety of life
cycles. These life cycles define the states and transitions associated with various
business objects and the available transitions between those states.

This section includes the following topic groups:

• Understanding Life Cycles

• Working with Life Cycle Templates

5.13 Understanding Life Cycles:

A life cycle is an automated, graphical model, employing phases and gates, used
to manage business objects as they progress from conceptualization through
obsolescence.

When created, a life cycle-managed object enters a life cycle phase, where it is
assigned an initial state, which is associated with the initial phase of its life cycle.

30 | P a g e
Each Windchill object type can have unique sets of life cycle states. While an
object is in a specific life cycle phase, certain business rules apply, such as
access control rules or a specific workflow defined for that phase.

Windchill PDMLink supports the following business processes that you can use
to manage the life cycle of a part, document, or CAD document. You can use
transition rules to control when in the life cycle this operation is available. For
example:

• Set State—Enables you to informally set the life cycle state of an object.
• Promote—Enables you to set the state of one or more objects to a new life
cycle state as part of a review process.
• Change—Enables you to execute a change order for a product development
object.

• Revise—Enables you to create a new version of the object.

5.14 Life Cycle Template Administration:

The Life Cycle Template Administration utility to manage existing life cycles
and create new ones. For more information on life cycles, including conceptual
information, see Life Cycle Management.

The Life Cycle Template Administration utility is available from the Utilities
page under Site, Organizations, Products, and Libraries:

31 | P a g e
Table Actions
The following actions are available from the Life Cycle Templates table. The
visibility of actions depends on your permissions and the context from which
you launch the utility.

Actions are available from the table toolbar, the table Actions menu, and from the
right click actions menu in table rows:

32 | P a g e
33 | P a g e
6. Certifications completed and undergoing status:

S. No Certification Name Platform Status

1 JAVA Programming - Besent technology Completed
Beginner to Master
2 Java developer technology In Progress

7. Feedback on Internship:

 This intern is very helpful for my work space

 I successfully translated theoretical knowledge acquired in college into
practical scenarios, thereby reinforcing my skills.
 Through active engagement, I enhanced my understanding of
contemporary software and technologies prevalent in the industry.
 Using this platform I have good knowledge in windchill software.

34 | P a g e