Device management apparatus, device management method, and device management program

Abstract

To prevent oversight of timing of recovery of a commodity based on a machine history.SOLUTION: A machine history data generation part generates machine history data indicating a machine history corresponding to transition of the apparatus including a manufacturing date of the apparatus, a movement date of a physical place, and a repair date. The display control unit displays an inquiry screen on which a list of equipment history data corresponding to the designated equipment among the generated equipment history data is displayed. The determination unit refers to a service life master table in which the service life of each device is stored, and determines whether the number of days from the date of manufacture to the current date exceeds the service life. The display control part adds information indicating that the service life is exceeded to the machine history data of the equipment whose number of days from the manufacturing date to the present date is discriminated as the number of days exceeding the service life among the machine history data of the equipment list-displayed on the inquiry screen, and displays it.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a device management apparatus, a device management method, and a device management program. [Background technology]

[0002] In the information processing device disclosed in Patent Document 1 (JP 2023-158922 A), an estimation unit estimates fluctuations in value that occur when a user possesses an item based on the user's buying and selling history for the item. A generation unit generates content based on the estimated fluctuations in value. Then, a provision unit provides the generated content to the user. This makes it possible to provide useful information to the user.

[0003] Paragraphs 0039 and 0040 of Patent Document 1 state that the estimation unit generates a model trained using trading characteristics extracted from the trading machine history as explanatory variables and a score indicating value fluctuations as a target variable, and that the estimation unit inputs the trading characteristics into the model and estimates value fluctuations based on the score output from the model.

[0004] Furthermore, the sales characteristics include the price at which the item was purchased, the price at which it was sold, the difference between the prices at the time of purchase and the time of sale, and the period of ownership between purchase and sale. The model describes that explanatory variables include information about the item (manufacturing date, model, performance, repair history, etc.) or information about the item's characteristics, such as deterioration over time. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2023-158922 Summary of the Invention [Problem to be solved by the invention]

[0006] Here, the manufacturer manages the timing of inspection or replacement of manufactured products based on the "history" of each manufactured product, such as the manufacturing date, shipping date, repair history, and installation location, for each serial number.

[0007] However, the timing of inspections or replacements of products is managed by the person in charge by visually checking the displayed "product history." Therefore, if an oversight occurs, there is a problem of delays in recovery or non-implementation of recovery.

[0008] The present invention has been made in consideration of the above-mentioned problems, and aims to provide an equipment management device, an equipment management method, and an equipment management program that can prevent overlooking the timing of product recovery based on machine history. [Means for solving the problem]

[0009] In order to solve the above-mentioned problems and achieve the objectives, the equipment management device of the present invention comprises: an equipment history data generation unit that generates equipment history data indicating the equipment history corresponding to changes in the equipment, including the date of manufacture, the date of transfer to a physical location, and the date of repair; a display control unit that displays an inquiry screen that lists the equipment history data corresponding to a specified equipment from the generated equipment history data; and a discrimination unit that refers to a useful life master table in which the useful life of each equipment is stored and determines whether the number of days between the manufacture date and the current date exceeds the useful life, and the display control unit adds information indicating that the useful life has been exceeded to the equipment history data of equipment that has been determined to be a number of days that exceeds the useful life from the equipment history data of the equipment listed on the inquiry screen.

[0010] In addition, in order to solve the above-mentioned problems and achieve the objective, the equipment management method of the present invention includes: an equipment history data generation step in which an equipment history data generation unit generates equipment history data indicating equipment history corresponding to changes in the equipment, including the manufacturing date of the equipment, the date of moving to a physical location, and the date of repair; a display control step in which a display control unit displays an inquiry screen that lists equipment history data corresponding to a specified equipment from the equipment history data of the equipment generated in the equipment history data generation step; and a determination step in which a discrimination unit refers to a useful life master table in which the useful life of each equipment is stored, and determines whether the number of days between the manufacturing date and the current date exceeds the useful life.In the display control step, the display control unit displays the equipment history data of equipment that has been determined to have a number of days between the manufacturing date and the current date that exceeds the useful life, by adding information indicating that the useful life has been exceeded, to the equipment history data of the equipment listed on the inquiry screen.

