Method and system for enabling the circulation of mechanical fluids

Abstract

Disclosed are methods, apparatus, systems, and reuse commands or control data configured to control the reuse of at least one spent mechanical fluid and chemical materials produced from at least one spent mechanical fluid by using control data. The present invention further relates to methods, systems, apparatus, and computer elements for sorting mechanical fluid waste in a data-driven manner over a distributed network.

Description

[Technical Field]

[0001] Technical field Disclosed are methods, apparatus, systems, and reuse commands or control data configured to control the reuse of at least one spent mechanical fluid and chemical materials produced from at least one spent mechanical fluid by using control data. The present invention further relates to methods, systems, apparatus, and computer elements for sorting mechanical fluid waste in a data-driven manner over a distributed network. [Background technology]

[0002] Technical background Mechanical fluids are used in a variety of applications and ultimately involve multiple supply chains. Used mechanical fluids are not easily reusable. This hinders the reliable resupply of used mechanical fluids into the reuse chain and the creation of a circular ecosystem. [Overview of the Initiative] [Means for solving the problem]

[0003] Summary of the Invention In one aspect, the present disclosure relates to a method for monitoring a machine fluid during use, particularly a method performed by a computer, the method being: ● Provide at least one usage trigger that includes at least one distributed machine identifier associated with a mechanical fluid, ●Collect status data associated with the mechanical fluid via at least one distributed machine identifier, ● Provide one or more distributed mechanical fluid identifiers associated with the status data, ●Generating one or more digital representations of status data, in particular, the digital representations including representations for accessing the status data. ●Generate an access element that includes one or more distributed mechanical fluid identifiers and one or more digital representations, ● Providing an access element to a distributed network for access to status data by one or more data-consuming network nodes of the distributed network, under the control of a data-providing network node associated with a producer of mechanical fluids, wherein the status data is stored in a database associated with the producer of mechanical fluids, and access to such database is controlled by the producer of mechanical fluids via the data-providing network node.

[0004] In a further embodiment, the present disclosure relates to an apparatus for monitoring a machine fluid during use, the apparatus comprising: ● A trigger generator configured to generate at least one use trigger, which includes at least one distributed machine identifier associated with a mechanical fluid, ● A distributed network interface configured to collect status data associated with a machine fluid via at least one distributed machine identifier, ● An identifier provider configured to collect one or more distributed mechanical fluid identifiers associated with status data, ● A representation generator configured to generate one or more digital representations of status data, wherein the digital representation includes a representation for accessing the status data, ● An access element generator configured to generate access elements including one or more distributed mechanical fluid identifiers and one or more digital representations, ●A distributed network interface configured to provide an access element to a distributed network for access to status data by one or more data-consuming network nodes of a distributed network, under the control of a data-providing network node associated with a mechanical fluid producer, wherein the status data is stored in a database associated with the mechanical fluid producer, and access to such a database is controlled by the mechanical fluid producer via the data-providing network node.

[0005] In further embodiments, the Disclosure relates to a method for monitoring a machine fluid during use, particularly a computer-based method, the method being: ● Provide at least one usage trigger, which includes at least one distributed machine identifier associated with the machine and status data associated with the machine fluid. ● Provide one or more distributed mechanical fluid identifiers associated with the status data, ●Generating one or more digital representations of status data, in particular, the digital representations including representations for accessing the status data. ●Generate an access element that includes one or more distributed mechanical fluid identifiers and one or more digital representations, ● Providing an access element to a distributed network for access to status data by one or more data-consuming network nodes of the distributed network, under the control of a data-providing network node associated with a producer of mechanical fluids, wherein the status data is stored in a database associated with the producer of mechanical fluids, and access to such database is controlled by the producer of mechanical fluids via the data-providing network node.

[0006] In a further embodiment, the present disclosure relates to an apparatus for monitoring a mechanical fluid during use of a machine that includes such mechanical fluid, the apparatus is A trigger provider configured to provide at least one usage trigger, which includes at least one distributed machine identifier associated with a machine and status data associated with a machine fluid, ● An identifier provider configured to collect one or more distributed mechanical fluid identifiers associated with status data, ● A representation generator configured to generate one or more digital representations of status data, wherein the digital representation includes a representation for accessing the status data, ● An access element generator configured to generate access elements including one or more distributed mechanical fluid identifiers and one or more digital representations, ●A distributed network interface configured to provide an access element to a distributed network for access to status data by one or more data-consuming network nodes of a distributed network, under the control of a data-providing network node associated with a mechanical fluid producer, wherein the status data is stored in a database associated with the mechanical fluid producer, and access to such a database is controlled by the mechanical fluid producer via the data-providing network node.

[0007] In a further aspect, the disclosure relates to a method for accessing status data related to monitoring mechanical fluids used in a machine, particularly a method performed by a computer, the method being ● Provide at least one distributed machine identifier associated with the machine, ●Collecting one or more access elements generated and / or provided by the methods disclosed herein or by the apparatus disclosed herein, via a provided distributed machine identifier, in particular, the collection of one or more access elements via a distributed network, ● In particular, this includes requesting access to status data from mechanical fluid producers based on one or more collected access elements.

[0008] In a further embodiment, the Disclosure relates to a device for accessing status data related to monitoring mechanical fluids used in a machine, wherein the device is ● An identifier providing interface configured to provide a distributed identifier associated with a machine, ● An access element read unit configured to collect one or more access elements generated and / or provided by a device disclosed herein or in accordance with a method disclosed herein, via a provided distributed machine identifier, wherein the access element read unit is configured such that one or more access elements are collected via a distributed network. ● In particular, it includes an access request unit configured to request access to status data from a mechanical fluid producer based on one or more collected access elements.

[0009] In further embodiments, the Disclosure relates to a distributed network node configured to provide access elements in accordance with the methods disclosed herein or by the devices disclosed herein, or a distributed network node configured to access status data in accordance with the methods disclosed herein or by the devices disclosed herein.

[0010] In further embodiments, this disclosure relates to mechanical fluids associated with access elements generated and provided in accordance with the methods disclosed herein or by the apparatus disclosed herein.

[0011] In a further aspect, this disclosure relates to a method for generating maintenance data associated with the maintenance of used machine fluid, particularly a method performed by a computer, wherein the machine fluid is used in a machine, and the method is ● Provide at least one distributed machine identifier associated with the machine, ● Based on the provided distributed machine identifier, machine fluid data, including status data associated with used machine fluid and accessed in accordance with the methods disclosed herein or by the devices disclosed herein, is collected by distributed network nodes from distributed network nodes, ● By correlating collected mechanical fluid data with accessed status data, maintenance data is generated. ●Includes providing generated maintenance data for the maintenance of used mechanical fluids.

[0012] In a further aspect, the present disclosure relates to an apparatus for generating maintenance data associated with the servicing of used machine fluid, where the machine fluid is used within a machine, and the method ● an identifier providing interface configured to provide at least one distributed machine identifier associated with the machine, and ● a distributed network interface configured to collect machine fluid data including status data associated with the used machine fluid and accessible according to the methods disclosed herein or by the apparatus disclosed herein, based on the provided distributed machine identifier, from a distributed network node, and ● a maintenance data generator configured to generate maintenance data by correlating the collected machine fluid data with the accessed status data, and ● a data provider configured to provide the generated maintenance data for the servicing of the used machine fluid.

[0013] In a further aspect, the present disclosure relates to the use of maintenance data generated according to the methods disclosed herein or by the apparatus disclosed herein for controlling the servicing of used machine fluid.

[0014] In a further aspect, the present disclosure relates to a method for performing one or more reuse operations on used machine fluid, particularly a method implemented by a computer, where the machine fluid is used within a machine, and the method ● provides at least one distributed machine identifier associated with the machine, and ● collects status data associated with the used machine fluid according to the methods disclosed herein or by the apparatus disclosed herein, and ●Generating control data by correlating collected status data with one or more devices configured to perform reuse operations on spent mechanical fluids, and by generating machine-readable instructions to control reuse by one or more devices configured to perform reuse operations. ●Providing generated control data, including machine-readable instructions for execution by one or more devices configured to perform one or more reuse operations on spent mechanical fluids.

[0015] In a further embodiment, the present disclosure relates to an apparatus for performing one or more reuse operations on used mechanical fluid, wherein the mechanical fluid is used in a machine, and the apparatus is ● An identifier providing interface configured to provide at least one distributed machine identifier associated with a machine, ● A distributed network interface configured to collect status data relating to used mechanical fluids in accordance with the methods disclosed herein or by the apparatus disclosed herein, A control data generator configured to generate control data by correlating the collected status with one or more devices configured to perform reuse operations on spent mechanical fluid, and by generating machine-readable instructions to control reuse by one or more devices configured to perform reuse operations. ● A control data provider configured to provide generated data including machine-readable instructions for performing one or more reuse operations on used mechanical fluids by one or more devices configured to perform reuse operations.

[0016] In a further embodiment, the disclosure relates to a system for performing one or more reuse operations on used mechanical fluids, wherein the system is ● Apparatus for performing one or more reuse operations on spent mechanical fluids as disclosed herein, ●The following devices, configured to receive control data generated according to the methods disclosed herein, for example: ○ Chemical and / or physical equipment for cleaning used mechanical fluids, ○ Chemical and / or physical apparatus for recovering chemical materials from spent mechanical fluids It comprises at least one of the following, and

[0017] In further embodiments, the disclosure relates to one or more chemical materials produced from at least one spent mechanical fluid by following the methods disclosed herein, by the apparatus disclosed herein, or by using control data generated by the system disclosed herein. In a further embodiment, the disclosure relates to a cleaned mechanical fluid produced from at least one used mechanical fluid in accordance with the methods disclosed herein or by using control data generated by the apparatus disclosed herein.

[0018] In further embodiments, the disclosure relates to the use of control data provided in accordance with the methods disclosed herein or by the apparatus disclosed herein for controlling the reuse of at least one spent mechanical fluid and / or for resupplying chemical materials recovered from at least one spent mechanical fluid to one or more chemical production processes.

[0019] In further embodiments, the Disclosure relates to a method for sorting waste mechanical fluids, particularly a computer-based method, wherein the method is ● A step of detecting at least one identifier element for each machine containing at least one waste machine fluid, wherein at least one identifier element relates to at least one distributed machine identifier associated with each machine containing the waste machine fluid, A step of providing a distributed machine identifier associated with a machine and collecting machine fluid data based on the distributed machine identifier, wherein the machine fluid data is collected based on the distributed machine identifier provided by one or more network nodes of the distributed network. ● A step of assigning waste mechanical fluid to one or more mechanical fluid waste fractions based on collected mechanical fluid data, wherein one or more mechanical fluid waste fractions are: ○Specified mechanical fluid producers, ○ Physical recycling processes and / or, ○ Chemical recycling processes and / or, ○Recycling processes involving physical and chemical treatment and / or, ○Thermal recycling process, The waste fraction that will be processed by the allocation step, ● A step of generating sorting data for sorting waste mechanical fluid into the assigned mechanical fluid waste fraction based on the assigned mechanical fluid waste fraction, ● The process includes the step of providing generated sorting data for sorting waste mechanical fluid into assigned mechanical fluid waste fractions.

[0020] In a further aspect, the present disclosure relates to an apparatus for sorting waste mechanical fluid, the apparatus is ● For each machine containing at least one waste machine fluid, an identifier reader configured to detect at least one identifier element relating to at least one distributed machine identifier associated with each machine containing the waste machine fluid, ● A distributed network interface that provides a distributed machine identifier associated with a machine, and is configured to collect machine fluid data based on the distributed machine identifier provided by one or more network nodes of the distributed network, ●Based on mechanical fluid data, waste mechanical fluid is one or more mechanical fluid waste fractions, ○Specified mechanical fluid producers, ○ Physical recycling processes and / or, ○ Chemical recycling processes and / or, ○Recycling processes involving physical and chemical treatment and / or, ○Thermal recycling process, Regarding the waste fractions to be processed by, one or more mechanical fluid waste fractions, A fractional unit configured to be assigned to, ● A sorting data generator configured to generate sorting data for sorting waste mechanical fluid into assigned mechanical fluid waste fractions based on the assigned mechanical fluid waste fractions, ●Includes an interface configured to provide generated sorting data for sorting waste mechanical fluid into assigned mechanical fluid waste fractions.

[0021] In a further aspect, this disclosure relates to a system for sorting waste mechanical fluids, wherein the system is ● A distributed network interface, ○An identifier reader configured to detect at least one identifier element relating to at least one distributed machine identifier associated with each machine containing at least one waste machine fluid, for each machine containing at least one waste machine fluid, A distributed network interface, which includes a distributed network interface that provides a distributed machine identifier associated with a machine and is configured to collect machine fluid data based on the distributed machine identifier provided by one or more network nodes of the distributed network, ● A sorting data generation unit, ○Based on mechanical fluid data, waste mechanical fluid is one or more mechanical fluid waste fractions, - Specified mechanical fluid producers, - Physical recycling processes and / or, - Chemical recycling processes and / or, - Recycling processes involving physical and chemical treatment and / or, - Thermal recycling process, One or more mechanical fluid waste fractions related to the waste fractions to be processed by, A fractional unit configured to be assigned to, A sorting data generator configured to generate sorting data for sorting waste mechanical fluid into assigned mechanical fluid waste fractions based on the assigned mechanical fluid waste fractions, The system includes a sorting data generation unit, which includes an interface configured to provide generated sorting data for sorting waste mechanical fluid into assigned mechanical fluid waste fractions.

[0022] In further embodiments, the disclosure relates to a method for controlling and / or sorting waste mechanical fluids, the method being: A step of collecting machine fluid data based on one or more distributed machine identifiers associated with a machine containing waste machine fluid, wherein the machine fluid data is collected by one or more network nodes of a distributed network based on the provided distributed machine identifiers, ● A step of assigning waste mechanical fluid to one or more mechanical fluid waste fractions based on collected mechanical fluid data, wherein one or more mechanical fluid waste fractions are: ○Specified mechanical fluid producers, ○ Physical recycling processes and / or, ○ Chemical recycling processes and / or, ○Recycling processes involving physical and chemical treatment and / or, ○Thermal recycling process, The allocation step related to the waste fraction that will be processed by, ● A step of generating sorting data for sorting waste mechanical fluid into the assigned mechanical fluid waste fraction based on the assigned mechanical fluid waste fraction, ● The process includes the step of providing generated sorting data for sorting waste mechanical fluid into assigned mechanical fluid waste fractions.

[0023] In further embodiments, the present disclosure relates to an apparatus for controlling and / or sorting waste mechanical fluids, the apparatus is ●A fractional unit, ○ Based on one or more distributed machine identifiers associated with a machine containing waste machine fluid, collect machine fluid data that is collected by one or more network nodes of the distributed network based on the provided distributed machine identifiers. Based on the collected mechanical fluid data, waste mechanical fluid is classified into one or more mechanical fluid waste fractions, - Specified mechanical fluid producers, - Physical recycling processes and / or, - Chemical recycling processes and / or, - Recycling processes involving physical and chemical treatment and / or, - Thermal recycling process, A fraction unit configured to assign waste mechanical fluid to one or more mechanical fluid waste fractions that will be processed by the waste fraction, ● A sorting data generator configured to generate sorting data for sorting waste mechanical fluid into assigned mechanical fluid waste fractions based on the assigned mechanical fluid waste fractions, ●Includes an interface configured to provide generated sorting data for sorting waste mechanical fluid into assigned mechanical fluid waste fractions.

[0024] In a further embodiment, the disclosure relates to a method for controlling sorted mechanical fluid waste fractions according to the method disclosed herein, wherein mechanical fluid data is aggregated into waste fraction mechanical fluid data for each sorted waste fraction, preferably a distributed waste fraction mechanical fluid identifier is assigned to the waste fraction mechanical fluid data, and the distributed waste fraction mechanical fluid identifier associated with the sorted fraction is provided for access by one or more distributed network nodes of a distributed network.

[0025] In further embodiments, the Disclosure relates to an apparatus for controlling mechanical fluid waste fractions sorted by the apparatus disclosed herein, the apparatus further comprising a data aggregater configured to aggregate mechanical fluid data into waste fraction mechanical fluid data for each sorted waste fraction, preferably the apparatus comprising a distributed network interface configured to assign distributed waste fraction mechanical fluid identifiers to waste fraction mechanical fluid data and to provide distributed waste fraction mechanical fluid identifiers associated with sorted fractions for access by one or more distributed network nodes of a distributed network.

[0026] In a further embodiment, the Disclosure relates to a distributed data consumption network node configured to provide mechanical fluid data for sorting or controlling sorting in accordance with the methods disclosed herein or by the apparatus or system disclosed herein.

[0027] In a further embodiment, the Disclosure relates to a distributed data serving network node configured to provide waste fraction mechanical fluid data generated in accordance with the methods disclosed herein or by the apparatus or system disclosed herein.

[0028] In a further embodiment, the disclosure relates to a mechanical fluid waste fraction associated with a distributed waste fraction mechanical fluid identifier relating to waste fraction mechanical fluid data characterizing the mechanical fluid waste fraction, and generated according to a method for controlling the mechanical fluid waste fraction or by an apparatus for controlling the mechanical fluid waste fraction.

[0029] In a further embodiment, the Disclosure relates to a classification command, which is configured to receive mechanical fluid data and associate the mechanical fluid data with mechanical fluid waste fractions processed by a specified mechanical fluid producer, a physical recycling process, a chemical recycling process, a recycling process involving physical and chemical treatment, and / or a thermal recycling process, and the classification command is usable in the manner disclosed herein or by the apparatus disclosed herein.

[0030] In a further embodiment, the Disclosure relates to a distributed classification command providing network node, associated with one or more mechanical fluid producers and / or one or more consumers of recycletes produced by recycling waste mechanical fluids, and configured to provide classification commands, the classification commands being configured to receive mechanical fluid data and associate the mechanical fluid data with mechanical fluid waste fractions processed by specified mechanical fluid producers, physical recycling processes, chemical recycling processes, recycling processes involving physical and chemical treatments, and / or thermal recycling processes, and the classification commands being used in the manner disclosed herein or by the apparatus disclosed herein.

[0031] In further embodiments, the Disclosure relates to the use of mechanical fluid data for sorting waste mechanical fluid into one or more mechanical fluid waste fractions, or for controlling the sorting of waste mechanical fluid into one or more mechanical fluid waste fractions, in accordance with the methods disclosed herein or by the apparatus or systems disclosed herein.

[0032] In further embodiments, this disclosure relates to the use of waste fraction mechanical fluid data associated with mechanical fluid waste fractions and generated in accordance with the methods disclosed herein for recycling mechanical fluid waste fractions or by the apparatus or systems disclosed herein.

[0033] In further embodiments, the disclosure relates to computer elements such as computer-readable storage media, computer programs, or computer program products, which, when executed by a computing node or computing system, include instructions that instruct the computing node or computing system to perform steps of a method performed on a computer as disclosed herein.

[0034] In further embodiments, the Disclosure relates to computer elements such as computer-readable storage media, computer programs, or computer program products, which, when executed by the apparatus or system disclosed herein, include instructions that instruct the apparatus or system to perform steps configured to be performed by the apparatus or system disclosed herein.

[0035] All disclosures, embodiments, and examples described herein relate to the methods, systems, apparatus, products, chemical materials, instructions, uses, consumption services, services provided, and computer elements described above and below. Advantageously, any benefits derived from any one embodiment or example are equally applicable to all other embodiments and examples.

[0036] Embodiment To improve the reuse of used machine fluids, such as maintenance or recycling, and to increase the time that machine fluids are used in a machine before reuse or replacement is performed, it is important to share status data that indicates at least one characteristic of the used state of the machine fluid. However, to date, data sharing in machine ecosystems, including machine fluids, has not been standardized by communication protocols to control access to such data by stakeholders in the machine ecosystem. Distributed networks enable controlled peer-to-peer communication among stakeholders in the machine ecosystem. By making at least one characteristic of the used state of the machine fluid, such as status data, available in a standardized manner, it is possible to ensure more efficient and reliable reuse of the machine fluid by accessing such data to determine the next maintenance date and / or the necessary reuse work to be performed. This makes it possible to increase the time that machine fluids are used in a machine, as it avoids replacing machine fluids according to a fixed maintenance schedule that does not take into account the actual wear of the machine fluid during use. This also makes it possible to determine appropriate reuse operations, such as cleaning operations to extend the lifespan of the mechanical fluid within the machine, and / or recycling operations to ensure the recovery of chemical materials from the mechanical fluid, thereby avoiding waste generation and enabling the circularity of the mechanical fluid or its components.

[0037] By collecting status data through access elements via a distributed network and providing access to such status data, it becomes possible to share such status data with stakeholders in the mechanical fluid chain or loop that performs reuse operations. In particular, by providing such status data relevant to selected stakeholders such as maintenance providers, status data owners such as mechanical fluid producers are given the necessary control over sensitive mechanical fluid monitoring data. In particular, by providing such status data relevant to the reuse operations to be performed, more targeted data sharing becomes possible, resulting in more reliable and efficient reuse of mechanical fluids.

[0038] By providing access to status data through an access element, details of spent machine fluid can be considered when determining maintenance data, thereby extending the lifespan of the machine fluid that can be used in the machine and minimizing the environmental impact, for example, by reducing the amount of discarded machine fluid. By combining status data with machine fluid data, the maintenance intervals and / or maintenance work to be performed can be determined based on the current wear of the spent machine fluid, and by adjusting maintenance to the wear of the spent machine fluid, it becomes possible to minimize the environmental impact of the machine fluid without adversely affecting the performance of the machine.

[0039] By providing access to status data via access elements, details of spent machine fluid can be considered during the control of the reuse process, minimizing environmental impact, for example, by extending the life of the machine fluid and / or determining an appropriate recycling process, thereby reducing the amount of waste machine fluid. By correlating status data reflecting the current wear of spent machine fluid with equipment configured to reuse (e.g., cleaning or recycling) the spent machine fluid, more efficient reuse of the machine fluid, such as cleaning or recycling, can be achieved. This makes it possible to reduce the environmental impact of machine fluid flow within the machine ecosystem.

[0040] Based on a distributed machine identifier for each machine containing waste machine fluid from one or more network nodes of a distributed network, machine fluid data associated with the waste machine fluid (e.g., status data indicating at least one characteristic of used machine fluid in a used state) can be accessed. By assigning one or more waste machine fluids to one or more machine fluid waste fractions based on the collected machine fluid data, the quality of machine fluid waste fractions can be controlled in a simple and reliable manner. Furthermore, by specifically defining the sorting by machine fluid waste fractions related to machine fluid waste fractions that will be processed by a specified machine fluid producer, a physical recycling process and / or a chemical recycling process and / or a recycling process involving physical and chemical treatment and / or a thermal recycling process, machine fluid waste fractions can be tailored to the appropriate recycling process. In this way, machine fluid recycling can be improved by increasing the amount of machine fluid that can be resupplied into the material loop. As a result, the environmental impact of machine fluids can be reduced.

