Month 3: Pandora D8.1 Project website

This deliverable presents an overview of the PANDORA public website including the project presentation, schematic architecture of the Pandora solution, work to be performed and milestones to achieve. The Pandora consortium is presented along with the possibilities for access to publications and news about the project. The private section of the website (available only for consortium members) gives access to private documents (contributions to deliverables) and messaging facilities for sharing the work between partners. Once completed, public deliverables will be accessible on the PANDORA public website.

Month 3: Pandora D8.2 Dissemination strategy

This document is the first release of the dissemination and exploitation plan for Pandora Project. It describes the initial activities and as well as a group of strategic choices to be made in order to disseminate knowledge gained during the work, achievements, results and findings. This release mostly aims at indentifying the target audience and/or groups of interest to which address the Pandora information, namely about progress, deliverables, and as well the impact of the project in terms of improvement for crisis managers training or creation of opportunities for the participants. In such a way other workers in the area can make use of the results and give back helpful suggestions to improve the project.

Month 4: Pandora D1.1 URA and SOA

The deliverable D1.1 User Requirement Analysis and State of the Art, is provided in two parts:
Part I sets out the user requirements as determined from research conducted by the UK Government with over 300 senior emergency response practitioners. The user requirements have subsequently informed an analysis of the systems that Pandora will need to encompass. These system requirements are set-out with accompanying justification and prioritisation of individual attributes.
Part II of the deliverable D1.1, provides an extended report on the related technological standards, best practices and research established principles that constitutes the reference point for the proposed PANDORA framework. The PANDORA project has a strong multidisciplinary character in its nature and this is reflected in a review of the literature that spans several research areas. The document outlines the current state of the main areas of research relevant to the design and development phase of the PANDORA project.

Month 8: Pandora D1.2 system reference architecture

The general scope of this deliverable is to identify the technical requirements for the PANDORA system, as well as to specify the PANDORA use cases and the architecture. The technical requirements will define the functionalities, which will be necessary to meet user requirements defined in Deliverable D1.1, and steer the realisation of the pilot scenarios according to the identified use cases. This work has been performed to a level that enables the definition of the PANDORA architecture and the derivation of the functional and technical specifications of the architecture entities and software infrastructure components. It is important to specify that there is a distinction between the terms “use cases” and “scenario” in the PANDORA project terminology:
Use Case, which presents a graphical overview of the functionality provided by a system, using actors and how these interact with the system.
Scenario, which is the crisis or the emergency situation that is created by the PANDORA system and will be used for the training session.
D1.2 specifies the PANDORA use cases according to the requirements that have been already pointed out. There are three use cases:
Single site Training (Figure 1): The system can be used by a group of Gold Commanders at the same time, which have been called together by the trainer and are working around a table in a dedicated room, where the system is installed, at the national or international training facility. This dedicated room has been set up with sensors, devices, tools and monitors that are fixed and not portable.
Deployed training: This use case differs from the previous in that it does not use of a dedicated room and is located, for example, at an institutional building of a gold commander (Civil Protection Centre, MIC, etc.).
Distributed training: the system is used via the web, which means that a dedicated room isn’t present, but the system creates a virtual room in which the Gold Commanders can log in remotely and perform the exercise.

Month 10: Pandora D4.1 Definition and modelling of the emotion simulation engine including the environment framework design

This deliverable sets out the conceptual and logical design for the Emotion Simulation Engine (now known as the Engaging Interaction Framework) and Environment Framework, based on the initial specification set out in the PANDORA Document of Work and refined through deliverable D1.2: The PANDORA system reference architecture.
Initial specifications are repeated here as the basis for the initial work of the consortium, and the revisions already reported in D1.2 are highlighted and form the basis for the development of the design of these components of the overall PANDORA system.
This initial specification of the design will enable the development of the PANDORA prototype and alpha release, but further revisions to the design occasioned by evaluation of the initial prototype(s) will be reported through D4.2: The Implementation of environment framework builder and of the emotion simulation engine.
""The Emotion Simulation Engine, herein described as the Engaging Interaction Framework, and the Environment Framework, represent opportunities to extend the realisation of the existing crisis management frameworks beyond simple digitisation of existing functionality. Clearly, digital environments offer the capability for 3D graphical representations of virtual reality, and some aspects of these capabilities will be realised within the PANDORA system. However, there are other aspects of working within digital environments that can offer significant benefits to the crisis management training scenarios, without requiring the suspension of disbelief necessary to move fully into virtual environments. This document addresses two aspects that could be of considerable benefit in such scenarios, in offering more extensive and detailed multimedia representations of the crisis environment, and associated information. Since the purpose of the project is to support the training of Gold Commanders, who are responsible for the strategic development of responses to crisis situations, the opportunity to place those individuals under some emotional or behavioural stress, related to the crisis scenario, while developing that strategy, could be of considerable benefit in developing more realistic strategies. Extending the existing training situation by using these facilities also provides the opportunity to evaluate responses and reactions, and to provide feedback to trainees on their performance under stress, which could be of considerable benefit in the high level management of real crisis situations.""