[0011] In addition, in order to solve the above-mentioned problems and achieve the objective, the equipment management program of the present invention causes a computer to function as: an equipment history data generation unit that generates equipment history data indicating the equipment history corresponding to changes in the equipment, including the date of manufacture of the equipment, the date of movement to a physical location, and the date of repair; a display control unit that displays an inquiry screen that lists the equipment history data corresponding to a specified equipment from the generated equipment history data; and a discrimination unit that refers to a useful life master table in which the useful life of each equipment is stored and determines whether the number of days between the manufacture date and the current date exceeds the useful life; and when the computer is caused to function as the display control unit, the computer is caused to function to add information indicating that the useful life has been exceeded to the equipment history data of equipment that has been determined to be a number of days in which the number of days between the manufacture date and the current date exceeds the useful life from the equipment history data of the equipment listed on the inquiry screen, and display the data. [Effects of the Invention]

[0012] The present invention can prevent overlooking the timing of product recovery based on product history. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram illustrating a hardware configuration of a device management apparatus according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a movement section master table. [Figure 3] FIG. 3 is a diagram showing an example of a moving date update destination master table. [Figure 4] FIG. 4 is a diagram illustrating an example of the management classification master table. [Figure 5] FIG. 5 is a diagram illustrating an example of a sales division master table. [Figure 6] FIG. 6 is a diagram illustrating an example of the useful life master table. [Figure 7] FIG. 7 is a diagram illustrating an example of movement data. [Figure 8] FIG. 8 is a diagram showing an example of the vehicle history data that is automatically generated based on the movement data. [Figure 9] FIG. 9 is a diagram illustrating an example of sales data. [Figure 10] FIG. 10 is a diagram showing an example of machine history data that is automatically generated based on sales data. [Figure 11] FIG. 11 is a diagram illustrating an example of repair data. [Figure 12] FIG. 12 is a diagram showing an example of machine history data automatically generated based on repair data. [Figure 13] FIG. 13 is a diagram showing a medical history inquiry screen in which the medical history of the medical device for which an inquiry is desired is displayed in a list. [Figure 14] FIG. 14 shows the machine history inquiry screen in a state where the desired number of years for inspection alerts has been entered. [Figure 15] FIG. 15 is a diagram showing how a medical device is detected based on the machine history data, where the number of days between the last repair date and the current date exceeds the number of years input as an inspection alert. [Figure 16]FIG. 16 is an enlarged view of a key portion of the machine history data, showing how, based on the machine history data, a medical device is detected whose number of days between the last repair date and the current date exceeds the number of years entered as an inspection alert. DETAILED DESCRIPTION OF THE INVENTION

[0014] As an example, an embodiment of the present invention applied to a device management device in the medical device manufacturing industry will be described in detail below with reference to the accompanying drawings. Note that the present invention is not limited to the following embodiment and may be applied to terminal devices in industries other than the medical device manufacturing industry. In this case, the same effects as those described below can be obtained.

[0015] (overview) Medical device manufacturers assign serial numbers to their products and manage their product history by recording the manufacturing date, shipping date, repair history, installation location, etc. Some products have a useful life of 5 or 7 years, and some medical devices require specific maintenance. Based on the product history, personnel in charge determine the timing of product inspections or replacements.

[0016] However, because product history data was manually entered into the table management software, the registration process was time-consuming and burdensome for the person in charge. Therefore, the equipment management device of the embodiment automatically generates product history data based on the manufacturing data, shipping data, sales data, repair data, etc. entered during daily operations, thereby reducing the burden on the person in charge.

[0017] Furthermore, if the timing for recovery based on the device history is overlooked, there is a risk that inspections and other procedures will be delayed. For this reason, the device management device of the embodiment compares the number of days from the product's manufacturing date to the current date with the product's useful life, and if the number of days from the product's manufacturing date to the current date exceeds the product's useful life, an alert is displayed indicating the need for inspections and other procedures. This prevents overlooking the timing for recovery based on the device history, making it possible to recover products at the appropriate time.

[0018] (Hardware configuration) As shown in FIG. 1, the device management device 1 of the embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5. The output device 7 corresponds to a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to achieve a pointing device function. The communication interface unit 4 is connected to a network, for example, a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0019] A storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be used as the storage unit 2. The storage unit 2 stores a device management program that can prevent overlooking the timing of product recovery based on the device history.

[0020] In addition, this memory unit 2 is provided with a transfer category master table 11, a transfer date update destination master table 12, a management category master table 13, a sales category master table 14, a useful life master table 15, a transfer data memory unit 16, a machine history table 17, a sales data memory unit 18, and a repair data memory unit 19, each of which is a memory area.

[0021] As shown in Figure 2, the transfer category master table 11 indicates the physical location of the product, and the transfer category name for transfer category "1" is "production entry," which indicates that the produced product has been moved to a warehouse. The transfer category name for transfer category "2" is "inter-warehouse transfer," which indicates that the product has been moved between warehouses. The transfer category name for transfer category "3" is "disposal (adjusted delivery)," which indicates that the product has been shipped to a disposal location.

