JP7383001B2 - module management system - Google Patents

Description

This specification discloses a module management system.

Conventionally, in a robot with a detachable forearm including a hand such as an end effector, when the forearm is attached to the robot, a control unit in the forearm and a control device of the robot exchange information necessary for controlling the forearm. something is proposed. For example, in Patent Document 1, a control unit in the forearm stores identification information for specifying the type of forearm, and when the forearm is attached to a robot, the identification information is transmitted to the robot's control device. do. Further, upon receiving the identification information, the robot control device reads forearm information corresponding to the identification information from among the various types of forearm information stored in advance and performs various settings.

Japanese Patent Application Publication No. 2016-190282

For modules that are communicably attached to the robot, such as the above-mentioned forearm, the robot's control device can acquire identification information. However, in a system including a robot, there are some modules that cannot communicate with the robot, so the robot control device may not be able to acquire the identification information of all modules. In this case, for example, it becomes difficult to confirm whether the module configuration of the system simulated before installation matches the module configuration of the system actually installed, and the system may be operated with an incorrect module configuration.

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

The present disclosure has taken the following measures to achieve the above-mentioned main objective.

The module management system of the present disclosure includes:
A module management system that manages multiple types of modules that constitute a work system,
a storage unit that stores 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 specifications of the module;
Equipped with
The gist is that at least an identifier associated with the unique information is provided on the module so that it can be recognized by a recognition device from the outside.

In the module management system of the present disclosure, unique information for each predetermined classification of modules is set, and the unique information is stored in the storage unit in association with the specifications of the module. Furthermore, at least an identifier associated with the unique information is provided on the module so that it can be recognized by a recognition device from the outside. As a result, even if the unique information of a module cannot be acquired due to communication between modules, it is possible to acquire the unique information of the module and the specifications associated with the unique information by recognizing the identifier provided on the module. can. Therefore, it is possible to easily classify modules and check specifications, so that modules can be managed more appropriately with a simple configuration. Note that the predetermined classification may be any classification based on module type, vendor, model, or the like. Further, the identifier may be provided as an identification code such as a 2D code that can be recognized by a code recognition device or an identification tag such as an IC tag that can be recognized by a tag recognition device.

FIG. 1 is a configuration diagram showing an outline of the configuration of an equipment introduction support system 10. An explanatory diagram showing an outline of the marketplace MP. FIG. 2 is a configuration diagram showing an outline of the configuration of a work system 60. FIG. An explanatory diagram showing an example of module DB30. FIG. 4 is a sequence diagram showing an example of processing by a management server 20, a vendor terminal 40, and a customer terminal 50. An explanatory diagram showing an example of module data 30B of an end effector. An explanatory diagram showing an example of an end effector 63 provided with a 2D code C. An explanatory diagram showing an example of an introduction record DB 35. An explanatory diagram showing an example of a combination module. FIG. 3 is an explanatory diagram showing an example of how a combination of modules is changed. FIG. 3 is an explanatory diagram showing an example of module combination information 36;

Next, embodiments for carrying out the present disclosure will be described with reference to the drawings.

FIG. 1 is a block diagram schematically showing the structure of the equipment installation support system 10 of this embodiment, FIG. 2 is an explanatory diagram schematically showing the marketplace MP, and FIG. 3 is a schematic diagram showing the structure of the work system 60. FIG. As shown in FIGS. 1 and 2, the equipment installation support system 10 includes a management server 20 that manages a marketplace MP for customers to purchase various types of equipment and equipment (hereinafter referred to as modules) provided by vendors. . 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. Although FIG. 1 shows one vendor terminal 40 and one customer terminal 50, a plurality of them are actually connected.

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

The vendor terminal 40 is connected to a control unit 41 including a CPU, ROM, RAM, etc., a storage unit 43 such as an HDD that stores various application programs and data, and a network 12 to communicate with the management server 20 and the like. A communication section 46 is provided. The vendor terminal 40 receives various instructions from the vendor through an 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 module data of a module to be provided in the marketplace MP on a display unit 48 such as a display. Further, the vendor terminal 40 is connected to a printer 49 such as an inkjet printer, for example. When a print command is input from the vendor terminal 40 or the like, the printer 49 prints characters, images, 2D codes, etc. on paper based on the print command.

Like the vendor terminal 40, the customer terminal 50 includes a control section 51, a storage section 53, and a communication section 56. The communication unit 56 communicates with a control device 68 of a work system 60, which will be described later, via the network 12 or the like. The customer terminal 50 receives various instructions from the customer through an 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 results on a display unit 58 such as a display.

