Market system and ordering promotion method

Abstract

This market system for operating an electronic commerce site on which a customer can order components that make up production equipment comprises: a storage unit that collects and stores, for each component, operation information including the cumulative use time or the cumulative number of uses of the component; a prediction unit that predicts a replacement timing for each component on the basis of the replacement cycle of the component and the operation information; and a notification unit that, prior to a predicted replacement timing, notifies the customer of guidance for ordering the component associated with said timing through the electronic commerce site.

Description

Market system and order promotion method

[0001] This specification discloses a market system and a method for facilitating orders.

[0002] Conventionally, there have been proposed methods for estimating the replacement timing of parts used in production facilities, etc. For example, Patent Literature 1 describes a method for acquiring operation information of the production facilities, diagnosing the condition of the parts of the production facilities based on the operation information, and estimating the replacement timing from the condition of the parts.

[0003] International Publication No. 2022 / 149368

[0004] There are also known market systems that operate e-commerce sites where customers can purchase components such as devices and machinery that make up production facilities. In such systems, if replacement or maintenance of components becomes necessary to ensure stable operation of the production facilities installed by the customer, it is desirable for the customer to place an order through the e-commerce site. However, some customers may find it difficult to properly manage the timing of replacement or maintenance. For this reason, it is necessary to appropriately notify customers of the necessary information in order to reduce the management burden on the customer.

[0005] The main purpose of the present disclosure is to appropriately notify customers of the guidance necessary to ensure stable operation of production facilities, and to encourage them to place orders on e-commerce sites.

[0006] The present disclosure has adopted the following means to achieve the above-mentioned main object.

[0007] The market system of the present disclosure is a market system that operates an e-commerce site where customers can order components that make up production equipment, and comprises: a memory unit that collects and stores operation information for each component, including the cumulative usage time or cumulative number of uses of the component; a prediction unit that predicts the replacement time for each component based on the component replacement cycle and the operation information; and a notification unit that notifies customers, before the predicted replacement time arrives, to order the component related to the predicted replacement time on the e-commerce site.

[0008] The market system disclosed herein predicts the replacement time for each component based on the component replacement cycle and operation information, including the component's cumulative usage time or cumulative usage count. Furthermore, before the predicted replacement time arrives, the system notifies customers of the need to order the component on an e-commerce site. This reduces the customer's management burden and allows appropriate notification to customers when component replacement is necessary, encouraging them to place an order on the e-commerce site.

[0009] 1 is a configuration diagram showing an outline of the configuration of the market system 10. An explanatory diagram showing an outline of the functions and processing of the market system 10. An explanatory diagram showing an example of information stored in the operation DB 33e. A flowchart showing an example of a period setting process. An explanatory diagram showing an example of a correction coefficient map. An explanatory diagram showing an example of information stored in the period DB 33f. A flowchart showing an example of a timing prediction process. A flowchart showing an example of a notification process. A configuration diagram showing an outline of the configuration of a market system 10B of a modified example. An explanatory diagram showing an outline of the functions and processing of the market system 10B of a modified example. A flowchart showing an example of a derivation model related process. A flowchart showing an example of a period derivation process.

[0010] An embodiment of the present disclosure will be described with reference to the drawings. FIG. 1 is a configuration diagram showing an outline of the configuration of a market system 10. FIG. 2 is an explanatory diagram showing an outline of the functions and processing of the market system 10. The market system 10 includes a management server 20 that manages the entire system, and a data server 30 that stores a database (DB) in which various information is collected (accumulated). The management server 20 and the data server 30 are connected via a network 12. The management server 20 is also connected to a vendor terminal 50 and a customer terminal 60 via the network 12. Although FIG. 1 shows one vendor terminal 50 and one customer terminal 60, in reality, multiple vendor terminals 50 and one customer terminal 60 are connected.

[0011] The market system 10 supports the purchase of components such as various devices and equipment, as well as production facilities configured with the components, and also supports the maintenance of the components. Examples of production facilities include a work system WS used for various tasks in various industries, such as manufacturing and transportation. As shown in FIG. 2 , the work system WS is configured to perform a predetermined task using a robot 100 equipped with a vertically articulated robot arm. Examples of the predetermined task include picking workpieces such as mechanical parts and electronic parts. The task may include welding, deburring, painting, or other tasks performed in collaboration with a worker. The work system WS in FIG. 2 also includes an end effector 102 and a camera 103 attached to the tip link of the robot arm, a conveyor 104 for transporting trays or substrates on which workpieces are placed, and a feeder 105 for supplying workpieces.

[0012] The components that make up the work system WS, such as the robot 100, end effector 102, camera 103, conveyor 104, and feeder 105, are also referred to as modules. In this embodiment, each module of the work system WS is configured as an IoT (Internet of Things) module equipped with various sensors and wireless communication functions. Each module transmits information acquired by the various sensors to the data server 30 via the network 12 using the wireless communication function. Each module also uses replaceable consumables. Examples of consumables include tubes, cables, belts, chains, filters, bearings, gaskets, and packing. Replaceable claw parts used by the end effector 102 to grip a workpiece are also consumables.

