Teamcenter® software’s classification and re-use capabilities enable companies to manage previously created product definition data in digital libraries that design engineers can subsequently use in new product initiatives or continuous improvement programs. Manufacturing engineers can also use these capabilities to evaluate alternative and substitute parts before finalizing their designs. By providing product developers with rapid access to validated and/or standardized design definitions, Teamcenter facilitates component and supplier management (CSM) and its related advantages.
By allowing you to manage previously designed, validated and approved product and tool definition data, the Teamcenter classification and re-use capabilities expedite product development, reduce its cost and build design intent and lessons learned into your new product initiatives.
Most new product offerings – and all continuous improvement programs – include numerous design elements that have already been used in earlier products. Typically, these re-usable elements constitute up to 85 percent of the new offering’s design content. Teamcenter enables manufacturing engineers to re-use existing tools instead of creating new tooling every time.
While Teamcenter classification and re-use capabilities are tightly integrated with NX™software, you can easily integrate these capabilities into your existing applications. As a result, application users can search your library for a part/component and bring its associated 3D models, 2D designs, specifications, tooling, part files and documentation into their sessions without leaving their application interface or desktop.
Teamcenter provides a variety of classification and resource management tools that enable you to quickly build a digital library. Teamcenter lets you categorize your definition data on the basis of hierarchical classifications. You can establish attributes for each class, including physical characteristics (such as height, weight, density, color and material) that designers can use when searching your library.
You can also classify definition data by accounting for product-related intentions. For example, to enable designers to quickly locate design information about the fasteners in your library, you could describe each fastener in terms of:
• Its level of quality
• Available suppliers and approved vendor list
• Locations where the fastener can be assembled into a full product
• Whether the fastener being described has been approved for prototype or high-production use
You can establish rules, user identifiers and role definitions to make certain that individual users only access library information that they are entitled to employ.
In this scenario, you can build design intent, lessons learned, re-usable product structures, generic design elements and substitutable real life parts into the process you use when executing new programs. Template based processes enable you to take advantage of cataloged design rules, design requirements and approved design elements.
Template-based design enables an automaker’s engineer teams to quickly fill their product configurations with preferred or optimized design elements that team members can access, view, validate and change using their everyday CAD/CAM/CAE tools.
Teamcenter lets you categorize your definition data on the basis of hierarchical classifications. You can establish attributes for each class, including physical characteristics (such as height, weight, density, color, and material) that designers can use when searching your library.
Teamcenter classification enables to build of hierarchies, classes, attributes, and valid attribute values into class definitions. This enables design engineers to quickly search the library when they want to locate a particular design element and reuse its related product and process data in a new project or program.
Classification is used to create and maintain a hierarchical classification structure based on the attribute values of your workspace objects. We can use Classification to: Add classification objects (ICOs) to the classification hierarchy. Classify workspace objects.