Tyes ------In Windchill, Types are used to classify and organize data objects based on their

properties and characteristics. Types define a set of attributes that objects of that type should

have, and they provide a way to manage the lifecycle of objects within Windchill.

For example, in Windchill, you can create a type called "Document" to represent a document

within a product design. This type could have attributes such as document number, title,

revision, and status. You can also define workflows, access controls, and other properties for

the "Document" type.

By using types, you can ensure that data objects in Windchill are consistent and structured in
a

way that makes sense for your organization. You can also use types to define different

behaviors and processes for different types of objects.

Windchill provides a number of pre-defined types for different types of objects, such as parts,

documents, CAD models, change requests, and more. You can also create custom types to suit

your organization's specific needs.

Overall, types are an essential aspect of organizing and managing data in Windchill, and they

help ensure that information is accurate, consistent, and accessible when it is needed.

Attributes ---------- In Windchill, Attributes are the specific characteristics or properties that

define an object within a particular type. Attributes describe the unique features of an object,

such as its size, color, weight, or location, and provide important information about how it

should be managed.

Attributes can be defined at the type level, which means that all objects of that type will have

the same set of attributes. For example, all "Part" objects in Windchill might have attributes

such as part number, description, material, and weight.

Attributes can also be defined at the instance level, which means that individual objects can

1
have their own unique set of attributes. For example, a specific "Part" object might have a

custom attribute called "Customer Name" that is not defined at the type level.

Attributes can have different data types, such as text, number, date, or Boolean, and can also

have constraints, such as minimum and maximum values, or allowed values from a
predefined

list.

Overall, Attributes in Windchill are an important aspect of defining and managing data, and
they

help ensure that information is accurate, consistent, and accessible when it is needed. By
using

attributes to describe and categorize objects, users can quickly and easily find the information

they need and ensure that data is consistent and accurate.

Local Attributes - In Windchill, Local Attributes are attributes that are specific to a particular

object or instance of a class. These attributes are defined locally and are not inherited by
other

objects of the same class. Local attributes can be used to provide additional information or

context that is specific to a particular object, but may not be relevant or applicable to other

objects.

Single-valued—can have zero or one value

Stored in columns directly on the underlying object class

Tied to a specific type and its subtypes

Global Attributes- Global attributes can be used in various ways in Windchill. For example,
they

can be used to store common metadata about a particular object, such as part numbers,

descriptions, or revision history. They can also be used to define custom workflows or
business

2
rules that are common to all objects of a particular class.

* Reusable Attributes -Reusable attributes can be very useful in situations where you need to

define a common set of attributes that can be used across multiple classes. For example, if
you

have several classes that require a "cost" attribute, you can define this attribute as a reusable

attribute and add it to each of the relevant classes. This way, you only need to define the

attribute once, and it will be available for use in all classes that require it.

*Global Inumeration List- Global enumeration lists are similar to global attributes, in that they

are defined at the class level and inherited by all instances of that class. However, instead of

defining a single value for an attribute, a global enumeration list defines a set of allowable

values that can be used to populate the attribute.

For example, suppose you have a "status" attribute for parts in your system. You might define
a

global enumeration list called "Part Status" that includes values like "Released", "In Review",

and "Obsolete". When users create new parts, they can choose one of these values from the

Part Status list to populate the status attribute, ensuring that all parts are assigned one of the

allowable status values.

Alias Attributes--- Alias attributes map to an attribute on a related object. This mapping
allows

information from the related object to be displayed on a user interface for the current type,

such as an information page or table, by including the alias attribute in a layout . The mapping

to the other attribute is specified in the Mapping property, using operators and the internal

names of types and attributes to navigate object links and references.

Data Types - In Windchill, Attributes can have different types based on the kind of data they

3
represent. Some of the common types of attributes in Windchill are:

Text: Used to store alphanumeric characters, such as names, descriptions, or comments.

Integer: Used to store whole numbers, such as counts, quantities, or indices.

Floating Point: Used to store decimal numbers, such as measurements, dimensions, or

weights.

Boolean: Used to store values that represent true or false, such as for flags, switches, or

options.

Date and Time: Used to store specific dates and times, such as for deadlines, schedules, or

milestones.

Rich Text: Used to store formatted text, such as for document content, notes, or instructions.

List: Used to store a set of predefined values, such as for categories, statuses, or priorities.

Object: Used to reference another object within Windchill, such as for relationships, links, or

dependencies.

File: Used to store files associated with a Windchill object, such as for CAD files, documents,
or

images.

Reference: Used to link one object to another, such as for assembly structures, BOMs, or

variants.

URL: Used to store URLs that link to external resources, such as for web pages, product

catalogs, or technical specifications.

These are just a few examples of the types of attributes that can be defined in Windchill.

Attributes can also have other properties, such as default values, constraints, or display
settings,

to further define their behavior and appearance. By using attributes to describe and
categorize

4
objects, users can quickly and easily find the information they need and ensure that data is

consistent and accurate.

These are used to define the different types of parts that can be created and managed within
the system. For example, you might have part types for mechanical parts, electrical parts, and
software components.

Document Types: These are used to define the different types of documents that can be
created and managed within the system. For example, you might have document types for
design specifications, manufacturing instructions, and test reports.

In Windchill, you can apply constraints to attributes. The constraints are applied in the Type
and Attribute Manager utility, or in Object Initialization Rules. In Windchill, the constraints
are applied at site, organization, product, and library levels. For example, in the Type and
Attribute Manager utility, you can apply a Legal value list constraint to an attribute. When
you apply this constraint, the attribute can only take permitted values specified in the
constraint.

Constraints can be applied using an OIR. For example, when an attribute like Number takes
the value which is automatically generated by the server either at time of persistence or a
pre-generated value before persistence.

You can enter the formula in the Formula field during the Set Properties step of creating the
calculated attribute, or by editing the Formula field on the attribute information page once
the calculated attribute has been created.

Calculated attributes

A translated text attribute is a read-only attribute that displays the translated text for the
associated source text attribute, as determined by the user’s language configuration setting.
To display translated text for an attribute, a translated text attribute must be created. For
more information about user language configuration setting, see User Language
Configuration.

translated tex