Systems and methods for generating chemical product passports

Abstract

The invention relates to the field of sustainability, in particular to the field of sustainable industrialization. The disclosure relates to methods, apparatuses, systems, and computer elements for generating or updating a chemical product passport associated with a chemical product. The disclosure further relates to a chemical product associated with a chemical product passport generated and / or updated as disclosed herein. The disclosure further relates to a chemical product passport generated and / or updated as disclosed herein. The disclosure further relates to a use of the chemical product passport generated and / or updated as disclosed herein to further process a chemical product associated with the chemical product passport.

Description

[0001] SYSTEMS AND METHODS FOR GENERATING CHEMICAL PRODUCT PASSPORTS

[0002] TECHNICAL FIELD

[0003] The invention relates to the field of sustainability, in particular to the field of sustainable industrialization. The disclosure relates to methods, apparatuses, systems, and computer elements for generating or updating a chemical product passport associated with a chemical product. The disclosure further relates to a chemical product associated with a chemical product passport generated and / or updated as disclosed herein. The disclosure further relates to a chemical product passport generated and / or updated as disclosed herein. The disclosure further relates to a use of the chemical product passport generated and / or updated as disclosed herein to further process a chemical product associated with the chemical product passport.

[0004] TECHNICAL BACKGROUND

[0005] In the supply and production of chemical products multiple regulatory requirements need to be met, which differ depending on the product. To fulfil such regulatory requirements, product passports may need to be generated for such chemical products. The product passports contain various data including data associated with input material(s) used to produce the product. Such data needs to be provided by input material producer(s) producing such input material(s) for generating and / or updating the product passports. The lack of standardized data models with respect to such data may hamper provision of accurate and reliable data required for generation and / or updating of such product passports.

[0006] SUMMARY OF THE INVENTION

[0007] In an aspect disclosed is a method for generating a chemical product passport associated with a chemical product, wherein the chemical product is produced from one or more input material(s) by a production chain, the method comprising:

[0008] • providing data associated with the chemical product including at least one digital chemical product identifier associated with the chemical product,

[0009] • gathering validated data associated with the production of the chemical product based on the at least one digital chemical product identifier, wherein the validated data is generated by gathering data associated with the production of the chemical product from decentral data providing node(s) associated with the data associated with the production by a decentral data consuming node based on the provided digital chemical product identifier(s) and validating at least a part of the gathered data using a rule-based engine including one or more rule(s) related to a data model associated with the chemical product passport, optionally wherein the one or more rule(s) are generated based on the data model associated with the chemical product passport,

[0010] • providing at least one decentral identifier associated with the validated data,

[0011] • generating the chemical product passport including the decentral identifier(s) and at least a part of the validated data and providing the generated chemical product passport for access. In a further aspect disclosed is an apparatus for generating a chemical product passport associated with a chemical product, wherein the chemical product is produced from one or more input material(s) by a production chain, the apparatus comprising:

[0012] • a data providing interface configured to provide data associated with the chemical product including at least one digital chemical product identifier associated with the chemical product,

[0013] • a data gathering unit configured to gather validated data associated with the production of the chemical product based on the at least one digital chemical product identifier, wherein the validate data is generated by gathering data associated with the production of the chemical product from decentral data providing node(s) associated with the data associated with the production by a decentral data consuming node based on the provided digital chemical product identifier(s) and validating at least a part of the gathered data using a rule-based engine including one or more rule(s) related to a data model associated with the chemical product passport, optionally wherein the one or more rule(s) are generated based on the data model associated with the chemical product passport,

[0014] • a decentral identifier provider configured to provide at least one decentral identifier associated with the validated data,

[0015] • a passport generator configured to generate the chemical product passport including the decentral identifier(s) and at least a part of the validated data and providing the generated chemical product passport for access.

[0016] In yet a further aspect disclosed is a method for updating a chemical product passport associated with a chemical product, wherein the chemical product is produced from one or more input material(s) by a production chain, the method comprising:

[0017] • providing data associated with the chemical product including at least one digital chemical product identifier associated with the chemical product,

[0018] • gathering validated data associated with the production of the chemical product based on the at least one digital chemical product identifier, wherein the validated data is generated by gathering data associated with the production of the chemical product from decentral data providing node(s) associated with the data associated with the production by a decentral data consuming node based on the provided digital chemical product identifier(s) and validating at least a part of the gathered data using a rule-based engine including one or more rule(s) related to a data model associated with the chemical product passport, optionally wherein the one or more rule(s) are generated based on the data model associated with the chemical product passport

[0019] • providing the chemical product passport including at least one decentral identifier and at least one of the digital chemical product identifiers based on the data associated with the chemical product,

[0020] • updating the chemical product passport based on the validated data and providing the updated chemical product passport for access. In yet a further aspect disclosed is an apparatus for updating a chemical product passport associated with a chemical product, wherein the chemical product is produced from one or more input material(s) by a production chain, the apparatus comprising:

[0021] • a data providing interface configured to provide data associated with the chemical product including at least one digital chemical product identifier associated with the chemical product,

[0022] • a data gathering unit configured to gather validated data associated with the production of the chemical product based on the at least one digital chemical product identifier, wherein the validated data is generated by gathering data associated with the production of the chemical product from decentral data providing node(s) associated with the data associated with the production by a decentral data consuming node based on the provided digital chemical product identifier(s) and validating at least a part of the gathered data using a rule-based engine including one or more rule(s) related to a data model associated with the chemical product passport, optionally wherein the one or more rule(s) are generated based on the data model associated with the chemical product passport

[0023] • a passport provider configured to provide the chemical product passport including at least one decentral identifier and at least one of the digital chemical product identifiers based on the data associated with the chemical product,

[0024] • a passport updater configured to update the chemical product passport based on the validated data and providing the updated chemical product passport and optionally the data completeness metric for access.

[0025] In yet a further aspect disclosed is a chemical product associated with a chemical product passport as generated and / or updated by the methods disclosed herein or by the apparatuses disclosed herein.

[0026] In yet a further aspect disclosed is a use of a chemical product passport as generated and / or updated for a chemical product by the methods disclosed herein or by the apparatuses disclosed herein to further process the chemical product associated with the chemical product passport.

[0027] In yet another aspect disclosed is a computer element, in particular a computer program chemical product or a computer readable medium, with instructions, which when executed on one or more computing node(s) are configured to carry out the steps of any of the methods disclosed herein.

[0028] In yet another aspect the present disclosure relates to a computer element with instructions, which when executed on one or more computing node(s) is configured to carry out the steps of the method(s) of the present disclosure or configured to be carried out by the apparatus(es) of the present disclosure.

[0029] Any disclosure, embodiments and examples described herein relate to the methods, the apparatuses, systems, the uses and computer elements lined out above and below. Advantageously, the benefits provided by any of the embodiments and examples equally apply to all other embodiments and examples. Embodiments

[0030] In the following, embodiments of the present disclosure will be outlined by ways of embodiments and / or examples. It is to be understood that the present disclosure is not limited to said embodiments and / or examples.

[0031] To enable efficient further processing of chemical products, chemical product passports associated with such chemical products may be provided. Such chemical product passports may be generated and / or updated by gathering data associated with the production of the chemical product from multiple participants of the production chain associated with the production of the chemical product. However, the completeness and accuracy of such gathered data needs to be ensured since a low degree of completeness and accuracy negatively impacts the further processing of such chemical products based on incomplete and / or inaccurate data contained in chemical product passports generated from such gathered data and / or updated using such gathered data.

[0032] By generating and / or updating the chemical product passport based on data validated according one or more rule(s) related to a data model associated with the chemical product passport, it can be ensured that the data used to generate and / or update the chemical product passport includes data points defined according to the data model. This avoids incomplete, false and / or missing data present within the data associated with the production of the chemical product and hence missing data points present within the passport data of the chemical product passport. This way, a higher data quality of the passport data can be ensured, allowing to provide chemical product passports for access which have an improved reliability since the passport data is associated with a higher degree of completeness. In addition, validation of consumed data associated with the production of the chemical product allows to determine whether the consumed data contains data defined by the semantic model used to generate such chemical product passports, hence allowing to reduce the complexity associated with the generation of data associated with the production at the provider side by avoiding the use of complex data models during generation of such data. This may enable reliable sharing of such data irrespective of the existence of data models for such data since the data provided by the provider side is validated against the data model used to generate and / or update the chemical product passport.

[0033] By updating the chemical product passport, data accessible for updating and being provided after generation of the chemical product passport may be included in such chemical product passport. This allows to “fill up” the passport data after generation of the chemical product passport when data providers start to provide data for such chemical product passport. By generating and providing a data completeness metric indicating the degree of completeness of the passport data with respect to the data defined by the data model used for its generation, the quality of the updated passport data can be reliably judged by data consumers consuming the chemical product passport. In addition, the degree of updating and the progress of data provision can be made transparent, for example to the entity generating the chemical product passport. This allows the entity generating the chemical product passport to request provision of missing data to achieve a higher quality and reliability of the passport data.

[0034] By generating and providing a data completeness metric indicating the degree of completeness of the passport data with respect to the data defined by the data model used for its generation, a stream of chemical products associated with the chemical product passports to a downstream production using the chemical products to produce one or more further product(s) can be monitored and / or controlled based on the data completeness metric associated with the chemical product passports. The stream of chemical products may be controlled and / or monitored by validating the chemical product passports based on the associated data completeness metric. Validation may include comparing the data completeness metric associated with the chemical product passports with target data completeness metrics. Based on validated chemical product passports, the chemical products associated with the validated chemical product passports may be provided to the downstream production for producing the further product(s). Based on non-validation of the chemical product passports, the chemical products associated with the non-validated chemical product passports may be rejected, e.g. may not be provided to the downstream production. This way, a more efficient and reliable production of the further products based on data included in the chemical product passports can be ensured.

[0035] Various units, entities, nodes or other computing components may be described as “configured to” perform a task or tasks. Configured to shall recite structure meaning “having circuitry that” performs the task or tasks on operation. The units, circuits, entities, nodes or other computing components can be configured to perform the task even when the unit / circuit / component is not operating. The units, circuits, entities, nodes or other computing components that form the structure corresponding to “configured to” may include hardware circuits and / or memory storing program instructions executable to implement the operation. The units, circuits, entities, nodes or other computing components may be described as performing a task or tasks, for convenience in the description. Such descriptions shall be interpreted as including the phrase “configured to.”

[0036] In general, the methods, apparatuses, systems, computer elements, nodes or other computing components described herein may include memory, software components and hardware components. The memory can include volatile memory such as static or dynamic random-access memory and / or nonvolatile memory such as optical or magnetic disk storage, flash memory, programmable read-only memories, etc. The hardware components may include any combination of combinatoric logic circuitry, clocked storage devices such as flops, registers, latches, etc., finite state machines, memory such as static random-access memory or embedded dynamic random-access memory, custom designed circuitry, programmable logic arrays, etc.

[0037] The chemical product passport may be a data set having a defined semantic structure. The semantic structure may be defined by a data model associated with the chemical product passport. The data model may define one or more data points included in the chemical product passport. The data model may define such data points as mandatory data points or as optional data points. The data model may define a semantic description of the respective chemical product passport. The semantic description may include the structure of at least a portion of the chemical product passport, and / or properties of the chemical product passport. The properties of the chemical product passport may include data types. The properties of the chemical product passport may include possible or allowable values and / or value ranges. The properties of the chemical product passport may be a physical unit of parameter(s) described by values contained in the chemical product passport. The properties of the chemical product passport set may include one or more attribute(s). The data model may define data points, such as data types and values and / or value ranges, to be included in the chemical product passport.

[0038] The chemical product passport may include at least one decentral identifier and passport data. The decentral identifier may comprise any unique identifier uniquely associated with the chemical product. The decentral identifier may include one or more Universally Unique Identifier(s) (UUID) or a Digital Identifier(s) (DID). The decentral identifier may be issued by a central or decentral identity issuer. The decentral identifier may include authentication information. Via the decentral identifier and its unique association with the chemical product access to passport data may be controlled by the data owner of the passport data, such as the chemical product producer, the entity generating the chemical product passport including the passport data or the entity on behalf of which the chemical product passport including the passport data is generated. This contrasts with central authority schemes, where identifiers are provided by such central authority and access to data is controlled by such central authority. Decentral in this context refers to the usage of the decentral identifier(s) as controlled by the data owner of the passport data.

[0039] The passport data may include data points defined by the data model used to generate the respective chemical product passport. The passport data may include data associated with the production of the chemical product and / or chemical product identifier(s) associated with the chemical product. This way, the chemical product passport may be uniquely linked to the chemical product. The passport data may include at least one measured chemical and / or physical property of the input material(s) used to produce the chemical product and / or the chemical product, and / or at least one chemical and / or physical property determined from data collected during production and / or use of the input material(s) and / or the chemical product. Examples of chemical properties include heat of combustion, enthalpy of formation, toxicity, chemical stability in a given environment, flammability, oxidation state(s), ability to corrode, combustibility, acidity and basicity, chemical composition, recyclate content, bio-based content, renewable content, carbon footprint, biodegradability, and / or pH value. Examples of physical properties include absorption, brittleness, boiling point, capacitance, color, concentration, density, ductility, distribution, efficacy, elasticity, electric charge, electrical conductivity, electrical impedance, electric potential, flow rate, fluidity, hardness, heat capacity, inductance, intrinsic impedance, luminescence, luminescence, luster, mass, melting point, opacity, permeability, permittivity, plasticity, pressure, radiance, resistivity, reflectivity, refractive index, solubility, specific heat, strength, stiffness, temperature, tension, thermal conductivity, thermal resistance, viscosity, volume and / orwave impedance.

[0040] The chemical product passport may include one or more authentication mechanisms associated with the decentral identifier(s) and the passport data. The chemical product passport may relate to one or more authorization mechanisms associated with the decentral identifier(s) and the passport data. The one or more authorization mechanisms may include authorization rules determining if access to the at least a part of the passport data is granted. The chemical product passport and / or the decentral identifier(s) may be associated with one or more digital representations of the passport data. The digital representations may be regarded as access element(s) providing access to the chemical product passport or parts thereof. The digital representation may include decentral identifier(s) and access data. The decentral identifier(s) included in the digital representation may correspond to or be associated with the decentral identifier(s) included in the chemical product passport. The access data may include a locator or pointer, such as am url or uri, to a dedicated storage, such as a dedicated storage address, associated with the data owner of the chemical product passport. The pointer or locator may point directly to the dedicated storage storing the chemical product passport. The pointer or locator may point to a data providing network node associated with the dedicated storage storing the chemical product passport. The access element may include one or more authentication mechanisms associated with the decentral identifier(s) and the access data. The access element may be associated with one or more authentication mechanisms associated with the decentral identifier(s) and the access data. The access element may be provided to a decentral registry storing access elements. The decentral registry may be associated with a data providing network node. This may allow to control access to such registry and access to access element(s) stored in such registry via the data providing network node. The decentral registry may be associated with a participant of the chemical product ecosystem. The decentral registry may be associated with the data owner of the chemical chemical product passport. The decentral registry may be part of the decentral network but may not be associated with a particular participant of the production chain, e.g. may be regarded as infrastructure node of the decentral network.

[0041] Updating the chemical product passport may include modifying the passport data included in such chemical product passport. The passport data may be modified by adding data point(s), deleting data point(s) and / or modifying data point(s) present within the passport data. The passport data may be modified by adding, deleting and / or modifying value(s) and / or value range(s).

[0042] The data model associated with the chemical product passport may be a data model used to generate and / or update the chemical product passport. The data model may be associated with a chemical product type identifier. The chemical product type identifier may be associated with a chemical product type the chemical product is associated with. Based on the chemical product type identifier the chemical product is associated with, such data model as well as data related to such data model may be gathered, for example from database(s) storing such data. A mapping table may be used to determine the chemical product type identifier of the chemical product type the chemical product is associated with. The mapping table may include chemical product identifier(s) interrelated with a respective chemical product type identifier of the chemical product type the chemical product is associate with. The chemical product type identifier may be determined based on data included in the chemical product identifier(s). For instance, the chemical product identifier(s) may include a chemical product type or a chemical product name indicating the chemical product type.

[0043] The production chain used to produce the chemical product may include one or more production step(s). At least some production step(s) of the production chain may be performed by different participants of a chemical product ecosystem. The chemical product ecosystem may be associated with the production, use and / or recycling of the chemical product. One or more input material(s) may be used to produce one or more intermediate chemical product(s) or the chemical product in a production step. The input material(s) used within a production step may correspond to intermediate chemical product(s) produced by an upstream participant of the participant performing said production step.

[0044] Input material may refer to any good which is bought from suppliers and brought to a production plant of a participant of the production chain. The input material may include starting material used in the production process of the production plant to produce the chemical product. The input material may include starting material used in the production chain to produce the chemical product. An input material can be used in any production step of the production chain used to produce the chemical product. This means, the chemical product of the one production step can be used as input material of the subsequent production step. Input material may include recycled material. The input material may comprise or be any input material entering a production associated with a production step of the production chain. The input material may comprise or be any input material provided at any entry point of the production associated with a production step of the production chain. The input material may include virgin input material. The input material may include recycled material. The input material may include virgin material and / or recycled material.

[0045] Chemical product may include any chemical product produced from one or more input materials. The chemical product may be produced via one or more production steps. The production steps may involve chemical reactions and / or physical processes and / or assembly processes. The input material may be used in one or more of such production step(s). The chemical product may comprise or be any chemical product produced by a production and provided at any exit point of the production. The chemical product may be used as input material to produce one or more further chemical product(s), such as end products. The chemical product(s) may be produced by one or more downstream participants which may use material(s) produced by one or more upstream participants as input material(s). The chemical product may include inorganic chemical products and organic chemical products. Inorganic chemical products may be devoid of carbon atoms and / or carbon-hydrogen bond(s) while organic chemical products may include at least one carbon atom and / or at least one carbon-hydrogen bond. The chemical product may be a naturally occurring chemical product, i.e. any unprocessed chemical substance that is found in nature, such as chemicals from plants, micro-organisms, animals, the earth and the sea or any chemical substance that is found in nature and extracted using a process that does not change its chemical composition. The chemical product may be produced via one or more process steps. The process steps may involve chemical reactions and / or physical processes. The physical process(es) may involve the use of chemical production inputs, such as chemical materials. Physical process(es) may include mixing, dispersing, extrusion, molding, casting, weaving, knitting, coating and / or filling.

[0046] Inorganic chemical products may include aluminium, iron, steel, copper, zinc, lead, nickel, titanium, magnesium, chromium, tin, manganese and / or cobalt. Organic chemical products may include detergents, cosmetic products, paints, lubricants, paper, pulp paper, paper boards, polymer products, curable composition(s), machine fluid(s), chemical product(s) for activation of metal surfaces, corrosion protection product(s), cleaning agent(s), cutting fluid(s), release agent(s), coagulating agent(s), chemical product(s) comprising a structured coating layer, olefin composition(s), formulation additive(s), care composition ingredient(s), additive(s) for industrial composition(s), plastic additive(s), aroma chemical(s), pharmaceutical active ingredient(s), pharmaceutical excipient(s), food supplement(s), unsaturated chemical compound(s), chemical compound(s) comprising at least one oxirane(s), aliphatic or cycloaliphatic chloride(s), organic phosphine(s), organic phosphate(s), sulfonic acid(s), nitrogen containing chemical compound(s), cosmetic ingredient(s), compositions including alkanes, alkenes and alkynes, aromatic compounds, alcohols, aldeyhdes, ketons, carboxylic acids, esters, ethers, amines, amides, nitriles and / or halides any combinations thereof or any single compound / composition thereof. Polymer products may include chemical products including or consisting of at least one polymer, such as synthetic textiles, footwear, mattresses, absorbent hygiene products, toys, fishing nets, fishing gear, polymer composition(s) and / or aqueous polymer composition(s). The polymer may be selected from polyolefins, polyvinyls, polystyrenes, polyesters, polyethers, polyurethanes, poly(meth)acrylates, polyamides, polycarbonates, polyacetals, fluoropolymers, epoxides, silicons, polyimides, polylactic acid, cellulose, lignin, copolymers of such polymers and / or blends of such polymers.

[0047] The chemical product may be associated with a chemical product identifier(s). The chemical product identifier(s) may be digital or virtual chemical product identifier(s). The chemical product identifier may uniquely identify the chemical product within the entity producing the chemical product. The chemical product identifier may uniquely identify the chemical product within the decentral network. The chemical product identifier may be associated with an identifier element physically connected to the chemical product. The identifier element may encode the digital chemical product identifier. The chemical product identifier may include a chemical product name, a chemical product number, a LOT number, a batch number, a serial number, an identification number or the like.

[0048] The input material and the chemical product may be part of a chemical product ecosystem. The chemical product ecosystem may include chemical products. The chemical product ecosystem may include production chains to produce a chemical product. The chemical product may be a chemical product, an intermediate chemical product, a component, a component assembly, an end-chemical product or a recycled material. The chemical product ecosystem may include processing chains to process used chemical products resulting from the use of produced chemical products. Processing chains may include recycling chains to recycle at least part of the used chemical product (e.g. end-of-life chemical product) or a component thereof. Processing chains may include re-use chains to re-use the used chemical product. The chemical product ecosystem may include various participants, such as raw input material producers, chemical intermediate chemical product producers, chemical product producers, chemical product users (e.g. component producers and / or component assembly producers), end-chemical product producers, end-chemical product users, EOL chemical product collectors and recyclers. The chemical product ecosystem may allow the use of recycled materials resulting from recycling of end-of-life end chemical products to produce new chemical products, such as chemical intermediate chemical products and / or chemical products. The chemical product ecosystem may be associated with the production and / or re-use and / or recycling of physical chemical products.

[0049] The participants of the chemical product ecosystem may be connected via a decentral network. The decentral network may include one or more decentral network node(s) configured to perform data transactions. At least a part of the decentral network node(s) may be associated with participant(s) of the chemical product ecosystem. The data transactions may be based on a transaction protocol including authentication and / or authorization mechanism(s). Based on the authentication and / or authorization mechanism(s) a peer-to-peer network between decentral network node(s) of the decentral network may be established. The one or more authentication mechanism(s) may be associated with or linked to decentral identifier(s), such as decentral identifier(s) included in the chemical product passports and / or decentral identifier(s) included in digital representations associated with such chemical product passports. The one or more authentication mechanism(s) associated with decentral identifier(s) may be provided to decentral network node(s). The one or more authentication mechanism(s) associated with decentral identifier(s) may be accessible by decentral network node(s). The decentral configuration allows for more efficient use of computing resources and strengthens control by each data owner of the data associated with the respective decentral identifier.

[0050] The decentral data providing network node may comprise computer-executable instructions for providing and / or processing data within a decentral network, such as data associated with the production of the chemical product, by a decentral data consuming network node. The decentral data providing network node may be associated with or connected to one or more dedicated data storage(s) storing the data associated with the production of the chemical product. The decentral data providing network node may be directly or indirectly connected to the data storage(s) storing the data associated with the production of the chemical product. Hence, the decentral data providing network node may be associated with the data associated with the production of the chemical product. The dedicated data storage(s) may be under control of the data owner of the data associated with the production of the chemical product. The data owner may be an entity having access to the data associated with the production of the chemical product and controlling access by data consuming services of the decentral network to the data associated with the production of the chemical product. The data owner may be the input material producer or the chemical product producer. Via the decentral identifier and its unique association with the data owner and data associated with the production of the chemical product access to the data associated with the production of the chemical product may be controlled by the data owner. The data associated with the production of the chemical product may be accessible for the data owner. The data owner may hence directly or indirectly own the data associated with the production of the chemical product. The data associated with the production of the chemical product may be stored in a database of or associated with the data owner. The data associated with the production of the chemical product may be stored in a database accessible by the data owner. The data owner may control access to the data associated with the production of the chemical product via the data providing service of the data owner. The data associated with the production of the chemical product may be associated with the data owner. The data owner may be the owner of the data associated with the production of the chemical product.

[0051] The decentral data consuming network node may comprise computer-executable instructions for accessing and / or processing data within a decentral network, such as data associated with the production of the chemical product, provided by a decentral data providing network node. The decentral data consuming network node may be controlled or owned by or associated with a consumer of the data associated with the production of the chemical product, such as an entity generating the chemical product passport. The data consumer may be any entity processing the data associated with the production of the chemical product, for example by generating and / or updating chemical product passports. The data consumer may be any entity operating a production configured to process the chemical product associated with the data associated with the production of the chemical product. Processing may include using the chemical product as input material to produce further chemical products. Processing may include performing one or more recycling step(s) on the chemical product or a component thereof. The data consumer may be a downstream participant of the chemical product producer in the chemical product ecosystem.

[0052] A rule-based engine may be used to validate at least part of the data associated with the production of the chemical product gathered via the decentral network. The rule-based engine may be a software or software component that applies one or more rules to at least part of the gathered data associated with the production of the chemical product. The rule-based engine used to validate at least part of the gathered data associated with the production of the chemical product may include one or more rule(s) related to a data model associated with the chemical product passport. The one or more rule(s) may be associated with or relate to one or more data point(s) defined by the data model. Hence, the one or more rule(s) may allow to determine whether the gathered data includes one or more data point(s) defined according to the data model. The one or more rule(s) may be associated with data point(s) defined as mandatory according to the data model. The one or more rule(s) may be generated based on the mandatory data points defined by the data model. This allows to validate whether data point(s) required by the data model is / are included in the gathered data, hence ensuring reliable generation of the data completeness metric based on such validated data. The rule-based engine may operate on individual data point level, combination of data points or the whole gathered data. The operation of the rule-based engine may be defined by the one or more rule(s). Rule(s) associated with individual data point(s) may include one or more rule(s) defining condition(s) for individual data points present with the gathered data. Use of such rule(s) allows to validate whether data point(s) required by the data model associated with the chemical product passport are contained in the gathered data. Rule(s) associated with multiple data points may include one or more rules defining required combination of data points. Use of such rule(s) allows to validate whether combination(s) of data point(s) required by the data model associated with the chemical product passport are contained within the gathered data.

