Deliverable 5.4: Platform Implementation V1 Status Overview

This project has received funding from the European Union’s H2020 Programme under Grant Agreement No. 958448 WP 5 CircThread Architecture Development and Implementation Task 5.4 CIRCTHREAD DIGITAL THREAD IMPLEMENTATION Deliverable 5.4 PLATFORM IMPLEMENTATION V1 STATUS OVERVIEW Ref. Ares(2025)139361 - 09/01/2025 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. ACKNOWLEDGEMENT 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. 5.4 Deliverable title Platform Implementation v1 Status Overview Description Linked to T5.4 Provides the Platform Implementation v1 Status Overview for the CircThread projects including as outcomes: an overview of the iterated CircThread architecture following the T5.1 basis and agile developments from the architecture, a description of the integrated CircThread Digital Thread implemented with the components from T5.2 and T5.3 and the added API and communication interface and an authentication system for roles and users with a user environment. A summary of laboratory testing scenarios for the CircThread prototype instance. WP No. 5 Related task T5.4 CIRCTHREAD DIGITAL THREAD IMPLEMENTATION Lead Beneficiary EKODENGE Contributor(s) Yigit Yayalar, Umut Makascioglu, Tugba Aslan, Rembrandt Koppelaar Type Report Dissemination L. Public Language English – GB Due Date 30/11/2024 Submission Date 09/01/2025 4 Version Action Owner Date V.0.1 TOC, Written EKODENGE 25/11/2024 V.0.2 Initial Chapter Drafts EKODENGE 2/12/2024 V.0.3 First Draft of All Chapters EKODENGE 9/12/2024 V.0.4 Internal Review EKODENGE 10/12/2024 V.0.5 Advanced Draft EKODENGE 20/12/2024 V.0.6 Final Draft EKODENGE 27/12/2024 V.0.7 Copy-edited & reviewed ECOWISE 08/1/2025 V.1.0 Final checks for submission CARTIF 08/01/2025 5 1 EXECUTIVE SUMMARY CircThread is a H2020 EU-funded project with the objective to unlock access to product data for circular economy purposes. The main target is to facilitate information flow exchanges across the extended product life cycle. The information can vary from data consisting of product characteristics, product components, their materials and chemicals data, and related circularity, environmental, social, and economic information. This data will be captured, linked, and shared on a cloud-based, collaborative, Ecosystem with a software Platform with a core set of open-source modules, to allow all actors throughout the product life cycle to share the necessary information. To ensure that more materials and products stay in the economic loop, benefitting the sustainability of the economy and the environment and reducing carbon emissions. This deliverable D5.4 provides an overview of the CircThread platform implementation, an IT product information management platform for the Circular Economy. An overview is provided of the finalised CircThread architecture as evolved from D5.1, a description of the integrated CircThread Digital Thread implemented with the components from T5.2 and T5.3, and the added API and communication interface and authentication system for roles and users within the platform user environment. The deliverable also includes a description of all user interfaces and functionalities of the CircThread piloting instance that is up and running. The deliverable first outlines the description of the platform with its purpose and development activities. The text then continues by describing the implemented software architecture. The software implementation consists of descriptions of microservices, authentication systems, and used technologies to establish the IT infrastructure. Then, the next part details the CircThread platform services with their user interfaces and main functions. Finally, the integration of the CircThread Platform with external services is explained with specific services connected for the digital thread implementation. This deliverable will be useful for public and private initiatives focusing on building circular economy product information management ecosystems, to facilitate product information exchanges between actors across the product life cycle. As well as the CircThread software delivery partners to guide them on the journey to deploy the CircThread Platform. 6 Contents 1 EXECUTIVE SUMMARY ......................................................................................................... 5 2 INTRODUCTION ....................................................................................................................... 8 2.1 Overview .............................................................................................................................. 8 2.2 Methodology ....................................................................................................................... 8 2.3 Structure of the report ..................................................................................................... 8 3 CIRCTHREAD PLATFORM DESCRIPTION ................................................................... 9 3.1 Purpose ................................................................................................................................. 9 3.2 CircThread Platform v2 description .......................................................................... 12 3.2.1 Microservice Architecture ........................................................................................... 12 3.2.2 IT System Components ................................................................................................. 13 3.2.3 CircThread Platform developed services ............................................................... 15 3.3 Restful Open API Implementation ............................................................................. 16 3.4 Main Functionalities ....................................................................................................... 18 3.4.1 Ecosystem instance setup ............................................................................................ 18 3.4.2 Organisation Registry .................................................................................................... 19 3.4.3 User Registry .................................................................................................................... 19 3.4.4 Product Model Registry ................................................................................................ 19 3.4.5 DPP provider Registry ................................................................................................... 19 3.4.6 Product Model Search ................................................................................................... 19 3.4.7 DPP Linkages .................................................................................................................... 20 4 CIRCTHREAD PLATFORM USER INTERFACES ....................................................... 21 4.1 Ecosystem Admin ............................................................................................................ 21 4.2 Manufacturer (Economic Operator) .......................................................................... 26 4.3 Product Lifecycle Actors ............................................................................................... 30 5 SERVICES INTEGRATION .................................................................................................. 34 5.1 Overview ............................................................................................................................ 34 5.2 DPP data providers integration .................................................................................. 35 5.3 Metadata Catalogue Integration ................................................................................ 35 5.4 Integration with CircThread External Services ...................................................... 37 6 Conclusions and Next Steps................................................................................................ 39 6.1 Conclusions ....................................................................................................................... 39 6.2 Next steps .......................................................................................................................... 39 7 List of Figures Figure 1: CircThread Ecosystem Scheme ................................................................................................................... 11 Figure 2: Microservice Architecture ............................................................................................................................ 13 Figure 3: System Architecture Overview .................................................................................................................... 14 Figure 4: Swagger page of the development environment ..................................................................................... 16 Figure 5 : Login request example on the API documentation page ...................................................................... 17 Figure 6: Create an organisation .................................................................................................................................. 21 Figure 7: Edit Organisation ............................................................................................................................................ 21 Figure 8: Viewing Roles and Edit Button .................................................................................................................... 22 Figure 9: Create a Role .................................................................................................................................................... 22 Figure 10: Add/Remove users ....................................................................................................................................... 23 Figure 11: Add user to the organisations ................................................................................................................... 23 Figure 12: Registration e-mail example ...................................................................................................................... 24 Figure 13: Create a new DPP provider ....................................................................................................................... 24 Figure 14: Viewing DPP providers in the ecosystem ............................................................................................... 25 Figure 15: Create a new service.................................................................................................................................... 25 Figure 16: Register new product models .................................................................................................................... 26 Figure 17: Viewing product models ............................................................................................................................. 26 Figure 18: API Key and Secret generation ................................................................................................................. 27 Figure 19: Synchronisation with DPP provider ........................................................................................................ 27 Figure 20: Link for DPP................................................................................................................................................... 28 Figure 21: Sample Product Model DPP ...................................................................................................................... 28 Figure 22: Link for metadata catalogue ..................................................................................................................... 28 Figure 23: Sample Metadata Catalogue .................................................................................................................... 29 Figure 24: Vewing of services ........................................................................................................................................ 29 Figure 25: Button for request to use service .............................................................................................................. 29 Figure 26: Searching product models.......................................................................................................................... 30 Figure 27: Viewing product model details ................................................................................................................. 31 Figure 28: Request for viewing DPP ............................................................................................................................ 32 Figure 29: Viewing available services ......................................................................................................................... 33 Figure 30: Services container integration overview ................................................................................................ 35 Figure 31: Metadata catalogue feature on the search page .................................................................................. 36 Figure 32: Metadata catalogue feature on the product model view page ......................................................... 36 Figure 33: S8 integrated API endpoints ..................................................................................................................... 37 Figure 34:S10-Greta integrated API endpoints ....................................................................................................... 37 Figure 35: A request result from a Greta endpoint .................................................................................................. 38 8 2 INTRODUCTION 2.1 Overview The CircThread project aims to develop and demonstrate the digital means to enable product information exchanges across the life cycle of a product. It seeks to develop a Circular Digital Thread (CircThread), where product information is collected, updated and shared for individual products across the product life cycle. The possible information exchanges from such a digital setup are critical to improve decision making and enable services and associated business models to increase product recycling, increase product lifespan, and enhance product reuse. The deliverable describes the developed CircThread Platform version 2 carried out up to November 2024, which is being used for piloting under WP7. 2.2 Methodology This deliverable is the result of T5.4, which has been carried out based on agile software development processes. The basis was the deliverable 5.1 that described the software architecture of the CircThread platform. The methodology also covered detailed IT design workshops, sequence diagram creation, user story creation, and dataflow designs. As well as feedbacks from pilot actors that has led to different additional features. 2.3 Structure of the report The deliverable is structured to provide a comprehensive overview of the CircThread Platform, its architecture, functionalities, and integration capabilities. Chapter 3 introduces the platform, detailing its purpose in fostering ecosystem development and outlining its microservice architecture, including authentication mechanisms and employed technologies. The chapter also elaborates on its main functionalities, such as ecosystem setup, product model registry, DPP provider registry, and integration capabilities with external DPP providers. In Chapter 4, user functionality and user interfaces are defined to demonstrate how users interact with platform functionalities. Chapter 5 focuses on services integration, starting with an overview of the integration framework, followed by specific discussions on metadata catalogue integration and connections with services developed in WP6. The deliverable concludes in Chapter 5 with a summary of findings and recommendations for next steps, setting the stage for future developments and implementations. 9 3 CIRCTHREAD PLATFORM DESCRIPTION 3.1 Purpose The CircThread project seeks to develop a common data Ecosystem as a new digital infrastructure that will enable the exchange of product information across the life-cycle of Electronic and Electrical Equipment (EEE). A digital Ecosystem is defined as a group of interconnected IT resources that can function together, whereas a Platform is an online software infrastructure that facilitates interactions between users. In the case of CircThread an Ecosystem will be developed that can combine many interconnected IT resources. The purpose of the CircThread Ecosystem is to enable novel digital solutions to existing challenges to make products with a wire circular. Examples of these challenges as identified in Work-Package 2 of CircThread include: • The absence of coordinated information sharing about products. • The lack of visibility on products through their life cycle stages from usage to collection, reuse and recycling. • The unfulfilled need of consumers for circular economy product information at point of purchase, during usage and collection. • The absence of a common system to retrieve spare parts from end-of-life products. • The limited information available to recyclers on the materials and chemicals content of the products they recycle. • The lack of shared disassembly knowledge and feedback between manufacturers and disassembly workers at recycling facilities. The new digital infrastructure will lower the cost to establish information exchanges by developing coordinated means for them, using Digital Product Passports, a Product MetaData catalogue, and a Digital information exchange system. The CircThread Ecosystem enables the following IT capabilities (see also Figure 1): • The registration and validation of organizations and their users based on their roles across the life cycle of products. Based on their roles they will have different permissions for writing, reading and exchanging information. • The central registration of product models, which form the basis of a model in a company’s line of devices or appliances. Product model numbers allow for identifying the devices that are part of the same model. The product model information is the basis for relating the relevant information in terms of documents at product model level to a product from its physical label. • Digital Product Passports Linkage for individual product passports or batches under a product model, based on a linkage between the product model, the item level identifier or batch identifier that allows the identification of a product/batch, a product tag such as a QR code for the digital-physical linkage, and the digital product information captured in the passports. • The generation of product meta-data catalogues at the product model level to enable a registry of potentially available information for exchange at document and database entry to database entry level or similar. The catalogue captures in a 16 3.3 Restful Open API Implementation In order to provide a more thorough understanding of the platform and the functions that operate under the hood, swagger pages are automatically generated for each instance of the platform (see Figure 4 for a generated example). It should be noted that the functions that are visible on the swagger page do not contain all of the backend functions of the whole CircThread platform. In v2 of the CircThread Platform, adding a token for the listed functions is not possible on the swagger page. Figure 4: Swagger page of the development environment In addition to the swagger page, a separate API documentation page is under development to be part of v3, for release by February 2025 (see Figure 5). The purpose of this page is to provide detailed information regarding the available endpoints of the platform. This to enable users to inquire about the functions of the endpoints and the data bodies that are sent and received from the requests. Also request structures for different programming languages are given to provide ease for more technical partners. 17 Figure 5 : Login request example on the API documentation page 18 3.4 Main Functionalities The CircThread Platform is designed to address the unique needs and responsibilities of its diverse user base, ensuring an intuitive and tailored experience for each stakeholder. To achieve this, the platform provides distinct user interface functionalities based on each different user role, and linked backend access differentiations, enabling appropriate authentication and security based interactions within the ecosystem. This is necessary to foster collaboration across the product lifecycle on a restricted data and need to know only basis, so that each party such as a manufacturer, a retailer, a recycler, or another party can be confident that when it shares sensitive data it is only viewable by the appropriate counterparty. The predetermined roles are ecosystem admins, manufacturers (economic operators), and product lifecycle actors: • Ecosystem admins are responsible for overseeing and managing the platform's ecosystem. Their functionalities are centred around creating, maintaining, and monitoring the ecosystem infrastructure to ensure all stakeholders can operate effectively and securely. • Manufacturers (Economic Operators) play a critical role as creators of product models and custodians of product lifecycle data. Their functionalities enable the efficient registration, management, and integration of product models and Digital Product Passports (DPPs) to comply with regulatory and market requirements. • Product Lifecycle Actors, such as recyclers, repairers, and refurbishers, interact with the platform to access and contribute data related to product usage, maintenance, and end-of-life stages. Their functionalities support circular economy practices by providing tools to retrieve, update, and utilize critical product information. The CircThread platform v2 includes a flexible roles management system as part of the identity management service, so as to enable a wide range of product lifecycle actor roles to be managed depending on the ecosystem needs. 3.4.1 Ecosystem instance setup The Ecosystem instance Setup feature empowers ecosystem administrators to initiate and configure a new instance of the CircThread Platform independently. By providing access to a well-documented Git repository, this feature guides administrators through the necessary steps to deploy an instance of the platform. CircThread’s architecture for deployment utilises Docker. Therefore, the Ecosystem admin must first setup Docker and Docker compose via the docker-setup.sh provided in the project Git repository. Following the Docker setup, the Ecosystem admin must also run the CircThread-stup.sh script that will ask the following parameters; • An existing domain that will be used as the website of the platform. • Email for the SSL certificate. • Database password. • SMTP server address, port and credentials. • IDS credentials. 19 After successfully providing these, the script will setup necessary microservices and the CircThread instance will be ready to use. 3.4.2 Organisation Registry The Organization Registry serves as a centralized directory for registering and managing all organizations participating in the ecosystem. It captures detailed information, including organization type, and industry. The function enables secure, role-based access to ensure compliant data sharing and collaboration between ecosystem members. 3.4.3 User Registry The User Registry maintains a comprehensive database of all platform users and associates them with their respective organizations and ecosystems. It provides rolebased access control, assigning permissions based on user roles such as admin, editor, or viewer, to define the scope of activities they can perform. The function facilitates user onboarding through streamlined processes such as email verification and Single Sign-On (SSO) integration via Keycloak. 3.4.4 Product Model Registry The Product Model Registry functions as the core repository for managing product models within the CircThread Platform. It stores product model description, product model name, product model identifiers, and also a link to the metadata catalogue of the product model. In addition, product models can be linked to associated Digital Product Passports (DPPs) for a seamless integration of product and lifecycle data. The product model registry ensures that all information exchanges can be related to the same product model as a verification system. 3.4.5 DPP provider Registry The DPP Provider Registry maintains a directory of all registered Digital Product Passport providers integrated into the CircThread platform. This registry ensures interoperability between different product passports and their providers. This feature uses APIs and middleware to facilitate standardized data exchange. 3.4.6 Product Model Search The Product Model & DPP Search function provides users with powerful capabilities to locate both product models and their associated Digital Product Passports (DPPs) and product model catalogues within the platform. It supports advanced search options, allowing users to filter and query based on criteria such as product type, lifecycle phase, industry, or specific keywords. This functionality enables quick and efficient retrieval of relevant product and DPP data, streamlining processes such as linking DPPs to product models. The search interface is designed to be user-friendly, offering sorting and categorization options to enhance usability. In addition, the search interface is linked to a specific landing page for a product model that gives basic information and the related linkages to its DPPs, catalogues and other external services linked to it within the ecosystem. Thereby forming a main navigation feature in the CircThread Platform. 20 3.4.7 DPP Linkages A critical feature of the CircThread Platform is its ability to serve as a Digital Product Passport registration service, with referencing to the web URIs of DPPs, both using centralised data architecture as well as novel decentralised frameworks such as Decentralized Identifiers (DIDs) and blockchain infrastructures. Thereby it allows for novel information exchange infrastructures from/to Digital Product Passports and information acquisition as well as information processing services, within supply chain and product life cycle contexts. It also allows for future use cases where data is transferred from Digital Product Passports from product component to Digital Product Passports of final products. As well as use cases where information is compared between different Digital Product Passports of manufacturers for the same product type. 21 4 CIRCTHREAD PLATFORM USER INTERFACES In this chapter, the user options in the CircThread Platform are described based on the services developed based on brief descriptions and screenshots of related user interfaces. 4.1 Ecosystem Admin Register organisations: The Ecosystem admin can create new organisations to ecosystem and provide the available access roles for the organisation (Figure 6). Figure 6: Create an organisation. Edit organisations: The Ecosystem Admin can edit the organisations that are registered and assign their roles (Figure 7). Figure 7: Edit Organisation. 22 Role definitions: The Ecosystem Admin can create and edit roles for ecosystem users by entering the role name (Figure 8 and Figure 9). Figure 8: Viewing Roles and Edit Button. Figure 9: Creating a Role. 23 Add/Remove users: Ecosystem admin can register users to the organisation by entering users’ email, users’ name and surname (Figure 10 and 11). In addition, the users can be removed from the organisation. Figure 10: Adding/Removing users. Figure 11: Adding user to the organisations. Receive registration email: Once the users are registered, they receive an email which includes password information and their CircThread platform instance link (Figure 12). 24 Figure 12: Registration e-mail example. Register DPP providers: Ecosystem admin can register DPP providers by entering provider name, organisation name, and provider endpoint (Figure 13). Figure 13: Creating a new DPP provider. View DPP providers: The Ecosystem Admin can view existing DPP providers registered in the ecosystem (Figure 14). 25 Figure 14: Viewing DPP providers in the ecosystem. Register services and assign roles to services: The Ecosystem admin can view existing services from CircThread partners in the ecosystem and also register new ones by entering service name, service organisation name, service type and endpoints and authentication endpoint (Figure 15). In the service registration also, specific access roles can be selected as previously defined in the platform instance, to enable service level role authentication. Figure 15: Creating a new service 32 Figure 28: Request for viewing DPP. View available services for the product model: By clicking on the ‘available services’ button from the interface that is shown in Figure 27, users can see the services that are available for the product model and their roles. In addition, they can request to use these services by clicking on the button which is located on the service card. This button is shown in the Figure 29 with red rectangle. 33 Figure 29: Viewing available services. 34 5 SERVICES INTEGRATION 5.1 Overview The CircThread Ecosystem becomes more useful when a large number of external services are integrated, so as to provide for particular data processing and information provisioning needs in relation to particular use cases in either the product supply chain and/or the product life cycle. The aim of the services registry and platform integration is to enable discovery and use of external services in CircThread in a user friendly and easy to use manner, as well as to orchestrate the information flow from/to external services in conjunction with the use of Digital Product Passports and Metadata catalogues. The services may have different infrastructures in terms of software. It may that an external service can be used with web-based access (e.g. to route the user to the user interface of the service), or it simply consist of background services (to retrieve specific data-points for the product model in a hidden automated manner, that can then be viewed or accessed and used in another service). The integrations thereby include i-frame user interface access as well as backend integration options, or a combination of both. The integration details need to be specified for each service or application available in the services registry and associated services container. Also, a clear description of the service, how to use it, and the main contact point for the service is needed. New external services can be added to the CircThread Platform through a registration process. The starting point of this process requires provisioning of information about the services in a standardised structure. Two information sets are needed: • Descriptive information, including the name of the service, details of its owner and IPR and associated usage conditions, and a brief description. • Technical information, including the product information the service needs to operate, and provides to the user, the API endpoints and information exposed, and where the service’s host IP and port information are held for its integration in the CircThread Platform. The information entered regarding the external service need to be saved to the services registry database of the CircThread Platform, including the endpoints provided for the integration process of each service. The Services Container allows for three types of external services integration (see also Figure 30 below): • A standalone iFrame, which provides for a window to view and operate the respective external service within the CircThread Platform environment and its window or tab; 35 • An API with a reference weblink, which provides for two-way data transfer between the CircThread Platform and the external service, where the external service if using an interface is operated in a different browser tab or window separate from the CircThread Platform. • A standalone iFrame + API with a reference weblink, where both options are combined to enable frontend and backend interactions. Figure 30: Services container integration overview. 5.2 DPP data providers integration EKODENGE has provided their TRACID DPP service as a reference example for integration with the CircThread Platform, including their swagger page and endpoints documentation. The service was successfully integrated with the CircThread Platform and the integration is fully completed as an example of a DPP provider integration case. 5.3 Metadata Catalogue Integration CARTIF has provided their swagger page for their service as part of the release of CircThread v2 in November 2024. The endpoints are being tested by the software team of EKODENGE to ensure all information flow is ready for integration. Once the testing of the endpoints of the Metadata Catalogue and the discussion between the two partners is concluded, the integration of the Metadata Catalogue will be finalised in Q1 2025. Already under v2 the search and product model viewing pages the users are given the option to use the metadata catalogue feature, which act gateways to the service (see Figure 31 and 32). 36 Figure 31: Metadata catalogue feature on the search page. Figure 32: Metadata catalogue feature on the product model view page. 37 5.4 Integration with CircThread External Services For CircThread S8 (Legacy Products Data Identification service), SIMAVI has provided EKODENGE with the API documentation for the service and a token for testing (Figure 33). The endpoints are integrated in the development environment and testing is ongoing for the complete integration. Figure 33: S8 integrated API endpoints. For CircThread S10 (GRETA), SUPSI has provided their API documentation as well as a lifetime token that can be used for testing (Figure 34). These have been integrated within the development environment and tested. Figure 34:S10-Greta integrated API endpoints. 38 Figure 35: A request result from a Greta endpoint. For S8 and S10, the next steps will be the visualisation of the results of the requests on the pages. Once the documentation for further services is provided to the software team of EKODENGE, the endpoints for these services will be integrated, the tests with or without authentications tokens will be conducted, and the results will be visualized on the pages respectively. This will conclude the integration of the services within the scope of CircThread, and provide for a route for further integration of relevant services beyond the scope of the project. 39 6 CONCLUSIONS AND NEXT STEPS 6.1 Conclusions The CircThread Platform offers a comprehensive product information management solution for managing complex product lifecycle data to enhance a circular economy, providing collaborative, secure, interoperable IT ecosystems. By addressing the needs of diverse stakeholders across the product life cycle, the platform enables efficient registration, management, and integration of product information. Platform development works carried out for version 2 of the CircThread Platform under task 5.4, of which the results are described in this deliverable. These works cover the IT components and six different core CircThread Platform services. The organisation and user registry to ensure role-based access control, fostering secure and compliant collaboration among stakeholders. The Product Model Registry and DPP Provider Registry which establish the foundation for integrating lifecycle data and achieving interoperability across different systems and providers. Advanced tools like Product Model Search and DPP and Metadata catalogue linkages empower users to access, link and utilize critical product information effectively, promoting traceability and transparency. A significant strength of the CircThread Platform is its ability to integrate with 3rd party services through standardised APIs. This integration allows external services, such as Sustainability Advisory and Legacy Product Data Identification Services, to connect seamlessly with the platform. By leveraging these external services, stakeholders gain access to advanced analytics and enhanced decision-making tools. The interoperability ensured by these integrations extend the ecosystem’s value and fosters collaboration between different sectors and service providers. Services integration has been carried out with the implementation of the Digital Product Passport service, the Metadata Catalogue Service, the Legacy Product Data Identification Service, and the CircThread Circular Sustainability Advisory Service. Further services integration is planned with other CircThread services beyond task 5.4 based on the respective services API documentations and the information exchange user journeys regarding the integration. 6.2 Next steps The CircThread Platform development will continue under the pilot implementations of WP7 up to February 2025, so as to provide for the release of v3 of the CircThread platform. This version includes further services integrations and feedback from the final pilot testing efforts of the 7 CircThread use cases, utilising the different connected CircThread services. The v3 will be publicly released once it is ready, governed by the CircThread Association that has been setup under WP8. The consortium will seek to develop further versions of the CircThread Platform beyond the CircThread platform governed under the CircThread Association, based on further grants and commercialisation of specific CircThread Platform services.