Here, an example of a work system 60 that combines modules that can be purchased on the marketplace MP will be described. For example, the work system 60 can be configured as a system in which a robot 61 performs a predetermined work, and in the example of FIG. 3, it includes a substrate transfer device 66 and a feeder 67 in addition to the robot 61. An example of the predetermined work is 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 board S. The robot 61 includes a vertically articulated robot arm 62 and a control device 68 that controls the entire system including the operation of the robot arm 62. Furthermore, an end effector 63 as a work tool is removably attached to the tip link of the robot arm 62, and a camera 64 for capturing images and a lighting device 65 such as a ring light arranged coaxially with the camera 64 are attached. It is being Note that examples of the end effector 63 include an electromagnetic chuck, a mechanical chuck, and a suction nozzle. The substrate transport device 66 transports the substrate S using 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 that feeds a tray on which a plurality of works are arranged. The control device 68 is composed of a CPU, ROM, HDD, RAM, etc., and stores a system program for managing the entire work system 60 in addition to the operation program of the robot 61. Further, although not shown, the operation program for the substrate transfer device 66 is stored in a PLC (Programmable Logic Controller) of the substrate transfer device 66, and the operation program for the feeder 67 is stored in the PLC of the feeder 67. The robot 61 (robot arm 62), end effector 63, camera 64, illumination 65, substrate transfer device 66, and feeder 67 that constitute such a work system 60 are each referred to as a module.

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 vendors who have been certified and registered, vendor IDs unique to each vendor, contact information such as e-mail addresses and addresses, and information on the types of modules provided by the vendors. There is. Further, although not shown in the figure, the customer DB 39 stores the names of customers who have been authenticated and registered, a customer ID unique to each customer, contact information such as e-mail address and address, customer purchase history, and the like. In the installation record DB 35, information about each module installed by a customer is registered in association with a customer ID. Note that when modules purchased from the Marketplace MP constitute a work system, a simulation is normally performed using a model MD constructed with those modules, and the customer confirms the simulation results before purchasing each module. Make a purchase.

The module DB 30 is used to register module data registered by a vendor via a registration screen from the vendor terminal 40, and a plurality of module data 31 are registered for each type of module. The plurality of module data 31 is registered, for example, as shown in FIG. 4, divided into robot data 30A, end effector data 30B, feeder data 30C, conveyor data 30D, camera data 30E, and illumination data 30F. In the robot data 30A, module data of the robot arm 62 (robot A) and module data of various other robots B to D are registered. Various types of robots may be of the horizontal multi-joint type, parallel link type, etc. other than the vertical multi-joint type. These module data include shape data such as three-dimensional CAD data of the robots A to D, operation programs, module IDs, specifications, etc., respectively. Similarly, the end effector data 30B includes the shape data, module ID, and specifications of the end effector 63 (end effector A) that can be attached to and detached from robot A and other types of end effectors B to D that can be attached to and detached from robots A to D. Module data including such items are registered. Furthermore, module data including shape data, operation programs, module IDs, specifications, etc. of the feeder 67 (feeder A) and other types of feeders B to D is 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 substrate transfer device 66 and other types of conveyors is registered. In the camera data 30E, module data including shape data, module ID, specifications, etc. of the camera 64 (camera A) and other types of cameras B to D is registered. In the lighting data 30F, module data including shape data, module ID, specifications, etc. of the lighting 65 (lighting A) and other types of lighting B to D is registered. Although not shown, the module DB 30 also registers module data including shape data, physical property data, etc. of typical workpieces to be worked on. The module data of the workpiece may be registered by a vendor or by an administrator who has received a request from a customer, and is used in a simulation using a model MD.

On the top screen of the marketplace MP displayed on the customer terminal 50 or the like, it is possible to request and view the purchase of these modules, request and view the purchase of various tools, and log in to the customer's my page. As shown in Figure 2, the top screen includes icons for each type of module, such as robots, end effectors, feeders, conveyors, cameras (including lighting here), tool icons, purchase buttons, and login to my page. Buttons, etc. are displayed. When the customer operates (clicks) the purchase button through operation input using the input unit 57 and then selects the icon of the desired module, a module selection screen (not shown) is displayed that displays a list of module data of the corresponding type in a selectable manner. be done. For example, when a customer selects a robot icon, a list of module data 31 for robots A to D is displayed, and the customer can select and purchase a required module from among them. Note that the module data displayed in a list is registered in the module DB 30. Further, when a customer operates a purchase button and then selects a tool icon, a tool selection screen (not shown) is displayed that displays a list of various tools for selection. Customers can select and purchase the tools they need. The various tools include an analysis tool that collects and analyzes information such as the work status of each module and the frequency of abnormalities, a proposal tool that proposes improvements such as module changes based on the analysis results, and a proposal tool that proposes improvements such as module changes based on the analysis results. Examples include layout tools that perform layout. Note that the customer can select the module icon or tool icon to view the contents of the displayed module or tool without clicking the purchase button. Furthermore, when a customer logs in to their My Page, they can check the purchase history of modules, the contents and change history of modules scheduled to be introduced, communications from the management server 20 and vendors, and the like.

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

