Accelerating PLM Workloads with PTC Windchill and Amazon FSx for NetApp ONTAP: A POC Implementation Guide

Why Amazon FSx for NetApp ONTAP for PLM File Vaults

PTC Windchill relies heavily on file vault storage for CAD documents, engineering drawings, and related artifacts. These vaults demand low-latency access, strong consistency, and efficient storage utilization.

Amazon FSx for NetApp ONTAP provides a fully managed shared storage service built on the ONTAP file system. Key capabilities that align well with PLM vault requirements include:

• NFS and SMB protocol support for cross-platform file access
• Built-in deduplication and compression for storage efficiency
• Multi-AZ deployment options for high availability
• SnapMirror for data replication and disaster recovery
• Capacity pool tiering for cost optimization on infrequently accessed data

POC Objectives

The goal of this POC is to validate that Amazon FSx for NetApp ONTAP can serve as the storage layer for PTC Windchill file vaults in a cloud deployment. Specifically:

• Performance validation — Demonstrate acceptable latency and throughput for Windchill vault file operations (check-in, check-out, search) on FSx for ONTAP.
• Collaboration capabilities — Validate CAD file management and multi-user document collaboration workflows.
• Storage efficiency — Evaluate deduplication and compression gains on typical PLM data sets.
• High availability — Assess failover behavior and disaster recovery readiness using Multi-AZ and SnapMirror.

Architecture Overview

The diagram above illustrates the end-to-end deployment topology. The following numbered steps describe how each component fits into the overall data flow:

[1] On-premises corporate network — End users access the PLM system from the corporate network. Engineering teams use CAD applications and web browsers to interact with Windchill for file check-in, check-out, and collaboration workflows.

[2] AWS Direct Connect — The on-premises data center connects to AWS through AWS Direct Connect, providing a dedicated, low-latency network link. This ensures consistent performance for hybrid operations during migration and for any ongoing on-premises integrations.

[3]Amazon VPC — All cloud resources reside within a Virtual Private Cloud, keeping the application and data private and secure. The VPC spans two Availability Zones with private subnets, route tables, and security groups controlling all inbound and outbound traffic.

[4] Elastic Load Balancer — An Elastic Load Balancer sits at the entry point of the VPC, distributing incoming user traffic across the Windchill Foreground Servers. This provides fault tolerance and ensures no single server becomes a bottleneck during peak usage.

[5–6] Windchill Foreground Servers — Two or more Amazon EC2 instances run the Windchill Foreground Server role. These handle user-facing requests — web UI rendering, file vault operations, search queries, and session management. The load balancer routes traffic evenly across these instances.

[7–8] Windchill Background Servers — Separate EC2 instances run the Windchill Background Server role. These handle asynchronous processing tasks such as publishing, indexing, notifications, and workflow execution. They also coordinate with the CAD Worker servers for file conversion and visualization jobs.

[9–10] CAD Workers — Dedicated EC2 instances run CAD Worker processes (e.g., Creo Worker, Visualization Worker). These perform compute-intensive operations like thumbnail generation, viewable creation, and format conversion. The Background Servers dispatch jobs to these workers as needed.

[11–12] Amazon RDS (Multi-AZ) — The Windchill relational database runs on Amazon RDS deployed in a Multi-AZ configuration. This provides automatic failover, automated backups, and high durability for the PLM metadata, part structures, and workflow state stored in the database.

[13] Amazon FSx for NetApp ONTAP — All Windchill vault data (CAD files, documents, and engineering artifacts) is stored on Amazon FSx for NetApp ONTAP. The Foreground and Background Servers mount FSx volumes via NFS to read and write vault content. FSx for ONTAP provides built-in deduplication, compression, Multi-AZ availability, and SnapMirror replication for disaster recovery.

Prerequisites and Assumptions

Before starting the POC, ensure the following are in place:

• AWS account with permissions to create VPC, EC2, RDS, and FSx resources
• Two subnets, each in a separate Availability Zone
• Active Directory access for domain join and service account management
• Network connectivity between all components (VPC routing, DNS resolution)
• PTC Windchill licenses obtained separately
• Required ports opened in security groups (see Phase 1 below)

Phased Implementation

Phase 1: Environment Setup (Weeks 1–2)

VPC and networking: Create a VPC with subnets in two Availability Zones. Configure route tables and DNS settings.

Amazon FSx for NetApp ONTAP deployment:

