The start of MAYA's third and last year has marked an important milestone in the project with the beginning of demonstration-oriented activities (Work Package 6). It also marked the end of WP2 and WP3 with a whopping 7 deliverables submitted in September. The development-focused WP4 and WP5 are in the middle of their activities.

The road so far

Before introducing the newly started WP6, let’s recap what has been done in the last year. WP2, just ended, was focused on the design and implementation of the CPS representation and communication tiers that are at the base of the MAYA Framework, and that implement respectively the concepts of digital-continuity and digital-real synchronization: it is thus impacting on the development of WP3 and on the tools-related-WPs. WP3, started in M12 and ended in M24, dealt with the development of the MAYA runtime as the integration of the Centralized Support Infrastructure and the Simulation Framework, created for the management of the multi-disciplinary simulations and the concurrent orchestration of the models. During the second year of the project, the effort has been focused on CPS meta data model design, definition of behavioural models, conception of Communication Layer, design and implementation of the Centralized Support Infrastructure, taking into consideration the required synergies between the general semantic data model and the specific concepts dealt in the other carried out. The completition of all the activities within WP2 and WP3 has led the project to a stable MAYA runtime based on a consolidated MAYA semantic meta-data model.

Tools integration

WP4 and WP6 are running in parallel addressing the integration of High-End tools, on one side, and on the other side SME oriented tools. The activities are in the middle of their scheduled execution, with two tasks on each WP already completed. As a general approach, both WPs have organized their work around frequent meetings with the reference industrial partner in order to keep the development in track with the end-user requirements. Using an iterative and incremental development process has also allowed the tools software vendor to build a very robust prototype in a structured manner and constantly refine it. This approach, in addition to the beforementioned benefit of better acknowledge end-user requirements, is better suited to introduce new developments to an existing commercial application that has an already well-defined maintenance and feature update cycle.

The next year

The newly started WP6 is focused on the demonstration implementation: the most important tasks are T6.2 and T6.3, dedicated respectively to the high-end (Volkswagen) and SME (Finn-Power) scenarios. Following the successfully approach carried on during WP4 and WP5, all the partners are motivated to continue the iterative and incremental development process with frequent meeting with the end-user. Moreover, the feedback from the end-user is very crucial during these tasks as the demonstrators will be validated in the context of a real physical line.

A consortium-wide meeting was hosted on 29th and 30th November by Siemens in Münich, being an occasion to discuss the work done so far and to plan the activities for the last year.