Information processing device, information processing method, and program

Abstract

We provide technology to help you plan production while reducing the risk of production stoppages and quality defects. [Solution] The information processing device of the present disclosure is an information processing device that creates a production plan for a production line comprising a plurality of devices, each having a plurality of components, and is characterized by having a processing unit that creates the production plan based on information that the components have been changed.

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus, an information processing method, and a program.

Background Art

[0002] With the decrease in the working population, the introduction of various devices has been progressing at production sites. In recent years, devices have become larger, more specialized, more complex, and more sophisticated. Such devices are more likely to cause troubles compared to devices with simple structures. Also, specialized knowledge is required to handle troubles. Therefore, it is necessary to formulate a production plan so that the production target number can be achieved while adjusting the production volume and speed so that the load on the device is not too high and appropriately arranging workers with the skills to handle troubles. In formulating a production plan, in recent years, a scheduler such as that disclosed in Patent Document 1 may be used.

[0003] In a production site, unexpected behavior may occur during the update of a device (for example, component replacement, software update). In such a case, there is a risk of leading to long-term production stoppage and quality defects.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] An object of the present disclosure is to provide a technique for formulating a production plan by reducing the risk of production stoppage and quality defects.

Means for Solving the Problems

[0006] The information processing device of the present disclosure is an information processing device for creating a production plan for a production line comprising a plurality of devices, each having a plurality of components, and is characterized by having a processing unit that creates the production plan based on change information of the components. [Effects of the Invention]

[0007] The technology disclosed herein makes it possible to formulate production plans while reducing the risk of production stoppages and quality defects. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows a schematic diagram of an information processing device according to the first embodiment. [Figure 2] This is a diagram showing part change information data according to the first embodiment. [Figure 3] This is a diagram showing the priority constraint data according to the first embodiment. [Figure 4] This is a diagram showing component data according to the first embodiment. [Figure 5] This is a diagram showing order data according to the first embodiment. [Figure 6] This is a diagram showing the process data according to the first embodiment. [Figure 7] This is a diagram showing worker data according to the first embodiment. [Figure 8] This figure shows the data of equipment that can be assigned to each process according to the first embodiment. [Figure 9] This is a diagram showing calendar data according to the first embodiment. [Figure 10] This figure shows a dataset according to the first embodiment. [Figure 11] This figure shows an example of the display of the user interface section according to the first embodiment. [Figure 12] This diagram shows a flowchart of the production plan creation process according to the first embodiment. [Figure 13] This diagram shows the management priority for each device according to the first embodiment. [Figure 14] It is a diagram showing the number of people to be arranged for each device according to the first embodiment. [Figure 15] It is a diagram showing the monitoring workers to be arranged for each device according to the first embodiment. [Figure 16] It is a diagram showing the constraint application period for each device according to the first embodiment. [Figure 17] It is a diagram showing the production plan created by the scheduler according to the first embodiment. [Figure 18] It is a diagram showing a schematic diagram of the information processing apparatus according to the second embodiment. [Figure 19] It is a diagram showing the constraint condition data for each priority according to the second embodiment. [Figure 20] It is a diagram showing the data set according to the second embodiment. [Figure 21] It is a diagram showing a flowchart of the production plan creation process according to the second embodiment. [Figure 22] It is a diagram showing the ratio of the normal cycle time for each device according to the second embodiment. [Figure 23] It is a diagram showing the ratio of the normal production volume per day for each device according to the second embodiment. [[ID=3__0]] [Figure 24] It is a diagram showing an example of the production plan created by the scheduler according to the second embodiment. [Figure 25] It is a diagram showing a schematic diagram of the information processing apparatus according to the third embodiment. [Figure 26] It is a diagram showing the constraint condition data for each priority according to the third embodiment. [Figure 27] It is a diagram showing the process data according to the third embodiment. [Figure 28] It is a diagram showing the data set according to the third embodiment. [Figure 29] It is a diagram showing a flowchart of the production plan creation process according to the third embodiment. [Figure 30] It is a diagram showing the achievable process difficulty level set for each device according to the third embodiment. [Figure 31]This figure shows a schematic diagram of an information processing device according to the fourth embodiment. [Figure 32] This figure shows the priority constraint data according to the fourth embodiment. [Figure 33] This figure shows a dataset according to the fourth embodiment. [Figure 34] This diagram shows a flowchart of the production plan creation process according to the fourth embodiment. [Figure 35] This diagram shows the available delivery dates set for each device according to the fourth embodiment. [Modes for carrying out the invention]

[0009] Each embodiment of this disclosure will be described in detail below with reference to the drawings.

[0010] (First embodiment) Figure 1 is an overall configuration diagram of the first embodiment showing the information processing device 200 and its peripheral devices in the first embodiment. As shown in Figure 1, the information processing device 200 includes a storage unit 300, a processing unit 400, a scheduler 500, and a user interface unit 600. A production plan is created by applying a dataset generated by a method described later to the scheduler 500, and goods are manufactured by the production line 100 according to the production plan.

[0011] The production line 100 has multiple devices, namely device A110 and device B120, and each of devices A110 and B120 has multiple components. For example, device A110 has component a111 and component b112. Device B120 has component c121 and component d122.

[0012] The information processing device 200 includes a storage unit 300 and a processing unit 400. The processing unit 400 includes a data set generation unit 410, which can generate data sets that can be used by the scheduler 500, which will be described later.

