WO2020170426A1

WO2020170426A1 - Module management system

Info

Publication number: WO2020170426A1
Application number: PCT/JP2019/006799
Authority: WO
Inventors: 明洋東田; 雅史天野
Original assignee: 株式会社Ｆｕｊｉ
Priority date: 2019-02-22
Filing date: 2019-02-22
Publication date: 2020-08-27
Also published as: JP7383001B2; JPWO2020170426A1

Abstract

This module management system, which manages multiple types of modules constituting a work system, comprises: a storage unit that stores information; and a management unit that sets unique information for each prescribed category of the modules, associates the unique information with the specifications of the modules, and stores the unique information in the storage unit. Identifiers associated at least with the unique information are provided to the modules so as to be recognizable from the outside by a recognition device.

Description

Module management system

This specification discloses a module management system.

Conventionally, in a robot in which a forearm including a hand such as an end effector can be attached and detached, when the forearm is attached to the robot, a control unit in the forearm and a robot controller exchange information necessary for controlling the forearm. Things have been proposed. For example, in Patent Document 1, the control unit in the forearm stores information such as identification information for identifying the type of the forearm, and when the forearm is attached to the robot, the identification information is transmitted to the controller of the robot. To do. Further, when receiving the identification information, the control device of the robot performs various settings by reading out information of the forearm portion corresponding to the identification information from the information of the various forearm portions stored in advance.

JP, 2016-190282, A

The control device of the robot can acquire the identification information of the modules such as the above-mentioned forearm that are communicatively attached to the robot. However, in a system including a robot, there are modules that cannot communicate with the robot, and thus the controller of the robot may not be able to acquire the identification information of all the modules. In that case, for example, it may be difficult to confirm whether the module configuration of the system simulated before the installation and the module configuration of the system actually installed match, and the incorrect module configuration may be used.

The main purpose of this disclosure is to more appropriately manage modules with a simple configuration.

The present disclosure has adopted the following means in order to achieve the main purpose described above.

The module management system of the present disclosure is
A module management system that manages multiple types of modules that make up the work system,
A storage unit for storing information,
A management unit that sets unique information for each predetermined classification of the module, and stores the unique information in the storage unit in association with the specification of the module;
Equipped with
The gist is that at least an identifier associated with the unique information is provided in the module so that it can be recognized from the outside by a recognition device.

In the module management system of the present disclosure, unique information is set for each predetermined classification of modules, and the unique information is stored in the storage unit in association with the module specifications. Further, at least an identifier associated with the unique information is provided in the module so that the identifier can be recognized from the outside by the recognition device. As a result, even if the unique information of the module cannot be obtained due to the communication between the modules, it is possible to obtain the unique information of the module and the specification associated with the unique information by recognizing the identifier provided in the module. it can. For this reason, it is possible to easily classify the modules and check the specifications, so that it is possible to more appropriately manage the modules with a simple configuration. The predetermined classification may be classified according to the type of module, vendor, model, or the like. Further, the identification body may be provided as an identification code such as a 2D code that can be recognized by the code recognition device or an identification tag such as an IC tag that can be recognized by the tag recognition device.

The block diagram which shows the outline of a structure of the equipment introduction support system. Explanatory drawing which shows the outline of marketplace MP. The block diagram which shows the outline of a structure of the work system 60. Explanatory drawing which shows an example of module DB30. FIG. 5 is a sequence diagram showing an example of processing of the management server 20, the vendor terminal 40, and the customer terminal 50. Explanatory drawing which shows an example of the module data 30B of an end effector. Explanatory drawing which shows an example of the end effector 63 in which the 2D code C was provided. Explanatory drawing which shows an example of introduction record DB35. Explanatory drawing which shows an example of a combination module. Explanatory drawing which shows an example of a mode that a combination of modules is changed. Explanatory drawing which shows an example of the module combination information 36.

Next, a mode for carrying out 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 facility introduction support system 10 of the present embodiment, FIG. 2 is an explanatory diagram showing an outline of a marketplace MP, and FIG. 3 shows an outline of a configuration of a work system 60. It is a block diagram. As shown in FIGS. 1 and 2, the facility introduction support system 10 includes a management server 20 that manages a marketplace MP for customers to purchase various facilities and devices (hereinafter, modules) provided by a vendor. .. In this equipment introduction support system 10, a management server 20 is connected to a vendor terminal 40 and a customer terminal 50 via a network 12. In FIG. 1, one vendor terminal 40 and one customer terminal 50 are shown, but a plurality of vendor terminals 40 and customer terminals 50 are actually connected.

