D2.1 - HARTU Architectural specification and integration plan

The current deliverable (i.e., D2.1 - HARTU Architectural specification and integration plan) aims to report the main results of tasks T2.1 and provides relevant information about Reference Architecture or high-level specification of the HARTU software solutions that will be provided by technical partners (TEK, AIMEN, ITRI and DFKI) to address pilot needs and requirements. Tasks T2.1 covers the overall project approach on Reference Architecture model, reporting the results on technical drawings and software components specifications identifying key technical challenges to be addressed in HARTU, in terms of implementation and architecture definition. Considering this, the main inputs that contributed to the definition of the architecture and the
specifications of the software are:

• “D1.1 - Real world scenarios and metrics for validation definition”: an exploratory investigation of ‘requirements’ for the HARTU solution and its results, capturing both user level requirements and high-level requirements (i.e., functional, and non-functional)
  important to understand and extract the basic functionalities of the system.
• “D1.2 Initial setup of real-world scenarios”: helps to extract ‘technical requirements’ considering the different prototypes corresponding to the 8 use cases defined by the project.

The approach followed to complete deliverable D2.1 included:

• The summary (ToC) and scope of the document agreed between the partners, and a detailed template including a description of each section and what was required to detail it, were disseminated to guide section leaders in collecting the required information.
• A general overview of the manufacturing context and the reference architectures in Industry 4.0 is presented.
• Specifications, definition of the reference model (Reference Architecture) in terms of technical drawings (HARTU Blueprint), definition of the architectural layers and FBB specification: starting from the requirements (D1.1) and the use case descriptions as well as prototypes (D1.2), the HARTU approach is represented using UML diagrams.
• Definition of the integration plan that clearly shows “when” all functional blocks within each layer of the HARTU architecture will be delivered for testing and validation within industrial environments or test labs.
• Support for the software development plan through a CI/CD enabled tool that allows rapid updating of the source codes of HARTU components, as well as code quality control and providing a valid repository for technical documentation and problem management.
• Follow-up activities to monitor the progress of the work through different types of meetings: (1) General project follow-up web meetings (every three weeks) involving all partner representatives; (2) WP2 conference specific meetings; (3) Overall project F2F meeting.