We have arequirement to provide our part descriptions (BOLT, HEX) in at least 5 specific languages for use on shipping documents. To my knowledge we don't have any other requirements and all internal documentation like engineering drawings, manufacturing planning and supply chain documents will be exclusively in English.
Currently,we have a division thatis supplying this information through their PLM system. There are five free-text fields associated to the part and language output is selectable by the user running the report or shipping document. A BOM of parts can be output in at least English, French, German, Spanish, and Italian. The fields are populated manually either at part creation or some other phase of the process. We have a requirement to replace this capability when we replacetheir PLM systemwith Windchill.
Current state in Windchill at Solar San Diego is that the description of the part is determined by the system through the classification taxonomy in PartsLink. A part would be classified under the BOLT node and further under the HEX node and a program constructs the description BOLT, HEX and populates PLM and ERP with the standard description. This is currently a customization we can modify. We need to adapt this to the multi language requirement.
We know we are not talking about "translation" here. We understand the word BOLT (or whatever) won't translate into something that means a threaded fastener in every language. Further, we understand that BOLT, HEX as a phrase has even less promise of being "translated" correctly into several languages.
What we would like to verify somehow is that if we insert into our Taxonomy structure the equivalent word for BOLT for every language we want and the correct word for HEX in every language we want, would we arrive at an acceptable part description of BOLT, HEX that would be understood in each language and we could keep our standard description capability across multiple languages with rigid control over how the descriptions are constructed without entering each one manually. Of course this is a very simple example for proof of concept only.
Any thoughts on this or other approaches for our situation?
Do any of you have this requirement? How are you dealing with it?