[0022] 3, the transfer date update destination master table 12 stores the name of the transfer date for each transfer mode set in the transfer classification master table 11 when it is assigned to the machine history data, which will be described later. That is, the transfer date update destination master table 12 is set so that the transfer date of "1: Production entry" is assigned to the machine history data as the "manufacturing date," "2: Inter-warehouse transfer" is assigned to the machine history data as the "relocation date," and "3: Disposal (adjusted delivery)" is assigned to the machine history data as the "disposal date."

[0023] In the management category master table 13, various management categories for machine history data are set as shown in Fig. 4. That is, if the machine history data is machine history data corresponding to the "manufacturing" of a product, a management category of "1: manufacturing" is assigned based on this management category master table 13. Also, if the machine history data is machine history data corresponding to the "sales" of a product, a management category of "2: sales" is assigned based on this management category master table 13. If the machine history data is machine history data corresponding to the "return" of a product, a management category of "3: return" is assigned based on this management category master table 13.

[0024] Furthermore, if the machine history data corresponds to the "relocation" of the product, a management category of "4: Relocation" is assigned based on this management category master table 13. Furthermore, if the machine history data corresponds to the "repair" of the product, a management category of "5: Repair" is assigned based on this management category master table 13. Furthermore, if the machine history data corresponds to the "disposal" of the product, a management category of "6: Disposal" is assigned based on this management category master table 13. Furthermore, if the machine history data corresponds to the "loan" of the product, a management category of "7: Loan" is assigned based on this management category master table 13.

[0025] As shown in Figure 5, the sales category master table 14 sets the sales category for the sales of the product. That is, when the product is sold to a customer, the sales data is assigned a transfer category of "1: Sales" based on this sales category master table. Also, when the product is repaired and sales for the repair are obtained, the sales data for the repair is assigned a transfer category of "2: Repair Sales" based on the sales category master table. Also, when a product that has been sold is returned, the sales data for the return is assigned a transfer category of "3: Sales Returns" based on the sales category master table.

[0026] In the service life master table 15, the service life of each manufactured medical device is set as shown in Fig. 6. Fig. 6 shows an example in which a service life of "3 years" is set for "100: Medical Device A" and a service life of "5 years" is set for "200: Medical Device B."

[0027] (Functional configuration of device management device) Next, the control unit 3 executes the device management program stored in the storage unit 2, thereby functioning as a data generation unit 21, a display control unit 22, a determination unit 23, and a storage control unit 24, as shown in Fig. 1. The data generation unit 21 also functions as a device history data generation unit 25.

[0028] The data generation unit 21 generates product movement data, sales data, and correction data in response to input operations by the person in charge. Furthermore, by functioning as a machine history data generation unit 25, the data generation unit 21 generates machine history data indicating the machine history corresponding to the transition of the equipment (product), including the manufacturing date of the equipment (product), the date of transfer to a physical location, and the date of repair, based on the product movement data, sales data, and correction data.

[0029] The display control unit 22 displays an inquiry screen (see FIG. 13) that displays a list of the device history data corresponding to the specified device from among the generated device history data.

[0030] The determination unit 23 refers to the useful life master table 15 (see Figure 6) in which the useful life of each device is stored, and determines whether the number of days between the manufacturing date and the current date exceeds the useful life.

[0031] The display control unit 22 displays the machine history data of the equipment listed on the inquiry screen, adding information indicating that the useful life has been exceeded to the machine history data of the equipment for which the number of days between the manufacturing date and the current date has been determined to be a number of days that exceeds the useful life (warranty period expiration information indicated by a check mark in Figure 13).

[0032] Furthermore, the display control unit 22 displays an inspection alert input field on the inquiry screen for inputting the desired number of days that have passed since the repair date (for example, an input field in which the value "2 years" is inputted as shown in FIG. 14).

[0033] The determination unit 23 determines whether the number of days between the repair date and the current date exceeds the desired number of elapsed days input in the inspection alert input field.

[0034] The display control unit 22 displays the equipment history data of the equipment listed on the inquiry screen, with information indicating that the number of days between the repair date and the current date has exceeded the desired number of days entered in the inspection alert input field, along with information indicating that the number of days has exceeded the desired number of days entered in the inspection alert input field (check mark indicating that the maintenance period has expired, as shown in Figure 14).