[0013] In this embodiment, maintenance of the modules, which are components, involves checking the operation of each module, checking for abnormal noise, rattles, and continuity, applying lubricant, retightening bolts, removing foreign matter, and cleaning. Replacement involves replacing each module, which is a durable item that can be used for a relatively long period of time, with a new one, and replacing consumables used in each module with new ones. That is, in this embodiment, maintenance is performed on the modules, but not on the consumables. Replacement, on the other hand, is performed on both the modules and the consumables.

[0014] The management server 20 includes a control unit 21, a storage unit 23, and a communication unit 25. The control unit 21 includes a CPU, ROM, RAM, etc. The control unit 21 exchanges information with the data server 30, the vendor terminal 50, the customer terminal 60, etc. The control unit 21 also manages Marketplace MP, an e-commerce site where customers can select and purchase various modules online. Customers can select various modules from Marketplace MP and request quotations or purchases, or request maintenance of the various modules. The work system WS1 in FIG. 2 was purchased by customer A from Marketplace MP and delivered to a factory (FIG. 2(1)).

[0015] The storage unit 23 is configured with an HDD, SSD, etc., and stores various application programs, various data, etc. The communication unit 25 is connected to the network 12, etc., and communicates with the data server 30, the vendor terminal 50, the customer terminal 60, etc. Various instructions, etc., are input by the administrator to the management server 20 via an input unit 27 such as a keyboard or mouse. The management server 20 also displays various information on a display unit 29 such as a display.

[0016] The data server 30 includes a control unit 31 having a CPU, ROM, RAM, etc., a storage unit 33 configured with an HDD, SSD, etc., and a communication unit 35 connected to the network 12, etc., for communicating with the management server 20 and each module of each operation system WS. The storage unit 33 stores a module DB 33a, a case DB 33b, a vendor DB 33c, a customer DB 33d, an operation DB 33e, and a cycle DB 33f. Note that although the data server 30 is a separate device from the management server 20, it may also be part of the management server 20.

[0017] Module DB 33a stores module data including the module type and specification information for each module available for purchase on Marketplace MP. The module type includes, for example, a robot, end effector, camera, conveyor, feeder, and the like. The specification information includes information on the vendor providing each module (vendor ID, described below), the module's product number (model), size, shape, and drawing files such as 3D CAD data. The specification information also includes performance information such as rated load, range of motion, payload capacity, and operating speed, depending on the module type.

[0018] The project DB 33b registers various information for each project of each work system WS (each piece of equipment) that has already been delivered to a customer or that the customer is considering purchasing, i.e., has not yet been delivered. The various information registered includes the name of the project (project name), overall specification information for the work system WS, specification information for each module of the work system WS, and information on the delivery cost and estimated cost. The overall specification information includes information such as the size, weight, and shape of the work (object) to be worked on, information on the layout and installation space of each module in the work system WS, and drawing files such as 3D CAD data for the work system WS. The delivery cost and estimated cost information includes information such as the overall cost of the work system WS, the cost of each module, and installation costs.

[0019] The vendor DB 33c stores various information for each vendor, such as the name of the authenticated vendor, a vendor ID unique to each vendor, capital, number of employees, business field, types of modules provided by the vendor, etc. The customer DB 33d stores customer information for each customer, such as the name of the authenticated customer, a customer ID unique to each customer, contact information such as email address and address, and purchase history of the customer.

[0020] As shown in FIG. 3 , the operation DB 33e stores specification information, configuration information, operation information, and work information for each work system WS (equipment) that has been delivered to a customer. The specification information includes information on the work to be performed, information on the layout and installation space of each module, and information on the work content. The work information includes the size, weight, and shape of the work. The configuration information includes information on the name and product number of each module and each consumable. While FIG. 3 illustrates an example in which the robot, end effector, and conveyor each include one type of consumable, this is not limiting and two or more types of consumables may be included. Furthermore, some types of modules, such as cameras, may not include consumables.

[0021] The operation information includes, for example, load information on the work situation (content and environment), such as output, continuous time, and temperature, as well as information on cumulative usage time, such as cumulative time 1 and cumulative time 2. Because each module is configured as an IoT module as described above, information acquired by various sensors is sequentially transmitted to the data server 30 and accumulated and stored in the operation DB 33e ( FIG. 2 (2)). While FIG. 3 shows an example of items included in the operation information, the operation DB 33e actually stores received information, such as output and temperature, in chronological order. The output indicates, for example, the output of an actuator, such as a motor, possessed by the module. In addition to the chronological output, the average value of maximum output per operating day or the average output ratio to rated output may also be stored. Since the robot 100 has multiple motors, such as a motor in each joint of the robot arm, it is sufficient that the output of each motor is registered. The continuous time indicates, for example, the time during which the module is continuously used on an operating day of the operating system WS, i.e., the time during which the operating system WS is continuously operating without pausing (continuous operating time). In addition, the average continuous time per operating day (average continuous operating time) may be stored. Temperature indicates the temperature of the module during operation. Note that other information indicating the working environment of the module (such as humidity) may be registered in addition to temperature. Cumulative time 1 indicates the accumulated time of use since the module was maintained. Cumulative time 2 indicates the accumulated time of use since the module or consumables were replaced. Note that if no maintenance or replacement has been performed since the operation system WS was delivered, cumulative time 1 and cumulative time 2 may be the accumulated time of use since the operation system WS started operating. Furthermore, for modules that can count the number of images taken (operations), such as a camera, the number of uses may be stored instead of the usage time. In that case, cumulative time 1 and cumulative time 2 may be the accumulated number of uses, respectively.