When the controller 21 of the management server 20 receives a request for authentication from the vendor, it sets a module ID, which is unique information for each predetermined classification of modules, and notifies the vendor terminal 40 (S200). The predetermined classification may be determined based on the type, vendor, model, etc. of the module. For example, the predetermined classification is whether the type of module is a robot, end effector, feeder, conveyor, camera, or lighting, or if it is an end effector, whether it is an electromagnetic chuck, mechanical chuck, or suction nozzle. It is sufficient if it is determined based on the following. Furthermore, the predetermined classification may be determined based on which vendor or which type of vendor it is. 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, as the module data 31, end effector data 30B will be used for explanation. FIG. 6 is an explanatory diagram showing an example of the end effector data 30B. As shown in the figure, each module ID is registered in each end effector data 30B of end effectors A, B, . . . in association with the specifications of the end effector. In addition to the module model number, the specifications include information such as the end effector's size, weight, material, chuck force (adsorption force), maximum chuckable size, and operating parts. Further, although not shown, module IDs and their specifications are similarly registered in association with module data other than end effectors. The modules thus registered can be selected and purchased by the customer on the marketplace MP. Note that when the customer selects a module on the marketplace MP, the simulation unit 22 constructs a model MD using the module data (see FIG. 2) and performs a simulation. As shown in FIG. 2, the model MD includes the module ID of each module. When the simulation unit 22 performs the simulation, the simulation unit 22 stores the results together with the module ID of each module that constructs the model MD in the introduction record DB 35 in association with the customer ID.

On the other hand, the vendor terminal 40 waits for the manufacturing of the designed module to start (S120). The vendor may start manufacturing the module when a customer makes a purchase request via the module selection screen of the Marketplace MP, or the vendor may start manufacturing the module based on a predetermined production plan regardless of whether there is a purchase request. You may start manufacturing. When manufacturing of a module is started, the vendor terminal 40 receives serial number information such as serial number information of the module. is set and transmitted to the management server 20 (S130). Serial No. may be set in advance according to the manufacturing order or the like before starting manufacturing. The vendor terminal 40 also records the manufacturing results of the module at the time of manufacturing the serial number. The information is stored in the storage unit 43 in association with (S140). Note that the vendor terminal 40 has a serial number. and the manufacturing results 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 receives 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 QR code (registered trademark), which indicates the following (S150). The printer 49 prints and issues the 2D code C on a sticker sheet, and the vendor affixes the sticker sheet to the outer surface of the module. Next, 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 in FIG. 7 includes a main body 63a and a pair of chuck claws 63b that can be opened and closed, and a 2D code C is pasted on the side surface of the main body 63a. In this way, the module ID and serial number. The module is shipped to the customer with the 2D code C indicating the 2D code C affixed to the outside surface.

When the module shipped from the vendor arrives, the customer terminal 50 images the 2D code C of the module (S300), and records the module ID and serial number. (S310). In S300 and S310, the customer terminal 50 causes the camera 64 of the work system 60 to take an image of the 2D code C, and the control device 68 reads the module ID and serial number from the image. can be obtained through communication. Alternatively, the customer terminal 50 allows the customer to read the 2D code C using a hand-held code reader, etc., and obtains the module ID and serial number. may be obtained. Next, the customer terminal 50 receives 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 receiving the notification, it is confirmed that the module matches the module of the model MD when the simulation was executed (S230). Here, FIG. 8 is an explanatory diagram showing an example of the introduction record DB 35. As described above, information on 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 are no problems with the simulation results using the model MD, each module ID such as the robot ID, end effector ID, feeder ID, conveyor ID, etc. is stored in association with the customer ID. Note that the timing for registering each module ID is before the module is delivered, and the serial number. Since the serial number has not been determined, is left blank. In the example shown in FIG. 8, the serial number of the end effector with the customer ID "CU**B". is left blank. Other serial numbers. is registered in the next step 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 record DB 35. When the control unit 21 confirms that the modules match, the control unit 21 adds the serial number to each module ID in the installation record DB 35. are associated and registered (S240). Therefore, for example, when an end effector is delivered to a customer whose customer ID is "CU**B", when the control unit 21 confirms that the module IDs match, the end effector is displayed in the blank space in FIG. Serial No. will be registered. Note that if the control unit 21 cannot confirm that they match in S230, it notifies the customer terminal 50 that different modules have been delivered to the customer. In this way, the control unit 21 can confirm that the same module as the model MD on which the simulation was executed has been delivered to the customer.