[0053] In an embodiment the data associated with the chemical product further includes a chemical product type associated with the chemical product and optionally input material identifier(s) associated with at least a part of the input material(s). The chemical product type may define the category or classification the chemical product falls under based on the property / ies of the chemical product, the purpose of the chemical product and / or the usage of the chemical product. The chemical product type may allow to categorize or group defined physical entities of chemical products into chemical product types, hence allowing to reduce the dimensionality and avoiding multiplication of data for each individual chemical product.

[0054] In an embodiment, the data associated with the production of the chemical product includes input material data associated with input material(s) used to produce the chemical product and / or chemical product data associated with the chemical product. Input material data may be present in the form of input material data set(s) associated with respective input materials. Likewise, the chemical product data may be present in the form of a chemical product data set. The input material data may include at least one measured chemical and / or physical property of the respective input material and / or at least one chemical and / or physical property determined from data collected during production and / or use of the respective input material. The chemical product data may include at least one measured chemical and / or physical property of the chemical product and / or at least one chemical and / or physical property determined from data collected during production and / or use of the chemical product. Examples of chemical properties include heat of combustion, enthalpy of formation, toxicity, chemical stability in a given environment, flammability, oxidation state(s), ability to corrode, combustibility, acidity and basicity, chemical composition, recyclate content, bio-based content, renewable content, carbon footprint, biodegradability, and / or pH value. Examples of physical properties include absorption, brittleness, boiling point, capacitance, color, concentration, density, ductility, distribution, efficacy, elasticity, electric charge, electrical conductivity, electrical impedance, electric potential, flow rate, fluidity, hardness, heat capacity, inductance, intrinsic impedance, luminescence, luminescence, luster, mass, melting point, opacity, permeability, permittivity, plasticity, pressure, radiance, resistivity, reflectivity, refractive index, solubility, specific heat, strength, stiffness, temperature, tension, thermal conductivity, thermal resistance, viscosity, volume and / or wave impedance.

[0055] In an embodiment the decentral data providing node(s) are determined from data associated with data sources indicating data accessible for generating and / or updating the chemical product passports by determining data set identifier(s) associated with input material(s) used to produce the chemical product based on at least one of the chemical product identifier(s) using relationship representation(s) included in the data associated with the data sources. The data associated with data sources may include data set identifiers associated with data sets including data associated with the production of the chemical product and data sources data indicating the data sources associated with such data set identifiers. The data sets may include input material data associated with input material(s) used to produce the chemical product and / or chemical product data associated with the chemical product. The data associated with data sources may be stored in a storage associated with or included in a system performing the validation of the gathered data. The data sources associated with such data set identifier(s) may provide data set(s) associated with such data set identifier(s) upon request from a data consuming node.

[0056] Data source data may include endpoints associated with such data sources. Data source data may further include a decentral participant identifier related to the data source and / or a participant role associated with the participant of the chemical product ecosystem being associated with or controlling the data source. Data sources may include network node(s) configured to provide data, such as data accessible for generating and / or updating the chemical product passports, upon request of a further network node (e.g. a consumer node). The data sources may be associated with a dedicated storage storing the provided data. The data sources may be configured to exchange data based on a transaction protocol including authentication and / or authorization mechanism(s) as previously described. Based on the authentication and / or authorization mechanism(s) a peer-to-peer network between a data sources and a consumer node may be established. The data source(s) may be configured to provide data based on an identifier associated with such data (e.g. the data set identifier). The data source(s) may be decentral network providing node(s). The data source(s) may be associated with input material producer(s) producing the input material(s) and / or with the chemical product producer producing the chemical product.

[0057] The relationship representation(s) may specify relationship(s) between a given data set identifier (e.g. parent identifier) and further data set identifier(s) (e.g. child identifier(s)) associated with data set(s) of input material(s) used to produce the intermediate chemical product or chemical product the given data set identifier (e.g. parent identifier) is associated with. Such relationship representation(s) may allow to resolve the production chain and to determine the data set identifier(s) associated with input material(s) used to produce a given chemical product based on the data set identifier associated with such chemical product. Hence, the number of child identifier(s) associated with data being accessible for generating and / or updating the chemical product passport may be determined using such relationship representation(s) based on a given chemical product identifier, such as a data set identifier associated with a chemical product data set.

[0058] The data associated with data sources may not contain data set(s) associated with the data set identifier(s) included in such data associated with data sources. Hence the database storing such data may not be regarded as a central repository of data set(s). Instead, the control over access to the data set(s) is retained by the respective data owners of such data sets, while such database only allows to locate data set(s) and to request access to such data set(s) for generating and / or updating the chemical product passport.

[0059] In an embodiment validating the gathered data includes providing the gathered data to one or more input node(s) configured to gather the data and to provide the gathered data as data set(s) to one or more downstream node(s), wherein the one or more downstream node(s) include the rule-based engine configured to validate at least a part of the data included in the data set(s) provided by the one or more input node(s). The rule-based engine may include one more rule(s) associated with or related to data associated with the data model associated with the chemical product passport. The one or more downstream node(s) may further be configured to link the validated data to at least one of the chemical product identifiers, determine storage location(s) for the validated data and to provide the validated data linked to chemical product identifier(s) to the determined storage location(s). An input node may represent a computing node gathering input material data from one or more decentral data consuming node(s). The one or more input node(s) may be configured to generate data packages, such as messages or events, from the gathered data. The generated data packages may be sent downstream from the input node(s) to the one or more downstream node(s). The downstream node(s) may be configured to retrieve data packages provided by the input node(s). The input node(s) may be configured to provide data packages to a persistent or non-persistent log. The downstream node(s) may be configured to retrieve data packages provided to the persistent or non-persistent log. The downstream node(s) may be configured to receive data packages provided to the persistent or non-persistent log. The input node(s) may be associated with a decentral network. For instance, the input node(s) may be associated with a decentral data consuming network node being part of a decentral network. Downstream node may refer to a computing node consuming data from a computing node present upstream with respect to the flow of data. Consuming data may include receiving data or retrieving data packages from the input node(s) or the persistent or non-persistent log. For instance, data “flows” downstream from an input node to the downstream node. The downstream node may be regarded as an output node. A request for data may be sent upstream from the downstream node to the input node.

[0060] In an embodiment the rule-based engine operates on individual data points present within at least part of the gathered data, multiple data points present within at least part of the gathered data or the whole gathered data. The rule-based engine may be configured to validate data based on one or more rule(s) included in the rule-based engine. The rule-based engine may apply one or more rule(s) to individual data point(s), multiple data point(s) and / or the whole data set to generate validated data. If the rule-based engine determines that individual data point(s), multiple data point(s) and / or the whole data matches one or more condition(s) in the rule(s), such individual data point(s), multiple data point(s) or the whole data may be regarded as validated. The validated data may be associated with a classifier indicating successful validation of the respective data point, combination of data point(s) or the whole data. The classifier may indicate that the data passed the one or more applied rule(s). Validating the data on data point level may allow to determine the number of data point(s) defined by the data model associated with the chemical product passport which are included in the gathered data.

[0061] In an embodiment the one or more rule(s) are generated from a rule template including unstructured data associated with instructions related to validation operation(s). The validation operation(s) may relate to one or more data point(s) and / or data point combination(s) to be present within the gathered data. The rule template may be used to generate executable logic that may be executed by the rule-based engine. Use of a rule template may facilitate generation of one or more rule(s) since the instructions for generation of executable logic may be formulated in natural language. The rule template may be a predefined rule template. The rule template may be generated to match the data model associated with the chemical product.

[0062] In an embodiment the one or more rule(s) define data point(s) and / or combination(s) of data point(s) to be present within the gathered data. This may allow to determine the number of data point(s) defined by the data model which are included in the gathered data, hence allowing to determine the completeness of the gathered data by comparing the determined number of data points to a target number of data points defined by the data model. The one or more rule(s) may define data point(s) and / or combination(s) of data point(s) based on data defined by the data model. Hence the one or more rule(s) may be generated based on the data model associated with the chemical product passport.

[0063] In an embodiment the one or more rule(s) are associated with or derived from the data model associated with the chemical product passport, in particular wherein the one or more rule(s) are associated with data point(s) defined as mandatory by the data model.

[0064] In an embodiment validating the gathered data by the rule-based engine includes identifying one or more rule(s) applicable to the gathered data and providing the applicable rule(s) to the rule-based engine. The applicable rule(s) may be identified based on an identifier associated with each applicable rule matching or being related to at least one identifier included in the gathered data. The applicable rule(s) may be included in a rule template. Hence validating the gathered data may include identifying an applicable rule template. The applicable rule(s) and / or the applicable rule template may be stored on a database connected to the rule-based engine. The identifier associated with each applicable rule or rule template may correspond to a digital identifier included in the gathered data. The applicable rule(s) or rule template may be gathered based on mapping data include identifier(s) associated with rule(s) or rule template(s) and associated data set identifier(s) and optionally type identifier(s). In an embodiment the gathered data is validated responsive to fulfilment of one or more rule(s) applied to the gathered data by the rule-based engine. This may ensure that the gathered data is only validated if the rule(s) could be successfully applied to the gathered data by the rule-based engine, e.g. if application of the rule(s) did not result in an error, for example due to missing data, wrong data, incomplete data, etc.. This may allow to reliably determine the number of data point(s) being accessible for generating and / or updating the chemical product passport and to generate the data completeness metric indicating a degree of completeness of the validated data with respect to the data defined by the data model.

[0065] In one embodiment the decentral identifier(s) is / are provided in response to a request to provide the decentral identifier(s). The request may include data related to the validated data and / or an owner or chemical product identifier associated with the validated data owner or the chemical product, respectively. The request to provide the decentral identifier(s) may include data related to the validated data and an owner identifier associated with the data owner of the validated data or the chemical product. The owner / chemical product identifier may be a string identifier associated with a data owner name or the chemical product name. The owner or chemical product identifier may be provided by a physical identifier provider, such as a bar code or a tag like a RFID tag, or a QR code. Such communication can be completed via ad hoc WIFI, BLE beacon, and / or NFC. The communications between wallet apps may be performed via any available communication channel, including but not limited to, web servers, ad hoc WIFI, BLE beacon signal, NFC, a barcode or QR code scanning, etc.

[0066] Through the owner identifier the generated chemical product passport may be associated with the data owner of the passport data by including the owner identifier. The owner identifier may be used for data transaction, such as sharing or exchanging passport data. The owner identifier may be provided to a transaction manager. By providing the decentral identifier and the owner identifier of the data owner to a transaction manager or a data consuming service may simplify tracking of data transactions. Any transaction in the data ecosystem can e.g. be associated with the clear name of the data owner.

[0067] In one embodiment the decentral identifier(s) is / are provided by one central node or by one or more decentral node(s). The decentral identifier as generated by one central node or by one or more decentral nodes may be provided to a node generating the chemical product passport. The decentral identifier may be associated with authorization rule(s) regulating access to the passport data as described later on. This enables customized data sharing or exchange with respect to the chemical product and the chemical product ecosystem the chemical product is used within. In particular, the data providing service and / or the data consuming service may customize data sharing or exchange protocols based on the anchoring of the decentral identifier to the passport data.

[0068] The decentral identifier may be associated with a physical entity of the chemical product. The decentral identifier may be associated with the physical entity of the chemical product the chemical product passport is generated for. The decentral identifier may or may be assigned to a physical identifier connected to the chemical product. The connection of the physical identifier with the chemical product may be provided by means of physical connection to the physical chemical product or physical entity. For instance, the physical identifier may be connected with the physical entity of the chemical product. The physical identifier may have one-to-one correspondence to a virtual identity or to a physical identity by means of a physical connection to the physical entity. The physical identifier may be physically attached to the chemical product via an identifier element. Physical identifier or physical identifier element may refer to any virtual or physical arrangement that associates the decentral identifier with the chemical product. The physical identifier may be any identifier for the produced chemical product, such as a batch number or a part number. The physical identifier element may comprise a passive or active element, e.g. QR-code, RFID-tag, but is not limited thereto. The physical identifier element may be a physical identifier physically connected to the chemical product. The identifier element may include markers embedded in materials, a bar code, a QR-Code, a tag like a RFID tag or similar physical arrangement that allows to digitally identify the chemical product.

[0069] In an embodiment generating the chemical product passport includes providing a data model associated with the chemical product passport, applying the data model to the validated data to generate passport data and generating the chemical product passport including the decentral identifier(s) and the passport data. The generated chemical product passport may be stored on a dedicated storage associated with or under control by the data owner of the chemical product passport. The generated chemical product passport may be associated with a digital representation pointing to the storage location storing the chemical product passport. The digital representation may be stored in a decentral registry of a decentral network associated with or under control by the data owner of the chemical product passport. This enables further participants of decentral network authorized to query the decentral registry to gather the digital representation and to access the chemical product passport based on such digital representation.

[0070] In an embodiment the method further includes a step of generating access policy data associated with the chemical product passport and providing the access policy data, wherein the access policy data is generated by

[0071] • generating group access data associated with the digital twin data structure, the group access data identifying access control groups including data consumer identifier(s) associated with data consumers permitted to access at the chemical product passport,

[0072] • generating consumer access data associated with one or more data point(s) present within the chemical product passport based on the generated group access data, the consumer access data identifying the data consumer(s) permitted to access the one or more data point(s) and one or more actions allowed to be performed on the one or more data points(s) by data consumer(s) associated with the data consumer identifier(s),

[0073] • generating access policy data associated with the chemical product passport based on the generated group access data and the generated consumer access data, the access policy data identifying the group access data and the associated consumer access data. The access policy data may indicate the data consumer(s) permitted to access the chemical product passport and the action(s) such data consumer(s) are allowed to perform on data point(s) included in the chemical product passport, e.g. data point(s) included in the passport data.

[0074] The group access data may be generated based on the decentral identifier(s) included in the chemical product passport and associated attribute data related to data consumer(s). The data consume(s) may include a participants of the chemical product ecosystem. Data consumer(s) may be associated with respective decentral participant node(s) allowing peer-to-peer communications within the decentral network. Data consumer(s) may be associated with respective application(s) allowing access to the storage structure storing the chemical product passport. The attribute data may be associated with or includes the role of the data consumer(s). Roles may include a raw material supplier role, a chemical product producer role, a chemical product consumer role, an OEM role, an end-chemical product user role, a dismantler role, a recycler role, etc.. Roles may be associated with production step(s) and / or processing operations (such as re-use, refurbishment, recycling) performed by the data consumer within the chemical product ecosystem. The group access data may be generated by

[0075] • gathering data on data consumer(s),

[0076] • generating at least one access control group,

[0077] • assigning at least part of the data consumer identifier(s) included in the gathered data to at least one generated access control group,

[0078] • providing the decentral identifier(s) included in the chemical product passport,

[0079] • generating the access group data including the provided decentral identifier(s) and at least one group access policy defining generated access control group(s) for which access to the chemical product passport is permitted.

[0080] Generating the consumer access data includes generating access control list data including at least one access control list entry, the at least one access control list entry including the consumer identifier(s) associated with the data consumer(s) permitted to access one or more data point(s) present within the chemical product passport, the respective data point(s) to which access is permitted for said data consumer(s), and the one or more action(s) allowed to be performed on the data point(s) for which access is permitted. Action(s) allowed to be performed on the data point(s) may include actions allowed to be performed on data point(s) may include processing such data point(s). An access control list entry may be generated for at least part of the data points present within the chemical product passport.

[0081] The access policy data may include computer-executable instructions to allow access to the chemical product passport, deny access to the chemical product passport, to modify access to the chemical product passport or to perform one or more action(s) on the chemical product passport.

[0082] In an embodiment the chemical product passport is provided under control of the data owner of the chemical product passport. The data owner may include an entity generating and / or updating the chemical product passport. The data owner may include an entity on behalf of which the chemical product passport is generated and / or updated. The data owner may be the chemical product producer. The data owner may be the chemical product user, e.g. an entity using the chemical product to produce further chemical products. For example the data owner may be the end chemical product producer using the chemical product to produce the end chemical product. The chemical product passport may be stored in a data base of or associated with the data owner. The chemical product passport may be stored in a data base of or under control by the data owner. The chemical product passport may be stored in a data base accessible by the data owner. The chemical product passport may be associated with the data owner. The data owner may be the owner of the chemical product passport or the chemical product passport data owner. In this sense, the data owner is to be construed broadly as the entity having access to the chemical product passport controlling access by decentral data consuming network nodes of the decentral network to the chemical product passport or parts thereof. Access to the digital twin or parts thereof may hence be under control of the data owner. This allows to retain full control over the chemical product passport by the data owner but at the same time enabling sharing of the chemical product passport or parts thereof under controlled conditions, for example by using appropriate authorization and authentication mechanisms or schemes.

[0083] Providing the chemical product passport under control of the data owner may include gathering access policy data associated with the chemical product passport based on a request to access the chemical product passport from a data consumer and applying the access policy data to the chemical product passport based on the data included in the received request. The request may include a consumer identifier. The request may further include one or more actions to be performed on data point(s) included in the chemical product passport, such as read action(s).

[0084] The access policy data may be generated by

[0085] • generating group access data associated with the chemical product passport, the group access data identifying access control groups including data consumer identifier(s) associated with data consumer(s) permitted to access at the chemical product passport,

[0086] • generating consumer access data associated with one or more data point(s) present within the chemical product passport based on the generated group access data, the consumer access data identifying the data consumer(s) permitted to access the one or more data point(s) and one or more actions allowed to be performed on the one or more data point(s) by data consumer(s) associated with the data consumer identifier(s),

[0087] • generating access policy data associated with the chemical product passport based on the generated group access data and the generated consumer access data, the access policy data identifying the group access data and the associated consumer access data.

[0088] The access policy data may be generated by • generating group access data associated with the chemical product passport, the group access data identifying access control groups including data consumer identifier(s) associated with data consumer(s) permitted to access at the chemical product passport,

[0089] • generating consumer access data associated with the chemical product passport based on the generated group access data, the consumer access data identifying one or more actions allowed to be performed on the passport data by data consumer(s) associated with the data consumer identifier(s),

[0090] • generating access policy data associated with the chemical product passport based on the generated group access data and the generated consumer access data, the access policy data identifying the group access data and the associated consumer access data.

[0091] The group access data includes a gathering of one or more data consumer identifier(s) associated with the data consumer(s) permitted to access the chemical product passport.

[0092] Applying the access policy data to the chemical product passport may include

[0093] • validating whether the data consumer is permitted to access the chemical product passport,

[0094] • responsive to validating access to the chemical product passport for the data consumer validating whether the data consumer is permitted to perform the requested action(s) on the chemical product passport.

[0095] The access policy data and / or the group access data may be linked to the chemical product passport, for example via the decentral identifier(s) and / or the chemical product identifier. This way, the access policy data and / or the group access data may be obtained based on one of the decentral identifier(s) and / or the chemical product identifier.

[0096] Validating whether the data consumer is permitted to perform the requested action(s) on the chemical product passport may include

[0097] • obtaining access control list data associated with one or more data point(s) present within the chemical product passport,

[0098] • identifying one or more actions to be performed on the one or more data point(s) present within the chemical product passport based on data contained in the received request,

[0099] • determining whether the data consumer is permitted to perform the one or more actions requested to be performed on the one or more data point(s) by comparing access control list entries present within the access control list data with the data included in the received request, and, in response,

[0100] • performing the one or more actions requested to be performed on the one or more data point(s) or providing the chemical product passport according to the one or more requested actions to the data consumer. By filtering data consumer(s) requesting access to the chemical product passport based on a group- based policy for accessing the chemical product passport, the chemical product passport can be securely exchanged and shared under the sovereignty of the data owner of the chemical product passport and unauthorized access to the chemical product passport can be avoided. This allows for controlled access to the chemical product passport or parts thereof by participants of the chemical product ecosystem, such as upstream participants of the chemical product producer, the passport generator or the entity on behalf of which the passport is generated. Moreover, access to the chemical product passport or a part thereof by multiple data consumers can be controlled by the data owner using the group-based policy and the decentral identifier(s) included in the chemical product passport. Use of a group-based access in combination with fine-grained access controls on data point level allows to avoid the generation of multiple copies of the chemical product passport customized to the access rights associated with each data consumer permitted to access the chemical product passport. Hence, the amount of data associated with the chemical product passport may be reduced since access may be controlled on data point level of the chemical product passport, making generation of multiple copies of the chemical product passport redundant.

[0101] The access policy data may identify access control group(s) including data consumer identifier(s) associated with data consumer(s) permitted to access at the chemical product passport. Applying the access policy data may include

[0102] • determining consumer identifier(s) based on user data contained in the received request,

[0103] • determine whether the determined consumer identifier(s) are permitted to access the chemical product data based on group access data identifying access control groups including data consumer identifier(s) associated with data consumer(s) permitted to access at the chemical product passport,

[0104] • if the determined consumer identifier(s) are permitted to access the chemical product data, determine usage data associated with validated data used to generate the chemical product passport, apply the determined usage data based on the determined consumer identifier(s) to the chemical product passport and provide the chemical product passport according to the applied usage data.

[0105] In another example, applying the access policy data may include

[0106] • determining consumer identifier(s) based on user data contained in the received request,

[0107] • determine group access data associated with the chemical product passport and identifying consumer identifier(s) associated with data consumer(s) permitted to access at the chemical product passport,

[0108] • apply the determined group access data based on the determined consumer identifier(s) to the chemical product passport and provide the chemical product passport according to the applied group access data.

[0109] The consumer identifier(s) may be determined from data indicting relationships between consumer identifier(s) and user data. User data may include a username. Such relationships may indicate the user data associated with given consumer identifier(s). Such relationships may be stored within the data associated with data sources. This way, users can be related to data source data including consumer identifier(s).

[0110] Usage may include rule(s) and / or condition(s) associated with the usage of the input material data for passport generation and passport usage. Passport usage may include providing the generated chemical product passport to passport consumers. Usage rule(s) may include rule(s) restricting access to the input material data to defined data consumer(s). The rule(s) may restrict the access based on consumer identifier(s).

[0111] In an embodiment the method further includes a step of generating and providing a data completeness metric associated with the chemical product passport, wherein the data completeness metric indicates a degree of correlation between the validated data included in the chemical product passport and data related to a data model associated with the chemical product passport. A high degree of correlation may indicate a high amount of data being accessible for generating and / or updating the chemical product passport and hence a high degree of completeness of the passport data contained in the generated and / or updated chemical product passport while a low degree of correlation may indicate a low amount of data being accessible for generating and / or updating the chemical product passport and hence a low degree of completeness of the passport data. The data completeness metric may indicate a total degree of completeness (e.g. a fraction of the amount of data available for generating and / or updating the chemical product passport compared to the amount of data defined by the data model associated with such chemical product passport). The data completeness metric may indicate a degree of completeness per participant required to provide data according to the data model and optionally a total degree of completeness. Based on the data completeness metric, a stream of chemical products associated with the chemical product passports to a downstream production using the chemical products to produce one or more further product(s) can be monitored and / or controlled. This way, a more efficient and reliable production of the further products based on data included in the chemical product passports may be ensured.

[0112] The data completeness metric may be generated by comparing data points defined by the data model with data points included in the validated data. The data related to the data model may include participant role(s) of participants associated with the production of the chemical product and a number of data points to be provided by such participant role(s) according to the data model. The data related to the data model may further include a digital chemical product identifier, such as a chemical product type identifier. This way, the data related to the data model may be linked to a chemical product or a chemical product type. Participants associated with the production of the chemical product may include participants performing at least one production step of the production chain used to produce the chemical product. The number of data points to be provided by such participant role(s) according to the data model may be determined by assigning a participant role to at least a part of the data points defined by the data model and accumulating the data points per assigned participant role. The data points defined by the data model may be assigned to participant role(s) based on properties of the intermediate chemical product or chemical product produced by such participant role. For instance, data points defining the battery properties within the data model may be assigned to the participant role “battery producer”. Likewise, data points defining the properties of cathode active material contained within the electrode of the battery may be assigned to the participant role “cathode active material (CAM) producer”. The data related to the data model may be included in one or more validation rule(s).

[0113] The degree of correlation may be determined by a rule based-engine including one or more validation rules configured to validate a completeness of the data accessible for generating and / or updating the chemical product passport based on the data related to the data model associated with the chemical product passport. The rule-based engine may operate on individual data point(s) included in the validated data, combination of data point(s) included in the validated data or the whole validated data.

[0114] The degree of correlation may be determined by comparing the number of validated data points with a number of data points included in the data related to the data model associated with the chemical product passport. Comparing the number of validated data points with a number of data points included in the data related to the data model may include

[0115] • determining the participant role(s) associated with the validated data points based on data associated with data sources,

[0116] • mapping the determined participant role(s) and associated number of validated data point(s) to participant role(s) and associated number of data points included in the data related to the data model.

[0117] The participant role(s) associated with the validated data points may be determined using data set identifier(s) associated with the validated data points. For instance, data set identifier(s) associated with the validated data point(s) may be compared to data set identifiers included in the data associated with data sources. The validation allows to determine the amount of accessible data points that are matching data points defined in the data model. Determining the degree of correlation based on the number of validated data points allows a more accurate determination of the completeness of the data accessible for generating and / or updating the chemical product passport since the data points have been validated against the data model associated with the chemical product passport.

[0118] The data completeness metric may include the digital chemical product identifier(s) and a total degree of completeness of the validated data. The total degree of completeness may correspond to the fraction of validated data compared to the amount of data defined by the data model. The total degree of completeness may be given in percent based on the total amount of data defined by the data model. Hence, a degree of completeness of 100% indicates that the validated data includes all data defined by the data model while a degree of 0% indicates that no validated data is available or that the validated data does not include any data defined by the data model. The data completeness metric may include the digital chemical product identifier(s) and a degree of correlation between validated data points provided per participant and data points to be provided per participant according to the data model.