[0013] The information processing device 200, based on the information stored in the memory unit 300, creates a dataset with defined constraints for use in creating a production plan using the dataset generation unit 410 of the processing unit 400, and stores it in the dataset storage unit 390. The information processing device 200 transmits the dataset recorded in the recording unit 300, order data, calendar data, process data, and data recording the processes that each device can handle to the scheduler 500. Based on the received data, the scheduler 500 creates a production plan to ensure that product delivery dates are met. Details of the dataset recording unit 390, dataset generation unit 410, and scheduler 500 will be described later. The information processing device 200 is composed of, for example, a personal computer.

[0014] The storage unit 300 creates a dataset with defined constraints used to create production plans and records data such as order data, calendar data, and process data necessary for the scheduler to create production plans. The storage unit 300 has a parts configuration change information data storage unit 310, a priority-based constraint data storage unit 320, and a component data storage unit 330. The storage unit 300 also has an order data storage unit 340, a process data storage unit 350, worker data 360, a process-specific equipment data storage unit 370, a calendar data storage unit 380, and a dataset storage unit 390. This information is also used by the scheduler 500, as shown in Figure 1. The storage unit 300 can be implemented using any known storage medium, and its form is not limited. For example, HDDs and SSDs can be used.

[0015] Figure 2 is a diagram showing the data stored in the parts change information data storage unit 310 in the first embodiment. The parts change information data is data that records when, which equipment, and which parts were replaced for the components of the equipment included in the production line. As shown in Figure 2, the format of the parts change information data includes fields for the name of the equipment on which the parts were replaced, the name of the changed part, and the date and time of the change.

[0016] Figure 3 is a diagram showing the data stored in the priority-based constraint data storage unit 320 in the first embodiment. The priority-based constraint data is data that defines the constraints used when creating a production plan for each management priority determined by the management priority determination unit 411, which will be described later. As shown in Figure 3, the format of the priority-based constraint data includes fields for management priority (explained in the section on the management priority determination unit 411, which will be described later), the number of personnel assigned to the equipment, and the constraint application period. The number of personnel assigned is the number of people who monitor the progress of the equipment after parts replacement, and may include not only the number of people who are present at the equipment but also the number of personnel who periodically check on its condition. The constraint application period refers to the period during which constraints such as the number of personnel assigned are applied when creating a production plan. In this example, the constraint application period is set to "during the next production," in which case the next production, which is the first production after the parts change, will be carried out with the defined number of personnel assigned. The method of specifying the constraint application period is not limited to this method; any period such as 2 hours may be set.

[0017] Figure 4 shows the component data stored in the component data storage unit 330 in the first embodiment. The component data is data that records the components of each device in the production line and their component priority. Component priority refers to the degree to which, for each component constituting each device, replacing that component would have a significant impact on the operation of the device, and therefore requires higher priority in monitoring and managing the progress after component replacement compared to other components. Component priority is used to calculate the management priority determined by the management priority determination unit 411, which will be described later. As shown in Figure 4, the format of the component data includes fields for device name, component name, and component priority, which are associated with each other.

[0018] Figure 5 is a diagram showing the order data stored in the order data storage unit 340 in the first embodiment. The order data is data that records the quantity and delivery date of the ordered products. As shown in Figure 5, the order data format includes fields for product name, quantity, and delivery date, which are associated with each other.

[0019] Figure 6 is a diagram showing the process data stored in the process data storage unit 350 in the first embodiment. The process data is data that defines the production process and its sequence to be performed for each product. As shown in Figure 6, the format of the process data includes fields for the product name, the process name entered in the order of the process, and the standard working time for each process.

[0020] Figure 7 shows the worker data stored in the worker data storage unit 360 in the first embodiment. The worker data is data that records the devices that each worker is capable of handling.

[0021] In this example, "devices that a worker can handle" refers to devices that a worker is capable of maintaining and troubleshooting. As shown in Figure 7, the worker data format includes fields for the worker and the devices they can handle, with these fields linked together.

[0022] In this example, we defined "devices that can be handled" as devices that a worker can maintain and troubleshoot, but this definition is not the only way to define them. For example, if the worker is the developer of the software installed on the device, then the devices on which that software is installed could also be considered "devices that can be handled."

[0023] Figure 8 is a diagram showing the process-specific equipment data recorded in the process-specific equipment data storage unit 370 in the first embodiment. The process-specific equipment data is data that records the equipment that can be used for each process performed in the production of each product. As shown in Figure 8, the format of the process-specific equipment data includes fields for product name, process name, and equipment that can be used in the process, with these fields being associated.

[0024] Figure 9 is a diagram showing the calendar data recorded in the calendar data storage unit 380 in the first embodiment. The calendar data is data that records the holidays and business days of the production site for each day.

[0025] Figure 10 is a diagram showing the dataset recorded in the dataset storage unit 390 in the first embodiment. The dataset is data that defines the constraints used to create the production plan. The dataset is used by the scheduler 500 as constraints when creating the production plan. As shown in Figure 10, the dataset format includes fields such as equipment name, modified part name, part modification date and time, management priority, number of personnel to be assigned, assigned workers, and constraint application period. The management priority will be explained in the section on the management priority determination unit 411, which will be described later.