The management server 20 includes a control unit 21, a simulation unit 22, a storage unit 23, and a communication unit 26. The control unit 21 has a CPU, a ROM, a RAM, etc., and controls the entire server such as management of the marketplace MP, and also manages modules introduced to the customer. The simulation unit 22 constructs a model MD (digital twin, see FIG. 2) such as a work system 60 (see FIG. 3) in which modules that can be purchased at the marketplace MP are combined in a virtual space, and the model MD is created in the virtual space. Run a simulation using. The storage unit 23 includes an HDD and stores various application programs and various databases (DB). The communication unit 26 is connected to the network 12 or the like and communicates with the vendor terminal 40 or the customer terminal 50. Various instructions from the administrator are input to the management server 20 from the input unit 28 such as a keyboard and a mouse. Further, the management server 20 displays various information on the display unit 29 such as a display. The management server 20 is not limited to one including the simulation unit 22 and the storage unit 23 (various DBs), and the simulation unit may be configured as another device capable of communicating with the management server 20 or stores various DBs. The data server may be configured as another device capable of communicating with the management server 20.

The vendor terminal 40 is connected to the control unit 41 having a CPU, a ROM, a RAM, a storage unit 43 such as an HDD for storing various application programs and various data, and is connected to the network 12 and communicates with the management server 20 and the like. And a communication unit 46. The vendor terminal 40 receives various instructions from the vendor from the input unit 47 such as a keyboard and a mouse. Further, the vendor terminal 40 displays various information such as a registration screen for registering the module data of the module to be provided in the marketplace MP on the display unit 48 such as a display. Further, the vendor terminal 40 is connected to a printer 49 such as an inkjet printer. When the printer 49 inputs a print command from the vendor terminal 40 or the like, the printer 49 prints a character, an image, a 2D code, or the like on a sheet based on the print command.

Like the vendor terminal 40, the customer terminal 50 includes a control unit 51, a storage unit 53, and a communication unit 56. The communication unit 56 communicates with the control device 68 of the work system 60 described later via the network 12 or the like. Various instructions and the like from the customer are input to the customer terminal 50 from the input unit 57 such as a keyboard and a mouse. Further, the customer terminal 50 displays various information such as the top screen (purchase screen) of the marketplace MP, the simulation model MD, and the simulation execution result on the display unit 58 such as a display.

Here, an example of the work system 60 in which modules that can be purchased at the marketplace MP are combined will be described. For example, the work system 60 can be configured as a system that performs a predetermined work with the robot 61, and in the example of FIG. 3, a substrate transfer device 66 and a feeder 67 are provided in addition to the robot 61. An example of the predetermined work is, for example, a mounting work in which the robot 61 picks up a work such as a mechanical component or an electronic component and mounts it on the substrate S. The robot 61 includes a vertical articulated robot arm 62 and a control device 68 that controls the entire system including the operation of the robot arm 62. Further, an end effector 63 as a work tool is detachably attached to the tip end link of the robot arm 62, and a camera 64 for picking up an image and an illumination 65 such as a ring light arranged coaxially with the camera 64 are attached. Has been. The end effector 63 may be an electromagnetic chuck, a mechanical chuck, a suction nozzle, or the like. The substrate transfer device 66 transfers the substrate S by a pair of belt conveyors. The feeder 67 is configured as a tape feeder that feeds out a tape containing a plurality of works at predetermined intervals. Note that the feeder 67 is not limited to a tape feeder, and may be a tray feeder or the like that supplies a tray on which a plurality of works are arranged. The control device 68 is composed of a CPU, a ROM, a HDD, a RAM, and the like, and stores, in addition to the operation program of the robot 61, a system program for managing the entire work system 60 and the like. Although not shown, the operation program of the board transfer device 66 is stored in the PLC (Programmable Logic Controller) of the board transfer device 66, and the operation program of the feeder 67 is stored in the PLC of the feeder 67. The robot 61 (robot arm 62), the end effector 63, the camera 64, the illumination 65, the substrate transfer device 66, and the feeder 67 that configure the work system 60 are referred to as modules.

