Where to place “Product Hierarchy” data in Agile PLM?
I am new to the Oracle Agile PLM product (v9.3.6).
Our company needs to enter their product feature hierarchy (i.e. categories / taxonomy) into Oracle Agile PLM ideally to be in one place instead of maintaining it on a separate Excel file or DB. Appreciate if anyone has a suggestion on where to place this data in PLM (or even extend/customize PLM)?
We don’t want to buy PIM or PDQ.
You can do this but remember that PIM-centric (or product portfolio) data is highly susceptible to change and when speaking to large numbers of parts that could prove a daunting task to update. First I would explore which subclasses would require the data be added… i.e. most companies do not include screws and such unless you retail these items. Once the subclass list is decided upon I recommend adding the segment fields to page two and, on the initial data entry, import without causing a change. Then you would need to decide if these are change required fields (most likely an MCO) and either turn that on or provide teh privileges to update to a select few. If this data needs to move to ERP or other down stream apps then it will need to be under change control of course.
I have seen the use of document hierarchies in PLM for such needs. Think of a BOM only made up of documents. For instance, market requirements can start with global requirements at the top, regional under them and country under those. The same concept for a product hierarchy: base product info at the top with variants under them–the reverse of a product BOM.
