JP7263886B2 - Driving device management method and driving device management program - Google Patents

Description

The present disclosure relates to a driving device management method and a driving device management program that are executed by a driving device management system that manages the state of a driving device.

Various techniques have been proposed for managing various types of information related to ophthalmology or spectacles. For example, in the ordering method for ophthalmic medical products described in Patent Document 1, the serial code attached to the ophthalmic medical product is used to manage sales and inventory of the ophthalmic medical product.

JP 2009-211549 A

Drives manufactured by manufacturers are often installed in various locations around the world. Therefore, a skilled person (for example, a developer of the driving device) who is familiar with the management of the driving device (for example, maintenance when malfunction occurs, grasping whether the operation is being performed normally, etc.) It is not always possible to visit the established bases. When it is necessary to manage a driving device, conventionally, for example, a worker from a manufacturer's agency visits the location where the driving device is installed and communicates with the expert by phone or e-mail. I was in charge of the drive system. In some cases, the user using the driving device himself communicated with the expert. However, in the conventional method, the driving device may not be properly managed due to factors such as the skill level of the worker or user, the operating environment of the driving device, and the difference in language used by the worker or the like and the expert.

A typical object of the present disclosure is a driving device management method and driving device management capable of appropriately managing the state of a driving device that performs at least one of ophthalmic or ophthalmic examination, treatment, measurement, and processing. to provide the program.

A drive device management method provided by an exemplary embodiment of the present disclosure includes a drive device for performing at least one of ophthalmic or spectacle examination, treatment, measurement, and processing, a terminal device, the drive device and the terminal. A driving device management method that is executed in a driving device management system that manages the state of the driving device, the driving device management method including an information processing device located at a base different from the device, wherein the terminal device drives the driving device. a device information acquisition step of acquiring device information including information from the driving device; and a state in which the terminal device adds additional information input by a user to the device information, thereby indicating at least the state of the driving device. A state information acquisition step of acquiring information, and a state information transmission step of transmitting the state information to the information processing device by the terminal device.

A driving device management program provided by a typical embodiment of the present disclosure includes a driving device that performs at least one of examination, treatment, measurement, and processing related to ophthalmology or spectacles, a terminal device, the driving device and the terminal. A driving device management program that is executed in a driving device management system that manages the state of the driving device, the driving device management program comprising an information processing device that is located at a location different from the driving device, wherein the driving device management program is used to manage the driving device. a device information acquisition step in which the terminal device acquires device information including drive information of the drive device from the drive device; a state information acquiring step of acquiring state information indicating at least a state of the driving device by adding information to the device information; and a state information transmitting step of transmitting the state information from the terminal device to the information processing device. , are performed by the drive management system.

According to the driving device management method and the driving device management program of the present disclosure, the state of the driving device that performs at least one of ophthalmic or spectacle examination, treatment, measurement, and processing is appropriately managed.

1 is a block diagram showing a schematic configuration of a driving device management system 1; FIG. FIG. 5 is a sequence diagram showing an example of the flow of drive device management processing;

<Overview>
A driving device management system illustrated in the present disclosure includes a driving device, a terminal device, and an information processing device. The driving device executes at least one of ophthalmic or spectacle examination, treatment, measurement, and processing (hereinafter referred to as “examination, processing, etc.”). The information processing device is arranged at a site different from the driving device and the terminal device. The drive management system executes a device information acquisition step, a status information acquisition step, and a status information transmission step. In the device information obtaining step, the terminal device obtains device information including driving information of the driving device from the driving device. In the state information acquisition step, the terminal device acquires state information indicating at least the state of the driving device by adding additional information input by the user to the device information. In the state information transmission step, the driving device transmits the state information to the information processing device.