[0119] The data completeness metric may include the digital chemical product identifier(s), input material identifier(s) associated with input material(s) used to produce the chemical product, participant role(s) associated with the input material identifier(s) and / or the chemical product identifier(s), and the degree of completeness of the data being accessible for generating and / or updating the chemical product passport for at least a part of the input material identifier(s) and / or the digital chemical product identifier(s). The degree of completeness per digital chemical product identifier(s) may correspond to the total degree of completeness as previously described. The degree of completeness for a given input material identifier may correspond to the degree of completeness of the data set associated with such input material identifier. The degree of completeness of the data set may be determined based on the participant role defined for the data set (e.g. by comparing the participant role defined for the accessible data set with the participant role(s) defined by the data model). The degree of completeness of the data set may be determined based on the number of validated data points included in such data set (e.g. by comparing the number of validated data points for a participant role associated with such validated data points to the number of data points defined by the data mode for such participant role). The degree of completeness per input material identifier allows to identify participant role(s) associated with missing data, e.g. participant(s) of the production chain not yet having provided data for access. Based on such data, a request to provide missing data may be generated and provided. Since only participant role(s) are provided by the data completeness metric to ensure sufficient privacy with respect to the production chain participant(s), the request to provide missing data cannot be directly provided to the participant(s) not yet having provided data for access. Instead, the request may be provided to the participant(s) associated with upstream participants not yet having provided data for access. The participant(s) associated with the upstream participant(s) may be identified using the data completeness metric by determining the participant(s) providing data set(s) associated with child identifier(s) for which no data accessible for generating and / or updating of the chemical product passport has been provided. Since such participant has information on its upstream participant(s), such participant may forward the request to such upstream participant(s).

[0120] The data completeness metric may further include the number of validated data point(s) for at least a part of the input material identifier(s) and / or the digital chemical product identifier(s), the number of data points per input material identifier and digital chemical product identifier as defined by the data model and optionally the total degree of completeness of the validated data. This may allow to provide a more granular transparency on the validated amount of data.

[0121] By generating and providing a data completeness metric indicating the degree of completeness of the passport data with respect to the data defined by the data model used for its generation, a stream of chemical products associated with the chemical product passports to a downstream production using the chemical products to produce one or more further product(s) can be monitored and / or controlled based on the data completeness metric. This way, a more efficient production of the further products based on data included in the chemical product passports can be ensured.

[0122] By generating and providing a data completeness metric, the degree of completeness of validated data available for generation and / or updating of the chemical product passports can be made transparent to chemical product passport generators. This transparency allows to identify participants of the production chain of the chemical product not yet having generated and / or provided access to data to be included in the chemical product passports according to the data model associated with the chemical product passports. This way, participants can be requested to generate and / or provide access to such data to ensure a high degree of completeness of the generated and / or updated chemical product passports. This way, a more efficient and reliable production of further products based on data included in the chemical product passports can be ensured.

[0123] In an embodiment updating the chemical product passport includes generating a data set by applying a data model associated with the chemical product passport to the validated data and updating the chemical product passport with the generated data set.

[0124] BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0125] In the following, the present disclosure is further described with reference to the enclosed figures. The same reference numbers in the drawings and this disclosure are intended to refer to the same or like elements, components, and / or parts. The description of drawings is provided for illustrative purposes and shall not be considered limiting. The embodiments and examples are illustrative embodiments and examples to further line out the concepts lined out herein. The figures include schematic illustrations and shall not be considered limiting. Other embodiments and examples that fall under the concepts lined out herein are possible and may not be explicitly described herein.

[0126] FIG. 1 illustrates an example of a participant network of a product ecosystem including a material loop and being associated with a decentral peer-to-peer network for exchange of data associated with raw materials, chemical product(s), discrete product(s), end product(s) and recycled material(s).

[0127] FIG. 2 illustrate a schematic diagram of a production process of a chemical product.

[0128] FIG. 3 illustrates an example architecture of a system configured to validate completeness of data accessible for generating and / or updating a product passport associated with a product. FIG. 4A illustrates an example block diagram of an asset generation system configured to generate data associated with the production of a product and to provide the generated data for access within a decentral network.

[0129] FIG. 4B illustrates a diagram showing an example of a system configured to gather output product data and to transform at least part of the gathered output product data using a rule-based engine.

[0130] FIG. 5 illustrates an example of a system and associated methods for generating data associated with the production of a product and to provide the generated data for access within a decentral network.

[0131] FIG. 6 illustrates a flow chart of an example method for generating output product data set(s) associated with produced output product(s).

[0132] FIG. 7 illustrates an embodiment of the method illustrated in FIG. 6 in accordance with one embodiment.

[0133] FIG. 8 illustrates a sequence diagram of an example method for generating output product data set(s) associated with produced output product(s).

[0134] FIG. 9 illustrates a decentral system for accessing data associated with produced output product(s).

[0135] FIG. 10 illustrates an example of a product passport service configured to generate and / or update a product passport associated with a product.

[0136] FIG. 11A illustrates an example of a data structure stored in a database of the product passport service illustrated in FIG. 10.

[0137] FIG. 11 B illustrates examples of relationship representations stored in the database of the product passport service illustrated in FIG. 10.

[0138] FIG. 11 C illustrates an example of a user interface for providing asset data and associated data source to the product passport service illustrated in FIG. 10 for storage.

[0139] FIG. 12 illustrates a system for generating and / or updating a product passport associated with a product.

[0140] FIG. 13A illustrates a block diagram of an example system for validating data associated with the production of a product. FIG. 13B illustrates a diagram showing an example of validating data associated with the production of a product using a rule-based engine included in the data validation unit described in the context of FIG. 13A.

[0141] FIG. 14 illustrates an example of a method for generating a product passport associated with a product.

[0142] FIG. 15 illustrates a flow chart of an example method for validating data associated with the production of the product.

[0143] FIG. 16 illustrates an embodiment of the method illustrated in FIG. 15.

[0144] FIG. 17 illustrates a sequence diagram of an example method for validating data associated with the production of the product.

[0145] FIG. 18 illustrates an example of a method for updating a product passport associated with a product.

[0146] FIG. 19 illustrates an example of a data quality analyzer illustrated in FIG. 10.

[0147] FIG. 20 illustrates an example of a metrics generator illustrated in FIG. 19.

[0148] FIG. 21 A illustrates a first example of a data completeness metric.

[0149] FIG. 21 B illustrates a further example of a data completeness metric.

[0150] FIG. 21 C illustrates yet a further example of a data completeness metric.

[0151] FIG. 22 illustrates a flow chart of an example of a method for validating a completeness of data available for generating and / or updating a product passport associated with a product.

[0152] DETAILED DESCRIPTION

[0153] FIG. 1 illustrates an example of a participant network of a product ecosystem associated with a decentral peer-to-peer network for exchange of data associated with raw materials, chemical product(s), discrete product(s), end product(s) and recycled material(s).

[0154] The participant network 130 of the product ecosystem associated may be associated with a decentral peer-to-peer network 134 for exchange of data associated with raw material(s), chemical product(s), discrete product(s), end product(s), recycled material(s) and / or their respective production. The participant network 130 may include one or more network participants, such as decentral participants 102 to 114. The network participants may be part of a product ecosystem including chemical products. The product ecosystem may include production chains to produce an end-product. The product ecosystem may include recycling chains to recycle at least part of an end-of-life product resulting from the use of the end product.

[0155] The product ecosystem may include a raw material producer 104, a chemical product producer 102, a chemical product user 106, an end-product producer 108, an end-product user 110 an EOL product collector 112 and a recycler 114. The product ecosystem illustrated in FIG. 1 is a mere example and may include more or less network participants. For example, the product ecosystem may include a chain of chemical product producers instead of only one chemical product producer 102. The decentral participant network 130 may include a chemical supply chain. The product ecosystem may allow to use of recycled materials resulting from recycling of end-of-life products to produce new products, such as chemical products. The product ecosystem may be associated with the production and / or recycling of physical products. The product may be a chemical product, an intermediate chemical product, a component, a component assembly, an end product, an end-of-life product or a recycled material.

[0156] The participant network 130 may be associated with the production of the product and / or the recycling of end-of-life products resulting from the use of the product by product users, such as end-product users 110. The network participant 102 to 114 may refer to a manufacturer of physical products, such as raw material producer 104, chemical product producer 102, chemical product user 106, end-product producer 108, a user of physical goods, such as end-product user 110, and / or a participant of a recycling chain associated with the physical product, such as EOL product collector 112 and recycler 114. The network participant may be associated with a participant node 116 to 128 and a decentral participant identifier related to an associated participant node(s) 116 to 128. The decentral participant identifier may uniquely identify the decentral network participant and its associated decentral participant node within the decentral peer-to-peer network 134.

[0157] Participant(s) of the participant network 130 may be associated with or involved in the generation of product passport(s) and / or the updating of existing product passports. Product passports may be generated and / or updated by an entity on behalf of participants of the product ecosystem, for example as described in the context of FIG. 24 to FIG. 27. Generation and / or updating of product passports may include validation of completeness of data to be used for the generation and / or updating of a product passport, for example as described in the context of FIG. 13 to FIG. 23. The generated product passports may be provided for access via the decentral network 130. For instance, recycler 114 may access such product passports to determine the composition of the end-of-life product, allowing adaption of the recycling process to the composition determined based on the accessed product passports. The generated or updated product passports may be provided under control of the data owner of the product passport. The data owner of the product passport may be the entity generating the product passport. The data owner of the product passport may be the entity on behalf of which the product passport is generated. The data owner of the product passport may be the product producer. The data owner of the product passport may be an end product producer using the product to produce the end-product. The participant(s) of the participant network 130 may be connected via material flows. The material flow may be a loop material flow 136. The loop material flow 136 may be a closed loop material flow. A closed loop material flow may refer to a material loop where recycled material is used to produce the same end products the recycled material is obtained from via recycling. The loop material flow 136 may be an open loop material flow. An open loop material flow may refer to a material loop where recycled material is used to produce different end products than the one the recycled material is obtained from. The material flow may be a linear material flow (e.g. not including recycling). The material flow 136, 138 may correspond to the flow of product from one participant of the decentral participant network 130 to the downstream participant of the decentral participant network 130. The material flow 136, 138 may refer to a continuous or a discontinuous flow of product. The flow of product may include any means of transportation suitable to transport the product from a participant to the downstream participant. The means of transportation may include pipes, containers, barrels, packages. The material flow 138 may be associated with raw materials used to produce a chemical product, such as virgin raw materials. The raw materials may be provided to chemical product producer 102 for producing chemical product(s) and / or intermediate chemical product(s). The loop material flow 136 may be associated with chemical product(s) and discrete product(s). The chemical product(s) may be provided from chemical product producer 102 to chemical product user 106 for producing discrete product(s). In contrast to chemical production, the discrete products being produced are distinct units sold as individual products. The loop material flow 136 may be associated with recycled material. The recycled material may be provided from recycler 114 to chemical product producer 102 for the production of chemical product(s) using the recycled material.

[0158] At least part of the participants of the decentral participant network 130 may be associated with decentral participant network nodes 116 to 128. The decentral participant nodes 116 to 128 may be under control of the respective decentral participant associated with the respective decentral participant node. The decentral participant nodes 116 to 128 may form decentral network 134. The decentral network 134 may be a peer-to-peer communication network. The decentral network 134 may be configured to perform data transactions 132. The data transactions 132 may be based on a transaction protocol including authentication and / or authorization mechanism(s). Based on the authentication and / or authorization mechanism(s) a peer-to-peer communication between decentral network nodes 116 to 128 associated with decentral network participants 102 to 114 may be established. The one or more authentication mechanism(s) may be associated with or linked to an identifier as described in the context of FIG. 12. The one or more authentication mechanism(s) associated with the identifier may be accessible by the decentral participant nodes as described in the context of FIG. 12. The decentral configuration allows for more efficient use of computing resources and strengthens control by the data owners of the decentral network by allowing for data sovereignty.

[0159] Data transactions between decentral network participant nodes may be based on an identifier associated with respective data to be accessed, for example as described in the context of FIG. 12. The identifier may be uniquely associated with the physical entity of the respective product and associated product data. The identifier may be a decentral identifier uniquely identifying the product within the decentral network. The identifier may be associated with further identifier(s), such as identifier(s) of production input(s) (e.g. input materials) used to produce the product (hereinafter denoted as child identifier(s)). This may allow to track the product input(s) used to produce a product, such as a chemical product, a component, a component assembly or end-product. The identifier may, for example, be included in an output product data set associated with the product, for example as described in the context of FIG. 9. The child identifier(s) associated with the identifier may be provided, for example, as described in the context of FIG. 13 to FIG. 14C.

[0160] The data flow 132 (e.g. transactions) between decentral network participant nodes may be directly or indirectly associated with the material flow 136, 138 between the decentral network participants. For instance, data flow 132 may be directly associated with material flow 136, 138 if data associated with an input material provided from the raw material producer 104 to the chemical product producer 102 is accessed by decentral participant node 118 associated with said chemical product producer 102. For instance, data flow 132 may be indirectly associated with material flow 136, 138 if data associated with a chemical product produced by chemical product producer 102 is accessed by decentral participant node 128 associated with recycler 114.

[0161] The decentral participant nodes 116 to 128 may be decentral computing nodes. The decentral computing node may be any device or system that includes at least one physical and tangible processor, and a physical and tangible memory capable of having thereon computer-executable instructions that are executed by a processor. The memory may take any form and depends on the nature and form of the computing node.

[0162] At least part of the decentral participant nodes 116 to 128 may be decentral data providing network nodes. At least part of the participant nodes 116 to 128 may be decentral data consuming network nodes. A participant of the decentral participant network 130 may be associated with a decentral data providing network node and / or a decentral data consuming network node depending on whether data is provided to downstream participants and / or consumed from upstream participants. For instance, end-product producer 108 may be associated with a decentral data providing network node configured to provide product data to a downstream participant (e.g. recycler 114). In addition to or alternatively, end-product producer 108 may be associated with a decentral data consuming network node configured to access data associated with a discrete product produced by an upstream participant (e.g. chemical product user 106) for example as described in the context of FIG. 12.

[0163] The decentral network 134 may include further decentral network nodes. The further decentral network nodes may be decentral infrastructure service nodes (not shown in FIG. 1). The decentral infrastructure service nodes may not be associated with a participant of the product ecosystem. The decentral infrastructure service nodes may provide services for decentral participant nodes 116 to 128, such as verifying the identity of the decentral network participant nodes 116 to 128 prior to performing a data exchange. The decentral network participant nodes 116 to 128 may be associated with or include certificate(s), such as X.509 certificate(s). The certificate(s) may be associated with decentral infrastructure service node(s) including e.g. a certificate issuing service and / or a dynamic provisioning service providing dynamic attribute tokens (e.g. OAuth Access Tokens). This way the decentral network participant nodes 116 to 124 possess a unique identifier embedded in a X.509 certificate that identifies the respective decentral network participant node 116 to 128. The information required to verify the certificate may be provided via an authentication registry associated with the certificate issuing service and / or a dynamic provisioning service. For instance, in the IDSA Reference Architecture Model, Version 3.0 of April 2019, a decentral data providing network node associated with a data owner, a Certification Authority (CA), a Dynamic Attribute Provisioning Service (DAPS) and a decentral data consuming network node associated with a data consumer are used to verify the identity prior to performing a data exchange (not shown, refer to FIG. 12).

[0164] FIG. 3 illustrates an example architecture of a system configured to generate and / or update a product passport associated with a product. The chemical product passport may be generated and / or updated as described in the context of FIG. 4A to FIG. 8.

[0165] The chemical product may be a liquid or solid. The chemical product may be a chemical intermediate chemical product or a chemical product. The chemical product may include inorganic chemical products and organic chemical products. Inorganic chemical products may be devoid of carbon atoms and / or carbon-hydrogen bond(s) while organic chemical products may include at least one carbon atom and / or at least one carbon-hydrogen bond. The chemical product may be a naturally occurring chemical product, i.e. any unprocessed chemical substance that is found in nature, such as chemicals from plants, microorganisms, animals, the earth and the sea or any chemical substance that is found in nature and extracted using a process that does not change its chemical composition. The chemical product may be produced via one or more process steps. The process steps may involve chemical reactions and / or physical processes. The physical process(es) may involve the use of chemical production inputs, such as chemical materials. Physical process(es) may include mixing, dispersing, extrusion, molding, casting, weaving, knitting, coating and / or filling.

[0166] The inorganic chemical product may include aluminium, iron, steel, copper, zinc, lead, nickel, titanium, magnesium, chromium, tin, manganese and / or cobalt. The iron may be produced from supply chain products including inorganic chemical materials, such as iron ore, coke and limestone. The steel may be produced from supply chain products including inorganic chemical materials, such as iron, oxygen and limestone. The aluminum may be produced from supply chain products including inorganic chemical materials, such as bauxite ore, sodium hydroxide and cryolite.

[0167] Organic chemical products may include detergents, cosmetic products, paints, lubricants, paper, pulp paper, paper boards, polymer products, curable composition(s), machine fluid(s), chemical product(s) for activation of metal surfaces, corrosion protection product(s), cleaning agent(s), cutting fluid(s), release agent(s), coagulating agent(s), chemical product(s) comprising a structured coating layer, olefin composition(s), formulation additive(s), care composition ingredient(s), additive(s) for industrial composition(s), plastic additive(s), aroma chemical(s), pharmaceutical active ingredient(s), pharmaceutical excipient(s), food supplement(s), unsaturated chemical compound(s), chemical compound(s) comprising at least one oxirane(s), aliphatic or cycloaliphatic chloride(s), organic phosphine(s), organic phosphate(s), sulfonic acid(s), nitrogen containing chemical compound(s), cosmetic ingredient(s), compositions including alkanes, alkenes and alkynes, aromatic compounds, alcohols, aldeyhdes, ketons, carboxylic acids, esters, ethers, amines, amides, nitriles and / or halides any combinations thereof or any single compound / composition thereof. Polymer products may include chemical products including or consisting of at least one polymer, such as synthetic textiles, footwear, mattresses, absorbent hygiene products, toys, fishing nets, fishing gear, polymer composition(s) and / or aqueous polymer composition(s). Polymer products may include chemical products including or consisting of at least one polymer, such as synthetic textiles, footwear, mattresses, absorbent hygiene products, toys, fishing nets, fishing gear, polymer composition(s) and / or aqueous polymer composition(s). The polymer may be selected from polyolefins, polyvinyls, polystyrenes, polyesters, polyethers, polyurethanes, poly(meth)acrylates, polyamides, polycarbonates, polyacetals, fluoropolymers, epoxides, silicons, polyimides, polylactic acid, cellulose, lignin, copolymers of such polymers and / or blends of such polymers.

[0168] Detergents may include chemical products used to remove dirt, grease and / or oil from surfaces, such as clothes, dishes or the like. Detergents may reduce or lower the surface tension of water to facilitate the removal of the dirt, grease and / or oil from the surfaces. Detergents may include surfactant(s), such as anionic surfactants, nonionic surfactants, cationic surfactants and / or amphoteric surfactants. Detergents may further include solvents, builders, such as phosphates, zeolites and / or citrates, enzymes, bleaching agents, optical brighteners, fragrances and / or preservatives. The detergents may be produced from supply chain products including organic chemical materials, such as surfactants, solvents, builders, enzymes, bleaching agents, optical brighteners, fragrances and / or preservatives.

[0169] Paints may include coating materials used to coat at least a part of the surface of an object. Paints may be used to protect the surface, to improve the appearance (e.g. color and / or texture) of the surface and / or to provide texture to the surface. Paints may include solvents, pigments and physically and / or chemically curable polymer(s). Paints may further include additives, such as thickeners, UV additives, flow additives or the like. Physically curable polymer(s) may form a coating film during release solvent from the paint by interlooping of polymer chains. Chemically curable polymer(s) may form a coating film by crosslinking reactions between complementary functional groups, e.g. chemical groups that can undergo chemical reactions. Crosslinking may be initiated by thermal energy and / or irradiation. Paints may be liquid or solid. The paint may be produced from supply chain products including organic chemical materials, such as solvents, pigments, physically and / or chemically curable polymer(s) and additives. The lubricant may be chemical products capable of reducing friction between surfaces (preferably metal surfaces), such as surfaces of mechanical devices or machines. A mechanical device may be a mechanism consisting of a device that works on mechanical principles, such as the machines previously described. The lubricant may be a lubricating liquid, lubricating oil or lubricating grease. The lubricant may be produced from supply chain products including organic chemical materials, such as base oils, additives and thickeners.

[0170] Textiles, footwear, mattresses, absorbent hygiene products, toys, fishing nets and fishing gear may include or consist of synthetic polymers, e.g. organic polymers produced by chemical reaction(s) and / or mixture of synthetic polymers and naturally occurring polymers. Textiles and footwear may include polyesters, nylon, acrylic polymers, polypropylene, polyurethane, polyethylene and / or polytetrafluoroethylene. Such polymer(s) may be extruded to produce yearn which may then be used in physical knitting and / or weaving processes to produce the textiles and / or parts of the footwear. Soles of footwear may include ethylene-vinyl acetate, polyurethane, natural or synthetic rubber, thermoplastic rubber, thermoplastic polyurethane and / or polyvinyl chloride. The soles may be produced from such polymers using injection molding, compression molding or foaming. The textiles and parts of the footwear may be produced from supply chain products including organic chemical materials, such as polymer(s) produced from chemical reaction(s). Mattresses may include one or more layers of polymer foams produced by polymerizing monomers in the presence of blowing agents. The layers of polymers may be encased in a fabric cover. The fabric cover may be produced from natural polymers, like cotton and / or synthetic polymers, like polyester. The mattresses may be produced from supply chain products including organic chemical materials, such as monomers, blowing agents, natural polymer(s) and / or polymer(s) produced from chemical reaction(s). Tires may be produced by assembling the inner liner made of rubber, the body piles made of fabric cord, such as nylon cord and / or polyester cord, coated with rubber, the rubber sidewalls, the bead rings, e.g. steel wires coated with rubber, the steel belts and the rubber tread and heating the assembly in a mold to vulcanize, e.g. crosslinking, the rubber. The tires may be produced from supply chain products including organic chemical materials, such as rubber and polymer cords, and inorganic chemical materials, such as steel. Absorbent hygiene products may include top sheets of nonwoven fabric, such as polypropylene or polyethylene, acquisition and distribution layers of nonwoven material layers, absorbent cores of cellulose fibers combined with superabsorbent polymers (SAP), back sheets made of polyethylene or bilaminate materials and adhesives. The absorbent hygiene products may be produced from supply chain products including polymers, such as polypropylene, polyethylene, cellulose, polyacrylates and adhesives. Toys may include plastic toys including one or more polymers. The toys may be produced from supply chain products including at least one polymer, such as acrylonitrile butadiene styrene, polyvinyl chloride, polyethylene, polypropylene, polyester, polyamide and / or thermoplastic elastomers. Fishing nets and fishing gear may include synthetic and / or naturally occurring polymers. Supply chain products used to produce the fishing nets and / or fishing gear may include polyethylene, polypropylene, polyester, polyamide, cotton and / or hemp. The chemical product may be present within a packaging unit. The chemical product may be produced from one or more input material(s) by a production step, for example as described in the context of FIG. 2. The chemical product may be produced from the input material(s) via a production chain including one or more chemical production step(s). At least some chemical production step(s) of the production chain may be performed by different participants of the chemical product ecosystem. For instance and with reference to FIG. 1 , the production chain may involve several production steps (e.g. production of raw metals, production of recycled material, production of chemical product). The production step(s) may be performed by different participants of the chemical product ecosystem, such as the participants shown in FIG. 1. The chemical product produced by one participant of the chemical product ecosystem may be used as input material by a downstream participant of the chemical product ecosystem. For instance and with reference to FIG. 1 , the chemical product produced by chemical product producer 102 may be used by the downstream participant, e.g. chemical product user 106, as input material to produce discrete products, such as components, parts or component assemblies.

[0171] The chemical product passport may be a data set having a defined semantic structure. The defined semantic structure may be obtained by applying a data model to data associated with the production of the chemical product. The data model may define a semantic description of the respective chemical product passport. The semantic description may include the structure of at least a portion of the chemical product passport, and / or properties of the chemical product passport. The properties of the chemical product passport may include data types. The properties of the chemical product passport may include possible or allowable values and / or value ranges. The properties of the chemical product passport may be a physical unit of parameter(s) described by values contained in the chemical product passport. The properties of the chemical product passport set may include one or more attribute(s). The data model may define data points, such as data types and values and / or value ranges, to be included in the chemical product passport.

[0172] The chemical product passport may include at least one decentral identifier (also denoted as decentral chemical product identifier) and passport data. The decentral identifier may comprise any unique identifier uniquely associated with the chemical product. The decentral identifier may include one or more Universally Unique Identifier(s) (UUID(s)) or a Digital Identifier(s) (DID(s)). The decentral identifier may be issued by a central or decentral identity issuer. The decentral identifier may include authentication information. Via the decentral identifier and its unique association with the chemical product access to passport data may be controlled by the data owner of the passport data, such as the chemical product producer, the entity generating the chemical product passport including the passport data or the entity on behalf of which the chemical product passport including the passport data is generated. This contrasts with central authority schemes, where identifiers are provided by such central authority and access to data is controlled by such central authority. Decentral in this context refers to the usage of the decentral identifier(s) as controlled by the data owner of the passport data. The passport data may include data points defined by the data model used to generate the respective chemical product passport. The passport data may include data associated with the production of the chemical product and chemical product identifier(s) associated with the chemical product. This way, the chemical product passport may be uniquely linked to the chemical product. Data associated with the production of the chemical product may include input material data associated with at least a part of the input material(s) used to produce the chemical product. Input material(s) used to produce the chemical product may include input material(s) used in one or more production step(s) of the production chain used to produce the chemical product. Data associated with the production of the chemical product may include chemical product data associated with the chemical product.

