AIMS is the common link between most systems, and the AIMS cabinets supply a digital signal for engine fail warnings. The Flight Management Computing System within AIMS will use this to determine EO ops. The FMC puts the EO SID into the route as a modification if an engine failure is sensed, and the flaps are extended, and the navigation database has an EO SID for the departure runway.
Generically, the EEC is monitoring engine parameters, and outputs engine data and system status to the systems ARINC 629 buses (through the Engine Data Interface Units (EDIUs)), from which AIMS and other systems will use the data. AIMS also receives analogue N1 & N2 data direct from the tachometers for use when there is no digital engine speed data (e.g. EEC failure).
For Thrust Asymmetry Compensation, the TAC function receives thrust data for the two engines from the EDIUs. The EDIUs use the N1 signals from the EECs to calculate the thrust values. The EECs also send other engine data to the EDIUs to make sure that the thrust value is accurate. The EDIUs send the engine thrust data to the PFCs through AIMS. The PFCs use the difference between the thrust signals to calculate rudder and rudder trim commands.