EAM/AFT Linking Plug-In & EN-EL proposed workflow
→
Europe/Zurich
30/6-019 (CERN)
- A proposal for the implementation of the EAM to AFT linking plug-in
- Ricardo showed a demo of the plug-in based on the proposals we have been converging to in previous meetings, which were
- A 1:N mapping (1 logbook entry : N AFT entries) as this would also enable future integrations
- Links to different logbooks are allowed though in AFT
- EAM would own linking between the logbooks eventually, by setting both the EAMàAFT and AFTàEAM link
- It would check beforehand whether a link already exists and notify the user to change it
- AFT would grey out the option to link to EAM
- · To guide the user, an adequate time window of AFT faults is suggested (either on date of creation or event date) and based on the logbook a set of AFT systems is suggested (e.g. CV logbook only suggests Cooling and Ventilation categories)
- AFT faults could eventually be automatically marked as expert reviewed once an EAM link was set and the EAM entry closed – to be reviewed
- The general feedback was that the possibility of creating AFT faults from EAM should be hidden
- A proposal for EAM and AFT workflow for EN-EL
- Patricia presented data fields and structure of data and whether they should reside in AFT or EAM
- After discussion, we noted that the majority of data fields marked to be residing in AFT and EAM could actually be “owned” by EAM and with the help of the integration be shown in AFT
- E.g. the glitch duration/magnitude data should be recorded once in EAM and then 1:N be propagated to AFT
- System classification and Description should still always be tracked in AFT as well
- For the next meeting
- Serge would present the situation for EN-CV
- Based on Anti’s suggestion, we should discuss through in more detail the work flow in particular for modifications of already linked faults
There are minutes attached to this event.
Show them.