[0173] Input material data and / or chemical product data may include one or more chemical and / or physical property / ies associated with the input material or chemical product, respectively. The chemical and / or physical property / ies may include at least one measured chemical and / or physical property of the input material and / or at least one chemical and / or physical property determined from collected data associated with the chemical production and / or the use of the input material. The chemical and / or physical property / ies may include at least one measured chemical and / or physical property of the chemical product and / or at least one chemical and / or physical property determined from collected data associated with the chemical production and / or the use of the chemical product. The collected data may be used to determine the at least one physical and / or chemical property. For instance, the at least one physical and / or chemical property may be determined from sensor data obtained from sensor(s). The data may be collected with a suitable sensor configured to measure the chemical and / or physical property. The measured at least one physical and / or chemical property may be obtained by sensors configured to measure such property. The sensor may be included in a measuring device. The sensor may correspond to the measuring device.

[0174] The chemical product passport may include one or more authentication mechanisms associated with the decentral identifier(s) and the passport data. The chemical product passport may relate to one or more authorization mechanisms associated with the decentral identifier(s) and the passport data. The one or more authorization mechanisms may include authorization rules determining if access to the at least a part of the passport data is granted. The chemical product passport and / or the decentral identifier(s) may be associated with one or more digital representations of the passport data. The digital representations may be regarded as access element(s) providing access to the chemical product passport or parts thereof. The digital representation may include decentral identifier(s) and access data. The decentral identifier(s) included in the digital representation may correspond to or be associated with the decentral identifier(s) included in the chemical product passport. The access data may include a locator or pointer, such as am url or uri, to a dedicated storage, such as a dedicated storage address, associated with the data owner of the chemical product passport. The pointer or locator may point directly to the dedicated storage storing the chemical product passport. The pointer or locator may point to a data providing network node associated with the dedicated storage storing the chemical product passport. The access element may include one or more authentication mechanisms associated with the decentral ide ntifier(s) and the access data. The access element may be associated with one or more authentication mechanisms associated with the decentral identifier(s) and the access data. The access element may be provided to a decentral registry storing access elements. The decentral registry may be associated with a data providing network node. This may allow to control access to such registry and access to access element(s) stored in such registry via the data providing network node. The decentral registry may be associated with a participant of the chemical product ecosystem. The decentral registry may be associated with the data owner of the chemical product passport. The decentral registry may be part of the decentral network but may not be associated with a particular participant of the chemical production chain, e.g. may be regarded as infrastructure node of the decentral network.

[0175] The architecture may connect participants of the product ecosystem via a decentral network 134 to a chemical product passport service 322. The participants of the product ecosystem may provide access to data for generating and / or updating product passports, for example as described in the context of FIG. 4A to FIG. 9. The data may be provided via one or more decentral participant nodes, such as nodes 116, 118 and 128. The data may be provided via an asset generation service, such as asset generation service 1 302 to asset generation service 3 306. The asset generation service may be configured to generate input material data or chemical product data and to provide such generated data for access via a decentral network 134 under control of the data owner of the input material data or chemical product data, such as the input material producer or the chemical product producer, respectively. The input material data or chemical product data may be generated by the asset generation service 1 302, the asset generation service 2 304 and / or the asset generation service 3 306 from data stored in databases associated with the respective participant, such as databases 308 to 320. The databases may store respective input material data or chemical product data and may be accessible by respective data providing nodes, such as nodes 116, 118 and 128. Access to the database may be controlled by the data owner of the data stored in such data bases, for example via respective data providing nodes 116, 118 and 128. The participants may use the asset generation service to provide input material data or chemical product data. Alternatively, participants may generate input material data or chemical product data without the use of such asset generation service.

[0176] The chemical product passport service 322 may be configured to store data associated with data sources providing data accessible for generating and / or the updating chemical product passports. Such data associated with data sources may relate to or be associated with provider nodes 116, 118 and 128 providing data generating and / or updating chemical product passports associated with products, for example as described in the context of FIG. 9. The data associated with data sources may include endpoints of such data sources, such as endpoints of provider nodes 116, 118 and 128, decentral participant identifier(s) related to the data sources, participant role(s) related to the data sources and identifiers of input material data or chemical product data provided by such data sources, for example as illustrated in FIG. 11 A. Participant role(s) may indicate the role of a respective participant within the product ecosystem. The data associated with data sources may hence indicate data accessible for generating and / or updating product passports. The decentral participant identifier(s) may uniquely identify the respective participant within the decentral network, such as decentral network 134. The decentral participant identifier may include an identifier as described in the context of FIG. 9. The decentral participant identifier may be associated with a verifiable credential as described in the context of FIG. 9. The verifiable credential may include the decentral participant identifier. The verifiable credential may further include data indicating the role of the participant within the product ecosystem.

[0177] The identifiers of the input material data and / or the chemical product data may be associated with respective child identifier(s) indicating input materials used to produce a given intermediate chemical product or the chemical product, for example as illustrated in FIG. 11 B. Linking of identifiers allows to determine input materials used to produce a given chemical product based on the product identifier associated with the chemical product, for example as illustrated in FIG. 11 B. This way, it can be determined which participants have not provided data required for the chemical product passport according to data related to the data model associated with the respective chemical product passport.

[0178] The data associated with data sources may be provided by the participants of the decentral network, such as participants illustrated in FIG. 1. Data associated with data sources may be provided by participants as described in the context of FIG. 10 to FIG. 11 C.

[0179] The product passport service 322 may be configured to validate input material data or chemical product data gathered from data providing nodes according to the data associated with the data sources, for example as described in the context of FIG. 10 and FIG. 13A to FIG. 17. Validation ensures that data defined by the data model associated with such chemical product passport is included in the gathered data, hence allowing to reduce the complexity associated with the data set generation at the provider side by avoiding the use of complex data models during generation of such data set(s). This may enable reliable sharing of such data irrespective of the existence of data models for such intermediate chemical products since the rule(s) required to transform the gathered data may be readily derived from the data model associated with the chemical product passport.

[0180] The chemical product passport service 322 may be configured to generate data completeness metrics based on the data associated with the data sources or the validated data (e.g. the validated input material data and the validated chemical product data), for example as described in the context of FIG. 10, FIG. 12 and FIG. 19 to FIG. 22. The product passport service 322 may be configured to provide the generated data completeness metrics. The data completeness metrics may indicate the degree of correlation between the data stored in the data associated with the data sources and the data related to the data model associated with the respective chemical product passport. The data completeness metrics may indicate the degree of correlation between the validated data and the data related to the data model associated with the respective chemical product passport. A high degree of correlation may indicate a high amount of data being accessible for generating and / or updating the chemical product passport while a low degree of correlation may indicate a low amount of data accessible for generating and / or updating the chemical product passport. Based on the data completeness metric, a stream of chemical products associated with the chemical product passports to a downstream production using the chemical products to produce one or more further product(s) can be monitored and / or controlled. This way, a more efficient and reliable production of the further products based on data included in the chemical product passports can be ensured. In addition, the data completeness metric may be used by the entity generating the chemical product passport or by a third party on behalf of which the chemical product passport is generated to determine the amount of data accessible for generating and / or updating particular chemical product passports. This way, the data completeness metric may be used by such entity or third party to identify participants not yet having provided data defined by the data model associated with the chemical product passport and to request to provide such data for access. In addition, the data completeness metric may be used by such entity or third party to control generation of chemical product passports to ensure that the generated product passports contain a minimum amount of passport data. This allows to ensure a high degree of completeness of chemical product passports and hence a high reliability of the passport data included therein, resulting in more efficient further processing of chemical products associated with such chemical product passports based on data included in such chemical product passports.

[0181] The chemical product passport service 322 may be configured to generate chemical product passports and / or to update existing chemical product passports based on input material data and chemical product data gathered from data providing nodes for example as described in the context of FIG. 14 and FIG. 18. The generated and / or updated chemical product passports may be persisted in an archive to allow retrieval of such chemical product passports without having to regenerate such chemical product passports. Alternatively, the generated chemical product passports may be provided to a user requesting such chemical product passport without persisting the generated chemical product passport. Chemical product passport service 322 may be configured to generate one or more digital representations of the passport data and to provide such representations to a decentral registry for access by data consuming nodes under control of a decentral node associated with the entity operating the chemical product passport service 322 or on behalf of which the chemical product passport service 322 is operated.

[0182] By generating and / or updating the chemical product passport based on data validated according one or more rule(s) related to a data model associated with the chemical product passport, it can be ensured that the data used to generate and / or update the chemical product passport includes data points defined according to the data model. This avoids incomplete, false and / or missing data present within the data associated with the production of the chemical product and hence missing data points present within the passport data of the chemical product passport. This way, a higher data quality of the passport data can be ensured, allowing to provide chemical product passports for access which have an improved reliability since the passport data is associated with a higher degree of completeness. In addition, validation of consumed data associated with the production of the chemical product allows to determine whether the consumed data contains data defined by the semantic model used to generate such chemical product passports, hence allowing to reduce the complexity associated with the generation of data associated with the production at the provider side by avoiding the use of complex data models during generation of such data. This may enable reliable sharing of such data irrespective of the existence of data models for such data since the data provided by the provider side is validated against the data model used to generate and / or update the chemical product passport.

[0183] By updating the chemical product passport, data accessible for updating and being provided after generation of the chemical product passport may be included in such chemical product passport. This allows to “fill up” the passport data after generation of the chemical product passport when data providers start to provide data for such chemical product passport. By generating and providing a data completeness metric indicating the degree of completeness of the passport data with respect to the data defined by the data model used for its generation, a stream of chemical products associated with the chemical product passports to a downstream production using the chemical products to produce one or more further product(s) can be monitored and / or controlled based on the data completeness metric associated with the chemical product passports. The stream of products may be controlled and / or monitored by validating the chemical product passports based on the associated data completeness metric. Validation may include comparing the data completeness metric associated with the chemical product passports with target data completeness metrics. Based on validated chemical product passports, the chemical products associated with the validated chemical product passports may be provided to the downstream production for producing the further product(s). Based on non-validation of chemical digital product passports, the chemical products associated with the non-validated chemical product passports may be rejected, e.g. may not be provided to the downstream production. This way, a more efficient and reliable production of the further products based on data included in the chemical product passports can be ensured. In addition, the degree of updating and the progress of data provision can be made transparent, for example to the entity generating the chemical product passport. This allows the entity generating the chemical product passport to request provision of missing data to achieve a higher quality and reliability of the passport data.

[0184] FIG. 4A illustrates a block diagram of an example of an asset generation system configured to generate data associated with the production of a product and to provide the generated data for access within a decentral network. The chemical product may be a chemical product as described in the context of FIG. 3. The decentral network may be a decentral network as described in the context of FIG. 1. The asset generation system may be configured to perform the methods illustrated in FIG. 6 and FIG. 7. The data associated with the production of the chemical product may include input material data associated with input material(s) used to produce the chemical product and / or chemical product data associated with the chemical product. At least a part of the input material(s) may include output products described in the context of FIG. 4A. With reference to FIG. 5, the output product 506 may be produced using one or more input material(s) 502. The output product may comprise or be any product produced by the production 504 and provided at any exit point of the production 504. The output product may correspond to the product. The output product may correspond to an intermediate product used to produce the product. The input material may include starting material used in a production process performed within production 504 to produce the output product. An input material can be used in any process step of the production process. This means, the intermediate output product of the one production plant of production 504 can correspond to the input material of a subsequent production plant of production 504. Input material may include recycled material. The input material may comprise or be any input material entering the production 504. The input material may comprise or be any input material provided at any entry point of the production 504.

[0185] The output product may be produced via one or more process steps from the input material(s) 502 within production 504. The process steps may involve chemical reactions and / or physical processes and / or assembly processes involving the assembly of different discrete input material(s) and / or processes involving chemical input materials and discrete input materials, such as filling processes. The input material may be used in one or more of such production step(s). The input materials 502 may enter the system boundary 510 of the production 504 at the entry point, such as a production plant or a material storage associated with the production 504. The amount of input material entering the system boundary 510 of the production 504 may be measured, for example using sensor 508a. Sensors 508a may include sensors configured to measure an amount of input material, such as a weight and / or a volume, and / or sensor(s) configured to detect input material identifier(s) associated with the input material(s). The input material(s) may comprise a physical identifier element associated with the input material identifier(s). The identifier element may encode the input material identifier. The input material identifier may be a digital identifier. The data collected by the sensor(s) 508a may be stored in a database associated with the operation operating systems 516 of the production 504.

[0186] Chemical and / or physical properties of the input material may be measured, for example using sensor 808b, upon passing system boundary 510 of the production 504. The measured data may be used to determine at least one chemical and / or physical property of the respective input material. Examples of chemical properties include heat of combustion, enthalpy of formation, toxicity, chemical stability in a given environment, flammability, oxidation state(s), ability to corrode, combustibility, acidity and basicity, chemical composition, recyclate content used for producing or manufacturing the input material, biobased content used for producing or manufacturing the input material, renewable content used for producing or manufacturing the input material, biodegradability, and / or pH value. Examples of physical properties include absorption, brittleness, boiling point, capacitance, color, concentration, density, ductility, distribution, efficacy, elasticity, electric charge, electrical conductivity, electrical impedance, electric potential, flow rate, fluidity, hardness, heat capacity, inductance, intrinsic impedance, luminescence, luminescence, luster, mass, melting point, opacity, permeability, permittivity, plasticity, pressure, radiance, resistivity, reflectivity, refractive index, solubility, specific heat, strength, stiffness, temperature, tension, thermal conductivity, thermal resistance, viscosity, volume and / orwave impedance.

[0187] An operating system 516 of the production 504 may monitor and / or control the production 504 based on operating parameters of the different processes. The operating system 516 may receive production demand data associated with the production planning for the production 504. The production demand data may be produced from target production capacities for one or more output product(s) produced by the production 504. The production demand data may be produced from pre-defined production capacities or data-driven models that relate production capacities to market demand data or quantities consumed at the consumption location. The production demand data may include target capacities for output products produced by the production 504. The operating system 516 may further receive a bill of materials associated with output products to be produced. The bill of materials may include material data associated with the input materials used to produce the output product, process data associated with the production chain for producing the output product and / or output product data associated with the output product, such as a product specification data or data on the amount of output product to be produced.

[0188] Based on the received production demand data and the bill of materials, material demand data may be determined. The material demand data may include data on the amount of input material required to produce the target capacities of output product. The material demand data may include input material identifiers associated with input materials required to produce the output product and data on amounts of input material for respective input materials. The material demand data may include one or more material specifier(s) per input material identifier signifying the material specification. The material demand data may include data on the material amount per input material identifier signifying the amount of material to be supplied. The material demand data may specify the production chain(s) of the production 504. The material demand data may include a bill of materials for one or more production chain(s) of the production 504. The material demand data may include one or more recipe(s) specifying one or more material(s) for production process(es) of the production 504. The determined material demand data may be provided for access by a supplier system associated with a supplier outside the physical system boundary of the production 504. Material supply may be triggered by the supplier system accessing the material demand data.

[0189] The amount of output product(s) resulting from processes performed within production 504 may be measured using a sensor, such as sensor 508b. The measured data may be stored in one or more databases associated with operating system 516. Moreover processes performed within production 504 may be monitored using sensors, such as sensors 508b, and the generated monitoring data may be stored in one or more databases associated with operating system 516. The monitoring data may be interrelated with a digital output product identifier associated with the respective output product. Physical and / or chemical properties of produced output products may be measured by sensors, such as sensors 808a. Physical and / or chemical properties may include the properties previously described. The measured and / or determined data of the produced output products may be stored in one or more databases associated with operating system 516. The measured and / or determined data of the produced output products may be interrelated with a digital output product identifier associated with the respective output product. The digital output product identifier may be interrelated with a physical identifier element present on the output product or the packaging unit including the output product.

[0190] The produced output products 506 may be provided at one or more exit points of the production 504. The output product 506 may exit the system boundary 510 of the production 504.

[0191] The operating system 516 may include an asset generation service, such as asset generation service 2 304. The operating system 516 may be associated with such asset generation service (not shown). Asset generation service 2 304 may be configured to generate data set(s) (e.g. asset(s)) associated with output product(s) produced by production 504, for example as described in the context of FIG. 6 and FIG. 7.

[0192] Referring back to FIG. 4A and with continued reference to FIG. 5, the asset generation service 2 304 may generate data sets associated with the output product(s) (e.g. output product data set(s)) in response to receiving a trigger. The trigger may be associated with or may include trigger data. The trigger data may include data associated with the output product produced by production 504. The trigger may be generated by trigger generator 512. Trigger generator 512 may be part of a packaging line or may be present within a storage location, such as a warehouse. Trigger generator 512 may include sensor(s) configured to detect produced output product(s) and / or packaged output products. The sensor(s) may be configured to detect an identification element physically attached to the produced output product or the packaged output product. The sensor data may be used by trigger generator 512 to generate trigger data including data associated with the produced output product. Data associated with the produced output product may include a digital output product identifier associated with the produced output product. The trigger may be generated by a user, for example using a front-end application allowing to generate trigger data. The front-end application may display data associated with produced output products, such as output product name(s), output product quantities, output product identifiers, etc.. The data associated with the output product may be gathered from the one or more databases storing such data. The user may select output product(s) displayed by the front-end application. In response to selecting output product(s), a back-end application connected to the front-end application may generate the trigger data by collecting digital output product identifier(s) associated with the selected output product(s). The collected digital output product identifier(s) may be used to generate the trigger data.

[0193] The trigger or trigger data may be received by data gathering unit 414 of asset generation service 2 304. Data gathering unit 414 may be connected to a data source layer 412. The data source layer 412 may include one or more databases, such as DB1 314, DB2 316 and DB3 318. The databases may be distributed data sources. The distributed data source may be a data lake comprising output product data from a plurality of distributed data sources. A distributed data source may be a collection of data stored at different sites of a computer network. Each site might expose a degree of autonomy, providing services for the execution of local applications, but also participating in the execution of a global application. For instance, a distributed data source may be a distributed database. A distributed database can be created by splitting and scattering the data of an existing database over different sites or by federating together multiple existing databases. Each data source may contain only a fragment of the data associated with the output product data. This leads to a fragmentation of said data. Two common types of data fragmentation are horizontal fragmentation, wherein (possibly overlapping) subsets of data tuples are stored at different sites; and vertical fragmentation, wherein (possibly overlapping) subtuples of data tuples are stored at different sites. More generally, the data associated with the output product may be fragmented into a set of relations (tables of a relational database, distributed across multiple sites). The one or more distributed data sources may contain output product data associated with produced output products. The output product data may include at least one measured physical and / or chemical property of produced output product(s) and / or at least one physical and / or chemical property determined from collected data associated with the production and / or the use of produced output product(s) as previously described. At least one of the distributed data sources may contain data instances that relate to the output product for which the asset generation service 2 304 is configured to generate the output product data set(s). The data source layer 412 may be owned or controlled by the data owner of the data associated with output product data. The data source layer 412 may be associated with the data owner of the output product data. Data gathering unit 414 may be configured to gather output product data based on received trigger data (e.g. data associated with produced output products) from the data source layer 412, for example as described in the context of FIG. 6.

[0194] The output product data gathered by data gathering unit 414 may be provided to data transforming unit 416. Data transforming unit 416 may be configured to generate output product data set(s) by transforming output product data gathered by data gathering unit 414 based on one or more rule(s) retrieved from rule DB 412, for example as described in the context of FIG. 4B. Transforming may include filtering the gathered output product data, aggregating output product data gathered from multiple data sources into a given format, attribute construction to create or add new attributes to the output product data based on existing attributes, discretization to convert continuous output product data values into sets of data intervals with specific values, generalization of gathered output product data to convert low-level data attributes into high-level data attributes, manipulation to change or alter gathered output product data and / or normalization to converts output product data into another format to limit the occurrence of duplicated data. The rule(s) may define key-value pair(s) to be included in the generated output product data. The rule(s) may define value(s) to be included in the generated output product data. The rule(s) may define unit(s) for data point(s) and / or one or more conversion(s) to convert a unit associated with a data point into another unit. Gathered data may be aggregated and filtered to extract the value(s) matching the key(s) defined in the rule(s) from the aggregated data. The generated output product data sets may include one or more data points. The output product data sets may include one or more key-value pairs. The output product data sets may include the output product data in tabular form. Use of rule(s) associated with a product produced from such output product(s) allows to ensure that output product data point(s) required according to a data model associated with the product passport are contained in the output product data set, hence avoiding missing data point(s) during generation of a product passport associated with the product using said semantic model. The transformation allows to aggregate the gathered output product into a given data format, such as a tabular format, without the use of complex semantic models, hence facilitating generation and sharing of output product data set(s) within the product ecosystem. Such sharing may enable more efficient production and / or recycling processes based on the shared output product data, for instance output product composition data. The tabular format can be readily consumed via a decentral network by product passport service 322 described in the context of FIG. 3.

[0195] Data transforming unit 414 may further be configured to provide the generated output product data set(s) (hereinafter also referred to as asset(s)) to data provider unit 418. Data provider unit 418 may be configured to provide the received output product data set(s) to a database for storage, such as assets DB 404. The asset(s) may include or be associated with the digital output product identifier associated with the output product. This may allow to retrieve the asset based on the digital output product identifier. The asset(s) may further include input material identifier(s) of input material(s) used to produce the output product. This way, input material(s) used to produce the product can be identified. The asset(s) may be persisted by data transforming unit 416 in assets DB 404. Assets DB 404 may be configured to store output product data set(s) generated by data transforming unit 416. Assets DB 404 may be configured to provide output product data set(s) to data transfer service 402.

[0196] Data provider unit 418 may further be configured to provide data included in the generated output product data set(s), such as the digital output product identifier, to asset publisher service 408.

[0197] Asset publisher service 408 may be configured to generate group access data associated with the respective output product data set. The group access data may identify access control groups including decentral participant identifier(s) associated with decentral network participants permitted to access at the respective output product data set. The group access data may include a group access data identifier. The group access data may further identify one or more authorization rule(s) defining access to and / or usage of the output product data set. Asset publisher service 408 may further be configured to generate access control data including the digital output product identifier and the group access data identifier. The access control data may hence be associated with the output product data set as well as respective group access data. The access control data may further include access data associated with assets DB 404. The access data may include a locator or pointer to the assets DB 404 storing the respective output product data set. This may allow to access the respective output product data set based on data included in the access control data, e.g. the digital output product identifier and the access data. The group access data and access control data may be generated by asset publisher service 408 per data included in the output product data set, for example per digital output product identifier. The generated group access data and access control data may be provided to decentral data providing node 128 connected to asset generation service 2 304.

[0198] Decentral data providing node 128 may be part of a decentral network, such as decentral network 134 described in the context of FIG. 1 . Decentral data providing node 128 may be configured to provide output product data set(s) in response to a request received from decentral data consuming node(s), for example as described in the context of FIG. 9. Decentral data providing node 128 may be configured to control access to output product data set(s) based on associated group access data and access control data generated by asset publisher service 408, for example as described in the context of FIG. 9. Decentral data providing node 128 may be associated with a participant of the product ecosystem, such as a producer of the output product(s).

[0199] Data transfer service 402 may be configured to gather output product data set(s) from assets DB 404 in response to a request from decentral data providing node 128. Data transfer service 402 may be configured to fetch asset metadata from assets DB 404 based on data received from decentral data providing node 128. Data transfer service 402 may be configured to parse the fetched metadata to determine group access data associated with the respective output product data set and / or the storage location of the respective output product data set. Data transfer service 402 may be configured to gather respective output product data set(s) from assets DB 404 based on the fetched metadata. Data transfer service 402 may be configured to provide the gathered output product data set(s) to decentral data providing node 128.

[0200] The system may not comprise a decentral registry storing digital representations associated with identifier(s) of the generated output product data set(s) and allowing access to such output product data set(s) via the identifier(s) and endpoint(s) included in the digital representations. Hence, output product data set(s) may not be located by querying the decentral network 134 using the digital output product identifier but may only be accessed directly from decentral data providing node 128 using the digital output product identifier. Hence, location data pointing to the dedicated storage storing the output product data set as well as the output product identifier may be required to access the respective output product data set. The location data in combination with the digital output product identifier of the output product data set may result in a unique identifier allowing to uniquely identify a given output product data set within the decentral network. The location data may be provided by the entity operating the asset generation service 2 304, to the product passport service 322, for example as described in the context of FIG. 10.

[0201] FIG. 4B illustrates a diagram showing an example of a system configured to gather output product data and to transform at least part of the gathered output product data using a rule-based engine. Transforming at least a part of the gathered output product data may result in generation of output product data set(s) as described in the context of FIG. 4A. The system may be configured to perform the methods described in the context of FIG. 6 and FIG. 7. Data transforming unit 416 may include rule-based engine 422. The rule-based engine 422 may operate on individual data point(s), multiple data point(s) and / or the gathered output product data. The rule-based engine 422 may operate on data gathered per output product identifier individually. This allows to transform gathered output product data per output product, hence allowing a more granular transformation of the output product data. Rule-based engine 422 may receive a request to transform gathered output product data. The request may contain at least a part of the gathered output product data. Output product data may be gathered (see operation 420) by data gathering unit 414 from a data source layer 412 as described in the context of FIG. 4A. Rule based engine 422 may be configured to determine output product identifier(s) associated with the output product data. For instance, rule-based engine 422 may parse the received output product data to determine the respective output product identifier(s). The rule-based engine 422 may have access to one or more rule(s). The rule-based engine 422 may include one or more rule(s). The one or more rule(s) may be present within a rule template. The one or more rule(s) may be stored in a data storage, such as rule DB 410. The one or more rule(s) or rule template(s) may be provided to rule DB 410 by a user. The one or more rule(s) may correspond to unstructured data associated with instructions related to transformation operation(s). The rule template(s) may correspond to unstructured data associated with instructions related to transformation operation(s). The one or more rule(s) or the rule template may be included in a file provided by the user. The one or more rule(s) or the rule template(s) may be associated with output product type identifier(s) and / or output product data identifier(s). Rule-based engine 422 may generate a request to obtain one or more rule(s) from rule DB 410. The request may contain the respective output product identifier(s).

