<p>Here are the point that I noted about our discussion for the VFC FESA SW</p>

<p>- averaging sum-sum 50 values</p>

<p>- offset/scaling factor to be set by BI BCT experts</p>

<p>- test and migration to 64bit</p>

<p>- interface for OP (fesa properties)</p>

<p>- turn by turn acquisition triggered by intensity changes (injection or dump)</p>

<p>- post-mortem and xpoc</p>

<p>- only system A for operation</p>

<p>Other</p>

<p>- the FESA server is available however to minimize the work for the different users and their application, the communication interface will be the same as for the dab server.</p>

<p>A proposal from JJ is to use the same mechanism used for the lifetime (not yet validated) via a FESA server as a concentrator. This server will have an interface that will not be changed and only the links with the different BCT servers will be set by BI.</p>

<p>There is also a question to be asked to CO whether it is possible to define virtual devices visible as fesa devices. These devices could be configured by OP in the database. I don&#39;t think it exists but I will investigate.</p>