[0035] In addition, when generating machine history data corresponding to sales data (see Figure 9) that includes a unique serial number along with at least the sales date, product information, and sales amount, the machine history data generation unit 25 generates machine history data that includes the serial number assigned to the sales data (see the serial number of the machine history data in Figure 8 and the serial number of the sales data in Figure 9).

[0036] (Automatic generation of aircraft history data) Next, the operation of automatically generating historical data in the device history management device of the embodiment having such a configuration will be described. The control unit 3 of the device history management device of the embodiment executes the device management program stored in the memory unit 2, thereby functioning as a data generation unit 21, a determination unit 23, a memory control unit 24, and a device history data generation unit 25, and performs the operation of automatically generating historical data.

[0037] In this example, the data generating unit 21, the determining unit 23, the storage control unit 24, and the machine history data generating unit 25 are described as being realized by software, but some or all of these may be realized by hardware. In either case, the same effects as those described below can be obtained.

[0038] (Automatic generation of aircraft history data based on movement data) First, assume that equipment is manufactured and stored in a specified warehouse. The person in charge inputs the transfer number, line number, transfer category, transfer date, receiving warehouse, product name, serial number, quantity, etc. As a result, the data generation unit 21 generates transfer data including the transfer number, line number, transfer category, transfer date, receiving warehouse, product name, serial number, quantity, etc., in accordance with the person in charge's input operation, as shown in FIG. 7. The storage control unit 24 stores the generated transfer data in the transfer data storage unit 16.

[0039] The transfer number and row number are assigned numbers automatically assigned by the control unit 3. The transfer category is input by the person in charge with reference to the transfer category master table 11 shown in Figure 2. In this example, the transfer category of "1: Production and warehousing" is input.

[0040] As the transfer date, the person in charge inputs the date when the equipment was moved to the warehouse, for example, "April 1, 2023." As the receiving warehouse, the person in charge inputs the location or warehouse to which the equipment was moved, for example, "head office factory." In this example, the product name of the moved product is "100: Medical Device A." Furthermore, the serial number is automatically assigned by the control unit 3, or a desired number is input by the person in charge. As the quantity, the person in charge inputs the number of devices moved.

[0041] The device history data generation unit 25 references the movement data generated in this way from the movement data storage unit 16 and automatically generates device history data regarding the movement of equipment, including the product name, serial number, revision date, management classification, manufacturing date, installation location, original slip number, and original line number, as shown in Fig. 8. The storage control unit 24 stores the generated device history data in the device history table 17.

[0042] The product name and serial number are the same as those in the movement data shown in Figure 7. By using the same serial number, the movement data and the vehicle history data are associated with each other.

[0043] The revision date uses the transfer date (April 1, 2023) of the movement data shown in Fig. 7. For the management classification, the history data generation unit 25 refers to the management classification master table 13 shown in Fig. 4, selects a management classification corresponding to the preset movement classification of the movement data, and assigns it to the history data.

[0044] That is, for example, it is preset in the equipment management program that when the transfer category of the transfer data is "1: Production entry," "1: Production" in the management category master table 13 is set as the management category of the machine history data, and when the transfer category of the transfer data is "2: Transfer between warehouses," "4: Relocation" in the management category master table 13 is set as the management category of the machine history data. Also, when the transfer category of the transfer data is "3: Disposal (adjusted delivery)," "6: Disposal" in the management category master table 13 is set as the management category of the machine history data.

[0045] For this reason, the machine history data generating unit 25 acquires a management classification that is set in advance according to the movement classification of the movement data from the management classification master table 13, and adds it to the machine history data.

[0046] For the manufacturing date, use the transfer date (April 1, 2023) of the transfer data shown in Figure 7. For the installation location, use the receiving warehouse (head office factory) of the transfer data shown in Figure 7. For the original slip number and original line number, use the transfer number (ID001) and line number (1) of the transfer data shown in Figure 7.

[0047] (Automatic generation of machine history data based on sales data) Next, suppose that a device is sold. The person in charge performs an input operation to input the sales information for the device, such as the sales number, line number, sales category, sales date, customer name, end user name, shipping warehouse, product name, serial number, quantity, and sales amount. As a result, the data generation unit 21 generates sales data including the sales number, line number, sales category, sales date, customer name, end user name, shipping warehouse, product name, serial number, quantity, and sales amount in accordance with the person in charge's input operation, as shown in FIG. 9. The storage control unit 24 stores the generated sales data in the sales data storage unit 18.

[0048] The sales number and row number are assigned numbers automatically assigned by the control unit 3. The sales category is entered by the person in charge with reference to the sales category master table 14 shown in Figure 5. In this example, the sales category "1: Sales" is entered.

