EMSA 2017/OP/16/2017 ORCHESTRA EMSA Meeting 16 January 2019

Agenda • Alert Creation Workflow • Alerting User Interfaces • Alerting System Interfaces • Questions to EMSA • Requirements scope of R3 |2

Alert Creation Workflow

Alert Creation Workflow

Alerting User Interfaces |5

Alerting User Interfaces |6

Alerting User Interfaces |7

Alerting System Interfaces Design overview |8

Questions to EMSA • The current questions are related to the possible source of the data for the alerting report and to the rules to apply to the report filtering • Please open the attached excel AlertReportAttributes and consult the questions related to the mapping of information • Tab “Report Attributes” contains the attribute mapping to their sources •   Yellow highlight are warning and red highlights are parameters for which no source of data was found • Tab “Report Rules” contains the current report rules •   Red highlights are parameters for which no source of data was found |9

Requirements scope of R3 • We propose to review the requirement that are present in the attached excel RequirementReview •  Consider that Partial status means that the requirement is implemented partially and the reason is present on the comment column •  Consider that Not Implemented is for planned requirement that were not implemented in the release 2.0 and we need to review each of them to realocate or descope them •  Consider that Req must be reviewed are for requirements that are outdated due to diferent decisions and specification on meeting that make them obsolete or mismatched. | 10