Windchill Gateway for I-deas TDM
Windchill 9.1 introduces support for the I-deas Gateway for Windchill PDMLink. This provides I-deas users with the ability to publish data stored in the TDM library to the Windchill environment. Leveraging this capability exposes TDM data to the enterprise, and integrates the I-deas TDM environment with the product lifecycle management capabilities of Windchill.
PDM & Process Solutions
PTC Windchill Integrations
|Product / Module||
PTC Windchill ECAD/MCAD Integrations
PTC Windchill PDMLink
|Product Functional Area||
Structured Content Management
|User Interface Location|
|Processes, Initiatives, and Best Practices||
Benefits and Description
The Windchill® Gateway for I-deas® TDM connects the I-deas TDM design community with the extended product development environment of Windchill by publishing the information for parts, assemblies, drawings, product structures and ProductView data from the TDM vault to Windchill. I-deas users continue to work in their native I-deas environment. Part, assembly, and drawing files are published and uploaded to the PDMLink sever based on previously scheduled publishing tasks. The published parts, assemblies, and drawings are stored on the PDMLink server along with their viewables for use in ProductView. By integrating distributed design and development activities, the I-deas Gateway significantly reduces the time it takes to bring complex and innovative products to market.
I-deas Gateway service operates by extracting the object’s definition, product structure information and metadata information. This content is published and stored to the Windchill server and automatically associated with PDMLink objects to describe the product structure at the enterprise level. In addition to publishing to the standard Windchill object model, I-deas Gateway can be customized to account for specific requirements. The I-deas Gateway supports Windchill Visualization Service (WVS) for visualization of published parts and assemblies using Windchill ProductView. The Windchill administrator can define publishing criteria on the basis of an object's attributes in I-deas and scheduled intervals. This provides flexibility for controlling the timing of an object's availablility to the enterprise and how frequently publishing should occur. System architecture allows you to publish objects either on a specific interval or an on-demand basis using an overnight batch process.