Here, the correspondence between the components of this embodiment and the components 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 executes S200 and S210. The control unit 21 corresponds to a management unit, and the 2D code C corresponds to an identifier. Further, 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 type of module, and stores the module ID in the module DB 30 of the storage unit 23 in association with the module specifications. Further, a 2D code C (identifier) associated with the module ID is provided on the module so that it can be recognized from the outside. Thereby, even if the module ID cannot be acquired due to communication between modules, the module ID and the specifications associated therewith can be acquired. Therefore, the type and specifications of the module can be easily confirmed. Furthermore, it is possible to prevent the customer from mistakenly installing a module different from the module used when the simulation was executed. In addition, if the marketplace MP adopts a system that charges a module usage fee according to the number, type, usage time, etc. of modules installed by the customer, it is necessary to have the customer properly declare the modules. You can charge appropriately. Further, since the management server 20 can appropriately grasp the customer's module configuration, it is possible to collect data such as the usage status of modules and analyze the collected data.

In addition to the module ID, the 2D code C also includes the module serial number. is associated with. Therefore, from the 2D code C, the module serial number. You can also check the manufacturing results of the module by obtaining the information. That is, the vendor terminal 40 records the manufacturing results of the module by serial number. Since the module ID and serial number are stored in the storage unit 43 in association with the serial number, if any abnormality occurs in the module, the vendor can store the module ID and serial number. You can check the manufacturing results and investigate the relationship with the abnormality. In addition, various tools such as analysis tools use the serial number notified by the customer. It may also be possible to analyze the information subject to registration. In this way, the customer's serial number. You can prompt for reading and notifications.

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

For example, in the embodiment described above, the 2D code C includes the module ID and the serial number. However, the present invention is not limited to this, and it is sufficient that at least module IDs are associated. Also, serial no. In addition, all or part of the specifications may be associated. Further, information regarding months and dates, such as the manufacturing date and delivery date of the module, the date when the customer started using it, and the period of use by the customer, may be associated. In addition, as information regarding the module, information regarding the operating program and setting parameters of the module, information on maintenance methods, consumable parts, replacement parts, etc. may be associated with the 2D code C. The customer may then read the 2D code C using a tablet, smartphone, or the like to recognize this information. In this way, when a module breaks down or parts of the module are replaced, the customer can easily obtain necessary information and take prompt action.

In the embodiment described above, the module ID and serial number. Although the 2D code C associated with the 2D code C is pasted on the module, the present invention is not limited to this, and any type of identifier such as the 2D code C may be provided on the module. For example, the identifier may be provided by directly printing or marking on the module.

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

FIG. 10 is an explanatory diagram showing an example of how the combination of modules is changed, 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, each time the combination of modules is changed, the customer causes the camera 64, code reader, or the like to read the 2D code C on the storage bag P. The customer terminal 50 also receives the acquired module ID and serial number. is sent 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 this. In the case of FIG. 10A, the combination information 36 includes the module ID of the end effector main body 63a, the module ID of the chuck jaw 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 jaw 63b(2), and the serial number. are stored in association with each other (see FIG. 11B). Therefore, by reading the 2D code C provided on the main body 63a and inquiring the management server 20 based on the module ID of the main body 63a, the customer can receive not only the main body 63a but also the module ID of the chuck jaw 63b from the management server 20. Or serial no. It becomes possible to obtain the following.

In this way, the management server 20 of the modification collectively manages the module IDs of the two modules, the end effector main body 63a (first module) and the chuck claw 63b (second module), using the module ID of the main body 63a. be able to. Therefore, even if the vendor or the like does not provide a module ID on the chuck claw 63b, the module can be appropriately managed. In addition, when the chuck jaw 63b is changed to a different chuck jaw 63b, the control unit 21 of the management server 20 changes the module ID of the chuck jaw 63b stored in association with the module ID of the main body 63a to the module of the chuck jaw 63b after the change. Update to ID. Therefore, the information on the chuck claw 63b can be easily corrected by updating the information in the storage section 23 without the customer having to reapply the 2D code C provided on the main body 63a.