[0041] Therefore, by collecting status data specifying at least one characteristic of used mechanical fluid in a used state via access elements through a distributed network, and by providing access to such status data, a circulating mechanical fluid system can be enabled, thereby reducing the environmental impact of mechanical fluid flow within the mechanical ecosystem.

[0042] The embodiments of this disclosure are outlined below as examples. It should be understood that this disclosure is not limited to the embodiments and / or examples described above.

[0043] Mechanical fluids may include any liquid substances commonly used to operate machinery. Mechanical fluids may be present within or in parts of a machine. The substance may be liquid at room temperature under ambient pressure, or at the temperature present during the machine's operation. Used mechanical fluids may include mechanical fluids present in used machinery, for example, machinery that has been operated at least once. The operation of a machine uses up the mechanical fluids within the machine (e.g., in parts of the machine), and thereby the mechanical fluids may be considered used. The use of mechanical fluids may result in deterioration of their chemical and / or physical properties, for example, by contamination and / or decomposition. Contamination may occur if mechanical fluids come into contact with other mechanical fluids or parts of the machine during use. Decomposition may occur when mechanical fluids are exposed to high temperatures that occur during the machine's operation.

[0044] Machinery can be stationary or mobile. Stationary or mobile machinery can be driven by spark-ignition or self-ignition engines, two- or four-stroke engines, electric engines, fuel cells, or combinations thereof (hybrid engines). Stationary machinery may include air conditioning systems, power units (nuclear, coal, natural gas, oil, wind, hydro, solar, geothermal), generators, pumps, hydraulic power units, wind turbines, substations, heat pumps, and compressors. Mobile machinery may include vehicles. Vehicles may include automobiles. Examples of automobiles include motorcycles, cars, trucks, buses, vans, minivans, ATVs (all-terrain vehicles), and electric carts for disabled persons. Vehicles may include rail vehicles. Examples of rail vehicles include trains and trams. Vehicles may include ships. Examples of ships include ships, boats, and underwater vehicles. Vehicles may include amphibious vehicles. Examples of amphibious vehicles include screw-propeller vehicles and hovercraft. Vehicles may include aircraft. Examples of aircraft include airplanes, helicopters, and light aircraft. Vehicles may include spacecraft. Machinery may correspond to the end product of a product ecosystem.

[0045] Identifier elements may be associated with or linked to machines. Identifier elements may be associated with or linked to machine fluids or machine fluid packaging. Identifier elements may be associated with or linked to machines or machine fluids, respectively, with respect to the production of at least the machine or machine fluid. Digital twins of machines or machine fluids may be accessible through distributed networks via identifier elements. Digital twins of machines may contain status data. Digital twins of machine fluids may contain status data. Digital twins of machine fluids may contain further data about the machine fluids (hereinafter referred to as machine fluid data). A digital twin may contain one or more datasets. One or more datasets may contain status data. One or more datasets may contain machine fluid data. One or more datasets may be associated with their respective distributed identifiers (e.g., distributed machine identifiers or distributed machine fluid identifiers). One or more datasets may contain or be associated with dataset identifiers. This allows for the unique identification of datasets in a digital twin. Identifier elements may be uniquely associated with machines or machine fluids. Identifier elements may be uniquely associated with digital machine or machine-fluid identifiers. Digital machine or machine-fluid identifiers may be uniquely associated with machines or machine-fluids. Thus, status data and machine-fluid data may be provided for each machine / machine-fluid or for individual machines / machine-fluids. A machine identifier may include one or more distributed machine identifiers uniquely associated with a machine. A machine identifier may include one or more distributed machine-fluid identifiers uniquely associated with a machine-fluid. A machine identifier may be associated with one or more distributed machine identifiers representing a digital twin of the physical entity of a machine. A machine-fluid identifier may be associated with one or more distributed machine-fluid identifiers representing a digital twin of the physical entity of a machine-fluid. Distributed machine identifiers and distributed machine-fluid identifiers may be digital identifiers of a distributed network or digital identifiers for a distributed network. Distributed machine identifiers and distributed machine-fluid identifiers may be digital identifiers provided to a distributed network and its participant nodes.Therefore, a distributed machine identifier may represent the physical entity of a machine in a distributed network, and an involved node may be able to interpret the relationship between the distributed machine identifier and the physical entity of the machine in the material chain. Similarly, a distributed machine fluid identifier may represent the physical entity of a machine fluid in a distributed network, and an involved node may be able to interpret the relationship between the distributed machine fluid identifier and the physical entity of the machine fluid in the material chain.

[0046] A distributed machine identifier may include any unique identifier uniquely associated with a machine. A distributed machine identifier may include one or more universally unique identifiers (UUIDs) or digital identifiers (DIDs). A distributed machine identifier may be issued by a central or distributed identity issuer. A distributed machine identifier may include authentication information. Access to machine data, including status data, may be controlled by the machine producer through the distributed machine identifier and the unique association between the distributed machine identifier and the machine. This is in contrast to a centralized authority scheme, where the identifier is provided by such centralized authority and access to data is controlled by such centralized authority. In this context, distributed refers to the use of distributed identifiers that are controlled by data owners, such as machine producers or machine owners.

[0047] A distributed machine identifier may include one or more identifiers used in a distributed network that enable data exchange across the distributed network. Data exchange may include the discovery of distributed machine identifiers of network nodes in the distributed network, the authentication of network nodes in the distributed network, and / or authorization of data transfer via peer-to-peer communication between network nodes in the distributed network. A distributed machine identifier may be associated with stakeholders in the material chain, particularly the material loop, including input material suppliers, machine fluid producers, machine manufacturers, machine users, used machine collectors, and / or used machine recyclers. A distributed machine identifier may be associated with material entities in the material chain, particularly the material loop, including input materials, machine fluids, and / or machines.

[0048] Status data may indicate the status of a used mechanical fluid (e.g., used mechanical fluid). Status data associated with used mechanical fluid may relate to the characteristics of the used mechanical fluid and, optionally, the used machine. Status data may relate to the physical and / or chemical properties of the used mechanical fluid and, optionally, the used machine. Status data may include measurement data collected by one or more sensors. Measurement data may include transmittance data and / or viscosity data. Transmittance data may be analyzed to provide status data such as the degree of impurities. Viscosity data may be analyzed to provide status data such as the degree of wear. Status data may relate to the age of the used mechanical fluid, the operating time of the machine and the mechanical fluid, the mileage of the machine, previous maintenance work performed on the used mechanical fluid, or a combination thereof.

[0049] A distributed mechanical fluid identifier may include any unique identifier uniquely associated with a mechanical fluid. A distributed mechanical fluid identifier may include one or more universally unique identifiers (UUIDs) or digital identifiers (DIDs). A distributed mechanical fluid identifier may be issued by a central or distributed identity issuer. A distributed mechanical fluid identifier may include authentication information. Access to mechanical fluid data, such as status data, may be controlled by the mechanical fluid producer through the distributed mechanical fluid identifier and its unique association with the mechanical fluid.

[0050] A distributed mechanical fluid identifier may include one or more identifiers used in a distributed network and enabling data exchange across the distributed network. A distributed mechanical fluid identifier may be associated with stakeholders in the material chain, particularly the material loop, including input material suppliers, mechanical fluid producers, machine manufacturers, machine users, used machine recovery companies, and / or used machine recyclers. A distributed mechanical fluid identifier may be associated with material entities in the material chain, particularly the material loop, including input materials, mechanical fluids, and / or machines.

[0051] Distributed machine identifiers and distributed machine fluid identifiers can be digital identifiers. Therefore, distributed machine identifiers and distributed machine fluid identifiers may not correspond to physical identifiers physically attached to the machine fluid (such as the machine fluid packaging and the machine, respectively).

[0052] Data collection may include reading or receiving various types of data, such as machine fluid data and status data.

[0053] Mechanical fluids may be associated with access elements via distributed mechanical fluid identifiers. Access elements may include a digital representation of status data, an authentication mechanism, and / or a distributed mechanical fluid identifier. Access elements may be generated for collected status data or a portion thereof. For example, an access element may be generated for at least a portion of a dataset generated from collected status data. A digital representation of status data may be provided to a distributed network. A digital representation of status data may be provided by a distributed network node associated with a mechanical fluid producer's dedicated storage. Dedicated storage may store status data or datasets generated from status data. Dedicated storage may be under the control of, or controlled by, the data owner of the status data, such as a mechanical fluid producer. The data owner may control access to the dedicated storage. Access may be controlled via a distributed network node associated with such storage. A digital representation may include a representation of the status data or a portion thereof (e.g., a dataset containing status data). A digital representation may include a locator or pointer to dedicated storage or a dedicated storage address associated with a mechanical fluid producer. The pointer or locator may directly point to the dedicated storage or storage address. A pointer or locator may point to a data-serving network node associated with the dedicated storage. This may improve data security because the dedicated storage address is not exposed to further participants in the distributed network, thus avoiding the risk of direct access to the dedicated storage without access control via the distributed data-serving network node. The digital representation may include one or more digital links pointing to status data. The digital representation may include a locator or pointer, e.g., a URL or URI, to a dedicated storage address associated with a mechanical fluid producer that stores status data. The digital representation may include a representation for accessing the status data or a portion thereof.

[0054] One or more authentication mechanisms may be associated with distributed mechanical fluid identifiers and digital representations. An access element may be associated with one or more authorization mechanisms, each associated with a distributed mechanical fluid identifier and a dataset containing at least a portion of the mechanical fluid monitoring data. One or more authorization mechanisms may include authorization rules that determine whether access to the mechanical fluid monitoring data is permitted. One or more authorization mechanisms may be associated with data provision network nodes associated with mechanical fluid producers.

[0055] A machinery ecosystem may encompass various chains, including manufacturing, use, and reuse. In these chains, one or more ecosystem stakeholders may contribute to the manufacture, use, or reuse of machinery and machinery fluids. For example, the production chain may include raw material manufacturers, machinery fluid manufacturers, and / or machinery manufacturers. Furthermore, for example, the use chain may include machinery users, machinery repairers, and / or machinery dealers. Furthermore, for example, the reuse chain may include collectors, sorters, recyclers, restorers, and / or refurbishers.

[0056] Participants in a machine ecosystem may be connected via a distributed network. The distributed network may include one or more distributed network nodes configured to perform data transactions. Distributed network nodes may be associated with participants in a product ecosystem. Data transactions may be based on transaction protocols that include authentication and / or authorization mechanisms. Based on the authentication and / or authorization mechanisms, a peer-to-peer network may be established between the distributed network nodes of the distributed network.

[0057] One or more authentication mechanisms may be associated with or linked to a distributed identifier (e.g., a distributed machine identifier and / or a distributed machine-fluid identifier). One or more authentication mechanisms associated with a distributed identifier may be provided to a distributed network node. One or more authentication mechanisms associated with a distributed identifier may be accessible by a distributed network node. The distributed configuration enables more efficient use of computing resources and enhances control by each data owner in the distributed network.

[0058] Data-serving network nodes may be configured to provide access to data stored in dedicated storage associated with each data-serving network node. Data-serving network nodes may be associated with stakeholders in the machinery production chain, such as producers of mechanical fluids and manufacturers of machinery. Data generated by stakeholders in the production chain at each stage of production may be provided to the distributed network by data-serving network nodes, particularly for access by data-consuming network nodes. Access to the data may be under the control of the data-serving network node associated with that data. Data-serving network nodes may be configured to authenticate data-consuming network nodes and / or to authorize data-consuming network nodes to access the data.

[0059] A data consumption network node may be configured to request access to data stored in dedicated storage associated with a data provision network node. Data consumption network nodes may be associated with stakeholders in the production chain, such as mechanical fluid producers and machinery manufacturers, and / or stakeholders in the usage chain, such as machinery repairers. At each stage of the production chain, data generated by stakeholders in the production chain may be accessed by the data consumption network node once authenticated and / or authorized.

[0060] Waste mechanical fluid may include mechanical fluid that can no longer be used as intended in a machine and therefore needs to be replaced. Waste mechanical fluid may be sorted by machine maintenance equipment and / or provided to sorting equipment for sorting. Sorting of waste mechanical fluid may provide a mechanical fluid waste fraction. A mechanical fluid waste fraction may include mechanical fluid sorted by one or more types of mechanical fluid. A waste fraction may be tailored to a specific mechanical fluid producer (e.g., may include only mechanical fluid types produced by that producer) or to a recycling process. A mechanical fluid waste fraction may relate to mechanical fluid waste fractions that will be processed by a physical recycling process (e.g., a recycling process involving physical treatment such as separation and distillation). A mechanical fluid waste fraction may relate to mechanical fluid waste fractions that will be processed by a chemical recycling process (e.g., a recycling process involving chemical reactions carried out on the waste mechanical fluid). A mechanical fluid waste fraction may relate to mechanical fluid waste fractions that will be processed by both physical and chemical recycling processes. Mechanical fluid waste fractions may be related to mechanical fluid waste fractions that will be processed by a thermal recycling process.

[0061] Sorting data for separating waste mechanical fluid into assigned mechanical fluid waste fractions may include control signals for controlling sorting equipment configured to separate waste mechanical fluid into mechanical fluid waste fractions. Sorting data for separating waste mechanical fluid into assigned mechanical fluid waste fractions may include sorting commands provided to applications used by users, such as machine maintenance equipment. Fraction control data may be associated with individual mechanical fluids. Fraction control data may associate individual mechanical fluids with specific mechanical fluid waste fractions. Mechanical fluid waste fractions may be associated with spatially separated fractions for sorting waste mechanical fluid.

[0062] The identifier element for each machine may be associated with at least one distributed machine identifier associated with a machine containing waste machine fluid. The identifier element may include any physical configuration that associates the machine identifier with the machine. The identifier element may include, but is not limited to, passive or active elements, such as QR codes® or RFID tags. The identifier element may be a physical identifier physically attached to the machine or at least one component of the machine. The identifier element may include a marker embedded in a material, a barcode, a QR code, a tag such as an RFID tag, or a similar physical configuration that enables digital identification of the machine.

[0063] Identifier elements may be uniquely associated with a machine. Identifier elements may be uniquely associated with a digital machine identifier. Digital machine identifiers may be uniquely associated with a machine. In this way, machine fluid data may be provided per machine or for individual machines. A machine identifier may include one or more distributed machine identifiers uniquely associated with a machine, as described above. A machine identifier may be associated with one or more distributed machine identifiers.

[0064] In one embodiment, the mechanical fluid is selected from the group consisting of lubricants, engine coolants, and working fluids. The engine coolant may be a heat exchange medium. The working fluid may be brake fluid.

[0065] Lubricants are typically substances that can reduce friction between surfaces (preferably metal surfaces), such as mechanical devices or the surfaces of machines. Mechanical devices can be mechanisms consisting of devices that operate on mechanical principles, such as the machines described above. Lubricants are typically lubricating fluids, lubricating oils, or lubricating greases.

[0066] Lubricants include light, medium, and heavy load engine oils, industrial engine oils, marine engine oils, automotive engine oils, crankshaft oils, compressor oils, refrigeration oils, hydrocarbon compressor oils, ultra-low temperature lubricants, high temperature lubricants, wire rope lubricants, textile machine oils, refrigeration oils, aviation and aerospace lubricants, aviation turbine oils, transmission oils, gas turbine oils, spindle oils, spin oils, traction fluids, transmission oils, plastic transmission oils, passenger car transmission oils, truck transmission oils, industrial transmission oils, and industrial It can be used in a variety of applications, including gear oil, insulating oil, instrument oil, brake fluid, transmission oil, shock absorber oil, thermal dispersion oil, transformer oil, greases, chain oil, minimum volume lubricants for metalworking, hot and cold working oils, water-based metalworking fluid oils, neat-oil metalworking fluid oils, semi-synthetic metalworking fluid oils, synthetic metalworking fluid oils, excavation detergents for soil exploration, hydraulic oils, biodegradable lubricants or lubricating greases or waxes, chainsaw oils, mold release agents, molding fluids, lubricants for guns, pistols, rifles or watches, and food-grade approved lubricants.

[0067] The lubricant is applied in an amount of at least 10, 50, 100, 150, 200, 300, 400, 500, 600, 900, 1400, or 2000 mm 2 It may have a kinematic viscosity of / s at 40°C. Alternatively, the lubricant may have a kinematic viscosity of 200-30,000 mm at 40°C. 2 / s(cSt), preferably 500~10,000mm 2 / s, especially 1000~5000mm 2 It may have a kinematic viscosity of / s.

[0068] The lubricant should be applied in an amount of at least 2, 3, 5, 10, 20, 30, 40, or 50 mm 2 It may have a kinematic viscosity of 100°C of / s. In another embodiment, the lubricant may have a kinematic viscosity of 10 to 5000 mm at 100°C. 2 / s(cSt), preferably 30-3000mm 2 It can have a kinematic viscosity of 50-2000 mm² / s, particularly 50-2000 mm² / s.

[0069] The lubricant may have a viscosity index (VI) of at least 150, 160, 170, 180, 190, or 200.

[0070] The lubricant may comprise a lubricant base oil and one or more lubricant additives. The lubricant may comprise, in relation to the total amount of the lubricant, 50% to 99% by weight of the base oil, or 80% to 99% by weight, or 90% to 99% by weight of the base oil.

[0071] Suitable lubricant base oils may be selected from the group consisting of mineral oils (oils of Group I, II, or III), polyalphaolefins (oils of Group IV), polymerized and copolymerized olefins, alkylnaphthalenes, alkylene oxide polymers, silicone oils, phosphate esters, and carboxylic acid esters (oils of Group V). The definition of base oil is the same as that given in the American Petroleum Institute (API) publication "Engine Oil Licensing and Certification System," Industry Services Department, Fourteenth Edition, December 1996, Addendum 1, December 1998. The said publication classifies base oils as follows: a. Group I base oils contain less than 90% saturated matter (ASTM D 2007) and / or more than 0.03% sulfur (ASTM D 2622), and have a viscosity index of 80 or more and less than 126 (ASTM D 2270). b. Group II base oils contain 90% or more saturated material and 0.03% or less sulfur, and have a viscosity index of 80 or more and less than 126. c. Group III base oils contain 90% or more saturated material and 0.03% or less sulfur, and have a viscosity index of 126 or higher. d. The base oil of Group IV contains polyalphaolefins. Known PAO materials include polyalphaolefins (PAOs), which typically include relatively low molecular weight hydrogenated polymers or oligomers of alphaolefins, including but not limited to C2 to about C32 alphaolefins, with C8 to C16 alphaolefins such as 1-octene, 1-decene, and 1-dodecene being preferred. Preferred polyalphaolefins are poly-1-octene, poly-1-decene, and poly-1-dodecene. e. Group V base oils include any base oils not listed in Groups I through IV. Examples of Group V base oils include alkylnaphthalenes, alkylene oxide polymers, silicone oils, carboxylic acid esters, and phosphate esters.

[0072] Examples of synthetic base oils include hydrocarbon oils and halo-substituted hydrocarbon oils, such as polymerized and copolymerized olefins (e.g., polypropylene, propylene-isobutylene copolymer, chlorinated polybutylene, poly(1-hexene), poly(1-octene), poly(1-decene)); alkylbenzenes (e.g., dodecylbenzene, tetradecylbenzene, dinonylbenzene, di(2-ethylhexyl)benzene); polyphenyls (e.g., biphenyl, terphenyl, alkylated polyphenols); alkylated diphenyl ethers and alkylated diphenyl sulfides, as well as their derivatives, analogs, and congeners.

[0073] Examples of synthetic base oils include alkylene oxide polymers in which terminal hydroxyl groups are modified by esterification, etherification, etc., as well as their interpolymers and derivatives. These include polyoxyalkylene polymers prepared by polymerization of ethylene oxide or propylene oxide, and alkyl and aryl ethers of polyoxyalkylene polymers (e.g., methyl-polyisopropylene glycol ether with a molecular weight of 1000 or diphenyl ether of polyethylene glycol with a molecular weight of 1000 to 1500); and their mono and polycarboxylic acid esters, such as acetate ester of tetraethylene glycol, mixed C3-C8 fatty acid esters and C3-C8 fatty acid esters. 13 This is exemplified by oxo acid diesters.

[0074] Examples of synthetic base oils include silicone-based oils such as polyalkyl-, polyaryl-, polyalkoxy-, or polyaryloxysilicone oils. Examples include tetraethyl silicate, tetraisopropyl silicate, tetra-(2-ethylhexyl) silicate, tetra-(4-methyl-2-ethylhexyl) silicate, tetra-(p-tert-butylphenyl) silicate, hexa-(4-methyl-2-ethylhexyl) disiloxane, poly(methyl)siloxane, and poly(methylphenyl)siloxane. Other synthetic base oils include liquid esters of phosphorus-containing acids (e.g., tricresyl phosphate, trioctyl phosphate, diethyl esters of decylphosphonic acid) and high molecular weight tetrahydrofuran.

[0075] Examples of carboxylic acid ester base oils include esters of monobasic acids and polybasic acids with monoalcohols (simple esters), or esters of monoalcohols and mixtures of polyalcohols (complex esters), and esters of monocarboxylic acids with polyols (simple esters), or esters of mixtures of monocarboxylic acids and polycarboxylic acids (complex esters). Examples of monobasic / polybasic type esters include esters of monocarboxylic acids such as heptanoic acid, and dicarboxylic acids such as phthalic acid, succinic acid, alkyl succinic acid, alkenyl succinic acid, maleic acid, azelaic acid, suberic acid, sebacic acid, fumaric acid, adipic acid, linoleic acid dimer, malonic acid, alkyl malonic acid, alkenyl malonic acid, and esters of these with various alcohols such as butyl alcohol, hexyl alcohol, dodecyl alcohol, 2-ethylhexyl alcohol, or mixtures of these with polyalcohols. Specific examples of these types of esters include nonyl heptanoate, dibutyl adipate, di(2-ethylhexyl) sebacate, di-n-hexyl fumarate, dioctyl sebacate, diisooctyl azelate, diisodecyl azelate, dioctyl phthalate, didecyl phthalate, dieicosyl sebacate, dibutyl-TMP-adipate, and the like.

