# Enterprise Communication Interface (ECI)

## Agile e6 Environment

Important aspects of the application of Agile e6 are:

- a heterogeneous hardware environment,
- a window oriented user interface, and
- a variety of CAX applications, which must be linked to Agile e6.

Base is an ETHERNET network with protocol TCP/IP running:

Example:

If different workstations work simultaneously with MCAD and ECAD systems, their data model should be managed uniformly with Agile e6.

The central management of the Agile e6 data itself is executed on a data base server, which exchanges BOM data with a MRP system from time to time.

The technical documentation is performed finally by using a DTP system running on a PC and should also be managed with Agile e6.

Therefore, the hardware and software environment and the desired mode of operation results in following requirements:

- The user will work simultaneously with different CAX processes .
- The user requires for the CAX data management an own Agile e6 process running on his workstation.
- For optimal work the user requires an asynchronous link of the specific CAX processes with the Agile e6 process (i.e. simultaneous working).
- If the CAX process calls an Agile e6 function (e.g. Store with Agile e6), a synchronization between the CAX process and the related Agile e6 widget must be executed (the CAX process and the related Agile e6 widget remain captive until the transaction in Agile e6 is finished).