The storage unit 23 of the management server 20 stores a module DB (database) 30 shown in FIG. 4, an introduction record DB 35, a vendor DB 37, and a customer DB 39. Although not shown in the figure, the vendor DB 37 has registered therein the names of the vendors who have been certified and registered, vendor IDs unique to each vendor, contact information such as email addresses and addresses, and information on the types of modules provided by the vendors. There is. Further, although not shown, the customer DB 39 stores the name of the customer who has been authenticated and registered, a customer ID unique to each customer, contact information such as an email address and an address, and a purchase history of the customer. In the introduction record DB 35, information on each module introduced to the customer is registered in association with the customer ID. In addition, when the modules purchased in the marketplace MP constitute a work system, a simulation using a model MD constructed by those modules is usually executed, and the customer confirms the result of the simulation before each module. Make a purchase.

The module DB 30 is for registering module data and the like registered by the vendor from the vendor terminal 40 via the registration screen, and a plurality of module data 31 is registered for each module type. For example, as shown in FIG. 4, the plurality of module data 31 are classified and registered into robot data 30A, end effector data 30B, feeder data 30C, conveyor data 30D, camera data 30E, and illumination data 30F. Module data of the robot arm 62 (robot A) and module data of other various robots B to D are registered in the robot data 30A. The various robots may be of a horizontal articulated type or a parallel link type other than the vertical articulated type. Each of these module data includes shape data such as three-dimensional CAD data of the robots A to D, an operation program, a module ID, and specifications. Similarly, the end effector data 30B includes shape data, module IDs, specifications of the end effector 63 (end effector A) that can be attached to and detached from the robot A, and other types of end effectors BD that can be attached to and detached from the robots A to D. Module data including, etc. is registered. Further, module data including shape data of the feeder 67 (feeder A) and other types of feeders B to D, operation programs, module IDs, specifications, etc. are registered in the feeder data 30C. In the conveyor data 30D, module data including shape data, operation programs, module IDs, specifications, etc. of the conveyor A as the board transfer device 66 and other types of conveyors is registered. In the camera data 30E, module data including shape data, a module ID, specifications, etc. of the camera 64 (camera A) and other types of cameras B to D are registered. In the illumination data 30F, module data including shape data of the illumination 65 (illumination A) and other types of illuminations B to D, module IDs, specifications, and the like are registered. Although not shown, the module DB 30 is also registered with module data including shape data and physical property data of a typical work to be worked. The work module data may be registered by a vendor or an administrator who receives a request from a customer, and is used in a simulation using the model MD.

On the top screen of the marketplace MP displayed on the customer terminal 50 or the like, it is possible to make purchase requests and browses for these modules, purchase requests and browses for various tools, and log in to the customer's My Page. As shown in Fig. 2, on the top screen, icons for each type of module such as robots, end effectors, feeders, conveyors, cameras (including lighting here), tool icons, purchase button, login to My Page Buttons etc. are displayed. When the customer operates (clicks) the purchase button by inputting the operation using the input unit 57 and then selects the icon of the desired module, a module selection screen (not shown) for displaying a list of applicable types of module data is displayed. To be done. For example, when the customer selects the robot icon, each module data 31 of the robots A to D is displayed in a list, and the customer can select and purchase a required module from the list. The module data displayed as a list is registered in the module DB 30. When the customer operates the purchase button and then selects a tool icon, a tool selection screen (not shown) for displaying a list of various tools in a selectable manner is displayed. Customers can select and purchase the necessary tools from among them. As various tools, an analysis tool that collects and analyzes information such as the work status of each module and the frequency of occurrence of abnormalities, a proposal tool that proposes improvement plans such as module changes based on the analysis results, and an efficient module Examples include layout tools that perform layout. The customer can select the module icon or the tool icon without clicking the purchase button to browse the contents of the listed modules or tools. Further, when the customer logs in to My Page, the customer can check the purchase history of the module, the content and change history of the module to be introduced, the contact information from the management server 20 and the vendor, and the like.