[0026] Next, the processing unit 400 will be described. The processing unit 400 is a processing unit that creates data for production planning based on the data stored in the storage unit 300. The processing unit 400 has a data set generation unit 410.

[0027] The dataset generation unit 410 creates a dataset with defined constraints for use in creating a production plan and records it in the dataset recording unit 390. The dataset generation unit 410 includes a management priority determination unit 411, a worker assignment unit 412, and a constraint application period determination unit 417.

[0028] The management priority determination unit 411 is a processing unit that determines the management priority for each device that has had its parts replaced. Management priority refers to the degree to which monitoring and management of a device whose components have been changed is prioritized after the parts replacement. The management priority determination unit 411 searches the list of components recorded in the component data recording unit 330 for the names of the parts that have been changed for each device, as recorded in the component change information data recording unit 310, and obtains the numerical value of the component priority set for the corresponding part name. Based on the obtained component priority, the management priority determination unit 411 determines the management priority for each device that has had its parts changed.

[0029] The worker assignment unit 412 is a processing unit that assigns workers to monitor the progress of each device whose parts have been replaced. The worker assignment unit 412 searches the list of constraint conditions recorded for each management priority in the priority constraint condition data storage unit 320 for the management priority value of each device determined by the management priority determination unit 411, and obtains the number of people to be assigned set for the corresponding management priority. Based on the number of people to be assigned obtained above, the worker assignment unit 412 determines the number of people to be assigned to each device whose parts have been replaced. Next, the worker assignment unit 412 refers to the devices that each worker can be assigned to, which are recorded in the worker data storage unit 360. Based on the information of devices that each worker can be assigned to, which is recorded in the worker data storage unit 360, the worker assignment unit 412 determines the number of workers to be assigned to each device whose parts have been changed, which is the number of people determined above.

[0030] The constraint application period determination unit 417 is a processing unit that determines the constraint application period, which is the period during which constraint conditions such as the number of personnel to be assigned and the workers to be assigned are applied when creating a production plan. The constraint application period determination unit 417 searches the list of constraint conditions recorded by management priority in the priority-based constraint condition data storage unit 320 for the management priority value of each device determined by the management priority determination unit 411, and obtains the constraint application period set for the corresponding management priority. Based on the constraint application period obtained above, the constraint application period determination unit 417 determines the constraint application period for each device that has undergone a parts change.

[0031] The user interface unit 600 includes a screen for referencing and registering information on parts changed for each device, and an input means. The user interface unit 600 is configured so that the user can input information on replaced parts. For example, the user interface unit 600 may use a known device such as a personal computer, tablet terminal, or smartphone. Figure 11 shows an example of the display of the user interface unit 600 in the first embodiment.

[0032] The scheduler 500 creates a production plan based on the information in the memory unit 300 to ensure that product production is completed on time.

[0033] Next, the process in the first embodiment will be explained step by step using a flowchart. Figure 12 is a flowchart of the production plan creation process in the first embodiment. In the following example, we will explain the process using the case where a plan is created that assigns the number of people to monitor and the workers to the equipment for which parts have been replaced.

[0034] In step S1001, component a111 and component b112 of device A110 installed on production line 100 are replaced, and component c121 of device B120 is replaced.

[0035] In step S1002, the user interface unit 600 is used to register information about the replaced parts for each device. Figure 2 shows the part change information data in this example that is registered in the part change information data storage unit 310.

[0036] In step S1003, the management priority determination unit 411 determines the management priority for each device in which a part has been replaced, based on the data from the part change information data storage unit 310 and the information from the component data recording unit 330 that were entered in S1002. Figure 13 is a diagram showing the management priority for each device in the first embodiment. In this example, component a111 and component b112 have been changed in device A110, and component c121 has been changed in device B120. From the data in the component data recording unit, the component priorities of component a111, component b112, and component c121 are identified, and in device A110, the component priority of component a111 is 1 and the component priority of component b112 is 2. Since device A has replaced two parts at the same time, the higher priority of component priorities 1 and 2 is adopted, and the management priority of device A110 is determined to be 1. In device B120, the component priority of component c121 is 2, so the management priority of device B120 is set to 2. In this example, when two parts are replaced simultaneously, the priority of the part with the higher priority is used. However, this method is not the only way to determine the priority. Alternatively, the average of the two priorities is calculated and rounded, or the priority is set one level higher when two parts are changed simultaneously.

[0037] In step S1004, the worker assignment unit 412 determines the number of personnel to be assigned to each device and the personnel to monitor each device, based on the management priority for each device determined in S1003, the priority constraint data storage unit 320, and the worker data storage unit 360. Figure 14 is a diagram showing the number of personnel to be assigned to each device in the first embodiment. In this example, as determined in S1003, the management priority of device A110 is 1 and the management priority of device B120 is 2. When the number of personnel to be assigned to each device for each management priority is identified from the data in the priority constraint data recording unit 320, it is defined that the number of personnel to be assigned is 2 for management priority 1 and 1 for management priority 2. Therefore, the number of personnel to be assigned to device A110 is determined to be 2, and the number of personnel to be assigned to device B120 is determined to be 1. Next, the monitoring personnel are determined. Figure 15 is a diagram showing the monitoring personnel to be assigned to each device in the first embodiment. In this example, as shown in Figure 15, there are two workers, worker A and worker C, who can be in charge of device A110, and one worker, worker B, who can be in charge of device B120. In this example, since device A110 is assigned to two people, worker A and worker C are assigned as supervisors. Since device B120 is assigned to one person, worker B is assigned as a supervisor. In this example, supervisors are selected based on the worker data, with the knowledge to troubleshoot and maintain the devices, but this is not the only method of selection. Workers with available schedules may be assigned regardless of whether they have knowledge of the devices.