Month 12: Pandora D2.1 Behavioural modeller and planner module instantiation alpha release

This deliverable is a very short introduction to the work realized for PANDORA WP2 to support the software demo Alfa Release. It is devoted to introduce main concepts underlying the software prototype and to act as a gentle introduction to the current software demo.

Month 12: Pandora D3.1 Specifications of Pandora crisis knowledge database and Crisis Planner and Modeller Description

This deliverable includes the specifications of the module developed within WP3, namely the Crisis Simulation and Modelling. This module consists of a number of components: the Crisis Planner – responsible for creating flexible concatenation of crisis scenes to form a consistent script for personalized crisis training sessions – and the Crisis Knowledge Base – responsible for crisis description and modelling as well as “storage” of PANDORA knowledge.

Month 12: Pandora D3.2 – Crisis module framework alpha release

This deliverable contains a simple introductory material to support the delivery of a soft- ware Alfa Release for the Crisis Planner and Modeler, a key component of the PANDORA- BOX. This software release contains the basic data structures for plan representation, the Event Network, and two active services for its manipulation: the Crisis Planner and the Executor. These services guarantee basic functionalities to serve PANDORA activities.
""The overall goal of the WP3 is to deliver the Crisis Modelling and Simulation Framework (CMSF) whose complete description is given in D3.1. Aim of this report is to describe a subset of the CMSF, which essentially reflects the current status of the delivered integrated demo alpha release. Specifically we will illustrate the subpart of the CMSF (see Figure 1), which contains three main modules: the Event Network, the Crisis Planner and the Executor. As shown in the figure the WP3 is responsible for producing the basic engine to create active exercises for classes of trainees. The figure also shows how the framework is connected to all the other key modules synthesized by the project, which together ensure a continuous loop trainees-system-trainer. Stimuli from a crisis scenario are continuously generated and submitted to trainees during a training session, while trainees’ actions are registered, analysed and reacted upon by updating the future planned stimuli.""

Month 12: Pandora D5.1 The emulated crisis room blueprint

According to D1.2, the PANDORA project has considered three different use cases: fixed site, deployed site and distributed training. In the fixed site training, there will be a dedicated room at the trainer premises where all the equipment needed for training is available. While in the deployed site training, the training room could be set up everywhere, starting from a standard meeting room. Finally in the distributed training, all the actors, (trainer and trainees) will connect to the system remotely, accessing to a virtual training room. The objective of WP5 is the design of the simulation environment room in which the training will take place. This means not only deciding what equipment has to be selected and/or installed in the above mentioned uses cases, but also design the trainee “interface”. Furthermore the design of the trainee interface must be done with the objective of recreating a realistic crisis situation as much as possible: the trainee interface, in fact, should be able to perceptually engage, using both real and virtual visions and sounds, the involved gold commanders. D1.2 presents the “simulation environment framework” and the “recording framework” as the two components of the PANDORA system architecture that constitutes the trainee interface. In D1.2 there is only an initial definition of their functionalities and input/output interfaces with other system modules. The aim of this document is to detail both components using UML diagrams, class and sequence, in order to translate the functionalities in specific pieces of software and to show the interactions with other modules.

Month 12: Pandora D6.1 Technical project scope and design including the environment run time engine design and development

This deliverable motivates and sets out a framework for a high-level approach to Pandora component integration. The approach provisions for smooth integration, management and scalability. It builds on the concept of SaaS (Software as a Service) and the annotation of software components with formal specifications that instruct interoperability through a unified interface. A short survey and analysis of different problems and mechanisms associated with software component integration is presented. In particular, we investigate current research in component and service based system development to identify and define salient requirements. An initial specification for a functional framework is then set out, guiding developers through the annotation requirements for describing components for integration purposes. The specified framework will use these annotations to enable the management of heterogeneous components for assembly into a fully-functioning Pandora system. The deliverable further provides the technical detail of the identified Pandora components and the overall integration framework implementation completed to date.

Month 12: Pandora D6.2 Subsystem and module testing plan and metric

Deliverable describes the theoretical background of used testing methodology, the unit testing and code quality metrics. The main part of the document is specification of integration test cases for each module

Month 12: Pandora D8.3 Dissemination material

This deliverable summarizes the dissemination activities undertaken during the first year of the project, encompassing the period from the 1st January 2010 to 31st December 2010. In particular it shows what materials have been produced by the consortium for promotion and for information, like also mentioned in the DoW, and what important achievements have been acquired in the period. It finally points out the general strategy applied in the first year to attain the target “awareness” among end-users and relevant scientific/business parties. As for the second year, the deliverable provides updates and planning for the next dissemination steps, when developments and results will be partially and/or fully achieved, in order to attain the target “understanding and/or involving” the potential end-users in a more effective dissemination.

Month 12: Pandora D8.5 Business plan

The deliverable draw the preliminary business plan for Pandora. Contents are Market Analysis, Competitive Environment, Marketing Strategy, Financial and Operations Plan.