[0076] Suitable carboxylic acid ester base oils can be obtained by reacting one or more polyhydric alcohols, preferably hindered polyols such as neopentyl polyols, for example, neopentyl glycol, trimethylolethane, 2-methyl-2-propyl-1,3-propanediol, trimethylolpropane, trimethylolbutane, pentaerythritol, and dipentaerythritol, with monocarboxylic acids containing at least 4 carbons, usually C5-C 30 acids, for example, saturated straight-chain fatty acids including caprylic acid, capric acid, lauric acid, myristic acid, palmitic acid, stearic acid, arachidic acid, and behenic acid, or corresponding branched-chain fatty acids or unsaturated fatty acids such as oleic acid, or mixtures of these with polycarboxylic acids.

[0077] Lubricant additives may be selected from viscosity index improvers, polymer thickeners, corrosion inhibitors, cleaning agents, dispersants, defoamers, dyes, wear protection additives, extreme pressure additives, wear-resistant additives, friction modifiers, metal deactivators, pour point depressants, and deemulsifiers. The total amount of lubricant additives in the lubricant may range from 0 to 25% by weight, or 0.01 to 20% by weight, or 0.1 to 15% by weight, or 0.5 to 10% by weight, or 1 to 5% by weight of the total amount of lubricant.

[0078] Viscosity index improvers may include high molecular weight polymers that increase the relative viscosity of an oil at high temperatures compared to its relative viscosity at low temperatures. Examples of viscosity index improvers include polyacrylates, polymethacrylates, alkyl methacrylates, vinylpyrrolidone / methacrylate copolymers, polyvinylpyrrolidone, polybutene, olefin copolymers, e.g., ethylene-propylene copolymer or styrene-butadiene copolymer, or polyalkenes, e.g., PIB, styrene / acrylate copolymer, and polyethers, as well as combinations thereof. The most common viscosity index improvers are methacrylate polymers and copolymers, acrylate polymers, olefin polymers and copolymers, and styrene-butadiene copolymer. Other examples of viscosity index improvers include polymethacrylates, polyisobutylene, alpha-olefin polymers, alpha-olefin copolymers (e.g., ethylene-propylene copolymer), polyalkylstyrene, phenol condensates, naphthalene condensates, and styrene-butadiene copolymer. Of these, polymethacrylates having a number average molecular weight of 10,000 to 300,000 and alpha-olefin polymers or alpha-olefin copolymers having a number average molecular weight of 1,000 to 30,000, particularly ethylene-alpha-olefin copolymers having a number average molecular weight of 1,000 to 10,000, are preferred. Viscosity index improvers can be added and used, either alone or in mixtures, in amounts conveniently ranging from 0.05% to 20.0% by weight relative to the weight of the base stock.

[0079] Suitable (polymeric) thickeners include, but are not limited to, polyisobutene (PIB), oligomer copolymer (OCP), polymethacrylate (PMA), styrene-butadiene copolymer, or high-viscosity esters (compound esters).

[0080] Examples of corrosion inhibitors include various oxygen-containing materials, nitrogen-containing materials, sulfur-containing materials, and phosphorus-containing materials, as well as metal-containing compounds (salts, organometallics, etc.) and non-metal-containing or ashless materials. Examples of corrosion inhibitors include hydrocarbyl-, aryl-, alkyl-, arylalkyl-, and alkylaryl-type cleaning agents (neutral, overbasic), sulfonates, phenates, salicylates, alcoholates, carboxylates, salixalates, phosphates, phosphates, thiophosphates, amines, amine salts, amine phosphates, amine sulfonates, alkoxylated amines, etheramines, polyetheramines, amides, imides, azoles, diazoles, triazoles, benzotriazoles, benzothiadols, and methylamines. Examples of additive types include, but are not limited to, captobenzothiazole, toltriazole (TTZ type), heterocyclic amines, heterocyclic sulfides, thiazoles, thiadiazoles, mercaptothiadiazoles, dimercaptothiadiazoles (DMTD type), imidazoles, benzimidazoles, dithiobenzimidazoles, imidazolines, oxazolines, Mannich reaction products, glycidyl ethers, anhydrides, carbamates, thiocarbamates, dithiocarbamates, polyglycols, or mixtures thereof.

[0081] Detergents may include those that adhere to dirt particles and prevent them from adhering to the critical surface. Detergents can also adhere to the metal surface itself to keep it clean and prevent corrosion. Detergents include calcium alkyl salicylate, calcium alkyl phenate, and calcium alkali sulfonate, with alternative metal ions such as magnesium, barium, or sodium being used. Examples of usable detergents and dispersants include metal-based detergents such as neutral and basic alkaline earth metal sulfonates, alkaline earth metal phenates, and alkaline earth metal salicylates, alkenyl succinimides and alkenyl succinimide esters and their borohydrogen, phenate, and Salienius complex detergents, and ashless dispersants modified with sulfur compounds. These agents can be added and used individually or in mixtures, preferably in amounts ranging from 0.01% to 1.0% by weight relative to the weight of the base stock; they may also be high total base number (TBN), low TBN, or high / low TBN mixtures.

[0082] Dispersants are lubricant additives that help prevent the formation of sludge, varnish, and other deposits on critical surfaces. Dispersants can be succinimide dispersants (e.g., N-substituted long-chain alkenyl succinimides), Mannich dispersants, ester-containing dispersants, condensation products of fatty hydrocarbyl monocarboxylic acid acylating agents with amines or ammonia, alkylaminophenol dispersants, hydrocarbyl-amine dispersants, polyether dispersants, or polyetheramine dispersants. In one embodiment, a succinimide dispersant is a polyisobutylene-substituted succinimide, in which case the polyisobutylene from which the dispersant is derived may have a number average molecular weight of about 400 to about 5000, or about 950 to about 1600. In one embodiment, a borate dispersant is a succinimide dispersant. Typically, borate dispersants include succinimide dispersants, including polyisobutylene succinimide, in which case the polyisobutylene from which the dispersant is derived may have a number average molecular weight of about 400 to about 5000. The borate dispersant is described in more detail in the section on extreme pressure agents mentioned above.

[0083] The defoaming agent may be selected from silicones, polyacrylates, and the like. The amount of defoaming agent in the lubricant composition described herein may be in the range of 0.001% by weight or more to 0.1% by weight or less, based on the total weight of the formulation. As a further example, the defoaming agent may be present in an amount of about 0.004% by weight or about 0.008% by weight.

[0084] Suitable extreme pressure additives include sulfur-containing compounds. These sulfur-containing compounds may be sulfurized olefins, polysulfides, or mixtures thereof. Examples of sulfurized olefins include sulfurized olefins derived from propylene, isobutylene, and pentene; polysulfides containing organic sulfides and / or benzyl disulfides; bis-(chlorobenzyl) disulfide; dibutyltetrasulfide; di-tert-butyl polysulfide; and sulfurized methyl esters of oleic acid, sulfurized alkylphenols, sulfurized dipentene, sulfurized terpenes, sulfurized Diels-Alder adducts, alkylsulfenyl N'N-dialkyldithiocarbamates, or mixtures thereof. In one embodiment, sulfurized olefins include sulfurized olefins derived from propylene, isobutylene, pentene, or mixtures thereof. In one embodiment, sulfur-containing compounds of the extreme pressure additive include dimercaptothiadiazole or its derivatives, or mixtures thereof. Examples of dimercaptothiadiazoles include compounds such as 2,5-dimercapto-1,3,4-thiadiazole or hydrocarbyl-substituted 2,5-dimercapto-1,3,4-thiadiazole or their oligomers. Oligomers of hydrocarbyl-substituted 2,5-dimercapto-1,3,4-thiadiazole are typically formed by forming sulfur-sulfur bonds between 2,5-dimercapto-1,3,4-thiadiazole units to form two or more derivatives or oligomers of the thiadiazole units. Suitable 2,5-dimercapto-1,3,4-thiadiazole derivatives include, for example, 2,5-bis(tert-nonyldithio)-1,3,4-thiadiazole or 2-tert-nonyldithio-5-mercapto-1,3,4-thiadiazole. The number of carbon atoms in the hydrocarbyl substituent of hydrocarbyl-substituted 2,5-dimercapto-1,3,4-thiadiazole typically includes 1 to 30, 2 to 20, or 3 to 16. Examples of extreme pressure additives include compounds containing boron and / or sulfur and / or phosphorus. The extreme pressure additive may be present in the lubricant composition at a concentration of 0% to about 20% by weight, or about 0.05% to about 10.0% by weight, or about 0.1% to about 8% by weight.

[0085] Examples of wear-resistant additives include organic borates, organic phosphites such as didodecyl phosphite, organic sulfur-containing compounds such as sperm whale oil or sulfur terpenes, zinc dialkyldithiophosphates, zinc diaryldithiophosphates, phosphosulfur hydrocarbons, and any combination thereof.

[0086] Examples of friction modifiers include metal-containing compounds or materials, ashless compounds or materials, or mixtures thereof. Metal-containing friction modifiers include metal salts or metal ligand complexes, in which case the metal may be an alkali metal, an alkaline earth metal, or a transition metal. Such metal-containing friction modifiers may also have low ash content properties. Examples of transition metals include Mo, Sb, Sn, Fe, Cu, and Zn. Examples of ligands include alcohols, polyols, glycerols, partially ester glycerols, thiols, carboxylates, carbamates, thiocarbamates, dithiocarbamates, phosphates, thiophosphates, dithiophosphates, amides, imides, amines, thiazoles, thiadiazoles, dithiazoles, diazoles, triazoles, and hydrocarbyl derivatives of other polar molecular functional groups containing effective amounts of O, N, S, or P, either alone or in combination. Specifically, Mo-containing compounds, such as Mo-dithiocarbamate, Mo(DTC), Mo-dithiophosphate, Mo(DTP), Mo-amine, Mo(Am), Mo-alcolate, and Mo-alcohol-amide, may be particularly effective. Examples of ashless friction modifiers include lubricant materials containing an effective amount of polar groups, such as hydroxyl-containing hydrocarbyl base oils, glycers, partial glycers, and glyceride derivatives. Examples of polar groups in friction modifiers include hydrocarbyl groups containing an effective amount of O, N, S, or P, either individually or in combination. Other friction modifiers that may be particularly effective include, for example, fatty acid salts (both ash-containing and ashless derivatives), fatty alcohols, fatty amides, fatty esters, hydroxyl-containing carboxylates, and equivalent synthetic long-chain hydrocarbyl acids, alcohols, amides, esters, and hydroxycarboxylates. In some cases, fatty organic acids, fatty amines, and sulfurized fatty acids may be used as suitable friction modifiers. Examples of friction modifiers include fatty acid esters and amides, organic molybdenum compounds, molybdenum dialkylthiocarbamates, and molybdenum dialkyldithiophosphates.

[0087] Suitable metal deactivators include benzotriazoles and their derivatives, such as 4- or 5-alkylbenzotriazoles (e.g., triazoles) and their derivatives, 4,5,6,7-tetrahydrobenzotriazoles, and 5,5'-methylenebisbenzotriazoles, Mannich bases of benzotriazoles or triazoles, such as 1-[bis(2-ethylhexyl)aminomethyl)triazoles and 1-[bis(2-ethylhexyl)aminomethyl)benzotriazoles, and alkoxyalkylbenzotriazoles, such as 1-(nonyloxymethyl)benzotriazoles, 1-(1-butoxyethyl)benzotriazoles, and 1-(1-cyclohexyloxybutyl)triazoles, as well as combinations thereof. Additional non-limiting examples of one or more metal deactivators include 1,2,4-triazoles and their derivatives, e.g., 3-alkyl(or aryl)-1,2,4-triazoles, and Mannich bases of 1,2,4-triazoles such as 1-[bis(2-ethylhexyl)aminomethyl-1,2,4-triazole], alkoxyalkyl-1,2,4-triazoles such as 1-(1-butoxyethyl)-1,2,4-triazole, and acylated 3-amino-1,2,4-triazoles, imidazole derivatives, e.g., 4,4'-methylenebis(2-undecyl-5-methylimidazole) and bis[(N-methyl)imidazole-2-yl]carbinol octyl ethers, and combinations thereof. Further non-limiting examples of one or more metal deactivators include sulfur-containing heterocyclic compounds, such as 2-mercaptobenzothiazole, 2,5-dimercapto-1,3,4-thiadiazole and its derivatives, and 3,5-bis-[di(2-ethylhexyl)aminomethyl]-1,3,4-thiadiazolin-2-one, and combinations thereof. Further non-limiting examples of one or more metal deactivators include amino compounds, such as salicylidenepropylenediamine, salicyaminoguanidine and its salts, and combinations thereof.The amount of one or more metal deactivators in the composition is not particularly limited, but is typically present in amounts of about 0.01 to about 0.1% by weight, about 0.05 to about 0.01% by weight, or about 0.07 to about 0.1% by weight, based on the weight of the composition. Alternatively, one or more metal deactivators may be present in amounts of less than about 0.1% by weight, less than about 0.7% by weight, or less than about 0.5% by weight, based on the weight of the composition.

[0088] Examples of pour point depressants (PPDs) include polymethacrylates, alkylated naphthalene derivatives, and combinations thereof. Commonly used additives, such as alkyl aromatic polymers and polymethacrylates, are also useful for this purpose. Typically, the treatment rate is in the range of ≥0.001% to ≤1.0% by weight relative to the weight of the base stock.

[0089] Examples of deemulsifiers include trialkyl phosphates, as well as various polymers and copolymers of ethylene glycol, ethylene oxide, and propylene oxide, or mixtures thereof.

[0090] The engine coolant may contain alkylene glycol, water, and additives. The alkylene glycol may be selected from monoethylene glycol. Suitable additives include corrosion inhibitors, antifreezes, defoamers, bittering agents, and colorants.

[0091] The working fluid may contain a mixture of alkyl oligoalkylene glycol borate and oligoalkylene glycol, and additives. Suitable additives include corrosion inhibitors and defoamers.

[0092] In one embodiment, the use trigger is provided by the machine manufacturer, or the machine user, or the machine maintenance facility. The use trigger may be generated by at least one node in a distributed network. Such a node may be associated with the machine manufacturer, or the machine user, or the machine maintenance facility. The use trigger may include at least one distributed machine identifier associated with the used machine. The use trigger may be generated when the physical identifier associated with the machine is read. The physical identifier may be linked to or physically attached to the machine, for example, via an identification number, an electronic tag such as an RFID tag, or a code such as a QR code. The physical identifier may be linked to a distributed machine identifier associated with the machine. The distributed machine identifier associated with the machine may be provided for the generation of the use trigger.

[0093] In one embodiment, the usage trigger is provided based on a predetermined criterion. The predetermined criterion may include a predetermined usage period, a predetermined location, and / or a predetermined event. The predetermined event may include performing maintenance work on the used machine.

[0094] In one embodiment, status data may include at least one physical and / or chemical property of the used mechanical fluid, at least one physical and / or chemical property of the used machine, maintenance data related to maintenance work performed on the mechanical fluid, location associated with the maintenance work, or a combination thereof. Chemical properties may be properties of the mechanical fluid that become apparent during or after a chemical reaction. Thus, chemical properties may be any quality that can only be established by altering the chemical identity of the mechanical fluid. Examples of chemical properties include heat of combustion, toxicity, chemical stability in a given environment, flammability, corrosiveness, acidity and basicity, mechanical fluid material composition, recyclable content used to produce or manufacture the mechanical fluid, biobase content used to produce or manufacture the mechanical fluid, renewable material content used to produce or manufacture the mechanical fluid, and / or pH value. Physical properties may be any measurable properties. Thus, values ​​of physical properties describe the condition of the vehicle or a part thereof. Examples of physical properties include boiling point, color, density, ductility, distribution, refractive index, solubility, temperature, transmittance, and / or viscosity.

[0095] In one embodiment, status data is collected from one or more data-providing network nodes associated with machine manufacturers and / or machine users and / or machine maintenance facilities connected via a distributed network, and the data-providing network nodes from which status data is collected are selected based on a distributed machine identifier associated with the machine.

[0096] A distributed machine identifier can associate a machine's physical entity with status data. This status data may be related to historical information collected at different points in time during the machine's use. The status data may be stored by or in connection with one or more nodes associated with participants in the machine ecosystem. The status data may be distributed across multiple nodes in a distributed network associated with different participants in the machine ecosystem.

[0097] A distributed network may be configured to provide access to status data stored by one or more nodes associated with at least one participant in the machine ecosystem. Access may be provided in accordance with a distributed network protocol, including authentication and / or authorization. Status data collection may include providing at least one request to one or more nodes associated with a participant in the machine ecosystem, based on a distributed machine identifier.

[0098] In one embodiment, providing one or more distributed mechanical fluid identifiers includes collecting at least a portion of the identifiers from existing mechanical fluid data associated with the mechanical fluid. The existing mechanical fluid data may correspond to a digital twin of the mechanical fluid or a portion thereof. The digital twin may include distributed mechanical fluid identifiers and mechanical fluid data. At least a portion of the mechanical fluid identifiers contained in the digital twin may be collected. The digital twin may be generated during or after the production of the mechanical fluid. The existing mechanical fluid data may include data related to the production of the mechanical fluid. The data related to the production of the mechanical fluid may reside in one or more datasets. The datasets may be associated with a dataset identifier to enable unique identification of the datasets. The data related to the production of the mechanical fluid may include input data associated with one or more production inputs used to produce the mechanical fluid. The input data may include distributed input material identifiers associated with the production inputs. The data related to the production of the mechanical fluid may include relational expressions that specify the relationships between the production inputs used to produce the mechanical fluid. The existing mechanical fluid data may be stored in dedicated storage associated with the mechanical fluid producer, e.g., the data owner of the mechanical fluid data. Access to dedicated storage may be controlled by the mechanofluid producer (e.g., the data owner of the mechanofluid data storage within such storage). Access to dedicated storage may be controlled by the mechanofluid producer (e.g., the data owner of the mechanofluid data storage within such storage) via distributed network nodes associated with such storage. Providing one or more distributed mechanofluid identifiers may further include generating one or more further distributed mechanofluid identifiers, such as dataset identifiers associated with at least a portion of the collected status data. Further distributed mechanofluid identifiers may be generated by a central node or distributed nodes. Distributed nodes may be part of a distributed network.

[0099] In one embodiment, a method for monitoring a mechanical fluid further includes the step of determining at least one physical and / or chemical property of the mechanical fluid from at least a portion of the collected status data. For example, the degree of impurities may be determined from transmittance data included in the collected status data.

[0100] In one embodiment, a method for monitoring a mechanical fluid further includes the step of updating existing mechanical fluid data associated with the mechanical fluid using at least a portion of the collected status data and / or at least physical and / or chemical properties determined from the status. Updating may include associating at least a portion of the collected status data with distributed mechanical fluid identifiers associated with the existing mechanical fluid data. Updating may include generating one or more datasets containing at least a portion of the collected status data and associating the generated datasets with distributed mechanical fluid identifiers associated with the existing mechanical fluid data. Updating the existing mechanical fluid data makes it possible to maintain a correspondence between the digital twin of the mechanical fluid and the physical entities of the spent mechanical fluid so that the digital twin can at any time represent the current state of the physical entities of the spent mechanical fluid. Updating the existing mechanical fluid data makes it possible to generate maintenance data that takes into account the current state of the mechanical fluid, and thus make it possible to adapt the maintenance of the mechanical fluid to the current state without adversely affecting machine performance, while reducing the environmental impact by avoiding extra mechanical fluid maintenance work such as replacement or cleaning.

[0101] In one embodiment, a method for monitoring mechanical fluid further includes the step of generating one or more datasets, each dataset including at least a portion of the collected status data, and / or at least physical and / or chemical properties determined from the collected status data. Each dataset may further include a dataset identifier. Each dataset may further include, or be associated with, a distributed mechanical fluid identifier associated with existing mechanical fluid data (e.g., an existing digital twin of the mechanical fluid). Further steps may be performed before providing one or more distributed mechanical fluid identifiers. By generating different datasets, access rules used to control access to the status data can be defined separately for each dataset, thus enabling finer control over access to the collected status data.

[0102] A dataset may be associated with status data for each maintenance task or for each distributed participant identifier. Participant identifiers may be associated with data-consuming network nodes that request access to the status data. A maintenance task may be indicated by a maintenance task identifier. Distributed participant identifiers may be provided by data-consuming network nodes that request access to the status data. Maintenance task identifiers may be provided by data-providing network nodes that request access to the status data. Maintenance task identifiers may be provided by authorization rules that associate distributed participant identifiers associated with data-consuming network nodes that request access to the status data with the maintenance task identifier. Authorization rules may be associated with one or more datasets associated with status data for each maintenance task and / or for each distributed participant identifier.

[0103] In one embodiment, the access element relates to authorization rules that provide access to status data dependent on participant identifiers associated with reuse operations and / or participants in a distributed network performed on used machine fluids, and the access element is provided for access to status data, including data dependent on reuse operations and / or participant identifiers, by one or more data-consuming network nodes associated with one or more maintenance operators performing one or more reuse operations. Thus, access to sensitive data related to machine fluid maintenance operations may be restricted to specific network nodes to which data access is relevant, such as machine maintenance facilities.

[0104] Reuse operations may include cleaning operations performed on used mechanical fluids. These cleaning operations may remove impurities from the mechanical fluid. The success of the cleaning operation can be determined by measuring the permeability of the cleaned mechanical fluid. The cleaning operations may include processes well known in modern techniques for cleaning mechanical fluids.

[0105] In one embodiment of a method for generating maintenance data associated with the maintenance of used mechanical fluid, the collected mechanical fluid data includes work data with at least one predefined maintenance criterion. The predefined maintenance criteria may indicate that maintenance is required when such criteria are met. The criterion may be the degree of impurities and / or an SAE (Society of Automotive Engineers) class as defined by the standard SAE J300. Each SAE class may be associated with maximum and / or minimum viscosity. Viscosity may correspond to kinematic viscosity, high-temperature high-shear viscosity, and / or low-temperature characteristics. High-temperature high-shear viscosity may be measured by a tapered bearing simulator. Low-temperature characteristics may be measured by a cold cranking simulator and a mini rotational viscometer.

[0106] In one embodiment of a method for generating maintenance data associated with the maintenance of used mechanical fluids, collecting mechanical fluid data includes determining a distributed mechanical fluid identifier associated with the mechanical fluid based on a provided distributed mechanical identifier, and using at least a portion of the determined distributed mechanical fluid identifiers to collect mechanical fluid data from data-providing network nodes associated with the mechanical fluid data.

[0107] A distributed mechanical fluid identifier can be determined by a distributed network node. The distributed mechanical fluid identifier can also be determined by a further distributed network node that is in communication with a distributed network node that collects status data and mechanical fluid data. For example, a further distributed network node may determine a distributed mechanical fluid identifier and provide the determined identifier to the distributed network node. The distributed network node may then collect status data and mechanical fluid data based on the provided distributed mechanical fluid identifier.