[0202] One or more rule(s) associated with the output product data to be transformed (e.g. one or more applicable rule(s)) may be provided to rule-based engine 422 in response to the request. The one or more rule(s) may be associated with product(s) produced from the output product associated with the output product data to be transformed, e.g. the output product associated with the output product data to be transformed may be used as input material to produce the chemical product. The chemical product may be an intermediate chemical product or a chemical product. The one or more rule(s) may be associated with or derived from a data model associated with the chemical product. Hence, the one or more rule(s) may ensure that data point(s) for such output products required according to the data model may be included in the generated output product data set. The one or more rule(s) may be defined by the mandatory output product data points present within the data model. The one or more rule(s) may be generated based on the mandatory output product data points present within the data model. This may ensure that output product data required by the data model is included in the generated output product data set. The one or more rule(s) may be associated with output product identifier(s) and / or output product type identifier(s). A mapping table may be used to map output product identifier(s) to corresponding output product type identifier(s). The output product type identifier(s) may be associated with output product type(s). The mapping table may be stored in a separate database (not shown). Rule-based engine 422 may be configured to gather output product type identifier(s) based on determined output product identifiers) and to request rule(s) based on the gathered output product type identifier(s). This may allow to gather rule(s) associated with output product type identifier(s) based on output product identifier(s), hence avoiding generation of rule(s) per output product identifier and reducing the number of rule(s) that need to be generated, stored and maintained in rule DB 410.

[0203] The one or more rule(s) may define aggregation rule(s) for aggregating output product data gathered from multiple data sources into a given format. The given format may be a tabular representation. Aggregation may hence result in filling gathered output product data into a tabular format. The one or more rule(s) may define filters to filter gathered output product data. The filters may be associated with or relate to the semantic model of the product. This may ensure that output product data required by the semantic model is included in the generated output product data set. The one or more rule(s) may define attribute construction(s) to create or add new attributes to the gathered output product data. The one or more rule(s) may define manipulation(s) to convert output product data point(s). For instance, data point(s) present within the gathered output product data may be converted from one unit into another unit. This may ensure that the generated output product data set includes data points associated with a unit required by the semantic model of the product. The one or more rule(s) may include a trigger condition and a corresponding group of one more actions. The trigger conditions may involve a set of variables, sometimes called “working memory”, which may contain data (sometimes called “facts” or “data tuples”) representing the states of pertinent real-world items. The one or more action(s) may include attribute construction, filters and / or manipulations. A given output product identifier and / or output type identifier may be associated with rule(s) defining aggregation, rule(s) defining filters, rule(s) defining attribute construction, rule(s) defining manipulations and / or rule(s) including a trigger condition and action(s). The rule(s) may be associated with a given order.

[0204] Rule-based engine 422 may be configured to initialize the rule engine (see operation 426). Initialization of the rule engine may include generating rule data executable by a processor included in rule-based engine 422. The rule data may include or correspond to executable logic. This may allow to transform rule(s) or rule template(s) present in unstructured data form into code that can be executed by the processor. Execution of the code may result in applying the executable rule data to the gathered output product data (see operation 428) to transform the output product data according to the obtained rule(s). Execution of the logic may result in matching gathered output product data to condition(s) included in the executable logic, evaluating the condition(s) with matched output product data and triggering execution of rule actions based on condition evaluation results. Transforming the output product data may include filtering gathered output product data. Filtering the gathered output product data may include comparing individual data points present within the gathered output product data to data points defined by the filter(s) to determine output product data points to be included in the output product data set. Transforming the output product data may include comparing attributes of the gathered or filtered output product data to attributes defined in rule(s) to determine whether new attributes have to be created or added to the gathered or filtered output product data. In addition or alternatively, transforming may include comparing attribute(s) included in the gathered or filtered output product data or output product data including added or created attribute(s) to attribute(s) included in the modification rule(s). The modification rule(s) may include a trigger condition which may be associated with one or more action(s), for example unit conversion, if the trigger condition is satisfied and / or error handling if application of filters results in empty data points due to lack of data points in the gathered output product data. The trigger condition may be satisfied if the attribute(s) included in the gathered or filtered output product data or output product data including added or created attribute(s) are not matching attribute(s) defined in the modification rule(s). Operations performed by rule-based engine 422 may be determined by rule(s) gathered from rule DB 410. For instance, rule(s) gathered from rule DB 410 may determine whether rule-based engine 422 operates on individual data point(s) and / or multiple data point(s) and / or the whole gathered output product data.

