# Enterprise Communication Interface (ECI)

## Responsibility

Agile e6 is the organizational master of the Inter-Process-Communication (IPC).

This means:

- All CAX processes communicate always with Agile e6.
- If a new document is to be processed, Agile e6 may automatically determine the suitable application and start it with the corresponding file resp. data base.
- The communication between two CAX processes is always performed using Agile e6. (Example: Transfer of MCAD geometry to ECAD via IGES is performed using "check-out", "preprocessing", "postprocessing" and "check-in").

| Agile e6 manages only those CAX objects/structures, which are meaningful in an independent object in the design and release procedure of a company.

This means:

- Independent Agile e6 objects are e.g. application related CAX data bases, single parts, drawings, 3D models, spare lists etc., but generally not the CAX base elements itself (e.g. CAD lines, solids, layouts of drawing frames, DTP layouts etc.).
- Subordinate, internal CAX structures are unknown in Agile e6 and may be manipulated by the user with specific CAX system.
- The user must apply an Agile e6 function resp. an Agile e6 check to load, store, delete, copy, etc. any Agile e6 relevant CAX object and corresponding structures.
- Independent of the start up, the action is usually performed first in Agile e6 and after check of correct result repeated in the CAX system. If an error occurs the user is informed by an appropriate error message and has the option to UNDO the action on the Agile e6 system.

The responsibility for all CAX internal relations has definitely the CAX system itself, because only the CAX system has all necessary information to manipulate them (e.g. position, rotation, layout etc.).

Therefore, in Agile e6 no actions may be performed, which change the internal relations of structures managed by the specific CAX system.

Agile e6 requires therefore an object -identification "source system" and the user may only apply informational attributes.

Manipulations of the CAX structure resp. objects (e.g. create, move, delete, copy, etc.) are generally initiated on the CAX system.

The object names (especially of physically copiep objects) must be unique:

- Agile e6 manages internally an unequivocal count number.
- A unique relation to the CAX document is maintained via the document master attributes resp. the CAX keys contained in the Agile e6 file management.