One of the main drivers for descriptions in Agile PLM is the type of part numbering/naming scheme utilized in your environment. An intelligent or semi-intelligent part numbering scheme identifies certain elements of the part. Depending on the extent to which your part numbers contain information about the parts themselves, the description may not need as much information.
However, if you’re using a purely random Part Numbering system, then you’ll want to document information about that part that might normally be captured in a Numbering/Naming scheme. If so, then you’re best off first defining attributes that capture the particular information around form, fit, function, origin, related product or lifecycle status and then including the relevant information in the Description in an ordered way that encourages readability and searchability. Enforcing and automating corporate standards become very important at this point, because the information is only as useful as it is easily parsed, or found.
Unfortunately, if you’re manually entering this information into the Description field, then you’re introducing the risk for user error, which potentially invalidates the information. In response to this perceived problem, “description builders” were designed for Agile PLM that would automatically map attributes and other information to the Description field.
Zero Wait-State’s DescriptionState is one such tool. However, DescriptionState has the advantage of years of development and implementation in a variety of different PLM environments, driving both a robust framework, and a high capacity for customization that is not easily emulated.
DescriptionState is easy to implement, configure and maintain. It can map information from any table on a Part including Supplier and Manufacturer. The mapping logic is kept in an Excel Spreadsheet and making updates is as simple as checking the spreadsheet in and out of Agile.
Watch our "Automate your PLM" webinar to learn more about tools that help enhance your current PLM solution.