[0038] In step S1005, the constraint application period determination unit 417 determines the constraint application period for which the constraint conditions are applied to the production plan. Figure 16 is a diagram showing the constraint application period for each device in the first embodiment. In this example, as determined in S1003, the management priority of device A110 is 1 and the management priority of device B is 2. The constraint application period for each management priority is identified from the data in the priority-based constraint condition data recording unit 320. In this example, since the constraint application period is defined as "during the next production" for both management priority 1 and management priority 2, the constraint application period for devices A110 and B120 is determined to be "during the next production". Here, "during the next production" refers to the period from the start of production until the planned number of units are produced or until production is stopped for planned reasons such as maintenance. During the period specified here, the number of personnel and monitoring workers determined in S1004 are assigned to the devices. In this example, the constraint application period was determined to be "during the next production", but this method of determination is not limited to this. For example, you could set a period of time, such as two hours, and only turn on monitoring for the first two hours after production starts.

[0039] In step S1006, the dataset generation unit 410 creates a dataset based on the information determined in S1003 to S1005 and records it in the dataset storage unit 390. Figure 10 shows an example of a dataset.

[0040] In step S1007, the scheduler creates a production plan based on the dataset created in S1006 and the information stored in the memory unit 300, ensuring that the products are delivered on time. A well-known scheduler may be used. A typical scheduler takes various conditions for creating a plan as input, allocates equipment and workers to ensure that products are delivered on time, and outputs a production plan.

[0041] Figure 17 is a diagram showing the production plan created by the scheduler in the first embodiment. In this example, the order data storage unit 340 is set to have an order quantity of 1000 units for product A with a delivery date of June 7, 2024, and an order quantity of 800 units for product B with a delivery date of June 11, 2024, as shown in Figure 5. In this example, as shown in Figure 17, the scheduler assigns the production processes for products A and B to devices A110 and B120, respectively, in order to ensure that the delivery dates for products A and B are met. Furthermore, based on the constraints recorded in the dataset, the scheduler creates a production plan that assigns monitoring tasks to two workers, A and C, for the first production using device A110, and assigns monitoring tasks to worker B for the first production using device B120.

[0042] By performing the processes described above, the scheduler generates a production plan that includes measures to protect the equipment (for example, increasing the number of workers or extending the cycle time) based on information about the equipment whose components have been changed. This reduces the risk of production stoppages and quality defects.

[0043] (Second embodiment) Figure 18 is an overall configuration diagram showing the information processing device 200 and its peripheral devices in an embodiment of the second embodiment. As shown in Figure 18, it comprises a storage unit 300, a processing unit 400, a scheduler 500, and a user interface unit 600. A description of the parts of these components that are common to the first embodiment will be omitted.

[0044] Only the parts of the data stored in the memory unit 300 that differ from those of the first embodiment will be described.

[0045] Figure 19 is a diagram showing the data stored in the priority-based constraint data storage unit 320 in the second embodiment. The priority-based constraint data is data that defines the constraints used when creating a production plan for each management priority determined by the management priority determination unit 411, which will be described later. As shown in Figure 19, the data format includes fields for management priority, percentage of normal cycle time, percentage of normal production volume, and constraint application period. The percentage of cycle time means, for example, if the cycle time when producing a product with device A110 is 5 seconds, setting the percentage of cycle time to 200% means that the cycle time will be 10 seconds. The percentage of production volume means, for example, if it is set to 50%, if the normal production volume is 500 units, it means that the production volume will be 250 units.

[0046] Figure 20 is a diagram showing the dataset recorded in the dataset storage unit 390 in the second embodiment. The dataset is data that defines the constraints used to create the production plan. The dataset is used by the scheduler 500 as constraints when creating the production plan. As shown in Figure 20, the dataset format includes fields such as equipment name, modified part name, part modification date and time, management priority, percentage of normal cycle time, percentage of normal production volume / day, and constraint application period.

[0047] Next, we will explain the operation of each part of the processing unit 400, focusing only on the parts that differ from the first embodiment.

[0048] The dataset generation unit 410 creates a dataset with defined constraints for use in creating a production plan and records it in the dataset recording unit 390. The dataset generation unit 410 includes a management priority determination unit 411, a cycle time determination unit 413, a production volume determination unit 414, and a constraint application period determination unit 417.

[0049] The cycle time determination unit 413 is a processing unit that determines, for each device that has had its parts replaced, what percentage of the normal cycle time it should operate at. For example, if the percentage is 200%, then if the normal cycle time is 5 seconds, it will operate at 10 seconds. The cycle time determination unit 413 retrieves the management priority value for each device from the priority constraint data storage unit 320 and obtains the percentage value of the normal cycle time set for the corresponding management priority. Based on the value obtained above, the cycle time determination unit 413 determines the percentage of the normal cycle time for each device that has had its parts replaced.