According to the technology according to the present disclosure, device information including driving information of a driving device is transmitted from the driving device to the information processing device via the terminal device. Accordingly, the information processing apparatus appropriately manages the state of the driving device regardless of the skill level of workers at the site where the driving device is installed, the operating environment of the driving device, the language used, and the like. Furthermore, by adding additional information input by the user to the device information, state information indicating at least the state of the driving device is acquired and transmitted to the information processing device. The additional information can include information that is difficult for the driving device itself to obtain as device information (for example, information about the driving device that can be obtained only from the outside of the driving device, etc.). Further, when the information amount of the device information is small, it is possible to add information that is desirable to be added to the device information as additional information to the device information. Therefore, the information processing apparatus can grasp the state of the driving apparatus more appropriately than when only the apparatus information is transmitted to the information processing apparatus. Therefore, according to the technology according to the present disclosure, management of the driving device is performed more appropriately.

The device information includes, for example, the time when the power of the driving device was turned on and off, the time when the driving device was driven, the length of time when an operation such as inspection or processing was performed by the driving device, the inspection or processing by the driving device It may include at least one of the number of times an operation such as machining has been performed, information on equipment connected to the driving device, and identification information for identifying the driving device (for example, a serial number for identifying the device). In this case, the device information suitably includes the state of the drive, including the history of the operation of the drive.

The device information may include at least one of information indicating the type of inspection or processing performed by the driving device, and parameters used when controlling the operation of inspection or processing by the driving device. For example, when the driving device is an eyeglass lens processing device, the parameter information may be information on the shape of the frame in which the processed eyeglass lens is fitted (that is, information on the shape of the eyeglass lens to be processed). In this case, when an operation failure such as inspection or processing by the drive device occurs, the operation of the drive device can be properly grasped based on at least one of the type of inspection or processing and the parameters.

The device information may also include information about an object to be inspected or processed by the driving device. For example, when the driving device is an ophthalmic examination device or an ophthalmic treatment device, the information about the target of the executed test or treatment is information indicating whether the target of the test or treatment was the left eye or the right eye of the subject. may be In this case, when a malfunction occurs due to the driving device, the details of the operation of the driving device that caused the malfunction can be properly grasped depending on whether the examination or treatment for the left eye or the right eye was performed. be. Further, when the drive device is an eyeglass lens processing device, the information about the processing object that has been executed may be information on the type of lens that has been processed. In this case, when a malfunction occurs due to the driving device, the details of the operation of the driving device that caused the malfunction can be properly grasped according to the type of the processed lens.