Next, the processing of the equipment introduction support system 10 thus configured, particularly the processing when the vendor registers the module in the marketplace MP and the processing when the module manufactured by the vendor is delivered to the customer will be described. FIG. 5 is a sequence diagram showing an example of processing of the management server 20, the vendor terminal 40, and the customer terminal 50. First, the vendor designs the module on the vendor terminal 40 (S100), and requests the management server 20 from the vendor terminal 40 to authenticate the module together with specifications such as the type and model of the module, an image of the module, and the like (S110). For example, when the vendor designs the end effector as a module, information indicating that the type of the module is the end effector, specifications including information on the model number appropriately determined by each vendor, etc. are transmitted from the vendor terminal 40 to the management server 20. ..

When the vendor requests authentication, the control unit 21 of the management server 20 sets a module ID, which is unique information for each predetermined classification of the module, and notifies the vendor terminal 40 (S200). The predetermined classification may be determined based on the type of module, vendor, model, or the like. For example, the predetermined classification is whether the module type is a robot, an end effector, a feeder, a conveyor, a camera, or an illumination, and if the end effector is an electromagnetic chuck, a mechanical chuck, or a suction nozzle. It may be determined based on. Further, the predetermined classification may be determined based on which vendor and what type of vendor. Next, the control unit 21 associates the set module ID with the specifications of the module and registers them in the module data 31 of the module DB 30 (S210). Here, the end effector data 30B will be described as the module data 31. FIG. 6 is an explanatory diagram showing an example of the end effector data 30B. As shown in the figure, module IDs are registered in the respective end effector data 30B of the end effectors A, B,... Corresponding to the specifications of the end effectors. The specifications include information such as the model number of the module, the size and weight of the end effector, the material, the chucking force (suction force), the maximum size that can be chucked, and the operating unit. Further, although not shown in the figure, module IDs and specifications thereof are also registered in association with each other for module data other than the end effector. The modules thus registered can be selected and purchased by the customer on the marketplace MP. When the customer selects a module in the marketplace MP, the simulation unit 22 constructs a model MD using those module data (see FIG. 2) and performs a simulation. As shown in FIG. 2, the model MD includes the module ID of each module. After performing the simulation, the simulation unit 22 stores the simulation result and the module ID of each module that constructs the model MD in the introduction record DB 35 in association with the customer ID.

Meanwhile, the vendor terminal 40 waits until the manufacturing of the designed module starts (S120). The vendor may start manufacturing the module when the customer makes a purchase request via the module selection screen of the marketplace MP, or the module may be manufactured based on a predetermined production plan regardless of the purchase request. The production of may be started. When the manufacturing of the module is started, the vendor terminal 40 displays the serial number. Is set and transmitted to the management server 20 (S130). Serial No. May be set in advance according to a manufacturing order or the like before the start of manufacturing. Further, the vendor terminal 40 uses the serial number as the serial number when manufacturing the module. And is stored in the storage unit 43 in association with (S140). The vendor terminal 40 uses the serial number. The manufacturing history may be transmitted to the management server 20, and the management server 20 may store them in the storage unit 23. When the manufacturing of the module is completed, the vendor terminal 40 determines the module ID and serial number of the module. The printer 49 is caused to issue a 2D code C such as a barcode or a QR code (registered trademark) indicating S (S150). The printer 49 prints and issues the 2D code C on a sticker sheet, and the vendor attaches the sticker sheet to the outer surface of the module. Subsequently, the vendor terminal 40 instructs the customer to ship the module to which the 2D code C is attached (S160). FIG. 7 is an explanatory diagram showing an example of the end effector 63 provided with the 2D code C. The end effector 63 of FIG. 7 includes a main body 63a and a pair of chuck claws 63b that can be opened and closed, and the 2D code C is attached to the side surface of the main body 63a. In this way, the module ID and serial number. The module is shipped to the customer in a state in which the 2D code C indicating the is attached to the outer surface.

When the module shipped from the vendor arrives, the customer terminal 50 captures an image of the 2D code C of the module (S300), and the module ID and serial number. And are acquired (S310). In S300 and S310, the customer terminal 50 causes the camera 64 of the work system 60 to image the 2D code C, and the control device 68 reads the module ID and serial number. Can be obtained by communication. Alternatively, the customer terminal 50 causes the customer to read the 2D code C using a handheld code reader or the like, and the module ID and serial number. May be obtained. Next, the customer terminal 50 uses the acquired module ID and serial number. Is notified to the management server 20 (S320).