[0049] As the sales date, the person in charge will enter the date the device was sold, such as "April 15, 2023." The person in charge will also enter the customer name, such as "XX dealer," and the end user name, such as "XX clinic."

[0050] In this example, the shipping warehouse is the "head office factory," and the location or warehouse where the sold equipment was shipped is entered by the person in charge. The product name of the sold equipment is "100: Medical Equipment A" in this example. The serial number is also entered by the person in charge as "1234," the same as the sales data. By using the same serial number, the sales data, movement data, and equipment history data are correlated. The quantity is entered by the person in charge as the number of equipment sold. The sales amount is also entered by the person in charge as the sales amount of the equipment sold, for example, "30 million yen."

[0051] The machine history data generation unit 25 references the sales data generated in this way from the sales data storage unit 18 and automatically generates machine history data related to the sales of the equipment, including the product name, serial number, revision date, management classification, manufacturing date, sales date, installation location, original slip number, and original line number, as shown in Fig. 10. The storage control unit 24 stores the generated machine history data in the machine history table 17.

[0052] The product name and serial number use the product name and serial number from the sales data shown in Figure 9. The revision date uses the sales date (April 15, 2023) from the sales data shown in Figure 9. For the management category, the machine history data generation unit 25 refers to the sales category master table 14 shown in Figure 5, selects a management category corresponding to the sales category of the sales data that has been set in advance, and assigns it to the machine history data.

[0053] That is, for example, it is preset in the equipment management program that when the sales category of the sales data is "1: Sales," "2: Sales" in the management category master table 13 is set as the management category of the equipment history data, and when the sales category of the sales data is "2: Repair Sales," "5: Repair" in the management category master table 13 is set as the management category of the equipment history data. Also, when the sales category of the sales data is "3: Sales Returns," it is preset in the equipment management program that "3: Returns" in the management category master table 13 is set as the management category of the equipment history data.

[0054] For this reason, the machine history data generating unit 25 acquires, from the management classification master table 13, a management classification that is set in advance according to the sales classification of the sales data, and adds it to the machine history data.

[0055] For the manufacturing date and sales date, the sales date (April 15, 2023) of the sales data shown in Figure 9 is used. For the installation location, the end user name (XX Clinic) of the sales data shown in Figure 9 is used. For the original slip number and original line number, the sales number (UR001) and line number (1) of the sales data shown in Figure 9 are used.

[0056] (Automatic generation of machine history data based on repair data) Next, suppose that a device is repaired. The person in charge performs input operations such as inputting the sales number, line number, sales category, sales date, customer name, end user name, shipping warehouse, product name, serial number, quantity, and repair cost to enter sales information for the repair. As a result, the data generation unit 21 generates repair data including the sales number, line number, sales category, sales date, customer name, end user name, shipping warehouse, product name, serial number, quantity, and repair cost in accordance with the person in charge's input operations, as shown in FIG. 11 . The storage control unit 24 stores the generated repair data in the repair data storage unit 19.

[0057] The sales number and row number are assigned numbers automatically assigned by the control unit 3. The sales category is entered by the person in charge with reference to the sales category master table 14 shown in Figure 5. In this example, the sales category "2: Repair sales" is entered.

[0058] As the sales date, the person in charge will enter the date the equipment was repaired, such as "May 1, 2023." The person in charge will also enter the customer name, such as "XX dealer," and the end user name, such as "XX clinic."

[0059] In this example, the shipping warehouse is the "head office factory," and the location or warehouse where the repaired equipment was shipped is entered by the person in charge. The product name of the repaired equipment is "100: Medical Equipment A" in this example. The serial number is entered by the person in charge as "1234," the same as the movement data and sales data. The quantity is entered by the person in charge as the number of equipment repaired. The repair cost is also entered by the person in charge as the sales amount for the repaired equipment, for example, "100,000 yen."

[0060] The machine history data generation unit 25 references the repair data generated in this way from the repair data storage unit 19 and automatically generates machine history data related to the sales of equipment repairs, including the product name, serial number, revision date, management classification, manufacturing date, sales date, repair date, installation location, original slip number, and original line number, as shown in Fig. 12. The storage control unit 24 stores the generated machine history data in the machine history table 17.

[0061] The product name and serial number are those of the repair data shown in Fig. 11. By using the same serial number, the machine history data of the movement data, the machine history data of the sales data, and the machine history data of the correction data are associated with each other.

[0062] The revision date uses the sales date (May 1, 2023) of the repair data shown in Fig. 11. For the management category, the machine history data generation unit 25 refers to the management category master table 13 shown in Fig. 4, selects a management category corresponding to the sales category of the repair data that has been set in advance, and assigns it to the machine history data.

