Work packages

Work packages



Analysis of User Requirements.
Collection of user requirements and assessment of currently existing technology and infrastructure, resulting in the User Requirement Specifications report (URS).



Functional Specifications.
Production of the detailed architecture of the demonstrator, as well as the Functional Design Specification report (FDS).



System Implementation.
This WP deals with the demonstrator integration and the development and adaptation of required interfaces.



System Verification.
Verification tasks required prior to the demonstrator phase.



Running the system in a real life environment in two distinct sites.



Evaluation and Assessment.
Evaluation and assessment of the project, divided into two activities: The development of the evaluation guidelines and the actual evaluation and assessment effort.



Project Management.
All the managerial, administrative and technical steering functions required for the proper execution of the contract.







WP 1: User Needs & Requirements


  • To analyse user needs and to identify technical, qualitative, and quantitative requirements of the solution to be proposed.
  • To investigate existing technology and infrastructure.
  • To analyse user needs and to define requirements for use of the proposed technology in other emergency types (forest fires, floods, etc.).
  • To investigate the interoperability requirements between the three validation sites.
  • To record available technical options about other sources of data (SAR imagery and other remote sensing imagery).
  • To collect all background information and technology either in consortium or outside it, in the application domain.

Technical approach:

The end users (in Greece and Spain) participated actively in this work package. They provided input based on their previous experience with sea pollution problems (due mainly to oil spills but also to other pollution sources), as well as in future anticipation (e.g. new pipelines now under construction). Other emergency situations (forest fires, floods etc.) causing extreme damages in the countries involved were also examined. In a more general context, actual emergency management practice, existing methods, equipment or tools used were presented, analysed and evaluated, while their possible integration in the system was examined. The operational scenarios were recorded against a seasonal adjusted timetable (in order to take into account prevailing meteorological phenomena across the whole year). 

In Spain, for example, the regional governments were contacted in order to study what additional features would be needed in the oil spill application. The Spanish National Meteorology Institute was also contacted, in order to obtain homogeneous data regarding the status and forecasts over time of both the target maritime areas and inland areas subject to possible fires or floods.

The user requirements collection process was by no means limited by the users involved directly in the consortium. It was extended to other agencies (Marine Institutes, Coast Guard, Special Marine Pollution Authorities etc.) and it was backed by rapid-prototyping techniques (using data provided by the project partners) for a better understanding of concepts and terms.

The WP also recorded external sources (in particular satellite radar imagery sources), geographical areas covered, frequency of revisit and reception, and spectral signatures of the phenomena, as well as financial factors of this service. In addition, processing, storage, and archiving requirements were recorded for subsequent use in the specifications and implementation phases. Collections of information from international bibliographies and interviews with user organisations (besides the users involved in the project) were used in the frame of this WP.

One of the major activities in this work package was the investigation of the interoperability requirements between the validation sites. Major issues, concerning the differences between the sites were identified, analysed and undertaken in the overall ENVISYS system architecture. Finally, interoperability on the various requirements was mapped between the different sites, with the common and the additional requirements on a per site basis.

In addition, the WP recorded communication infrastructure available or anticipated in the near future for data transmissions to the user sites. 

Concerning emergency management, there was a full recording of the operational scenarios, resources deployment patterns (from user or other related agencies), in particular with connection to seasonal timings. 

Responsible partner: A2.1 - INTELSERVE
Participating Partners: A1.4, A1.1, C2, C3, C4, C5, C1, A1.5
D1: User Requirements

