Fluid Machine Data Consent via GUI for Third-Party Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for acquiring operational data from fluid machines are cumbersome and inefficient, requiring manual contract agreements for each transaction, especially when a third party other than the machine owner seeks to utilize the data.
Innovation Solution
A fluid machine equipped with a GUI and communication apparatus allows for simplified consent and transmission of operational data to external servers via wired or wireless communication, enabling direct input and output of data usage permissions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual contract conclusion procedures are used for data acquisition, then legal agreements can be established, but the process becomes cumbersome and inefficient
Solution Approach 1:
The patent replaces manual mechanical contract conclusion processes with automated electronic systems. The controller automatically transmits operational data to external servers through communication apparatuses, eliminating the need for manual document exchange and signature procedures while maintaining legal validity through electronic contract formation.
Solution Approach 2:
The system enables self-service data transmission where the fluid machine's controller automatically handles data acquisition and transmission without requiring manual intervention from the owner or third parties. The GUI allows users to configure preferences, and the system autonomously executes data transmission based on established agreements.
2Adaptability or versatility
If third parties acquire operational data without simplified procedures, then data can be obtained for service provision, but administrative burdens increase
Solution Approach 1:
The communication apparatus and controller serve multiple functions: they manage data transmission to various external servers, handle different types of operational data, support multiple communication protocols, and facilitate both service provision and data analysis purposes. This multi-functionality reduces the need for separate administrative procedures for each data sharing scenario.
Solution Approach 2:
The controller acts as an intermediary between the fluid machine and external servers. It automatically manages the data transmission process, authenticates third parties, and handles the contractual agreements, thereby simplifying the administrative burden on owners and reducing the complexity of data sharing operations.
3Productivity
If automated data transmission is implemented, then operational data can be transmitted efficiently, but consent management becomes more complex
Solution Approach 1:
The system obtains user consent and establishes data sharing agreements in advance before automated transmission begins. The GUI allows users to pre-configure their data sharing preferences and authorize third parties, so that when automated transmission occurs, the consent management is already in place, eliminating the need for real-time complex consent management during data transmission.
Data Source
AI summary
An object is to proceed with a contract-concluding process for an operational data transaction simply, conveniently and clearly. A fluid machine including: a driving source; a fluid machine body that generates a fluid by a driving force of the driving source; a controller that has a GUI allowing an external input and output, and controls driving of the driving source; and a communication apparatus that allows communication with an external server via a wired or wireless communication line. In the fluid machine, when transmitting operational information of the fluid machine to the external server, the external server being owned by a third party other than an owner or an authorized person of a legitimate use right of the fluid machine or the external server whose legitimate use right being held by the third party, the controller transmits the operational information after receiving, via the GUI, an input indicating that the operational information is approved to be output to the third party and to be used by the third party.