[0022] The work information includes the maintenance date, evaluation, replacement date, etc. The maintenance date is information on the date on which module maintenance was performed. The evaluation is information indicating whether the maintenance cycle MC was appropriate when maintenance was performed according to the maintenance cycle MC. For example, the worker checks the wear on the module after maintenance and, if the wear is normal and the maintenance cycle MC is appropriate, registers the evaluation as "○." Furthermore, if the wear is lighter than normal and the maintenance cycle MC is short, i.e., the maintenance should be performed early, the worker registers the evaluation as "△." Furthermore, if the wear is more severe than normal and the maintenance cycle MC is long, i.e., the maintenance should be performed late, the worker registers the evaluation as "×." Note that evaluations may be registered not only at the time of maintenance but also at the time of replacement. The replacement date is information on the date on which the module or consumable was replaced. The work information may be registered based on information transmitted from the mobile terminal of the worker who performed the maintenance or replacement, or based on information input by the worker via the input unit 27 or 67. Furthermore, by performing a predetermined operation on each module, which is an IoT module, the maintenance date or replacement date may be transmitted to the data server 30. Note that in this embodiment, it is not essential that the operation information includes specification information and work information, and such information may not be included.

[0023] The period DB 33f stores the maintenance period MC, replacement period RC, etc. for each module and each consumable item in the work system WS. The registration process for the maintenance period MC and replacement period RC will be described in detail later.

[0024] The vendor terminal 50 includes a control unit 51 having a CPU, ROM, RAM, etc., a storage unit 53 such as an HDD or SSD that stores various application programs and various data, and a communication unit 55 that is connected to the network 12 or the like and communicates with the management server 20, etc. Various instructions from the vendor and various information that needs to be registered are input into the vendor terminal 50 via an input unit 57 such as a keyboard or mouse. The vendor terminal 50 also displays various screens of the Marketplace MP on a display unit 59 such as a display.

[0025] Like the vendor terminal 50, the customer terminal 60 includes a control unit 61, a storage unit 63, and a communication unit 65. The customer terminal 60 receives various instructions from the customer and various pieces of information that need to be registered via an input unit 67, such as a keyboard or mouse. The customer terminal 60 also displays various screens of the Marketplace MP on a display unit 69, such as a display. In this embodiment, the customer accesses the data server 30 via the network 12 from the customer terminal 60, for example, and is presented with information such as that shown in FIG. 3 (FIG. 2(a)). This information is displayed, for example, on the display unit 69 of the customer terminal 60. This allows the customer to check the operational status of the operational system WS, such as the operational information and task information stored in the operational DB 33e.

[0026] Next, we will explain the operation of the market system 10 configured in this manner, particularly the process of notifying customers of replacement and maintenance instructions for each module and each consumable item in the work system WS that has already been delivered to the customer. First, we will explain the process of setting the maintenance period MC and the replacement period RC. Figure 4 is a flowchart showing an example of the period setting process. This process is executed by the control unit 21 of the management server 20 when, for example, period setting is selected on a setting screen (not shown) displayed on the display unit 69 of the customer terminal 60.

[0027] In the cycle setting process, the control unit 21 sets a maintenance cycle MC and a replacement cycle RC for each module constituting the operation system WS (S100), and sets a replacement cycle RC for each consumable included in the module (S110). The control unit 21 may set the maintenance cycle MC and replacement cycle RC by accepting input from the customer via, for example, a setting screen displayed on the display unit 69 of the customer terminal 60. The customer may input and set each cycle based on the settings of previously delivered operation systems WS and general maintenance and replacement cycles. Recommended maintenance and replacement cycles are displayed by default on the setting screen, and the customer may set these recommended cycles or may change the recommended cycles.

[0028] Next, the control unit 21 determines whether the customer has selected to set a correction coefficient (S120), and if it determines that the correction coefficient has not been selected, the process proceeds to S140. As described above, the operation information includes output, time (continuous time), temperature, and the like. The correction coefficient is a coefficient for correcting the maintenance cycle MC and replacement cycle RC in the process described below based on the output, time, and temperature. If the control unit 21 determines that the correction coefficient has been selected, the control unit 21 sets a correction coefficient map for the item selected by the customer from among output, time, and temperature (S130), and then proceeds to S140. Note that the customer only needs to select at least one item from among output, time, and temperature, and may select two or more items.

[0029] FIG. 5 is an explanatory diagram showing an example of a correction coefficient map. In FIG. 5, the horizontal axis represents the selected item (output, time, or temperature), and the vertical axis represents the correction coefficient. A correction coefficient map is set for each item. In the correction coefficient map, the correction coefficient is set based on one of the setting lines L. The reference setting line L is set as setting line L0 (see solid line). Each setting line L is set so that the correction coefficient is set to 1 when the item value is within a reference range R that includes a reference value (reference output, reference time, reference temperature) SV. When the item value is outside the reference range R, the correction coefficient decreases as the value increases, and increases as the value decreases. For example, the output coefficient X, which corrects the period based on output, is set to 1 when the output is within the reference range R, and decreases as the output increases outside the reference range R, and increases as the output decreases. A time coefficient Y, which corrects the period based on time, and a temperature coefficient Z, which corrects the period based on temperature, are also set in a similar manner. Note that each coefficient X to Z may be set to a different reference range R, and are not limited to using the same setting line L. For example, for a coefficient for which the influence is more important, a setting line L2 may be used whose slope is determined so that the influence becomes greater when the reference range R is exceeded. Conversely, a setting line L1 may be used whose slope is determined so that the influence becomes smaller when the reference range R is exceeded. Note that the reference range R is not limited to a symmetrical range centered on the reference value SV, but may be, for example, a range that includes all sides smaller than the reference value SV. Furthermore, the slope of the setting line L may be determined arbitrarily by the customer. In setting the correction coefficient map in S130, the reference value SV, reference range R, setting line L, etc. of the coefficient to be set are set.