[0108] Distributed machine fluid identifiers can be determined using relational expressions that specify the relationship between a machine and the machine fluid contained within it. Relational expressions can be directly or indirectly associated with distributed machine identifiers. This makes it possible to determine each relational expression using a distributed machine identifier. Relational expressions can specify that machine fluid may be used to produce a machine, and / or that a machine is produced using machine fluid. Relational expressions can be associated with the relationship between a machine and each material used to produce it, for example, using a distributed machine identifier and distributed identifiers associated with all materials used to produce the machine (e.g., distributed machine fluid identifiers). Relational expressions can be associated with the relationship between input and output materials of a single production step in a machine production chain. A machine production chain may include one or more production steps. A machine production chain may cover all production steps necessary to produce a machine. Relational expressions associated with a single production step can be linked to each other to reflect the entire machine production chain. Linking can be done by using distributed identifiers associated with input materials used in a production process and distributed identifiers associated with output materials resulting from the production process. Since the input materials of one production step correspond to the output materials of the previous production step, the relational representation of the previous production step is linked to the relational representation of the subsequent production step via its respective distributed material identifier. Such linking of relational representations can be used to obtain the bill of materials tree structure of a machine.

[0109] A relational representation can be accessed based on data associated with the relational representation. Data associated with a relational representation can be stored in a distributed registry accessible by a distributed network node that determines a distributed material identifier. A distributed network node may access the distributed registry using a distributed vehicle identifier to determine data associated with a relational representation associated with the distributed vehicle identifier. Data associated with a relational representation may include a distributed relational representation identifier and a digital representation pointing to each relational representation. A digital representation pointing to a relational representation may include at least one interface to a distributed data consumption network node associated with the relational representation. It may further include at least one interface to a distributed data consumption network node associated with the relational representation. It may include an endpoint for data exchange or sharing (resource endpoint) or an endpoint for service interaction (service endpoint), uniquely identified via a communication protocol. Therefore, a digital representation pointing to a relational representation can be uniquely associated with a distributed relational representation identifier and a distributed vehicle identifier. A digital representation pointing to a relational representation can be considered a locator indicating the location or dedicated data storage where each relational representation is stored.

[0110] The distributed network node may be configured to determine data associated with each relational expression based on a distributed machine identifier. For example, the distributed network node may be configured to read data associated with a relational expression from a distributed registry that stores the data associated with the relational expression associated with the distributed machine identifier, based on the distributed machine identifier. The distributed network node may be configured to access a relational expression from a distributed data-providing network node associated with the relational expression. The distributed data-providing network node associated with the relational expression may be associated with the machine producer. The relational expression may be stored in a storage environment associated with the distributed data-providing network node. The relational expression may be part of the machine data associated with the distributed machine identifier and stored in the storage environment associated with the distributed data-providing network node. The distributed data-providing network node may be associated with the data owner of the machine data. The distributed network node may be configured to determine the distributed identifiers contained in the accessed relational expression. If relational expressions are linked, the distributed network node may be configured to determine materials, such as machine fluids, used to produce the machine by recursively determining data associated with the linked relational expressions, access each relational expression using the determined data, and read the distributed identifiers associated with the materials used to produce the machine based on the accessed relational expression.

[0111] In one embodiment of a method for generating maintenance data associated with the maintenance of used machine fluid, correlating collected machine fluid data with accessed status data may include performing a data consistency operation on the collected machine fluid data and the accessed status data. If consistency is determined, this may indicate that the machine fluid is due for maintenance.

[0112] In one embodiment of a method for generating maintenance data associated with the maintenance of used mechanical fluid, the generated maintenance data includes data related to the mechanical fluid maintenance interval, data related to the maintenance work to be performed on the used mechanical fluid, data related to at least one physical and / or chemical property of the used mechanical fluid, or a combination thereof. The data related to the mechanical fluid maintenance interval may include data relating to the operating time or distance covered by the vehicle (e.g., driven and / or flown) when the maintenance work is due, and / or data relating to the remaining operating time or distance until the maintenance work is due. The date associated with the maintenance work may include a maintenance work identifier associated with the maintenance work to be performed. The maintenance work may include cleaning work.

[0113] In one embodiment of a method for performing one or more reuse operations on spent mechanical fluid, a machine-readable instruction for controlling reuse includes at least one distributed identifier associated with at least one device configured to perform the reuse operation, and at least one distributed mechanical fluid identifier associated with the spent mechanical fluid. The instruction may relate to cleaning the spent mechanical fluid. The instruction may relate to recovering at least one chemical material from the spent mechanical fluid, for example, recycling the spent mechanical fluid.

[0114] Control data may be configured to provide used mechanical fluid to chemical and / or physical processing plants associated with mechanical fluid producers or recyclers. Control data may be associated with one or more reuse operations performed on used mechanical fluid. Control data may be associated with chemical and / or physical processing of used mechanical fluid, such as cleaning, to enable further use of the mechanical fluid within the machine. Control data may be associated with chemical and / or physical processing of used mechanical fluid to recover chemical materials as a recyclable rate. Control data may be configured to initialize a process for performing at least one reuse operation on used mechanical fluid. Control data may be provided to one or more nodes in a distributed network, one or more nodes may be associated with reusers, for example, for cleaning and / or recycling. Control data may include specifications of reuse operations, such as cleaning and / or recycling methods, recycler identifiers, and / or mechanical fluid producer identifiers associated with the mechanical fluid producer that produced the used mechanical fluid. Based on the generated control data, a process for performing one or more reuse operations on used mechanical fluid, for example, to clean or recycle the used mechanical fluid, can be initialized and / or controlled.

[0115] In one embodiment of a method for sorting waste mechanical fluid, the mechanical fluid data includes status data. The status data may indicate the status of the used mechanical fluid in a used state. The status data associated with the used mechanical fluid may relate to the characteristics of the used mechanical fluid and, optionally, the used machine. The status data may relate to the physical and / or chemical properties of the used mechanical fluid and, optionally, the used machine. The status data may include measurement data collected by one or more sensors. The measurement data may include transmittance data and / or viscosity data. The transmittance data may be analyzed to provide status data such as the degree of impurities. The viscosity data may be analyzed to provide status data such as the degree of wear. The status data may relate to the age of the used mechanical fluid, the operating time of the machine and the mechanical fluid, the mileage of the machine, previous maintenance work performed on the used mechanical fluid, or a combination thereof.

[0116] In one embodiment of a method for sorting waste machine fluids, assigning waste machine fluids includes classification according to a classification command that associates machine fluid data with one or more machine fluid waste fractions. Classification enables data-driven sorting, simplifies the sorting process, and ensures the quality of the machine fluid waste fractions. The classification command may be configured to classify one or more waste machine fluids according to machine fluid data. This may include classifying one or more machine fluids into machine fluid waste fractions to be processed, based on machine-specific machine fluid data. Assigning one or more waste machine fluids to one or more machine fluid waste fractions may include providing a classification command configured to associate machine fluid data for each waste machine fluid with the waste fractions to be processed.

[0117] In one embodiment of a method for sorting waste mechanical fluids, assigning one or more waste mechanical fluids includes providing a classification command that collects a distributed mechanical fluid identifier for each mechanical fluid waste fraction based on mechanical fluid data for each waste mechanical fluid. The classification command can collect a distributed mechanical fluid identifier associated with a waste mechanical fluid according to the mechanical fluid waste fraction that will be processed by a specified mechanical fluid producer, a physical recycling process and / or a chemical recycling process and / or a recycling process involving physical and chemical treatment and / or a thermal recycling process, and the mechanical fluid waste fraction can be adjusted to the appropriate recycling process. The distributed mechanical fluid identifiers collected for each mechanical fluid and mechanical fluid waste fraction can be provided as sorting data for sorting one or more mechanical fluids. The location of the machine containing the waste mechanical fluid associated with the distributed mechanical fluid identifier for each machine and mechanical fluid waste fraction can be provided as sorting data for sorting one or more mechanical fluids. The sorting data can be provided to a sorting system configured to sort one or more mechanical fluids into their assigned mechanical fluid waste fractions. Sorting data may be provided to an interface configured to display sorting data to the user, such as machine fluid waste fractions associated with waste machine fluid contained in the machine. Assigning one or more machine fluids to one or more machine fluid waste fractions may include providing a classification command, which specifies the machine fluid waste fractions to be processed by a machine fluid recycler (such as a machine fluid producer), the recycling process for each machine fluid waste fraction, or a combination thereof. Assigning one or more machine fluids to one or more machine fluid waste fractions may include providing a classification command, which specifies the machine fluid waste fractions to be processed by the contaminants and / or decomposition level and / or machine fluid type for recycling.

[0118] In another embodiment of the method for sorting waste mechanical fluids, the mechanical fluid waste fraction may specify the fraction composition for each mechanical fluid waste fraction, the fraction history for each mechanical fluid waste fraction, the recycling process for each mechanical fluid waste fraction, or a combination thereof. The mechanical fluid waste fraction may specify the mechanical fluid composition, one or more contaminants for recycling, the content of each contaminant for recycling, the degradation level for each mechanical fluid type, the mechanical fluid producer, and / or the mechanical fluid type. Accessibility of data via a distributed network can extend the sorting depth and ensure more reliable sorting.

[0119] In one embodiment of a method for sorting waste mechanical fluids, sorting instructions are provided by one or more distributed network nodes associated with one or more mechanical fluid producers and / or one or more consumers of recycletes produced by implementing at least one recycling process on waste mechanical fluids. In this way, the sorting of waste mechanical fluid fractions can be tailored to the use of mechanical fluid prouders and / or recycletes, which also operate as recyclers. Additionally or alternatively, sorting instructions may be provided by one or more distributed network nodes associated with one or more recyclers operating recycling processes including physical and / or chemical or thermal treatments. In this way, the sorting of waste mechanical fluid fractions can be tailored to the recycling processes.

[0120] Sorting instructions may be executed by one or more distributed network nodes in a distributed network, such as distributed network nodes associated with sorters, mechanical fluid producers, and / or further recycle consumers. Sorting instructions may be provided by one or more distributed network nodes in a distributed network, such as distributed network nodes associated with mechanical fluid producers and / or further recyclers. Sorting instructions may be executed by a sorting system. For example, if a sorting instruction contains confidential process know-how, execution of the sorting instruction by sorters, mechanical fluid producers, and / or further recycle consumers may be required for information protection. Execution of sorting instructions by a sorting system may reduce latency.

[0121] In one embodiment of a method for sorting waste mechanical fluid, sorting data is provided to a sorting system configured to sort the waste mechanical fluid into assigned waste mechanical fluid fractions. The sorting system may include a display configured to display the sorting data.

[0122] In one embodiment of a method for sorting waste mechanical fluids, mechanical fluid composition data associated with the waste mechanical fluid is collected and aggregated into fraction data, which includes fraction composition data. A fraction identifier may be provided, and fraction data may be assigned to the fraction identifier. The fraction identifier may include at least one distributed fraction identifier. Representations linked to the distributed fraction identifier and fraction data may be provided for access by one or more network nodes of a distributed network. The fraction data may be provided for access by distributed network nodes associated with recyclers who further process the waste mechanical fluid fractions, and / or distributed network nodes associated with mechanical fluid producers who further process the waste mechanical fluid fractions. In this way, fraction characteristics can be tracked from mechanical fluid waste to the use of recycled rates in chemical production processes.

[0123] In another embodiment of the method for sorting waste mechanical fluids, the waste mechanical fluid fraction to be processed is associated with a recycling process identifier, and the recycling process identifier is assigned to a fraction identifier. The recycling process identifier may include at least one distributed recycling identifier. The fraction data may be provided for access by one or more network nodes associated with recyclers and / or mechanical fluid producers that further process the waste mechanical fluid fractions, based on the distributed recycling identifier. In this way, the material flow of the waste mechanical fluid fractions or recycles can be controlled and / or monitored to reach the appropriate recyclers and mechanical fluid producers.

[0124] A brief explanation of some of the figures in the drawing. The present disclosure will be further described below with reference to the attached drawings. The drawings and the same reference numerals in this disclosure are intended to refer to the same or similar elements, components, and / or parts. [Brief explanation of the drawing]

[0125] [Figure 1] This illustrates an exemplary embodiment of a circulating material loop, which includes material participants connected via a distributed network having distributed network nodes associated with the material participants. [Figure 2] This diagram illustrates how distributed data consumption network nodes associated with mechanical fluid users can be used to provide access to mechanical fluid-related data via distributed data provision network nodes associated with data owners. [Figure 3A] This shows an example of a data structure for a digital twin of mechanical fluids. [Figure 3B] Figure 3A shows an example of the data structure of dynamically used data included within the digital twin data structure. [Figure 4]This example illustrates a chemical production process involving the production of one or more mechanical fluids in relation to an operating system that includes a digital twin management system. [Figure 5] A schematic diagram illustrates an exemplary apparatus for generating access elements associated with spent mechanical fluids. [Figure 6A] A schematic diagram of the first example is shown, which provides a usage trigger and collects status data via the provided usage trigger. [Figure 6B] This diagram illustrates how to provide a usage trigger and collect status data in response to the receipt of the usage trigger. [Figure 7] This shows an example of digital access elements, including DID owner data, DID document data, and a distributed identity infrastructure. [Figure 8] A flowchart illustrating an exemplary method for monitoring a mechanical fluid during the operation of a machine containing that mechanical fluid is shown. [Figure 9] This document illustrates an exemplary system for acquiring machine fluid data and / or monitoring data based on distributed machine identifiers. [Figure 10] This document presents one embodiment of a relational expression that specifies the relationship between a machine and the materials used to produce it. [Figure 11] A schematic diagram illustrates an exemplary apparatus for generating maintenance data associated with the maintenance of spent mechanical fluids. [Figure 12] This provides a schematic representation of the user interface for the maintenance of used mechanical fluids. [Figure 13] A flowchart illustrating an exemplary method for generating maintenance data associated with the maintenance of used machine fluids is shown. [Figure 14] A schematic diagram illustrates an exemplary apparatus for generating control data associated with spent mechanical fluids. [Figure 15] A flowchart illustrating an exemplary method for generating control data associated with spent mechanical fluids is shown. [Figure 16]This document presents an example of a sensor-based sorting method for separating waste mechanical fluids contained in vehicles. [Figure 17] Figure 16 shows an example of waste mechanical fluid separation using a sensor-based sorting method. [Figure 18] This invention illustrates a sorting system for sorting waste mechanical fluids, comprising a distributed network interface according to an exemplary embodiment of the present invention. [Figure 19] Figure 18 shows a flowchart illustrating an example of a sorting method for sorting waste mechanical fluids, which can be implemented in the sorting system. [Figure 20] Figure 18 shows a flowchart illustrating an example of a selection method that can be implemented by a selection system with a distributed network interface. [Figure 21] An exemplary data structure used for the sorting method shown in Figure 18, based on mechanical fluid data accessible via a distributed network interface, is shown. [Figure 22] This shows an example of a predefined classification system configured to separate waste mechanical fluids by recycling processes and mechanical fluid producers. [Modes for carrying out the invention]

[0126] Detailed explanation The following embodiments are merely examples of, and should not be considered as limiting, implementations of the methods, systems, or application devices disclosed herein.

[0127] Figure 1 shows an exemplary embodiment of a circulating material loop 132, which includes material stakeholders 102 to recyclers 116, connected via a 136 having distributed network nodes 118 to 130 associated with material stakeholders 102 to 116.

[0128] The stakeholder network shown in Figure 1 may be a material chain network. The material chain network may include one or more linear material chains, such as a production chain and / or a recycling chain. A linear material chain may include a material production chain in which materials are produced by a material producer 102 and used by an original equipment manufacturer, such as a machinery producer 108, to produce a final product. A linear material chain may include a material production chain in which the produced final product is collected, sorted, and recycled to a recycler 116, and the recycled material is used by the material producer 102 to produce new materials. A material chain may include one or more production and / or recycling chains. A material chain may include one or more connected production and / or recycling chains. One or more linear material chains may be connected to a material loop 132.

[0129] A materials chain network may include a materials loop network that includes the use of recycled materials to produce new materials. One or more materials loops 132 may enable the use of materials resulting from the recycling of used products to produce new products, such as chemical products or materials, associated with one or more materials chains. A materials chain network, preferably a materials loop 132, may include the production, use, and / or recycling of physical materials or products containing such materials. Products may be materials, chemical products, intermediate chemical products, individual components containing materials, assemblies of individual components, final products, used products, products to be recycled, recycled products, or recyclates.

[0130] Materials or chemical products may refer to chemical compounds, chemical components, chemical molecules, chemical compositions, chemical mixtures, chemical formulations, intermediate chemical products, or chemical substrates that can be used to produce individual products. Chemical material or product flows may include non-individual material flows that can be further processed to produce individual products or components. Chemical material or product flows may include liquids, pellets, beets, powders, etc. Individual products may refer to individual components, assemblies of individual components, final products, used products, recycled products, or recycled individual products.

[0131] Chemical materials or products may be produced using raw materials and / or recyclates. Recyclates may refer to materials that have been mechanically or chemically recycled. Recyclate or recycled material flows may include undifferentiated material flows that can be further processed to produce new materials or chemical products. Recyclate or recycled material flows may include liquids, pellets, beets, powders, etc. Raw materials may refer to starting materials used to produce materials or chemical products, such as unprocessed raw materials. Unprocessed raw materials may be unused raw materials that have not undergone any processing other than for their production.

[0132] The term "final product" can refer to a product that is the result of a materials chain. The term "final product" can also refer to a product used by an end-of-life (EOL) user. "End-of-Life (EOL) product" can refer to a product that has been used by an end-of-life user. "End-of-Life (EOL) product" can refer to a product that no longer meets the requirements for its use. "End-of-Life (EOL) product" can refer to a product that is no longer needed. "End-of-Life (EOL) product" can refer to a product that has been discarded as waste, such as plastic waste. "Recycled product" can refer to any product or material produced using an EOL product. "Recycled product" can also refer to a new product or material produced using an EOL product.

[0133] The material loop 132 shown in Figure 1 may include multiple stakeholders 102-116 that form the material loop 132. The material loop 132 may include all stages of the material, from the production of the material through its use to its reuse. Thus, the material can flow in a closed loop, from the production of its components to the production of the final product, through use to reuse. Reuse may include the reuse of used products for another purpose, the refurbishment of used products, and / or the recycling of used products to resupply the recycle rate to material production.

[0134] The participants in the material loop 102–116 may be associated with the production of any material or product, and / or the recycling of any material or product. The participants in the material loop 132 may include chemical product producers 102, original equipment manufacturers (OEMs) 108, end-of-life product users 110, end-of-life product repair shops 112, end-of-life product recovery and / or sorting companies 114, recyclers 116, or a combination thereof. The participants may include various participants in the material chain or loop not shown in Figure 1.

[0135] The participants 102-116 in the material loop 132 may be linked through a material flow 138. The material flow 138 may correspond to a flow of products or materials from one of the participants 102-116 in the material loop to a downstream participant 102-116 in the material loop 132. The material flow 138 may refer to a continuous or discontinuous flow of products or materials. The flow of products or materials may include any means of transport suitable for transporting products from one participant 102-116 to another downstream participant 102-116. The means of transport may include pipes, containers, barrels, packages, or similar. The material flow 404 may be a unidirectional flow, such as the directional material flow 138. The material flow 138 may flow from an upstream participant 102-116 to a downstream participant 102-116 in the material loop 132, such as a material flow 138 from a recycler 116 to a chemical producer 102. The material flow may include a reverse material flow 138 from downstream participants 102-116 to upstream participants 102-116 in the material loop 132. For example, the material flow 138 could be from a chemical producer 102 to a recycler 116 if, for example, a recycled product or recycle rate does not meet quality specifications and requires further processing.

[0136] Material flow 138 may be associated with raw materials used to produce materials or chemical products, such as raw materials. Material flow 138 may include recycled materials instead of, or in addition to, raw materials. Raw materials and recycled materials may be provided to chemical producers for the production of materials, chemical products, and / or intermediate chemical products (not shown).

[0137] The material loop 132 shown in Figure 1 may be based on an example of a mechanical fluid and its circulation loop. The mechanical fluid may include lubricants, engine coolants, and working fluids. Material stakeholders may include input material suppliers 106, mechanical fluid producers 102, original equipment manufacturers 108 such as machine manufacturers, machine users 110 such as consumers, machine maintenance facilities 112, waste collectors and / or sorters 114, and recyclers 116 such as recyclers or refiners.

[0138] The mechanical fluid 140 may be produced by a mechanical fluid producer 102. The mechanical fluid may be supplied to a machine producer 108. The machine producer 108 may use the mechanical fluid received during the production of the machine. The machine may be supplied to a machine user 110. The machine may be used by the user. Maintenance of the machine in use may be carried out at a machine repair shop 112. At the end of its life, the mechanical fluid may be disposed of by the machine repair shop 112. The disposed mechanical fluid may be supplied to a waste collection and / or sorting company 114. The disposed mechanical fluid may be collected by the machine repair shop 112. The collected mechanical fluid may be sorted by an EOL product collection / sorting company 114. The collected mechanical fluid may be supplied to a sorting company to sort the mechanical fluid fractions to be recycled. The sorted fractions may be supplied to a recycler to recycle the mechanical fluid fractions. The recycled fraction can be supplied to the mechanical fluid producer 102 to produce new mechanical fluid, thus closing the material loop 132. The material flow 138 can close the loops between material participants.

[0139] In addition to connections via material flow 138, material participants 102-116 of the circulating material loop 132 may be connected through data flow 134 via distributed network 136. The distributed network 136 may include one or more distributed network nodes 118-130 associated with material participants 102-116 of the material loop 132. In a decentralized or decentralized network 136, the distributed network nodes 118-130 do not exclusively rely on a central network node, as opposed to a central network. In other words, no single entity has exclusive authority over the network. The distributed network 136 may include distributed network nodes and a central network node. The distributed network 136 may include a central network node that can control and / or monitor the distributed network nodes 118-130. For example, a central network node may provide authentication information that enables at least two distributed network nodes 118-130 to establish peer-to-peer communication channels between themselves.

[0140] Network nodes 118-130 may be computing nodes. A “computing node” can be any device or system that includes at least one physical, tangible processor and physical, tangible memory capable of having computer-executable instructions executed by the processor. Computing nodes are now taking on an increasingly diverse range of forms. Computing nodes may be, for example, handheld devices, monitoring systems, control systems, laptop computers, desktop computers, mainframes, and / or data centers. Memory may take any form and may depend on the nature and form of the computing node. Distributed network nodes 118-130 may be connected via wired and / or wireless connections, such as Ethernet, USB, LAN, WLAN, etc. Wireless communication may use, for example, WLAN, Wi-Fi, cellular, and / or Bluetooth. Distributed network nodes 118-130 may be configured to perform peer-to-peer data transactions, indicated by arrows 134 indicating data flow.