[0063] That is, for example, if the sales category of the repair data is "2: Repair Sales," it is preset in the equipment management program that "5: Repair" in the management category master table 13 is set as the management category of the machine history data. Therefore, the machine history data generation unit 25 obtains the management category that is preset according to the sales category of the repair data from the management category master table 13 and adds it to the machine history data.

[0064] For the manufacturing date and sales date, based on the serial number "1234", the manufacturing date of the movement data and the sales date of the sales data shown in Figure 10 are referenced, and the same manufacturing date (April 1, 2023) and the same sales date (April 15, 2023) are used. For the repair date, the sales date of the repair data shown in Figure 11 (May 1, 2024) is used.

[0065] The installation location uses the end user name (XX Clinic) of the repair data shown in Figure 11. The original slip number and original line number use the sales number (SHU001) and line number (1) of the repair data shown in Figure 11.

[0066] (Alert display behavior for devices that have exceeded their useful life when checking device history) Next, when the desired equipment history data is queried from among the equipment history data stored in the equipment history table 17 in this manner, the equipment management device 1 of the embodiment is configured to display a predetermined alert for medical equipment that has exceeded its useful life.

[0067] Specifically, when the person in charge specifies that the device history inquiry screen be displayed, the display control unit 22 displays the device history inquiry screen shown in Fig. 13 via the output device 7. The person in charge inputs the name of the device (product name) that the person in charge wishes to inquire about into this device history inquiry screen. Fig. 13 shows an example in which "Medical Device A" with product code "QA260A" is input as the name of the device (product name) that the person in charge wishes to inquire about.

[0068] When the name of the device (product name) desired to be inquired is input, the display control unit 22 refers to the device history table 17 and acquires the device history data of "medical device A" specified by the person in charge. Then, the display control unit 22 displays the acquired device history data of "medical device A" in a list on the device history inquiry screen in descending order of manufacturing date, as shown in Fig. 13.

[0069] At this time, the display control unit 22 refers to the service life master table 15 shown in Fig. 6 and detects the service life of the medical device A being queried. In this example, the display control unit 22 detects a service life of "3 years" as the service life of the medical device A. Then, the display control unit 22 displays the detected service life by attaching it to each record of the machine history data displayed in a list.

[0070] Here, the determination unit 23 detects the period from the manufacturing date of each medical device A to the current date obtained from a timer or the like (not shown) for each listed medical device A. Then, the determination unit 23 determines whether or not the period from the manufacturing date to the current date for each medical device A exceeds the service life of "3 years".

[0071] The display control unit 22 displays, among the records of the machine history data displayed in a list, records of medical device A that have been determined to have a period from the manufacturing date to the current date exceeding the useful life of "3 years" by adding information indicating that the useful life has been exceeded. Records with a check mark added in the warranty expiration date column shown in Fig. 13 are records to which information indicating that the useful life has been exceeded has been added.

[0072] This makes it possible to prevent overlooking the timing of product recovery based on the product history, and makes it possible to carry out recovery such as repairs and inspections of medical device A at the appropriate time.

[0073] (Alert display behavior for equipment that is past its inspection period when checking the equipment history) Next, when the desired equipment history data is queried from the equipment history data stored in the equipment history table 17, the equipment management device 1 of the embodiment is configured to display a predetermined alert for medical equipment whose desired inspection period has expired.

[0074] Specifically, when the person in charge specifies display of the medical history inquiry screen, the display control unit 22 displays the medical history inquiry screen shown in Fig. 14 via the output device 7. The person in charge inputs a desired inspection period, such as "two years," in the inspection alert input field on this medical history inquiry screen. As a result, the display control unit 22 acquires the medical history data of each medical device (medical device A and medical device B) stored in the medical history table 17 and displays the data in a list on the medical history inquiry screen.

[0075] At this time, the display control unit 22 refers to the service life master table 15 shown in Fig. 6 and detects the service life of the medical device A and medical device B being queried. In this example, the display control unit 22 detects a service life of "3 years" as the service life of medical device A and a service life of "5 years" as the service life of medical device B. Then, the display control unit 22 displays the detected service life by attaching it to each record of the machine history data to be displayed in a list.

[0076] Here, as shown in Figures 15 and 16, the discrimination unit 23 determines whether the period from the repair date to the current date for a medical device for which a repair date has been entered exceeds the number of years, "2 years," entered in the inspection alert input field.