[0030] The control unit 21 then registers the settings made in S110 and S130 in the cycle DB 33f (S140), and terminates this process. FIG. 6 is an explanatory diagram showing an example of the cycle DB 33f. For example, in a work system WS, the maintenance cycles MC and replacement cycles RC of modules such as robots, end effectors, cameras, and conveyors, as well as the replacement cycles RC of consumables included in each module, are registered. Furthermore, the output coefficient X, time coefficient Y, and temperature coefficient Z are registered as correction coefficients for each module and its consumables.

[0031] 7 is a flowchart showing an example of a timing prediction process. This process determines the timing of maintenance or replacement based on the maintenance cycle MC and replacement cycle RC, and is executed by the control unit 31 of the data server 30. In the timing prediction process, the control unit 31 acquires operation information of the operation system WS to be predicted, and the maintenance cycle MC and replacement cycle RC of each module and each consumable item in the operation system WS (S200). The control unit 31 acquires the operation information from the operation DB 33e (FIG. 2(b)), and acquires the maintenance cycle MC and replacement cycle RC from the cycle DB 33f (FIG. 2(c)).

[0032] Next, the control unit 31 determines whether the cycle DB 33f contains a correction coefficient map for any of the modules or consumables of the work system WS, i.e., whether the correction coefficient map set in S130 of the cycle setting process is registered (S210). If the control unit 31 determines that a correction coefficient map is not present, the process proceeds to S230. On the other hand, if the control unit 31 determines that a correction coefficient map is present, the control unit 31 sets a correction coefficient based on the operation information and the correction coefficient map to correct each cycle MC and RC (maintenance cycle MC and replacement cycle RC) (S220). In S220, the control unit 31 sets the correction coefficient for which a correction coefficient map is registered, among the output coefficient X, time coefficient Y, and temperature coefficient Z, based on the operation information and the correction coefficient map. The control unit 31 also corrects the maintenance cycle MC and replacement cycle RC by multiplying the maintenance cycle MC and replacement cycle RC by the set correction coefficient, respectively. If multiple correction coefficients are set, the control unit 31 may perform correction by multiplying the maintenance cycle MC and the replacement cycle RC by the multiple correction coefficients, respectively.

[0033] For example, in FIG. 6 , an output coefficient X, a time coefficient Y, and a temperature coefficient Z are registered as correction coefficients for the robot and its consumables. Therefore, the control unit 31 sets the output coefficient X based on the output correction coefficient map and the output of the operation information, sets the time coefficient Y based on the time correction coefficient map and the usage time of the operation information, and sets the temperature coefficient Z based on the temperature correction coefficient map and the temperature of the operation information. The control unit 31 then performs correction by multiplying the output coefficient X, the time coefficient Y, and the temperature coefficient Z by the maintenance cycle MC (X×Y×Z×MC) and the replacement cycle RC (X×Y×Z×RC). Note that in FIG. 6 , the output coefficient X and the time coefficient Y are registered as correction coefficients for the end effector, conveyor, and their consumables, but the temperature coefficient Z is not. Therefore, each cycle MC and RC is corrected by multiplying the corrected output coefficient X by the time coefficient Y and by the temperature coefficient Z, which remains at 1. Furthermore, since the correction coefficients for the camera are not registered, the camera periods MC and RC are not corrected and remain at the registered values.

[0034] Next, the control unit 31 predicts the timing of maintenance or replacement for each module and each consumable item based on the maintenance cycle MC, the replacement cycle RC, and the cumulative times 1 and 2 included in the operation information (S230). The control unit 31 calculates the approximate number of days until maintenance by, for example, dividing the difference between the maintenance cycle MC and the cumulative time 1 by the average continuous operation time, and predicts the timing of maintenance. The control unit 31 also calculates the approximate number of days until replacement by, for example, dividing the difference between the replacement cycle RC and the cumulative time 2 by the average continuous operation time, and predicts the timing of replacement.

[0035] For example, if the output of the operation information is higher than the reference range R of the reference value SV of the correction coefficient map, an output coefficient X smaller than 1 is set. Multiplying each cycle MC and RC by this output coefficient X for correction results in a shorter cycle MC and RC. On the other hand, if the output of the operation information is lower than the reference range R of the reference value SV of the correction coefficient map, an output coefficient X larger than 1 is set. Multiplying each cycle MC and RC by this output coefficient X for correction results in a longer cycle MC and RC. Similarly, the time coefficient Y and the temperature coefficient Z are set smaller than 1 when the output is higher than the reference range R of the reference value SV of the correction coefficient map, and are set larger than 1 when the output is lower than the reference range R of the reference value SV of the correction coefficient map. Therefore, when the load on a module or consumable is high due to high output or temperature or a long duration (continuous time), it becomes easier to determine the timing of maintenance or replacement, and the processing described below can be used to appropriately prompt maintenance or replacement. On the other hand, if the load on the module or consumables is low because the output or temperature is low or the time (continuous time) is short, it becomes difficult to determine the time for maintenance or replacement, so the processing described below can prevent unnecessary prompting for maintenance or replacement.