[0141] Distributed network nodes 118-130 may be configured as data consuming and / or providing network nodes. Distributed network nodes 118-130 may be configured to provide data to other network nodes in the distributed network 136 and / or to consume data from other nodes in the distributed network 136. For example, distributed network node 120 associated with mechanical fluid producer 102 may be configured to provide mechanical fluid data and / or monitoring data associated with the characteristics of mechanical fluid and / or used mechanical fluid to downstream stakeholders such as a machine repair shop 112 or a recycler 116. Furthermore, distributed network nodes 118-130 associated with EOL product collector / sorter 114 or recycler 116 may be configured to access data from network nodes 118-130 associated with upstream stakeholders such as mechanical fluid producer 102.

[0142] The distributed network nodes 118-130 may include computer executable instructions configured to provide, consume, and / or process data, such as data associated with mechanical fluids or machinery produced or processed within the circulating material loop 132. The network nodes may operate data provisioning services configured to provide data to other distributed network nodes 118-130 in the distributed network 136. Distributed network nodes 116-126 configured to provide data may be associated with data owners or data generation nodes associated with materials or products produced or processed within the circulating loop 128. The distributed network nodes 118-130 may be connected to one or more dedicated data storages that store data associated with materials or products produced or processed in the circulating loop 132 (see, for example, Figure 2). The dedicated data storages may be under the control of data owners or data generation nodes associated with materials or products produced or processed in the circulating loop 132. The data owners may be the respective stakeholders 102-116 in the circulating loop 132 to which the data generation nodes 118-130 are associated. The data generation nodes 118-130 can access dedicated data storage. Therefore, access to data associated with materials or products produced or processed within the circular loop 132 118 can be under the control of the data owner to which each distributed network node 118-130 is associated. This makes it possible for the data owner to maintain complete control over the data associated with materials or products produced or processed within the circular loop 132. At the same time, this makes it possible to share data associated with materials or products produced or processed within the circular loop 132 under controlled conditions, for example, by using an appropriate protocol that includes an authorization or authentication mechanism or scheme for establishing peer-to-peer communication.

[0143] Distributed network nodes 118-130 configured to consume data may include computer executable instructions for accessing and / or processing data in the distributed network 136, such as data provided by distributed data-providing network nodes 118-130, which are associated with materials produced or processed within the circulating loop 132. Distributed data-consuming network nodes 118-130 may be controlled or owned by, or associated with, any upstream or downstream participants in the circulating material loop 132. For example, distributed data-consuming network node 126 may be associated with a machine shop 112 to enable access to machine fluid data and monitoring data associated with the machine fluid supplied by the machine fluid producer 102 through a distributed data-providing network node 122 associated with the machine fluid producer.

[0144] The distributed network 136 may include further distributed network nodes. These further distributed network nodes may not be associated with further participants in the circular loop 132. These further nodes may be distributed infrastructure service nodes (not shown in Figure 1). The distributed infrastructure service nodes may provide services to the distributed network participant nodes 118-130, such as verifying the identity of the distributed network participant nodes 118-130 before performing data exchange. The distributed network participant nodes 118-130 may be associated with, or include, certificates such as X.509 certificates. The certificates may be associated with an identity manager, which may include, for example, a certificate issuing service and / or a dynamic provisioning service that provides dynamic attribute tokens (e.g., OAuth access tokens). In this way, the distributed network nodes 118-130 may be associated with, or linked to, a unique identifier embedded in the X.509 certificate that identifies each of the distributed network nodes 116-126. The information required for certificate verification may be provided through an authentication registry associated with the certificate issuing service and / or the dynamic provisioning service. For example, in the IDSA Reference Architecture Model, version 3.0 as of April 2019, prior to the implementation of data exchange (not shown), distributed data serving network nodes associated with the data owner, certificate authorities (CAs), dynamic attribute provisioning services (DAPS), and distributed data consumption network nodes associated with the data consumer are used to verify identity information.

[0145] Materials or products produced by participants 102-116 in the circular loop 132 may be associated with material or product data related to the properties of the materials or products produced by participants 102-116 in the circular loop 132. Material or product data may be provided for access by distributed data provision network nodes 118-130 associated with material or product producers. Access to material or product data may be controlled by distributed data provision network nodes 118-130. Material or product data may be accessed by distributed data consumption network nodes 118-130 associated with further participants 102-116 in the material loop 132, such as any downstream participants 102-116.

[0146] The data flow 134 between distributed network nodes 118-130 may be directly or indirectly associated with the material flow 138 between participants 102-116 in the material loop 132. For example, if data associated with mechanical fluid provided from mechanical fluid producer 102 to machine producer 108 is accessed by a distributed data consumption network node 122 associated with machine producer 108, the data flow 134 may be directly associated with the material flow 138. For example, if data associated with mechanical fluid produced by mechanical fluid producer 102 is accessed by a distributed data consumption network node 130 associated with recycler 116, the data flow 134 may be indirectly associated with the material flow 138.

[0147] Data transactions between distributed network nodes 118-130 may be based on a distributed identifier associated with the data of the material or product being accessed. The distributed identifier may be associated with the physical entity of the material or product. The distributed identifier may be uniquely associated with the physical entity of the material or product. The distributed identifier may uniquely identify the material or product within the distributed network 136. The distributed identifier may be associated with further distributed identifiers, such as the distributed identifier of the material or product used to produce the final product. This may make it possible to track the materials or products used to produce a product, such as the final product. The distributed identifier may be included in the access elements associated with the material or product, as will be explained in more detail in relation to Figures 5-8.

[0148] Specifically, the generation of access elements associated with monitoring data related to the use of mechanical fluids enables maintenance that depends on the wear of the mechanical fluids, and thus improves the environmental impact of the circulating material loop 132 by avoiding maintenance that uses fixed time intervals, resulting in waste mechanical fluids that can be used further without adversely affecting the operation of the machine. Such wear-dependent maintenance can be carried out by providing access to monitoring data related to the use of mechanical fluids, as will be explained in more detail with the examples in Figures 3A to 15 below.

[0149] Figure 2 shows a schematic diagram of providing access to machine fluid data via distributed data serving network nodes associated with machine fluid data owners, using distributed data consumption network nodes associated with data users. Access to the digital twin or a portion thereof (e.g., datasets contained in the digital twin; see Figures 3A and 3B) may be requested by distributed data consumption network nodes associated with stakeholders in the distributed network 136 (see Figure 1). Stakeholders may be machine producers 108 that produce machines containing machine fluids (see Figure 1). Machine fluid data (or digital twin) may be associated with machine fluids. Machine fluids may be selected from the group consisting of lubricants, engine coolants, and working fluids. Digital twins may be generated as described in relation to Figure 3A. Digital twins may include distributed machine fluid identifiers and machine fluid data. Machine fluid data may include status data, which may be included in or collected via usage triggers, as described, for example, in relation to Figures 5 and 8. The mechanical fluid data may include at least one measured physical and / or chemical property of the mechanical fluid, and / or at least one physical and / or chemical property determined from collected data associated with the production of the mechanical fluid.

[0150] The mechanical fluid 140 may be produced by chemical production, such as chemical production 402 as described in relation to Figure 4. Digital access elements may be generated during or after the production of the mechanical fluid, as described, for example, in relation to Figure 5. Digital access elements may be associated with a digital twin or a portion thereof. Digital access elements may include a distributed access element identifier and access data. The distributed access element identifier may correspond to or be associated with a distributed mechanical fluid identifier of the digital twin. Access data may include a digital representation pointing to the mechanical fluid data or a portion thereof. Access data may include a representation for accessing the mechanical fluid data or a portion thereof. Access data may include a dataset identifier associated with a dataset included in the digital twin (see, for example, Figures 3A and 3B). An exemplary digital access element is shown in Figure 7. Digital access elements may further include, or be associated with, authentication and / or authorization information linked to the distributed access element identifier. Authentication and / or authorization information may be provided for authentication and / or authorization of the data provision network node 120 and / or data consumption network node 122. Digital access elements may be provided to a distributed registry 208, for example, by a data-serving network node 120 associated with a device that generates access elements (see, for example, Figure 5). The distributed registry 208 may store distributed access element identifiers and associated access data. The distributed registry 208 may be accessible by data-consuming network nodes via distributed data-serving network nodes 120 associated with such a registry. Thus, entities associated with data-serving network nodes 120 may control access to the registry 208 via data-serving network nodes 120.

[0151] The mechanical fluid 140 produced by chemical production 402 may be provided to mechanical fluid consumers, such as machine producers 108, in association with a digital access element. Mechanical fluid consumers may use the mechanical fluid to produce machines containing the mechanical fluid. The mechanical fluid 140 may be associated with a code, such as a barcode or QR code, that encodes a distributed access element identifier. Mechanical fluid consumers may read the code through a code reader 202. The code reader 202 may be a smartphone running a code reading application, such as a QR code reader app. Data obtained by the code reading application may be used to determine the distributed access element identifier. Data obtained by the code reading application may be used to determine the distributed mechanical fluid identifier. Data obtained by the code reading application may be used to determine the mechanical fluid identifier. Data obtained by the code reading application may be used to determine the access data. The distributed access element identifier, distributed mechanical fluid identifier, mechanical fluid identifier, and access data may be determined by the code reader 202. For example, the distributed access element identifier determined by the code reader 202 may be a DID, and the code reader 202 may be configured to read the associated DID document containing the distributed machine fluid identifier and access data, for example, using a DID resolver (see also Figure 7). In another example, the machine fluid identifier may be determined by the code reader 202 and used to read the distributed access element identifier and associated access data from a database, for example, a distributed registry 208. Therefore, the code reader 202 may be configured to read a digital access element containing the distributed access element identifier and access data from the distributed registry 208. The code reader 202 may be configured to provide the distributed access element identifier and / or distributed machine fluid identifier to the database 206 associated with the machine manufacturer 108. The code reader 202 may be configured to provide the determined distributed access element identifier, distributed machine fluid identifier, and access data to the distributed data consumption network node 122.

[0152] The code reader 202 may be configured to display determined / read data on a user interface, as indicated by reference numeral 204. The user interface may display the determined distributed access element identifier (element ID), the determined distributed machine-fluid identifier (twin ID), and the determined access data (DT location). In this embodiment, the distributed access element identifier and the distributed machine-fluid identifier are different from each other. In another embodiment, the distributed access element identifier is equal to the distributed machine-fluid identifier. The user interface may further display the determined machine-fluid identifier (fluid ID). The user interface may also enable the initiation of reading machine-fluid data or a portion thereof based on the distributed access element identifier and access data, as described below. This process may be initiated by a button labeled "Access DT". When the button is pressed, the code reader 202 may send a request to access machine-fluid data or a portion thereof to the distributed data consumption network node 122.

[0153] A distributed data consumption network node 122 associated with a machine producer 108 may generate requests to access machine fluid data or a portion thereof. The distributed data consumption network node 122 may generate requests based on data received from a code reader 202. For example, the distributed data consumption network node 122 may generate requests based on distributed machine fluid identifiers received from the code reader 202. The data consumption network node 122 may generate requests based on distributed access element identifiers and / or distributed machine fluid identifiers provided to the database 206. For example, the distributed data consumption network node 12 may be configured to read distributed machine fluid identifiers and access data from the distributed registry 208 based on distributed access element identifiers stored in the database 206. Requests generated by the distributed data consumption network node 122 may include distributed machine fluid identifiers and distributed participant identifiers associated with the distributed data consumption network node 122. The requests may further include one or more dataset identifiers associated with the digital twin datasets (Figures 3A and 3B). The distributed data consumption network node 122 may be configured to determine the data provision network node 120 associated with the mechanical fluid data based on access data provided by the code reader 202 or read from the distributed registry 208.

[0154] The distributed data consumption network node 122 may send a request to the determined data provision network node 120 to access the mechanical fluid data or a portion thereof, as indicated by the arrow 210. The data provision network node 120 may be associated with the mechanical fluid producer 102. The data provision network node 120 may be associated with a chemical production that produces mechanical fluids. The data provision network node 120 may be associated with a data owner of the mechanical fluid data, such as the mechanical fluid producer 102. In addition to the request, authentication and / or authorization information may be provided by the distributed data consumption network node 122, as described, for example, in relation to Figure 1.

[0155] Requests can be authenticated (see also Figure 1). Requests can be authorized by the data-providing network node 120, for example, by retrieving access rules from the database of the data-providing network node 120 based on the distributed mechanical fluid identifier contained in the received request. The access rules may define data-consuming network nodes that can access the mechanical fluid data or a portion thereof. At least a portion of the retrieved access rules can be applied to the received request. This makes it possible to filter distributed data-consuming network nodes requesting access based on the distributed participant identifier associated with the network node. If the request is not authorized, the peer-to-peer communication channel will be terminated by the digital data-providing network node 120, and no mechanical fluid data will be provided.

[0156] If the request is approved, the data provision network node 120 may initiate contract negotiations with the distributed data consumption network node 122. The data provision network node 120 may provide the distributed data consumption network node 122 with an electronic contract. The electronic contract may include access rules associated with the distributed mechanical fluid identifier. This allows data consumers to determine the access and usage conditions associated with the desired data. The data provision network node 120 and the distributed data consumption network node 122 may be configured to negotiate and sign the electronic contract. The use of the electronic contract ensures that the distributed data consumption network node 122 and any further systems handling the mechanical fluid data or a portion thereof comply with the access rules associated with the mechanical fluid data. Once the electronic contract is signed, the data provision network node 120 may read or request mechanical fluid data stored in the digital twin storage 214 based on the distributed mechanical fluid identifier and optionally the dataset identifier included in the received request, as indicated by arrows 212 and 216. The data provision network node 120 may apply the determined access rules to the read or received mechanical fluid data. Subsequently, the data provision network node 120 may provide the mechanical fluid data or a portion thereof to the distributed data consumption network node 122 in accordance with the applied access rules, as indicated by arrow 218.

[0157] The mechanical fluid data provided by the data provision network node 120 may be stored in the database 206 associated with the distributed data consumption network node 122, according to the access rules, as indicated by the arrow 220.

[0158] The associated digital twin can be uniquely linked to the machine fluid through a distributed machine fluid identifier. Machine fluid data or a portion thereof can be transferred in a standardized and secure manner between machine fluid producer 102 and machine producer 108 via a distributed network, allowing machine fluid producer 102 to control access to the machine fluid data or a portion thereof by multiple distributed data consumption network nodes within the distributed network. In this way, machine fluid or a portion thereof can be shared using a unique association to the machine fluid, without direct, centralized mediation among stakeholders in the machine ecosystem. This enables transparency of digital twins within the machine ecosystem.

[0159] By generating a digital twin of the physical entity of the produced mechanical fluid, and generating digital access elements associated with the digital twin, it becomes possible to share mechanical fluid data and portions thereof under simplified and customizable conditions without compromising data security and data sovereignty.

[0160] Figure 3A shows an example of a data structure for a digital twin of a mechanical fluid. The mechanical fluid used may be selected from the group consisting of lubricants, engine coolants, and working fluids. The exemplary data structure may have a tree structure with a root node and one or more leaf nodes (e.g., nodes without child nodes). The root node may resemble the digital twin of the mechanical fluid. The root node may contain a distributed mechanical fluid identifier. The distributed identifier may contain one or more UUIDs and / or DIDs, as described above. The root node may have one or more child nodes.

[0161] Child nodes may represent different datasets, such as datasets 304-334. A dataset may also have a tree structure. A dataset may include static characteristics, such as safety data, technical data, production data, usage instruction data, specification data, maximum usage data such as the maximum distance and / or maximum duration before required cleanup, and identification data such as color. A dataset may also include dynamic characteristics, as shown in Figure 3B. Each dataset may include or be associated with a dataset identifier. A dataset identifier may include one or more UUIDs and / or DIDs. A dataset identifier can uniquely identify a dataset within the digital twin data structure. Each dataset may be associated with a distributed mechanical fluid identifier. Therefore, the combination of a distributed mechanical fluid identifier and its respective dataset identifier allows for the unique identification of a dataset in the digital twin.

[0162] A digital twin data structure can be generated by collecting data associated with the production of mechanical fluids, such as production data, analysis certificate data, material safety data, technical data, usage instruction data, specification data, maximum usage data, identification information data, composition data, data associated with production inputs used to produce mechanical fluids, or combinations thereof. Distributed mechanical fluid identifiers can be provided from a central node or distributed nodes. At least one data model can be provided that defines the structure of one or more datasets, such as datasets 304-334. The data model may include a semantic description of each dataset. This ensures the generation of datasets with harmonized data structures and enables efficient data sharing and processing. The data model can be applied to the collected data to generate one or more datasets. A dataset identifier can be provided for each dataset. A digital twin data structure can be generated by associating distributed mechanical fluid identifiers with one or more datasets.

[0163] A digital twin data structure can be generated when a request for such a data structure is received. The request may be received from a requester. For example, a packaging line may have a labeling device that detects the packaging of the machine fluid produced. Based on such recognition, the requester may generate a request for a digital twin data structure, and each distributed machine fluid identifier contained in the generated digital twin data structure may be assigned to its respective physical identifier by, for example, an ID assigner. Assignment may include encoding each distributed machine fluid identifier to a physical identifier and providing the physical identifier, such as a code, to a labeling device configured to attach the physical identifier to each machine fluid, such as the packaging of each machine fluid. The ID assigner may be part of the labeling device or a separate device.

[0164] A digital twin data structure can be generated by the data owner of the collected production data associated with the production of mechanical fluids. A digital twin data structure can be generated by mechanical fluid producer 102. A digital twin data structure can be generated on behalf of a data owner such as mechanical fluid producer 102.

[0165] The digital twin data structure may be associated with a data owner, such as a mechanical fluid producer, or stored in the data owner's dedicated storage. The dedicated storage may be accessible to the data owner. The dedicated storage may be associated with a data-providing network node that provides access to the digital twin data structure, for example, via an access element, as illustrated in relation to Figure 2.

[0166] Figure 3B shows an example of the data structure for dynamic usage data included within the digital twin data structure of Figure 3A. The dynamic usage data structure may include a tree structure containing a root node and one or more leaf nodes. The root node may contain a dynamic usage dataset identifier. Dynamic usage data may include monitoring data collected during machine use, for example, as described in relation to Figures 5 to 15. Monitoring data may be collected when a usage trigger is received, for example, as described in relation to Figures 5 and 8. Monitoring data may include data associated with the operation of the machine. Monitoring data may include data associated with used machine fluid. Monitoring data may include at least one measured physical property of the machine fluid. Monitoring data may include at least one physical property determined from the collected data associated with the used machine fluid. For example, collected transmittance data may be used to determine the degree of impurities in the machine fluid.

[0167] Dynamic usage data may be collected by one or more sensors. One or more sensors may be located within the machine. One or more sensors may not be located within the machine. One or more sensors may be configured to determine at least one property of the used machine fluid. At least one property may be permeability and / or viscosity. Dynamic usage data may be determined from data collected by one or more sensors, as described above. Dynamic usage data may correspond to or include status data.

[0168] Status data may include at least one characteristic related to the location of the maintenance work, such as an identifier associated with the repair shop. This could, for example, make it possible to track whether maintenance on mechanical fluids was performed by an authorized repair shop.

[0169] Figure 4 shows an example of a chemical production 402 that produces one or more mechanical fluids 408 from one or more input materials 404, relating it to an operating system 406 that includes a digital twin management system. The mechanical fluids may be selected from the group consisting of lubricants, engine coolants, and working fluids. The chemical production 402 may be associated with distributed network stakeholders, such as a mechanical fluid producer 102, which is described in relation to Figure 1. The operating system 406 may be used to operate the chemical production 402, for example, by managing different production chains that exist within the chemical production. Different chemical materials 404 (hereinafter also referred to as input materials 404) may be provided as physical inputs from material providers or suppliers in order to produce one or more mechanical fluids 408. The physical inputs to the chemical production 402 may include chemical materials such as raw materials, intermediate materials, or combinations thereof. Raw materials may be raw materials or recycled raw materials (see Figure 1). The input materials 404 may be supplied to the chemical production 402 at any inlet point. The input material 404 may be supplied to chemical production 402 at the start of chemical production 402. The input material may be considered an input to chemical production 402.

[0170] Chemical production 402 can be a chemical production network that includes multiple interconnected processing steps. A chemical production network can be an integrated chemical production network having interrelated production chains. A chemical production network can include multiple different production chains that share at least one intermediate product. A chemical production network can include multiple stages of a chemical value chain. A chemical production network can include multiple production chains that produce chemical products as output from one or more inbound materials as inputs. A chemical production network can include multiple layers of a chemical value chain. A chemical production network can include the arrangement of physically interconnected production sites. Production sites can be in the same location or in different locations. In the latter case, production sites can be interconnected by dedicated transportation systems such as pipelines, supply chain vehicles such as trucks, supply chain ships, or other means of freight transport.

[0171] Chemical production 402 may include multiple production steps. The production steps included in chemical production 402 may be defined by the system boundary of chemical production 402. The system boundary may be defined by the area to which the production process extends or by the control over the production process. The system boundary may be defined by the locations of chemical production 402. The system boundary may be defined by a production process jointly controlled by one or more entities. The system boundary may be defined by a value chain with time-delayed production processes to the final product, and these processes may be individually controlled by multiple entities.

[0172] Chemical production 402 can convert inbound material 404 into one or more mechanical fluids 408 exiting chemical production 402. The conversion may be carried out via intermediate chemical products. The conversion may be a chemical reaction or any other processing step such as physical treatment. Since the yield of a chemical reaction may be less than 100%, the chemical reaction may result in a mixture of different chemical products. Thus, a chemical reaction of one or more starting materials such as inbound material 202 may result in a mixture of different chemical products. Thus, a chemical reaction may be characterized by a one-to-many or many-to-many relationship between the starting materials and the resulting reaction products. This is in contrast to discrete manufacturing, where a many-to-one relationship exists between parts / components and assemblies, for example, the result of a discrete manufacturing process is a specific and predictable assembly. Since the yield of a chemical reaction may not necessarily be equal to 100%, the amount of desired mechanical fluid 408 may be less than the theoretical amount of mechanical fluid calculated from the amount of starting material. In such mixtures, separation of the different chemical products contained in the mixture is typically required. This makes it possible to avoid the adverse effects of impurities and unreacted inbound material 404 on further processing of the mechanical fluid 408. Separation may include distillation, washing, extraction, crystallization, and recrystallization. The resulting mixture may contain unreacted starting materials, such as unreacted inbound material 404. The unreacted starting materials may be reintroduced into the chemical reaction to reduce the amount of starting materials required. The resulting mixture may contain the desired mechanical fluid 408 supplied to upstream participants in the product ecosystem, such as the mechanical producer 108 (see Figure 1). The resulting mixture may contain intermediate chemicals used as input materials in further chemical reactions carried out in chemical production 402. This makes it possible to reduce the amount of waste associated with the disposal of the intermediate chemicals and / or the amount of energy associated with transporting these intermediates to other chemical productions. The resulting mixture may contain waste chemicals, for example, chemicals that can no longer be used and must be disposed of, for example, by incineration. Waste chemicals may be produced from undesirable chemical side reactions.

