Ongoing discussions within the SWIM communities of interest

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Task Status

This page is part of the ongoing SWIM communities of interest discussions. The content is working material. It should not be treated as final as it is still subject to review, comment and change.

This page contains discussion on the supervision and monitoring of services. In particular it discusses what is possible to have a harmonised way to notify users when a service is down or degraded.

Background

Supervision was addressed in a SESAR project on virtual centres. This presentation summarises the approach used in the project. Details are also available in the the PJ 16 final report (https://www.sesarju.eu/sites/default/files/documents/projects/FPR/PJ_16 Final Project Report official V2.doc.pdf).

The topic was further discussed at the October Round Table meeting. The participants discussed what the objectives of the task would be. It was agreed that there is no need to create a service definition for a monitoring and supervision service. In reality, this would be difficult to create. The focus should therefore be on certain best practices.

Topics for best practices

  • semantics of availability statuses

  • cybersecurity - how does this apply to a supervision service?

  • will the service have a ticketing mechanism to inform support?

  • each implementation may have a different set of statuses - is it possible to align them?

  • No labels

Status: Working Material