[0036] The control unit 31 then determines whether any module is nearing its predicted maintenance deadline, for example, whether the maintenance deadline is within a predetermined period of time (S240), and if it determines that no module is nearing its maintenance deadline, the process proceeds to S260. On the other hand, if the control unit 31 determines that any module is nearing its predicted maintenance deadline, the control unit 31 sets the corresponding module as a module to be maintained (S250) and proceeds to S260. The control unit 31 also determines whether any module is nearing its predicted replacement deadline, for example, whether the replacement deadline is within a predetermined period of time (S260), and if it determines that no module is nearing its replacement deadline, the process proceeds to S280. On the other hand, if the control unit 31 determines that any module or consumable is nearing its replacement deadline, the control unit 31 sets the corresponding module or consumable as a module to be replaced (S270) and proceeds to S280.

[0037] Next, the control unit 31 determines whether or not there is a target set in at least one of S250 and S270 (S280), and if it determines that there is no target set, it ends this process. On the other hand, if it determines that there is a target set, the control unit 31 transmits information about that target to the management server 20 (S290, FIG. 2 (3)), and ends this process.

[0038] Next, the notification process of the management server 20 will be described. FIG. 8 is a flowchart showing an example of the notification process. In the notification process, the control unit 21 of the management server 20 first determines whether or not the information transmitted from the data server 30 in S290 of FIG. 7, i.e., information on the module to be maintained or replaced, has been received (S300). If it determines that the information has not been received, the control unit 21 terminates this process. On the other hand, if the control unit 21 determines that the information has been received, it determines whether or not there is a module to be maintained (S310). If it determines that there is no module to be maintained, the process proceeds to S330. If the control unit 21 determines that there is a module to be maintained, it creates a maintenance guide for the module to be maintained (S320) and proceeds to S330. The maintenance guide includes information such as the name of the module to be maintained and the predicted maintenance time.

[0039] Next, the control unit 21 determines whether there is a replacement item (S330). If it determines that there is no replacement item, the control unit 21 proceeds to S370. If it determines that there is a replacement item, the control unit 21 creates a replacement guide for the target module or consumable (S340). The replacement guide includes information such as the name of the target module, the predicted replacement time, and the purchase price on Marketplace MP. Next, the control unit 21 determines whether a replacement item, such as a successor or improved product, is available for the target module or consumable (S350). If it determines that there is no replacement item, the control unit 21 proceeds to S370. The control unit 21 determines whether a replacement item is available based on, for example, whether information on a successor or improved product is registered in the module DB 33a. If it determines that a replacement item is available, the control unit 21 includes the replacement item for the target module or consumable in the guide (S360) and proceeds to S370. That is, the guide in S360 also includes information such as whether the module or consumable may be replaced with a replacement item and the purchase price of the replacement item on Marketplace MP. Next, the control unit 21 notifies the customer of the information created in at least one of S320, S340, and S360 (S370, FIG. 2(4)), and ends this process.

[0040] A customer who is notified of a maintenance or replacement notice may respond, for example, as follows: When a customer is notified of a maintenance notice, if the customer is able to perform the maintenance themselves, they will have their own workers perform the maintenance. If the customer is unable to perform the maintenance themselves, they will request maintenance from Marketplace MP (Figure 2 (5)). That is, the customer places an order for maintenance with the module vendor or other party via Marketplace MP. The vendor that receives the order will have a worker go to the customer's factory or other location to perform maintenance on the module (Figure 2 (6)). The worker who performed the maintenance registers the maintenance date and evaluation for the module and resets the cumulative time 1.

[0041] Furthermore, when a customer receives a replacement notice, the customer purchases the module or consumable related to the notice through Marketplace MP (FIG. 2 (5)). That is, the customer places an order for the module or consumable related to the notice with the vendor via Marketplace MP. If the notice includes a replacement, the customer may purchase a replacement module or consumable. Upon receiving such an order, the vendor sends a worker to the customer's factory or other location along with the module or consumable (including the replacement) to replace the module or consumable (FIG. 2 (6)). Alternatively, if the customer can replace the module or consumable in-house, the customer may have their own worker replace the module or consumable shipped from the vendor. The worker who replaces the module registers the replacement date of the module and resets the maintenance date and cumulative time 1 and 2. The worker who replaces the consumable also registers the replacement date of the consumable and resets cumulative time 2. The cumulative time 1 and 2 may be recorded without being reset. By recording the cumulative times 1 and 2, it is possible to obtain multiple pieces of data that combine the cumulative time when maintenance or replacement is performed and the evaluation at that time, and the customer can use the obtained multiple pieces of data to check the maintenance records and evaluate the appropriateness of the maintenance cycle at a later date.