The additional information includes, for example, the date and time when the malfunction of the drive device occurred, the country/region where the drive device is used, information on the environment in which the drive device is used (e.g. temperature, etc.), and the operation of the terminal device. It may include at least one of information of a user (for example, a worker of a manufacturer's agency, etc.), user's contact information, and user's comment (for example, contents of malfunction of the driving device, etc.). For example, even if the driving device does not have a clock function, the state of the driving device can be grasped more appropriately by adding information such as date and time as additional information to the device information. Also, even if the driving device does not have a thermometer and a hygrometer, by adding at least one of temperature and humidity information as additional information to the device information, the state of the driving device can be grasped more appropriately. In addition, by adding information such as comments as a result of observing the driving device from outside the driving device to the device information as additional information, the state of the driving device can be grasped more appropriately.

The driving device may execute a device information identifier display step of causing the display unit to display an identifier indicating the device information. In the device information obtaining step, the terminal device may obtain the device information from the driving device by reading, with an identifier reader, an identifier of the device information displayed on the display unit by the driving device. In this case, even if data is not transmitted and received between the driving device and the terminal device, accurate device information can be acquired by the terminal device.

However, it is also possible to change the specific method for the terminal device to acquire the device information. For example, when data transmission/reception is performed between the driving device and the terminal device (for example, transmission/reception by NFC, Wi-Fi, Bluetooth (registered trademark), wired communication, etc.), data indicating device information is It may be sent from the device to the terminal device. In this case, the driving device may transmit the device information to the terminal device when receiving an instruction to transmit the device information from the terminal device. Further, the drive device may transmit the device information to the terminal device at a preset timing (for example, at regular time intervals), or may transmit the device information to the terminal device at the timing when a failure occurs.

The information processing device may execute a setting information transmitting step of transmitting to the terminal device setting information indicating setting details of the driving device, which is determined based on the state information transmitted from the terminal device. In other words, the terminal device may receive, from the information processing device, setting information indicating setting details of the driving device, which are determined based on the state information. In this case, even if a skilled person (for example, a developer of the drive device) who is familiar with the management (for example, maintenance, etc.) of the drive device is not at the base where the drive device is installed, the state information sent from the terminal device , the desired settings of the driving device are appropriately transmitted to the terminal device.

Note that the setting information may be generated according to an instruction input by the user who grasps the state information. Alternatively, a control unit such as an information processing device may automatically generate setting information based on state information.

The drive management system may further execute a setting information identifier display step and a setting information acquisition step. In the setting information identifier display step, the terminal device causes the display unit to display the identifier of the setting information. In the setting information acquisition step, the driving device acquires the setting information by reading the identifier of the setting information displayed on the display unit by the terminal device using the identifier reader. In this case, unlike the case where the user sets the driving device while confirming the setting information, the setting contents determined based on the state information are more accurately reflected in the driving device. Also, even if data is not transmitted or received between the drive and the terminal device, the setting of the drive can be performed accurately.

However, it is also possible to change the specific method for the driving device to acquire the setting information. For example, when data is transmitted and received between a driving device and a terminal device, instead of identifier data, data indicating setting information may be transmitted from the information processing device to the driving device via the terminal device. good. It is also possible for the user to manually set the driving device while checking the setting information displayed on the display section of the terminal device.

The drive may comprise a camera for inspection, treatment, measurement and/or processing. In the setting information acquisition step, the driving device may read the identifier by using the camera also as an identifier reader. In this case, the setting information can be properly acquired by the drive device without separately mounting an identifier reader on the drive device.

The drive management system may perform a configuration information storage step. In the setting information storing step, at least one of the terminal device and the drive device stores the setting information transmitted from the information processing device in the storage device. In this case, the settings of the drive can be changed back to the settings of the drive appropriately determined based on the status information at any time. In other words, the backup of the setting of the driving device is appropriately performed. Note that the setting information may be stored as an identifier, or may be stored as data indicating the setting information.

The above technique can also be expressed as follows. A driving device for performing at least one of ophthalmic or spectacle examination, treatment, measurement, and processing, comprising a camera used for at least one of the examination, treatment, measurement, and processing, and a control unit, The control unit uses the camera also as an identifier reader to read an identifier of setting information indicating setting details of operating conditions of the driving device, and sets the operating conditions based on the read setting information. A driving device characterized by:

In the state information acquisition step, the terminal device acquires at least one of audio data of operation sound and image data of the driving device while the driving device is performing at least one of inspection, treatment, measurement, and processing, as a state information. may be included in the information. In this case, even if an expert who is familiar with the maintenance of the driving device is not at the location where the driving device is installed, the state of the driving device can be properly grasped by at least one of the operation sound and the image.

For example, when the driving device is an eyeglass lens processing device, the operation sound may be a processing sound while the lens is being processed by the eyeglass lens processing device. In this case, the state of machining can be grasped appropriately with consideration given to machining noise. Also, the audio data of the operation sound may be input to the terminal device through the microphone of the terminal device. Further, when data is transmitted and received between the drive device and the terminal device, the voice data may be acquired by a microphone provided in the drive device and then transmitted from the drive device to the terminal device. The image data may be moving image data (for example, moving image data of a driving device in operation) or still image data (for example, still image data of a failure location).

<Embodiment>
One typical embodiment of the present disclosure will be described below with reference to the drawings. First, referring to FIG. 1, the system configuration of a driving device management system 1 in this embodiment will be schematically described. A driving device management system 1 of this embodiment includes a terminal device 10 , a driving device 20 , an information processing device 30 , and a personal computer (hereinafter referred to as “PC”) 40 . The terminal device 10 is used at a site (site A in the present embodiment) where the driving device 20 is installed. The information processing device 30 and the PC 40 are arranged at a site different from the terminal device 10 and the driving device 20 . In this embodiment, the site where the information processing device 30 is located (site B in this embodiment) and the site where the PC 40 is located (site C in this embodiment) are also different. However, the information processing device 30 and the PC 40 may be arranged at the same location.

The terminal device 10 is used by a user at a site where the driving device 20 is installed. The user of the terminal device 10 may be, for example, an agent worker entrusted with part of the work of the manufacturer of the driving device 20, or a user using the driving device 20 himself. The terminal device 10 of this embodiment is a mobile terminal such as a smart phone or a tablet terminal. However, devices other than mobile terminals (for example, PCs, etc.) may be used as the terminal device 10 .

The terminal device 10 includes a control unit 11 that performs various control processes, and a communication I/F 14 . The control unit 11 includes a CPU 12 that is a controller for control, and a storage device 13 that can store programs, data, and the like. The storage device 13 stores a driving device management program for executing part of a driving device management process (see FIG. 2), which will be described later. The communication I/F 14 connects the terminal device 10 with an external device (eg, information processing device 30) via a network 5 (eg, Internet, etc.).

The terminal device 10 includes an operation unit 16 , a monitor (display unit) 17 , a camera (photographing unit) 18 , and a microphone (voice input unit) 19 . The operation unit 16 is operated by the user to input various instructions to the terminal device 10 . At least one of a touch panel, a keyboard, a mouse, and the like can be used for the operation unit 16, for example. The monitor 17 is an example of a display capable of displaying various images. The camera 18 takes various images. Although the details will be described later, the camera 18 of this embodiment is also used as an identifier reader for reading identifiers. The microphone 19 inputs various sounds and outputs signals corresponding to the sounds to the control unit 11 . At least one of the operation unit 16, the monitor 17, the camera 18, and the microphone 19 may be an external device that is not built into the terminal device 10. FIG.

Various devices for performing at least one of examination, treatment, measurement, processing, etc. in the field of ophthalmology or spectacles can be used for the drive device 20 . In this embodiment, a case where an eyeglass lens processing apparatus for processing eyeglass lenses is used as the driving device 20 will be described as an example. However, the driving device 20 is, for example, an OCT device, a fundus camera, a scanning laser ophthalmoscope (SLO), an eye axial length measuring device, a corneal shape measuring device, an intraocular pressure measuring device, an eye refractive power measuring device, an ophthalmic laser therapy It may be a device, a tracer for measuring the frame shape of spectacles, or the like.

The drive device 20 includes a control unit 21 that performs various control processes, and a drive section 25 . The control unit 21 includes a CPU 22 which is a controller for control, and a storage device 23 capable of storing programs, data, and the like. The storage device 23 stores a driving device management program for executing part of a driving device management process (see FIG. 2), which will be described later. The drive unit 25 has various configurations necessary for the drive device 20 to perform at least one of examination, treatment, measurement, processing, and the like. As an example, the drive unit 25 of the present embodiment includes various motors, solenoids, sensors, etc. for driving the drive device 20 as an eyeglass lens processing device. Further, the drive unit 25 is provided with a camera 28 that is used by the drive device 20 to perform at least one of inspection, treatment, measurement, processing, and the like. As an example, the camera 28 provided in the drive unit 25 of this embodiment is used for photographing the lens shape and hole position of the lens.

The driving device 20 includes an operating section 26 and a monitor 27 . The operation unit 26 is operated by the user to input various instructions to the driving device 20 . At least one of various buttons, a touch panel, a keyboard, a mouse, and the like can be used for the operation unit 26, for example. The monitor 27 is an example of a display capable of displaying various images.

For example, a server or the like can be used as the information processing device 30 . When the information processing device 30 is a server, the information processing device 30 may be, for example, a server of a manufacturer that provides cloud services (a so-called cloud server), or a server other than a cloud server (for example, a server that manufactures the driving device 20). It may be a server of a manufacturer that does the same). Further, the PC 40 described later may function as the information processing device 30, or a device other than the server and the PC 40 (for example, a smartphone, a tablet terminal, etc.) capable of processing various types of information may function as the information processing device 30. may In these cases, it is possible to omit the server.