[0173] The chemical production system 402 may include several sensors (not shown). The sensors may collect at least one chemical and / or physical property of the mechanical fluid 408 produced by the chemical production system 402. The sensors may measure at least one chemical and / or physical property of the inbound material 404 supplied to the chemical production system 402. The sensors may collect data relating to the quantities of the inbound material 404 and / or the produced mechanical fluid 408. Examples of such sensors may include measuring instruments or flow meters. The sensors may include sensors configured to measure at least one chemical and / or physical property of the inbound material 404. Measuring the chemical and / or physical properties of the inbound material 404 makes it possible to control the production process based on the measurement data. The sensors may include sensors configured to determine the chemical and / or physical properties of the produced mechanical fluid 408. The data collected by the sensors may be stored in one or more databases, as described in relation to Figure 3A, and may be used to generate a digital twin data structure of the mechanical fluid. The stored data may be related to input material identifiers and / or mechanical fluid identifiers, respectively.

[0174] The chemical production operating system 406 may monitor and / or control the chemical production 402 based on operational parameters associated with different processes carried out by the chemical production 402. One process step to be monitored and / or controlled may be the supply of inbound material 404 or the shipment of the produced mechanical fluid 408. Another process step to be monitored and / or controlled may be the separation of chemical products contained in the mixture resulting from the chemical reactions carried out in the chemical production 402. Another process step to be monitored and / or controlled may be the determination of the chemical and / or physical properties of the produced mechanical fluid 408 from data associated with the production of the mechanical fluid, such as data measured by sensors before, during, and / or after the production of the mechanical fluid 408. Another process step to be monitored and / or controlled may be the generation of a digital twin (e.g., a digital twin data structure; see, for example, Figure 3A). The digital twin may be generated as described in relation to Figure 3A. Another process step that is monitored and / or controlled may be the generation of access elements associated with the collected status data, as described, for example, in relation to Figures 5 and 8. Another process step that is monitored and / or controlled may be the control of access to the collected status data based on the generated digital access elements, as described, for example, in relation to Figure 2.

[0175] Figure 5 schematically shows an exemplary apparatus for generating access elements associated with spent machine fluid. The machine fluid may be present in spent machine. The spent machine fluid may be selected from the group consisting of spent lubricant, spent engine coolant, and spent working fluid. The apparatus may be configured to carry out the method shown in Figure 8. The apparatus may correspond to the operating system 406 of chemical production 402 as described in relation to Figure 4. The apparatus may be in communication with the input material operating system 406 of chemical production 402 as described in relation to Figure 4.

[0176] Use triggers can be generated by a use trigger provider 502. Use triggers can also be generated by nodes associated with stakeholders in a machine ecosystem, such as the machine ecosystem shown in Figure 1. Stakeholders may be factories that repair machines, clean used machine fluids, and / or replace used machine fluids, for example, the machine repair shop 112 in Figure 1. For use trigger generation, machine identification information can be read via a code reader 202 or manually entered into an application such as a mobile app. Based on providing machine identification information, distributed machine identifiers associated with used machines can be read via a distributed network using an ID provider 506. For example, machine identification information may be provided to a distributed database or distributed registry that stores distributed machine identifiers related to the machine identification information. The distributed database may be a database containing distributed machine identifiers of machines in the machine ecosystem. The distributed database may include a distributed ledger that can enable verification of machine identifiers. Furthermore, for example, distributed machine identifiers may be read from a registry that stores distributed machine identifiers related to machine identification information and associated with stakeholders that trigger use triggers. Furthermore, for example, distributed machine identifiers may be retrieved from a registry associated with any participant in the machine ecosystem, such as a machine manufacturer or machine user. Participants who trigger usage events may connect to nodes associated with other participants in the machine ecosystem via authentication and / or authorization protocols of the distributed network, as illustrated, for example, in relation to Figure 1.

[0177] According to a first exemplary embodiment, and with reference to Figure 6A, the use trigger may include a distributed machine identifier associated with the used machine and status data associated with the used machine fluid. The status data may indicate the status of the used machine fluid. The status data associated with the used machine fluid may relate to the characteristics of the used machine fluid and, optionally, the used machine. The status data may relate to the physical and / or chemical characteristics of the used machine fluid and, optionally, the used machine. The status data may include at least one physical and / or chemical characteristic of the used machine fluid, at least one physical and / or chemical characteristic of the used machine, maintenance data related to maintenance work performed on the machine fluid, the location associated with the maintenance work, or a combination thereof. The status data may include measurement data collected by one or more sensors. The measurement data may include transmittance data and / or viscosity data. The transmittance data may be analyzed to provide status data such as the degree of impurities. The viscosity data may be analyzed to provide status data such as the degree of wear. Status data may relate to the age of the used mechanical fluid, the operating time of the machine and the mechanical fluid, the machine's mileage, previous maintenance work performed on the used mechanical fluid, or a combination of these.

[0178] Continuing to refer to Figure 6A, a usage trigger, which includes a distributed identifier associated with the used machine and further includes status data, may be provided to any node associated with a participant in the machine ecosystem that monitors the maintenance of used machine fluids. For example, a usage trigger may be provided to a node associated with machine fluid producer 102. The usage trigger may be transmitted to the nodes associated with each participant, as shown in Figure 6A. Thus, the apparatus of this embodiment does not need to include a status data collector 508, because the status data is already provided by the usage trigger provider 502. A node may have an access element generator 512. A node may be in communication with the access element generator 512.

[0179] The mechanical fluid producer 102 may generate a dataset that includes an endpoint address associated with the data consumption network node 120 and data indicating that this is an endpoint that receives status data associated with used mechanical fluid. The dataset (hereinafter referred to as assets) may be provided to the distributed registry node 612. The distributed registry node 612 may be configured to store assets and provide access to the stored assets upon request from distributed data consumption network nodes and / or distributed data provision network nodes associated with participants in the distributed network, such as the distributed network 136 described in relation to Figure 1. The distributed data consumption network node 120 may be configured to provide the status data received from the distributed data provision network node 122 associated with the mechanical fluid producer 108 to the database 606.

[0180] As described above, the machine repair shop 112 may generate status data about used machine fluid. The generated status data may be stored in the status data storage 610 associated with the distributed data provision network node 122 of the machine repair shop 112. At the point where a usage trigger is generated, the distributed data provision network node 122 may be configured to read assets registered by the machine fluid producer 102 from the distributed registry node 612. Assets may be retrieved by identifying an asset catalog associated with the machine fluid producer 102 (e.g., a dataset showing a list of available assets accessible from the distributed data provision nodes associated with the distributed registry node 612) based on the distributed participant identifier of the machine fluid producer 102. Assets may be identified within the catalog by searching for assets that include characteristics indicating endpoint data for receiving status data associated with used machine fluid.

[0181] Upon identifying each endpoint, the distributed data providing network node 122 may establish a connection to the distributed data consuming network node 120 using the data contained in the retrieved assets. The distributed data providing network node 122 and the distributed data consuming network node 120 may perform an authentication step, as illustrated in relation to Figure 2, for example. Upon successful authentication, electronic contract negotiation may be performed, as illustrated in relation to Figure 11. Upon successful electronic contract negotiation, the distributed data providing network node 122 may provide the generated usage trigger to the distributed data consuming network node 120, and the distributed data consuming network node 120 may store the status data contained in the received usage trigger in the database 606.

[0182] According to a second exemplary embodiment, referring to Figure 6B, a use trigger provided by the use trigger provider 502 may include a distributed machine identifier associated with the used machine. Continuing to refer to Figure 6B, a use trigger including the distributed identifier associated with the used machine may be provided to any node associated with a participant in the machine ecosystem monitoring the maintenance of used machine fluids. For example, a use trigger may be provided to a node associated with machine fluid producer 102. The use trigger may be transmitted to nodes associated with each participant, as shown in Figure 6B. A node may comprise an access element generator 512. A node may be in communication with the access element generator 512.

[0183] In response to receiving a usage trigger, node 120 may be configured to collect (e.g., gather) status data from node 122 associated with machine shop 112 via the distributed machine identifier contained in the received usage trigger. Status data may be collected from node 122 as described in relation to Figure 2. Status data may be collected by status data collector 508.

[0184] Referring again to Figure 5, access elements associated with status data can be generated by the access element generator 512 based on the provision of a usage trigger. One or more datasets can be generated using the status data by the dataset generator 510. Each dataset may include at least a portion of the collected status data, and / or at least physical and / or chemical properties determined from the collected status data. Each dataset may further include a dataset identifier. By generating different datasets, access rules used to control access to the status data can be defined separately for each dataset, thus enabling finer control over access to the status data. Datasets can be generated by applying one or more data models to the status data. This makes it possible to generate standardized data that ensures efficient data transfer and processing, for example, for determining maintenance data and control data.

[0185] One or more datasets may be used by the Digital Twin Updater 514 to update an existing digital twin of used machine fluid. An existing digital twin may be generated as described in relation to Figure 3A. Updating may involve associating at least some of the collected status data with distributed machine fluid identifiers associated with the existing machine fluid data. Updating the existing machine fluid data makes it possible to maintain the correspondence between the digital twin of the machine fluid and the physical entities of the machine fluid so that the digital twin can represent the current state of the physical entities of the used machine fluid at any time. By updating the existing machine fluid data, maintenance data that takes into account the current state of the machine fluid can be generated, and thus it becomes possible to adapt the maintenance of the machine fluid to the current state without adversely affecting machine performance, while reducing the environmental impact by avoiding extra machine fluid maintenance work such as replacement or cleaning.

[0186] At least one distributed mechanical fluid identifier may be provided by the distributed mechanical fluid ID provider 516. The distributed mechanical fluid ID provider 516 may collect distributed mechanical fluid identifiers included in an existing digital twin of the mechanical fluid. The distributed mechanical fluid ID provider 516 may generate one or more further distributed mechanical fluid identifiers, such as a dataset identifier, associated with at least a portion of the status data.

[0187] At least one digital representation associated with the status data may be generated by the digital representation generator 518. The digital representation may include a representation of the status data or a portion thereof (e.g., a dataset containing the status data). The digital representation may include a locator or pointer to a dedicated storage or storage address associated with the mechanical fluid producer 102. The pointer or locator may directly point to the dedicated storage address. The dedicated storage may store the status data or a dataset containing the status data. Access to the dedicated storage may be controlled by the data owner of the status data, such as the mechanical fluid producer 102. The pointer or locator may point to a data-serving network node associated with the dedicated storage. This may improve data security because the dedicated storage address is not exposed to further participants in the distributed network, thus avoiding the risk of direct access to the dedicated storage without access control via the distributed data-serving network node. The digital representation may include one or more digital links pointing to the status data. The digital representation may include a locator or pointer, e.g., a url or uri, to a dedicated storage address associated with the mechanical fluid producer that stores the status data. Digital representations may include representations for accessing status data or datasets containing status data.

[0188] Access elements associated with status data may be generated by the access element generator 504. An exemplary access element generated by the access element generator 504 is shown in Figure 7. The access element may include a distributed machine fluid identifier and a digital representation. An access element may be generated for each dataset generated by the dataset generator 510. The access element may relate to authorization rules that provide access to status data depending on the maintenance work performed on the spent machine fluid and / or the participants in the distributed network. The access element may be provided for one or more data-consuming network nodes associated with one or more maintenance operators performing one or more maintenance processes to access status data containing data dependent on the maintenance work and / or the participants. Thus, access to sensitive data related to maintenance work on spent machine fluid may be restricted to specific network nodes to which data access is relevant, such as the machine shop 112.

[0189] The access element generator 504 may provide the generated access elements to the data supply network node 120 for data consumption network nodes to access status data. Access to status data based on the access elements may be controlled by the data supply network node 120. The data supply network node 120 may be associated with storage for storing status data.

[0190] Figure 7 shows an example of digital access elements, including DID owner data, DID document data, and a distributed identity infrastructure.

[0191] A distributed identifier may include a distributed identifier (DID). In this case, a distributed identifier-based digital access element may be a DID document 704 associated with the DID. In addition to the DID document 704 acting as a digital access element, Figure 7 shows a DID owner data element 702 that includes distributed identifier-based owner data. Generally, distributed identifier-based owner data may include a distributed identifier associated with a subject such as a chemical product dataset and may include one or more authentication mechanisms. Distributed identifier-based owner data 702 may include owner data that is electronically owned and controlled by the DID owner. In this context, electronically owned may mean data stored in an owner repository or wallet. Such data may be securely stored and / or managed on an organized server or client device. Distributed identifier-based owner data 702 may include a DID, a private key, and a public key. A DID owner may own and control a DID representing the identity associated with a DID subject, and a private key and public key pair associated with the DID. A DID can be understood as an identifier and authentication information associated with or uniquely linked to the identifier.

[0192] A DID subject may be a raw material, a basic substance, a chemical product, or a finished product. A DID subject may be a machine, system, or device used to produce a raw material, a basic substance, a chemical product, an intermediate product, or a finished product, or an assembly of such machines, devices, and / or systems. A DID owner may be a supply chain participant or a manufacturer, such as a chemical manufacturer that produces chemicals. A DID owner may be an upstream participant of a mechanical fluid producer 102, such as a supplier that supplies raw chemicals or precursors for producing mechanical fluids. A DID owner may be a downstream participant of a mechanical fluid producer 102, such as a customer that consumes chemicals to produce intermediate products, components, component assemblies, or finished products. A DID owner may be any participant in the product ecosystem, including raw chemical suppliers, intermediate chemical manufacturers, intermediate component manufacturers, component manufacturers, component assembly manufacturers, finished product manufacturers, finished product users, service providers, EOL collectors, or recyclers.

[0193] DID can be any identifier associated with the DID subject and / or DID owner. Preferably, the identifier is unique to the DID subject and / or DID owner. The identifier can be unique at least to the extent that the DID is expected to be used. The identifier can be a locally or globally unique identifier for any participant in the product ecosystem, including: raw materials, precursors, basic substances, chemical products, intermediate products, components, component assemblies, final products, recycled materials, or assemblies thereof; machines, systems, or devices used to produce raw materials, basic substances, mechanical fluids, intermediate products, components, component assemblies, final products, or recycled materials, or assemblies of such machines, devices, and / or systems; chemical manufacturers producing chemicals, upstream participants of chemical manufacturers, downstream participants of chemical manufacturers, or assemblies thereof; raw material chemical product suppliers, intermediate chemical product manufacturers, intermediate component manufacturers, component manufacturers, component assembly manufacturers, final product manufacturers, final product users, maintenance operators, EOL collectors, or recyclers, or assemblies thereof.

[0194] A DID can be any identifier associated with a DID subject and / or DID owner. Preferably, a DID is unique to the DID subject and / or DID owner. A DID can be unique at least to the extent that it is expected to be used. A DID can be a locally or globally unique identifier for any of the possible DID subjects described above. A DID can also be a Unified Resource Identifier (URI), such as a Unified Resource Location Specifier (URL). Furthermore, a DID can be an Internationalized Resource Identifier (IRI). A DID can be a Unified Resource Identifier (URI), such as a Unified Resource Location Specifier (URL). A DID can be an Internationalized Resource Identifier (IRI). For enhanced security, a DID can be a random string of numbers and letters. In one embodiment, a DID can be a sequence of 128 letters and numbers following the format did:method name:method specific-did, such as did:example:ebfeb1f712ebc6f1c276e12ec21. DID can be a decentralized identity that is independent of a centralized third-party management system and is under the control of the DID owner.

[0195] Digital access elements as DID document data, DID document data 704, may be associated with a DID, i.e., a DID contained in distributed identifier-based owner data 702. Thus, digital access elements may include a reference to a DID associated with a DID subject described by DID document 1904. DID document 704 may also include authentication information, such as a public key. The public key may be used by a third-party entity authorized by the DID owner / subject to access information and data owned by the DID owner / subject. The public key may also be used to verify that the DID owner actually owns or controls the DID. The DID document may include authentication and authorization information, for example, to authorize a third-party entity to read the DID document or a portion of the DID document, without, for example, granting the third party the right to prove ownership of the DID.

[0196] The digital access element 704 may include, for example, one or more representations that digitally link to the digital twin data contained in the digital twin to which the digital access element is associated, via a service endpoint. The service endpoint may include a network address on which the service operates on behalf of the DID owner. Specifically, the service endpoint may refer to a service such as a data provision service of the DID owner that grants access to the digital twin data. Such a service may include a service that reads or analyzes the data contained in the digital twin data. The data contained in the digital twin may include chemical product declaration data, chemical product safety data, certificates of analytical data, emission data, product carbon footprint data, product environmental footprint data, chemical product specification data, product information, technology application data, production data, chemical composition data, or a combination thereof.

[0197] The digital access element 704 may include further identifiers such as a digital twin data identifier and a chemical product identifier.

[0198] The digital access element 704 may contain various other information, such as metadata specifying when the digital access element was created, when the last modification was made, and / or when it expires.

[0199] The DID and digital access element 704 may be associated with a central data service system or a distributed data service system 706, such as a data registry node including a distributed ledger, blockchain, or distributed file system. The distributed ledger or blockchain may be used to store a representation of the DID that points to the digital access element 704. The representation of the DID may be stored in the distributed computing nodes of the distributed ledger or blockchain 1606. For example, a DID hash may be stored in multiple computing nodes of the distributed ledger and point to the location of the digital access element 704. In some embodiments, the digital access element 704 may be stored in the distributed ledger 706. Each computing node may store a copy of the distributed ledger 706. In this way, each DID hash can be stored redundantly, thereby increasing data security. Multiple DIDs associated with different digital access elements 704 may be included in the distributed ledger 706.

[0200] In some embodiments, the digital access element 704 may be stored in the distributed ledger 706, i.e., in addition to or alternative to the associated DID representation stored in the distributed ledger 706. In other embodiments, the digital access element 1604 may be stored in data storage associated with a distributed ledger or blockchain or distributed file system (not shown).

[0201] A distributed ledger or blockchain 706 can be any decentralized distributed network comprising various computing nodes that are in communication with one another. For example, a distributed ledger 706 may include a first distributed computing node, a second distributed computing node, a third distributed computing node, and any number of additional distributed computing nodes (not shown). A distributed ledger or blockchain 706 may include known technology stacks such as Bitcoin (see, for example, the Bitcoin documentation published on November 11, 2022 at https: / / en.bitcoin.it / wiki / Protocol_documentation), Ethereum (see, for example, the Ethereum documentation published on August 15, 2022 at https: / / ethereum.org / en / developers / docs / ), Solana (see, for example, the Solana documentation published on November 11, 2022 at https: / / spl.solana.com / ), Polygon (see, for example, the Polygon documentation published on November 11, 2022 at https: / / wiki.polygon.technology / ), or other embodiments with varying degrees of data transactions performed on a distributed ledger. The description of exemplary frameworks is for illustrative purposes only and should not be considered limiting.

[0202] Figure 8 shows a flowchart of an exemplary method for monitoring a mechanical fluid during use of a machine containing that mechanical fluid. The method may be carried out by a system described in conjunction with Figure 5. The mechanical fluid may be present in a used machine. The used mechanical fluid may be selected from the group consisting of used lubricant, used engine coolant, and used working fluid.

[0203] According to one embodiment of the present method, a usage trigger may be generated and provided as described in relation to Figures 5 and 6A. The usage trigger may include a distributed machine identifier and status data (see block 822). According to another embodiment, a usage trigger may be generated and provided as described in relation to Figures 5 and 6B (see block 802). The usage trigger may include a distributed machine identifier. The usage trigger may not include status data. Upon receipt of a usage trigger, status data may be collected as described in relation to Figures 5 and 6B (see block 804).

[0204] In determination block 806, it may be determined whether to generate one or more datasets using at least a portion of the status data. If datasets are to be generated, the method may proceed to block 808. Otherwise, the method may proceed to determination block 810.

[0205] In block 808, the dataset can be generated by the dataset generator 510, as described in relation to Figure 5.

[0206] In block 810, it may be determined whether to update the existing digital twin of the spent machine fluid. The existing digital twin may have been generated at the time of production of the machine fluid or after production. The existing digital twin may have been generated before supplying the machine fluid to the machine producer 108. If the existing digital twin is to be updated, the method may proceed to block 812. Otherwise, the method may proceed to block 814.

[0207] In block 812, the digital twin updater 514 can update the existing digital twin, as described in relation to Figure 5.

[0208] In block 814, one or more distributed mechanical fluid identifiers associated with the status data may be provided as described in relation to Figure 5. One or more distributed mechanical fluid identifiers may be provided by the distributed mechanical fluid ID provider 516.

[0209] In block 816, one or more digital representations of the status data may be generated as described in relation to Figure 5. One or more digital representations may be generated by the digital representation generator 518.

[0210] In block 818, an access element including one or more distributed mechanical fluid identifiers and one or more digital representations may be generated as described in relation to Figure 5. The one or more digital representations may be generated by the digital access element generator 504.

[0211] In block 820, the generated access elements may be provided to a distributed network, such as the distributed network 136 in Figure 1, to access status data, as described in relation to Figure 5. The status data makes it possible to determine the maintenance interval of the mechanical fluid according to the current state of the mechanical fluid, and thus it may be possible to extend the life of the mechanical fluid and reduce the environmental impact of the material loop 132.

[0212] Figure 9 shows an exemplary system for acquiring machine fluid data based on distributed machine identifiers. The system in Figure 9 can be used to generate maintenance data and / or control data, as described in relation to Figures 11 to 15.

[0213] The machine may be provided in association with a digital access element. The machine 918 may be associated with machine identification information, as described in relation to Figure 5. The machine identification information may be read through the ID provider 506. The ID provider 506 may be a smartphone running a machine identification application. The data obtained by the code reading application may be used to determine a distributed access element identifier (hereinafter referred to as DID1), as described in relation to Figure 5. The data obtained by the code reading application may be used to determine a distributed machine identifier (hereinafter referred to as UUID1), as described in relation to Figure 5. The ID provider 506 may be configured to perform an authentication step together with a distributed registry node 902. For example, the ID provider 506 may have access to a distributed IAM network node (not shown), and the distributed IAM network node may be configured to provide the ID provider 506 with an access token upon successful authentication. This access token may be used by the ID provider 506 to access the distributed registry node 902. The ID provider 506 may provide distributed participant identifiers associated with participants in the machine ecosystem to distributed IAM network nodes for authentication.