[0050] The production volume determination unit 414 is a processing unit that determines what percentage of the normal production volume per day should be set for each device whose parts have been replaced. The production volume determination unit 414 retrieves the management priority value for each device from the priority constraint condition data storage unit 320 and obtains a value that indicates the percentage of the normal production volume set for the corresponding management priority. Based on the value obtained above, the production volume determination unit 414 determines the percentage of the normal production volume for each device whose parts have been replaced.

[0051] Next, the process in the second embodiment will be explained step by step using a flowchart. Figure 21 is a flowchart of the production plan creation process based on one aspect of this embodiment. In the following example, we will explain the case where a plan is created for a device that has had its parts replaced, setting a longer cycle time than usual and a lower daily production volume, by setting the ratio to the normal cycle time and the ratio to the normal production volume per day.

[0052] Step S2001 is the same as step S1001 in the first embodiment, so its explanation is omitted. Also, step S2002 is the same as step S1002 in the first embodiment, so its explanation is omitted. Also, step S2003 is the same as step S1003 in the first embodiment, so its explanation is omitted.

[0053] In step S2004, based on the information determined in S2003, the cycle time determination unit 413 determines the ratio of the normal cycle time for devices A110 and B120. Figure 22 is a diagram showing the ratio of the normal cycle time set for each device in this embodiment. In this example, as determined in S2003, the management priority of device A110 is 1 and the management priority of device B120 is 2. From these management priorities, the ratio of the normal cycle time for each management priority is identified from the data in the priority-based constraint data recording unit 320. Since the ratio of the normal cycle time is defined as 200% for management priority 1 and 120% for management priority 2, the ratio of the normal cycle time for device A110 is 200% and for device B120 is 120%.

[0054] In step S2005, based on the information determined in S2003, the production volume determination unit 414 determines the ratio of normal production volume / day for devices A110 and B120. Figure 23 is a diagram showing the ratio of normal production volume / day set for each device in this embodiment. In this example, as determined in S2003, the management priority of device A110 is 1 and the management priority of device B120 is 2. The number of people assigned to each device at each management priority is determined from the management priority and the data in the priority-specific constraint condition data recording unit 320. Here, since the ratio of normal production volume / day is defined as 50% for management priority 1 and 80% for management priority 2, the ratio of normal production volume / day for device A110 is 50% and for device B120 is 80%.

[0055] Step S2006 is the same as step S1005 in the first embodiment, so its explanation will be omitted.

[0056] In step S2007, the dataset generation unit 410 creates a dataset based on the information determined in S2003 to S2006 and records it in the dataset storage unit 390. Figure 20 is a diagram showing the dataset in this embodiment.

[0057] Step S2008 is the same as step S1007 in the first embodiment, so its explanation will be omitted.

[0058] Figure 24 shows an example of a production plan created by the scheduler in this embodiment. The conditions of the dataset created in S2007 are reflected, and the scheduler has created a plan for equipment A110 to produce with a cycle time of 200% and a production volume of 50%. Equipment A110 was originally planned to produce 500 units per day, but in this example, the production volume is limited to 250 units to reflect the constraints of the dataset.

[0059] By performing the processes described above, it is possible to reduce the risk of production stoppages or quality defects by formulating a production plan that reduces the production speed and production volume per day immediately after the change, based on the information of the equipment whose components have been modified.

[0060] (Third embodiment) Figure 25 is an overall configuration diagram showing the information processing device 200 and its peripheral devices in an embodiment of the third embodiment. As shown in Figure 25, it comprises a storage unit 300, a processing unit 400, a scheduler 500, and a user interface unit 600. A description of the parts of these components that are common with the first embodiment will be omitted.

[0061] Only the parts of the data stored in the memory unit 300 that differ from those of the first embodiment will be described.

[0062] Figure 26 is a diagram showing the data stored in the priority-based constraint data storage unit 320 in the third embodiment. The priority-based constraint data is data that defines the constraints used when creating a production plan for each management priority determined by the management priority determination unit 411, which will be described later. As shown in Figure 26, the data format includes fields for management priority, process difficulty level that can be handled, and constraint application period. Process difficulty level that can be handled refers to the difficulty level of the process that the equipment can handle. In this example, it is assumed that each process has one of the following difficulty levels set: "low," "medium," or "high," and the process difficulty level that can be handled indicates which of the three difficulty levels the equipment can handle. If the process difficulty level that can be handled is "medium," then the equipment can handle processes of lower difficulty levels, namely "low" and "medium."

[0063] Figure 27 is a diagram showing the process data stored in the process data storage unit 350 in the third embodiment. The process data defines the production process to be performed for each product, the order of the processes, and the difficulty level of each process. As shown in Figure 27, the format of the process data includes fields for product name, process name entered in the order of the processes, process difficulty level, and standard work time. Process difficulty level is an indicator of the difficulty of the work performed in the process. In this example, the difficulty level is set to "high" if high precision is required for the work performed in the process, "medium" if standard precision is required, and "low" if high precision is not required. In this example, the difficulty level is classified in this way, but this classification method is not limited to this method.

[0064] Figure 28 is a diagram showing the dataset recorded in the dataset storage unit 390 in the third embodiment. The dataset is data that defines the constraints used to create the production plan. The dataset is used by the scheduler 500 as constraints when creating the production plan. As shown in Figure 28, the dataset format includes fields such as equipment name, modified part name, part modification date and time, management priority, difficulty level of the process that can be handled, and constraint application period.

[0065] Next, we will describe only the parts of the processing unit 400 that differ from those of the first embodiment.