The control unit 21 of the management server 20 receives the module ID and serial number from the customer terminal 50. When it receives the notification of, it is confirmed that the module matches the module of the model MD when the simulation is executed (S230). Here, FIG. 8 is an explanatory diagram showing an example of the introduction record DB 35. As described above, the information of each module that constructs the model MD is stored in the introduction record DB 35 in association with the customer ID. For example, at the timing when the customer confirms that there is no problem in the result of the simulation using the model MD, as shown in FIG. 8, each module ID such as the robot ID, the end effector ID, the feeder ID, and the conveyor ID. Is stored in association with the customer ID. In addition, at the timing of registering each module ID, it is before delivery of the module and the serial number. Since the serial number is not decided, the serial number. Is left blank. In the example of FIG. 8, the serial number of the end effector having the customer ID “CU**B” is set. Is left blank. Other serial numbers. Has been registered in the next S240.

In S230, the control unit 21 can confirm that the modules match by referring to the module ID of each module in the introduction result DB 35. When the control unit 21 confirms that the modules match, the serial No. is assigned to each module ID in the introduction result DB 35. Are registered in association with each other (S240). Therefore, for example, when the end effector is delivered to the customer with the customer ID “CU**B”, when the control unit 21 confirms that the module IDs match each other, the end effector of the end effector is displayed in a blank space in FIG. Serial No. Will be registered. Note that the control unit 21 notifies the customer terminal 50 that a different module has been delivered to the customer if it cannot be confirmed in S230 that the two match. In this way, the control unit 21 can confirm that the same module as the model MD for which the simulation has been executed has been delivered to the customer.

Here, the correspondence relationship between the constituent elements of the present embodiment and the constituent elements of the present disclosure will be clarified. The work system 60 of this embodiment corresponds to a work system, the equipment introduction support system 10 corresponds to a module management system, the storage unit 23 of the management server 20 corresponds to a storage unit, and the management server 20 that executes S200 and S210. The control unit 21 of 1 corresponds to the management unit, and the 2D code C corresponds to the identifier. A combination of the camera 64 and the control device 68 or a hand-held code reader corresponds to the recognition device.

The equipment introduction support system 10 described above sets a module ID (unique information) for each module type, and stores the module ID in the module DB 30 of the storage unit 23 in association with the module specifications. The 2D code C (identifier) associated with the module ID is provided on the module so that it can be recognized from the outside. As a result, even if the module ID cannot be acquired due to the communication between the modules, the module ID and the specifications associated therewith can be acquired. Therefore, it is possible to easily confirm the type and specifications of the module. Further, it is possible to prevent the customer from mistakenly introducing a module different from the module used when the simulation was executed. In addition, if the marketplace MP adopts a mode in which the usage fee of the module is charged according to the number and type of modules installed in the customer, usage time, etc., the customer should properly declare the module. You can charge appropriately. Further, since the management server 20 can appropriately grasp the module configuration of the customer, it becomes possible to collect data such as the usage status of the module and analyze the collected data.

-In addition to the module ID, the 2D code C is the serial number of the module. Is associated with. Therefore, from the 2D code C, the module serial number. It is also possible to confirm the manufacturing record of the module by acquiring That is, the vendor terminal 40 displays the module manufacturing record as the serial number. The module ID and the serial number are stored in the storage unit 43 in association with the module ID. It is possible to check the manufacturing record from and investigate the relationship with abnormalities. Further, for example, various tools such as an analysis tool are serial No. notified by the customer. It may be possible to perform analysis on the condition that the registration is performed. By doing this, the serial No. by the customer can be changed. Can be prompted for reading or notification.

Needless to say, the present disclosure is not limited to the above-described embodiments and can be implemented in various modes as long as they are within the technical scope of the present disclosure.

For example, in the above-described embodiment, the 2D code C has the module ID and the serial number. Although and are associated with each other, the invention is not limited to this, and at least the module ID may be associated with each other. In addition, the serial number. Besides, all or part of the specifications may be associated. Further, information regarding the date of manufacture of the module, the date of delivery, the date of start of use by the customer, the period of use by the customer, and the like may be associated. In addition, as the information about the module, information about the operation program of the module, setting parameters, etc., maintenance method, consumable parts, replacement parts information, etc. may be associated with the 2D code C. Then, the customer may recognize the information by reading the 2D code C using a tablet or a smartphone. In this way, when the module breaks down or the parts of the module are replaced, the customer can easily obtain the necessary information and take prompt action.

