The IFS Applications integration with the ShipConstructor Software provides a robust exchange of data between these systems. The integration uses EIS to transfer Bills of Materials (BOM), viewables, part numbers, attributes and more between assembly drawings automatically created by ShipConstructor and IFS Application suite. It provides real-time updates of BOM changes into the IFS ERP application, streamlines data flow between the engineering, manufacturing and purchasing departments, eliminates manual data entry or processes of large sets of data and insures that manufacturing and purchasing has access to the most up to date BOM and drawings inside the IFS.
Out-of-Box Integration between ShipConstructor Software and IFS ERP
Integration features:
- Robust exchange of data between AutoCAD with ShipConstructor and IFS ERP systems
- Transfer BOM table from AutoCAD into IFS BOM
- Transfer of AutoCAD 2D drawings as Viewables
- Flexible, modular data transfer Etrage Integration Server (EIS) “backbone”, with AutoCAD with ShipConstructor and IFS ERP-specific plug-ins
- Transactional, with reliable retry mechanism in case of failure
- Observable in real-time. Fast and scalable. Database-portable
- Out-of-box functionality and flexibility at a competitve price
- Works with AutoCAD 2011 and 2012
- Supports ShipConstructor 2013 & 2014
- There are three main components to EIS. The EIS Backbone which connects and enable communication between application plug-ins, the Configurator to connect the integration actions together and the Monitor to observe execution of the various actions as they occur in real-time.
The EIS Configurator is used to “chain” the integration actions together. This way, EIS can be tailored to the customer’s existing IT infrastructure in a visual, understandable and flexible manner. Once actions are chained, they automatically communicate with each other until unchained.
Integration actions are triggered in response to events in the system, such as releasing objects in PDM or through a direct user action. Through the EIS Monitor, the user can see the action executions as they happen. If for any reason an action fails, that fact is recorded in the EIS backbone, so the action can be retried at later time.