[0066] The dataset generation unit 410 creates a dataset with defined constraints to be used in creating a production plan and records it in the dataset recording unit 390. The dataset generation unit 410 includes a management priority determination unit 411, an assignable process difficulty determination unit 415, and a constraint application period determination unit 417.

[0067] The process difficulty determination unit 415 is a processing unit that determines the process difficulty that can be handled for each piece of equipment that has had its parts replaced. The process difficulty determination unit 415 searches for the management priority value of each piece of equipment in the priority-based constraint data storage unit 320 from a list of constraint conditions recorded by management priority, and obtains the process difficulty that can be handled set for the corresponding management priority. Based on the difficulty obtained above, the process difficulty determination unit 415 determines the process difficulty that can be handled for each piece of equipment that has had its parts replaced.

[0068] Next, the process in the third embodiment will be explained step by step using a flowchart. Figure 29 is a flowchart of the production plan creation process based on one aspect of this embodiment. In the following example, we will explain the case where a plan is created in which a device that has had its parts replaced is set so as not to be assigned any processes with high difficulty levels as the processes that can be handled.

[0069] Step S3001 is the same as step S1001 in the first embodiment, so its explanation is omitted. Also, step S3002 is the same as step S1002 in the first embodiment, so its explanation is omitted. Also, step S3003 is the same as step S1003 in the first embodiment, so its explanation is omitted.

[0070] In step S3004, the difficulty level of the process that can be handled is determined based on the management priority for each device determined in S3003, the priority constraint condition data storage unit 320, and the information in the worker data storage unit 360. Figure 30 is a diagram showing the process difficulty level set for each device in this embodiment.

[0071] In this example, as determined in S3003, the management priority of device A110 is 1 and the management priority of device B120 is 2. The difficulty level of the processes that each device can handle is identified from the data in the priority constraint data recording unit 320. In this example, the difficulty level of the processes that can be handled is defined as "low" for management priority 1 and "medium" for management priority 2, so the difficulty level of the processes that device A110 can handle is "low" and the difficulty level of device B120 is "medium".

[0072] Step S3005 is the same as step S1005 in the first embodiment, so its explanation is omitted.

[0073] In step S3006, the dataset generation unit 410 creates a dataset based on the information determined in S3003 to S3005 and records it in the dataset storage unit 390. Figure 28 is a diagram showing the dataset in this embodiment.

[0074] Step S3007 is the same as step S1007 in the first embodiment, so its explanation is omitted. In this example, as shown in the process data in Figure 27, all processes for product A have a difficulty level of "high," while the process difficulty levels for product B are "low" for process C and "medium" for process D. The process difficulty level that device A110 can handle is "low," and the process difficulty level that device 120B can handle is "medium." Since neither can handle the processes for product A, the scheduler creates a production plan so that device A110 is responsible for process C of product B and device B120 is responsible for process D of product B.

[0075] By performing the processes described above, it is possible to reduce the risk of production stoppages and quality defects by formulating a production plan based on information about the equipment whose components have been changed, and assigning less difficult processes to the equipment immediately after the component change.

[0076] (Fourth embodiment) Figure 31 is an overall configuration diagram showing the information processing device 200 and its peripheral devices in an embodiment of the fourth embodiment. As shown in Figure 31, it comprises a storage unit 300, a processing unit 400, a scheduler 500, and a user interface unit 600. A description of the parts of these components that are common with the first embodiment will be omitted.

[0077] Only the parts of the data stored in the memory unit 300 that differ from those of the first embodiment will be described.

[0078] Figure 32 shows the data stored in the priority-based constraint data storage unit 320 in the fourth embodiment. The priority-based constraint data is data that defines the constraints used when creating a production plan for each management priority determined by the management priority determination unit 411, which will be described later. As shown in Figure 26, the data format includes fields for management priority, available delivery date, and constraint application period. Available delivery date refers to the delivery date of a product that the equipment can handle. In this example, if the management priority is 1, the available delivery date is set to 5 days or more, and in this case, the equipment is assigned to the production of products with a delivery date of 5 days or more.

[0079] Figure 33 is a diagram showing the dataset recorded in the dataset storage unit 390 in the fourth embodiment. The dataset is data that defines the constraints used to create the production plan. The dataset is used by the scheduler 500 as constraints when creating the production plan. As shown in Figure 33, the dataset format includes fields such as equipment name, modified part name, part modification date and time, management priority, available delivery date, and constraint application period.

[0080] Next, we will explain the functions of each part of the processing unit 400, focusing only on the parts that differ from those of the first embodiment.

[0081] The dataset generation unit 410 creates a dataset with defined constraints for use in creating a production plan and records it in the dataset recording unit 390. The dataset generation unit 410 includes a management priority determination unit 411, an assignable delivery date determination unit 416, and a constraint application period determination unit 417.

[0082] The assignable delivery date determination unit 416 is a processing unit that determines the delivery dates of products that a device can handle for each device that has had its parts replaced. The assignable delivery date determination unit 416 searches the list of constraint conditions recorded for each management priority in the priority constraint condition data storage unit 320 for the management priority value of each device determined by the management priority determination unit 411, and obtains the assignable delivery date set for the corresponding management priority. Based on the difficulty level obtained above, the assignable delivery date determination unit 416 determines the assignable delivery date for each device that has had its parts replaced.