[0205] Rule-based engine 422 may be configured to determine whether the gathered output product data can be transformed by one or more applied rule(s) (see operation 430). Gathered output product data may not be transformed or only partially transformed (e.g. transformation may result in at least one error associated with applying one or more obtained rule(s) to the gathered output product data) if the gathered output product data does not include data point(s) required according to one or more obtained rule(s). Rule-based engine 422 may provide the generated output product data set to assets DB 404 responsive to the gathered output product data being successfully transformed (e.g. responsive to generation of an output product data set by applying one or more obtained rule(s) without resulting in an error.

[0206] If at least a part of the gathered output product data could not be transformed, rule based engine 422 may proceed to operation 432. In operation 432, rule-based engine 422 may generate message data indicating that at least part of the gathered output product data could not be transformed. The message data may include an indication which data point(s) of the gathered output product data could not be transformed. The message data may be provided to a display device configured to display data received from rule-based engine 422. The display device may comprise a graphical user interface 434. The display device may display the message in response to receiving message data from rule-based engine 422. This allows to trigger correction or updating of data point(s) identified as not matching one or more of the obtained rule(s). After correction or updating of respectively identified data point(s), gathering and transformation of updated or corrected output product data may be initiated.

[0207] FIG. 6 illustrates a flow chart of an example method for generating data associated with the production of a chemical product. The method illustrated in FIG. 6 may be implemented by the systems illustrated in FIG. 4A to FIG. 5. The chemical product may be a chemical product as described in the context of FIG. 3. The data associated with the production of the chemical product may include output product data set(s) associated with output products. The output product(s) may correspond to input material(s) used to product the chemical product. The output product may be produced by a production, such as illustrated in FIG. 5. With reference to FIG. 8, data associated with the output product may be provided. The data may be provided by a computing system connected to the system performing the method of FIG. 6, such as an asset generation service described in the context of FIG. 4A to FIG. 5. The data may be provided by a user via a communication interface to the system performing the method of FIG. 6, such as the asset generation service. The data may be provided to data gathering unit 414 of the asset generation service. The provided data may be generated in response to receiving a trigger, for example as described in the context of FIG. 5. Data associated with the output product may include digital output product identifier(s). The digital output product identifier(s) may include output product name, output product number, output product ID, serial number, an identification number, LOT number, batch number or a combination thereof.

[0208] With continued reference to FIG. 8, output product data may be gathered based on the provided data. The output product data may be gathered from a data source layer, such as data source layer 412 described in the context of FIG. 4A and FIG. 4B. The output product data may be gathered from data source layer 412 based on digital output product identifier(s) included in the data provided in block 902. The output product data may be gathered by data gathering unit 414. The output product data may include physical and / or chemical properties of produced output products and / or production data associated with the production of the output product as described in the context of FIG. 4A.

[0209] An output product data set may be generated by transforming the gathered output product data using a rule-based engine including one or more rule(s) related to a data model associated with chemical product passports of the chemical product. The chemical product may be produced from the output product by using the output product as input material within at least one production step of a production chain used to produce the chemical product. The production process of the product may include one or more production steps. The production steps may be performed by one or more entities of the product ecosystem. The output product may be used as input material within at least one of such production step.

[0210] With reference to FIG. 4B, FIG. 47 and FIG. 8, transforming the gathered output product data by the rule-based engine may include identifying one or more rule(s) applicable to the gathered output product data. The gathered output product data may be transformed by data transforming unit 416. The applicable rule(s) may be identified based on an identifier associated with each applicable rule matching or being related to an output product identifier included in the gathered output product data. The identifier associated with each applicable rule may include an output product identifier matching the output product identifier included in the gathered output product data. The identifier associated with each applicable rule may include an output product type identifier related to the output product identifier included in the gathered output product data. The output product type identifier related to the output product identifier included in the gathered output product data may be determined based on mapping data as described in the context of FIG. 4B.

[0211] With continued reference to FIG. 4B, FIG. 7 and FIG. 8, executable logic may be generated from the one or more applicable rule(s). The executable logic may be generated by data transforming unit 416. Executable logic may include machine code, interpretable code, bytecode, and / or code that runs on a virtual machine. The logic included in the applicable rule(s) may be encoded in the executable logic. The logic included in the applicable rule(s) may be mirrored in the executable logic. Upon finalizing the generation of the executable logic, data transforming unit 416 may sent a response to data gathering unit 414 indicating finalizing the generation of the executable logic.

[0212] With continued reference to FIG. 4B, FIG. 7 and FIG. 8, an output product data set may be generated by transforming the gathered output product data by executing the generated executable logic by the rulebased engine subject to rule execution criteria. Data gathering unit 414 may sent a request to data transforming unit 416 to transform the output product data based on the executable logic generated for the applicable rule(s). Rule execution criteria may include rule execution order, exemptions and conditions. For instance, the rule designated in the condition is executed first as it triggers the execution or exemption action in the execution of the rule with which it is associated. The generated output product data set(s) may be provided from data transforming unit 416 to data provider unit 418.

[0213] It may be verified whether the gathered output product data could be transformed according to one or more applicable rule(s) (e.g. one or more rule(s) gathered from rule DB 410 based on the gathered output product data). Verification may be performed as described in the context of FIG. 4B. If the gathered output product data could be transformed according to the applicable rule(s), e.g. application of such rule(s) did not result in any error, the method may proceed to block 612. Otherwise message data may be generated and provided, for example as described in the context of FIG. 4B.

[0214] The generated output product data set may be provided for access via a decentral network, such as decentral network 134 described in the context of FIG. 1 , under control of the data owner of the output product data set. With reference to FIG. 8, this may include storing the generated output product data set in a data storage, such as assets DB 404, for example as described in the context of FIG. 4A. With continued reference to FIG. 8, this may further include generating group access data and access control data as described in the context of FIG. 4A. The group access data and access control data may be used to control access to the associated output product data set, for example as described in the context of FIG. 9.

[0215] Use of rule(s) associated with a data model associated with the chemical product passport allows to ensure that output product data point(s) required according to the data model are contained in the output product data set, hence avoiding missing data point(s) during generating and / or updating the chemical product passport using the data model. The transformation allows to aggregate the gathered output product data into a given data format, such as a tabular format, without the use of complex data models, hence facilitating generation and sharing of output product data set(s) within the product ecosystem. Such sharing may enable more efficient production and / or recycling processes based on the shared output product data, for instance output product composition data. The tabular format can be readily consumed via the decentral network by a product passport service, such as product passport service 322 described in the context of FIG. 3 and FIG. 10, configured to generate and / or update chemical product passports. Verification by the consumer side ensures that the chemical product passports contain the data defined by the data model associated with the chemical product passports, hence allowing to reduce the complexity associated with the output product data set generation at the provider side by avoiding the use of complex data models during generation of the output product data set(s). This may enable reliable sharing of output product data of output product(s) irrespective of the existence of data models for such output products since the rule(s) required to transform the gathered output product data may be readily derived from the data model associated with the respective chemical product passport of the chemical product produced using such output product(s).

[0216] FIG. 9 illustrates an example of a decentral system for accessing data associated with the production of a chemical product. The decentral system may be a decentral peer-to-peer network 134 as described in the context of FIG. 1. The chemical product may be a chemical product as described in the context of FIG. 3. The data associated with the production of the chemical product may include input material data associated with input material(s) used to produce the chemical product and chemical product data associated with the chemical product. The input material(s) may be used within production step(s) of the production chain used to produce the chemical product. The input material(s) may include output products described in the context of FIG. 5.

[0217] The input materials may be associated with input material data. The input material data may be generated as described in the context of FIG. 4A to FIG. 5. The product may be associated with chemical product data. The chemical product data may be generated as described in the context of FIG. 4A to FIG. 5.

[0218] The input material data or chemical product data may be stored in assets DB 404 associated with data transfer service 402. Assets DB 404 may be associated with a decentral provider node 116. The decentral provider node may be associated with a decentral network participant. The decentral network participant may be the producer of the input material or the product. The decentral network participant may be the data owner of the input material or product data stored in assets DB 404. The input material data or chemical product data may represent at least a part of a digital twin of the physical entity of the input material or chemical product, respectively. The digital twin may be a digital representation of the physical entity. The digital twin may hence represent a digital version of said physical entity. Once created, the digital twin may be used to represent the physical entity of the input material or chemical product in a digital representation of a real-world system.

[0219] The decentral system may be used to gather input material data associated with input material(s) used to produce the chemical product and chemical product data as described in the context of FIG. 13A and FIG. 17.

[0220] The decentral system may include one or more decentral participants, such as a data consumer and a data provider. The data consumer and the data provider may be connected via a decentral network, such as a decentral peer-to-peer network 134 (see for example FIG. 1). The data provider may provide data, such as input material data or chemical product data, to the data consumer. The data consumer may request input material data or chemical product data from the data provider. The data provider may correspond to an entity producing the respective input material or the chemical product. The data consumer may correspond to an entity operating the product passport service as illustrated in FIG. 3 and FIG. 10. The data provider may be associated with a data provider environment 904. The data consumer may be associated with a data consumer environment 902. The environments may include one or more node(s). The node(s) may be connected via peer-to-peer communication channels to allow data transfer between the nodes, as described in the context of FIG. 1. The decentral network may include more or less environments than illustrated in FIG. 9.

[0221] The participants of the decentral network may be associated with decentral participant identifiers. Each participant of the decentral network may be associated with one or more decentral participant identifier(s). The decentral participant identifier may comprise any identifier uniquely associated with a participant of the decentral network and / or with a production site of the participant of the decentral network. The decentral participant identifier may include letters and / or numbers. The decentral participant identifier may include one or more Universally Unique Identifier(s) (UUID(s)) and / or one or more Decentralized Identifier(s) (DID(s)). The decentral participant identifier may be associated with or may include a verifiable claim or credential. The verifiable claim may be issued by a central or decentral identity issuer making one or more claims about a subject, such as an entity being a trustworthy participant of the decentral network. For instance, the issuer may make a claim about a consumer (e.g. the entity operating data consuming network node(s)) or a provider (e.g. the entity operating data providing network node(s)) the decentral participant identifier is associated with. The verifiable claim may include those claim(s) as well as proof instructions to prove that claim(s) have not been tampered with and were indeed issued by the claims issuer. The verifiable claim may also include duration information metadata that defines a period of time that the verifiable claim is valid for use or that defines a specific number of times that the verifiable claim is authorized for use. The verifiable claim may also include a DID of the claims issuer and / or the subject, such as an entity. The verifiable claim may be signed by the claims issuer. The claims issuer may provide the verifiable claim to a claims holder, such as the entity, for presentation to any relying party that relies upon the veracity of those claims, such as a decentral data provider. The signature of the verifiable claim may be validated with a public key associated with the claims issuer to determine that the respective entity is a trusted entity within the decentral network. The verifiable credential may be presented by a decentral data consuming network node and may be used by a decentral data providing network node to verify that the decentral participant associated with the decentral data consuming network node is a trusted entity within the decentral network prior to providing access to data, such as output product data, hence ensuring that the output product data can be exchanged in a secure and controlled manner within the decentral network. Data consumer environment 902 may include a consumer node 326 (e.g. decentral data consuming network node 326) and chemical product passport service 322. Chemical product passport service 322 may include or correspond to the service illustrated in FIG. 3 and FIG. 10. Consumer node 326 may be configured to communicate with chemical product passport service 322. Consumer node 326 may be configured to receive data from chemical product passport service 322 and to provide data to chemical product passport service 322. Consumer node 326 may be configured to receive data from provider nodes, such as provider node 128. Consumer node 326 may be configured to request data from provider nodes, such as provider node 128. Consumer node 626 may be configured to receive data from chemical product passport service 322, configured to provide data to chemical product passport service 322 and configured to receive and / or request data from provider node(s), such as provider node 128. Consumer node 326 may be configured to request input material data or chemical product data stored in assets DB 404 associated with the respective provider node, such as provider node 128. Chemical product passport service 322 may be configured to send a request for data to consumer node 326, for example as described in the context of FIG. 13A, FIG. 13B and FIG. 17. Chemical product passport service 322 may be configured to process data, such as input material data and chemical product data, received from consumer node 326, for example as described in the context of FIG. 12A to FIG. 17.

[0222] Data consumer environment 902 may be associated with a participant of the chemical product ecosystem, such as the product ecosystem illustrated in FIG. 1. For instance, data consumer environment 902 may be associated with an input material producer, such as chemical product producer 102 or a chemical product producer, such as chemical product user 106, receiving input material(s) and producing the chemical product using the input material(s) or a chemical product user, such as end-chemical product producer 108, producing end-products from the chemical product.

[0223] Data consumer environment 902 may be associated with an entity operating the chemical product passport service 322. Data consumer environment 902 may be associated with an entity performing the methods illustrated in FIG. 14 to FIG. 18 and / or FIG. 22. The entity performing such methods may be a participant of the product ecosystem. The entity performing such methods may not be a participant of the product ecosystem but may function as a service provider for a participant of the product ecosystem. The service provider may generate and provide data completeness metrics. The service provider may generate and / or update chemical product passports based on data gathered from data provider environments associated with input material data and chemical product data.

[0224] Data provider environment 904 may include provider node 128, data transfer service 402 and assets DB 404. Data provider environment 904 may include an asset generation system, such as asset generation service 2 304 illustrated in FIG. 4A, FIG. 4B and FIG. 5. Data provider environment 904 may be associated with a data owner, such as an input material producer or chemical product producer. Data provider environment 904 may include assets DB 404 storing input material data of input material(s) used to produce the chemical product or chemical product data associated with the chemical product. Assets DB 404 may be a dedicated storage associated with the data owner. The data owner may own such dedicated storage. The data owner may have access to such dedicated storage. The data owner may control access to such storage. Provider node 128 may be configured to provide data, such as input material data or chemical product data stored in assets DB 404. Provider node 128 may be configured to perform authentication and authorization step(s) prior to providing the data, for example as described with reference to FIG. 13A later on. Provider node 128 may be coupled to data transfer service 402 configured to gather input material data or chemical product data from assets DB 404 in response to a request received from provider node 128 and to provide the gathered data to provider node 128.

[0225] FIG. 10 illustrates an example of a chemical product passport service configured to generate and / or update a chemical product passport associated with a chemical product. The chemical product may be a chemical product as described in the context of FIG. 3. The chemical product passport service may be configured to perform the methods illustrated in FIG. 14 to FIG. 16, FIG. 19 and / or FIG. 22.

[0226] The chemical product passport service 322 may include different modules or units. In the embodiment illustrated in FIG. 10, chemical product passport service 322 includes asset registration and linking module 1002, asset validation system 1004, and chemical product passport generator 1008. Chemical product passport service 322 may further include one or more databases, such as registry 1310. Chemical product passport service 322 may further include data quality analyzer 1006. At least a part of the modules or units may be configured to communicate with each other. Use of a modular service allows to flexibly adjust the modules or units, for example by addition, removal or modification of single modules or units.

[0227] The chemical product passport service 322 and one or more modules included therein may be accessed via a communication interface. Accessing the chemical product passport service 322 may involve authentication and / or authorization steps. For instance, a user may provide authentication data and access to the chemical product passport service 322 may only be granted upon successful authentication. Access to module(s) included in the chemical product passport service 322 may be subject to successful authorization. For instance, some module(s) may only be accessible by a defined user group. For example, chemical product passport generator 1008 may only be accessible by a user group defined as chemical product passport generators.

[0228] The asset registration and linking module 1002 may be configured to provide an interface, such as a digital user interface or a computing interface, for providing asset data and associated data source data associated with data sources providing such asset data. The data sources may be provider nodes configured to provide data, such as input material data and chemical product data, stored in dedicated storages associated with such provider nodes, for example as described in the context of FIG. 9. Data source data may include endpoints associated with such data sources. Data source data may further include a decentral participant identifier related to the data source and / or a participant role associated with the participant of the chemical product ecosystem and being associated with or controlling the data source. Asset data may include asset identifiers associated with assets (e.g. input material data or chemical product data) provided by such data sources. The asset data may further include relationship representation(s) specifying relationships between the asset identifier associated with the asset data (e.g. parent identifier) and further asset identifier(s) (e.g. child identifier(s)) associated with asset(s) of input material(s) used to produce the intermediate chemical product or chemical product the parent identifier is associated with, for example as illustrated in FIG. 11 B.

[0229] Asset registration and linking module 1002 may further be configured to store data received via the interface in registry 1310. Prior to storage, the received data may be processed. For instance, the provided data may be transformed, for example by aggregation, interrelation or the like. With reference to FIG. 11A, the data acquired by the asset registration and linking module 1304 may be stored in registry 1310. Registry 1310 may include data associated with data sources 1402. Data associated with data sources may include asset identifiers associated with assets, such as input material data and chemical product data, provided by data sources associated with participants of the chemical product ecosystem. The asset identifiers may be interrelated with data source data. The data source data may include a participant role of the participant associated with the data source providing the asset, a decentral participant identifier related to the data source providing the asset and an endpoint of the data source providing the asset. The asset identifier may be further interrelated with child identifiers associated with input material(s) used to produce the output chemical product the asset is associated with. Since interrelation may not be applicable for all input materials used to produce the chemical product, the line connecting the asset ID with the child ID(s) is illustrated by a dashed line in FIG. 11 A. The output chemical product may correspond to an input material used to produce the chemical product.

[0230] To gather data associated with the production of the chemical product from one or more data sources providing such data based on a given output chemical product identifier, identifier(s) associated with input material(s) used to produce the chemical product may be linked to or related to the output chemical product identifier associated with the output chemical product produced from such input material(s). The output chemical product may be an intermediary chemical product used to produce the chemical product or the chemical product. This way identifier(s) associated with input material(s) used to produce a given chemical product may be determined based on the chemical product identifier associated with such chemical product. With reference to FIG. 11 B, registry 1310 may include a linking of asset identifiers of at least a part of the input material(s) used to produce the chemical product to the chemical product identifier (see left side of FIG. 11 B). In addition or alternatively, registry 1310 may include a linking of asset identifiers to child identifiers in the form of a tree structure, with the chemical product identifier being the top node of the tree (see right side of FIG. 11 B). The linking illustrated in FIG. 11 B may be generated from the asset data included in registry 1310 by resolving the relationships between asset identifiers included in such registry. With reference to FIG. 11 C, the asset data and associated data source data may be provided as entries to a digital user interface, such as graphical user interface 1104. In another embodiment (not shown), the data source data and associated asset data may be provided as entries to a computing interface. The graphical user interface 1104 may include a field for entering the asset ID 1106 and a field for entering data source data 1108 associated with the asset ID. Field 1108 may include a list of data sources and may allow the user to select the appropriate data source providing the asset associated with the asset ID. The graphical user interface 1104 may further include one or more data fields for entering child identifiers of the asset ID entered in field 1106. Graphical user interface 1104 may provide the option to upload such child identifiers using button 1110. Storage of the data entered into graphical user interface 1104 in registry 1310 may be triggered using button 1114. Based on the entries generated in the digital user interface or the data provided to the computing interface, data associated with the data sources may be generated and stored or persisted in registry 1310.

[0231] In an alternative embodiment, the interface may include a communication interface configured to receive data source data and associated asset data. For instance, the data source data and associated asset data may be provided via such interface to asset registration and linking module 1002.

[0232] The asset validation system 1004 may be configured to gather data associated with the production of the chemical product from one or more data sources, such as provider nodes, and to validate the gathered data, for example as described in the context of FIG. 13A to FIG. 17. Asset validation system 1004 may be configured to persist the validated data in one or more databases. Asset validation system 1004 may be configured to provide the validated data to chemical product passport generator 1008. Asset validation system 1004 may further be configured to provide the validated data to data quality analyzer 1006.

[0233] Data quality analyzer 1006 may be configured to validate the amount of data, such as validated data generated by asset validation system 1004, accessible for generating and / or updating chemical product passports. Data quality analyzer 1006 may include a metrics generator 1902 configured to generate data completeness metrics, for example as described in the context of FIG. 19 to FIG. 22. Data quality analyzer 1006 may be configured to perform the methods illustrated in FIG. 22. Data quality analyzer 1006 may be configured to generate a data completeness metric as illustrated in FIG. 21 A to FIG. 21 C. Data quality analyzer 1006 may be configured to provide generated data completeness metrics to chemical product passport generator 1008. By validating the quality of the data with respect to a degree of correlation between the data included in a data model associated with the chemical product passport and the validated data generated by asset validation system 1004, transparency on the number of data points available for generating and / or updating chemical product passports can be achieved. This transparency allows to determine the reliability of the passport data included in the generated and / or updated chemical product passports and allows to identify input material producers not yet having generated and / or provided input material data defined by the data model. This way, missing data can be requested and it can be ensured that the passport data has a sufficient degree of completeness to facilitate efficient further processing of the products associated with such chemical product passports

[0234] Chemical product passport generator 1008 may be configured to generate chemical product passports associated with products and / or to update existing chemical product passports based on the validated data generated by asset validation system 1004. Chemical product passport generator 1308 may be configured to perform the methods illustrated in FIG. 14 and FIG. 18. An example of the chemical product passport generator 1008 is illustrated in FIG. 12. Chemical product passport generator 1008 may be configured to persist the generated chemical product passports in an archive. Chemical product passport generator 1008 may be configured to provide the generated chemical product passports for access by data consumers. The generated chemical product passports may be provided via a decentral network, such as illustrated in FIG. 1. The generated chemical product passports may be provided to an application, such as illustrated in FIG. 12. The generated chemical product passports may be provided under control of the data owner of the chemical product passport.

[0235] FIG. 12 illustrates a system for generating and / or updating a chemical product passport associated with a chemical product. The chemical product may be a chemical product as described in the context of FIG. 3. The chemical product may be produced from one or more input material(s) by a production chain. The production chain may include one or more production step(s) as described in the context of FIG. 3. The chemical product passport generator 1008 may be configured to perform the methods illustrated in FIG. 1s4 and FIG. 18. The chemical product passport may include one or more decentral identifier(s) and passport data as described in the context of FIG. 3.

[0236] The system may include an application 1214 and a chemical product passport generator 1008. The application 1214 may be connected to the chemical product passport generator 1008 via a communication interface, for example via an API. The application 1214 may include an authentication module 1216. The authentication module may be configured to authenticate a user. The authentication module 1216 may be configured to receive authentication data, such as a username and password, a digital credential indicating the user identity, from the user. The authentication module 1216 may be configured to verify or initiate verification of the received authentication data. Verification may be performed using an authentication protocol, such as OAuth and / or OpenlD Connect. The application 1214 may receive a token containing information about the user and the permissions granted to the user. The token may be passed along with a request to chemical product passport generator 1008 and may be used by chemical product passport generator 1008 to authenticate and authorize the request received from application 1214.

[0237] Application 1214 may further include an ID provider 1218. The ID provider 1218 may be configured to determine chemical product identifier(s) associated with the chemical product. The chemical product identifier(s) may uniquely identify the chemical product. The chemical product identifiers may include a batch number and / or a LOT number a part number, a serial number, a battery identification number or a vehicle identification number. The ID provider 1218 may include a code reader configured to read the code present on the physical entity of the chemical product and to determine the chemical product identifier based on the acquired data. The ID provider 1218 may include a camera configured to acquire image data of an identification number present on the physical entity of the chemical product and a unit configured to determine the identification number from the acquired image data. The ID provider 1218 may further be configured to provide the determined chemical product identifier(s) to a database, such as local db 1222, of application 1214 for storage. This way, a list of all products and associated chemical product identifier(s) related to a user may be stored in the database.

[0238] Application 1214 may further include a data refresher 1220 (or data refreshing unit). Data refresher 1220 may be configured to gather data, such as chemical product passports, stored in local db 1222 of application 1214, for example based on chemical product identifier(s) received from ID provider 1518. Data refresher 1220 may further be configured to provide the gathered data, for example for display within a user interface of application 1214. Data refresher 1220 may further be configured to generate a request for a chemical product passport and to provide the generated request to passport archive 324 in response to receiving a chemical product identifier from ID provider 1218. The request may be generated after determination that local db 1222 does not store a chemical product passport matching the received chemical product identifier(s).

[0239] The request may include the chemical product identifier(s) associated with the chemical product, the authentication data and optionally a date indicating last access by the application 1214 to the chemical product passport. The request may be provided directly to passport archive 324. The request may be provided via chemical product passport generator 1008 to passport archive 324 (not shown). Passport archive 324 or chemical product passport generator 1008 may be configured to authenticate and optionally authorize the request. Upon successful authentication and optionally authorization, passport archive 324 or chemical product passport generator 1008 may be configured to determine whether passport archive 324 contains a chemical product passport matching the data included in the received request, such as matching the chemical product identifier included in the received request. In addition, passport archive 324 or chemical product passport generator 1008 may further be configured to determine whether the respective chemical product passport has been updated with respect to the last time the chemical product passport was accessed by said application. For example, passport archive 624 or chemical product passport generator 1008 may be configured to compare the date indicating last access to the chemical product passport with a date indicating last update of such chemical product passport in passport archive 324. If such dates are matching or if the passport stored in passport archive 324 has been updated earlier than the data indicating last access, passport archive 324 or chemical product passport generator 1008 may be configured to provide the chemical product passport matching the received chemical product identifier(s) to data refresher 1220 of application 1214. Providing the chemical product passport may include determining access policy data associated with the chemical product passport and applying the access policy data to the chemical product passport. The access policy data may be determined by chemical product passport generator 1008. The access policy data may be determined based on chemical product identifier(s) associated with the chemical product included in the received request. The access policy data may identify group access data associated with the chemical product passport and optionally associated consumer access data. The group access data may define consumer identifier(s) associated with data consumer(s) permitted to access the chemical product passport. The determined access policy data may be applied to the chemical product passport, for example by chemical product passport generator 1008.

[0240] Applying the access policy data may include validating whether the data consumer is permitted to access the chemical product passport, and responsive to validating access to the chemical product passport for the data consumer validating whether the data consumer is permitted to perform the requested action(s) on the chemical product passport.

[0241] In another example, applying access policy data may include validating whether the data consumer is permitted to access the chemical product passport, and responsive to validating access to the chemical product passport for the data consumer determining usage data associated with the validated data used to generate the chemical product passport and apply the determined usage data to the chemical product passport.

[0242] In yet another example, applying access policy data may include validating whether the data consumer is permitted to access the chemical product passport.

[0243] Validating whether the data consumer is permitted to access the chemical product passport may include determining consumer identifier(s) based on the received authentication data. The consumer identifier(s) may be determined from data stored in registry 1010, for example from relationship representations mapping authentication data to consumer identifier(s) stored in registry 1010. The determined consumer identifier(s) may be mapped to consumer identifier(s) defined by the group access data. In addition, group access data associated with validated input material data associated with input material(s) used to produce the chemical product may be determined. The determined consumer identifier(s) may be matched with consumer identifier(s) defined by group access data associated with validated input material data. If the determined consumer identifier(s) match a consumer identifier defined by the group access data, the request may be authorized and the chemical product passport may be provided to data refresher 1220 of application 1214. If no match is found, passport archive 324 or chemical product passport generator 1008 may be configured to generate message data indicating a lack of authorization to access the chemical product passport. The message data may be provided to application 1214.

[0244] If the chemical product passport stored in passport archive 324 has been updated later than the date indicating last access, passport archive 324 or chemical product passport generator 1008 may be configured to provide the chemical product passport, to generate message data and to provide such message data to data refresher 1220. The message data may indicate that the chemical product passport has been updated since the last access. Data refresher 1220 may be configured to store the chemical product passport(s) received from passport archive 324 or chemical product passport generator 1008 in local db 1222 or to update chemical product passports stored in local db 1222 based on the data received from passport archive 324 or chemical product passport generator 1008.

[0245] If data refresher 1220 receives message data indicating that no chemical product passport is available for the provided chemical product identifier(s) from passport archive 324 or chemical product passport generator 1008, data refresher 1220 may be configured to generate a request for generation of such a chemical product passport. The request may include the chemical product identifier(s) associated with the chemical product, the authentication data, an application identifier, an endpoint of the application 1214 or a combination thereof. The request may be provided to chemical product passport generator 1008. The request may be provided to stream storage system 1202 of chemical product passport generator 1008. The request may be authorized as previously described.

[0246] The chemical product passport generator 1008 may be part of a chemical product passport service, for example chemical product passport service 322 as described in the context of FIG. 3 and FIG. 10. The chemical product passport generator 1008 may be configured to generate chemical product passports associated with products, for example as described in the context of FIG. 14. The chemical product passport generator 1008 may be configured to update existing chemical product passports associated with products, for example as described in the context of FIG. 18. The chemical product passports may be generated and / or updated in response to a request received from applications, such as application 1214.

[0247] The chemical product passport generator 1008 may be connected to an asset validation system, such as asset validation system 1004 described in the context of FIG. 10, FIG. 13A and FIG. 13B, configured to validate data gathered from data provider via a decentral network, for example as described in the context of FIG. 15 to FIG. 17. The chemical product passport generator 1008 may be connected to a data quality analyzer, such as data quality analyzer 1006 described in the context of FIG. 10, FIG. 19 and FIG. 21 , configured to determine data completeness metrics, for example as described in the context of FIG. 22. The chemical product passport generator 1008 may be connected to the asset validation system and / or the data quality analyzer via a communication interface, such as an API.

[0248] The chemical product passport generator may include a stream storage system 1202, a passport archive 324 and a data aggregator 1208. The passport archive 324 may store chemical product passports associated with products. The chemical product passports stored in passport archive 324 may be generated by chemical product passport generator 1008. The chemical product passports stored in passport archive 324 may be updated by chemical product passport generator 1008. The passport archive 324 may be configured to provide chemical product passports upon request, for example upon request of application 1214 and / or upon request of chemical product passport generator 1008.

[0249] Stream storage system 1202 may be configured to receive requests for chemical product passports from one or more applications, such as application 1214. Requests may be received via a communication interface, such as an API. Stream storage system 1202 may be configured to authenticate such requests, for example based on authentication data contained in such requests. The requests may represent a stream of data. Such a stream may be an ordered sequence of records or data packages received from applications 1214 relatively continuously, i.e. not in accumulated batches or chunks. A record may for example comprise a request for a chemical product passport for a given chemical product. A record may be defined as data that can be delivered continuously in small chunks or increments. The records may or may not be time-ordered. Data refresher 1220 may be configured to generate data package(s) including the chemical product identifier(s) received from ID provider 1218. A data package may be generated per chemical product. The data package may include further data, such as a time stamp, a date stamp, authorization data, an application identifier, an application endpoint or a combination thereof. The data package may represent a message or an event. The generated data package(s) may be provided to stream storage system 1202.

[0250] Stream storage system 1202 may be configured to store data packages received (e.g. pushed) from data refresher 1220. Data packages may be stored upon successful authentication. The stream storage system 1202 may be configured to provide the stored data to data aggregator 1208. The stream storage system 1202 may be configured to provide the stored data to data gathering unit 1210 of data aggregator 1208. Stream storage system 1202 may comprise one or more persistent or non-persistent logs 1204, 1206. In this embodiment, stream storage system 1202 comprises two persistent or non-persistent logs 1204, 1206 (i.e. log 1 1204 and log 2 1206). Records stored in said logs may be ordered, for example by using IDs. This allows to identify a record within a specific log. A record may include a data package generated by data refresher 1220. Stream storage system 1202 may provide a streaming service or stream processing service between one or more streaming sources (e.g. data refresher 1220) and one or more streaming sinks (e.g. log 1 1204 and log 2 1206). Stream storage system 1202 may act as a persistent or non-persistent stream sink for requests for chemical product passports received from applications 1214. For example, open-source software systems such as Apache Kafka ("Kafka") or Azure Event Hubs may act as a persistent stream sink.

[0251] Stream storage system 1202 may be configured to pull data package(s) from the applications 1514. For instance, stream storage system 1202 may be configured to request data package(s) from the applications 1214 at regular time intervals.

[0252] Stream storage system 1202 may be configured to determine if the received or pulled data package(s) is / are already contained in the one or more persistent or non-persistent logs as described in the context of FIG. 13A. Data aggregator 1208 may be connected to the stream storage system 1202. Data gathering unit 1210 of data aggregator 1208 may be connected to stream storage system 1202. Data gathering unit 1210 may be connected to one or more persistent or non-persistent logs (e.g. in this embodiment in log 1 1204 and log 2 1206) of stream storage system 1202 to ingest and process data package(s) stored within the log(s). The stream storage system 1202 may be in a publisher-subscriber relationship with the data gathering unit 1210. For instance, data in one or more the logs(s) may be periodically read (e.g. pulled) by data gathering unit 1210. To avoid consumption of a data package stored in a log several times, such data package may be marked as consumed by stream storage system 1202. To avoid consumption of a data package stored in a log several times, an integer indicating the offset of the next data package to consume may be used. Such integer may be just one number for each persistent or non-persistent log. Such integer may be periodically checkpointed. Use of such an integer may allow data gathering unit 1210 to re-consume data packages by rewinding the integer to an old offset.

[0253] Data gathering unit 1210 may be configured to gather data associated with the production of the chemical product based on the data ingested from stream storage system 1202. Data gathering unit 1210 may be configured to determine input material identifier(s) associated with input material(s) used to produce the chemical product based on the chemical product identifier included in the ingested data. For example, data gathering unit 1210 may query registry 1010 for input material identifier(s) based on the chemical product identifier(s) included in the ingested data. In addition, data gathering unit 1210 may be configured to initiate determination of input material identifier(s) associated with input material(s) used to produce the chemical product associated with the chemical product identifier(s) included in the ingested data. Such determination may be initiated by generating a request including the chemical product identifier(s) and providing such request to decentral network node 326 associated with chemical product passport generator 1008. Decentral network node 326 may be configured to generate a request to a further decentral network node configured to determine such input material identifier(s) based on received chemical product identifier(s). The further network node may be configured to determine decentral input material identifier(s) associated with input material(s) used to produce the chemical product based on the receive chemical product identifier(s) by querying the decentral network and to return the determined decentral input material identifiers to network node 326. The determined input material identifier(s) may be returned via node 326 to data gathering unit 1210.

[0254] Data associated with the production may include validated data associated with the production of the chemical product. Data gathering unit 1210 may be configured to gather such validated data from a database associated with asset validation system 1004, such as archive DPP chemical product type A 1320. Asset validation system 1004 may include or be associated with one or more databases storing validated data associated with the production of the chemical product. The validated data may be generated and stored in such database as described in the context of FIG. 13A, FIG. 13B, FIG. 16 and FIG. 17. The validated data may be gathered based on the chemical product identifier(s) associated with the chemical product and input material identifier(s) associated with input material(s) used to produce the chemical product. In addition, data gathering unit 1210 may be configured to request gathering and validation of data associated with the production of the chemical product by asset validation system 1004. The request may include the chemical product identifier(s) associated with the respective chemical product and optionally input material identifier(s) associated with input material(s) used to produce the chemical product. In response to the request, asset validation system 1004 may be configured to gather and validate data associated with the production of the chemical product, for example as described in the context of FIG. 13A, FIG. 13B, FIG. 16 and FIG. 17.

[0255] Data gathering unit 1210 may further be configured to initiate gathering of data associated with the production of the chemical product from a decentral network, such as the decentral network described in the context of FIG. 1 , based on the chemical product identifier(s) included in the ingested data and optionally based on decentral input material identifier(s) received from a decentral node as previously described. The gathering may be initiated by generating a request and providing said request to node 326. The request may include the chemical product identifier(s) associated with the chemical product and optionally decentral input material identifier(s) associated with input material(s) used to produce the chemical product. The request may be generated per chemical product. Node 326 may be configured to determine - based on identifier(s) included in the request - provider node(s) by querying node(s) of the decentral network providing lookup services to search for decentral participant identifier(s) and endpoint(s) of data provider(s) related to such decentral participant(s) based on chemical product identifier(s). Node 326 may be configured to determine the decentral chemical product identifier associated with the chemical product data. Node 326 may be configured to request access to input material data associated with the input material(s) and / or chemical product data associated with the chemical product from the determined provider node(s) based on the decentral input material identifier(s) and / or the decentral chemical product identifier. The gathered data may be provided by node 326 to data gathering unit 1210. The gathered data may be provided to a storage, such as passport archive 324, and data gathering unit 1210 may be configured to gather such data from such storage.

[0256] Data gathering unit 1210 may further be configured to gather an existing data completeness metric generated by data quality analyzer 1006 based on the chemical product identifier(s) included in the ingested data. Data gathering unit 1210 may be configured to request generation of a data completeness metric by data quality analyzer 1006 by sending a request to data quality analyzer 1006. The request may include the chemical product identifier(s) associated with the chemical product for which a data completeness metric is to be generated. In response to the request, data quality analyzer 1006 may be configured to generate and / or to provide such metric, for example as described in the context of FIG. 19 to FIG. 22.

[0257] Data gathering unit 1210 may provide the gathered data associated with the production of the chemical product and optionally the gathered data completeness metrics to passport generator 1212. Passport generator 1212 may be configured to generate chemical product passports associated with products and / or to update existing chemical product passports, such as chemical product passports stored in passport archive 324. Passport generator 1212 may be configured to generate and / or update the chemical product passports based on data received from data gathering unit 1210. The data received from data gathering unit 1210 may include a data completeness metric associated with the respective chemical product and validated data associated with the production of the chemical product. Validated data associated with the production of the chemical product may include the chemical product identifier(s) and optionally validated input material data associated with input material(s) used to produce the chemical product and / or validated chemical product data associated with the chemical product.

[0258] Passport generator 1212 may be configured to determine whether a chemical product passport is already existing in passport archive 324 for a chemical product associated with chemical product identifier(s) received from data gathering unit 1210. Passport generator 1212 may be configured to query passport archive 324 using chemical product identifier(s) received from data gathering unit 1310. If no chemical product passport is existing for such chemical product identifier(s) in passport archive 324, passport generator 1212 may be configured to generate a decentral identifier associated with the data associated with the production of the chemical product. Alternatively, passport generator 1212 may be configured to request such a decentral identifier from a decentral identifier provider. The decentral identifier provider may be part of chemical product passport generator 1008 (not shown). The decentral identifier provider may be associated with chemical product passport generator 1008.

[0259] Passport generator 1212 may be configured to gather a data model associated with the respective chemical product. The data model may be associated with a chemical product type associated with the respective chemical product. The data model may be stored in a database included in or associated with chemical product passport generator 1008 (not shown). Such database may include data model(s) and associated model identifier(s). The model identifier(s) may include chemical product type identifier(s). Passport generator 1212 may be configured to gather such data model based on the chemical product identifier(s) associated with the chemical product. A mapping table may be used to determine chemical product type identifier(s) based on the chemical product identifier(s) and such chemical product type identifier(s) may be used to gather the respective data model from the database.

[0260] Passport generator 1212 may be configured to generate passport data by applying the gathered data model to the data associated with the production of the chemical product received from data gathering unit 1210. Applying the data model to the data associated with the production of the chemical product may include transforming the data associated with the production of the chemical product according to such data model. The resulting chemical product passport may include the decentral identifier and one or more data point(s) defined according to the data model (e.g. passport data). The data points defined according to the data model may include the data described in the context of FIG. 3. Passport generator 1212 may be configured to provide the generated chemical product passport and optionally the associated data completeness metric to passport archive 324. Alternatively, passport generator 1212 may be configured to generate a data set by applying the gathered data model to the data associated with the production of the chemical product received from data gathering unit 1210 and to provide the generated data set to passport archive 324 for updating an existing chemical product passport associated with the chemical product. Passport generator 1212 may further provide an associated data completeness metric to passport archive 324.

[0261] Passport generator 1212 may further be configured to generate access policy data associated with the generated chemical product passport. Passport generator 1212 may be configured to generate the access policy data to passport archive 324 and / or to node 326. Generating access policy data may include

[0262] • generating group access data associated with the chemical product passport, the group access data identifying access control groups including data consumer identifier(s) associated with data consumer(s) permitted to access at the chemical product passport,

[0263] • generating consumer access data associated with one or more data point(s) present within the chemical product passport based on the generated group access data, the consumer access data identifying the data consumer(s) permitted to access the one or more data point(s) and one or more actions allowed to be performed on the one or more data point(s) by data consumer(s) associated with the data consumer identifier(s),

[0264] • generating access policy data associated with the chemical product passport based on the generated group access data and the generated consumer access data, the access policy data identifying the group access data and the associated consumer access data.

[0265] Alternatively, generating access policy data may include generating group access data associated with the chemical product passport, the group access data identifying access control groups including data consumer identifier(s) associated with data consumer(s) permitted to access at the chemical product passport.

[0266] Passport generator 1212 may further be configured to generate data package(s) including an indication that the chemical product passport has been generated or updated. A data package may be generated per generated or updated chemical product passport. The data package may include further data, such as a time stamp, a date stamp, the chemical product identifier(s) included in the chemical product passport, the decentral identifier included in the chemical product passport, an application identifier associated with the application requesting the production passport, an endpoint of the application requesting the chemical product passport or a combination thereof. The data package may represent a message or an event. The generated data package(s) may be provided to stream storage system 1502 as previously described.

[0267] A notification unit (not shown) may be connected to stream storage system 1202 and may be configured to generate a notification of generation and / or updating of chemical product passports and to provide such notification to the application requesting such chemical product passport. In response to receiving such notification, data refresher 1220 of application 1214 may be configured to gather the chemical product passport from passport archive 324 and to provide such gathered chemical product passport. Providing may include providing such chemical product passport for storage in local db 1222. Proving such gathered chemical product passport may include providing the passport for display within a graphical user interface of application 1214. Local db 1222 may store chemical product identifier(s) associated with a date indicating when passport archive 324 was queried last for such chemical product identifier(s), the chemical product passport and generation date of the chemical product passport.

[0268] FIG. 13A illustrates a block diagram of an example system for validating data associated with the production of a chemical product. The chemical product may be a chemical product as described in the context of FIG. 3. The chemical product may be produced from one or more input material(s) by a production chain. The input material(s) may correspond to output chemical product(s) or intermediate chemical product(s) produced by participants of the production chain. The production chain may include one or more production step(s) as described in the context of FIG. 3. Data associated with the production of the chemical product may include input material data (e.g. input material assets) associated with input materials used to produce the chemical product. Data associated with the production of the chemical product may further include chemical product data (e.g. chemical product asset) associated with the chemical product. The system illustrated in FIG. 13A may be configured to perform the methods illustrated in FIG. 15 to FIG. 17.

[0269] Asset validation system 1004 may include data transfer service 1302, stream storage system 1312 and data transforming unit 1304. Various databases, such as rule DB 1306, archive general 1318 and archive DPP product type A 1320 may be connected to data transforming unit 1304.

[0270] Validation of data associated with the production of the chemical product may be initiated by a request to asset validation system 1004. With reference to FIG. 17, the request may be received at data transfer service 1302. The request may include the asset identifier(s) and associated data source data. With further reference to FIG. 3, the request may be generated in response to receiving an indication of a user to generate the chemical product passport for the chemical product. The user indication may trigger gathering of asset identifier(s) and associated data source data from registry 1010 based on the chemical product identifier(s) included in the user indication. The gathered data may be used to generate the request to asset validation system 1004.

[0271] The asset validation system 1004 may be connected to a decentral data consuming node, such as consumer node 326. The decentral data consuming node may be part of a decentral network, such as decentral network 134 described in the context of FIG. 1. The decentral data consuming node 326 may be associated with a decentral participant. The decentral participant may be a participant of the chemical product ecosystem associated with the chemical product. The decentral participant may not be a participant of the chemical product ecosystem, e.g. may be a service provider generating chemical product passports on behalf of a participant of the chemical product ecosystem. With reference to FIG. 9, decentral data consuming node 326 may be configured to request access to data associated with the production of the chemical product at provider node(s) associated with such data. The request may include the identifier associated with the respective data (e.g. asset) and a decentral participant identifier associated with the decentral participant operating consumer node 326. The request may be generated in response to data received from the system, for example received from data transfer service 1302. The data received from the system may include the asset identifier(s) and associated access data pointing to decentral provider node(s), such as provider node(s) 116, 118 and 128. The access data may include endpoint(s) associated with the decentral provider node(s), such as URI(s). The request may be generated per asset identifier and associated access data. The request received by the respective provider node(s) may be authenticated. Such authentication may be based on data related to an authentication mechanism. The authentication mechanism may be based on certificate(s) and / or token(s), for example a device certificate (X.509v3), a TLS connection certificate (X.509v3) and a ‘Dynamic Attribute Token’ (OAuth Access Token), associated with the respective decentral participant nodes, e.g. consumer node 332 and provider node(s), such as nodes 116, 118 and 128. If authentication fails, no output chemical product data set(s) may be provided by respective data provider(s).

[0272] Provider node(s), such as nodes 116, 118 and 128, receiving the request may initiate data transaction(s) according to a transaction protocol with consumer node 326. Provider node(s) may provide a data set including one or more data usage rule(s) associated with the decentral identifier(s). The data set may be provided to asset validation system 1004. The asset validation system 1004 may parse the received data set to determine the data usage rule(s). The determined rule(s) may be provided to a user for consent. The asset validation system 1004 may be configured to automatically accept such data set(s) provided by predefined provider node(s). The asset validation system 1004 may provide data being indicative of the signature, such as a token including the identifier associated with the data set and proof data (e.g. an electronic signature), to consumer node 326. If the rule(s) are not accepted, the asset validation system 1004 may likewise forward data being indicative of declining the data usage rule(s) included in the data set to consumer node 326. Consumer node 326 may forward this data to the provider node(s). Upon declining the data usage rule(s), provider node(s) may terminate the connection and may not provide any assets. Use of the data set including data usage rule(s) ensures that the consumer node 326 and further systems handling the data are complying to at least one data usage rule associated with the provided assets. This may ensure that the assets may be exchanged in a secure and controlled manner, hence avoiding access to assets by unauthorized decentral network participants while allowing to provide the assets to decentral network participants required to use such provided assets, for example to generate chemical product passports associated with the products produced from input materials associated with such assets.

[0273] With continued reference to FIG. 9, data provider(s) may provide assets associated with identifier(s) included in the request received from consumer node 326 upon acceptance of the usage rule(s). The assets may be gathered from a dedicated storage, such as assets DB 404 as described in the context of FIG. 4A and FIG. 6, by the data provider(s) and provided via the peer-to-peer network to consumer node 326.

[0274] Returning to FIG. 13A and with continued reference to FIG. 17, consumer node 326 may provide the received asset(s) to data transfer service 1302. Data transfer service 1302 may be connected to stream storage system 1312. Stream storage system 1312 may be connected to data transforming unit 1304. Data transforming unit 1304 may be positioned upstream from data transfer service 1302. Asset(s) gathered via the decentral network may flow through data transfer service 1302 and stream storage system 1312 to data transforming unit 1304.

[0275] Data transfer service 1302 may be configured to receive of asset(s) from consumer node 326. The asset(s) may represent a stream of data. Such a stream may be an ordered sequence of records received from consumer node 326 relatively continuously, i.e. not in accumulated batches or chunks. A record may for example comprise input material data (e.g. an asset) associated with a given input material via an input material identifier. A record may be in a tabular representation. A record maybe in an object representation, e.g. using JSON, an XML document. A record may be defined as data that can be delivered continuously in small chunks or increments. The records may or may not be time-ordered. Data transfer service 1302 may be configured to generate data package(s) including the asset(s) received from consumer node 326. A data package may be generated per received asset. The data package may include further data, such as a time stamp, a date stamp, the input material identifier associated with the asset, the decentral participant identifier associated with the provider node, location data pointing to the dedicated storage storing the asset or a combination thereof. The data package may represent a message or an event. The generated data package(s) may be provided to stream storage system 1312.

[0276] Stream storage system 1312 may be configured to store data packages received (e.g. pushed) from data transfer service 1302. The stream storage system 1312 may be configured to provide the stored data to data transforming unit 1304. The stream storage system 1312 may be configured to provide the stored data to data consuming unit 1308 of data transforming unit 1304. Stream storage system 1312 may comprise one or more persistent or non-persistent logs 1314, 1316. In this embodiment, stream storage system 1312 comprises two persistent or non-persistent logs 1314, 1316 (i.e. log 1 1314 and log 2 1316). Records stored in said logs may be ordered, for example by using IDs. This allows to identify a record within a specific log. A record may include a data package generated by data transfer service 1302.

[0277] Stream storage system 1312 may provide a streaming service or stream processing service between one or more streaming sources (e.g. data transfer service 1302) and one or more streaming sinks (e.g. log 1 1314 and log 2 1316). Stream storage system 1312 may act as a persistent or non-persistent stream sink for input material data set(s) received from consumer node 326. For example, open-source software systems such as Apache Kafka ("Kafka") or Azure Event Hubs may act as a persistent stream sink. Stream storage system 1312 may be configured to pull data package(s) from data transfer service 1302. For instance, stream storage system 1312 may be configured to request data package(s) from data transfer service 1302 at regular time intervals.

[0278] Stream storage system 1312 may be configured to determine if the received or pulled data package(s) is / are already contained in the one or more persistent or non-persistent logs. If said data package(s) is / are already contained in the one or more persistent or non-persistent logs, stream storage system 1312 may not store the received or pulled data package(s) in said logs. If said data package(s) is / are not contained in one or more persistent or non-persistent logs or is an update, stream storage system 1312 may be configured to store the received or pulled data package(s) in the one or more persistent or non- persistent logs or to update data package(s) present in the persistent or non-persistent log(s) with the received or pulled updated data package(s). This may avoid that the same input data package(s) is / are stored multiple times in the persistent or non-persistent log(s), hence avoiding redundant validation operations on the data package(s) stored in stream storage system 1312.

[0279] Data transforming unit 1304 may be connected to the stream storage system 1312. Data consuming unit 1308 of data transforming unit 1304 may be connected to stream storage system 1312. Data consuming unit 1308 may be connected to one or more persistent or non-persistent logs (e.g. in this embodiment in log 1 1314 and log 2 1316) of stream storage system 1312 to ingest and process data package(s) stored within the log(s). The stream storage system 1312 may be in a publisher-subscriber relationship with the data consuming unit 1308. For instance, data in one or more the logs(s) may be periodically read (e.g. pulled) by data consuming unit 1308. To avoid consumption of a data package stored in a log several times, such data package may be marked as consumed by stream storage system 1312. To avoid consumption of a data package stored in a log several times, an integer indicating the offset of the next data package to consume may be used. Such integer may be just one number for each persistent or non- persistent log. Such integer may be periodically checkpointed. Use of such an integer may allow data consuming unit 1308 to re-consume data packages by rewinding the integer to an old offset.

[0280] Data consuming unit 1308 may be connected to data validation unit 1310 of data transforming unit 1304. Data consuming unit 1308 may be configured to provide data packages gathered from stream storage system 1312 to data validation unit 1310 for validation of data included in said data packages. Data consuming unit 1608 may be configured to extract data from the data packages and provide the extracted data including an input material identifier or chemical product identifier to data validation unit 1310. Data validation unit 1310 may be configured to validate the extracted data based on one or more rule(s) retrieved from rule DB 1306, for example as described in the context of FIG. 13B. Validation may include applying one or more rule(s) retrieved from rule DB 1306 to the extracted data. The extracted data may be validated if at least a part of the applied rules is fulfilled. Applying the rule(s) to the extracted data may include comparing the combination of identifier and location data to a database storing such combinations of identifier(s) and associated location data. Applying the rule(s) to the extracted data may include comparing data point(s) present within one or more rule(s) to individual data point(s) present within the extracted data to be validated. Applying the rule(s) to the extracted data may include comparing data point combination(s) defined in the rule(s) to data point combination present within the extracted data to be validated. Applying the rule(s) to the extracted data may include comparing the data defined in one or more rule(s) to the whole extracted data to be validated. The one or more rule(s) may be related to a data model associated with a chemical product passport associated with the chemical product. The data model may define data points to be included in the chemical product passport. Data type(s) and associated value(s) and / or value range(s) included in the data model may be included in the one or more rule(s). This may allow to verify whether gathered data fulfils the data type(s) and associated value(s) and / or value range(s) defined by the data model. By validating the extracted data against one or more rule(s) generated based on the data model, the number of validated data points (e.g. data points included in the asset and matching data points defined by the data model) included in the gathered asset can be determined. This may allow to determine a data completeness metric by comparing the number of validated data points to the number of data points defined by the data model.

[0281] In an embodiment, data validation unit 1310 may further be configured to determine the archive to which the validated data is to be persisted. The archive may be determined based on mapping data including a mapping between identifier(s) and associated archive data. The archive data may include endpoint(s) associated with said archive(s). The archive(s) may be identified by way of archive identifier(s) included in the archive data. Such identifier(s) may be used to gather endpoint(s) associated with such archive(s). The mapping data may include a first mapping between input material identifiers and input material type identifiers and a second mapping between input material type identifiers and associated archive data. The mapping data may further include a first mapping between chemical product identifiers and chemical product type identifiers and a second mapping between chemical product type identifiers and associated archive data. The mapping data may be stored in a database connected to data validation unit 1610 (not shown). Determining the archive of validated input material data may allow to persist validated data in archives associated with given applications or systems(s). For instance, the validated data associated with a given chemical product may be persisted in an archive associated with a given application processing such validated data, such as chemical product passport service 328. Processing may, for example include generation of data completeness metrics, generation of chemical product passports and / or updating of chemical product passports using such validated data, for example as described in the context of FIG. 18 and FIG. 22. Validated data which may not be mapped to a given application may be persisted in a general archive, such as archive general 1318.

[0282] Data validation unit 1310 may further be configured to provide the validated data to the determined archive, such as general archive general 1318 or archive DPP chemical product type A 1320, for storage.

[0283] Data validation system may hence allow to validate gathered data associated with the production of the chemical product with respect to a data model associated with a chemical product passport of such chemical product. This way, it can be determined how many data points included in the gathered data match data points defined by the data model. This allows to determine the degree of completeness of the gathered data associated with the production with respect to data defined by the data model by comparing the number of validated data points to the number of data points defined by the data model. This way, transparency on the degree of correlation between the accessible and validated data points and the data points defined by the data model and hence also transparency on the degree of completeness of the passport data generated by applying the data model to the validated data can be achieved.

[0284] FIG. 13B illustrates a diagram showing an example of validating data associated with the production of a chemical product using a rule-based engine included in the data validation unit 1610 described in the context of FIG. 13A.

[0285] Data validation unit 1310 may include rule based engine 1324. The rule based engine 1324 may operate on individual data point(s), multiple data point(s) and / or the gathered data. The rule based engine 1324 may operate on data gathered per identifier individually. This allows to validate gathered data per input material or per chemical product, hence allowing a more granular validation of the gathered data. Rulebased engine 1324 may receive a request to validate gathered data. The request may contain at least a part of the gathered data. Data packages (e.g. messages or events) may be consumed from one or more log(s) of stream storage system 1312 (see operation 1340) by data consuming unit 1308 as described in the context of FIG. 13A. The consumed data packages may be extracted by data consuming unit 1308 (see operation 1646). The extracted identifier may be provided to rule-based engine 1324. The rule based engine 1324 may have access to one or more rule(s). The rule-based engine 1324 may include one or more rule(s). The one or more rule(s) may be present within a rule template. The one or more rule(s) and / or the rule template(s) may be stored in a data storage, such as rule DB 1306. The one or more rule(s) or rule template(s) may be provided to rule DB 1306 by a user. The one or more rule(s) may correspond to unstructured data associated with validation operation(s). The rule template(s) may include unstructured data associated with instructions related to validation operation(s). The one or more rule(s) or the rule template may be included in a file provided by the user. The one or more rule(s) or the rule template(s) may be associated with input material type identifier(s) and / or input material identifier(s). The one or more rule(s) or the rule template(s) may be associated with chemical product type identifier(s) and / or chemical product identifier(s). Rule-based engine 1324 may generate a request to obtain one or more rule(s) from rule DB 1306. The request may contain the respective input material identifier(s) or chemical product identifier(s).

[0286] One or more rule(s) associated with the data to be validated (e.g. one or more applicable rule(s)) may be provided to rule-based engine 1324 in response to the request. The one or more rule(s) may define data point(s) and / or combination(s) of data point(s) to be present within the consumed data. The one or more rule(s) may be associated with chemical product(s) produced from the input material associated with the input material data to be validated. The one or more rule(s) may be associated with or derived from a data model associated with a chemical product passport of the chemical product. Hence, the one or more rule(s) may ensure that data point(s) associated with input material(s) and the chemical product and being defined according to the data model may be included in the consumed data. The one or more rule(s) may relate to mandatory data point(s) defined by the data model. The one or more rule(s) may be generated based on the mandatory input material data point(s) present within the data model. This may ensure that mandatory data defined by the data model is included in the consumed data. The one or more rule(s) may be associated with input material identifier(s) and / or input material type identifier(s). The one or more rule(s) may be associated with chemical product identifier(s) and / or chemical product type identifier(s). A mapping table may be used to map input material identifier(s) to corresponding input material type identifier(s) and / or to map chemical product identifier(s) to corresponding chemical product type identifier(s). The input material type identifier(s) may be associated with input material type(s). The chemical product type identifier(s) may be associated with chemical product type(s). The mapping table may be stored in a separate database (not shown). Rule-based engine 1324 may be configured to gather input material type identifier(s) based on determined input material identifiers) and to request rule(s) based on the gathered input material type identifier(s). Rule-based engine 1324 may further be configured to gather chemical product type identifier(s) based on determined chemical product identifier's) and to request rule(s) based on the gathered chemical product type identifier(s). This may allow to gather rule(s) associated with input material type identifier(s) and / or chemical product identifier(s) based on respective input material identifier(s) and / or chemical product identifier(s), hence avoiding generation of rule(s) per identifier and reducing the number of rule(s) that need to be generated, stored and maintained in rule DB 1306.