1. Use the Standard Create option in the FSx console.
2. Select Generation 2 for current feature support and future compatibility.
3. Choose Multi-AZ (MAZ) HA pair for high availability.
4. Configure storage capacity, provisioned IOPS, and throughput based on your workload sizing.
5. Select an encryption key (AWS managed or customer managed via AWS KMS).
6. Set the ONTAP CLI administration password.
7. Create a Storage Virtual Machine (SVM) and a volume with Unix security style.
8. Configure capacity pool tiering policy based on your data access patterns.
9. Evaluate whether SnapLock is needed for compliance or data retention requirements.

Security group rules for FSx for ONTAP:

Protocol	Port	Purpose
TCP	22	SSH access to ONTAP CLI
TCP	111	Portmapper for NFS port negotiation
TCP	445	SMB access
TCP	635	NFS mountd for mount requests
TCP	2049	NFS server daemon

Compute and database: Launch EC2 instances for the Windchill application tier and provision an Amazon RDS instance for the Windchill database.

Active Directory integration: Join EC2 instances to the domain and assign appropriate service account permissions.

Volume mounting: Mount the FSx for ONTAP volumes on all Windchill servers. Set file and directory permissions to match Windchill vault requirements. Refer to the FSx for ONTAP documentation for mount instructions specific to your operating system.

Phase 2: Data Migration

Data migration from an on-premises environment involves three parallel workstreams:

1. Database migration — Export the Windchill database from the on-premises system and import it into Amazon RDS.
2. Application files — Copy the Windchill application directory from the on-premises server to the EC2 instance.
3. File vault data — Use NetApp SnapMirror to replicate vault data from the on-premises ONTAP system to the FSx for ONTAP instance. SnapMirror provides efficient block-level replication, minimizing migration time for large vault data sets.

Phase 3: Windchill Rehost and Configuration

With infrastructure and data in place:

1. Perform the Windchill rehost procedure to point the application at the new cloud infrastructure.
2. Configure Windchill to use the FSx for ONTAP volume as the file vault location.
3. Validate and reconfigure any Windchill integrations (CAD tools, visualization services, etc.).

Phase 4: Performance Testing and Validation (Week 3)

Testing framework:

• Execute CAD file check-in and check-out operations across a range of file sizes.
• Simulate concurrent user sessions to measure response times under load.
• Test search and retrieval operations against the vault.

Storage performance monitoring:

• Collect ONTAP performance metrics (latency, IOPS, throughput) from the FSx console and ONTAP CLI.
• Set up Amazon CloudWatch dashboards to monitor EC2, RDS, and FSx metrics in a unified view.

Phase 5: Optimization and Results Analysis (Week 4)

• Analyze storage efficiency gains from ONTAP deduplication and compression. A target of 30% or greater storage savings is a reasonable benchmark for typical PLM data.
• Review performance data and identify tuning opportunities (volume layout, tiering policy adjustments, IOPS provisioning).
• Build a cost analysis comparing on-premises storage costs to the FSx for ONTAP deployment, including compute, storage, and data transfer.

Phase 6: Migration Planning and Recommendations (Week 5)

• Develop a phased production migration strategy with defined rollback procedures.
• Document operational procedures for monitoring, alerting, backup, and recovery.
• Plan for team training on AWS and FSx for ONTAP administration.

Success Criteria

The POC is considered successful when the following criteria are met:

Criterion	Target
CAD file check-in/check-out performance	Meets or exceeds on-premises baseline
Concurrent user support	50+ users with acceptable response times
System availability	99.5% or higher
Data replication	Successful replication between on-premises and cloud
Storage efficiency	30%+ savings via deduplication and compression

Conclusion and Next Steps

A successful POC validates that Amazon FSx for NetApp ONTAP can serve as a performant, cost-effective storage layer for PTC Windchill file vaults in the cloud. The combination of NFS/SMB protocol support, built-in data efficiency features, and Multi-AZ availability aligns well with the demands of PLM workloads.

After completing the POC, recommended next steps include:

• Present findings to stakeholders with performance data and cost analysis
• Begin detailed production migration planning for a pilot group
• Finalize AWS resource sizing and licensing agreements
• Provision the production environment and initiate team training

References

• Amazon FSx for NetApp ONTAP documentation
• PTC Windchill system administration guide
• Amazon CloudWatch documentation

Authors

• Niki Willoughby, Cloud Solutions Architect, NetApp
• Preet Virk, Principal Partner Solutions Architect, AWS
• Rajesh Gomatam, Principal Partner Solutions Architect, AWS