Deliverable 6.7: Testing Report for Integrated Information Flow of Services

1 WP 6 FLEXIBLE DECENTRALISED CIRCULARITY AND SUSTAINABILITY SERVICES Task 6.7 Integration testing of CircThread information flow and services Deliverable 6.7 Testing Report for Integrated Information Flow of Services Ref. Ares(2024)9190857 - 20/12/2024 2 DISCLAIMER The opinion stated in this report reflects the opinion of the authors and not the opinion of the European Commission. All intellectual property rights are owned by CircThread consortium members and are protected by the applicable laws. Reproduction is not authorised without prior written agreement. The commercial use of any information contained in this document may require a license from the owner of that information. ACKNOWLEDGEMENTS This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement Nº 958448. 3 Project Data Project Acronym CircThread Project Title Building the Digital Thread for Circular Economy Product, Resource & Service Management Grant Agreement number 958448 Call identifier H2020-LCCI-2020-EASME-twostage Topic identifier CE-SC5-31-2020 Develop, implement, and assess a circular economy-oriented product information management system for complex products from cradle to cradle Funding Scheme IA - Innovation action Project duration 48 months (From 1 June 2021) Coordinator FUNDACION CARTIF Website https://www.circthread.com Deliverable Document Sheet Deliverable No. 6.7 Deliverable title Testing Report for Integrated Information Flow of Services Description Linked to T6.7 provides the Testing Report for integrated information flow of services for the CircThread projects including as outcomes: an overview of all the linkages made between the services and the CircThread middleware with their data exchanges from the micro-services prospective, including technical and security aspects following the T5.1 architecture baseline and T6.1 TO t6.7 developments, and overview of the testing scenarios of the integrated information flow from/to all services with validations, a summary of the successes and failures of the integration with feedback on improvement needs before release WP No. 6 Related task T6.7 Lead Beneficiary CAR Author(s) CAR Contributor(s) EKO, SUP, SIM, ECOW Type Report Dissemination L. Public Language English – GB Due Date 30/11/2024 Submission Date 20/12/2024 4 Version Action Owner Contributors Date V.0 ToC CAR CAR 24/09/24 V.1 Fisrt version CAR SIM, ECOW, EKO, SUP 18/10/24 V.2 Full advanced draft for review CAR CAR, ECOW 12/12/24 V.3 Final Version CAR CAR 20/12/24 5 EXECUTIVE SUMMARY This deliverable document the process and results of the integration and testing of the services developed in the framework of WP6 of the CircThread project. The main objective of the task T6.7 is to ensure the interoperability and correct communication between the different software modules created in the tasks T6.1 to T6.6, which form the architecture of decentralised and sustainable services of the project. The integration includes the validation of the information flows between services, the identification and resolution of possible technical issues, and the confirmation that the security aspects comply with the standards set in the overall project architecture. It is explained the methodology followed that included detailed planning of test scenarios, implementation of a controlled test environment. Each module was first subjected to unit testing before being integrated into a shared test environment. Subsequently, integration tests are being defined to ensure that data flowed correctly between the different services, and adjustments will be made to optimise interoperability. The test results need to confirm that the services developed in tasks T6.1 to T6.6 are integrate correctly and can communicate with each other through the CircThread middleware, meeting the technical and security requirements. This deliverable is fundamental for the preparation of the pre-industrial phase in WP7, as it ensures that the integrated system is ready to be implemented and tested in a real industrial environment. The correct integration of these services not only validates the technical architecture of the project, but also reinforces the viability of the solutions proposed by CircThread to improve sustainability and circularity in the management of end-of-life products. With the integrated system tested and validated, it will be deployed in industrial environments in WP7, where tests will be carried out under real operating conditions. Monitoring and adjustment of services will continue as necessary, ensuring that all proposed solutions meet the expectations and objectives of the project. 6 Table of Contents Executive Summary ............................................................................................................................ 5 1. INTRODUCTION ....................................................................................................................... 8 2. integration and test methodology ....................................................................................... 9 2.1 Overview of the Integration Process .............................................................................................. 9 2.2 Detailed Phases of Integration ............................................................................................ 9 2.2.1 Planning and Setup : ................................................................................................................. 9 2.2.2 Service specific Integration ................................................................................................. 10 2.2.3 System wide Integration....................................................................................................... 10 2.2.4 Final adjustments and validation ....................................................................................... 11 3. description of integrated information flows ................................................................ 12 3.1 Information Flow Across Services (T6.1 - T6.6) ........................................................................ 12 3.2. Technical Architecture of Data Exchanges................................................................................ 18 3.2.1 System use by the services ........................................................................................... 19 4. testing scenarios ...................................................................................................................... 23 4.1 Overview of Testing Strategy ......................................................................................................... 23 4.2 Detailed Integration Testing Scenarios .......................................................................... 24 4.3 Validation Criteria ................................................................................................................. 34 5. conclusion and next steps .................................................................................................... 36 7 List of Figures Figure 1. Information scheme for service S8 Legacy Product .............................................................................. 10 Figure 2 Service Container integration ( Deliverable 5.5 Service Container and Procedures description for Connections ) .................................................................................................................................................................... 19 8 1. INTRODUCTION Within the CircThread project, WP6 is focused on the development and implementation of flexible, decentralized circularity and sustainability services. These services are designed to support the circular economy by providing essential tools for identifying, managing, and improving the lifecycle of products, particularly at the end of their use. Each task from T6.1 to T6.6 contributes a specific software module that interfaces with the Digital Thread information exchange system, which is central to the CircThread architecture. The goal of this work package is to create a robust set of interoperable services that can seamlessly integrate into the broader CircThread ecosystem, enabling data-driven decision-making for circularity and sustainability. Task T6.7, Integration Testing of CircThread Information Flow and Services, plays an important role in ensuring that the services developed in WP6 operate cohesively as a unified system. The specific objectives of Task T6.7 include: Integration: To ensure the successful integration of the services developed in Tasks T6.1 to T6.6, making any necessary adjustments to achieve seamless interoperability. This involves connecting the services through the middleware established in previous work packages, ensuring that data flows accurately and efficiently between them. Testing: To test the integrated services from both a technical and security perspective. This includes validating the correctness of data exchanges, assessing the performance under different scenarios, and identifying any issues that may arise during integration. Final Adjustments: To identify and implement any final improvements needed to optimize the system's operation before its deployment in pre-industrial settings in WP7. This involves fine-tuning service orchestration, enhancing security measures, and ensuring that all components meet the required stability and performance standards. This deliverable reports on the integration and testing activities conducted within Task T6.7 covering aspects of the integration and testing process, including a description of the technical process, elements used and challenges faced along the way. It is presented the planning and the consideration about security of data exchanges and provides recommendations for further testing, potential improvements, and strategies for scaling up the system in future stages of the project 9 2. INTEGRATION AND TEST METHODOLOGY 2.1 Overview of the Integration Process The integration of the services developed in WP6 is a critical step to ensure that the CircThread ecosystem functions as a cohesive and interoperable platform. The integration process involves combining the individual services from Tasks T6.1 to T6.6 into a unified system that communicates seamlessly through the Digital Thread information exchange system, which is the backbone of the CircThread architecture. The integration process was planned and will be finally executed in phases to minimize risks and ensure that each service was properly incorporated before moving to the next stage. The phases included initial planning and setup, service-specific integration, systemwide integration, and final adjustments and testing. Each phase was designed to address specific integration challenges and ensure that the services work together as intended. 2.2 Detailed Phases of Integration 2.2.1 Planning and Setup : The evolution of the different services has been monitored, different files have been created with the characteristics and needs of each service throughout its development. The following information is taken as a starting point: a description of the service, estimated development time, included pilots, use cases, potential users, backend web service connections to other systems or modules, information about the materials, prerequisites for setup and usage environment, etc. This information was analysed and a first identification of dependencies was made, not only between the services developed in package 6, but also with the rest of the services defined in the project. This mapping was crucial to understand the order in which services needed to be integrated and to identify potential bottlenecks or conflicts. Meetings have been held with all developers to update this information and to get the integration environment ready. This environment considers the necessary middleware, database and network configurations to support the integration of the services. These meetings have confirmed the information provided by each service, the relationships with other services and actors by use case and pilots as well as the integration needs. 16 User Interface (UI): Interactive web interface for importing models, creating scenarios, and visualizing results via graphs and tables. REST API: Provides integration capabilities with external tools and ensures secure access with authentication and user management. Relationship to Other Services Digital Product Passport (DPP): Integrates to collect and update sustainability data throughout a product's lifecycle. CircThread Platform: External tool within the CircThread ecosystem, enabling centralized and collaborative data management. Decision-Making Services: Supports services like End-of-Use Collection Circularity Recommendations and Circular Design Recommendations, influencing decisions on product recycling based on environmental impacts. T6.5: S14 Circular Design Recommendations Service (EKOD) Category Details Service Name S14 Circular design recommendations service Objective Analyze disassembly operations in repair, recycling, or remanufacturing processes to identify problematic parts/components and recommend alternatives using the VESPER tool. Historical data on disassembly failures is considered to improve outcomes. Functionalities Design Evaluation: Allows users (product designers) to upload product design files (e.g., CAD files, product structures, BOM) and select target components to generate a PAC (Parent-ActionChild) model. Disassembly Process Visualization: Enables users to visualize disassembly sequences through generated PAC models. Recommendations for Design Improvement: Suggests alternative parts/components to (i) reduce disassembly effort and (ii) improve circularity indicator scores. Integration of Manufacturer’s Databases: Performs similarity analysis of parts/components using manufacturers' internal data, allowing users to upload related documents via an intuitive interface. Data Used for Development Database Tool: Uses MongoDB for storing structured and unstructured data flexibly. CircThread Product Model Registry Service for product model selection. BOM Quality Manager for Bill of Materials and product structure details (e.g., mass, materials, fasteners). Damaged Product Assessment Service for product status data (e.g., damaged parts, rust elements). GRETA Circularity Sustainability Advisory Service for circular economy indicator values. 17 Manufacturers/Recyclers' internal databases for potential disassembly failure data and similarity analysis. User Input: Allows manual uploading of required documents for integration and analysis. Data provided Alternative Recommendations: Suggests replacement parts/components to improve disassembly effort index and circularity indicator values. API or UI Developed User Interface (UI): A graphical interface for product designers to access integrated data and perform evaluations in real-time. Developed with React.js for the frontend and Node.js for the backend. API: Provides endpoints for integration with CircThread services such as the Product Model Registry and Identity Management Service. Relationship to Other Services Design Feedback: Recommendations are shared with the design process and services like S11 Manufacturing Supplier’s Intelligence Module to ensure material sourcing is considered in the design phase. T6.6: S11 Manufacturing Supplier's Intelligence Service Category Details Service Name S11 Manufacturing Supplier’s Intelligence Service Objective Evaluate the criticality of chemical and raw materials, assess suppliers' compliance with REACH and RoHS regulations, and analyze LCA impacts (via integration with GRETA) to rank multiple suppliers effectively. Functionalities Ranking Mechanism: Analyzes and scores multiple suppliers based on factors such as REACH, RoHS, CRM (Critical Raw Materials), SVHC (Substances of Very High Concern), and LCA evaluations. Data Used for Development Data Sources: European Chemicals Agency (ECHA) for REACH, RoHS, SVHC, and CRM information. GRETA Integration: Accesses LCA data for comprehensive supplier evaluation. Data provided Supplier Ranking: Produces a ranked list of suppliers, accompanied by detailed assessments of contributing factors, including SVHC, RoHS, CRM, REACH, and LCA evaluations. API or UI Developed API Integrations: Connects with GRETA and PRATIS services to allow users to evaluate suppliers based on environmental rankings. Relationship to Other Services Integration with PRATIS and GRETA: Uses these services to enhance the evaluation of suppliers and their environmental impact rankings. 18 3.2. Technical Architecture of Data Exchanges The integrated information flow relies on the CircThread’s architecture Service Container (Task 5.5) based on a microservice model, where each service functions independently but is integrated within a boarded CirThread ecosystem thought defined API endpoints. This modular approach enables a high degree of resilience and scalability, allowing for independent updates and scaling of individual services without disrupting the entire platform Ensuring the security and integrity of data is a critical aspect of CircThread’s architecture. All data exchanges are encrypted using secure protocols such as HTTPS and SSL/TLS. Additionally, access to services is controlled via a robust authentication and authorization mechanism, which utilizes Keycloak for centralized identity and user management. Keycloak is employed as an open-source identity and access management tool to provide seamless authentication, authorization, and user management. It supports features such as centralized authentication, Single Sign-On (SSO), and role-based access control (RBAC), which simplifies the implementation of secure systems without requiring custom-built solutionsk Implementation in CircThread Keycloak is configured as the central identity management system for the CircThread platform, managing user logins, roles, and access permissions. It supports multiple authentication standards like OpenID Connect, OAuth 2.0, and SAML 2.0, enabling integration with a wide range of external applications. Keycloak is integrated with the CircThread platform in the following ways: • Centralized Authentication and SSO: Keycloak allows users to authenticate once and gain access to multiple services without the need to log in separately. This Single Sign-On functionality reduces login fatigue and enhances the overall user experience. • Role-Based Access Control (RBAC): Keycloak administrators can define roles and permissions, which determine what actions or resources users can access. This model helps maintain strict security and personalized user access. • Token-Based Authentication: Upon successful authentication, Keycloak generates a JWT (JSON Web Token) containing user information and roles. This token is then used for all subsequent service requests, ensuring secure access and communication between services. Authentication of the services For each service, Keycloak handles authentication and authorization to ensure secure access control: 1. Login and Token Generation: When users access a service, they are redirected to Keycloak for authentication. If the credentials are validated, Keycloak issues a JWT token. 2. Single Sign-On (SSO): Users authenticated in one service are not required to log in again when accessing other services. 3. Token validation: Each service validates de JWT token provided by Keycloak to confirm the user’s identity and roles. Based on these roles, the service grants or restricts access to functionalities 19 Communication with Services The Service Container describes in D5.5 Service Container and Procedures description for Connections plays a relevant role in managing the integration and interaction of external services. It supports two types of external services integrations: • Standalone iFrame: Allows external services to be displayed and operated within the CircThread Platform environment at its window. • API with Reference Web Link: Facilitates two-way data transfer between the CircThread platform and external services, enabling interaction through an external browser window or tab Figure 2 Service Container integration ( Deliverable 5.5 Service Container and Procedures description for Connections ) 3.2.1 System use by the services S8 Legacy Product Identification Service and S9 Damaged Product Circularity Assessment Service (SIMAVI) These services use two mechanisms for authentication and registration: Authentication and Registration 1 Role-Based Authentication: In the current version of the service (standalone), user authentication and authorisation is handled by a proprietary role-based system. Each user is assigned a role at the time of registration, which determines the functionalities they can access within the application. Only users with specific roles can access certain windows and functionalities, guaranteeing data security. 2. Integration with the CircThread Platform: In the new version it will be integrated with the CircThread Platform and will use Keycloak, which is CircThread's identity management and authentication tool. Keycloak will provide external authentication and authorisation, allowing platform users to securely access different services using a single centralised authentication. 20 Registration Mechanism Registration Page: The registration process is required to access the contents of the service. Registration requires several pieces of information, including Registration code (predefined and provided by the organisation) • Organisation • Country • Email address • Username • Password S13 End-of-Use Collection Circularity Recommendations Service (EKOD) The service uses an authentication and registration system based on integration with the CircThread Platform, which manages the identity and access of users. Authentication and Registration 1. Authentication through the CircThread Platform: The service is integrated with the identity management system of the CircThread platform. When a user tries to access the service, they are redirected to CircThread's central authentication system. Users log in using their credentials within the CircThread platform, which is responsible for verifying and authenticating users before granting them access to the service. 2. User Roles: Users are classified into different roles within the system, such as operators, experts and managers, each with different levels of access and permissions. The system uses these roles to ensure that only authorised users can access certain functionalities or make critical decisions within the service. 3.QR Code access: For operators working in product picking, the service allows quick access through QR code scanning of products. This process is authenticated through the CircThread platform, linking the user with the scanned products and the actions performed. S10 Circular Sustainability Advisory Service (SUPSI) The Circular Sustainability Advisory Service (GRETA) uses an authentication and registration system based on a microservices architecture that integrates an Identity Provider to manage user authentication and access control. The key components of this system are detailed below: 21 Authentication and Registration System 1-Identity Provider: GRETA uses an Identity Provider that implements standard authentication protocols, such as OpenID Connect. This provider manages the users, roles and groups that have access to the platform. Each user must authenticate by providing their credentials (username and password). The Identity Provider generates a JWT (JSON Web Token), which contains the user information, including roles and groups, and this token is used for subsequent requests within the platform to control access. 2.API Gateway: All user requests pass through an API Gateway, which acts as an entry point to ensure secure communications. This gateway verifies the JWT token provided by the Identity Provider to authenticate requests before allowing access to GRETA services. 3.Authentication Manager: Manages the associations between users and the domains to which they belong (also called ‘realms’) and verifies the roles and permissions associated with each user. This administrator communicates with the API Gateway to validate requests based on the user's credentials and the permissions associated with their account. Authorisation and Roles Users in GRETA are assigned to different roles, such as sustainability experts, designers or producers. These roles determine the level of access and the functionalities they can access within the platform. The system ensures that users can only access the data and functionalities corresponding to their role and domain, providing a high level of security and personalisation of access. Authentication Flow 1.The user accesses the GRETA platform and enters his/her credentials in the login interface. 2. The credentials are sent to the API Gateway, which passes them to the Identity Provider. 3. If the authentication is successful, the Identity Provider generates a JWT containing the user's information, such as roles and permissions. 4.The JWT token is used to authenticate all subsequent requests through the API Gateway. 5.GRETA services verify the token to allow or deny access to functionalities according to the assigned roles. S14 Circular Design Recommendations Service The service uses an authentication and registration system based on integration with the CircThread Platform, which manages the identity and access of users. 22 1. Authentication through the CircThread Platform: The service is integrated with the identity management system of the CircThread platform. When a user tries to access the service, they are redirected to CircThread's central authentication system. Users log in using their credentials within the CircThread platform, which is responsible for verifying and authenticating users before granting them access to the service. 2. User Roles: The service is developed for designers from Original Equipment Manufacturers organisations. The system uses role and organisation identification to ensure that only authorised users from authorized organisation can access certain functionalities or make critical decisions within the service. S11 Manufacturing Supplier's Intelligence Service (MSIM) 1. The service has been developed alongside GRETA platform, therefore it exploits the same authentication mechanism. Since it is only a backend service it does not expose directly a UI so the API communication is secure through the exchange of a long term JWT token issued from the same IAM of GRETA platform. By means of an API gateway only the necessary endpoints are authorized for the specific token (by means of the assigned role). 23 4. TESTING SCENARIOS The testing scenarios for the integration of services in WP6 are designed to validate the functional, technical, and security aspects of the integrated system. These scenarios aim to ensure that all services (T6.1 to T6.6) communicate effectively, exchange data correctly, and function as expected under various conditions. Testing will be conducted in stages, beginning with unit testing for individual services, followed by integration testing of combined services, and concluding with end-to-end system testing. Additionally, security testing will be performed to ensure data integrity, privacy, and compliance with the project's security requirements. Some of the activities to follow the testing strategy has been developed, but the full integration will be achieved during the piloting phase in WP7 4.1 Overview of Testing Strategy The testing strategy followed a phased approach: • Unit Testing: Each service (T6.1 to T6.6) underwent individual testing to ensure its core functionalities worked as expected. Each service independently verifies its features before being integrated into the Service Container. • Integration Testing: Once individual services have been validated, they in same case have been tested in combination with other services to validate data flows and communication. Ensure that services like S8 Legacy Products Identification Tools and NIRware can exchange data accurately. This includes validating API endpoints, testing cross-service interactions, and verify data integrity. • System-Wide End-to-End Testing: Full system testing will be performed to ensure that the entire workflow, from data input to final output, operated without errors or disruptions. Use cases and pilot activities to confirm that services can communicate smoothly, data flows seamlessly between them, and the final outputs (such as reports or circularity recommendations) are accurate and consistent. • Security Testing: Security tests focuses on safeguarding data exchange between service using secure protocols, and standardized authentication procedures like KeyCloak will be carried out to detect vulnerabilities and ensure data security across services. • Performance and Stress Testing: The system will be tested under different loads to assess performance, scalability, and reliability. It will be tested scenarios with large amounts of data, simultaneous user loggings, and heavy data exchanges between services, to ensure the system remains responsive and reliable. The testing scenarios covered multiple aspects: • Functional Testing: To ensure each service performs its intended functions. • Interoperability Testing: To validate smooth communication between services and consistent data exchanges. • Performance Testing: To measure response times and system behaviour under different levels of user load. • Security Testing: To verify that data is handled securely, and unauthorized access is prevented. • Edge Case Testing: To handle exceptions and uncommon but possible conditions. 24 4.2 Detailed Integration Testing Scenarios S8: LEGACY PRODUCT DATA IDENTIFICATION SERVICE Phase Procedure Outcome Status Comments Unit testing Enter technical details for legacy products, including attributes like product type, components, materials, and hazardous substances. Generate a BoM report based on the entered data. Technical details, component information, and hazardous substances are correctly recorded. BoM report is accurately generated. Done Several tests have been carried out in SIMAVI environment for the development of the service. Also, test has been done with Slovenian actors. Integration testing Test integration with the NIRwave service to confirm that S8 can automatically identify polymer materials in components through spectrometry. Verify that the captured polymer data is linked accurately within the BoM. Add new products in S8 and verify that data is accessible to other services via the middleware. Data from NIRwave is accurately incorporated into the BoM report. Other services can access and use the data through the middleware. In Progress Several tests have been carried out during the development phase of the service. Also, integration with NIRware has been done with Slovenian pilot. Also, some test has been done too with Spanish materials to expand the background polymer database. Integration with DPP has been test in the Slovenian pilot. Detailed product and information workflows have been designed for Slovenian pilot. Need test for the rest of the pilots. Endto endtesting Simulate a collector/recycler enter to the service a legacy product to record its technical details, perform a component identification check via NIRwave, and generate a BoM report. The entire workflow runs smoothly, with all relevant details accurately recorded and reflected in the BoM report. In Progress Test have been developed to Slovenian pilot. It needs to be Include also test for the other pilots. 25 S8: LEGACY PRODUCT DATA IDENTIFICATION SERVICE Phase Procedure Outcome Status Comments Security testing Test user authentication using Keycloak, and assign roles such as collectors, product managers, and recyclers. Attempt unauthorized actions. Only authorized users can access and modify relevant data, with unauthorized attempts blocked and logged. To be done Verify that the integration with the platform works. The actors have been defined in the Slovenian pilot. The actors need to be verified with Spanish and Italian too. Setup the service in the service container of the platform. Performance testing Perform bulk uploads of product data simultaneously. Monitor system response times and server performance during uploads. The system processes bulk uploads efficiently without significant delays or crashes. To be done Try to perform the use of the service from different pilots at the same time. (WP7) Edge Case Testing Enter partial or incorrect product information, such as missing product tags or incomplete technical details. Attempt to generate a BoM report with incomplete data. The system detects missing or incorrect information, prompts the user for corrections, and prevents incomplete reports. To be done Some missing data need to be implemented, and also wrong actors to verify messages and get feedback from users to improve the services S8, S7 will mainly be tested for UC3, UC4 and UC6, to have a better characterisation of the product at the end of the life cycle. It provides the BoM, as well as CRM content information. In UC3 it is linked to parts recovery, and with S9, they must have the spare parts list from the manufacturer or repairer as well as the damaged product criteria implemented by the producers. Example step by step 1. Verify individual performance with actors from other pilots. Permissions to Reydesa as recycler and Domusa as manufacturer. Have the list of spare parts Have criteria for damage product (for S9) 2. Register the service as a service provider on the platform. 3. Verify the inclusion and operation of the service in the service container. (check also security testing) 32 S13 END OF USE RECOMMENDATION SERVICE Phase Procedure Outcome Status Comments end-of-use recommendations. Endto endtesting Simulate the entire process from product registration and data entry to generating end-ofuse recommendations based on product lifecycle assessments. Comprehensive and accurate recommendations that align with product lifecycle assessments. In progress Include in WP7 integration. Define the actors and steeps to follow in the different use cases and complete a full cycle Security testing Assign roles using Keycloak and restrict access to end-of-use recommendations based on roles such as recycling operators and managers. Attempt unauthorized modifications. Role-based access controls are enforced, preventing unauthorized modifications. In progress Verify that the integration with the platform works. The actors and roles have been defined. Setup the service in the service container of the platform. Performance testing Perform multiple end-of-use evaluations simultaneously and monitor system performance under different loads. Measure response times and processing efficiency. Efficient processing of multiple recommendations without significant delays or performance degradation. To be done Edge Case Testing Enter incomplete or incorrect lifecycle data for a product and attempt to generate an endof-use recommendation. The system detects missing or incorrect lifecycle data and prompts the user for correct To be done With the actors selected, it could also be done as the end to endtesting 33 S13 END OF USE RECOMMENDATION SERVICE Phase Procedure Outcome Status Comments Validate error handling and user prompts for corrections. S14 CIRCULAR DESIGN RECOMMENDATION SERVICE Phase Procedure Outcome Status Comments Unit testing Perform an analysis of product designs to identify disassembly failures or inefficiencies, focusing on specific parts or assemblies. Calculate the circularity index based on captured product data, disassembly metrics, and recovery potential. Accurate identification of problematic components and reliable calculation of the circularity index to guide design improvements. Done Integration testing Test the integration with BoM Manager to ensure that the disassembly information and failure points are continuously updated in the BoM. Validate integration with sustainability assessment tools to receive circularity performance data. Accurate and realtime data exchange between the Circular Design Recommendations Tool and other services. To be done Endto endtesting Simulate the full design review process, from uploading BoM data to running disassembly analysis and Smooth data flow and generation of detailed design recommendations based on real-time disassembly analysis. To be done 34 S14 CIRCULAR DESIGN RECOMMENDATION SERVICE Phase Procedure Outcome Status Comments generating design recommendations. Generate a report showing recommended design improvements. Security testing Use Keycloak to assign roles (e.g., product designers, project managers). Test restricted access for unauthorized users attempting to modify design recommendations. Role-based access controls are enforced, and unauthorized actions are blocked. In Progress Performance testing Perform largescale disassembly analysis on multiple products simultaneously. Measure response times and data processing speed. The tool maintains stable performance with acceptable response times even under high loads. To be done Edge Case Testing Enter incomplete BoM data and attempt to perform disassembly analysis. Simulate disassembly reports with outdated component details. The system detects missing or outdated information, prompts users for updates, and prevents generating invalid recommendations. To be done 4.3 Validation Criteria Establishing an evaluation framework is essential to ensure the success of the CircThread platform integration. The evaluation criteria will be focused on key aspects such as data flow accuracy, functionality, interoperability, security, and system performance under varying conditions. These criteria provide a structured approach to validate that the services developed within WP6 meet technical, functional, and security standards. By assessing the system against these benchmarks, the project ensures reliable operation, seamless communication between services, and alignment with circular economy objectives, paving the way for effective implementation in industrial environments. 35 The success of each testing scenario will be measured using predefined validation criteria: • Data flow accuracy: It should be ensured that data transmitted between services is processed without errors, loss or corruption during transmission. The criteria used will be: ✓ Validation of accurate and complete data in unit and integration tests ✓ Testing for compatibility and consistency in multi-service scenarios • Functionality: Verify that all the services operate as intended, delivering the expected outputs and aligning with their defined roles in the system. The criteria will be: ✓ Validation of each service’s core functionalities during unit testing ✓ Endto end testing to confirm system-wide functionality in real world scenarios • Interoperability: Guarantee affective and continuous communication between integrated services. The criteria include: ✓ API validation during system testing ✓ Verification of functionalities between services, including product identification, sustainability evaluation, and circular recommendations • Security: A Evaluate the implementation of security measures, including centralized authentication (Keycloak) and encryption protocols. In this case, the criteria involve: ✓ Testing roles and access as per specifications. ✓ Simulating unauthorized access attempts and effective mitigation. • Performance: Asses system stability with multiple users and large volumes of data. The criteria for the performance testing include stress and load testing with highconcurrency simulations. 36 5. CONCLUSION AND NEXT STEPS The integration and testing efforts outlined in WP6 will demonstrate the progress toward establishing a cohesive, secure, and efficient system for the CircThread platform. By ensuring interoperability between services, robust data protection, and compliance with circular economy principles, the project is well-positioned to achieve its sustainability goals. This section highlights the activities of the integration process, identifies areas for improvement, and offers targeted recommendations to enhance the system's performance, usability, and scalability. These insights will be crucial as the platform transitions into the industrial phase, supporting real-world applications in pilot settings. Key outcomes: • Interoperable System: Effective integration between services will confirm the system’s functionality as a modular and scalable platform. • Alignment with Security Standards: Tests will validate the efficiency of Keycloak and other protocols in securing data and managing access. • Support for Circular Economy Goals: Services enable data-driven decisions, facilitating sustainability through repair, recycling, and reuse initiative As the integration phase advances, the focus now shifts toward broader system implementation and validation in real-world environments. The next steps involve leveraging the insights gained from testing to refine the system, ensuring its readiness for industrial-scale deployment. By addressing remaining challenges, optimizing performance, and expanding pilot testing, the CircThread platform will transition seamlessly from development to operational use, driving sustainability and circularity within the ecosystem. Key observations include: Global Integration: • Implement service integration as part of the complete system in pilot environments. • Configure the service container on the platform, ensuring all required functionalities are included. Pilot Testing Execution: • Conduct comprehensive testing with all stakeholders involved (manufacturers, recyclers, designers). • Document issues and resolution strategies to optimize the system before industrial deployment. Technical Improvements: • Apply adjustments based on load and performance test results. • Update components with security gaps or improvement needs. 37 Planning for Industrial Phase: • Ensure the system is fully validated and ready for deployment in real operational environments. • Define success metrics for the WP7 phase, including scalability, security, and user experience parameters.