Information processing method, computer program, and information processing device
The information processing method and device address the limitations of conventional emulators by providing scenario-based data simulation, reducing costs and time, and enabling simulation of diverse environments.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-09-30
- Publication Date
- 2026-04-09
AI Technical Summary
Conventional device emulators cannot reproduce complex operation patterns, necessitating the use of actual machines for reproduction tests, which incur high costs and labor, and are limited to obtaining data from the installed environment.
An information processing method and device that provides scenario information based on application type and conditions, reads operating data from a database, and converts it for the destination system using a scenario server and emulator.
Enables efficient simulation of equipment operation scenarios without the need for actual machines, reducing costs and time, and allowing data from various environments to be simulated.
Smart Images

Figure 2026062017000001_ABST
Abstract
Description
Technical Field
[0004]
[0001] The present invention relates to an information processing method, a computer program, and an information processing apparatus.
Background Art
[0002] Patent Document 1 discloses a simulation apparatus for plant equipment that receives operation information indicating the operation state of plant equipment, sets the operation state of the plant equipment based on the operation information, and simulates the generation of data related to the plant equipment.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] Conventional device emulators cannot output complex patterns of operation data, so they cannot reproduce operation situations such as those in specific environments or during device failures. Therefore, when reproduction tests or the like are required, or when developing and testing applications for needs such as seasons and weather in various regions, the only option was to prepare the same environment and conditions and verify using actual machines.
[0005] When using actual machines, there are problems such as the need for purchase costs, labor costs, and installation man-hours to prepare the actual machines, the time required for accumulating and preparing time-series operation data, and the fact that only operation data in the environment where the actual machines are installed can be obtained. <00OO029>
[0006] The purpose of this disclosure is to provide an information processing method, a computer program, and an information processing device that can present scenario information to a user according to the type of application and the conditions required for scenario selection, read operating data of equipment from a database according to the scenario information selected by the user, and transmit the converted operating data according to the destination. [Means for solving the problem]
[0007] The information processing method relating to the first aspect of this disclosure receives the type of application program relating to the equipment, a scenario representing the state or operating environment of the equipment, or conditions necessary for selecting a scenario for a specific model or specific equipment configuration of the equipment, outputs one or more scenario information representing the state or operating environment of the equipment according to the received type and conditions, receives a selection of the output scenario information, reads the operating data of the equipment from a database according to the selected scenario information, converts the read operating data into operating data corresponding to the destination, and transmits it to the destination, all of which are performed by a computer.
[0008] The information processing method relating to the second aspect of this disclosure, in the information processing method relating to the first aspect, includes whether or not there is an abnormality in the equipment.
[0009] The information processing method relating to the third aspect of this disclosure is an information processing method relating to the first or second aspect, wherein the usage environment includes at least one of the country or region where the equipment is installed, the season in which the equipment is used, the weather in the country or region where the equipment is installed, and the type of object on which the equipment is installed.
[0010] The information processing method relating to the fourth aspect of this disclosure is an information processing method relating to any one of the first to third aspects, wherein the computer performs a process to output at least one of the following: scenario information that matches the received conditions, scenario information similar to the received conditions, scenario information extracted according to past selection history, and scenario information that is frequently used in the application program.
[0011] The information processing method relating to the fifth aspect of this disclosure is an information processing method relating to any one of the first to fourth aspects, wherein the operating data of the equipment and condition information are associated and stored in the database as scenario information, and the computer performs a process of reading out the scenario information to be output by referring to the database.
[0012] The information processing method relating to the sixth aspect of this disclosure is an information processing method relating to any one of the first to fifth aspects, wherein the database stores in association the operating data, regional information, weather information, failure information, and date and time information of equipment installed in various regions.
[0013] The computer program relating to the seventh aspect of this disclosure is a computer program that causes a computer to perform the following processes: receiving the type of application program relating to equipment, a scenario representing the state or operating environment of the equipment, or conditions necessary for selecting a scenario for a specific model or specific equipment configuration of the equipment; outputting one or more scenario information representing the state or operating environment of the equipment according to the received type and conditions; receiving a selection of the outputted scenario information; reading the operating data of the equipment from a database according to the selected scenario information; converting the read operating data into operating data appropriate for the destination; and transmitting it to the destination.
[0014] The information processing device relating to the eighth aspect of this disclosure comprises at least one processing unit, which receives the type of application program relating to the equipment, a scenario representing the state or operating environment of the equipment, or conditions necessary for selecting a scenario for a specific model or specific equipment configuration of the equipment, outputs one or more scenario information representing the state or operating environment of the equipment according to the received type and conditions, receives a selection of the output scenario information, reads the operating data of the equipment from a database according to the selected scenario information, converts the read operating data into operating data corresponding to the destination, and transmits it to the destination. [Effects of the Invention]
[0015] According to this disclosure, scenario information can be presented to the user according to the type of application and the conditions required for scenario selection. Based on the scenario information selected by the user, operating data for equipment can be read from the database, and the converted operating data can be sent according to the destination. [Brief explanation of the drawing]
[0016] [Figure 1] This is a schematic diagram showing an example configuration of an information processing system according to an embodiment. [Figure 2] This is a block diagram showing the internal configuration of the developer terminal. [Figure 3] This is a block diagram showing the internal configuration of the scenario server. [Figure 4] This is a conceptual diagram showing an example of the database configuration provided by the device cloud. [Figure 5] This is an explanatory diagram illustrating an example of storing driving data in a scenario database. [Figure 6] This is a conceptual diagram showing an example of the structure of a scenario database. [Figure 7] This is a schematic diagram showing an example of a user interface screen displayed on a developer's terminal. [Figure 8] This is a flowchart illustrating the steps of the process executed by the scenario server.
Embodiments of the Invention
[0017] Hereinafter, an information processing system according to an embodiment will be specifically described based on the drawings. FIG. 1 is a schematic diagram showing a configuration example of an information processing system 1 according to an embodiment. The information processing system 1 according to the embodiment includes a developer terminal 10 used by an application developer (hereinafter simply referred to as a developer), a scenario server 20 that presents various scenario information to the developer, and a device emulator 30 that converts operation data of facility equipment extracted according to the scenario information selected by the developer into data that can be used in the destination system. The developer terminal 10 and the scenario server 20 are communicably connected to each other via a first communication network NW1. Also, the scenario server 20 and the device emulator 30 are communicably connected to each other via a second communication network NW2.
[0018] In the example of FIG. 1, the first communication network NW1 and the second communication network NW2 are described separately for convenience, but these networks do not necessarily have to be different networks.
[0019] The information processing system 1 also includes a device cloud MC that collects and stores operation data from facility equipment, and a scenario database DB that stores various scenario information related to facility equipment. The device cloud MC and the scenario database DB are both accessible from the scenario server 20, and output operation data and scenario information, respectively, in response to requests from the scenario server 20.
[0020] In this embodiment, the developer is a developer who develops various application programs (also called applications or apps) related to equipment. One example of equipment is refrigeration and air conditioning equipment. Refrigeration and air conditioning equipment refers to equipment connected to refrigerant piping and constituting a refrigeration cycle. Refrigeration and air conditioning equipment includes equipment such as outdoor units, indoor units, ventilation systems, heat source equipment, and central control devices that constitute an air conditioning system, and equipment such as refrigerators, heat exchangers, and control devices that constitute a refrigeration system. Equipment is not limited to refrigeration and air conditioning equipment; it may also be any equipment such as elevators, power supply equipment, or residential equipment. The apps developed by the developer include, for example, energy management apps, fault prediction apps, and demand control apps related to the above-mentioned equipment.
[0021] When developers create an application and conduct tests such as reproduction tests using that application, traditionally, verification is performed using actual equipment in various environments and conditions. This presents problems such as the need for purchase costs, labor costs, and installation work for preparing the actual equipment, as well as the time required to accumulate and prepare time-series operating data. Furthermore, it has the problem that only operating data from the environment in which the actual equipment is installed can be obtained.
[0022] In this embodiment 1, the scenario server 20 provides the developer terminal 10 with one or more scenario information representing the status of equipment or the operating environment. The scenario information provided by the scenario server 20 is generated by the scenario server 20 by referencing the scenario database DB according to the type of application program specified by the user and the conditions required for scenario selection.
[0023] Furthermore, the scenario server 20 accepts the developer's selection of scenario information presented to the developer terminal 10, and reads the operating data of the equipment from the equipment cloud MC according to the scenario information selected by the developer. The scenario server 20 then sends the operating data read from the equipment cloud MC to the equipment emulator 30.
[0024] In this embodiment, the equipment emulator 30 is an independent piece of hardware (computer) that converts the operation data received from the scenario server 20 into operation data appropriate to the destination system. The scenario server 20 transmits the operation data converted by the equipment emulator 30 to a predetermined destination. Alternatively, the scenario server 20 may provide the operation data converted by the equipment emulator 30 to the developer (developer terminal 10). The developer verifies the equipment 40 based on the operation data provided by the scenario server 20.
[0025] In the configuration example shown in Figure 1, the scenario database DB is located outside the scenario server 20, but the scenario database DB may also be located inside the scenario server 20. Furthermore, in the configuration example shown in Figure 1, the scenario server 20 and the device emulator 30 are separate components, but the functionality of the device emulator 30 may also be integrated into the scenario server 20.
[0026] Figure 2 is a block diagram showing the internal configuration of the developer terminal 10. The developer terminal 10 is a general-purpose computer and includes a control unit 11, a storage unit 12, a communication unit 13, an operation unit 14, and a display unit 15, among others.
[0027] The control unit 11 includes a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), and the like. The ROM in the control unit 11 stores control programs and the like that control the operation of each hardware component of the developer terminal 10. The CPU in the control unit 11 reads and executes the control programs and the like stored in the ROM, and controls the operation of the hardware components, thereby making the entire device function as the developer terminal 10 in this disclosure. The RAM in the control unit 11 temporarily stores data used during the execution of various processes.
[0028] The control unit 11 may also include functions such as a clock for outputting date and time information, a timer for measuring the elapsed time from the time a measurement start instruction is given until a measurement end instruction is given, and a counter for counting numbers.
[0029] The memory unit 12 is equipped with an auxiliary storage device and stores various data and computer programs. The computer programs stored in the memory unit 12 include application programs (dedicated or general-purpose browsers) that access the scenario server 20, display information provided by the scenario server 20 on the display unit 15, and accept operations from developers.
[0030] The communication unit 13 is equipped with a communication module for wireless communication with external devices such as the scenario server 20. The communication module uses a communication module for wireless communication using known mobile communication standards such as 3G, 4G, and 5G, or wireless LAN methods such as WiFi (registered trademark). The communication unit 13 communicates with external devices such as the scenario server 20 via the first communication network NW1, transmits necessary data, and receives appropriate data transmitted by the external devices.
[0031] The operation unit 14 is equipped with operating devices such as a keyboard and mouse, and accepts various inputs and operations from the developer. The control unit 11 acquires information input through the operation unit 14 and performs appropriate control based on the various operation information provided by the operation unit 14.
[0032] The display unit 15 is equipped with a display device such as a liquid crystal monitor or an organic EL (Electro-Luminescence) monitor, and displays information that should be notified to the work manager, etc., in response to instructions from the control unit 11.
[0033] Figure 3 is a block diagram showing the internal configuration of the scenario server 20. The scenario server 20 is a dedicated or general-purpose server device and includes, for example, a control unit 21, a storage unit 22, a communication unit 23, an operation unit 24, and a display unit 25.
[0034] The control unit 21 includes a CPU, ROM, RAM, etc. The ROM in the control unit 21 stores control programs and the like that control the operation of each hardware component of the scenario server 20. The CPU in the control unit 21 reads and executes the control programs stored in the ROM and the computer programs described later stored in the memory unit 22, and by performing processes to control the operation of the hardware components, the entire device functions as the scenario server 20 (information processing device) of this disclosure. The RAM in the control unit 21 temporarily stores data used during the execution of various processes.
[0035] In this embodiment, the control unit 21 is configured to include a CPU, ROM, and RAM, but the configuration of the control unit 21 is not limited to the above. The control unit 21 may be one or more processing circuits, for example, including a GPU (Graphics Processing Unit), FPGA (Field Programmable Gate Array), DSP (Digital Signal Processor), quantum processor, volatile or non-volatile memory, etc. The control unit 21 may also include functions such as a clock that outputs date and time information, a timer that measures the elapsed time from the time a measurement start instruction is given to the time a measurement end instruction is given, and a counter that counts numbers.
[0036] The storage unit 22 is equipped with a storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). The storage unit 22 stores various computer programs executed by the control unit 21, and various data used when the computer programs are executed. The computer programs stored in the storage unit 22 include a scenario provision program PG that accepts the type of application and the conditions necessary for scenario selection, and provides candidate scenario information to the developer according to the accepted type and conditions. The scenario provision program PG accepts the developer's selection of the scenario information provided, and may cause the computer to execute a process to read the operation data of the equipment from the equipment cloud MC according to the selected scenario information, convert the read operation data into operation data according to the destination system, and send it to that system.
[0037] A computer program, including a scenario provision program PG, may be provided on a non-temporary recording medium RM on which the computer program is recorded in a readable format. The recording medium RM is a portable memory such as a CD-ROM, USB memory, SD card, microSD card, or CompactFlash®. The control unit 21 reads various computer programs from the recording medium RM using a reading device (not shown in the figure) and stores the read computer programs in the storage unit 22. The computer programs stored in the storage unit 22 may also be provided via communication. In this case, the control unit 21 acquires the computer programs via communication through the communication unit 23 and stores the acquired computer programs in the storage unit 22.
[0038] The scenario provider program PG may be a single computer program or may consist of multiple computer programs. Furthermore, the scenario provider program PG may run on a single computer or may run collaboratively on multiple computers (e.g., developer terminal 10 and scenario server 20). Additionally, the scenario provider program PG may partially utilize existing libraries.
[0039] The communication unit 23 is equipped with a communication module for wireless communication with external devices such as the developer terminal 10 and the device emulator 30. The communication module uses a communication module for wireless communication using known mobile communication standards such as 3G, 4G, and 5G, or wireless LAN methods such as WiFi (registered trademark). The communication unit 23 transmits necessary data and receives appropriate data transmitted by external devices through the first communication network NW1 and the second communication network NW2.
[0040] The operation unit 24 is equipped with operating devices such as a touch panel, keyboard, and switches, and accepts various inputs and operations from administrators, etc. The control unit 21 acquires information input through the operation unit 24 and performs appropriate control based on the various operation information provided by the operation unit 24.
[0041] The display unit 25 is equipped with a display device such as a liquid crystal monitor or an organic EL (Electro-Luminescence) monitor, and displays information that should be notified to administrators, etc., in response to instructions from the control unit 21.
[0042] The scenario server 20 may be a single computer, or it may be a computer system composed of multiple computers and peripheral devices. Furthermore, the scenario server 20 may be a virtualized virtual machine, or it may be a cloud.
[0043] Figure 4 is a conceptual diagram showing an example of the database configuration of the Equipment Cloud MC. The Equipment Cloud MC collects operational data from various equipment via the first communication network NW1 and registers it in the cloud database as it occurs. The Equipment Cloud MC is not limited to the above-mentioned equipment 40; it can collect operational data from various equipment. If the equipment does not have a means of communication, an edge controller can be installed on the equipment, and operational data can be acquired through the edge controller.
[0044] Figure 4 shows an example where the following are associated and stored in a cloud-based database: equipment ID, operation data item, current operation data value, model information, equipment configuration information, data update date and time, and data acquisition date and time. Here, the equipment ID is an identifier that identifies each piece of equipment. The operation data item represents the type of operation data. The current operation data value represents the latest value of the operation data acquired from each piece of equipment. The model information represents the type of equipment. The equipment configuration information is information that shows the configuration of the equipment. The data update date and time represents the date and time when the current operation data value in the database was updated. The data acquisition date and time represents the date and time when data was acquired from each piece of equipment.
[0045] Figure 5 is an explanatory diagram illustrating an example of storing operational data in the scenario database DB. In the scenario database DB, the operational data is stored with tag information attached. The example in Figure 5 shows an example where country / region information, seasonal information, property type information, and equipment failure information are attached as tag information. Here, country / region information indicates the country or region in which the equipment is installed. Seasonal information represents the seasonal information at the time the operational data was acquired. Weather information represents the weather information at the time the operational data was acquired. Property type information represents the type of property in which the equipment is installed. Equipment failure information represents information such as whether or not there is a failure in the equipment, the location of the failure, and the details of the failure. Such tag information is manually set by the administrator who manages the scenario data. The administrator of the scenario data simply needs to write the tag information for each operational data to the scenario database DB using their terminal device.
[0046] Alternatively, the scenario data management device (e.g., scenario server 20) may collect tag information for registered operation data via the first communication network NW1 when operation data is registered in the scenario database DB, and register it as corresponding tag information. For example, for country / region information, the system may search existing map information services based on information such as the address, latitude, and longitude of the property that is pre-registered in the equipment cloud MC, and register the obtained country / region information in the scenario database DB. The same applies to property type information. Furthermore, for weather information, the system may obtain weather information for the relevant region at the time of data acquisition or data update from an existing weather information distribution service and register the obtained weather information in the scenario database DB. Equipment failure information can be obtained from each piece of equipment and registered in the scenario database DB.
[0047] Figure 6 is a conceptual diagram showing an example of the configuration of the scenario database DB. The scenario database DB stores scenarios registered in advance by the administrator and tags selected according to the scenario. Scenarios describe scenarios that represent the status of equipment, scenarios that represent the operating environment of equipment, etc. Alternatively, scenarios describe scenarios for specific models of equipment, or scenarios for specific equipment configurations. Here, the status of equipment includes whether or not there is a malfunction in the equipment. The operating environment of equipment includes at least one of the country or region where the equipment is installed, the season in which the equipment is used, the weather in the country or region where the equipment is installed, and the type of property where the equipment is installed. Tags include tags common to each scenario (common items) and tags set individually for each scenario (unique items). Each tag is set appropriately by the administrator according to the content of the scenario.
[0048] Although not shown in Figure 6, the frequency of developer selection for each scenario can be counted and registered in the scenario database.
[0049] The operation of the information processing system 1 according to the embodiment will be described below. Figure 7 is a schematic diagram showing an example of a user interface screen displayed on the developer terminal 10. The user interface screen 110 illustrated in Figure 7 shows the screen displayed on the display unit 15 of the developer terminal 10 after accessing the scenario server 20 from the developer terminal 10 and performing predetermined procedures such as user authentication.
[0050] The user interface screen 110 includes an application type selection field 111, condition selection fields 112 and 113, a confirmation button 114, and a scenario display field 115. The application type selection field 111 accepts the selection of the application type being developed by the developer. In the example in Figure 7, a fault prediction application is selected. Not only fault prediction applications, but also energy management applications, demand control applications, etc., can be selected.
[0051] Condition selection fields 112 and 113 accept the conditions necessary for scenario selection. Condition selection field 112 is a selection field for selecting tags set as common items, and accepts information such as country / region information, seasonal information, and property type information. Condition selection field 113 is a selection field for selecting tags set as unique items, and accepts information such as the type of equipment failure.
[0052] When the OK button 114 is pressed on the user interface screen 110, the scenario server 20 searches the scenario database DB according to the type of application and scenario selection criteria selected by the developer, and displays the retrieved scenarios in the scenario display area 115. In the example in Figure 7, scenarios that match the criteria, recommended scenarios, and scenarios that are frequently used in the selected application are displayed.
[0053] A scenario that matches the criteria represents the scenario that most closely matches the set of tags (criteria) selected by the developer in the criteria selection fields 112 and 113. A recommended scenario represents a scenario that matches specific criteria (e.g., season, country / region, property type) from the tags (criteria) selected by the developer. A frequently used scenario represents a scenario that has been selected many times in the past.
[0054] In Figure 7, as an example of when a fault prediction application is selected, the screen accepts the equipment failure type condition in the unique items of the scenario selection conditions. However, the unique items of the scenario selection conditions may be changed depending on the selected application. For example, if a demand control application is selected, the demand control status and demand control target power may be displayed in the condition selection field 113 as mandatory selection conditions.
[0055] When a scenario is selected on the user interface screen 110 (when any of the selection buttons 115a to 115c are pressed), the developer terminal 10 notifies the scenario server 20 of the information of the scenario selected by the developer.
[0056] The scenario server 20 refers to the scenario database DB, which stores scenarios and tags in association, and reads the operating data of the equipment according to the scenario selected by the developer. As shown in Figure 5, the scenario database DB stores the operating data in association with tags, so the operating data corresponding to the scenario can be read from the scenario database DB.
[0057] The scenario server 20 reads the operation data from the scenario database DB and sends it to the equipment emulator 30. After converting the operation data to suit the destination system, the emulator 30 sends the converted operation data to the aforementioned system. Depending on the destination system, there may be specified formats for the operation data that can be used and time intervals (granularity) of the data. Therefore, the equipment emulator 30 converts the operation data and sends the converted operation data to the aforementioned system.
[0058] Figure 8 is a flowchart illustrating the procedure of the processing performed by the scenario server 20. The control unit 21 of the scenario server 20 displays a user interface screen 110, as shown in Figure 7, on the display unit 15 of the developer terminal 10 in response to a request from the developer terminal 10 (step S101).
[0059] The control unit 21 receives the application type selection and scenario selection conditions through the user interface screen 110 displayed on the display unit 15 of the developer terminal 10 (step S102). When the OK button 114 is pressed on the user interface screen 110, the selected application type and scenario information are notified from the developer terminal 10 to the scenario server 20.
[0060] The control unit 21 reads one or more scenario information from the scenario database DB according to the type of application selected by the developer and the scenario selection conditions, and displays it in the scenario display field 115 of the user interface screen 110 (step S103).
[0061] The control unit 21 accepts a selection of scenario information (step S104) and reads the operation data of the equipment from the scenario database DB according to the selected scenario information (step S105).
[0062] The control unit 21 reads the operation data from the scenario database DB and converts it into operation data corresponding to the destination system via the equipment emulator 30 (step S106), and then transmits the converted operation data to the system (step S107).
[0063] As described above, in this embodiment, scenario information is presented to the developer according to the type of application and the conditions required for scenario selection, and according to the scenario information selected by the developer, operating data of the equipment is read from the database and the operating data is transmitted after being converted according to the destination.
[0064] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims, not in the sense described above, and all modifications within the sense and scope equivalent to the claims are intended. [Explanation of Symbols]
[0065] 10 Developer terminal 20 Scenario Servers 21 Control Unit 22 Memory section 23 Communications Department 24 Control section 25 Display section 30 Device Emulators 40 Equipment PG Scenario Provision Program MC Equipment Cloud DB Scenario Database
Claims
1. The system accepts the type of application program related to the equipment, a scenario representing the state or operating environment of the equipment, or the conditions necessary for selecting a scenario for a specific model or configuration of the equipment. Depending on the type and conditions received, one or more scenario information representing the status or operating environment of the equipment is output. The system accepts selections regarding the outputted scenario information. Depending on the selected scenario information, the operating data of the equipment is read from the database. The read operating data is converted into operating data appropriate for the destination and transmitted to the destination. An information processing method in which processing is performed by a computer.
2. The aforementioned condition includes whether or not there is a malfunction in the equipment. The information processing method according to claim 1.
3. The aforementioned usage environment includes at least one of the country or region where the equipment is installed, the season in which the equipment is used, the weather in the country or region where the equipment is installed, and the type of property on which the equipment is installed. The information processing method according to claim 1.
4. The system outputs at least one of the following: scenario information that matches the accepted conditions, scenario information similar to the accepted conditions, scenario information extracted according to past selection history, and scenario information that is frequently used by the application program. The information processing method according to claim 1, wherein the processing is performed by the computer.
5. The operating data and condition information of the aforementioned equipment are associated and stored in the database as scenario information. Refer to the aforementioned database and retrieve the scenario information to be output. The information processing method according to claim 1, wherein the processing is performed by the computer.
6. The aforementioned database stores operational data, regional information, weather information, malfunction information, and date / time information of equipment installed in various regions, linking them together. The information processing method according to claim 1.
7. The system accepts the type of application program related to the equipment, a scenario representing the state or operating environment of the equipment, or the conditions necessary for selecting a scenario for a specific model or configuration of the equipment. Depending on the type and conditions received, one or more scenario information representing the status or operating environment of the equipment is output. The system accepts selections regarding the outputted scenario information. Depending on the selected scenario information, the operating data of the equipment is read from the database. The read operating data is converted into operating data appropriate for the destination and transmitted to the destination. A computer program that causes a computer to perform a process.
8. It comprises at least one processing unit, The aforementioned processing unit, The system accepts the type of application program related to the equipment, a scenario representing the state or operating environment of the equipment, or the conditions necessary for selecting a scenario for a specific model or configuration of the equipment. Depending on the type and conditions received, one or more scenario information representing the status or operating environment of the equipment is output. The system accepts selections regarding the outputted scenario information. Depending on the selected scenario information, the operating data of the equipment is read from the database. The read operating data is converted into operating data appropriate for the destination and transmitted to the destination. Information processing device.
Citation Information
Patent Citations
Simulation device
JP2023036203A