<p>Main discussion points:</p>
<ul>
<li>The linking plug-in and proposed workflow was discussed
<ul>
<li>test example - https://testeamlogbook.cern.ch/LBQLHC/log2/122051</li>
</ul>
</li>
<li>for activating the linking plug-in and sharing feedback EAM support should be contacted - eam.support@cern.ch</li>
<li>For systems under the TIOC umbrella a separate discussion will be held mid-march to agree on an internal workflow and linking
<ul>
<li>to be kept in mind that TIOC is not using EAM logbook yet but it is under development, EL &amp; CV partially use it</li>
<li>main discussion point is whether the TIOC event links to AFT or the equipment group event - from AFT perspective it is important that link to relevant information exists</li>
</ul>
</li>
<li>CV pointed out that an eventual automatic creation of EAM logbook entry from AFT side would be very useful - in comparison to EL they also do not have the situation where multiple machines are impacted by a single problem (as is the case with electrical perturbations)</li>
<li>For the EL PMU/perturbation monitoring use case, it needs to be reviewed whether the events should directly populate AFT (but only for the beam impacting sub-set) or rather to EAM (for all events) and those impacting the beam linked to AFT. A discussion for that is foreseen mid-March.</li>
<li>for CRG the use-case for the linking plug-in is not so clear yet</li>
<li>it was agreed to try out the plug-in for some key scenarios and provide the feedback for both the integration development and to identify the best workflows</li>
<li>a follow-up meeting is foreseen in Q2 2025 to discuss experiences made so far</li>
</ul>