# Windchill Private AI Layer Blueprint Generator

> Source: https://netray.co/tools/windchill-private-ai-layer-blueprint-generator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Generate a shareable architecture plan for a private AI assistant on Windchill, built on Windchill REST Services and your own GPUs.

## Category

engineering-plm

## Erp

PTC Windchill

## Audience

- PLM administrator
- IT architect
- Engineering manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Northfield Defense Electronics

#### Windchill version

**Key:** version

**Type:** select

**Options:**

- 11.x
- 12.0
- 12.1
- 13.x

**Default:** 12.1

#### Database engine

**Key:** database

**Type:** select

**Options:**

- Oracle
- Microsoft SQL Server

**Default:** Oracle

#### Hosting

**Key:** hosting

**Type:** select

**Options:**

- On-prem server
- Private cloud
- Air-gapped

**Default:** On-prem server

#### Named users

**Key:** users

**Type:** number

**Default:** 250

#### Sites or plants

**Key:** sites

**Type:** number

**Default:** 2

#### Main use cases

**Key:** usecases

**Type:** textarea

**Default:** Part and BOM lookup, change notice impact, document Q and A, lifecycle state questions.

#### Data that must never leave the site

**Key:** never_leave

**Type:** textarea

**Default:** Controlled drawings, program specific designs, supplier cost data.

#### GPU available

**Key:** gpu

**Type:** select

**Options:**

- None yet
- 1 x 48 GB
- 2 x 80 GB
- 4 x 80 GB or more

**Default:** 1 x 48 GB

#### Target go-live

**Key:** golive

**Type:** date

**Default:** 2027-04-30

**Blocks:**

#### 1. Context

**Body:** {{company}} operates Windchill {{version}} on {{database}} ({{hosting}}). Users in scope: {{users}} across {{sites}} site(s). Target go-live: {{golive}}.

Use cases:
{{usecases}}

Must stay on site:
{{never_leave}}

#### 2. Components

**Table:**

**Columns:**

- Component
- Design for Windchill {{version}}
- Notes

**Rows:**

**0:** Data access path

**1:** Windchill REST Services (OData) as the asking user; confirm entity sets from the $metadata of your server

**2:** Info*Engine or custom Java only for gaps

**0:** Retrieval index

**1:** Local index over document content with object reference, version, iteration and lifecycle state on each chunk

**2:** Filter to released data where required

**0:** Model serving

**1:** Open-weight model on vLLM, GPU: {{gpu}}

**2:** Local embeddings and reranker

**0:** Tool server

**1:** Named actions: find part, BOM, where-used, change notice status, document search

**2:** Bounded parameters, read-only

**0:** Identity and permissions

**1:** SSO identity to Windchill; domain policies and context team roles applied by the server

**2:** Live re-check before showing text

**0:** Audit

**1:** Append-only record of prompts, REST calls and object references

**2:** Immutable storage

#### 3. Security controls mapped to your inputs

**Body:** Hosting is {{hosting}}, with no outbound route from the model host.

For {{never_leave}}: contexts holding this data are indexed only if their access rules can be mirrored; otherwise they are excluded and queried live through REST only.

No write-back in phases 1 and 2. Phase 3 actions use supported REST operations or vetted services after user approval.

#### 4. Rollout

**Table:**

**Columns:**

- Phase
- Scope
- Exit criteria

**Rows:**

**0:** 1: Read-only

**1:** Part, BOM, document and change questions for one product context

**2:** Accuracy against a reviewed question set

**0:** 2: Drafts

**1:** Change notice summaries, review packs

**2:** Draft acceptance by reviewers

**0:** 3: Approved actions

**1:** Supported actions with approval

**2:** Audit and rollback verified

#### 5. Open questions for IT

**Body:** 1. Is Windchill REST Services enabled and which domains are exposed?
2. How does SSO reach the Windchill web tier?
3. Which contexts hold controlled data?
4. Is a reporting replica of {{database}} available?
5. How are vault contents read for extraction?

**Signatures:**

- Prepared by
- PLM owner
- IT security

**Notes:** A starting plan. Verify REST domains, entity names and access rules with your Windchill administrators.

## Content

**Intro:** Use this generator to draft an architecture plan for a private AI assistant on PTC Windchill. It frames the data path around Windchill REST Services and the identity of the asking user.

**Sections:**

#### How to use it

**Body:** Enter your Windchill release, database and hosting model, then describe the use cases in plain language. List which contexts hold data that must stay on site. Export the plan and use it to start the review with your PLM owner and security team.

#### The method behind it

**Body:** Authoritative reads use Windchill REST Services, which applies policy rules and team roles for the calling user. Documents are indexed with their object reference and state so retrieval can respect lifecycle. The model is open-weight and local. Anything that cannot be mirrored safely is queried live or excluded.

#### Reading the plan

**Body:** The components table is the part to challenge. For each row ask who owns it, which release it depends on and how it is tested. The rollout table states exit criteria so the project does not drift from read-only questions into actions before accuracy is shown.

#### Common mistakes

**Body:** Do not use a single integration user for everything, and do not assume REST domains are identical across releases. Also note versions and iterations: answers must say which iteration they came from.

**Cta:** If you want this plan reviewed against your Windchill setup, Netray can do that. The generator is free to use on its own.

**Faq:**

#### Why Windchill REST Services?

**Answer:** It is the supported modern API, uses OData query options and applies the calling user's permissions. Older estates may still rely on Info*Engine or custom services, which the plan allows for gaps.

#### Does it cover Windchill in PTC's cloud?

**Answer:** No. It targets installations you host yourself, where you control the network boundary and the GPUs.

#### Is the output legally binding?

**Answer:** No. It is a planning document that you adapt. Have your administrators and security team confirm each statement for your environment.

#### What about CAD data?

**Answer:** The assistant works with metadata, structure and document text. Geometry is not readable by a text model, so plan expectations accordingly.

## Search terms

Windchill AI architecture, Windchill REST Services AI plan, Windchill on-prem LLM, PTC Windchill AI blueprint, private AI Windchill, Windchill assistant design

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json