Windchill ERP Integration

As far as technology goes, on a high level these are the options available for integration with SAP or Oracle

Java API/ webservices/ Info*engine

- Develop custom integration using various supported APIs available. For eg you can write a custom code, trigger it from a workflow which would send metadata through a messaging system, a web service or even write an XML to a staging directory or to a staging database. If needed,you can even achieve a bi-directional synchronous/asynchronous integration with this and use this in conjunction with JMS/EAI solutions like MQ or web Methods(may be reuse the existing EAI solution). If you go down this path, you are responsible for maintaining your customization across upgrades/updates/patching.

ESI (Enterprise System Integration) - Uses TIBCO as middleware

- PTC offers off the shelf solution adapters for bidirectional communication with SAP or Oracle. With this module you would get a complete closed-loop transaction management as well. This uses TIBCO - Object adapter as messaging system, needless to say this is one of the best EAI suite out there in the market. The OOTB solution will suffice most of the requirements and can be configured as needed. Of course this might turn expensive

ERP Connector (Uni-Directional)

-This offers a uni directional communication (open-loop) light weight method to transfer business objects to any erp solutions. This one does not include middleware solution. The OOTB output from Windchill is XML or you can translate to CSV as well. If this module is installed you will have a RTM workflow, enterprise transaction administration and feature support that enables the creation of plant specific BOMs through distribution targets.This is scalable from an architecture front and can customized to add any required functionalities.

Third Party Windchill ERP Integration - A quick internet search will take you to some thirdparty off the shelf solutions.

A lot of this depends on your business needs

1. What needs to be transfered - Engineering Objects, Manufacturing objects and so on?
2. When and how the transfer should be triggered - release process through ECN(ECN centric or part centric) workflow, adhoc release from menu option, LC state change etc.
3. How frequent is the transfer, the volume of transfer, unidirectional/bidirectional, synch/asynch?
4. CRUD operations supported on each systems - Which one is SOR?
5. If integrating existing systems, how to handle the history?
6. and .......

Hope it helps.

Binesh Kumar

Medtronic - MITG