[0077] 15 is a diagram showing the overall machine history data of each medical device, and FIG. 16 is a diagram showing the main parts of the machine history data used when determining whether the inspection period has expired. In the example shown in FIGS. 15 and 16, the machine history of medical device A with serial number "100" is that it was manufactured on April 1, 2019, loaned to "XX Orthopedic Clinic" on April 15, 2019, and repaired on August 1, 2020. If the current date is September 23, 2024, the period from the last repair date to the current date is "four years or more," and therefore the determination unit 23 determines that the inspection alert has exceeded the "two years" specified.

[0078] 15 and 16, the machine history of medical device A with serial number "1234" is that it was manufactured on April 1, 2023, sold to "XX Clinic" on April 15, 2023, repaired on March 1, 2024, and moved from "XX Clinic" to "Municipal Hospital" on August 30, 2024. If the current date is September 23, 2024, the period from the last repair date to the current date is "approximately six months," and therefore the determination unit 23 determines that the period does not exceed "two years" specified as an inspection alert.

[0079] 15 and 16, the history of medical device B with serial number "101" is that it was manufactured on March 10, 2022, sold to "XX Lease" on March 20, 2022, and moved to "XX Clinic" on April 20, 2022. In this example, repairs have not been performed on medical device B with serial number "101" as of now. Therefore, the determination unit 23 does not determine whether the period specified for the inspection alert has expired.

[0080] When the determination unit 23 determines that the period specified for the inspection alert has expired in this way, the display control unit 22 adds inspection alert information indicating that the period specified for the inspection alert has expired to the machine history data records in which the repair date has been input, among the machine history data records of medical device A with serial number "100" that have been determined to have expired beyond the "two years" specified for the inspection alert, and displays them, as shown in Fig. 14. Records with a check mark added in the inspection alert display column shown in Fig. 14 are records to which information indicating that the period specified for the inspection alert has expired has been added.

[0081] This makes it possible to prevent overlooking the timing of product recovery based on the product history, and makes it possible to carry out recovery such as repairs and inspections of medical device A at the appropriate time.

[0082] In this example, if the period specified for the inspection alert has expired, inspection alert information is added to the machine history data record in which the repair date has been entered. However, inspection alert information may also be added and displayed for all machine history data records for medical device A with serial number "100." This means that for medical devices with repair dates that exceed the period specified for the inspection alert, inspection alert information is added and displayed overall for all machine history data, making it possible to better prevent overlooking the timing of recovery.

[0083] (Effects of the embodiment) As is clear from the above explanation, the device management device 1 of the embodiment automatically creates a device history master based on various data generated by inputting daily operations such as manufacturing, shipping, sales, and repairs. It then references the device history master to detect the number of days from the product's manufacturing date to the current date, and compares this with the product's useful life to display an alert indicating the need for inspection or other recovery. This prevents overlooking the timing of product recovery based on the device history, and allows product recovery to be performed at the appropriate time.

[0084] Furthermore, since the machine history data is generated using the same serial number as the serial number in the product sales data, it is possible to confirm the sales amount and gross profit, etc. based on the machine history data, making it possible to, for example, consider estimates or propose repairs for specific end users.

[0085] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This invention can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of goals "8" and "9" of the SDGs.

[0086] Furthermore, this invention can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs goals 12, 13, and 15.

[0087] Furthermore, the present invention can contribute to strengthening control and governance, thereby contributing to the achievement of Goal 16 of the SDGs.

[0088] [Other embodiments] The present invention can be implemented in various different forms other than the above-described embodiments within the scope of the technical concept described in the claims.

[0089] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually, or all or part of the processes described as being performed manually may be performed automatically using a known method or the like.

[0090] Furthermore, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in the specification or drawings may be changed as desired unless otherwise specified.

[0091] Furthermore, the components of the device management device 1 shown in the figure are conceptual functional elements and do not necessarily have to have the physical configuration shown in the figure. For example, all or any part of the processing functions of the device management device 1, particularly the processing functions performed by the control unit 3, may be realized by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or may be realized by hardware using wired logic.

[0092] The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in the embodiments, and is mechanically read by the device management device 1 as needed. That is, a computer program is recorded in the storage unit 2, such as a ROM or HDD, for working with an OS (Operating System) to give instructions to the control unit 3 (CPU) and perform various processes. The computer program is loaded into RAM, expanded, and executed by the control unit 3 as appropriate.

[0093] In addition, the equipment management program of this equipment management device 1 may be stored in another server device connected to the equipment management device 1 via any network, and all or part of it may be downloaded and executed as needed.

[0094] Furthermore, the device management program for executing the processes described in the embodiments may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product.