The information processing device 30 includes a control unit 31 that performs various control processes, and a communication I/F 34 . The control unit 31 includes a CPU 32 that is a controller for control, and a storage device 33 that can store programs, data, and the like. The storage device 33 stores a driving device management program for executing part of a driving device management process (see FIG. 2), which will be described later. The communication I/F 34 connects the information processing device 30 with external devices (for example, the terminal device 10 and the PC 5) via the network 5. FIG.

The PC 40 is used by experts familiar with the management of the driving device 20 (for example, developers of the manufacturer of the driving device 20, etc.). PC40 is provided with control unit 41 which performs various control processing, and communication I/F44. The control unit 41 includes a CPU 42 that is a controller for control, and a storage device 43 that can store programs, data, and the like. Communication I/F 44 connects PC 40 to an external device (for example, information processing device 30 ) via network 5 . The PC 40 is also connected to an operation unit 46 and a monitor 47 .

An example of drive device management processing executed by the drive device management system 1 will be described with reference to FIG. The driving device management process exemplified in the present embodiment is executed by the CPU 12 of the terminal device 10, the CPU 22 of the driving device 20, and the information processing device 30 according to the driving device management program stored in each of the storage devices 13, 23, 33, and 43. It is executed by the CPU 32 and the CPU 42 of the PC 40 .

