Managing Software Parts
Software parts for second-party and third-party integrations such as Integrity, IBM Rational ClearCase and Subversion are managed using the part functionality in Windchill.
A part in Windchill is a logical database representation of a physical item, or embedded software, used to build a product. A part has a name, a unique number, a version, and other attributes such as default unit of measure, lifecycle state, working status, or source.
Parts are also used to organize product information through database relationships to all forms of product definition data including design, manufacturing, and quality documentation. Related data is seen in tables and expandable data structures throughout Windchill.
The part usage relationship connects parts to each other in multi-level product structures. Product structures capture the composition of a product as it changes over time. It may be filtered to show the configuration of products produced in the past, currently in production, and planned for the future. Product structures can also contain optional parts that can be configured according to functional and marketing driven rules, and filtered to show allowable modular combinations. Product structure reports such as multi-level bills of material and parts lists can be programmatically created and output as reports. Finally, product structure information is transferred electronically to manufacturing systems such as enterprise resource planning (ERP) using Windchill ESI.
Software parts are maintained in Windchill from Products > Folders, Projects > Folders, or Libraries > Folders in Windchill.
Было ли это полезно?