Version: Windchill 12.1
Use Case: (1) Manually update option set-related information based on BOM information defined in other systems. However, this is not a realistic answer considering the frequency and accuracy of data updates. (2) Implement by customization by Info*Engine. However, it is necessary to use unsupported option set related classes. Since classes related to option sets are not supported, there is a possibility that the functionality will be removed when Windchill is updated. TMC(Toyota Morter Corp.) is in the process of implementing Windchill BOM (EBOM/MBOM/BOP) for production use in April 2025. Currently, TMC designers are using "TMC's own system" to perform tasks equivalent to "defining BOM information. The TMC designers are currently using "TMC's own system" to perform tasks equivalent to "defining BOM information. In the future, TMC plans to use Windchill to define BOM information. However, due to the business process changes involved, this is not expected to be realized until the second half of 2025 or later. Therefore, we would like to define BOM information in "TMC individual system" outside of Windchill during the period from April 2025 production use to the second half of 2025 or later, and then automatically import the definition contents into Windchill using REST API. Unfortunately, this is not possible because there is no REST API related to option sets in the "BOM information definition".
Description:
There is no way to automatically update option set related information in Windchill based on BOM information defined in other systems.
