This deliverable reports on the components of the first functional prototype of the WEKIT sensor fusion API and the experiences made with it. The development of these components is based on previous work on the WEKIT framework and methodology, requirements and scenarios, as well as technological selections and limitations. The deliverable specifies the key interfaces between the software component and the hardware, the backend infrastructure, and the front-end application modules.
In this deliverable we present the first version of the experience capturing hardware prototype design and API architecture, following on from D3.1 and the final selection of sensors. This deliverable involved acquiring, testing and integrating the various off-the-shelf sensors and developing a hardware/software design to connect the various devices and sensors into a single platform. This also involved solving problems around how we would manage the additional computing power, storage and wireless streaming capabilities required for this project.
In this first iteration of the Outreach and Dissemination Report – D7.2, we report on initial efforts and outcomes in dissemination and stakeholder outreach for the first year of the project. We thereby adhere to the planned structure of the original dissemination plan in D7.1. As planned for this early phase, we do not yet have shareable and tangible project results, but there is much external interest in our framework and vision; the consortium has not only reached but exceeded its target measures for five milestones (relevant stakeholders identified, community portal and social media online, community event planned, prepared, and organized, first stage of 30 members on community portal).
This deliverable describes the WEKIT evaluation case for Space. The space domain is a very complex and challenging environment where the range of pre-flight and in-flight activities that can benefit from the innovative and powerful forms of AR-based and knowledge-intensive training that WEKIT is aiming to develop, verify and make available to advanced industries across Europe.
This deliverable describes the WEKIT evaluation case for Engineering in healthcare. We identify scenarios and examples of use cases to demonstrate how the learning processes may be improved by using the WEKIT methodology, in terms of effectiveness, time reduction and user perception.
This deliverable describes the WEKIT evaluation case for Aeronautics. Three tasks of different complexity are presented: engine rigging, brake wear check, and preflight inspection.
This deliverable has the objective to introduce the work done within WP6, explaining the innovative methodology used to define and evaluate the Industrial cases.
Our starting point is the need to evaluate the learning methodology and the technological platform in authentic contexts.
In this first version of the deliverable, we make the following contributions: to design the WEKIT capturing platform and the associated experience capturing API, we use a methodology for system engineering that is relevant for different domains such as: aviation, space, and medical. Furthermore, in the methodology, we explore the system engineering process and how it can be used in the project to support the different work packages and more importantly the different deliverables that will follow the current.
This deliverable joins D1.1 (User Industry Needs) and D1.2 (Technology Industry Needs and Affordances) and reports on the outcomes of Tasks T1.1 (Training Industry Assessment) and T1.2 (Technology Industry Assessment).
This deliverable gathers information about current practices in the training industry about the current and potential use of AR/WT in educational processes in order to assess training industry needs (D1.1) and to extract input for the WEKIT Framework and Training Methodology (T1.1).
When mapping the transfer of a skill or some knowledge between and expert and a novice there are many high-level tangible and intangible factors that are present. Three key factors are the type of task to be carried out, what domain will be interacted with and dimensions that define the tasks constraints.