[0042] Furthermore, the customer may check the evaluation of the maintenance in the operation DB 33e and reset (change) the maintenance cycle MC. The customer selects cycle setting (resetting) on ​​a setting screen (not shown) displayed on the display unit 69 of the customer terminal 60, for example, and resets the cycle, such as lengthening or shortening, based on the evaluation. The cycle resetting may also be performed by a vendor or an operator. The control unit 21 of the management server 20 registers the reset cycle in the cycle DB 33f. In this way, by repeatedly resetting the maintenance cycle MC reflecting the evaluation, the maintenance cycle MC registered in the cycle DB 33f is optimized.

[0043] Here, the correspondence between the components of this embodiment and the components of the present disclosure will be clarified. In this embodiment, the memory unit 33 of the data server 30 corresponds to the memory unit, the control unit 31 of the data server 30 that executes the timing prediction process corresponds to the prediction unit, and the control unit 21 of the management server 20 that executes the notification process corresponds to the notification unit. In this embodiment, the operation of the market system 10 is explained, thereby clarifying an example of the order promotion method of the present disclosure.

[0044] The market system 10 of the present embodiment described above predicts the replacement time for each component based on the component's replacement cycle RC and operation information including the component's cumulative time 2 (cumulative usage time). Furthermore, before the predicted replacement time arrives, the system notifies the customer of the need to order the component due for replacement via Marketplace MP (an e-commerce site). This reduces the customer's management burden, and allows the customer to be appropriately notified when a component needs to be replaced, encouraging them to place an order via Marketplace MP.

[0045] In addition, the operation information includes the cumulative time 2 (cumulative usage time) of the consumables included in the component, and the replacement time for each consumable is predicted based on the consumable replacement cycle RC and the operation information. Before the predicted replacement time arrives, the system notifies the customer via Marketplace MP of the need to order the consumables. Therefore, the system can appropriately notify the customer of the need to replace consumables included in the component while minimizing the customer's management burden, encouraging them to order via Marketplace MP. When a component includes multiple consumables, the customer's management burden increases, making it highly significant to apply the present disclosure.

[0046] In addition, if there are alternatives, including successor products, for components that are due for replacement, the information about the alternatives will be included in the notification. Therefore, even if a replacement such as a successor product is available, customers can be encouraged to order the replacement product even if they are not aware of its existence.

[0047] The market system also predicts the timing of maintenance for each component based on the component's maintenance cycle MC and operation information including the component's cumulative time 1 (cumulative usage time). Furthermore, before the predicted maintenance time arrives, the system notifies customers of maintenance for the component related to the maintenance time. This reduces the customer's management burden while also appropriately notifying them when component maintenance is required, thereby encouraging them to order maintenance through Marketplace MP.

[0048] The market system also stores load information related to the operational load of components in the operational information. Furthermore, the timing of maintenance and replacement is predicted based on the operational information and the corrected maintenance and replacement cycles (MC and RC), which tend to become shorter as the operational load increases. This allows the operational load of components to be appropriately reflected in the determination of the cycles, enabling necessary information to be more appropriately communicated to customers.

[0049] In addition, in the market system, the storage unit collects and stores operation information for each module transmitted by communication from modules with IoT functions, making it possible to easily collect operation information and appropriately notify customers of necessary guidance.

[0050] It goes without saying that the present disclosure is not limited to the above-described embodiments, and can be embodied in various forms as long as they fall within the technical scope of the present disclosure.

[0051] In the embodiment, the management server 20 sets the maintenance cycle MC and the replacement cycle RC to cycles input by, for example, a customer, but this is not limited to this. As in the following modified example, a derivation model may be created and the maintenance cycle MC may be set to the derivation model derived from that derivation model. In the modified example, a derivation model for the maintenance cycle MC is used as an example, but it may also be applied to a derivation model for the replacement cycle RC. In the modified example, it is assumed that the maintenance cycle MC in the cycle DB 33f is reset and optimized based on the maintenance evaluation.

[0052] FIG. 9 is a configuration diagram showing an outline of the configuration of a market system 10B according to a modified example. FIG. 10 is an explanatory diagram showing an outline of the functions and processing of the market system 10B according to a modified example. The market system 10B includes a simulation device 40 (simulation unit) in addition to a management server 20 and a data server 30. The simulation device 40 includes a control unit 41 having a CPU, ROM, RAM, etc., a storage unit 43 such as an HDD or SSD, and a communication unit 45 connected to a network 12 or the like to communicate with the management server 20, the data server 30, the vendor terminal 50, the customer terminal 60, etc. Note that although the simulation device 40 is shown as a separate device from the management server 20 and the data server 30, it may also be part of the management server 20 or the data server 30.

[0053] The control unit 41 constructs a simulation model MS as a digital twin of the work system WS, which is a combination of various modules, and receives simulation conditions SC, including specification information such as information about the target workpiece and the work content of the work system WS. The simulation conditions SC are input by a customer to a customer terminal 60, for example, by customer B in FIG. 10 for simulating the work system WS0 (FIG. 10(d)). The simulation conditions SC may be input by a vendor to a vendor terminal 50 or may be generated by the management server 20 or the simulation device 40. The control unit 41 then executes a simulation using the simulation model MS based on the simulation conditions SC and generates simulation results SR, including information such as the motor output of the modules, load information such as continuous time and temperature, and cycle time. The simulation device 40 outputs the simulation model MS, simulation conditions SC, and simulation results SR to the data server 30 (FIG. 10(e)). The data server 30 stores the information input from the simulation device 40, for example, in the project DB 33b of the storage unit 33.

