Meetings

Meeting 3 - 26/02/2018

• Actualizar los apartados: 1, 2.3, 4, 5, 6, 8, 9.4 del documento anterior.

Puntos a modificar

• Jaime: 2, 5, 8
• Sergio: 1, 4, 7
• Pablo: 3, 6, 9

1. This module will process the incidents that are delivered by the different agents. The module will request information to module 2 (Agents) to check if the agents are registered in the system and are allowed to submit incidents
2. There are several kinds of agents that can submit incidents: people, entities, sensors, etc. The kind of agents is not predetermined as it will be obtained from the same master file described in the first deliverable.
3. Each incident can have the following fields: user name and password, incident name, description, location (which will be automatically obtained if possible), tags (list of words separated by commas that will allow to categorize incidents), additional information (pictures, videos, etc). For some incidents, a list of fields can also be added with the form "property/value", where the property field refers to a property name and the value field refers to the value of that property.
4. If the combination "user name/password" is not right, incidents will not be processed and an error will be reported. If the combination is right, incidents will be processed and the processed incident will be submitted to Apache Kafka for its further handling by module 4 (InciDashboard).
5. Some agents like sensors can continuously submit incidents depending on how they are configured. For example, a temperature sensor can be configured to emit incidents each hour with information about some place's temperature.
6. Incidents will acquire different states (open, in-process, closed, cancelled) as well as other information generated by the system like assigned operator/entity that must handle the incident, comments about the incident, etc. Incidents can also have an expiration, for example, in the case of the incidents submitted by a temperature sensor, if they are submitted each hour, the expiration time will be an hour).
7. The system will only store a selection of incidents (those submitted by a person or entity, or some specific values submitted by sensors, not all of them). Those agents will be able to query and visualize he incidents that they have submitted using the user name and password generated in module 1. Each agent can have access to see the incidents that he or she has submitted and follow their evolution.
8. Optionally, in the case of people or entities, the incident submission system will offer a conversational user interface using a chat-bot that will be asking information to the user about the incident.
9. Optionally, an alarm system will be developed to send some specific kinds of incidents to some operators so they can assign them.

Meeting 2 - 25/02/2018

• Sesion one finished and updated
• Can sensor have location?
• Discussed which parts to document for deliverable 2
• New parts being added to the Wiki

Meeting 1 - 19/02/2018

• Discussed how to improve the first deliverable
• Discussed how and what to do for the next deliverable

Return home