Windchill Business Administration Plans


Compare Plan Options Express Premium Enterprise Advanced
Common Options
Define Product and Library

Additional information

Products and Libraries are contexts or containers that store all data objects used by a user. Each Product and Library container can have their own access control permissions, preferences, teams, folders, life cycle definitions, workflows, domains, etc.

  • Product: Stores all design content for production.
  • Library: Stores all content that are used across the Products and are controlled by a library manager.Typically, the content is vendor items and items that are not manufacture by the company. Examples of library objects are bolts, nuts, washers, and screws.

Create Product and Library Templates

Additional information

Product and Library templates establishes initial settings for several business elements, including folders structure, context roles, team templates, domain polices, data types, data templates, object initialization rules, life cycle templates, and workflow templates. Product and Library templates allow a user to create a new Product and Library the same each time based on the template settings and configuration.

Define Users and Groups

Additional information

Users, organizations, and groups are called Participants. User accounts are used to grant and control access to data, maintain a historical record of activity, and enable E-mail messaging. Groups identify a set of users to access data and how to interact with the data.

Define Context Roles

Additional information

Roles are used to assign access control permission to users in a team. The domain policies or rules setup by the business administers are applied to a role. Users are mapped to the roles within a context team to determine what the users can do within the product or library. Examples of roles are members, designers, product manager, and engineers.

Define Version Schemes

Additional information

A version scheme identifies the revision sequence used for the Windchill objects, such as Documents, WTParts, and CAD Documents. For example, all the CAD Documents use revision A, B, C, or 1, 2, 3, or A1, A2, B1.

Set Windchill Preferences

Additional information

Preferences are a set of administrative settings that govern the behavior of the Windchill system.
Domain Access Control Polices

Additional information

Domain Polices are rules applied to roles in a Product or Library to control the access permissions, notification policies, and indexing rules. In other words, domain polices are the rules that determine who accesses what Windchill object and how. For example, all users in an engineering role cannot delete or rename any Windchill object, while a user belonging to the Product Manager role can delete or rename any object.

Promotion Request Administration

Additional information

Promotion Request is a process to promote or change an object state upon an approver or reviewer. The Promotion Request is Windchill Object using an advanced lifecycle that includes a promotion workflow process. The promotion is a vehicle collecting one or more objects to promote using a process plan for an approval to approve or reject the changes of a given object, such as a CAD document, Document, or WTPart.

Client Side Configuration

Additional information

While Windchill does not have an official client application, there are browser, network, Java, virus software, video card, and CAD application settings that should be evaluated and configured to get optimal performance from Windchill.

Business Settings Documentation

Additional information

A document of the Business Administration settings and configuration will be provided for the customer to review and store for future reference on how the Windchill business environment was configured.

CAD Document & Document Options
Define Basic Life Cycle & Transitions

Additional information

Life Cycles define the stages or states of maturity for a data object. It provides visible status to the community. Business administers apply business logic and access control permissions to the life cycle states. Life Cycles include transitions that are predefined actions that provide business logic and enable life cycle movement. Most transitions are performed by users from the actions menu. For example, a CAD document has a In-Work, Released, Obsolete, and a Under Review state.

Define Object Initialization Rules

Additional information

Object Initialization Rules control the behavior of the Windchill objects. Business administrators configures the OIR to set the behaviors and associations of an object. The rules are written in XML, assigned to a specific object class, and can be defined a all contexts. The OIR affect the object attributes, numbering, versionsing, folder path, life cycle association, and team template association.

Creating & Mapping Attributes

Additional information

Attributes are defined in an object type, such as a CAD Document, Document, and WTPart. Windchill attributes are defined in the Attribute Definition Manger mapping CAD Document parameters and other object types. For example, in order for Windchill to view or search for a Creo parameter, a Windchill attribute is setup to map or link the Creo parameter when the Creo object is checked-in.

Change Management Options
Configure Out-of-Box Change Process

Additional information

Change management is the process of controlling and recording information and decisions involving engineering change, and the change of other revision-controlled business objects. The Windchill Change Management process followings the industry standard Change Management 2 process (CM2). It uses four change objects to capture the modification of an object, Problem Report, Change Request, Change Notice, and Change Notice Task. Review the Change Management Process by going here .

Change Process Mentoring

Additional information

Mentoring will be provided to understand the Windchill Change Process to the customer. This will aid the efficiency of implementing the Change Process to the organization. A one day (8 hours) mentoring session is included for this option. .

WTPart & End Item Options
Define Basic Life Cycle & Transitions

Additional information

