Do your NX users need a better way to manage design issues? Come see how!
In business, Issue Management refers to the discipline and process of managing business issues and usually implies using technology to electronically automate the process. Electronic issue management has gathered steam as a business and technology movement in recent years as mid-sized and large businesses have realized the advantage of implementing systems to manage, document, and track work.
An issue tracking system is a computer software package that manages and maintains lists of issues, as needed by an organization. Issue tracking systems are commonly used in an organization’s customer support call center to create, update, and resolve reported customer issues, or even issues reported by that organization’s other employees. An issue tracking system often also contains a knowledge base containing information on each customer, resolutions to common problems, and other such data. These issue tracking systems almost always use standalone programs or internet browsers. To capture an issue related to the use of engineering software packages, customers are usually forced to switch back and forth between multiple software applications and perform many of the capture steps manually.
In environments where multiple designers contribute to product design, analysis and/or manufacturing (particularly where these teams are geographically distributed) effective communication of issues can be challenging. When issues are specific to an NX design, and effective resolution requires context information like an assembly configuration state or specific validation results, communication of this data through traditional issue tracking mechanisms (like shared Excel spreadsheets) can be very challenging. How can designers using NX report issues in real-time, capturing issues while attaching necessary issue data, without leaving the design environment?
NX Issue Management provides distributed teams with the ability to raise, share, and resolve NX-related issues while efficiently capturing assembly context and other relevant NX-specific data as part of the issue. The initial implementation uses Teamcenter Community Visual Issue Lists as the collaboration engine and central database for storing issues, allowing issues to be created, shared and/or reviewed directly using the Teamcenter Community Visual Issues tools as well. Visual issues originally created in Teamcenter Community can also be retrieved and updated directly using the NX Issue Management tools.
With the new ability to directly capture and retrieve important design issue data like NX assembly context bookmarks, validation results from Check-Mate, and/or any related 2D screen capture images — all without any manual copying and pasting, or temporary saving of image or bookmark files to a local drive) engineering teams using NX and Teamcenter Community will find that product design issues can be described more quickly and completely than was previously practical, and that the communication and resolution of issues can greatly accelerated. Please join us in the NX Validation Track to learn more about this exciting new capability.
Kelvin Zhang, PhD
Siemens PLM Software
KDA Validation Development
Shanghai, China