First, the CPU 22 of the drive device 20 drives the drive unit 25 to perform the operation of the drive device 20 (at least one of examination, treatment, measurement, processing, etc. in the field of ophthalmology or spectacles). (S21). Here, in the present embodiment, when the user operates the operation unit 26 of the driving device 20, an operation that is considered to cause a malfunction (for example, in the present embodiment, an operation when the lens is not processed as planned) is performed. ) is executed by the driving device 20 .

The CPU 12 of the terminal device 10 performs at least one of recording operation sound and shooting a moving image while the driving device 20 is performing the operation (S21). As a result, at least one of the audio data of the operation sound and the image data is acquired (S11). In other words, in the present embodiment, at least one of the operation sound (in this embodiment, the processing sound of the lens) during operation of the driving device 20 that is considered to be malfunctioning and the data of the moving image is transmitted to the terminal device 10. Obtained by Note that the image data may be still image data. In this case, the still image is not limited to the still image during operation of the driving device 20 .

Next, the CPU 12 of the terminal device 10 acquires device information including drive information of the drive device 20 from the drive device 20 (S12). The device information includes, for example, the time when the driving device 20 was turned on and off, the time when the driving device 20 operated, the length of time when the driving device 20 operated such as inspection or processing, At least one of the number of times the driving device 20 has performed an operation such as inspection or processing, information on devices connected to the driving device 20, identification information for identifying the driving device 20, and the like is included. The device information also includes the type of inspection or processing executed by the driving device 20 (specific type of processing in this embodiment). The device information also includes parameters (in this embodiment, for example, information on the shape of the spectacle frame into which the processed lens is fitted, etc.) when controlling operations such as inspection or processing by the driving device 20. In addition, the device information includes information about an object to be inspected or processed by the driving device 20 (in this embodiment, for example, information about the type of lens processed). By using the above information as the device information, the state of the driving device 20 can be properly grasped.

Further, in the present embodiment, the CPU 22 of the drive device 20 generates an identifier (for example, a QR code (registered trademark) or a barcode) indicating device information in accordance with an instruction input by the user, and the generated identifier is displayed on the monitor 27 (S22). The CPU 12 of the terminal device 10 acquires the device information from the drive device 20 by reading the identifier of the device information displayed on the monitor 27 by the drive device 20 with the identifier reader (the camera 18 in this embodiment) (S12). . Therefore, the state of the driving device 20 can be properly grasped regardless of the skill level of the user at the site where the driving device 20 is installed, the operating environment of the driving device 20, the language used, and the like. Communication failure or the like between users does not occur. There is no need to transmit and receive data between the drive device 20 and the terminal device 10 either.

Next, the CPU 12 of the terminal device 10 accepts input of additional information by the user (S13). The additional information is information that is transmitted to the information processing device 30 together with the device information in order to manage the drive device 20 more appropriately. The additional information includes, for example, the date and time when the drive device 20 malfunctioned, the country/region where the drive device 20 is used, and the environment (eg temperature and humidity) where the drive device 20 is used. , information about the user who operates the terminal device 10, contact information of the user who operates the terminal device 10, and user's comments (for example, contents of malfunction of the drive device 20, etc.). That is, the additional information of the present embodiment includes information that is difficult for the driving device 20 itself to acquire as device information. Note that in the present embodiment, additional information is input to the terminal device 10 by operating the operation unit 17 of the terminal device 10 . However, it is also possible to change the input method of the additional information. For example, additional information may be input via the microphone 19 .