[0054] Next, a process performed by the control unit 31 (derivation unit) of the data server 30 to derive the maintenance cycle MC will be described. First, a process for creating and updating the derivation model 34 for deriving the maintenance cycle MC will be described. FIG. 11 is a flowchart showing an example of the derivation model-related process. In the derivation model-related process, the control unit 31 determines whether it is time to create the derivation model 34 (S400), and if it determines that it is not time to create the derivation model 34, the process proceeds to S430. The timing for creating the derivation model 34 may be, for example, a timing when the operation DB 33e and the cycle DB 33f have accumulated sufficient information to be used for creating the derivation model 34, even though the derivation model 34 has not yet been created.

[0055] When the control unit 31 determines that it is time to create the derivation model 34, it acquires specification information and load information (output, continuous time, temperature, etc.) from the operation DB 33e and acquires the maintenance cycle MC from the cycle DB 33f to create the derivation model 34 (S410). The derivation model 34 may be created by statistical analysis or machine learning. For example, the derivation model 34 may be created for each type of workpiece or type of work content using load information as an explanatory variable and the maintenance cycle MC as a target variable. As described above, the maintenance cycle MC is optimized based on the evaluation of the work information, so that the maintenance cycle MC derived by the derivation model 34 can be made appropriate. The control unit 31 registers the created derivation model 34 in the storage unit 33 (S420) and proceeds to S430.

[0056] The control unit 31 also determines whether it is time to update the derived model 34 (S430), and if it determines that it is not time to update, ends this processing. The timing to update the derived model 34 may be, for example, the timing when information used to create the derived model 34 is additionally stored in the operation DB 33e or the cycle DB 33f. If the control unit 31 determines that it is time to update the derived model 34, it acquires the specification information and load information added to the operation DB 33e and the maintenance cycle MC added to the cycle DB 33f, updates the derived model 34 corresponding to the specification information (S440), and ends this processing. In this way, in the modified example, when information used to create the derived model 34 is added, the derived model 34 is updated, and therefore the accuracy of derivation of the maintenance cycle MC by the derived model 34 can be improved.

[0057] Next, a process for deriving a maintenance cycle MC using the derivation model 34 will be described. Fig. 12 is a flowchart showing an example of the cycle derivation process. The control unit 31 executes the cycle derivation process when there is a simulation result SR for the work system WS (work system WS0 in Fig. 10) from which the cycle is to be derived. Note that when there is no simulation result SR for the work system WS from which the cycle is to be derived, the control unit 31 may, for example, prompt the customer to input simulation conditions SC and execute a simulation.

[0058] In the cycle derivation process, the control unit 31 acquires simulation conditions SC, including specification information, for the work system WS to be derived (S500), and also acquires simulation results SR, including load information (S510). In S500 and S510, the control unit 31 acquires the simulation conditions SC and simulation results SR input from the simulation device 40 (stored in the case DB 33b of the storage unit 33). Next, the control unit 31 derives a maintenance cycle MC using the derivation model 34 based on the acquired specification information and load information (S520) and presents the maintenance cycle MC to, for example, a customer (S530, FIG. 10(f)). The control unit 31 may present the derived maintenance cycle MC to the customer terminal 60, for example. The customer can view the maintenance cycle MC transmitted to the customer terminal 60 on the display unit 69. This allows the customer to determine the appropriate maintenance cycle MC for the work system WS under consideration, such as by running a simulation. The control unit 31 may present the maintenance cycle MC not only to the customer but also to the vendor.

[0059] Next, the control unit 31 determines whether an instruction to register the presented maintenance cycle MC has been received (S540), and if it determines that an instruction has not been received, the process ends. For example, if the customer agrees with the maintenance cycle MC confirmed on the display unit 69, the customer may issue an instruction to register the maintenance cycle MC. On the other hand, if the control unit 31 determines that an instruction has been received, the control unit 31 associates the maintenance cycle MC with the work system WS and registers it in the cycle DB 33f (S550, FIG. 10(g)), and then ends the process.

[0060] In this modified example, the simulation device 40 creates a simulation model MS of the work system WS in a virtual space, accepts simulation conditions SC including specification information, simulates the simulation model MS, and outputs simulation results SR including load information. The control unit 31 generates a derivation model 34 for deriving a maintenance cycle MC from the specification information, load information, and cycle information based on the specification information, load information, and cycle information. The control unit 31 then uses the derivation model 34 to derive the maintenance cycle MC based on the simulation conditions SC and the simulation results SR. This allows the derivation model 34 to be created, reflecting the load information and maintenance evaluation of each work system WS that has already been delivered. The derivation model 34 can then be used to derive an appropriate maintenance cycle MC and present it to the customer when considering the configuration of a new work system WS or before placing an order. This allows the customer to consider the maintenance cycle MC when considering module components, for example, during the pre-installation stage of the work system WS. For example, a customer may select a small module because they prioritize price, but the motor's output or temperature may increase, shortening the maintenance cycle and increasing costs. Even in such a case, in the modified example, the derived model 34 is used to present the customer with the maintenance cycle MC before purchase, making it possible to appropriately select each module that makes up the work system WS.