[0287] Rule-based engine 1324 may be configured to initialize the rule engine (see operation 1328). Initialization of the rule engine may include generating rule data executable by a processor included in rule based engine 1324. The rule data may include or correspond to executable logic. This may allow to transform rule(s) or rule template(s) present in unstructured data form into code that can be executed by the processor. Execution of the code may result in applying the executable rule data to the extracted input material data (see operation 1630) to validate the consumed data according to the obtained rule(s). Execution of the logic may result in matching consumed data to data point(s) and / or combination(s) of data point(s) included in the executable logic, evaluating the consumed data with such data point(s) or combination(s) of data point(s) and generating validation result data based on the evaluation results. The validation result data may include a classifier and associated validated or non-validated data point(s). The classifier may be a binary classifier discriminating between validated and non-validated data. Consumed data point(s) may be considered validated if one or more rule(s) applied by rule-based engine 1324 are fulfilled. Applying the rule(s) to the consumed data may include comparing individual data point(s) present within the rule(s) to individual data point(s) present within the data to be validated to determine whether the data to be validated includes individual data point(s) required by such rule(s). Applying the rule(s) to the consumed data may include comparing data point combination(s) defined in the rule(s) to data point combination present within the data to be validated to determine whether the data contains data point combinations required by such rule(s). Applying the rule(s) to the consumed data may include comparing the data defined in the rule(s) to the whole data set to be validated to determine whether the data set contains all data required by such rule(s). Operations performed by rulebased engine 1324 may be determined by rule(s) gathered from rule DB 1306. For instance, rule(s) gathered from rule DB 1306 may determine whether rule-based engine 1324 operates on individual data point(s) and / or multiple data point(s) of the consumed data and / or the whole data set(s).

[0288] Rule-based engine 1324 may be configured to determine whether the consumed data fulfils one or more applied rule(s) (see operation 1332). Consumed data may not be validated or only partially validated (e.g. validation may result in at least one error associated with applying one or more obtained rule(s) to the consumed data) if the consumed data does not include data point(s) required according to one or more obtained rule(s). Rule-based engine 1324 may indicate to data validation unit 1310 successful validation of the consumed data responsive to the determination that the consumed data is successfully validated (e.g. fulfils one or more obtained rule(s)). In response to receiving that indication, data validation unit 1310 may determine the target archive where the validated data is to be persisted (see operation 1342). The target archive may be determined as described in the context of FIG. 13A. If data validation unit 1310 determines that the validated data is not associated with a given application, data validation unit 1310 may provide the validated data to an archive not being associated with any application or service processing the validated data, such as archive general 1320. If data validation unit 1310 determines that the validated data is associated with a given application or service processing such data, for example chemical product passport service 322, data validation unit 1310 may provide the validated data to a storage being associated with such application or service processing the validated data stored therein, for example by generating data completeness metrics and / or by generating and / or updating chemical product passports.

[0289] If at least a part of the consumed data could not be validated, rule-based engine 1324 may indicate to data validation unit 1310 that at least a part of the consumed data could not be validated. In response to receiving the indication, data validation unit 1310 may generate message data (operation 1334). The message data may indicate that at least part of the consumed data could not be validated. The message data may include an indication which data point(s) of the consumed data could not be validated. The message data may be provided to a display device configured to display data received from data validation unit 1310. The display device may comprise a graphical user interface 1336. The display device may display the message in response to receiving message data from rule based engine 1324. This allows to trigger correction or updating of non-validated data points, for example by generating a request to provide updated data point(s) to the data source having provided the non-validated data points.

[0290] Rule-based engine 1324 may be configured to provide non-validated data to an archive not being associated with any application processing the validated data, such as archive general 1318. The nonvalidated data may be provided to such storage along with a classifier classifying such data as non- validated. The non-validated data may be provided to such archive along with the classifier and rule data indicating the applied rule(s) resulting in non-validation of at least a part of such data.

[0291] FIG. 14 illustrates an example of a method for generating a chemical product passport associated with a chemical product. The chemical product may be a chemical product as described in the context of FIG. 3. The chemical product may be produced from one or more input material(s) by a production chain. The production chain may include one or more production step(s) as described in the context of FIG. 3. The method illustrated in FIG. 14 may be implemented by the system described in the context of FIG. 12. The chemical product passport may include one or more decentral identifier(s) and passport data as described in the context of FIG. 3.

[0292] Data associated with the chemical product may be provided. Data associated with the chemical product may include one or more chemical product identifier(s). The chemical product identifier(s) may be digital chemical product identifier(s). The chemical product identifier(s) may include a chemical product name, a chemical product number, a LOT number, a batch number, a serial number, a chemical product type, an identification number or a combination thereof. Data associated with the chemical product may further include one or more input material identifier(s) associated with input material(s) used to produce the chemical product. The chemical product identifier(s) may be provided from a code reader configured to read a physical code connected to the chemical product and to determine the digital chemical product identifier(s) encoded in the code. The chemical product identifier(s) may be provided from a device configured to acquire image data and to determine the chemical product identifier(s) based on the acquired image data.

[0293] Validated data associated with the production of the chemical product may be gathered based on provided data associated with the chemical product. Gathering validated data may include determining one or more input material identifier(s) associated with input material(s) used to produce the chemical product based on the provided data associated with the chemical product. The input material identifier(s) may be determined from relationship representation(s) indicating relationships between the chemical product identifier(s) associated with the chemical product and input material identifier(s) of input material(s) used to produce the chemical product. The relationship representation(s) may be stored in a database, for example in registry 1010 as described in the context of FIG. 10, FIG. 11 B and FIG. 12. The validated data may be gathered from a storage storing such data. The storage may be associated with the entity generating the chemical product passport. The storage may be associated with the system generating the chemical product passport, for example as described in the context of FIG. 12. The validated data may be gathered from one or more storages storing such validated data, for example the archives as described in the context of FIG. 13A and FIG. 13B.

[0294] With reference to FIG. 15, the validated data may be generated by gathering data associated with the production from a decentral network based on the provided data associated with the chemical product, such as chemical product identifier(s) included in such provided data. With further reference to FIG. 16, gathering the data associated with the production of the chemical product may include providing data associated with data sources indicating data accessible for generating and / or updating chemical product passports. The data may be provided by providing a database storing such data associated with data sources indicating data accessible for generation and / or updating of chemical product passports. The database may be a database as described in the context of FIG. 10 and FIG. 11A (e.g. registry 1010). The data associated with data sources may include data set identifiers (also denoted as asset identifiers hereinafter) associated with data sets (also denoted as assets hereinafter) including data associated with the production of the chemical product and data sources data indicating the data sources associated with such data set identifiers. The data sets may include input material data associated with input material(s) used to produce the chemical product and / or chemical product data associated with the chemical product. Data source data may include endpoints associated with such data sources. Data source data may further include a decentral participant identifier related to the data source and / or a participant role associated with the participant of the chemical product ecosystem being associated with or controlling the data source. Data sources may include network node(s) configured to provide data, such as data accessible for generating and / or updating the chemical product passports, upon request of a further network node (e.g. a consumer node), for example as described in the context of FIG. 3, FIG. 9 and FIG. 13A. The data sources may be associated with a dedicated storage storing the provided data, for example as described in the context of FIG. 4A and FIG. 5. The data sources may be configured to exchange data based on a transaction protocol including authentication and / or authorization mechanism(s) as described in the context of FIG. 9 and FIG. 13A. The data associated with data sources may further include relationships between chemical product identifier(s) and associated input material identifier(s). The relationships may indicate the input material identifier(s) associated with a given chemical product identifier, for example as described in the context of FIG. 11 B. Use of such relationship representation(s) allows to efficiently determine provider node(s) associated with the input material data and optionally chemical product data based on given chemical product identifier(s), hence resulting in a reduced latency associated with the gathering of the input material data and optionally the chemical product data. This way, data associated with the production of the chemical product may be efficiently validated and the validated data may be processed, for example by generating and / or updating chemical product passports.

[0295] The data associated with data sources may be provided by providing a database storing such data associated with data sources indicating data accessible for generating and / or updating chemical product passports. The database may be a database as described in the context of FIG. 10, FIG. 11A and FIG. 12 (e.g. registry 1010).

[0296] Based on such data associated with data sources indicating data accessible for generating and / or updating chemical product passports and the provided data associated with the production, target data sources may be determined. Determining target data sources may include determining input material identifier(s) based on the chemical product identifier(s) included in the provided data associated with the chemical product. The input material identifier(s) may be determined by querying the data associated with the data sources using the provided data associated with the chemical product. Data source data associated with target data sources matching the chemical product identifier included in the data associated with the chemical product may be determined from such data associated with the data sources. In addition or alternatively data source data associated with target data sources matching the determined input material identifier(s) may be determined from such data associated with the data sources.

[0297] The data source data associated with such target data sources data may be parsed to determine endpoint(s) and decentral participant identifier(s) associated with such target data sources (e.g. provider node(s) associated with dedicated storage(s) storing input material data associated with provided input material identifier(s) or storing chemical product data associated with the provided chemical product identifier).

[0298] With continued reference to FIG. 16, the data associated with the production of the chemical product may be gathered from determined target data sources based on the determined data source data and the determined and / or provided identifiers. The data associated with the production of the chemical product may be gathered as described in the context of FIG. 9 and FIG. 13A. The respective data may be provided by the target data sources in response to receiving a requests for access to such data, for example as described in the context of FIG. 9 and FIG. 13A.

[0299] Returning to FIG. 15, the gathered data associated with the production may be validated using a rulebased engine including one or more rule(s) related to a data model associated with the chemical product passport. Data model associated with the chemical product passport may refer to the data model used to generate the chemical product passport. The rule-based engine may be a rule-based engine as described in the context of FIG. 13B. The gathered data may be validated by data validation unit 1310 described in the context of FIG. 13A and FIG. 13B. The applicable rule(s) may be identified based on an identifier associated with each applicable rule matching or being related to an identifier included in the extracted data, such as input material data and / or chemical product data provided by the data source(s). The identifier associated with each applicable rule may include an identifier matching the identifier included in the extracted data. The identifier associated with each applicable rule may include a type identifier related to the identifier included in the extracted data. The type identifier related to the identifier included in the extracted data may be determined based on mapping data as described in the context of FIG. 13B. Executable logic may be generated from the one or more applicable rule(s). The executable logic may be generated by data validation unit 1310. Executable logic may include machine code, interpretable code, bytecode, and / or code that runs on a virtual machine. The logic included in the applicable rule(s) may be encoded in the executable logic. The logic included in the applicable rule(s) may be mirrored in the executable logic. Upon finalizing the generation of the executable logic, data validation unit 1310 may sent a response to data consuming unit 1308 indicating finalizing the generation of the executable logic. Extracted data, such as input material data and / or chemical product data, may be provided to data validation unit 1310 by data consuming unit 1308 in response to receiving an indication that the generation of the executable logic has been finalized. The extracted input material data may be validated by executing the generated executable logic. The executable logic may be subject to rule execution criteria. Data consuming unit 1308 may sent a request to data validation unit 1310 to transform the extracted input material based on the executable logic generated for the applicable rule(s). Rule execution criteria may include rule execution order, exemptions and conditions. Validation data including the result of the validation may be generated by the rule engine. The validation data may include the input material data points subject to the validation process and associated classifiers. The classifiers may indicate whether the respective input material data point passed or failed the validation process. The validation data may further include rule data associated with data point(s) for which validation failed. The rule data may indicate the applied rule(s) which resulted in a fail of the validation of such data point. By validating the gathered data by a rule-based engine including one or more rule(s) associated with the chemical product, data completeness metrics may be generated since validation allows to determine which data points defined by the data model are included in the gathered data. By validating the gathered data at the consumer side, the provider side may not be required to generate the gathered data using complex data models.

[0300] With continued reference to FIG. 15, it may be verified whether the extracted data could be validated according to one or more applicable rule(s) (e.g. one or more rule(s) gathered from rule DB 1306). If the extracted data could be validated according to the applicable rule(s), e.g. application of such rule(s) did not result in any error, the validated data may be linked to the chemical product identifier(s) and / or may be provided. Linking the validated data to the chemical product identifier(s) allows to gather the validated data based on at least one of the chemical product identifiers, for example upon generating and / or updating the chemical product passport. Providing the validated data may include providing the validated data to an archive for storage (see also FIG. 13A and FIG. 13B). Providing the validated data may include providing the validated data for generating and / or updating the chemical product passport.

[0301] If only a part of the extracted data could be validated, message data may be generated, for example as described in the context of FIG. 13B. The validated and the non-validated data may be provided to an archive as previously described.

[0302] If the extracted data could not be validated, message data may be generated, for example as described in the context of FIG. 13B. The non-validated data may be provided to an archive, for example as described in the context of FIG. 13B.

[0303] Returning to FIG. 14, data associated with the production of the chemical product may be data gathered via a decentral network from one or more provider node(s) associated with such data. This step may be generally optional. This step may be performed if validated data is not available for the chemical product identifier(s) associated with the chemical product and / or input material identifier(s) associated with input material(s) used to produce the chemical product. The decentral network may be a decentral network as described in the context of FIG. 1 . The provider node(s) may be determined using a decentral discovery service configured to provide decentral participant identifiers related to provider node(s) and endpoints associated with such provider node(s). The decentral discovery service may be part of the decentral network. The decentral discovery service may not be associated with or operated by a participant of the chemical product ecosystem. The decentral discovery service may not be operated on behalf of a participant of the chemical product ecosystem. The decentral discovery service may not be part of a chemical product passport service including the chemical product passport generator, such as chemical product passport service 422 described in the context of FIG. 4 and FIG. 10. Based on the provided endpoints, decentral identifier(s) associated with data provided by such provider(s) and matching the chemical product identifier(s) or the input material identifier(s) may be determined. Using the determined decentral identifier(s), data associated with such decentral identifier(s) may be gathered from the provider node(s) via the decentral network, for example as described in the context of FIG. 9. Gathering data associated with the production of the chemical product from the decentral network in addition to gathering the validated data allows to increase the degree of completeness of the passport data included in the chemical product passport.

[0304] A completeness of data available for generating and / or updating the chemical product passport may be validated. This step may be generally optional. Data available for generating and / or updating the chemical product passport may include the validated data and optionally the data gathered in block 1406. Validating the completeness of the available data may include generating a data completeness metric. The data completeness metric may be generated if such metric is to be provided along with the generated chemical product passport. The data completeness metric may be generated as described in the context of FIG. 19 to FIG. 22. The data completeness metric may indicate the degree of correlation between the validated data and optionally the data gathered in block 1406 and the data points defined by the data model associated with the chemical product passport (e.g. the data model used to generate the chemical product passport), for example as illustrated in FIG. 21 A to FIG. 21 C.

[0305] A decentral identifier associated with the gathered data may be provided. The decentral identifier may be a decentral identifier as described in the context of FIG. 3. The decentral identifier may be provided as described in the context of FIG. 12. A data model associated with the chemical product passport may be provided. The data model may be provided as described in the context of FIG. 12.