[0214] The ID provider 506 may be configured to provide a distributed machine identifier (e.g., UUID1) to the distributed network node 904. The ID provider 506 may also be configured to provide authentication data such as a distributed participant identifier, and optionally authentication data such as an access token, to the distributed network node 904.

[0215] The distributed network node 904 may be configured to validate authentication data received from the identity provider 506 together with the distributed IAM network node 906. Upon successful authentication, the distributed network node 904 may be configured to access the distributed registry node 902 using the distributed machine identifier received from the identity provider 506 and to read data related to the relational expression associated with the distributed machine identifier. The data related to the relational expression may include a distributed relational expression identifier and a digital representation pointing to each relational expression. The digital representation pointing to the relational expression may point to the distributed data providing network node associated with each relational expression. For example, data related to a relational expression associated with a machine may include a digital representation pointing to the distributed data providing network node associated with the machine fluid data of the machine fluid used to produce the machine. The distributed network node 904 or a distributed data consuming network node (not shown) associated with the distributed network node 904 may be configured to access the respective distributed data providing network node associated with the digital representation and request the relational expression associated with the distributed relational expression identifier from the distributed data providing network node, for example, as shown in Figure 2.

[0216] Referring to Figure 10, the relational expression 1004 associated with the machine may include a distributed machine identifier and a distributed machine fluid identifier. The relational expression may be contained in the digital twin 1002 of the machine. The relational expression 1008 associated with the machine fluid may include a distributed machine fluid identifier and a distributed production input identifier associated with the production inputs used to produce the machine fluid, such as diester base stocks and fuel additives. The relational expression may be contained in the digital twin 1006 of the machine fluid. The distributed production input identifiers are then associated with the digital twins of their respective production inputs 1010, 1012.

[0217] Continuing to refer to Figure 10 and then again to Figure 9, the distributed network node 806 may be configured to determine the distributed mechanical fluid identifier included in the relational expression. The distributed network node 904 may be configured to use the determined distributed mechanical fluid identifier to access the distributed registry node 902 and determine the access data associated with the distributed mechanical fluid identifier. The distributed network node 904 or a distributed data consuming network node (not shown) associated with the distributed network node 904 may be configured to access the mechanical fluid data using the distributed mechanical fluid identifier, the access data, and optionally, a distributed participant identifier provided by the ID provider 506 from the respective distributed data providing network node. As described above, the distributed network node 904 may be configured to determine the data related to the relational expression associated with the determined distributed material identifier.

[0218] In this example, distributed network node 904 may receive a distributed machine identifier associated with a machine from ID provider 506. Distributed network node 904 may use the distributed machine identifier to access distributed registry node 902 to determine data related to a relational expression associated with the distributed machine identifier. The determined data related to the relational expression may include a digital representation pointing to a distributed data providing network node associated with the machine data. The machine data may be stored in a storage environment associated with a distributed data providing network node (not shown). The machine data may include a relational expression indicating a distributed machine fluid identifier associated with the machine fluid used to produce the machine (see also Figure 10). Distributed network node 904 or a distributed data consuming network node associated with distributed network node 904 may be configured to access relational expressions from the distributed data providing network node. Distributed network node 904 or a distributed data consuming network node associated with distributed network node 904 may be configured to access machine data from the distributed data providing network node. Access to the machine data may be authorized based on a distributed participant identifier provided by ID provider 506. Access to the machine data may be controlled by a distributed data providing network node associated with the machine producer. This ensures that machine data is accessible only to authorized stakeholders in the machine ecosystem, thus preventing uncontrolled access to machine data.

[0219] The distributed network node 904 may be configured to read a distributed material identifier associated with the machine fluid used to produce the machine from the accessed relational representation. The distributed network node 904 may be configured to use the determined distributed machine fluid identifier to access data from the distributed registry node 902 related to the relational representation associated with the distributed machine fluid identifier. The distributed network node 904 or the distributed data consumption network node may be configured to access the relational representation from, for example, the distributed data providing network node 120 associated with the machine fluid. The machine fluid data may be stored in a storage environment (DT storage 1 912) associated with the distributed data providing network node 120. DT storage 1 912 may be associated with or under the control of the machine fluid producer 102. The distributed network node 904 or the distributed data consumption network node may be configured to access the machine fluid data as described above. The machine fluid data may include the data structures shown in Figures 3A and 3B.

[0220] The distributed network node 904 may be configured to read distributed material identifiers associated with materials used to produce mechanical fluids such as diester base stocks and fuel additives from the accessed relational representation. The distributed network node 904 may be configured to use the determined distributed material identifiers to access data from the distributed registry node 902 related to the relational representation associated with the distributed material identifiers. The distributed network node 904 or the distributed data consumption network node may be configured to access relational representations from, for example, the distributed data provision network node 2 908 associated with diester base stock data. The diester base stock data may be stored in a storage environment (DT storage 2 914) associated with the distributed data provision network node 2 908. DT storage 2 914 may be associated with or under the control of a diester base stock producer. The distributed network node 904 or the distributed data consumption network node may be configured to access the diester base stock data as described above.

[0221] The same procedure can be applied to fuel additive data. Thus, the distributed network node 904 may be configured to determine a bill of materials tree associated with the machine based on the accessed relational representation and the links between the distributed identifiers of the starting materials and the resulting product / intermediate product. The bill of materials tree may represent the relationships between the machine and all the materials used to produce it. Therefore, by recursively determining the distributed identifiers using the relational representation, it becomes possible to obtain machine fluid data and further material data used to produce the machine.

[0222] Material data collected by the distributed network node 904 may be provided to the ID provider 506. The ID provider 506 may use the collected data to generate maintenance data or control data, or provide the collected data to a system configured to generate maintenance data or control data, as illustrated in the following diagram.

[0223] Figure 11 schematically shows an exemplary apparatus for generating maintenance data associated with the maintenance of spent machine fluids. The apparatus may implement the method shown in Figure 13. The machine fluid may be present in the spent machine. The spent machine fluid may be selected from the group consisting of spent lubricant, spent engine coolant, and spent working fluid.

[0224] Referring to block 1302 in Figure 13, a computing device such as a code reader 202 may be used to identify machine identification information, as described in relation to Figure 5. The machine identification information may be used by an ID provider 506 to determine a distributed machine identifier, as described in relation to Figure 5.

[0225] Referring to blocks 1304 and 1304 of Figure 13, the machine fluid data associated with the used machine fluid may be collected from one or more participant nodes in the distributed network based on the distributed machine identifier provided by the ID provider 506. The collected machine fluid data may include status data. The collected machine fluid data may include operational data, including at least one predefined maintenance criterion. The predefined maintenance criteria may indicate that maintenance is required when such criteria are met. The machine fluid data may be read from different nodes associated with participants in the machine ecosystem, e.g., machine fluid producers, machine manufacturers, or any user of the machine. The machine fluid data may be associated with the history of the used machine fluid. The machine fluid data may include machine fluid characteristics, such as original viscosity, original permeability, machine fluid type, machine fluid production date, machine fluid material composition, number of cleaning cycles performed, or a combination thereof. The machine fluid data may be collected from different nodes associated with participants in the machine ecosystem. For example, status data such as current viscosity, current permeability, and cleaning operations performed may be collected from nodes associated with factory stakeholders or may be part of usage triggers. Status data may be collected based on access elements associated with such status data. Further status data related to the use of machine fluids related to machinery may be collected from nodes associated with machines or machine manufacturers involved in the machine ecosystem.

[0226] For the collection of machine-fluid data, distributed machine identifiers may be used as illustrated, for example, in relation to Figure 9. Distributed machine-fluid identifiers may be linked to distributed machine identifiers or distributed manufacturer identifiers (see, for example, Figure 10). Such links may be available to one or more stakeholders in the machine ecosystem.

[0227] Referring to block 1306 in Figure 13, the collected machine fluid data associated with the spent machine fluid can be analyzed by the maintenance data generator 1106 for the generation of maintenance data. The analysis may be based on the state of the spent machine fluid, the original properties of the machine fluid, and the maintenance properties of the machine fluid, as contained in the status data. Original properties may include the original viscosity and the original permeability of the produced machine fluid. Maintenance properties may include the maximum mileage or duration until maintenance work is required. Original properties and / or maintenance properties may be included in the machine fluid data. At least one physical and / or chemical property of the spent machine fluid can be determined from the machine fluid data collected via at least one distributed machine identifier associated with the spent machine fluid.

[0228] The physical and / or chemical properties of used mechanical fluid may relate to the physical and / or chemical state of the mechanical fluid. These physical and / or chemical properties may specify the wear of the mechanical fluid, including permeability, impurity levels, degree of wear, viscosity, age of the mechanical fluid, previous maintenance work performed, and maintenance conditions. The maintenance status may be determined based on the dispersed mechanical fluid identifier of the mechanical fluid and the associated mechanical fluid data.

[0229] The degree of impurities, specified by the permeability of the used mechanical fluid, and / or the degree of wear, indicated by the viscosity of the used mechanical fluid, may be used by the maintenance data generator 1106 to determine maintenance data. Maintenance data may be generated by comparing status data with mechanical fluid data. Specifically, maintenance data may be generated by comparing at least one physical and / or chemical property of the used mechanical fluid with the original property and / or maintenance property. Maintenance data may include data related to mechanical fluid maintenance intervals, data related to maintenance work to be performed on the used mechanical fluid, data related to at least one physical and / or chemical property of the used mechanical fluid, or a combination thereof. Maintenance data may be generated using a data structure that correlates the degree of wear with maintenance intervals and / or maintenance work.

[0230] Referring to block 1308 in Figure 13, the determined maintenance data may be provided to the maintenance data provider 1102. The maintenance data provider 1102 may be configured to provide the generated maintenance data to the machine user 110 and / or the machine repair shop 112. The maintenance data provider 1102 may provide the determined maintenance data via the distributed network 136. The maintenance data provider 1102 may provide the determined maintenance data via an application available to the machine user 110 and / or the machine repair shop 112. Figure 12 schematically shows a user interface for servicing used machine fluid when the used machine fluid may be provided to the holder of the used machine 110. The user interface 1202 may display information regarding the maintenance of the machine fluid, such as the mileage since the last cleanup and the date of the last cleanup. The user interface 1202 may display the status of the used machine fluid, such as the total mileage and the degree of impurities. The user interface 1202 may display the determined maintenance data.

[0231] Figure 14 schematically shows an exemplary apparatus for generating control data associated with spent machine fluid. The apparatus may implement the method shown in Figure 15. The machine fluid may be present in the spent machine. The spent machine fluid may be selected from the group consisting of spent lubricant, spent engine coolant, and spent working fluid.

[0232] Referring to block 1502 in Figure 15, a computing device such as a code reader 202 may be used to identify machine identification information, as described in relation to Figure 5. The machine identification information may be used by an ID provider 506 to determine a distributed machine identifier, as described in relation to Figure 5.

[0233] Referring to block 1504 in Figure 15, machine fluid data associated with used machine fluid may be collected from one or more participant nodes in the distributed network based on the distributed machine identifier provided by ID provider 506. The collected machine fluid data may include status data. The collected machine fluid data may include operational data, including at least one predefined maintenance criterion. The predefined maintenance criteria may indicate that maintenance is required when such criteria are met. The machine fluid data may be collected from different nodes associated with participants in the machine ecosystem, e.g., machine fluid producers, machine manufacturers, or any user of the machine. The machine fluid data may be associated with the history of used machine fluid. The machine fluid data may include machine fluid characteristics, such as original viscosity, original permeability, machine fluid type, machine fluid production date, machine fluid material composition, number of cleaning cycles performed, or a combination thereof. The machine fluid data may be collected from different nodes associated with participants in the machine ecosystem. For example, status data such as current viscosity, current permeability, and cleaning operations performed may be collected from nodes associated with plant participants or may be part of a usage trigger. Status data may be collected based on the access elements associated with the status data. Further status data related to the use of machine fluids related to the machine may be collected from nodes associated with the machine or machine manufacturer involved in the machine ecosystem.

[0234] For the collection of machine-fluid data, distributed machine identifiers may be used as illustrated, for example, in relation to Figure 9. Distributed machine-fluid identifiers may be linked to distributed machine identifiers or distributed manufacturer identifiers (see, for example, Figure 10). Such links may be available to one or more stakeholders in the machine ecosystem.

[0235] Referring to block 1506 of FIG. 15, the collected machine fluid data associated with the used machine fluid can be analyzed by the control data generator 1406 for the generation of control data. The analysis can be based on the state of the used machine fluid included in the status data, the original characteristics of the machine fluid, and the maintenance characteristics of the machine fluid. The original characteristics can include the original viscosity, the original permeability of the produced machine fluid. The maintenance characteristics can include the maximum mileage or duration until maintenance work is required. At least one physical and / or chemical characteristic of the used machine fluid can be determined from the machine fluid data collected via at least one distributed machine identifier associated with the used machine fluid.

[0236] The physical and / or chemical characteristics of the used machine fluid can be related to the physical and / or chemical state of the machine fluid. The physical and / or chemical characteristics can specify the wear of the machine fluid, including permeability, degree of impurities, degree of wear, viscosity, age of the machine fluid, previous maintenance work performed, and maintenance conditions. The maintenance status can be determined based on the distributed machine fluid identifier of the machine fluid and the machine fluid data associated therewith.

[0237] If the degree of impurities exceeds a first threshold, the wear of the machine fluid is designated as unacceptable, and the maintenance status is designated as cleanable, control data for cleaning the machine fluid can be generated. Such control data can include the permeability data of the used machine fluid and the distributed machine fluid identifier of the used machine fluid. The control data can further include the maximum threshold of the degree of impurities allowed for such a machine fluid. The control data can be provided to a node associated with the machine fluid cleaning vendor or the machine maintenance plant 112 for cleaning the machine fluid. The machine fluid can be cleaned according to methods known in the art for removing impurities. The success of the cleaning operation can be determined by measuring the permeability of the cleaned machine fluid. The cleaning operation can be carried out until the permeability of the cleaned machine fluid is below a given threshold, such as the threshold included in the control data.

[0238] If the degree of impurities exceeds a second threshold, the wear of the machine fluid is designated as unacceptable, and the maintenance state is designated as impossible to clean, control data for recycling the machine fluid can be generated. Such control data may include at least a part of the material composition of the machine fluid and a dispersed machine fluid identifier of the used machine fluid. The control data can be provided to nodes associated with one or more participants in the recycling chain.

[0239] If the viscosity is below a minimum threshold, the wear of the machine fluid is designated as unacceptable, and the maintenance state is designated as impossible to clean, control data for recycling the machine fluid can be generated. Such control data may include at least a part of the material composition of the machine fluid and a dispersed machine fluid identifier of the used machine fluid. The control data can be provided to nodes associated with one or more participants in the recycling chain.

[0240] Through such a decision tree, control data for cleaning and / or recycling can be generated by correlating at least one physical and / or chemical property of the used machine fluid with the processing characteristics of one or more devices configured to reuse the used machine fluid. In the case of cleaning, the degree of impurities as a physical property can be correlated with the maximum degree of impurities for the cleaning device. In the case of recycling, the material composition as a chemical property can be correlated with a suitable material composition for the recycling device.

[0241] The control data may include machine-readable instructions for processing the used machine fluid, including at least one dispersed identifier associated with at least one device configured to perform a reuse operation on the used machine fluid and at least one dispersed machine fluid identifier associated with the used machine fluid. The control data can be associated with one or more process steps for reusing the used machine fluid. The control data can be related to the chemical and / or physical treatment of the used machine fluid for recovering chemical materials as a recycle rate.

[0242] Referring to block 1508 in Figure 15, the control data may be configured to initialize a process for cleaning at least one used mechanical fluid. The control data may be provided to one or more nodes in a distributed network, one or more nodes may be associated with reusers, for example, who clean and / or recycle used mechanical fluids. The control data may include specifications for reuse methods, such as cleaning and / or recycling methods, cleaning operator identifiers, and / or recycler identifiers. Based on the generated control data, a reuse process, for example, for cleaning and / or recycling used mechanical fluids, may be initialized. For example, the cleaning process may be controlled according to the degree of impurities indicated by the control data.

[0243] The control data may be further configured to initialize a process for determining the duration of use of the mechanical fluid. For example, the control data may be used to determine how long the mechanical fluid has been used in the machine before it requires recycling. The determined duration may be used to determine the lease or rental fee associated with the use of the mechanical fluid. The lease or rental fee may further depend on the degree of wear, such as the degree of impurities. This makes it possible to rent or lease the mechanical fluid to machine manufacturers and / or machine users.

[0244] Figure 16 shows an example of a sensor-based sorting method for sorting waste mechanical fluids contained in machinery. Sorting of waste mechanical fluids present in machinery such as vehicles can be based on tracer materials (e.g., chemical compounds or materials uniquely linked to the mechanical fluid producer that produced the mechanical fluid containing each tracer material). Waste mechanical fluids may be selected from the group consisting of waste lubricants, waste engine coolants, and waste working fluids.

[0245] A machine user 110 may bring the machine to a machine repair shop 112 for maintenance. During maintenance, one or more samples of the machine fluid may be drawn. The samples may be analyzed in terms of permeability and / or viscosity, as described in relation to Figure 14. The machine fluid data may be collected via a distributed network through a distributed machine identifier associated with the machine, as described in relation to Figure 14. Control data indicating the recycling to be carried out may be generated, as described in relation to Figure 14.

[0246] The sample may be further analyzed, for example, as described in relation to Figure 17, to determine at least one tracer material present in the mechanical fluid. The waste mechanical fluid may be sorted into separate waste mechanical fluid fractions based on the determined tracer material. Each waste mechanical fluid fraction may be associated with a defined tracer material, which may then be associated with a specified mechanical fluid producer. This makes it possible to collect waste mechanical fluid for each mechanical fluid producer, and thus allows the mechanical fluid producer to recycle the compounds in the mechanical fluid to produce new mechanical fluid.

[0247] Figure 17 shows an example of waste mechanical fluid separation using the sensor-based sorting method shown in Figure 16. This is just one example based on the sorting system shown in Figure 16. Other sorting mechanisms may include similar stepwise sorting processes. The mechanical fluid waste fractions obtained from such sorting may differ from those shown as an example in Figure 17.

[0248] As shown in Figure 16, waste mechanical fluid 1702 can be sorted by a sensor-based sorting method. Figure 17 shows a fluorescence-based sorting 1704 that sorts into a fluorescent fraction 1706 containing specified fluorescent tracer material and a non-fluorescent fraction 1708. The fluorescent fraction 1706 containing specified fluorescent tracer material may be associated with mechanical fluid producer A 1716. The non-fluorescent fraction 1708 may contain non-fluorescent tracer material. The non-fluorescent fraction 1708 may not contain any tracer material at all, for example, it may not contain any tracer material at all.

[0249] Non-fluorescent fraction 1708, containing non-fluorescent tracer material, can be separated using a method configured to detect one or more ions in the waste mechanical fluid, such as ICP-MS (inductively coupled plasma-mass spectrometry), which allows for separation into ion-containing fraction 1712 and waste 1714. Ion-containing fraction 1712, containing specified tracer ions, can be associated with mechanical fluid producer B 1718 and mechanical fluid producer C 1720.

[0250] Multisensor systems, such as the one shown in Figure 17, necessary to reach the sorting depth required for further processing of mechanical fluid waste fractions are complex, costly, and limited in terms of the quality of mechanical fluid waste fractions required for reuse. For example, the degree of contaminants can affect whether waste mechanical fluid can be recycled by a given recycling process. For example, waste lubricants can be recycled through regeneration to obtain base oil. Regeneration may involve the removal of contaminants, oxidation products, and additives. However, contaminants such as chlorine and PCBs, or certain chemical compositions of lubricants, may hinder regeneration, and therefore such lubricants may be unsuitable for regeneration.

[0251] To overcome these shortages and quality problems, more extensive sorting of waste mechanical fluids is conceivable. However, mechanical fluid waste is difficult to separate into fractions for reuse because it is unlabeled and may contain different chemical compositions depending on the used machinery. For example, the composition of the fractions can have a critical impact on the quality and / or yield of recyclables such as base oils that can be extracted from lubricant waste fractions. Such base oils can be produced by the regeneration of lubricant waste fractions. However, the quality of the base oils depends on the composition of the lubricant waste fractions. For example, contaminants affect quality despite manual collection schemes and degrade the quality of the base oils.

[0252] In other words, in the case of mechanical fluid waste recovered by mixed recovery, excessive contaminants or additional sorting processes are required, while the value of the recycled material automatically decreases, and therefore the range of applications for which the recycled material can be used is limited, potentially leading to the interruption of sorting. By developing a more intelligent sorting scheme for separating waste mechanical fluids with varying mechanical fluid compositions, contamination levels will decrease, sorting efficiency will increase, and the quantity and quality of the recycled material will improve.

[0253] Figure 18 shows a sorting system for sorting waste machine fluid, comprising a distributed network interface 1804 according to an exemplary embodiment of the present invention. Waste machine fluid may be present in used machinery. The waste machine fluid may be selected from the group consisting of waste lubricant, waste engine coolant, and waste working fluid.

[0254] The sorting system 1808 may include an interface 1804 to a distributed network node 1812 associated with the sorting system 1808. The distributed network node 1812 may be connected to the distributed network 136, for example, as shown and described in relation to Figure 1.

[0255] The sorting system 1808 may further include an ID reader 504, mounted on the machine 918 and configured to read identifier elements such as a machine identifier, as illustrated, for example, in relation to Figure 5. The ID may be provided to a machine fluid data collector 1804 configured to collect machine fluid data. Based on the detection, a distributed machine identifier associated with the machine may be determined by the machine fluid data collector 1804, as illustrated, for example, in relation to Figure 5. The distributed machine fluid identifier may be collected using the distributed machine identifier, as illustrated, in relation to Figures 9 to 11. Based on the distributed machine fluid identifier, machine fluid data associated with the waste machine fluid 1814 may be collected from the distributed network node 120 of the distributed network 136. The machine fluid data of 1814 may include machine fluid composition data and / or status data. For example, the machine fluid composition data may relate to the chemical compounds used to manufacture the machine fluid, the chemical compounds contained in the machine fluid, the recycled content of the machine fluid, and / or the biobase content of the machine fluid. Furthermore, status data may indicate the status of used mechanical fluids in a decommissioned state, as illustrated in relation to Figure 5, for example. This may be particularly relevant to recycling streams where the degree of degradation of the waste mechanical fluid does not allow for the implementation of one or more recycling processes.

