PLM Case Study · Windchill + ThingWorx

ThingWorx Navigate Change Request and Problem Report Workflow for Windchill

By PSPTechHub ·

Engineer creating a Windchill change request and completing a workflow task in a customized ThingWorx Navigate app

Summary

When something goes wrong with a product, or a design needs to change, the request has to go through Windchill, the system that holds the company's product designs. Most people who spot these issues never use Windchill. PSPTechHub gave them a simple screen in ThingWorx Navigate where they can report a problem or ask for a change in a few minutes, and let reviewers approve, question or reject it from the same screen. Windchill still records and controls everything in the background.

The Problem: Only Windchill Users Could Raise a Change

In a factory, problems and improvement ideas come from everyone: the shop floor, quality, service and sales. But every change to a product had to be raised in Windchill, a powerful but complex engineering system that most of these people did not have and were not trained on.

Most people could not raise a change

Only Windchill users could log a problem or request a change, so others had to email an engineer and wait for them to type it in.

Requests arrived incomplete

The ready-made simple screen asked for less information than Windchill needs, so engineers had to chase people for missing details.

Reviewers had to switch systems

Anyone asked to review a problem or answer a question had to go into Windchill to do it, which slowed approvals.

Hard to find in the first place

The web address for the app was long and hard to share, so people did not know where to go.

The Solution: Simple Apps Anyone Can Use

PSPTechHub built three simple apps inside ThingWorx Navigate, the easy-to-use window onto Windchill. Anyone can use them in a web browser without learning Windchill, and every request lands in Windchill exactly as if an engineer had typed it in.

Report a Problem

Anyone can describe a problem with a product or document in a short form, and it goes straight to the right engineering team.

Request a Change

A clear form asks for everything engineering needs up front: what to change, why, how urgent it is and by when.

Point to what is affected

Users pick the parts or documents the problem or change affects, so engineers know exactly what to look at.

Checks before sending

The form flags any missing answer before it is sent, so no request arrives half-filled.

One click to submit

Pressing submit creates the request in Windchill and starts its review — no extra steps for the user.

My Tasks inbox

Reviewers see every problem or change waiting for them in one list, with the details, files and history in one place.

Decide from the same screen

Reviewers can approve, ask a question, mark it as a duplicate, say it can't be reproduced or pass it to someone else, and leave a comment.

Same permissions as before

People can only see and do what they are already allowed to in Windchill, so nothing becomes less secure.

Short, easy web address

One short link opens the apps, so it is easy to share across the company.

How It Works: From Problem to Decision

  1. 1

    Open the link

    The user opens one short link and sees three tiles: Report a Problem, Request a Change and My Tasks.

  2. 2

    Fill in a simple form

    They describe the problem or change, how urgent it is and when it is needed.

  3. 3

    Add what is affected

    They choose the parts or documents involved.

  4. 4

    Submit

    The request is saved in Windchill and its review starts automatically.

  5. 5

    Reviewer is notified

    The right engineer sees the new item in their My Tasks list.

  6. 6

    Decide and comment

    The engineer approves, asks a question or passes it on, and everyone can see the outcome and comments.

For IT Teams: How It Is Built

ThingWorx Navigate gives users simple screens, and Windchill stays the official record for every workflow, permission and decision.

  1. Customized Navigate landing page
    Request a Change, Report a Problem and My Tasks tiles behind a short URL
  2. Navigate mashups
    Custom layouts for forms, task table, task overview and CR details
  3. Project Things
    Change request, problem report, task and helper services
  4. Custom Windchill OData connector
    Every Windchill API call, with SSL client authentication
  5. Integration Runtime & Windchill
    PTC-recommended link to Windchill, the system of record for workflows

ThingWorx services built

ThingWorx components in the Navigate change workflow
ServicePurpose
Windchill OData connector (project)Holds all Windchill REST / OData services for the customization
Create Change Request ThingBuilds the request body, creates, reserves and submits the CR
Create Problem Report ThingCollects problem report details and creates the PR
Task App ThingRetrieves task data for My Tasks
Helper ThingShared services that support task completion and routing

Design decisions

  • PTC's recommended Navigate–Windchill connectivity is kept unchanged; customization sits on top
  • A separate project OData connector so new services deploy to every environment
  • Read-only out-of-the-box mashups were duplicated and customized, not edited
  • Windchill stays the system of record for workflows, permissions and routing
  • My Tasks scope limited to Analyze Change Request, Analyze Problem Report and Clarify, so each layout is built properly
  • Form validation and reset tested case by case: empty fields, blank-space names, missing reason, need date and description

Outcomes

Anyone can raise an issue

People across the company report problems and request changes without a Windchill licence or training.

Complete requests first time

Engineers get all the information they need, with less back-and-forth.

Faster reviews

Reviewers decide from one inbox instead of switching systems.

Nothing gets lost

Every request, decision and comment is recorded in Windchill.

No change to security

Everyone keeps exactly the access they already had.

Easy to roll out

One short link and three tiles mean very little training is needed.

This solution fits if you need to…

  • Create a Windchill change request from ThingWorx Navigate
  • Let non-Windchill users submit problem reports into the Windchill workflow
  • Complete Analyze Change Request and Clarify tasks in ThingWorx Navigate
  • Add custom Windchill attributes to the Navigate Request a Change app
  • Build a custom Windchill OData connector in ThingWorx

Frequently Asked Questions

Can people without Windchill raise a change request?

Yes. With the apps PSPTechHub built in ThingWorx Navigate, anyone with a browser can request a change or report a problem, and it is created in Windchill automatically.

What is ThingWorx Navigate?

ThingWorx Navigate is PTC's set of simple web apps that let non-engineers see and work with Windchill information without learning Windchill itself.

What is the difference between a problem report and a change request?

A problem report says something is wrong. A change request asks engineering to change a product or document, often to fix a reported problem.

Can reviewers approve requests in ThingWorx Navigate?

Yes. Reviewers open My Tasks, look at the details and files, and approve, ask a question, mark a duplicate or pass the item on, with a comment.

Is it still secure if people do not log into Windchill?

Yes. Each person can only see and do what their Windchill permissions already allow.

Why not use the standard ThingWorx Navigate apps?

The standard apps ask for less information than Windchill needs and only handle some review tasks. The custom apps capture everything and cover problem reports and questions too.

Which versions were used?

ThingWorx 9.6 and ThingWorx Navigate 9.6, connected to Windchill.

Need Windchill Workflows in ThingWorx Navigate?

PSPTechHub builds ThingWorx apps that bring Windchill change requests, problem reports and tasks to every user through ThingWorx Navigate.