[0061] In the embodiment, the timing of maintenance or replacement is determined using both the maintenance period MC and the replacement period RC, but this is not limited to this, and only one of the maintenance period MC and the replacement period RC may be used to determine the timing of maintenance or replacement.

[0062] In the embodiment, the timing of maintenance or replacement of modules is determined using the maintenance period MC and replacement period RC, and the timing of replacement of consumables is determined using the replacement period RC, but this is not limited to this. For example, the timing of maintenance or replacement of consumables may also be determined using the maintenance period MC and replacement period RC. Furthermore, while the timing of maintenance or replacement of modules is determined, the timing of maintenance or replacement of consumables may not be determined and they may not be managed. However, in order to reduce the management burden on customers, it is preferable to manage consumables as well.

[0063] In the embodiment, if it is determined that a substitute is available for a component or consumable item, the substitute is included in the notification and notified, but this is not limited to this, and it is also possible not to determine whether a substitute is available or not, and not to include the substitute in the notification.

[0064] In the embodiment, the maintenance period MC and replacement period RC can be corrected based on the output, time, and temperature, but this is not limiting, and the maintenance period MC and replacement period RC may be corrected based on only one or two of the output, time, and temperature. Alternatively, such correction of the maintenance period MC and replacement period RC may not be performed.

[0065] In the embodiment, each module is configured as an IoT module, and operation information is transmitted from the IoT module to the data server 30. However, this is not limiting, and each module does not have to be configured as an IoT module. For example, the control unit of the work system WS may collect operation information of each module and transmit it to the data server 30.

[0066] The present disclosure is applicable to technical fields such as e-commerce sites for components of production facilities.

[0067] 10, 10B Market system, 12 Network, 20 Management server, 21, 31, 41, 51, 61 Control unit, 23, 33, 43, 53, 63 Memory unit, 25, 35, 45, 55, 65 Communication unit, 27, 57, 67 Input unit, 29, 59, 69 Display unit, 30 Data server, 33a Module DB, 33b Project DB, 33c Vendor DB, 33d Customer DB, 33e Operation DB, 33f Period DB, 34 Derived model, 40 Simulation device, 50 Vendor terminal, 60 Customer terminal, 100 Robot, 102 End effector, 103 Camera, 104 Conveyor, 105 Feeder, MS Simulation model, MP Marketplace, WS0, WS1 Work system.

Claims

1. A market system that operates an electronic commerce site where customers can order components that make up production equipment, comprising: a storage unit that collects and stores operation information for each component, including the cumulative usage time or cumulative number of uses of the component; a prediction unit that predicts the replacement time for each component based on the replacement cycle of the component and the operation information; and a notification unit that notifies customers, before the predicted replacement time arrives, to guide them to order the component related to the predicted replacement time on the electronic commerce site.

2. The market system described in claim 1, wherein the memory unit stores the operation information including the cumulative usage time or cumulative usage count of the consumables of the component, the prediction unit predicts the replacement time for each consumable based on the replacement cycle of the consumables and the operation information, and the notification unit notifies the customer, before the predicted replacement time arrives, to order the consumables related to the predicted replacement time on the e-commerce site.

3. The market system according to claim 1, wherein, when there is a replacement product, including a successor product, for the component that is due for replacement, the notification unit notifies the user of the replacement product by including the replacement product in the notification.

4. A market system that operates an e-commerce site where customers can order components that make up production equipment, comprising: a memory unit that collects and stores operation information for each component, including the cumulative usage time or cumulative number of uses of the component; a prediction unit that predicts the timing of maintenance for each component based on the maintenance cycle of the component and the operation information; and a notification unit that notifies customers of maintenance information for the component related to the predicted maintenance period before the predicted maintenance period arrives.

5. A market system as described in claim 1 or 4, wherein the memory unit stores the operation information including load information regarding the operation load of the component, and the prediction unit predicts the timing based on the operation information and a corrected period in which the period has been corrected so that it tends to become shorter as the operation load is higher.

6. The market system according to claim 1 or 4, wherein the memory unit stores specification information relating to the objects and contents of production in the production facility, load information relating to the operating load of the components, and period information relating to the period; a simulation unit that creates a simulation model of the production facility in a virtual space, accepts simulation conditions including the specification information, performs a simulation using the simulation model, and outputs simulation results including the load information; and a derivation unit that generates a derivation model for deriving the period from the specification information and the load information based on the specification information, the load information, and the period information, and derives the period using the derivation model based on the simulation conditions and the simulation results.

7. A market system as described in claim 1 or 4, wherein the storage unit collects and stores the operation information transmitted by communication from the components having IoT functions for each of the components.

8. A method for promoting ordering on an e-commerce site where customers can order components that make up production equipment, comprising the steps of: collecting and storing operation information for each component, including the cumulative usage time or cumulative number of uses of the component; predicting the replacement time for each component based on the component replacement cycle and the operation information; and notifying customers, before the predicted replacement time arrives, of instructions to order the component related to the predicted replacement time on the e-commerce site.

9. A method for promoting orders on an e-commerce site where customers can order components that make up production equipment, comprising the steps of: collecting and storing operation information for each component, including the cumulative usage time or cumulative number of uses of the component; predicting the timing of maintenance for each component based on the maintenance cycle of the component and the operation information; and notifying customers of maintenance information for the component related to the predicted maintenance period before the predicted maintenance period arrives.

Images