Life Cycles define the stages or states of maturity for a data object. It provides visible status to the community. Business administers apply business logic and access control permissions to the life cycle states. Life Cycles include transitions that are predefined actions that provide business logic and enable life cycle movement. Most transitions are performed by users from the actions menu. For example, a CAD document has a In-Work, Released, Obsolete, and a Under Review state.

Define Object Initialization Rules

Additional information

Object Initialization Rules control the behavior of the Windchill objects. Business administrators configures the OIR to set the behaviors and associations of an object. The rules are written in XML, assigned to a specific object class, and can be defined a all contexts. The OIR affect the object attributes, numbering, versionsing, folder path, life cycle association, and team template association.

Creating & Mapping Attributes

Additional information

Attributes are defined in an object type, such as a CAD Document, Document, and WTPart. Windchill attributes are defined in the Attribute Definition Manger mapping CAD Document parameters and other object types. For example, in order for Windchill to view or search for a Creo parameter, a Windchill attribute is setup to map or link the Creo parameter when the Creo object is checked-in.

Advanced Configurations
Creating Folder Domains

Additional information

Folder domains enable an administrator to develop custom polices or rules that apply to the context folders. This allows folders to include access control polices. Any folder can be assigned to a folder domain.

Extending & Subtyping Objects

Additional information

Soft types are Windchill objects that are instances of the out-of-the-box business objects. They augment a primary business object by adding additional attributes, or by adding new object types with different attributes sets without changing the object model and writing extensive code. The soft type objects are created at runtime not requiring recompiling or interrupting operations, and are none-modeled. They allow to set type specific polices; configure rules that govern the business behavior of each object type. Business administrator’s has the capability of customizing the information capture in the system by using soft types.

Customization Options
Defining Custom Workflow Processes

Additional information

Workflows define the business process and establish the specific events and tasks that occur typically during a change or promotion request. Workflows can be built to define the process for a single life cycle state or entire business process. Life cycle templates associate the workflow template to a given object. Workflows include connectors, activities, and robots for a business process. They define the deliverables and tasks that a user will be performing. They can be defined at any context.

Expression Workflow Robots

Additional information

Robots automate tasks within a workflow to enforce process consistency and improve process performance and enabling a business administrator to automate many common process tasks. Expression robots enable to notify users, perform a standard set of functions by using the Windchill Java API or Info*Engine tasks.Expression robots allow specific tasks to be executed by a custom business event.

Define Info*Engine Tasks

Additional information

Windchill Info*Engine provides a flexible, standard base foundation to automate specific tasks and transfers information to other third party applications. It is an engine that includes standard adaptors to perform various tasks.

Uses application and technology adapters to meet integration needs.

Manages transactions such as synchronous/asynchronous operation modes and parallel processing.

Supports Java native and XML representations

Define JSP for Info*Engine

Additional information

JavaServer Pages (JSP) is a core technology of J2EE (the Java 2 Platform, Enterprise Edition) and solutions based upon EJB (Enterprise Java Beans). Info*Engine supports the development of enterprise custom Java applications and provides a JSP processor as an extension of the Info*Engine servlet engine. The JSP processor dynamically translates JSP pages into servlets. Customers can develop custom Windchill pages for specific needs.

Define SOAP & DAO for Info*Engine

Additional information

Info* Engine takes advantage of Service-Oriented Architecture (SOA) with the support for SOAP (Simple Object Access Protocol) and WSDL (Web Service Definition Language) Web Services Technologies.

Info*Engine supports J2EE, including JSP libraries, JMS (Java Messaging Services), and Java Connector with automatic DAO (Data Access Object) and EJB (Enterprise JavaBeans Technology) generation.

Define Java Applications

Additional information

Windchill includes a Java language toolkit. It gives administrators the ability to develop Java programs that access the internal components of a Windchill session, and to customize or automate Windchill objects. Windchill provides a large library of Java methods to provide automate Windchill task.

Add on Options - Options below can be added to any package for an additional cost.
2 Phase Workflow Expression Robot

Additional information

A 2 phase Workflow Expression Robot is a custom workflow robot that uses the Windchill Java API to automate an object’s revision attribute change for a 2 phase life cycle. The robot is located in the Promotion Request or Change Notice workflow. The Java code included in the robot typically determines if an object contains an alpha or integer revision value when promoted to the Released state. Then will change the revision of the object from a set of conditions.
For example, a product defines three states in a CAD Document life cycle, (In-Work, Prototype, Released). When a new CAD document is checked-in, it obtains the In-Work state and is assigned to revision 1. When the CAD document is approved for release, the expression robot changes the CAD document revision from 1 (integer) to A (alpha).