In the above-described embodiment, the module ID and serial number. Although the 2D code C associated with and is attached to the module, the present invention is not limited to this, and any identification element such as the 2D code C may be provided on the module. For example, the identification body may be provided by directly printing or engraving on the module.

In the embodiment described above, the 2D code C is provided for each module, but the present invention is not limited to this. For example, one 2D code C may be provided in any of the plurality of modules, and the plurality of modules may be collectively managed using the 2D code C. In that case, as a plurality of modules, a combination module used in combination may be collectively managed. FIG. 9 is an explanatory diagram showing an example of a combination module. In FIG. 9, as the combination module, a main body 63a of the end effector and a pair of chuck claws 63b (1), (2), and (3) that are replaceably attached to the main body 63a are illustrated. It is difficult to provide the 2D code C on the chuck claws 63b (1), (2), and (3) due to their small size and surface properties unsuitable for sticking sticker sheets. There is. For this reason, the chuck claws 63b (1), (2), and (3) are provided with the 2D code C in their respective storage bags P and storage boxes. The customer causes the camera 64 of the work system 60, a handheld code reader, or the like to read the 2D code C of the accommodation bag P, and causes the customer terminal 50 to read the module ID and the serial number. Can be obtained.

FIG. 10 is an explanatory diagram showing an example of changing the combination of modules, and FIG. 11 is an explanatory diagram showing an example of the module combination information 36. FIG. 10A shows a case where the main body 63a and the chuck claw 63b(1) are combined, and FIG. 10B shows a case where the main body 63a and the chuck claw 63b(2) are combined. In this modification, the customer causes the camera 64, a code reader, or the like to read the 2D code C of the accommodation bag P each time the combination of modules is changed. Further, the customer terminal 50 uses the acquired module ID and serial number. Is transmitted to the management server 20. The control unit 21 of the management server 20 receives the received module ID and serial number. The module combination information 36 in the introduction record DB 35 is updated based on In the case of FIG. 10A, the combination information 36 includes the module ID of the main body 63a of the end effector, the module ID of the chuck claw 63b(1), and the serial number. Are stored in association with each other (see FIG. 11A). In the case of FIG. 10B, the combination information 36 includes the module ID of the main body 63a of the end effector, the module ID of the chuck claw 63b(2) and the serial number. Are stored in association with each other (see FIG. 11B). Therefore, the customer reads the 2D code C provided on the main body 63a and inquires of the management server 20 based on the module ID of the main body 63a, so that the management server 20 can send the module ID of the chuck claw 63b as well as the main body 63a. Or serial No. Can be obtained.

In this way, the management server 20 of the modified example collectively manages the module IDs of the two modules of the main body 63a (first module) and the chuck claw 63b (second module) of the end effector by the module ID of the main body 63a. be able to. Therefore, the module can be properly managed without the vendor providing the module ID on the chuck claw 63b. Further, when the chuck claw 63b is changed to a different one, the control unit 21 of the management server 20 changes the module ID of the chuck claw 63b stored in association with the module ID of the main body 63a to the module of the changed chuck claw 63b. Update to ID. Therefore, the information of the chuck claw 63b can be easily corrected by updating the information of the storage unit 23 without the customer reattaching the 2D code C provided on the main body 63a.

In this modification, the combination of one module provided with the 2D code C and one module not provided with the 2D code C is collectively managed, but the present invention is not limited to this, and the 2D code C is provided. The module ID and the serial number in the combination of the module No. 1 and two or more modules not provided with the 2D code C. May be collectively managed. For example, when two sets of chuck claws are attached to the main body of the end effector to form a combination of three modules in total, the module ID and the serial number. May be collectively managed. Alternatively, it may be applied to the management of two or more feeders that respectively supply the component types used in a combination of two or more. Further, this modification may be applied to one in which the vendor confirms in advance the error or accuracy of the combination of two or more modules, and collectively manages the combination of the modules that secures the predetermined accuracy.