In this modified example, the combination of one module provided with 2D code C and one module not provided with 2D code C is collectively managed, but the combination is not limited to this. Module ID and serial number in a combination of one module and two or more modules for which 2D code C is not provided. It may also be used as something that collectively manages. For example, when two sets of chuck jaws are attached to the main body of an end effector, resulting in a total of three module combinations, the module ID and serial number. may be managed collectively. Alternatively, the present invention may be applied to the management of two or more feeders that respectively supply parts types used in two or more combinations. Further, this modification may be applied to a case in which a vendor checks in advance the errors and accuracy of combinations of two or more modules, and collectively manages combinations of modules that have ensured a 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 invention is not limited to this. For example, each time the chuck claw 63b is replaced, the customer may issue the 2D code C using a printer and reapply it to the main body 63a of the end effector.

In the embodiments and modifications described above, the module is provided with a 2D code C such as a barcode or QR code (registered trademark), but the module is not limited to this. ) An IC tag such as a tag may be provided in the module, and the information in the tag may be recognized by a tag recognition device. That is, the identifier may be anything provided as a code or an IC tag as a holding part that holds identification information. Note that the IC tag does not need to be exposed on the surface as long as information can be read and written from the outside.

In the embodiment described above, the vendor attaches the 2D code C to the module and ships the module to the customer, but the invention is not limited to this. For example, the vendor may ship the module to the customer without pasting the 2D code C and notify the customer of the 2D code C information, and the customer may issue the 2D code C using a printer and paste it onto the module. . Alternatively, the vendor may ship the 2D code C separately from the module. Alternatively, the information on the 2D code C may be notified to the customer not from the vendor but from the management server 20.

In the above-described embodiment, the work system 60 is composed of a plurality of modules including the robot 61. However, the work system is not limited to this, and may include the robot 61 as long as the work system is a system composed of a plurality of modules. It may be absent.

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 identifier may be associated with an individual serial number of the module in addition to the unique information. In this way, by recognizing the identifier provided on the module, it is possible to obtain the module's serial number and confirm the manufacturing history of the module, making it possible to manage the module more appropriately. .

In the module management system of the present disclosure, the modules include a first module provided with the identifier and one or more second modules used in combination with the first module and not provided with the identifier. and instead of providing the identifier in the second module, the management unit stores the unique information of the second module in association with the unique information of the first module in the storage unit. It may also be possible to do so. In this way, the unique information of each of the first module and the second module can be collectively managed using the identifier of the first module. Therefore, for example, even if the second module has a size or shape that makes it difficult to provide an identifier, the module can be appropriately managed.

In the module management system of the present disclosure, when the combination is changed to a different second module, the management unit stores the second module 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 changed unique information of the second module. In this way, the information in the second module can be easily modified by updating the information in the storage section without changing the identifier provided in the first module.

The present disclosure can be used in the manufacturing industry of module management systems and the like.

10 equipment introduction support system, 12 network, 20 management server, 21, 41, 51 control section, 22 simulation section, 23, 43, 53 storage section, 26, 46, 56 communication section, 28, 47, 57 input section, 29 , 48, 58 display section, 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 introduction record DB, 36 module combination information, 37 vendor DB, 39 customer DB, 40 vendor terminal, 49 printer, 50 customer terminal, 60 work system, 61 robot, 62 robot arm, 63 end effector, 63a main body, 63b, 63b (1) to (3) chuck claw, 64 camera, 65 lighting, 66 substrate transfer device, 67 feeder, 68 control device, C 2D code, MD model, MP marketplace, P storage bag, S substrate.

Claims (2)

A module management system that manages multiple types of modules that constitute a work system,
a storage unit that stores information;
a management unit that sets unique information determined based on the type and model of the module, stores the unique information in the storage unit in association with the specifications of the module;
Equipped with
an identifier associated with at least the unique information is provided on the module so that it can be recognized by a recognition device from the outside;
The modules include a first module provided with the identifier, and one or more first modules that are replaceably attached to the first module to be used in combination with the first module and are not provided with the identifier. 2 modules,
The management unit stores the unique information of the second module in association with the unique information of the first module in the storage unit, instead of providing the identifier on the second module, and When the second module attached to the first module is replaced , the unique information of the second module stored in the storage unit in association with the unique information of the first module is changed after the replacement . update the unique information of the second module of the module management system. The module management system according to claim 1,
The identifier is associated with the individual serial number of the module in addition to the unique information. Module management system.

Images