[0083] Next, the process in the fourth embodiment will be explained step by step using a flowchart. Figure 34 is a flowchart of the production plan creation process based on one aspect of this embodiment. In the following example, we will explain the case where a plan is created to assign the equipment that has had its parts replaced to the production of products with ample lead time, rather than products with approaching lead times.

[0084] Step S4001 is the same as step S1001 in the first embodiment, so its explanation is omitted. Also, step S4002 is the same as step S1002 in the first embodiment, so its explanation is omitted. Also, step S4003 is the same as step S1003 in the first embodiment, so its explanation is omitted.

[0085] In step S4004, the available delivery dates are determined based on the management priority for each device determined in S4003, the priority-specific constraint data storage unit 320, and the worker data storage unit 360. Figure 35 shows the available delivery dates set for each device in this embodiment. In this example, as determined in S4003, the management priority for device A110 is 1, and the management priority for device B120 is 2. When identifying the available delivery dates for each device at each management priority, the available delivery dates for management priority 1 are defined as "5 days or more," and for management priority 2, they are defined as "3 days or more." Therefore, the available delivery dates for device A110 are determined to be "5 days or more," and for device B120, they are determined to be "3 days or more."

[0086] Step S4005 is the same as step S1005 in the first embodiment, so its explanation is omitted.

[0087] In step S4006, the dataset generation unit 410 creates a dataset based on the information determined in S4003 to S4005 and records it in the dataset storage unit 390. Figure 33 is a diagram showing the dataset in this embodiment.

[0088] Step S4007 is the same as step S1007 in the first embodiment, so the explanation will be omitted. In this example, as shown in Figure 5, the delivery date for product A is "June 7, 2024", and the delivery date for product B is "June 11, 2024". Since the parts of equipment A110 and equipment B120 were replaced on "June 3, 2024", at the time of the parts replacement there is a grace period of "4 days" until the delivery date for product A and "8 days" until the delivery date for product B. The maximum delivery date that equipment A110 can handle is "5 days or more", and the maximum delivery date that equipment B120 can handle is "3 days or more", so the scheduler creates a production plan so that equipment A110 is responsible for the production of product B and equipment B120 is responsible for the production of product A.

[0089] By performing the processes described above, it is possible to reduce the risk of production stoppages and quality defects by formulating a production plan that allocates the production of products with sufficient lead time to the equipment based on information about the equipment whose components have been changed.

[0090] (Fifth embodiment) This embodiment provides specific examples for each type of replacement part. The contents of this embodiment can be appropriately combined with the first to fourth embodiments described above.

[0091] When a drive source is changed, if high-speed or high-load operation is performed from the start, there is a concern that malfunctions or failures may occur due to rapid wear of each component. Therefore, for example, if the changed component is a drive source, it may be planned to assign the device containing that component to a process with low operational load. Alternatively, the cycle time of the device containing that component may be set to be longer than usual for a predetermined period. Alternatively, it may be planned to break in the device containing that component at a low speed for a predetermined period. Furthermore, if any unusual events occur with the device containing that component for a predetermined period, the operator may be instructed to take countermeasures.

[0092] When oils and greases are added or replaced for the purpose of lubricating machinery, if high-speed or heavy-load operations are performed before the oils and greases have evenly settled into the machinery, there is a concern that malfunctions or failures may occur due to rapid wear of various parts. Therefore, it is advisable to plan a break-in period for the equipment containing the components in question by running it at low speed for a predetermined period. Alternatively, a break-in period may be planned by setting an idle period in which the equipment containing the components in question operates only in the process without producing any products.

[0093] If a manipulator is changed, assigning it to the assembly of products requiring high precision immediately after the change may lead to quality defects. Therefore, it may be advisable to plan the assignment of equipment containing the component to simple processes for a predetermined period. Alternatively, production plans may be designed to assign equipment containing the component to orders with non-urgent deadlines.

[0094] If a sensor is changed, performing high-precision measurements or other operations immediately after the replacement may result in quality defects. Therefore, production plans may be designed to assign equipment containing the component to simpler processes that do not require the same level of sensor accuracy as before the sensor replacement. Alternatively, instructions may be given to operators to take corrective action if any unusual events occur with equipment containing the component for a predetermined period.

[0095] When the software version is changed, the behavior may change before and after the change due to specification changes or bugs, potentially causing abnormalities in processes that previously worked without problems. Furthermore, although the software's operation is checked before installation, bugs may only be discovered after prolonged operation in actual production. Therefore, to ensure early confirmation that no problems occur even during prolonged operation, it may be advisable to plan for longer daily production hours for equipment containing the relevant component. Alternatively, instructions may be given to operators to take corrective action if any unusual events occur during a specified period with equipment containing the relevant component.

[0096] When various parameters of a device are changed, its behavior may change before and after the parameter change, potentially causing abnormalities in processes that previously operated without problems. For example, if the parameters of product inspection software are changed, a product that should be judged as NG may be incorrectly judged as OK. Also, for example, if the parameters of the operating position of a movable part of the device are changed, the operating path of the movable part will change, potentially causing problems such as interference with the surroundings or products falling during transport. Therefore, after changing parameters, it is desirable to monitor the situation in a process with a low production volume to confirm that no problems occur. Accordingly, it may be advisable to plan to reduce production volume for a predetermined period. Alternatively, a plan may be made to operate the device containing the movable part at a low speed for a predetermined period so that surrounding workers can avoid it if the movable part is about to interfere with the surroundings. Furthermore, instructions may be made to install monitoring means (people, cameras, etc.) around the device containing the movable part.