[0095] Here, the "recording medium" can be any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical Disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0096] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code.

[0097] It should be noted that a "program" is not necessarily limited to a single structure, but includes a structure that is distributed as multiple modules or libraries, and a structure that achieves its function by working together with other programs, such as an OS.

[0098] Furthermore, the specific configuration for reading the recording medium in the device management device 1 of the embodiment, the reading procedure, and the installation procedure after reading can be realized using well-known configurations or procedures.

[0099] The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, web page files, etc. used for various processes or to provide websites.

[0100] The device management device 1 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as an information processing device connected to any peripheral device. The information processing device may be implemented with software (including programs or data) that realizes the processes described in the embodiments.

[0101] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the drawings, and all or part of them can be functionally or physically distributed or integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be selectively implemented by combining them in any way. [Industrial Applicability]

[0102] The present invention can be applied to any industry that performs product recovery based on the product history, and is suitable for application to product recovery in the medical device manufacturing industry, for example. [Explanation of symbols]

[0103] 1 Equipment management device 2 Storage section 3. Control Unit 4. Communication interface section 5 Input / output interface section 6 Input Devices 7 Output Devices 11 Transfer Classification Master Table 12 Transfer date update destination master table 13 Management Classification Master Table 14 Sales Category Master Table 15 Useful Life Master Table 16 Mobile data storage unit 17. Aircraft History Table 18 Sales data storage section 19 Repair data storage unit 21 Data Generation Unit 22 Display control unit 23 Discrimination part 24 Memory control unit 25. Aircraft history data generation unit

Claims

1. a device history data generation unit that generates device history data indicating a device history corresponding to a transition of the device, including a manufacturing date of the device, a date of physical location transfer, and a date of repair; a display control unit that displays an inquiry screen that lists the device history data corresponding to a specified device from among the generated device history data; a determination unit that refers to a useful life master table in which the useful life of each device is stored, and determines whether the number of days from the manufacturing date to the current date exceeds the useful life, the display control unit adds information indicating that the useful life has been exceeded to the machine history data of the devices among the machine history data of the devices displayed in a list on the inquiry screen, the machine history data of the devices being determined to have a number of days between the manufacturing date and the current date that exceeds the useful life, and displays the machine history data; A device management device comprising:

2. the display control unit displays an inspection alert input field on the inquiry screen for inputting a desired number of days elapsed since the repair date; The determination unit determines whether the number of days between the repair date and the current date exceeds the desired number of elapsed days input in the inspection alert input field, the display control unit, when it is determined that the number of days between the repair date and the current date exceeds the desired number of elapsed days input in the inspection alert input field among the machine history data of the devices displayed in a list on the inquiry screen, adds information indicating that the number of elapsed days has exceeded the desired number of elapsed days input in the inspection alert input field, and displays the machine history data; 2. The device management device according to claim 1, wherein:

3. the machine history data generation unit generates the machine history data including the serial number attached to the sales data when generating the machine history data corresponding to the sales data including at least a sales date, product information, and sales amount as well as a unique serial number; 3. The device management device according to claim 1, wherein:

4. a machine history data generating step in which a machine history data generating unit generates machine history data indicating a machine history corresponding to a transition of the device, including a manufacturing date of the device, a date of moving the device to a physical location, and a date of repair; a display control step in which a display control unit displays an inquiry screen that lists the machine history data corresponding to a specified device from among the machine history data of the devices generated in the machine history data generation step; a determination step in which a determination unit refers to a useful life master table in which the useful life of each device is stored, and determines whether or not the number of days from the manufacturing date to the current date exceeds the useful life; In the display control step, the display control unit displays, among the machine history data of the devices listed on the inquiry screen, the machine history data of a device for which it has been determined that the number of days between the manufacturing date and the current date exceeds the useful life, information indicating that the useful life has been exceeded, with the data being added; A device management method comprising:

5. Computer, a device history data generation unit that generates device history data indicating a device history corresponding to a transition of the device, including a manufacturing date of the device, a date of physical location transfer, and a date of repair; a display control unit that displays an inquiry screen that lists the device history data corresponding to a specified device from among the generated device history data; a determining unit that refers to a useful life master table in which the useful life of each device is stored and determines whether the number of days between the manufacturing date and the current date exceeds the useful life; When the computer is made to function as the display control unit, the computer is made to function so that, among the machine history data of the devices displayed in a list on the inquiry screen, the machine history data of a device for which it has been determined that the number of days between the manufacturing date and the current date exceeds the useful life is displayed with information indicating that the useful life has been exceeded added thereto; An equipment management program that features:

Images