::APPS::

WP3. Plug & Play Surveillance Architecture

 

 

   This work package will perform data engineering for target applications and developing ontologies and profiles to achieve plug & play architecture for surveillance systems:

 

  • To explore data standards which are commonly being used by existing surveillance architecture and business models to carry out a comparative analysis to identify a data model which will constitute a base model for APPS Plug & Play Surveillance Architecture

  • To define Plug and Play Surveillance Architecture Profiles covering all three levels of interoperability stack

  • To analyse sensor models and propose an interoperability profile addressing sensor to surveillance system data communication

  • To define an interoperability services in-line with Plug and Play Surveillance Architecture Profiles for handling communications and resolving semantic mismatches



Task 3.1: Definition of publish/subscribe communication paradigm 

 

 Plug & Play Surveillance Architecture will incorporate a publish/subscribe communication paradigm for collecting messages provided by several kinds of sensors (publishers) and distribute those messages to the consumers (subscribers) interested in that information. The concept of publish/subscribe will allow customers to subscribe to certain events related to contexts, and content-related issues.


 

Task 3.2 Common Data Standard Analysis

  

  This task will address the collecting and formalizing of data models and business process of existing surveillance systems, in terms of the services to enable collaboration processes and exploitation of information from different surveillance systems across borders.

 It will to carry out a comparative analysis to specify underlying shared conceptualisations from multiple legacy systems. it will not only take as input the legacy systems identified, but will also take as input proposed data as well as any  more recent extension for surveillance systems available at the time of project implementation. Based on the information gathered in the Requirements and specifications defined in WP1 and the comparative analysis result a common meta-model will be identified.


 

Task 3.3: Plug & Play Surveillance Architecture Profiles

  

  In this task first of all an APPS ontology model will be developed based on the results of the Task 2.1 which will cover both data models and business processes. This ontology will be semantic model which will be used for mapping exchanged dynamical information to each other to be harmonized.

 For each level of the interoperability stack an interoperability profile will be created. The communication layer will cover the transport and communication layer protocols. The document data layer will specify the content of messages exchanged and the coding systems used among the applications. The business layer will determine choreography of the application interactions, such as the requirement to send an acknowledgement after receiving a message.

  In this task, the interoperability profiles defined for each layer will be integrated. The integrated profiles are independent of a specific country, organization or instance. The profiles will be presented to related standardization organizations to be reviewed and published publicly in order to increase their adoption. Another benefit of presenting the profiles to standardization organizations is that continuous feedback may improve the profiles. While integrating the profiles, the methodology used by the Integrating Healthcare Enterprise (IHE) will be followed.

 


Task 3.4: Sensor Data Models and Interoperability Profiles

  

  This task will address the collecting and formalizing of data models and business process of existing sensor data and process models. Based on survey of existing sensor data and process models a set of interoperability profile will be defined, which acts as a common denominator among sensors or 3rd party data providers being used by crisis management organizations and enables interoperability between APPS complaint sensors or 3rd party data providers and surveillance system environments. It will be based on OGC-SWE and will exploit so far lessons learnt and best practices which applied OGC-SWE standards in their applications

 


Task 3.5: Interoperability Services


 

  This task will provide Interoperability Services for the sensor and surveillance systems which are not compatible with APPS interoperability profiles. These services can also be utilized for resolving semantic mismatches among all sensor and surveillance systems. The APPS ontology model will be a common ground for mediation and the semantic models of other surveillance systems needs to be available. Interoperability Services will discover the similarities among semantic description of system interfaces according to both the semantic properties they share and the semantic equivalences established through reasoning. 

 Interoperability Services will fuse both ontological and logical rules by controlling them in a procedural flow. The rules can be defined in addition to APPS ontology model during Task 2.3. In addition to this, these services can also be utilized for integrating APPS non-complaint sensors or 3rd party data providers to surveillance system environments. Finally a module for generation of transformation files will be developed for converting ontological findings to transformation rules.