Next, the CPU 12 of the terminal device 10 acquires state information indicating at least the state of the driving device 20 (S14). Specifically, the CPU 12 acquires the state information by adding the additional information input by the user in S13 to the device information acquired from the driving device 20 in S12. Furthermore, the CPU 12 of the present embodiment includes at least one data of the operation sound and the image of the driving device 20 acquired in S11 in the state information. As a result, the state of the driving device 20 can be properly grasped with consideration given to the operation sound or the image.

Next, the CPU 12 of the terminal device 10 transmits the state information acquired in S14 to the information processing device 30 (S15). The CPU 32 of the information processing device 30 acquires the state information transmitted from the terminal device 10 and transmits the acquired state information to the PC 40 (S31). If the PC 40 also serves as the information processing device 30, the process of transmitting the state information from the information processing device 30 to the PC 40 (S31) may be omitted.

Next, the CPU 42 of the PC 40 generates setting information that indicates setting details of the drive device 20 (S41). A specific method for generating the setting information can be selected as appropriate. As an example, the CPU 42 of this embodiment causes the monitor 47 to display the status information received from the information processing device 30 . Further, the CPU 42 executes at least one of reproduction of the operation sound of the driving device 20 and display of an image based on the audio/image data included in the state information. A user of the PC 40 (in this embodiment, an expert who is familiar with the management of the driving device 20) grasps the state of the driving device 20 based on the contents displayed on the monitor 47, the reproduced operation sound, and the like. The user of the PC 40 operates the operation unit 46 to input setting information for instructing appropriate setting contents of the driving device 20 into the PC 40 based on the grasped state of the driving device 20 . The CPU 42 generates setting information according to the input result from the operation unit 46 . Note that the CPU 42 may automatically generate the setting information based on the state information.

The CPU 42 of the PC 40 transmits the setting information generated in S41 to the information processing device 30 (S42). The CPU 32 of the information processing device 30 acquires the setting information transmitted from the PC 40 and transmits the acquired setting information to the terminal device 10 (S32).

When the setting information is received from the information processing device 30, the CPU 12 of the terminal device 10 stores the received setting information in the storage device 13 (S15). In addition, the process of S15 may be performed after the process of S16 mentioned later.

Next, the CPU 22 of the driving device 20 acquires the setting information transmitted from the information processing device 30 to the terminal device 10 (S23). The CPU 22 sets operating conditions according to the acquired setting information (S24). As a result, the operating conditions of the driving device 20 are appropriately set to the contents determined based on the state information.

Here, a method for acquiring setting information by the driving device 20 will be described. In this embodiment, when the setting information is acquired from the information processing device 30, the CPU 12 of the terminal device 10 causes the monitor 17 to display an identifier indicating the acquired setting information (S16). The CPU 22 of the driving device 20 acquires the setting information from the terminal device 10 by reading the identifier of the setting information displayed on the monitor 17 by the terminal device 10 (S23). Therefore, unlike the case where the user manually sets the driving device 20 while checking the setting information, the setting contents determined based on the state information are more easily and accurately reflected in the driving device 20 . There is no need to transmit and receive data between the drive device 20 and the terminal device 10 either. Note that the identifier data indicating the setting information may be generated in advance by the PC 40 or the information processing device 30 and then transmitted to the terminal device 10 . Alternatively, the CPU 12 of the terminal device 10 may generate identifier data indicating the setting information based on the setting information received from the information processing device 30 .

In addition, the CPU 22 of the driving device 20 also uses the camera 28 used for executing at least one of inspection, treatment, measurement, processing, etc., as an identifier reader, and the image displayed on the monitor 17 of the terminal device 10 Read identifier. Therefore, even if an identifier reader is not mounted on the drive 20 separately from the camera 28, the configuration information is properly acquired by the drive 20. FIG.