[0097] (Other embodiments) Embodiments of this disclosure also include a control program capable of executing the method described above, and a computer-readable recording medium storing the control program. As a recording medium for supplying the control program, for example, ROM, disks, external storage devices, etc., may be used. To give specific examples, as a computer-readable non-temporary recording medium, flexible disks, optical disks, magneto-optical disks, magnetic tapes, non-volatile memory such as USB memory, SSDs, etc., can be used.

[0098] Furthermore, this disclosure can also be implemented by supplying a program that implements one or more functions of the embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be implemented by a circuit (e.g., an ASIC) that implements one or more functions.

[0099] Furthermore, this disclosure is not limited to the embodiments described above, and the components can be modified and implemented in practice without departing from the gist of the invention. Multiple components from each of the embodiments described above may also be combined as appropriate. Additionally, some components may be removed from the multiple components shown in each embodiment. Furthermore, components from different embodiments may also be combined as appropriate.

[0100] This embodiment includes the following configuration.

[0101] (Item 1) An information processing device for creating a production plan for a production line comprising multiple devices, each having multiple components, The processing unit has a processing unit that creates the production plan based on change information of the aforementioned components. An information processing device characterized by the following.

[0102] (Item 2) The processing unit implements measures in the production plan to protect the device whose components have been changed among the plurality of devices. The information processing device described in item 1, characterized by the features described herein.

[0103] (Item 3) The information processing device according to item 2, characterized in that the countermeasure is to extend the cycle time of the device having change information for the aforementioned components.

[0104] (Item 4) The information processing device according to item 2, characterized in that the countermeasure is to increase the number of workers in charge of the device that has change information on the aforementioned components.

[0105] (Item 5) The information processing apparatus according to item 2, characterized in that the countermeasure is to provide a period of time during which the apparatus having information on changes to the aforementioned components is operated without producing any products.

[0106] (Item 6) The information processing device according to item 2, characterized in that the countermeasure is to assign the production of products with long lead times to a device that has information on changes to the aforementioned components.

[0107] (Item 7) We also have information on the difficulty level of the process, The countermeasure involves assigning the least difficult process among multiple processes to the device that has the information on changes to the aforementioned components. The information processing device described in item 2, characterized in that it is an information processing device.

[0108] (Item 8) The information processing apparatus according to any one of items 1 to 7, characterized in that the information on the changes to the components is at least one of the following: drive source, lubricants, manipulator, sensor, software, operation change, parameter change.

[0109] (Item 9) The information processing device according to any one of items 1 to 8, further comprising a user interface section that allows a user to input the aforementioned change information.

[0110] (Item 10) An information processing method for creating a production plan for a production line comprising multiple devices, each having multiple components, The production plan is created based on the change information of the aforementioned components. An information processing method characterized by the following:

[0111] (Item 11) A program that causes a computer to execute the information processing method described in item 10.

[0112] (Item 12) A computer-readable recording medium containing the program described in item 11.

[0113] (Item 13) Products are manufactured according to a production plan created using the information processing device described in any one of items 1 through 9. A method for manufacturing an article characterized by the following: [Explanation of Symbols]

[0114] 100 production lines 110, 120 equipment 111, 112, 121, 131 Components 200 Information Processing Devices 400 Processing Unit 500 Schedulers

Claims

1. An information processing device for creating a production plan for a production line comprising multiple devices, each having multiple components, The processing unit has a processing unit that creates the production plan based on information that the aforementioned components have been changed. An information processing device characterized by the following.

2. The processing unit implements measures in the production plan to protect the device whose components have been changed among the plurality of devices. The information processing apparatus according to feature 1.

3. The information processing apparatus according to claim 2, characterized in that the countermeasure is to extend the cycle time of the apparatus having change information of the aforementioned components.

4. The information processing apparatus according to claim 2, characterized in that the countermeasure is to increase the number of workers in charge of the device that has change information on the aforementioned components.

5. The information processing apparatus according to claim 2, characterized in that the countermeasure involves providing a period of time during which the apparatus having information on changes to the aforementioned components is operated without producing any products.

6. The information processing apparatus according to claim 2, characterized in that the countermeasure involves assigning the production of products with long lead times to the device having information on changes to the aforementioned components.

7. We also have information on the difficulty level of the process, The countermeasure involves assigning the least difficult process among multiple processes to the device that has the information on changes to the aforementioned components. The information processing apparatus according to feature 2.

8. The information processing apparatus according to claim 1, characterized in that the information on the changes to the components is at least one of the following: a drive source, lubricants, manipulator, sensor, software, operation changes, and parameter changes.

9. The information processing device according to claim 1, further comprising a user interface unit that allows the user to input the modified information.

10. An information processing method for creating a production plan for a production line comprising multiple devices, each having multiple components, The production plan is created based on information that the aforementioned components have been changed. An information processing method characterized by the following:

11. A program for causing a computer to execute the information processing method described in claim 10.

12. A computer-readable recording medium storing the program described in claim 11.

13. Articles are manufactured according to a production plan created by the information processing device described in any one of claims 1 to 9. A method for manufacturing an article characterized by the following:

Images