[0306] A chemical product passport may be generated by applying the data model to the validated data and optionally to the data gathered in block 1406. Applying the data model to the validated data and optionally to the data gathered in block 1406 may result in passport data having a semantic structure as defined by the data model. The generated chemical product passport may include the decentral identifier and the passport data. The passport data may include the chemical product identifier. The passport data may further include chemical and / or physical property Zies of the chemical product as described in the context of FIG. 3.

[0307] Generating the chemical product passport may further include generating access policy data associated with the generated chemical product passport. The access policy data and / or the group access data may be linked to the chemical product passport, for example via the decentral identifier(s) and / or the chemical product identifier. This way, the access policy data and / or the group access data may be obtained based on one of the decentral identifier(s) and / or the chemical product identifier. The access policy data may be generated by

[0308] • generating group access data associated with the chemical product passport, the group access data identifying access control groups including data consumer identifier(s) associated with data consumer(s) permitted to access at the chemical product passport,

[0309] • generating consumer access data associated with one or more data point(s) present within the chemical product passport based on the generated group access data, the consumer access data identifying the data consumer(s) permitted to access the one or more data point(s) and one or more actions allowed to be performed on the one or more data point(s) by data consumer(s) associated with the data consumer identifier(s),

[0310] • generating access policy data associated with the chemical product passport based on the generated group access data and the generated consumer access data, the access policy data identifying the group access data and the associated consumer access data.

[0311] The group access data includes a gathering of one or more data consumer identifier(s) associated with the data consumer(s) permitted to access the chemical product passport.

[0312] By filtering data consumer(s) requesting access to the chemical product passport based on a group- based policy for accessing the chemical product passport, the chemical product passport can be securely exchanged and shared under the sovereignty of the data owner of the chemical product passport and unauthorized access to the chemical product passport can be avoided. This allows for controlled access to the chemical product passport or parts thereof by participants of the chemical product ecosystem, such as upstream participants of the chemical product producer, the passport generator or the entity on behalf of which the passport is generated. Moreover, access to the chemical product passport or a part thereof by multiple data consumers can be controlled by the data owner using the group-based policy and the decentral identifier(s) included in the chemical product passport. Use of a group-based access in combination with fine-grained access controls on data point level allows to avoid the generation of multiple copies of the chemical product passport customized to the access rights associated with each data consumer permitted to access the chemical product passport. Hence, the amount of data associated with the chemical product passport may be reduced since access may be controlled on data point level of the chemical product passport, making generation of multiple copies of the chemical product passport redundant. The generated chemical product passport and optionally the data completeness metric may be provided for access, for example as described in the context of FIG. 12. This way, users accessing the chemical product passport can determine the reliability of the passport data using the data completeness metric. The generated chemical product passport may be provided for access under control of the data owner of the chemical product passport. The data owner may be the entity generating the chemical product passport. The data owner may be the entity producing the chemical product. The data owner may be the entity producing a further chemical product using the chemical product. The chemical product passport may be provided for access via a decentral network. The chemical product passport may be provided for access as described in the context of FIG. 12 under control of the data owner of the chemical product passport. Control of access to the chemical product passport may allow secure exchange of passport data with entities using the chemical product while avoiding unauthorized access to such data by entities not being involved in the use of the chemical product, for example by using the chemical product to produce further products and or by recycling the chemical product or a part thereof.

[0313] Providing the chemical product passport may include generating an access element associated with the chemical product passport and providing the access element to a decentral registry for storage. The access element may include the decentral identifier and access data pointing the storage location of the chemical product passport. The decentral registry may be associated with the data owner of the chemical product passport. Access to the decentral registry may be controlled by the data owner of the chemical product passport. This way, access to the decentral registry and query of the decentral registry may be controlled by the data owner and only authorized participants of the decentral network may be allowed to query and access such registry to see the data offer indicated by such decentral registry of the data owner.

[0314] By generating the chemical product passport based on data validated according one or more rule(s) related to a data model associated with the chemical product passport, it can be ensured that the data points defined according to the data model are included in the validated data. This avoids incomplete, false and / or missing data present within the data associated with the production of the chemical product and hence missing data points present within the passport data of the chemical product passport. This way, a higher data quality of the passport data can be ensured, allowing to generate chemical product passports having an improved reliability since the passport data is associated with a higher degree of completeness.

[0315] By generating and providing a data completeness metric indicating the degree of completeness of the passport data with respect to the data defined by the data model used for its generation, a stream of chemical products associated with the chemical product passports to a downstream production using the chemical products to produce one or more further product(s) can be monitored and / or controlled. This way, a more efficient and reliable production of the further products based on data included in the chemical product passports can be ensured. FIG. 18 illustrates an example of a method for updating a chemical product passport associated with a chemical product. The chemical product may be a chemical product as described in the context of FIG. 3. The chemical product may be produced from one or more input material(s) by a production chain. The production chain may include one or more production step(s) as described in the context of FIG. 3. The method illustrated in FIG. 19 may be implemented by the system described in the context of FIG. 12. The chemical product passport may include a decentral identifier and passport data as described in the context of FIG. 2.

[0316] Data associated with the chemical product may be provided. Data associated with the chemical product be provided as described in the context of FIG. 15.

[0317] A chemical product passport including a decentral identifier and passport data may be provided. The passport data may include one or more chemical product identifier(s) associated with the chemical product. Providing the chemical product passport may include providing an archive or data storage storing the chemical product passport. The chemical product passport stored in the archive or data storage may be generated by the system described in the context of FIG. 12. The chemical product passport may be generated as described in the context of FIG. 15. In one embodiment, the passport data may further include at least one measured and / or determined chemical and / or physical property of the chemical product and / or input material(s) used to produce the chemical product, for example as described in the context of FIG. 3. In another embodiment the passport data may only include the chemical product identifier(s) (e.g. may be an “empty passport” in terms of data defined by the data model apart from the chemical product identifier(s)). Empty passports may be generated if data associated with the production of the chemical product may not be accessible or available upon generation of the chemical product passport or if only the chemical product identifier(s) are available or accessible upon generation of the chemical product passport. Block 1804 may be performed at any time after block 1802 and before block 1808.

[0318] Validated data associated with the production of the chemical product may be gathered based on provided data associated with the chemical product. The validated data may be gathered as described in the context of FIG. 15. The validated data may be generated as described in the context of FIG. 15.

[0319] Data associated with the production of the chemical product may be data gathered via a decentral network from one or more provider node(s) associated with such chemical product, this step being generally optional. The data may be gathered as described in the context of FIG. 15.

[0320] A completeness of data available for generating and / or updating the chemical product passport may be validated. This step may be generally optional. Data available for generating and / or updating the chemical product passport may include the validated data and optionally the data gathered in block 1406. Validating the completeness of the available data may include generating a data completeness metric. The data completeness metric may be generated if such metric is to be provided along with the generated chemical product passport. The data completeness metric may be generated as described in the context of FIG. 19 to FIG. 22. The data completeness metric may indicate the degree of correlation between the validated data and optionally the data gathered in block 1406 and the data points defined by the data model associated with the chemical product passport (e.g. the data model used to generate the chemical product passport), for example as illustrated in FIG. 21 A to FIG. 21 C.

[0321] The provided chemical product passport may be updated with the validated data and optionally the data gathered in block 1406. Updating the provided chemical product passport may include

[0322] • providing a data model associated with the chemical product passport,

[0323] • generating a data set by applying the data model to the gathered data,

[0324] • updating the chemical product passport with the generated data set.

[0325] The data model may be provided as described in the context of FIG. 12. Updating the chemical product passport with the generated data set may include updating passport data included in the chemical product passport with data included in the generated data set. Updating the passport data may include modifying, adding or deleting passport data based on data included in the generated data set.

[0326] The updated chemical product passport may be provided for access, for example as described in the context of FIG. 15. In addition, the generated data completeness metric may be provided along with the chemical product passport. This way, users accessing the updated chemical product passport can determine the reliability of the passport data.

[0327] By updating the chemical product passport, validated data available for updating and being provided later than generation of the chemical product passport may be included in such chemical product passport. This allows to “fill up” the passport data after generation of the chemical product passport when data providers start to provide data for such passport. By updating the chemical product passport based on data validated according one or more rule(s) related to a data model associated with the chemical product passport, it can be ensured that the data points defined according to the data model are included in the validated data. This avoids incomplete, false and / or missing data present within the data associated with the production of the chemical product and hence missing data points present within the updated passport data of the chemical product passport. This way, a higher data quality of the updated passport data can be ensured, allowing to provide updated chemical product passports having an improved reliability since the updated passport data is associated with a higher degree of completeness.

[0328] By generating and providing a data completeness metric indicating the degree of completeness of the passport data with respect to the data defined by the data model used for its generation, a stream of chemical products associated the chemical digital product passports to a downstream production using the chemical products to produce one or more further product(s) can be monitored and / or controlled. In addition, the degree of updating and the progress of data provision can be made transparent, for example to the entity generating the chemical product passport. This allows the entity generating the chemical product passport to request provision of missing data to achieve a higher quality and reliability of the passport data.

[0329] FIG. 19 illustrates an example of a data quality analyzer illustrated in FIG. 10. The data quality analyzer 1006 may include metrics generator 1902. The metrics generator 1902 may be communicatively coupled to registry 1010 and asset validation system 1004. In one embodiment, metrics generator 1902 may further be in communication with a rule database 1904 storing one or more validation rule(s) configured to validate completeness of data accessible for generating and / or updating chemical product passports based on data related to data models associated with the respective chemical product passports.

[0330] With reference to FIG. 20, metrics generator 1902 may include a rule-based engine 2002. The rule-based engine 2002 may operate on individual data point(s), multiple data point(s) and / or a whole data set, such as the validated data provided by asset validation system 1004. The rule-based engine 2002 may operate on validated data or data stored in registry 1010 per digital chemical product identifier individually. This allows to determine the degree of completeness of the data accessible for generating and / or updating a given chemical product passport, hence allowing transparency on the data accessible for generating and / or updating a given chemical product passport on a more granular level, e.g. on chemical product passport level. Rule-based engine 2002 may receive a request to validate the quality of the data accessible for generating and / or updating the chemical product passport. The data accessible for generating and / or updating the chemical product passport may include the validated data. The data accessible for generating and / or updating the chemical product passport may further include data associated with the production of the chemical product and gathered via a decentral network, for example as described in the context of block 1404 of FIG. 15 and FIG. 18. The request may contain data associated with the chemical product, such as a chemical product identifier. The chemical product identifier may include a unique chemical product ID. The chemical product identifier may further include a chemical product type identifier uniquely identifying the chemical product type or chemical product class of the chemical product. The rule-based engine 2002 may have access to one or more validation rule set(s) including one or more validation rule(s). The rule-based engine 2002 may include one or more validation rule set(s) including one or more validation more rule(s). The one or more validation rule set(s) may be stored in a data storage, such as rule DB 1904. The one or more rule(s) may correspond to unstructured data associated with instructions related to validation operation(s). The validation rule set(s) may correspond to unstructured data associated with instructions related to validation operation(s). The one or more validation rule set(s) and / or validation rule(s) may be associated with a chemical product type identifier(s) and / or with chemical product identifier(s). Rule-based engine 2002 may be configured generate a request to obtain at least one validation rule set from rule DB 1904. The request may contain the respective chemical product identifier(s).

[0331] One or more validation rule set(s) may be provided to rule-based engine 2002 in response to the request. The validation rule set(s) may include rules configured to validate completeness of data accessible for generating and / or updating chemical product passports based on data related to data models associated with the respective chemical product passports. The validation rule(s) may relate to data related to the data models. The validation rule(s) may relate to input material producer(s) producing input material(s) associated with input material data defined by the data models. The validation rule(s) may relate to one or more data point(s) defined by the data models. The validation rule(s) may relate to one or more data points associated with input material(s) used to produce the chemical product and the chemical product as defined by the data models. The validation rule(s) may relate to one or more data points to be provided for access per participant of the chemical product ecosystem involved in the production of the chemical product according to data models. The validation rule(s) may be configured to determine input material identifiers associated with the chemical product identifier(s), to determine validated data associated with the determined input material identifiers and optionally the chemical product identifier and to determine the degree of correlation by comparing target data points defined by the data model with the data points included in the validated data. The one or more validation rule(s) may be configured to generate the data completeness metric per chemical product identifier.

[0332] Rule-based engine 2002 may be configured to select at least one validation rule based on the data associated with the chemical product. The selection may be dynamic and / or static based on the data associated with the chemical product and validation rule pairs. For example, data associated with the chemical product, such as the chemical product type identifier, and validation rule pairs may be predefined. The one or more validation rule(s) may be associated with chemical product identifier(s) and / or chemical product type identifier(s). A mapping table may be used to map chemical product identifier(s) to corresponding chemical product type identifier(s) associated with the validation rule(s). The chemical product type identifier(s) may be associated with chemical product type(s). The mapping table may be stored in a separate database (not shown). This way, the validation rule set may include validation rule(s) associated with different chemical product type identifier(s), hence avoiding generation of different validation rule set(s) per chemical product type or per chemical product and allowing to reduce the number of validation rule set(s) that need to be generated, stored and maintained in rule DB 1904.

[0333] Rule-based engine 2002 may be configured to initialize the rule engine (see operation 2006). Initialization of the rule engine may include generating rule data executable by a processor included in rule-based engine 2002, for example as described in the context of FIG. 13B. The rule data may include or correspond to executable logic. This may allow to transform validation rule(s) present in unstructured data form into code that can be executed by the processor. Execution of the code may result in applying the executable rule data to the validated data provided by asset validation system 1004 and / or registry 1010 (see operation 2008) to validate the data accessible for generating and / or updating chemical product passports associated with products according to the obtained rule(s). Execution of the logic may result in matching the validated data provided by asset validation system 1004 and / or registry 1010 to condition(s) included in the executable logic, evaluating the condition(s) with matched data and triggering execution of rule actions based on condition evaluation results. Validation of the data may include determining input material identifiers and associated accessible data points based on the data associated with the chemical product, optionally determining accessible data points associated with the chemical product based on the data associated with the chemical product, and determining a degree of correlation by comparing target data points defined by the data model with the accessible data points. The validation rule(s) may be configured to determine input material identifiers associated with the chemical product identifier, to determine validated data associated with the determined input material identifiers and optionally the chemical product identifier and to determine the degree of correlation by comparing target data points defined by the data model with the data points included in the validated data. Operations performed by rule-based engine 2002 may be determined by validation rule set(s) and included validation rule(s) gathered from rule DB 2004. For instance, rule(s) gathered from rule DB 2004 may determine whether rule-based engine 2002 operates on individual data point(s) and / or multiple data point(s) and / or the whole data.

[0334] Rule-based engine 2002 may be configured to provide the validation result to metrics generator 1902. Metrics generator 1902 may be configured to generate a data completeness metric from the validation result received from rule based engine 2002. Metrics generator 1902 may be configured to provide the generated data completeness metrics. Providing may include providing the metrics for display. Providing may include providing the metrics to a data storage. Providing may include providing the metrics via a communication interface, for example to another module of chemical product passport service 322, such as chemical product passport generator 1008.

[0335] With reference to FIG. 21A, generating the data completeness metric may include determining a total or overall degree of correlation between data points included in the validated data (e.g. validated data points) and the target data points based on the validation result. The degree of correlation may correspond to the fraction of validated data points matching the target data points with respect to the total number of target data points. The degree of correlation may be determined per chemical product identifier. The generated data completeness metrics 2102 may include data associated with the chemical product, such as the chemical product identifier, and a total degree of correlation of validated data points to target data points. The total degree of correlation may be displayed within a graphical user interface as completeness bar 2104. Such metric provides an overview on the total degree of correlation, e.g. the total amount of validated data points and non-accessible data points (e.g. missing data points) and may allow to provide transparency on the overall quality of the passport data included in a chemical product passport generated from such validated data.

[0336] In another embodiment and with reference to FIG. 21 B and FIG. 21 C, generating the data completeness metric may include determining the degree of correlation of data points included in the validated data (e.g. validated data points) and target data points for at least a part of the participants of the chemical product ecosystem involved in the production of the chemical product (e.g. for at least a part of the participants of the production chain producing the chemical product). The degree of completeness may be determined by comparing the target data points per participant role with validated data points provided per respective participant role. In one example and with reference to FIG. 24B, the generated data completeness metric 2102 may include the chemical product identifier(s), available child identifier(s) (e.g. input material identifier(s) associated with input material(s) used to produce the chemical product) associated with said chemical product identifier(s), the participant role associated with such identifier(s) and the degree of completeness per participant role. The generated data completeness metric 2102 illustrated in FIG. 21 B may be displayed within a graphical user interface. In another example and with reference to FIG. 21 C, the generated data completeness metric may include the data mentioned with respect to FIG. 21 B and additional data points, such as whether validated data points associated with input material(s) used to produce the chemical product are available as well as the number of validated data points and the number of target data points per participant role. Based on the number of available validated data points and target data points, a total degree of correlation between the number of validated data points and the number of target data points may be determined. The data completeness metric 2402 illustrated in FIG. 21 C may be displayed within a graphical user interface. In addition, the total degree of correlation may be displayed as completeness bar 2104 within the graphical user interface.

[0337] The metrics illustrated in FIG. 21 B and FIG. 21 C do not only provide a transparency on the degree of completeness with respect to validated data points available for generating and / or updating chemical product passports, but at the same time allow to identify participants of the chemical product ecosystem who have not yet provided access to data associated with input material(s) and / or the chemical product. Such transparency allows to request data from such participants to improve the quality (e.g. the completeness) of the passport data included in the generated and / or updated chemical product passport.

[0338] FIG. 22 illustrates a flow chart of an example of a method for validating a completeness of data available for generating and / or updating a chemical product passport associated with a chemical product. The completeness of the data may be validated with respect to the availability of such data for generating the chemical product passport and / or for updating an existing chemical product passport. Data available for generating and / or updating the chemical product passport may include validate data generated as described in the context of FIG. 13A, FIG. 13B and FIG. 15 to FIG. 17. Data available for generating and / or updating the chemical product passport may further include data gathered from the decentral network as described in the context of block 1406 of FIG. 14 or FIG. 18. The completeness may signify a degree of correlation between the available data and data defined by a data model associated with the chemical product passport. The higher the degree of correlation, the lower the deviation between the available data and the data defined by the data model and hence the higher the completeness of the available data and the passport data generated from such available data. The chemical product may be a chemical product as described in the context of FIG. 3. The chemical product may be produced from one or more input material(s) by a production chain. The production chain may include one or more production step(s) as described in the context of FIG. 3. The method illustrated in FIG. 22 may be implemented by the chemical product passport service 322 described in the context of FIG. 3 and FIG. 10. The method illustrated in FIG. 22 may be part of the method illustrated in FIG. 15 or FIG. 18.

[0339] Data associated with data sources indicating data accessible for generating and / or updating chemical product passports may be provided, for example as described in the context of FIG. 15 and FIG. 16. The data sources may be provider nodes of a decentral network as described in the context of FIG. 3 and FIG. 10. Data source data may include endpoints associated with such data sources. With reference to FIG. 10 and FIG. 15, data associated with data sources indicating available data may be provided from a storage, such as registry 1010. Registry 1010 may store such data associated with the data sources. Data associated with the data sources may be generated and stored as described in the context of FIG. 10 and FIG. 11 C.

[0340] Data related to a data model associated with the chemical product passport may be gathered based on the provided data associated with chemical product. The data related to the data model may include participant role(s) of participants associated with the production of the chemical product and the number of data points to be provided by such participant role(s) according to the data model. The data related to the data model may further include a digital chemical product identifier, such as a chemical product type identifier. This way, the data related to the data model may be linked to a chemical product or a chemical product type. The participant role(s) may include the role(s) illustrated in FIG. 1 , such as recycler 114, producer 104 and chemical product producer 102. Participants associated with the production of the chemical product may include participants performing at least one production step of the production chain used to produce the chemical product. The number of data points to be provided by such participant role(s) according to the data model may be determined by assigning a participant role to at least a part of the data points defined by the data model and accumulating the data points per assigned participant role. The data points defined by the data model may be assigned to participant role(s) based on properties of the intermediate chemical product or the chemical product produced by such participant role. For instance, data points defining the chemical product properties within the data model may be assigned to the participant role “chemical product producer”. Likewise, data points defining the composition of the input materials used to produce the chemical product, such as raw materials and / or recycled materials, may be assigned to the participant...

Claims

CLAIMS1 . A method for generating a chemical product passport associated with a chemical product, wherein the chemical product is produced from one or more input material(s) by a production chain, the method comprising: providing data associated with the chemical product including at least one digital chemical product identifier associated with the chemical product, gathering validated data associated with the production of the chemical product based on the at least one digital chemical product identifier, wherein the validated data is generated by gathering data associated with the production of the chemical product from decentral data providing node(s) associated with the data associated with the production by a decentral data consuming node based on the provided digital chemical product identifier(s) and validating at least a part of the gathered data using a rule-based engine including one or more rule(s) related to a data model associated with the chemical product passport, providing at least one decentral identifier associated with the validated data, generating the chemical product passport including the decentral identifier(s) and at least a part of the validated data and providing the generated chemical product passport for access.

2. A method for updating a chemical product passport associated with a chemical product, wherein the chemical product is produced from one or more input material(s) by a production chain, the method comprising: providing data associated with the chemical product including at least one digital chemical product identifier associated with the chemical product, gathering validated data associated with the production of the chemical product based on the at least one digital chemical product identifier, wherein the validated data is generated by gathering data associated with the production of the chemical product from decentral data providing node(s) associated with the data associated with the production by a decentral data consuming node based on the provided digital chemical product identifier(s) and validating at least a part of the gathered data using a rule-based engine including one or more rule(s) related to a data model associated with the chemical product passport, providing the chemical product passport including at least one decentral identifier and at least one of the digital chemical product identifiers based on the data associated with the chemical product, updating the chemical product passport based on the validated data and providing the updated chemical product passport for access.

3. The method of claim 1 or 2, wherein the data associated with the production of the chemical product includes input material data associated with input material(s) used to produce the chemical product and / or chemical product data associated with the chemical product.

4. The method of any one of claims 1 to 3, wherein the decentral data providing node(s) are determined from data associated with data sources indicating data accessible for generating and / or updating the chemical product passports by determining data set identifier(s) associated with input material(s) used to produce the chemical product based on at least one of the chemical product identifier(s) using relationship representation(s) included in the data associated with the data sources.

5. The method of any one of claims 1 to 4, wherein validating the gathered data includes providing the gathered data to one or more input node(s) configured to gather the data and to provide the gathered data as data set(s) to one or more downstream node(s), wherein the one or more downstream node(s) include the rule-based engine configured to validate at least a part of the data included in the data set(s) provided by the one or more input node(s).

6. The method of any one of claims 1 to 5, wherein the rule-based engine operates on individual data points present within at least part of the gathered data, multiple data points present within at least part of the gathered data or the whole gathered data.

7. The method of any one of claims 1 to 6, wherein the gathered data is validated responsive to fulfilment of one or more rule(s) applied to the gathered data by the rule-based engine.

8. The method of any one of claims 1 to 7, wherein the chemical product passport is provided under control of the data owner of the chemical product passport.

9. The method of any one of claims 1 to 8, further including a step of generating and providing a data completeness metric associated with the chemical product passport, wherein the data completeness metric indicates a degree of correlation between the validated data included in the chemical product passport and data related to the data model associated with the chemical product passport.

10. The method of claim 9, wherein the data completeness metric is generated by comparing data points defined by the data model with data points included in the validated data.

11. The method of claim 9 or claim 10, wherein the data completeness metric includes a total degree of correlation between the validated data included in the chemical product passport and the data related to the data model associated with the chemical product passport and / or wherein the data completeness metric includes a degree of correlation between validated data points provided per participant and data points to be provided per participant according to the data model.

12. An apparatus for generating a chemical product passport associated with a chemical product, wherein the chemical product is produced from one or more input material(s) by a production chain, the apparatus comprising: a data providing interface configured to provide data associated with the chemical product including at least one digital chemical product identifier associated with the chemical product, a data gathering unit configured to gather validated data associated with the production of the chemical product based on the at least one digital chemical product identifier, wherein the validate data is generated by gathering data associated with the production of the chemical product from decentral data providing node(s) associated with the data associated with the production by a decentral data consuming node based on the provided digital chemical product identifier(s) and validating at least a part of the gathered data using a rulebased engine including one or more rule(s) related to a data model associated with the chemical product passport, a decentral identifier provider configured to provide at least one decentral identifier associated with the validated data, a passport generator configured to generate the chemical product passport including the decentral identifier(s) and at least a part of the validated data and providing the generated chemical product passport for access.

13. An apparatus for updating a chemical product passport associated with a chemical product, wherein the chemical product is produced from one or more input material(s) by a production chain, the apparatus comprising: a data providing interface configured to provide data associated with the chemical product including at least one digital chemical product identifier associated with the chemical product, a data gathering unit configured to gather validated data associated with the production of the chemical product based on the at least one digital chemical product identifier, wherein the validated data is generated by gathering data associated with the production of the chemical product from decentral data providing node(s) associated with the data associated with the production by a decentral data consuming node based on the provided digital chemical product identifier(s) and validating at least a part of the gathered data using a rulebased engine including one or more rule(s) related to a data model associated with the chemical product passport, a passport provider configured to provide the chemical product passport including at least one decentral identifier and at least one of the digital chemical product identifiers based on the data associated with the chemical product,a passport updater configured to update the chemical product passport based on the validated data and providing the updated chemical product passport and optionally the data completeness metric for access.

14. A chemical product associated with a chemical product passport as generated and / or updated by the methods of any one of claims 1 to 11 or by the apparatuses claimed in claim 12 and 13.

15. A use of a chemical product passport as generated and / or updated for a chemical product by the methods of any one of claims 1 to 11 or by the apparatuses claimed in claim 12 and 13 to further process the chemical product associated with the chemical product passport

Images