The project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No. 731246
D1.1 Improved AMORPH.aero Release 1 (Demonstrator); M6
The main goal of Work Package 1 Solution Prototype Improvements is to improve AMORPH.aero prototype based on the feedback gained from the proof-of-concept as well as the commercial trials organized in AERFOR. Improved AMORPH.aero Release 1 is the result of the first round of improvements being implemented on top of AMORPH.aero prototype.
D1.2 Improved AMORPH.aero Release 2 (Demonstrator); M12
The main goal of Work Package 1 Solution Prototype Improvements is to improve AMORPH.aero prototype based on the feedback gained from the proof-of-concept as well as the commercial trials organized in AERFOR. Improved AMORPH.aero Release 2 is the result of the second round of improvements being implemented on top of AMORPH.aero prototype.
D1.3 Improved AMORPH.aero Release 3 (Demonstrator); M18
The main goal of Work Package 1 Solution Prototype Improvements is to improve AMORPH.aero prototype based on the feedback gained from the proof-of-concept as well as the commercial trials organized in AERFOR. Improved AMORPH.aero Release 3 is the result of the third round of improvements being implemented on top of AMORPH.aero prototype.
D1.4 AMORPH.aero SaaS Report (Report); M18
The main goal of Work Package 1 Solution Prototype Improvements is to improve AMORPH.aero prototype based on the feedback gained from the proof-of-concept as well as the commercial trials organized in AERFOR. AMORPH.aero SaaS Report is the description of the tasks and efforts to specify AMORPH.aero repackaged as a cloud-based installation, in the initiative of reducing implementation cycles duration and overall costs. Within the report an investigation of a SaaS deployment for reducing implementation and support time and cost is provided.
D1.5 AMORPH.aero pre production Release (Demonstrator); M27
The main goal of Work Package 1 Solution Prototype Improvements is to improve AMORPH.aero prototype based on the feedback gained from the proof-of-concept as well as the commercial trials organized in AERFOR. AMORPH.aero pre-production Release is the result of the final round of improvements being implemented on top of AMORPH.aero prototype.
D2.1 Validation Test Reports (Report); M5
This document summarizes the requirements, use cases and test cases specified, reviewed and tested within the AERFOR project. The purpose of this deliverable is to document the internal test of the AMORPH.aero modules that were designed and developed. To support the internal testing, the tests are performed with fictitious airport data and the envisioned delivering to a dummy customer.
Primarily, this is performed to validate the software developed in work package 1 for quality assurance before release. The engineering team will run tests regarding functionality, stability, performance and scalability, using both manual approach and test automation software.
D2.2 Trial Agreements (Report); M6
An essential part of the AERFOR project is the further development of product features and enhancement of the existing software to make AMORPH.aero more advanced and improve the stability and product maturity. To make the product development close to real airports requirements, Amorph Systems (AS) plans to set-up so called trial installations together with potential customers as partners within the AERFOR project. Within 3 major trial installations, AS will install their AMORPH.aero platform onsite as well as develop and integrate new advanced customer features, which make the Amorph.aero platform unique of its art in the aviation industry. These functionalities will help AS to further strengthen their growth and reputation in the aviation market by addressing unique use cases.
D2.3 Deployment Handbook (Report); M6
This deliverable describes how the AMORPH.aero Collaborative Platform has to be deployed together with its prerequisite software. The document aims to provide a comprehensive guide that needs to be used by deployment engineers (in principle part of the Amorph Systems team) when performing new deployments of the AMOPRH.aero Collaborative platform. The steps offered in the guide provide all necessary details required to perform a successful deployment of the platform.
D2.4 Configuration Handbook (Report); M6
This deliverable describes how the AMORPH.aero Collaborative Platform has to be configured by the end user after the deployment phase. The document aims to provide a comprehensive guide that can be used by the end user in order to make configuration of the already deployed solution in order to make full use of the platform.
D2.5 Training Manual (Report); M6
This deliverable provides the training material content for the modules of the AMORPH.aero Collaborative Platform present in the first official release
D2.6 Validation Test Reports 2 (Report); M11
This document summarizes the requirements, use cases and test cases specified, reviewed and tested within the AERFOR project during the second period of the program. The purpose of this deliverable is to document the internal test of the AMORPH.aero modules that were designed and developed. To support the internal testing, the tests are performed with real airport data, the period corresponding to the first trial with a real airport.
Primarily, this is performed to validate the software developed in Work Package 1 for quality assurance before release. The engineering team will run tests regarding functionality, stability, performance and scalability, using both manual approach and test automation software.
D2.7 Validation Test Reports 3 (Report); M17
This document summarizes the requirements, use cases and test cases specified, reviewed and tested within the AERFOR project during the third quarter of the project. The purpose of this deliverable is to document the internal test of the AMORPH.aero modules that were designed and developed. To support the internal testing, the tests are performed with real airport data from the second trial.
D2.8 Validation Test Reports 4 (Report); M26
This document summarizes the requirements, use cases and test cases specified, reviewed and tested within the AERFOR project during the last quarter of the project and reiterates those which did not pass the validation tests in the past three quarters. The purpose of this deliverable is to document the internal tests of the AMORPH.aero modules that were designed and developed. To support the internal testing, the tests are performed with real airport data from the 3rd trial partner.
D3.1 Commercial trial 1 implementation report (Report); M12
An essential part of the AERFOR project is the further development of product features and enhancement of the existing software to make AMORPH.aero more advanced and improve the stability and product maturity. With the first trial partner, the solution in its current shape will have a much-needed contact with real airport environment in order to assess its strengths and weaknesses.
This deliverable focuses on the implementation of the solution at trial 1 airport starting with an overview of the trial and presenting the actual situation the airport. Within this document the objectives of the trial are clearly specified in relationship with the requirements that are grouped in two categories:
- Validation of existing functionalities inside the AMORPH.aero Collaborative Platform
- Development of new features
D3.2 Commercial trial 1 evaluation report (Report); M12
This deliverable compiles the results of the 1st performed trial of AMORPH.aero within the AERFOR-project at trail 1 airport. It describes in detail how the AMORPH.aero modules and features provided for the first 6 months trial at trial 1 airport are tested and validated.
D3.3 Commercial trial 2 implementation report (Report); M18
An essential part of the AERFOR project is the continuing development of product features and enhancements of the existing software to make AMORPH.aero more advanced and improve the stability and product maturity. Having already the experience of the first trial, the solution is now deployed at trial 2 airport in order to assess its utility in a different airport environment, which faces different challenges.
The current deliverable focuses on the implementation of the solution in trial 2 airport starting with an overview of the trial and presenting the actual situation at trial 2 airport. Within this document the objectives of the trial are clearly specified in relation to the requirements that are grouped in two categories:
- Validation of existing functionalities inside the AMORPH.aero Collaborative Platform;
- Development of new features and capabilities
D3.4 Commercial trial 2 evaluation report (Report); M18
This deliverable summarizes the results of the 2nd performed trial of AMORPH.aero within the AERFOR-project at trial 2 airport. It describes in detail how the AMORPH.aero modules and features provided for the 6 months trial at trial 2 airport were tested and validated.
D3.5 Commercial trial 3 implementation report (Report); M27
An essential part of the AERFOR project is the further development of product features and enhancements of the existing software to make AMORPH.aero more advanced and improve the stability and product maturity. Having already the experience of the first two trials, the solution was now deployed for the 3rd trial in order to assess its utility in a different airport environment, which faces different challenges.
D3.6 Commercial trial 3 evaluation report (Report); M27
The role of the current deliverable has provided the test cases that have been considered in order to evaluate the special developed features for the 3rd trial. In order to evaluate the AMORPH.aero Collaborative Platform and the relationship with the Amorph team, a questionnaire was provided to the two trial partner teams. As done in the previous trials, the target was to assess the effectiveness of the collaboration and the technical performance of the AMORPH.aero Collaborative Platform.
D3.7 Guidelines and best practices (Report); M27
Within this report an overview of guidelines and best practices for AMORPH.aero end users is provided. It gives an overview of:
- AMORPH.aero deployment guidelines
- AMORPH.aero configuration guidelines
- Basic interfaces and supported external systems
- Guidelines for data security and data protection
D4.1 External Project Website (Public Website); M2
This deliverable presents the external project website for the AERFOR project. The website is hosted at http://www.aerfor.eu and includes a description of the project and stakeholders, the structure of the project, downloads, a news section and a contact form.
D4.2 Communication Plan (Report); M3
The base of the communication plan is the marketing and sales strategy as developed in Phase 1 Concept & Feasibility Study and previous efforts to penetrate the market. Following this idea this document outlines the marketing strategy and the means which will be used by Amorph Systems (AS) to address the potential market for the product Amorph.aero.
Within all communication activities described in the communication plan AS make every effort to fulfil the duty of the promotion of the AERFOR project as documented in GA Article 38.1.1 in accordance with the promotion of the product and the project results from AERFOR.
D4.3 Communication report (Report); M27
The communication report gives a summary of the performed communication activities during the AERFOR project. These activities are based on the developed communication plan (refer to deliverable D4.2 Communication plan) and the efforts of Amorph Systems (AS) to develop the market for AMORPH.aero.
D4.4 User association report (Report); M27
This report provides a description of the activities that were taken during the AERFOR project to actively promote the project technologies and innovations to the market and to build up an AERFOR User Association. This report is linked closely to deliverable D4.3 “Communication report” and relates closely to the defined communication measures.
D4.5 Partner ecosystem report (Report); M27
The various activities of AS during the AERFOR project to build up a partner ecosystem are described within this report. Therefore, possible partnerships on the market for AS were identified, classified and evaluated. This covered existing partnerships as well as potential partnerships.
D4.6 Internal Project Repository (Other); M1
The project repository main purpose is to facilitate the collaboration within the project amongst project participants and partners by information sharing.
D5.1 Draft Commercialization Plan (Report); M6
This document provides a description of the AERFOR Commercialization Plan in a first draft. Within the report, the product, the market and the competition as well as the Go-to-Market concept is described and evaluated for the AMORPH.aero product and the AERFOR project. A price model was designed and on this basis a first revenue plan for AMORPH.aero was created to be presented in this report. Actual chances and risks are considered and discussed.
D5.2 Initial Commercialization Plan (Report); M12
This document provides a description of the AERFOR Commercialization Plan in a second iteration (Initial Commercialization Plan). This version reflects the knowledge the team has experienced in the second half of the first year of the AERFOR project.
The deep insight into the European airport market due to present and planned dissemination activities within the AERFOR project, the ongoing and planned trial projects as well as the discussion with the members of the External Advisory Board help AS to adjust the expectations regarding the market potential as well as the necessary functionalities. Actual chances and risks are considered and discussed.
D5.3 Final Commercialization Plan (Report); M27
This document provides a description of the AERFOR Commercialization Plan in a third and final iteration (Final Commercialization Plan) and is based on the AMORPH.aero Go-To-Market strategy, developed in deliverables D5.1 (Draft Commercialization Plan) and D5.2 (Initial Commercialization Plan).
The deep insight AS has gotten into the European airport market due to the numerous
performed dissemination activities, the trial projects as well as the discussion with the members of the External Advisory Board and the User Group has helped to adjust the expectations regarding the market potential as well as the necessary functionalities, their prices and the license model. Finally, actual chances and risks are considered and discussed.
D5.4 IPR registry and IPR strategy report (Report); M27
Within this deliverable an IPR strategy for the AMORPH.aero software platform was developed and established to ensure long term IPR protection of the developed AMORPH.aero software platform.
D5.5 Scaling up report (Report); M27
This deliverable covers all activities with regard to scaling-up the business, increase business relationships with intension to deploy the commercial solution of AMORPH.aero in line with the commercialization plan. Furthermore the possibility to extend the solution to other business segments was explored.
D5.6 Commercial trial package/rollout process (Demonstrator); M27
The goal of Work Package 5 Industrialization & Scaling up is to develop an industrialization strategy for AMORPH.aero based on the feedback gained from the proof-of-concept as well as the commercial trials organized in AERFOR. The Commercial Trial and Rollout Package is built on the experience from the trials and aims to accelerate customer adoption by simplified end-user-centric packaging of the offer and support scaling by maintaining integrity and control of the system and system components during operation, while developing and rolling out new versions of the software in a multi-tenant and multi distribution deployment context.
D5.7 Beta User Agreements (Other); M27
Goal of this deliverable was the market adoption of AMORPH.aero and the transitioning of the airport trials sites into commercial projects by utilizing Beta Users as base of the commercialization phase (AERFOR Phase 3).
D6.1 Project Quality Handbook (Report); M3
This deliverable describes how Quality Assurance (QA) procedures will operate within the AERFOR project.