[0256] By accessing the digital twin of the discarded machine fluid 1814 via a distributed machine identifier, the machine fluid data can be read from a distributed network node 120 associated with an entity 102 that owns or provides such data.

[0257] Based on such data read via the distributed network 1812, the sorting command generator 1808 can generate sorting data according to the characteristics of the waste mechanical fluid 1814, such as material composition data and / or status data. This enables simple sorting of the waste mechanical fluid 1814 by accessing the data via the distributed network 136. As a result, the sorting depth is extended by the data available via the distributed network 136 without requiring further sensors and multi-layer sorting machines, as described, for example, in relation to Figures 16 and 17. The proposed simple data-driven sorting system 1808 can be used as an extension of or in combination with a sensor-based sorting system, such as the one shown in Figure 16. Thus, waste mechanical fluids 1814 that are not digitally linked to their respective machines via the linking of their respective distributed identifiers (see, for example, Figure 10) can be sorted by the sensor-based system, while waste mechanical fluids 1814 that are digitally linked to their respective machines via their respective distributed identifiers can be sorted at a higher sorting depth.

[0258] In addition, enhanced sorting depth through data availability via the distributed network 136 allows for improved tracking and tracing of the composition of the sorted mechanical fluid waste fractions 1816-1822. For example, the distributed mechanical fluid identifier associated with the waste mechanical fluid 1814 collected by the sorting system 1808 can be stored according to the sorted fractions 1816-1822. Based on the distributed mechanical fluid identifier and sorting logic (explained in more detail in Figure 20), control data can be generated to sort each waste mechanical fluid 1814 into its dedicated mechanical fluid waste fraction 1816-1822. The distributed waste mechanical fluid 1814 identifier associated with the waste mechanical fluid 1814 can be assigned to the fraction ID associated with each waste fraction 1816-1822 into which the waste mechanical fluid 1814 is sorted. Thus, the mechanical fluid data for each mechanical fluid 1814 accessed by the distributed mechanical fluid identifier can be stored in relation to the waste fraction ID. Once the batch of waste fractions 1816-1822 is complete, the collected mechanical fluid data can be aggregated into fraction data by assigning a dispersed mechanical frid identifier associated with the fraction. Such assignments can be performed when controlling the sorting process. For example, composition data for each dispersed identifier can be aggregated by the composition, compound, or component contained in waste fractions 1816-1822, and the respective amounts thereof. Furthermore, for example, status data for each dispersed mechanical frid identifier can be aggregated to specify the degree of impurity or the degree of degradation (via viscosity). The fraction IDs and fraction data can be provided to the distributed network 136 for access by distributed network nodes 120-130 associated with other stakeholders 102-116 of the distributed network 136.

[0259] Figure 19 shows a flowchart of an example of a sorting method for sorting waste machine fluids, which may be implemented in the sorting system of Figure 18. Waste machine fluids may be present in used machinery. Waste machine fluids may be selected from the group consisting of waste lubricants, waste engine coolants, and waste working fluids.

[0260] In contrast to the examples shown in FIGS. 16 and 17 where multiple sensors are required to achieve a meaningful sorting depth, the sorting system of FIG. 18 enables a simpler and more reliable sorting. As shown in FIG. 18, sorting can be performed in a single step based on a distributed machine fluid identifier and data accessible through an interface 1812 for such a distributed machine fluid identifier to a distributed network 136. As a result, a stepwise sorting process based on different sensor technologies can be avoided, and sorting can be performed more efficiently. FIG. 19 shows the single-shot sorting depth achievable by the sorting system of FIG. 18 compared to a sensor-based sorting method using a stepwise sorting depth as shown in FIG. 17.

[0261] FIG. 20 shows a flowchart of an example of a sorting method that can be implemented by a sorting system having the distributed network interface of FIG. 18.

[0262] A machine containing waste machine fluid 1814 may include an identification element associated with a per-machine distributed machine identifier. The identification element can be detected as described in connection with FIG. 5 (see block 2002). The per-machine distributed machine identifier can be provided based on such detection, for example, as described in connection with FIG. 5 (see block 2004). The distributed machine identifier can be used to collect distributed machine fluid identifiers, for example, as described in connection with FIGS. 9 - 11. Based on the distributed machine fluid identifier, machine fluid data associated with the waste machine fluid 1814, such as composition data and / or status data, can be collected by accessing a distributed network node 120 of a distributed network 136 associated with a machine fluid producer 102 as shown in connection with FIG. 1.

[0263] Composition data and / or status data may be collected from one or more distributed network nodes 120 of the distributed network 136 (see block 2006). For example, mechanical fluid data and / or status data may be provided by a distributed network node 120 associated with mechanical fluid producer 102. Furthermore, for example, vehicle data may be provided by a distributed network node 122 associated with machine producer 108. Furthermore, for example, data on production inputs used to produce mechanical fluid may be provided by a distributed network node 118 associated with input material supplier 106. To provide data associated with the characteristics of 1814 from distributed network node 118, a distributed mechanical fluid identifier associated with mechanical fluid 1814 may be linked to a distributed identifier associated with the physical entity of the material or product used to produce the mechanical fluid 1814. To provide data associated with the characteristics of 1814 from distributed network node 122, a distributed mechanical fluid identifier associated with mechanical fluid 1814 may be linked to a distributed identifier associated with the physical entity of the product produced using the mechanical fluid 1814.

[0264] Linking distributed identifiers along the material flow enables tracking of the composition and / or status of machine fluids. Identifier linking can be resolved by an identifier management system of the distributed network 136 based on a distributed machine identifier associated with a machine, as illustrated, for example, in relation to Figure 9. Depending on the data requested by a distributed network node 1812 associated with a machine repair shop 112 or an EOL product collector / sorter 114, the identifier management system may manage the process of resolving linked identifiers and accessing the respective data-providing network nodes. Identifier links may be provided when providing a distributed machine identifier associated with a machine, including waste machine fluid 1814. For example, identifier links may be part of a machine passport associated with a machine. A machine passport may include a distributed machine identifier associated with a machine, a digital representation or link to machine data, and a distributed identifier associated with the machine fluid used to produce the machine and linked to the distributed machine identifier associated with the machine.

[0265] If machine fluid data cannot be collected, for example, if the link between distributed machine identifiers and distributed machine fluid identifiers cannot be determined or does not exist, fraction control data may be generated to separate machine fluids without machine fluid data from machine fluids from which machine fluid data has been collected (see Blocks 2008 and 2010). Machine fluid waste without machine fluid data may be fed into sensor-based sorting methods, such as those described in relation to Figures 16 and 17.

[0266] Based on the collected mechanical fluid data, fraction control data can be generated (see Block 2014). The waste mechanical fluid 1814 can be sorted according to the fraction control data. For example, the sorting system 1808 may include classification instructions configured to match producer data contained in the collected mechanical fluid data to a predetermined fraction of such mechanical fluid producer. This may allow the waste mechanical fluid to be returned to the mechanical fluid producer for recycling. This may improve recycling efficiency because the mechanical fluid producer knows the composition of the mechanical fluid and can therefore select an appropriate recycling process based on the known mechanical fluid composition.

[0267] Furthermore, for example, the sorting system 1808 may include classification commands configured to match status data to predetermined fractions of such status data. A predetermined fraction may specify the type of mechanical fluid, a range of impurity levels, the exclusion of specific compounds contained in the mechanical fluid, or a combination thereof. A predetermined waste fraction may specify the type of mechanical fluid contained in the waste fraction, for example, depending on the recycling process and further use of the recyclet. For a particular mechanical fluid 1814, the waste mechanical fluid 1814 can be separated into predefined fractions by matching characteristic data accessed via the distributed network 136 to the classification commands.

[0268] Mechanical fluid data and / or dispersion IDs may be collected for each mechanical fluid 1814 and for each fraction. The dispersion IDs and / or mechanical fluid data collected for each fraction may be assigned to fraction identifiers, such as the dispersion identifier for each fraction. The collected dispersion mechanical fluid identifiers and / or mechanical fluid data may be aggregated into fraction data. The fraction data may be related to the fraction composition and / or fraction status. For example, the composition data for each dispersion mechanical fluid identifier may be aggregated by the respective amounts of compounds, compositions, and / or quantities contained in the waste fraction. Furthermore, for example, the status data for each dispersion mechanical fluid identifier may be aggregated to indicate the degree of impurities and / or the degree of degradation.

[0269] Based on the classification and / or aggregated fraction data, the recycling process and / or mechanical fluid producer may be determined and / or assigned to a fraction identifier. The classification may include classifications specific to the recycling process and / or classifications specific to the mechanical fluid producer. For example, the material composition for each fraction may be specified to include a first class of lubricants and exclude a second class of lubricants. The first class may include lubricants with low chlorine and PCB content. For such lubricants, regeneration (e.g., chemical and / or physical recycling) may be specified as the recycling process.

[0270] The second class of lubricants can exclude lubricants unsuitable for recycling and contaminants that impair the quality of the recycle rate. These contaminants may include chlorine and PCBs. Therefore, by eliminating such substances or contaminants for recycling, already at the sorting stage of mechanical fluid waste through tracked compositional data accessible via a distributed network, a higher quality waste fraction, base oil, is obtained, resulting in safer and more reliable operation when supplied to the recycling process.

[0271] Each fraction may be assigned a fraction ID and a recycling process ID that specifies the recycling process, such as mechanical, chemical, and / or thermal (incineration). The fraction ID may include a distributed identifier. The recycling process ID may include a distributed identifier. The distributed identifier may be associated with aggregated fraction data.

[0272] Each fraction may be assigned a fraction ID and a mechanical fluid producer ID that specifies the mechanical fluid producer.

[0273] Fraction data may be provided for access to distributed network nodes 120 and 130. Fraction data may be provided by providing distributed identifiers associated with the fractions to the distributed network 136. Fraction data may be provided by distributed network node 128 associated with EOL product collector / sorter 114. Fraction data may be provided by distributed network node 128 associated with machine shop 112. Fraction data may be stored in dedicated storage associated with EOL product collector / sorter 114 or machine shop 112. Access to the fraction data may be provided by providing a representation that links to the fraction data or a representation that points to the fraction data. Distributed IDs and representations linked to or pointing to aggregated fraction data stored in dedicated storage associated with EOL product collector / sorter 114 or machine shop 112 may be provided to the distributed network 136 for access by nodes associated with other stakeholders in the distributed network 136. Fraction data may be provided by a distributed data provision network node 128 associated with an EOL product collector / sorter 114. Fraction data may be provided by a distributed data provision network node 126 associated with a machine repair shop 112. Fraction data may be accessed by a distributed data consumption network node 130 associated with a recycler 116, or by a distributed data consumption network node 120 associated with a machine fluid producer 102.

[0274] Figure 21 shows an exemplary data structure used in the sorting method of the selection method in Figure 18, based on mechanical fluid data accessible via a distributed network interface.

[0275] The data structure shown in Figure 21 is based on mechanical fluid data. Mechanical fluid data can be read from nodes 120 associated with mechanical fluid producers 102 in the distributed network 136 based on distributed identifiers (see Figure 1). Mechanical fluid data can be read from nodes 120 associated with stakeholders 102 in the distributed network 136 that own the respective data. Mechanical fluid data packages 1-5 can specify a mechanical fluid type and a mechanical fluid producer for each waste mechanical fluid. A predefined classification can be configured to sort one mechanical fluid type from each mechanical fluid producer into a single waste fraction. In this way, the quality of the sorted waste fraction can be improved with respect to the reuse of the waste fraction.

[0276] Figure 22 shows an example of a predefined classification configured to separate waste machine fluids by a recycling process and / or by a machine fluid producer. Waste machine fluids may be present in end-of-life machinery. Waste machine fluids may be selected from the group consisting of waste lubricants, waste engine coolants, and waste working fluids.

[0277] As shown in Figures 18 to 21, mechanical fluid data may be provided to the sorting system 1808 via an interface 1816 configured to retrieve data from nodes 120 and 122 of a distributed network 136. The data may relate to material composition and / or status data and / or mechanical data. A predefined classification may be configured to sort waste mechanical fluid 1814 into waste fractions according to material composition and / or status data and / or producer data. The data collected for each waste mechanical fluid 1814 may be aggregated. In addition, the predefined classification may be configured to assign a recycling process to each sorted waste fraction. Recycling processes may include mechanical, chemical, and / or thermal recycling processes. Recycling processes for lubricants may include cleaning, regeneration, regeneration, direct combustion, light reprocessing, heavy reprocessing, and pyrolysis. Cleaning may include removal of solids by filtration, dehydration by vacuum distillation, and addition of fresh additives. Minor reprocessing may involve the removal of water and sediment from heavily contaminated waste lubricants. After this process, the oil may contain metals, halogens, and sulfur, but can be further used as alternative fuel oil (RFO) for combustion at the Lodestone plant, blended with fuel oil, or used in power plants. Heavy reprocessing aims to separate the flammable portion of heavily contaminated WLO from the undesirable bottom fraction containing metals, non-flammable ash, and dust. Chemical or thermal treatments are applied to produce demetallized heavy fuel oil (HFO), also known as heavy fraction, which can be used as marine diesel oil (MDO), etc. Pyrolysis is based on the principle of breaking down larger hydrocarbon molecules with about 30 carbon atoms by heating them in a pressurized vessel to obtain hydrocarbons with 10-18 carbon atoms. High-quality products such as demetallized HFO and gas oil products are obtained. Recycling processes for engine coolants may include distillation and / or ion exchange processes to recover ethylene glycol and / or propylene glycol. The recycling process for brake fluid may involve chemical processes such as esterification.

[0278] As shown in Figure 22, the ID of a sorted fraction may be assigned to a recycling process ID and / or a mechanical fluid producer ID. A predefined classification may be used for sorting by a sorter. The sorter may associate a distributed mechanical fluid identifier associated with the fraction ID with the fraction. The fraction ID may include or be associated with the distributed identifier of the fraction. The fraction ID and associated fraction data may be provided by a distributed network node 1816 associated with an EOL product collector / sorter 114 or machine repair shop 112 that sorts mechanical fluid waste, for access by distributed network nodes 120 and 130 of the distributed network 136. The recycling process ID or producer ID associated with the fraction ID may also be provided by a distributed network node 1816 associated with an EOL product collector / sorter 114 or machine repair shop 112 that sorts mechanical fluid waste, for access by distributed network nodes 120 and 130 of the distributed network 136. The fraction ID and the recycling process ID or producer ID can be accessed by the distributed network nodes 130 of 116 or the distributed network node 120 of the mechanical fluid producer 102. Based on the fraction ID, the recycler 116 or mechanical fluid producer 102 can retrieve the fraction data and / or the recycling process ID or producer ID from the distributed network node 1816 associated with the EOL product collector / sorter 114 or the machine repair shop 112. The recycler 116 or mechanical fluid producer 102 can store the fraction data and / or the recycling process ID / producer ID in dedicated storage associated with the recycler 116 or mechanical fluid producer 102, respectively. Based on the fraction ID, fraction data, and recycling process ID, the recycler 116 can operate a recycling process. Based on the fraction ID, fraction data, and producer ID, the mechanical fluid producer 102 can operate an appropriate recycling process. The fraction data can be used to aggregate recycle rate data.A recycle rate ID can be assigned to each recycle rate produced from each fraction. In this way, not only the sorting process but also the recycling process can be monitored and / or controlled.

[0279] This disclosure has been described in conjunction with preferred embodiments and examples. However, a person skilled in the art who practices the invention described in the claims will be able to understand and implement other variations by examining the drawings, this disclosure, and the claims.

[0280] Any of the steps presented herein can be performed in any order. The methods disclosed herein are not limited to any particular order of these steps. It is not required that different steps be performed in a specific location or on a specific computing node of a distributed system; that is, each step may be performed on a different computing node using different equipment / data processing.

[0281] As used herein, “determine” also includes “initiate or cause to determine,” “generate” also includes “initiate and / or cause to generate,” and “provide” also includes “initiate or cause to determine, generate, select, transmit and / or receive.” “Initiate or cause to perform an action” includes any processing signal that triggers a computing node or device to perform the respective action.

[0282] In the claims and herein, the terms “comprising” do not exclude other elements or steps, and the indefinite articles “a” or “an” do not exclude plurals. A single element or other unit may perform the function of several entities or items described in the claims. The mere fact that certain means are described in different dependent claims does not imply that a combination of these means cannot be used in a favorable implementation.

Claims

1. A method for monitoring a machine containing a mechanical fluid during use, particularly a computer-based method, wherein the method is - To provide at least one usage trigger that includes at least one distributed machine identifier associated with the machine fluid, - Collecting status data associated with the machine fluid via the at least one distributed machine identifier, - To provide one or more distributed mechanical fluid identifiers associated with the status data, - To generate one or more digital representations of the aforementioned status data, - To generate an access element including one or more distributed mechanical fluid identifiers and one or more digital representations, A method comprising: providing the access element to a distributed network for access to the status data by one or more data consumption network nodes of the distributed network, under the control of a data provision network node associated with the producer of the mechanical fluid.

2. The method according to claim 1, wherein the usage trigger is provided by the producer or machine user of the mechanical fluid and / or the usage trigger is provided based on a predetermined criterion.

3. The method according to claim 1 or 2, wherein the status data includes at least one physical and / or chemical property of the used mechanical fluid, at least one physical and / or chemical property of the used machine, maintenance data relating to maintenance work performed on the used mechanical fluid, a location associated with the maintenance work, or a combination thereof.

4. The method according to any one of claims 1 to 3, wherein the status data is collected from one or more data-providing network nodes associated with machine manufacturers and / or machine users and / or machine maintenance facilities connected via a distributed network, and the data-providing network nodes from which the status data is collected are selected based on the distributed machine identifier associated with the machine.

5. The method according to any one of claims 1 to 4, wherein providing the one or more distributed mechanical fluid identifiers includes collecting at least a portion of the identifiers from existing mechanical fluid data associated with the mechanical fluid.

6. The method according to any one of claims 1 to 5, further comprising the step of determining at least one physical and / or chemical property of the used mechanical fluid from at least a portion of the collected status data.

7. The method according to any one of claims 1 to 6, further comprising the step of updating existing mechanical fluid data associated with the mechanical fluid using at least a portion of the collected status data and / or using at least physical and / or chemical properties determined from the collected status data.

8. The method according to any one of claims 1 to 7, wherein the access element is provided for access to the status data, which includes data dependent on the reuse operations and / or the participant identifiers, by one or more data-consuming network nodes associated with one or more maintenance operators performing one or more reuse operations, relating to authorization rules that provide access to the status data, which includes data dependent on the reuse operations and / or the participant identifiers.

9. A method for monitoring a machine containing a mechanical fluid during use, particularly a computer-based method, wherein the method is - To provide at least one usage trigger, which includes at least one distributed machine identifier associated with the machine and status data associated with the machine fluid, - To provide one or more distributed mechanical fluid identifiers associated with the status data, - To generate one or more digital representations of the aforementioned status data, - To generate an access element including one or more distributed mechanical fluid identifiers and one or more digital representations, A method comprising: providing the access element to a distributed network for access to the status data by one or more data consumption network nodes of the distributed network, under the control of a data provision network node associated with the producer of the mechanical fluid.

10. A method for accessing status data related to monitoring mechanical fluids used in a machine, particularly a method performed by a computer, wherein the method is - To provide at least one distributed machine identifier associated with the machine, - Collecting one or more access elements generated and / or provided in accordance with the method described in any one of claims 1 to 8 via the provided distributed machine identifier, A method comprising: requesting access to the status data from the producer of the mechanical fluid.

11. A method for generating maintenance data associated with the maintenance of used machine fluid, particularly a computer-based method, wherein the machine fluid is used in a machine, and the method - To provide at least one distributed machine identifier associated with the machine, - Based on the provided distributed machine identifier, machine fluid data including status data associated with the used machine fluid and accessed according to the method of claim 10 is collected by the distributed network node from the distributed network node, - To generate maintenance data by correlating the collected mechanical fluid data with the accessed status data, A method comprising providing the generated maintenance data for the maintenance of the used mechanical fluid.

12. Use of maintenance data generated according to the method of claim 11 for controlling the maintenance of used mechanical fluid.

13. A method for performing one or more reuse operations on used mechanical fluid, particularly a computer-based method, wherein the mechanical fluid is used in a machine, and the method is - To provide at least one distributed machine identifier associated with the machine, - To collect status data associated with the used mechanical fluid in accordance with the method described in claim 10, - To generate control data by correlating the collected status data with one or more devices configured to perform reuse operations on the used mechanical fluid, and by generating machine-readable commands to control reuse by the one or more devices configured to perform the reuse operations, A method comprising: providing generated control data, which includes machine-readable instructions for performing one or more reuse operations on the used mechanical fluid by one or more devices configured to perform the reuse operations.

14. An apparatus for performing one or more reuse operations on used mechanical fluid, wherein the mechanical fluid is used in a machine, and the apparatus performs one or more reuse operations on used mechanical fluid. - An identifier providing interface configured to provide at least one distributed machine identifier associated with the machine, - A distributed network interface configured to collect status data associated with the used mechanical fluid according to the method of claim 10, - A control data generator configured to generate control data by correlating the collected status data with one or more devices configured to perform reuse operations on the used mechanical fluid, and by generating machine-readable commands to control reuse by the one or more devices configured to perform the reuse operations, - A control data provider configured to provide generated control data, including machine-readable instructions, for performing one or more reuse operations on the used mechanical fluid by one or more devices configured to perform the reuse operations.

15. A method for sorting waste mechanical fluid, in particular a computer-based method, wherein the method is - A step of detecting at least one identifier element for each machine containing at least one waste machine fluid, wherein the at least one identifier element relates to at least one distributed machine identifier associated with each machine, - A step of providing the distributed machine identifier associated with the machine, and collecting machine fluid data based on the distributed machine identifier, wherein the machine fluid data is provided based on the distributed machine identifier provided by one or more network nodes of the distributed network. - A step of allocating mechanical fluid waste to one or more mechanical fluid waste fractions based on the collected mechanical fluid data, wherein the one or more mechanical fluid waste fractions relate to waste fractions that are processed by a specified mechanical fluid producer, and / or a physical recycling process, and / or a chemical recycling process, and / or a recycling process involving physical and chemical treatment, and / or a thermal recycling process, - A step of generating sorting data for sorting the mechanical fluid waste into the assigned mechanical fluid waste fraction based on the assigned mechanical fluid waste fraction, A method comprising the step of providing generated sorting data for sorting the mechanical fluid waste into the assigned mechanical fluid waste fraction.

Images