In this modification, the modules to be collectively managed are managed by updating the module combination information 36 stored in the storage unit 23 of the management server 20, but the present invention is not limited to this. For example, each time the chuck claw 63b is replaced, the customer may issue the 2D code C by the printer and re-attach it to the main body 63a of the end effector.

In the above-described embodiments and modified examples, the 2D code C such as a barcode and a QR code (registered trademark) is provided in the module, but the present invention is not limited to this, and RFID (Radio Frequency Identification) capable of reading and writing various kinds of information. ) An IC tag such as a tag may be provided in the module and the information in the tag may be recognized by the tag recognition device. That is, the identification body may be provided with a code or an IC tag as a holding unit that holds the identification information. Note that the IC tag may not be exposed on the surface as long as information can be read and written from the outside.

In the above-described embodiment, the vendor attaches the 2D code C to the module and sends the module to the customer, but the present invention is not limited to this. For example, the vendor may send the module to the customer without attaching the 2D code C and notify the customer of the information of the 2D code C, and the customer may issue the 2D code C by the printer and attach it to the module. .. Alternatively, the vendor may ship the 2D code C separately from the module. Alternatively, the customer may be notified of the information of the 2D code C not from the vendor but from the management server 20.

Although the working system 60 including a plurality of modules including the robot 61 is illustrated in the above-described embodiment, the working system is not limited to this, and the working system may be a system including a plurality of modules and includes the robot 61. It may be omitted.

Here, the module management system of the present disclosure may be configured as follows. For example, in the module management system of the present disclosure, the identification body may be associated with each serial number of the module in addition to the unique information. In this way, by recognizing the identification body provided on the module, the serial number of the module can be acquired and the manufacturing history of the module can be confirmed, so that the module can be managed more appropriately. ..

In the module management system of the present disclosure, as the module, a first module provided with the identifying body and one or more second modules used in combination with the first module and not provided with the identifying body are provided. The management unit stores the identification information of the second module in the storage unit in association with the identification information of the first module, instead of the identification unit being provided in the second module. It may be allowed to. With this configuration, the unique information of each of the first module and the second module can be collectively managed by the identifier of the first module. Therefore, for example, even if the second module has a size or shape in which it is difficult to provide the identification body, the module can be appropriately managed.

In the module management system of the present disclosure, when the management unit is changed to the different second module in the combination, the second unit is stored in the storage unit in association with the unique information of the first module. The unique information of the module may be updated to the unique information of the second module after the change. In this way, the information of the second module can be easily corrected by updating the information of the storage unit without changing the identifier provided in the first module.

The present disclosure can be used for the module management system manufacturing industry and the like.

10 facility introduction support system, 12 network, 20 management server, 21, 41, 51 control unit, 22 simulation unit, 23, 43, 53 storage unit, 26, 46, 56 communication unit, 28, 47, 57 input unit, 29 , 48, 58 display unit, 30 module DB, 30A robot data, 30B end effector data, 30C feeder data, 30D conveyor data, 30E camera data, 30F lighting data, 31 module data, 35 installation record DB, 36 module combination information, 37 vendor DB, 39 customer DB, 40 vendor terminal, 49 printer, 50 customer terminal, 60 working system, 61 robot, 62 robot arm, 63 end effector, 63a main body, 63b, 63b (1) to (3) chuck claw, 64 cameras, 65 lighting, 66 board transfer device, 67 feeder, 68 control device, C2D code, MD model, MP market place, P accommodation bag, S board.

Claims

A module management system that manages multiple types of modules that make up the work system,
A storage unit for storing information,
A management unit that sets unique information for each predetermined classification of the module, and stores the unique information in the storage unit in association with the specification of the module;
Equipped with
A module management system in which at least an identifier associated with the unique information is provided in the module so that the identifier can be recognized from the outside by a recognition device.
The module management system according to claim 1, wherein
The module management system in which the identifier is associated with each serial number of the module in addition to the unique information.
The module management system according to claim 1 or 2, wherein
As the module, a first module provided with the identification body, and one or more second modules used in combination with the first module and not provided with the identification body,
The management unit stores the identification information of the second module in the storage unit in association with the identification information of the first module, instead of the identification unit provided in the second module. system.
The module management system according to claim 3, wherein
When the management unit is changed to the different second module in the combination, the management unit changes the unique information of the second module stored in the storage unit in association with the unique information of the first module. A module management system for updating the unique information of the second module later.