Next, the CPU 22 of the driving device 20 causes the storage device 23 to store the setting information transmitted from the information processing device 30 (S25). In addition, the process of S25 may be performed before the process of S24. Further, when the setting information is stored in the storage device, the setting information may be stored in only one of the storage device 23 of the drive device 20 and the storage device 13 of the terminal device 10 . Also, the setting information may be stored as an identifier, or may be stored as data indicating the setting information. By storing the setting information, the setting of the driving device 20 is appropriately backed up.

The technology disclosed in the above embodiment is merely an example. Therefore, it is also possible to modify the techniques exemplified in the above embodiments. For example, it is also possible to implement only a part of the techniques illustrated in the above embodiments. Specifically, the processing (S11, S14) of transmitting the data of the operation sound/image of the driving device 20 to the information processing device 30 may be omitted. In addition, the processing (S21, S22, S11 to S15, S31) of acquiring and transmitting state information is omitted, and the processing ( S16, S23) only may be executed. Further, the processing (S41, S42, S32, S15, S16, S23 to S25) for setting the operating conditions of the driving device 20 is omitted, and the processing for acquiring and transmitting the state information (S21, S22, S11 to S15) is omitted. , S31) may be performed.

The process of acquiring the device information in S12 of FIG. 2 is an example of the device information acquisition step. The process of acquiring the state information in S14 is an example of the state information acquisition step. The process of transmitting the state information to the information processing device 30 in S15 is an example of the state information transmitting step. The process of displaying the device information identifier on the monitor 27 in S22 is an example of the device information identifier display step. The process of transmitting the setting information to the terminal device 10 in S32 is an example of the setting information transmission step. The process of displaying the identifier of the setting information on the monitor 17 in S16 is an example of the step of displaying the setting information identifier. The process of acquiring the setting information in S23 is an example of the step of acquiring setting information. The process of storing the setting information in the storage device in S15 and S25 is an example of the setting information storing step.

1 drive device management system 10 terminal device 12 CPU
13 storage device 17 monitor 18 camera 19 microphone 20 drive device 22 CPU
23 storage device 27 monitor 28 camera 30 information processing device 32 CPU

Claims (5)

a driving device for executing at least one of ophthalmic or spectacle examination, treatment, measurement, and processing; a terminal device; and an information processing device arranged at a site different from the driving device and the terminal device, A driving device management method executed in a driving device management system for managing the state of a driving device, comprising:
a device information acquisition step in which the terminal device acquires device information including drive information of the drive device from the drive device;
a state information acquiring step in which the terminal device acquires state information indicating at least a state of the driving device by adding additional information input by a user to the device information;
a state information transmission step in which the terminal device transmits the state information to the information processing device;
A driving device management method comprising: The drive device management method according to claim 1,
further comprising a device information identifier display step in which the driving device displays an identifier indicating the device information on a display unit;
In the device information acquisition step, the terminal device acquires the device information from the drive device by reading, with an identifier reader, an identifier of the device information displayed on the display unit by the drive device. drive management method. The driving device management method according to claim 1 or 2,
The information processing device further comprises a setting information transmission step of transmitting, to the terminal device, setting information indicating setting details of the driving device, which is determined based on the state information transmitted from the terminal device. A drive management method characterized by: The drive device management method according to any one of claims 1 to 3,
In the state information obtaining step, the terminal device acquires at least audio data of an operation sound while the driving device is performing at least one of inspection, treatment, measurement, and processing, and image data of the driving device. A driving device management method , characterized in that one is included in the state information . a driving device for executing at least one of ophthalmic or spectacle examination, treatment, measurement, and processing; a terminal device; and an information processing device arranged at a site different from the driving device and the terminal device, A drive management program executed in a drive management system for managing the state of a drive, comprising:
By executing the drive management program by the controller of the drive management system,
a device information acquisition step in which the terminal device acquires device information including drive information of the drive device from the drive device;
a state information acquiring step in which the terminal device acquires state information indicating at least a state of the driving device by adding additional information input by a user to the device information;
a state information transmission step in which the terminal device transmits the state information to the information processing device;
is executed by the drive management system .

Images