WP 2: Functional Specifications


  • To produce a detailed conceptual model of the system as a consequence of the analysis 
  • To produce the specific system architecture for the demonstrator sites, taking into account differences in infrastructure. 
  • To produce a detailed functional design specifications for each module to be implemented and to identify the adaptations needed for existing background information. 
  • To provide the necessary modifications for detecting other sources of natural disasters (forest fires and floods). 

 Technical approach: 

 The required functionality of the system regarding the detection of oil spills, the assessment procedures, and the management of emergency situations was revealed. 
 The system is composed of two main parts:

  • the core system and,
  • a set of additional modules

 The core system is of general use for various types of environmental emergencies based on remote sensing techniques. The additional modules are specifically directed towards the oil spill. The specification includes the Graphical User Interface (GUI), which is at the operators disposal, through which, the user has full command of the system components. 
 The proposed functionality was presented to and discussed in detail with the user organisations in order to ensure that the resulting specifications would meet the user requirements established in WP01. 
 Apart from the functional specifications of the ENVISYS system, additional work was carried out for the following : 

  • Image acquisitions, processing, and archiving requirements (both in terms of technical functionality as operational specifications of work to be carried out during demonstration and production phases of the system).
  • Collection, analysis, and evaluation of maps covering the areas which were used for the demonstrations. Thematic map requirements and oil spill condition changes were also analysed. It should be noted that thematic maps produced three days after an oil spill incident are considered as critical aids for developing possible response scenarios.
  • Non-functional specifications of the system including performance requirements and specifications (at the various system operations). In this context falls also the speed of the telecommunications links.
  • Security considerations, which are of major concern. Security is pertaining both to transmission of data, and the system operations itself. 
  • Availability, reliability and maintainability of the ENVISYS system. This includes alternative communications options (e.g. radio communications ) for back-up purposes, possibly duplication of hardware etc. In the context of the project, certain aspects of this work were not implemented, however full production of the ENVISYS system must take into account these concerns.  Within this framework of activities, a focus was provided on the data availability of the various service providers (in addition to ESA's ERS-1 and ERS-2 SAR data).  The expected performance of the ENVISYS system as a function of data availability was provided on a technical report (restricted to the project partners and the Commission).

1. Functional design specification 
2. Architectural specification
3. Module level specification
4. Determine technology available 
5. Validation criteria 
6. System operation specification 

Responsible partner: A1.4 - IMPETUS
Participating Partners: C1, A1.1, A1.2, A1.5, C2, C3, C4, C5, C7
D2:  Functional Design Specifications
D2-1:  Technical Report on ENVISYS System Performance and Coverage
D2-2:  System Architecture Enhancement


WP 3: System Implementation


Implementation of software for demonstration of the ENVISYS concept.

The system is composed of the following subsystems:

  1. Main Command Interpreter: Main user interface, which integrates all modules together.
  2. Background Command Sequencer: Controls the system in automatic mode (importing data to the system, image preprocessing and oil-spill detection up to alarm procedure).
  3. Data Import Unit: Automatic import of satellite and meteorological data from data suppliers. 
  4. Preprocessing Unit: Preprocess image data radiometrically and geometrically.
  5. Detection Module: Detect oil slicks automatically in satellite imagery.
  6. Verification Module: Support the operator with tools to verify or falsify an oil-spill alarm.
  7. Assessment Module: Assess the emergency situation in a geographical context.
  8. Operations Module: Support a cleanup operation with equipment and logistic plans.
  9. System Toolkit: General system resources used by the other modules.
  10. Oil Spill Simulator Unit: Sub-module to Assessment Module simulating an oil-spill trajectory.
  11. User-report templates: Templates for the generation of maps and tables intended for the various user groups in an emergency situation.


  • D3.1: Detailed system specification (NR/all)
  • D3.2: ENVISYS prototype, including user and technical documentation (all)

WP leader: NR (C1)

Other participants: IMPETUS (A1.4), EPSILON (A1.3), APEX (C2), ANETKY (C3), ISDEFE (C4), INDI (C5), STQ-URV (S5.1), KSPT (A1.6), INTELLSERVE (C7)

WP 4: System Verification


Verification of software developed for the demonstration of the ENVISYS concept.


 The system's technical performance was verified in the laboratory using historical data. The functionality and performance of the various modules were investigated systematically for individual modules, for several modules working together and for the whole system in a simulated environment. The criteria for the system functionality and performance was specified in:

  • Conceptual system design report (from WP 3)
  • Detailed system design report (from WP 3)

which were based on the findings and specifications in:

  • User requirement report (from WP 1)
  • Functional design report (from WP 2)

 The verification procedure was as follows:

1. Individual modules were tested by the WP leader as near-final versions of the software were received from the other partners. A test report was created and forwarded back to the corresponding implementing partner. The module was updated according to the report and sent back to the WP leader. The procedure was repeated until the module's functionality and performance were accepted.
2. Modules were tested in their complete system environment within ENVISYS. Hence, the purpose of this work was to ensure that the modules together fulfil the criteria for the overall system functionality and performance. The same correction procedure as above was followed until acceptance.
3. The system was tested in a simulated environment. This means that data providers (for images, wind and sea current data) and user groups were simulated. A correction and acceptance procedure as described above was followed.


1. Verification of Main Command Interpreter (NR)
2. Verification of Background Command Sequencer (NR/INT)
3. Verification of Data Import Unit (NR/INT)
4. Verification of  Preprocessing Unit (NR)
5. Verification of Detection Module (NR)
6. Verification of Verification Module (NR/KSPC)
7. Verification of Assessment Module (NR/APEX)
8. Verification of Operations Module (NR/ISDEFE)
9. Verification of System Toolkit (NR/INDI)
10. Verification of Oil Spill Simulator Unit (NR/STQ-URV)
11. Verification of user report templates (NR/IMPETUS)
12. Verification of integrated system (NR/all)
13. Verification of system within external environment (NR/all)


· D4.1: Verified ENVISYS prototype (all)
· D4.2: System verification report (NR)

WP leader: NR (C1)

 Other participants: IMPETUS (A1.4), KSPT (A1.6), APEX (C2), ISDEFE (C4), INDI (C5), STQ-URV (S5.1), INTELLSERVE (C7)

WP 5: Demonstration

The purpose of the demonstration was to test the functionality and usefulness of ENVISYS by running it in a real world environment in two different sites in parallel: Greece and Spain. The ENVISYS systems in the two sites were identical apart from local geographical maps, local meteorological and sea current data, and the format of the user reports, which was adapted to the specific needs of the local users. For both sites the radar images from the ERS-2 satellite were received at the ESA satellite ground stations of Fucino (Italy) and Maspalomas (Spain). After some preprocessing they were sent to Eurimage for further processing, before being sent on CD-ROM by express mail to the ENVISYS co-ordinator, NR (Norway). After transformation from 130 Mb images to 2 Mb low spatial resolution images, they were sent by FTP to ESA-ESRIN's FTP-server, from where the ENVISYS system could retrieve them. In parallel to this time-consuming and complicated procedure, low radiometric resolution products were generated at the satellite station and sent directly by FTP to ESA-ESRIN. They were available for ENVISYS some three hours after acquisition. Unfortunately, these images were not suited for automatic detection, but were used for real-time tests of some parts of ENVISYS. From the year 2000 radar images that are suitable for ENVISYS will be available from the European ENVISAT satellite in near real-time.

WP 6: Evaluation and Assesment



  1. Evaluate the system functionality and performance based on technical criteria.
  2. Evaluate the system based on the demonstration relative to the user requirement specification and user response during the demonstration phase.
  3. Evaluate possible system limitations given by natural conditions.
  4. Evaluate the system's functionality relative to other emergency types.


This work package was run in parallel with the other work packages in order to ensure that the project's overall objectives as well as the system functionality and performance goals identified during the user requirement investigation were met. During the early stages of the project, evaluation and assessment guidelines were developed. This document describes the procedures followed and the criteria evaluated.

The evaluation procedure run in parallel and interact with:

  • WP 4, System Verification: The system functionality and performance were evaluated based on technical criteria.
  • WP 5, Demonstration: The system was evaluated based on the demonstration and the user response during the demonstration phase.

The system's performance was also evaluated with respect to the natural conditions in Mediterranean Sea. The oil spill detection is based on the ability to detect the phenomenon in synthetic aperture radar (SAR) satellite imagery. The "visibility" of oil depends on the presence of capillary sea waves. The robustness of this approach for operational applications in the Mediterranean was evaluated.

The ENVISYS concept may be extended to other emergency situations, like forest fires, floods, earth quakes and volcanic activity. Technical consequences of an system extension and practical usability were evaluated.


  1. Development of Evaluation and Assessment Guidelines report (IMPETUS/ISDEFE).
  2. Technical evaluation of the system (ISDEFE/INDI/IMPETUS).
  3. Evaluation of system during demonstration (ISDEFE).
  4. Evaluation of system relative to natural conditions (ISDEFE/NR).
  5. Evaluation of system relative to other emergency types (ISDEFE/NR).


  • D6.1: Evaluation Guidelines - Draft Validation Plan (IMPETUS/ISDEFE).
  • D6.2: Final Validation Plan (IMPETUS/ISDEFE).
  • D6.3: Report of extension to other emergency types (ISDEFE).
  • D6.4: Validation Results (ISDEFE).

WP leader: ISDEFE (C4)
Other participants: IMPETUS (A1.4), INDI (C5), NR (C1)

WP 01: Project Management


Overall project co-ordination and management.


The work package covered:

  • Overall co-ordination of the work between the partners
  • Monitoring the performance of the partners and that the project goals were met
  • Performing administrative procedures between the partners and towards the CEC

The following management bodies were established and comprised the main administrative elements in the project:

  • Project Co-ordinator: The co-ordinating contractor of the project. 
  • Project Management Committee (PMC): Project management group with representatives of all full contractors.
  • Technical Advisory Committee (TAC): Advisory group of key technical persons among the partners.

The PMC represented the top decision level in the project. The Project Co-ordinator executed the decisions of the PMC. For technical issues, the PMC seeked expert support from the TAC. 


  1. Co-ordination of project partners
  2. Monitoring partner's performance
  3. Ensuring that project goals were met
  4. Perform administrative procedures between partners
  5. Perform administrative procedures towards the CEC


  • Progress reports
  • Annual reports
  • Cost statements
  • Final report

WP leader: NR (C1)

WP 02: Dissemination


  1. To disseminate and co-ordinate the project with other projects within the Telematics Programme.
  2. To disseminate the project results to potential user groups.
  3. To disseminate the project's scientific and technical results in international conferences, journals and to mass media in general.


Dissemination to and co-ordination with other Telematics projects took place through the CEC's concertation meetings.

The user group participating in the project, potential user groups identified throughout the user requirement investigation (WP 1) and other user groups identified during the later stages of the project, were informed about the development of the project. A database of user group information was established. The user groups were also invited to participate informally during the project and in the exploitation after the project.

An international event, a workshop on detection and handling of oil-spill emergency situations, was carried out during the demonstration phase of the project. The purpose of the event was to obtain closer contact with potential user groups and try to establish relations that ensure a solid support for exploitation of ENVISYS after the current project. 

During the course of the project, technical and scientific results were published and presented in international conferences and in journals. This included scientific publications as well as more popular and commercially related media. The project results were also presented to mass media.


  1. Participation in concertation meetings (all)
  2. Making ENVISYS brochures (IMPETUS/NR)
  3. Making ENVISYS CD-ROM (NR)
  4. Distribution of information about ENVISYS to (potential) user groups (all)
  5. Organising an international event (INDI)
  6. Presentations at international conferences (all)
  7. Publication in international journals (all)
  8. Information to media in general (all)


  • D8.1: ENVISYS brochure (IMPETUS; completed)
  • D02.1: ENVISYS CD-ROM (NR)
  • D02.2: ENVISYS end-of-project brochure (NR)

WP leader: NR (C1)

Other participants: IMPETUS (A1.4), IMPAE (A1.2), APEX (C2), ISDEFE (C4), INDI (C5), INTELLSERVE (C7)

WP 03: ExploitationObjectives:

Investigate the potential market for ENVISYS and perform actions that ensure that ENVISYS will outlive the project.


The project is based on the hypothesis that there is a reasonable large market for the ENVISYS concept. This work package investigated the characteristics of the market and developed a business plan in order to make ENVISYS a commercial success outliving the project. The information derived from contact with the project's user group and potential user groups was the foundation of the business plan. 

The work package established a company group that will pursue further investments in the ENVISYS concept after the current project in order to make it a commercial success. The involvement of pilot customers was crucial to achieve this goal. This involvement was established through the project, in particular during the demonstration period.


  1. Make an Intellectual Property Right document agreed upon by the contractors
  2. Make a market assessment
  3. Make a business plan


  • D9: Final Exploitation Plan (IMPETUS)
  • D9.1: Interim Report on consisten Exploitation Plan (IMPETUS)
  • D03.1: Intellectual Property Right document (INDI)
  • D03.2: ENVISYS Business Plan (INDI)

WP leader: INDI (C5)

Other participants:NR (C1), ANETKY (C3), INTELLSERVE (C7)