This deliverable presents the PHAROS service concept specification. In order to specify the service concept, the document introduces the main drivers leading the project and identifies the main application scenarios (high level use cases) involved. The drivers taken into consideration for the development of the PHAROS service concept are:
•The context in which the PHAROS project is developed;
•The PHAROS mission, considering the short and long term approaches;
•The actors and roles interacting with the system.
The main task contributing to this deliverable is Task 2.1 (Service Concept Specification), which has been performed from months 1 to month 7. The objectives of this task are:
•To define the overall service approach of the PHAROS platform, identifying and describing individual products and services to be provided through the PHAROS service platform and defining service packages that provide higher added value by combining the identified products and services and exploiting their synergies and complementarities.
•To identify the end-to-end service value chain including actors, roles and use cases and specify the service requirements. This second objective has been obtained by identifying the services to be provided in the short and long term versions of the system, but it must be pointed out that all requirements affecting the provision of services are translated into user and system requirements, and therefore, documented in D2.4: PHAROS Requirements and System Engineering–First Issue . In this way, the consistent set of requirements can be found together in a unique document. The outcome of the current document is taken into account for deriving the user and system requirements (T2.3: Requirements and System Engineering) and therefore, it will have an influence in the whole system design and implementation carried out in WPs from 3 to 6. The main challenges faced when defining the overall service concept have been (1) understanding the needs of end users that shall be covered by a system like PHAROS and (2) properly defining the services that PHAROS shall provide in order to satisfy the expressed needs. In order to fulfil these challenges in a satisfactory way, the followed approach has been based in keeping a close interaction with the members of the Advisory Board (AB) and additional end users by holding a joint workshop in Barcelona in March 2014 with the members of the Consortium. The details of the workshop can be found in Annex A, together with a summary of its outcome (Annex B, in terms of application scenarios and Annex C, in terms of services). Among the major findings of the task summarised in this document, there is the fact that on one hand, there is a series of needs which are shared among all participants, which deal mostly with the necessity of sharing information among involved authorities, integrate any new solution in their already existing systems and share lessons learned among different entities at local, regional, national and international level. On the other hand, there is a series of necessities that vary from one case to the other, depending on the type of authority being interviewed, their operational domains, ranging from fire fighting forces to police and security, and the tasks that the user has to perform. In this second case, even if it has been more challenging to find a generalisation about the services to be provided, some common ground has been found. In order to accommodate the multi-hazard approach that the PHAROS system shall present, the description of the proposed service concept is done in a general way, without focusing in any particular hazard, but it must be noticed that the system design and implementation will be carried out based on the forest fire case, since it is the one to be used in the pilot phase of the project. We acknowledge that this document uses material from the Volere Requirements Specification Template, copyright © 1995–2007 the Atlantic Systems Guild Limited .