Molding management system

Abstract

To provide a molding management system capable of suppressing unauthorized deletion of lot information change history information.SOLUTION: Provided is a molding management system including a server, wherein the server includes a storage unit that stores lot information in which lot identification information for identifying a lot of a product and lot-related information related to the lot of the product are associated with each other, and a control unit that displays an image for receiving an operation of deleting at least a part of information indicating a history related to a change of target lot information selected from the lot information as deletion target information, wherein when the operation is received through the image, the control unit deletes the deletion target information according to the operation, changes the target lot information to the target lot information before the history indicated by the deletion target information is changed, and stores deletion history information indicating a history related to deletion of the deletion target information in the storage unit in association with the lot identification information included in the target lot information.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] TECHNICAL FIELD This disclosure relates to a molding management system. [Background technology]

[0002] 2. Description of the Related Art Research and development is being conducted on techniques for managing the production of products in a production process that includes an injection molding process of products using resin materials such as plastics using an injection molding machine.

[0003] Here, in the management of product production, various information related to the production of products is recorded. Regarding the recording of such various information, a data cancellation control method is known that records transaction data and, when the transaction data is recorded erroneously, cancels the transaction data. The data cancellation control method includes a recording means that records transaction details and a total amount with a transaction serial number added thereto, and a means for inputting the transaction serial number and the total amount at the time of a cancellation operation, reads the total amount from the recorded data by the recording means corresponding to the input transaction serial number, compares the read total amount with the input total amount, and, if the comparison is consistent, cancels the recorded data in the storage area of ​​the recording means corresponding to the transaction serial number (see Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Special Publication No. 06-028072 Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the data cancellation control method described in Patent Document 1, no history is kept regarding the deletion of recorded data from the transaction serial number, making it difficult to later trace when, who, and why the recorded data was deleted. This leads to the unauthorized deletion of various information related to the production of products being overlooked, which is undesirable. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, one aspect of the present disclosure is a molding management system that includes a server communicably connected to a terminal device and manages production of a product in a production process that includes an injection molding process of the product by an injection molding device, the system including: a storage unit that stores one or more pieces of lot information in which lot identification information that identifies the lot of the product is associated with lot-related information that includes one or more pieces of information related to the lot of the product; and a lot information change history information deletion unit that deletes at least a portion of lot information change history information that indicates a history of changes to target lot information selected from the one or more pieces of lot information stored in the storage unit as deletion target lot information change history information. and a control unit that causes the terminal device to display a lot information change history information deletion image that accepts a deletion operation, wherein when the control unit receives the lot information change history information deletion operation via the lot information change history information deletion image, the control unit deletes the lot information change history information to be deleted in accordance with the received lot information change history information deletion operation, changes the target lot information to the target lot information before the change in history indicated by the lot information change history information to be deleted, and stores deletion history information indicating the history of the deletion of the lot information change history information to be deleted in the memory unit in association with the lot identification information included in the target lot information. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a diagram showing an example of the configuration of a molding management system 1. FIG. [Figure 2] FIG. 10 is a diagram showing an example of a main menu image P1. [Figure 3] FIG. 10 is a diagram showing an example of a terminal image P2. [Figure 4] FIG. 10 is a diagram showing an example of a lot search image P3. [Figure 5]10 is an example of a history information display image P4. The history information display image P4 is an area in which various information included as history information in the lot-related information of the target lot information is displayed. [Figure 6] FIG. 6 is a diagram showing an example of a comment acceptance image P5 displayed on the lot history image P4 by selecting the button B51 shown in FIG. 5. [Figure 7] FIG. 10 is a diagram showing an example of a lot history image P4 immediately after a selection operation is performed on a button B61. [Figure 8] FIG. 10 is a diagram showing an example of a lot search image P3 in which lot information is displayed after deletion of the deletion target lot information change history information. [Figure 9] FIG. 10 is a diagram showing an example of a history information display operation acceptance image P6. [Figure 10] FIG. 2 is a diagram illustrating an example of a hardware configuration of a server 30. [Figure 11] FIG. 2 is a diagram illustrating an example of a functional configuration of a server 30. [Figure 12] FIG. 10 is a diagram showing an example of the flow of processing in which the server 30 deletes lot information change history information. DETAILED DESCRIPTION OF THE INVENTION

[0008] <Embodiment> Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0009] <Outline of molding management system> First, an overview of the molding management system according to the embodiment will be described.

[0010] A molding management system according to an embodiment manages production of products in a production process that includes an injection molding process of the products using an injection molding machine. The molding management system includes a server. The server is communicably connected to a terminal device. The server also includes a memory unit and a control unit. The memory unit stores one or more pieces of lot information in which lot identification information identifying a lot of the product is associated with lot-related information including one or more pieces of information related to the lot of the product. The control unit causes the terminal device to display a lot information change history information deletion image that accepts a lot information change history information deletion operation to delete at least a portion of lot information change history information indicating a history of changes to target lot information selected from the one or more pieces of lot information stored in the memory unit as lot information change history information to be deleted. When the control unit accepts the lot information change history information deletion operation via the lot information change history information deletion image, it deletes the lot information change history information to be deleted in accordance with the accepted lot information change history information deletion operation. In this case, the control unit changes the target lot information to the target lot information before the history indicated by the lot information change history information to be deleted. In this case, the control unit also stores in the storage unit deletion history information indicating the history of deletion of the deletion target lot information change history information in association with the lot identification information included in the target lot information.

[0011] As a result, the molding management system according to the embodiment can easily identify the time when the target lot information change history information was deleted, the user, etc., based on the deletion history information. As a result, the molding management system can prevent the lot information change history information from being illegally deleted.

[0012] The configuration of the molding management system according to the embodiment and the processing performed by the server included in the molding management system will be described in detail below.

[0013] In addition, since the molding management system according to the embodiment can delete the lot information change history information, even if the user changes the lot information by mistake, the user can be made to change the lot information again. As a result, the molding management system can accurately trace events that have occurred to the products of a certain lot, even if a problem occurs at the delivery destination of the products of that lot, or in a work process that is performed after the work process currently being performed on the products of that lot.

[0014] <Configuration of molding management system> The configuration of the molding management system according to the embodiment will be described below by taking the molding management system 1 as an example.

[0015] FIG. 1 is a diagram showing an example of the configuration of a molding management system 1. As shown in FIG.

[0016] The molding management system 1 is a type of manufacturing execution system (MES). For example, the molding management system 1 includes one or more managed devices 10, an information processing device 20, and a server 30. The molding management system 1 may be configured not to include some or all of the one or more managed devices 10. The molding management system 1 may also be configured not to include the information processing device 20. In the following, as an example, a case will be described in which the molding management system 1 includes a plurality of managed devices 10 as the one or more managed devices 10.

[0017] Each of the multiple managed devices 10 included in the molding management system 1 is a device managed by the molding management system 1. In FIG. 1, for convenience of explanation, the multiple managed devices 10 are each denoted by the same reference numeral. However, some or all of the multiple managed devices 10 may be different types of devices. The multiple managed devices 10 include at least one injection molding device that performs injection molding of a product using a resin such as plastic. The injection molding device 11 shown in FIG. 1 is an example of such an injection molding device. Note that the multiple managed devices 10 may also include an injection molding device that performs metal injection molding (MIM) of a product. In the following, for convenience of explanation, injection molding of a product using a resin such as plastic will be simply referred to as injection molding. In the following, an injection molding device that performs injection molding of a product using a resin such as plastic will be simply referred to as an injection molding device. Furthermore, the multiple managed devices 10 include, in addition to the injection molding device, for example, peripheral equipment of the injection molding device. Examples of peripheral equipment of the injection molding device include, but are not limited to, a material supply device that supplies the injection molding device with material used by the injection molding device to inject mold the product, a transport device that transports the product injection molded by the injection molding device, a cleaning device that cleans the product injection molded by the injection molding device, and a sintering device that sinters the product after being cleaned by the cleaning device. Furthermore, at least one injection molding device included in the multiple managed devices 10 may be a device that performs injection molding using a material other than resin and metal.

[0018] The molding management system 1 manages the production of products in a production process that includes an injection molding process of the products using injection molding devices included in the multiple managed devices 10. Here, the injection molding devices included in the multiple managed devices 10 may have any configuration as long as they are capable of producing products by injection molding. For convenience of explanation, one injection molding of a product using the injection molding device will be referred to as one shot in the following description. In this case, for example, two shots refer to two injection moldings of a product using the injection molding device. Also, for convenience of explanation, each of one or more cavities in a mold that are filled with resin during one shot of molding a product will be referred to as a cavity in the following description. For example, an injection molding device equipped with a mold having two such cavities will mold two products in one shot.

[0019] The information processing device 20 acquires status information indicating the status of each of the multiple managed devices 10 from the managed device 10. For example, the information processing device 20 acquires status information about the injection molding device 11 from the injection molding device 11. Such status information includes a timestamp indicating the date and time when the status information was acquired by the information processing device 20. Some status information also includes device identification information that identifies the managed device 10 in the state indicated by the status information. The status information also includes detection information detected by one or more sensors attached to the managed device 10. The detection information includes, for example, information indicating temperature, information indicating pressure, information indicating current value, information indicating voltage value, etc. That is, the one or more sensors include, but are not limited to, a thermometer, a pressure gauge, an ammeter, a voltmeter, etc. Note that the detection information may include other information detected by the sensors instead of some or all of the above information, or in addition to all of the above information. The status information also includes operating status information indicating the operating status of the managed device 10. The operating status information indicating the operating status of the managed device 10 may be any information as long as it includes information indicating whether the managed device 10 is operating. Furthermore, the information processing device 20 may acquire such status information periodically or non-periodically. As an example, the following describes a case where the information processing device 20 acquires status information each time the above-mentioned one shot is taken. When the information processing device 20 acquires certain status information, it outputs the acquired status information to the server 30. This allows the information processing device 20 to store the acquired status information in the server 30.

[0020] The information processing device 20 is, for example, a workstation, a desktop PC (Personal Computer), a notebook PC, etc., but is not limited to these. The information processing device 20 is communicably connected to each of the multiple managed devices 10 via wired or wireless communication. The communication network connecting the information processing device 20 and each of the multiple managed devices 10 is, for example, a local area network (LAN) within a facility where the multiple managed devices 10 are installed, but is not limited to this. The communication network may also be another communication network such as the Internet or a mobile communication network.

[0021] The server 30 stores the status information acquired by the information processing device 20. For example, when the server 30 acquires certain status information from the information processing device 20, it stores the acquired status information. Here, if the server 30 has already stored status information including device identification information included in the status information, the server 30 replaces the already stored status information with the newly acquired status information. This allows the server 30 to always keep the status information indicating the status of the managed device 10 indicated by the device identification information up to date. Note that the server 30 may be configured to store all acquired status information without performing such replacement. Furthermore, even if the server 30 performs such replacement, it may be configured to newly store the status information before the replacement as information indicating the status history of the managed device 10.

[0022] In addition, in response to a request from a terminal device communicatively connected to the server 30, the server 30 displays various images based on status information stored in the server 30 on the display unit of the terminal device. Here, the images refer to GUIs (Graphical User Interfaces), icons, windows on an OS (Operating System), and the like. Hereinafter, as an example, a case will be described in which the server 30 is communicatively connected to the terminal device 40 as shown in FIG. 1 . Note that in this embodiment, the process of logging in to the server 30 by the terminal device 40 is known, and therefore will not be described here. For ease of explanation, the server 30 receiving an operation from the terminal device 40 via an image displayed on the terminal device 40 will be simply referred to as the server 30 receiving an operation. In other words, in the following, the server 30 performing a certain process in response to a received operation means that the server 30 performs the process in response to the operation received from the terminal device 40 via an image displayed on the terminal device 40.

[0023] The server 30 also accepts various types of information in response to the received operation. For example, the server 30 stores master data including various types of information about products produced by the injection molding apparatus 11 in response to the received operation. The master data includes, for example, product identification information that identifies the various products produced by the injection molding apparatus 11, product type information that indicates the type of product identified by each product identification information, planned production quantity information that indicates the planned production quantity of the product identified by each product identification information, and mold identification information that identifies the mold used to produce the product identified by each product identification information. The master data may have any data structure. For example, the various types of information included in the master data are included in the master data as information associated with the product identification information. Note that the various types of information included in the master data may be information associated with product type information instead of information associated with the product identification information, information associated with both the product identification information and the product type information, or information associated with other information.

[0024] Furthermore, in response to the received operation, the server 30 displays a lot search image on the display unit of the terminal device 40, which accepts a lot search operation for searching for a product lot. The display unit may be, for example, a display of the terminal device 40 or a display device communicably connected to the terminal device 40, but is not limited to these. In the following, as an example, a case will be described in which the display unit is the display of the terminal device 40. Also, in the following, for convenience of explanation, displaying an image on the display unit will be referred to as "displaying the image." The lot search image is an image that accepts various pieces of information that can be used as a search key through the aforementioned lot search operation. In the following, for convenience of explanation, a product lot will be simply referred to as a lot. A lot is a group of one or more products to which lot identification information is assigned for management purposes. Therefore, in the following, for convenience of explanation, products to which lot identification information identifying a certain lot is assigned will be referred to as products of that lot. The lot identification information may be any information that can identify the lot, for example, an ID (Identifier) ​​that identifies the lot, a character string that identifies the lot, or other information that can identify the lot.

[0025] Here, the server 30 stores lot identification information and lot-related information including one or more pieces of information related to the lot, in association with each other. As a result, when searching for information on a certain lot of products, the server 30 can use not only the lot identification information that identifies the lot, but also each of the one or more pieces of information included in the lot-related information associated with the lot identification information as search keys for the lot. In other words, in the lot search image, in addition to the lot identification information, each of the one or more pieces of information included in the lot-related information can be used as search keys for searching for the lot. Hereinafter, for convenience of explanation, information in which lot identification information that identifies a certain lot and lot-related information including one or more pieces of information related to the lot are associated with each other will be referred to as lot information indicating the lot. In other words, when the server 30 receives at least one piece of information from the one or more pieces of information included in the lot-related information through a lot search operation via the lot search image, it displays lot information indicating the lot identified by each of the one or more pieces of lot identification information associated with the received at least one piece of information. This allows the server 30 to easily search for information on products in a desired lot. For this reason, the server 30 stores one or more pieces of lot information for each piece of lot identification information. Here, the lot information is, for example, information that is generated or updated based on information received from a user via one of the update functions that can be executed by the server 30, and is information that is stored in the server 30. Certain lot information includes, for example, lot identification information that identifies the lot indicated by the lot information, and lot-related information about the lot.More specifically, the lot-related information includes: number of products in the lot; type of products in the lot; process information indicating the process currently being performed on the products in the lot; lot status information indicating the status of the lot; start date and time information indicating the date and time when production of the products in the lot began; quality information indicating the results of quality inspections performed on the products in the lot; injection molding device information regarding the injection molding device used to mold the products in the lot; mold identification information identifying the mold installed in the injection molding device; cavity number information indicating the number of cavities in the mold; and history information regarding the products in the lot. The lot-related information may include other information related to the lot instead of, or in addition to, some or all of the above information. However, the following describes, as an example, a case in which at least the history information is included in the lot information. Furthermore, if a quality inspection has not been performed on the product, the quality information indicates that the quality inspection has not been performed on the product. The injection molding apparatus-related information is information including, for example, injection molding apparatus identification information that identifies the injection molding apparatus, operating status information that indicates the operating status of the injection molding apparatus, detection information about the injection molding apparatus, etc. The history information is information including some or all of the following: lot information change history information that indicates the history of changes to the lot information, material history information that indicates the history of the use of materials for the products of the lot, work process change history information that indicates the history of changes to the work process performed on the products of the lot, lot management history information that indicates the history of management of the lot, quality inspection history information that indicates the history of quality inspection of the products of the lot, etc. Note that the history information may be configured to include other information about the products of the lot instead of some or all of the above information, or in addition to all of the above information.

[0026] The method for associating various pieces of information included in the lot-related information with the lot identification information and storing them as lot information in the server 30 may be a known method, such as a method via a GUI, or may be a method to be developed in the future. For the sake of simplicity, the following description will be given, as an example, of a case in which one or more pieces of lot information are pre-stored in the server 30. This means that the aforementioned history information is pre-stored in the server 30.

[0027] In response to the received operation, the server 30 displays a history information display image that displays history information included in the lot-related information of the lot information indicating the selected target lot from one or more pieces of lot information stored in the server 30. For simplicity of explanation, the following description will be given of an example in which the history information includes only lot information change history information. In this case, the history information displayed in the history information display image is lot information change history information.

[0028] For example, the server 30 displays the history information display image by accepting an operation via a main menu image P1 as shown in Fig. 2. Fig. 2 is a diagram showing an example of the main menu image P1.

[0029] When a predetermined main menu image display operation is received, the server 30 displays the main menu image P1. In the example shown in Fig. 2, the main menu image P1 includes six buttons, namely, button B11 to button B16.

[0030] The button B11 is a button that displays a dashboard image. When the server 30 receives a selection operation on the button B11, the server 30 generates a dashboard image and displays the generated dashboard image. Here, the dashboard image is an image that displays information necessary for a user of the terminal device 40 to manage the production of products by the injection molding device designated by the user while the injection molding device is in operation. In this embodiment, the selection operation is a click, a tap, or the like, but is not limited to these.

[0031] Button B12 is a button that displays a master data management image. When the server 30 receives a selection operation on button B12, it generates a master data management image and displays the generated master data management image. Here, the master data management image is an image that receives operations to input, change, delete, etc. the master data described above. The server 30 can generate, change, delete, etc. master data in response to operations on the master data management image. When the server 30 generates master data, it stores the generated master data. Furthermore, when the server 30 changes the master data, it updates the stored master data to the changed master data.

[0032] The button B13 is a button for displaying a manual image. When the server 30 receives a selection operation for the button B13, the server 30 generates a manual image and displays the generated manual image. Here, the manual image is an image that receives an operation for displaying a manual on how to operate the molding management system 1.

[0033] Button B14 is a button that displays terminal image P2. When server 30 receives a selection operation on button B14, it generates terminal image P2 and displays the generated terminal image P2. Here, terminal image P2 is an image that receives an operation to execute each of the various update-related functions possessed by server 30. In other words, terminal image P2 is an image that receives an operation to display a desired image from among images that receive operations for each of a plurality of update-related functions. A certain type of update-related function is a function that inputs, changes, deletes, etc. information according to that type. Note that terminal image P2 may also be configured to receive an operation to execute functions other than update-related functions. Furthermore, functions other than update-related functions may be any functions.

[0034] Button B15 is a button that displays a user management image. When server 30 receives a selection operation on button B15, it generates a user management image and displays the generated user management image. Here, the user management image is an image that receives operations to input, change, delete, display, etc., information about a user among the information stored in server 30.

[0035] The button B16 is a button that accepts an operation to log out the terminal device 40 from the server 30. When the server 30 accepts a selection operation on the button B16, the server 30 logs out the terminal device 40.

[0036] In this embodiment, the dashboard image, the master data management image, the manual image, and the user management image will not be described.

[0037] Fig. 3 is a diagram showing an example of a terminal image P2. As shown in Fig. 3, the terminal image P2 includes buttons for accepting operations to execute each of a plurality of update-related functions. For example, the terminal image P2 includes buttons B21 and B22 as such buttons.

[0038] The button B21 is a button that accepts an operation to display a lot search image P3, which is an example of the lot search image described above. When the server 30 accepts a selection operation on the button B21, the server 30 generates the lot search image P3 and displays the generated lot search image P3.

[0039] Fig. 4 is a diagram showing an example of the lot search image P3. In the example shown in Fig. 4, the lot search image P3 includes a lot search area RG1, a search result display area RG2, and a processing button group area RG3.

[0040] The lot search area RG1 includes, for example, input fields F11 to F18, a button B31, and a button B32. Note that the lot search area RG1 may be configured to include other GUIs that can accept a lot search operation instead of some or all of these GUIs, or in addition to all of these GUIs. Here, the aforementioned lot search operation refers to an individual operation accepted by the lot search area RG1. Note that in the molding management system 1, searching for a lot means searching for lot information.

[0041] The input field F11 is a field where lot identification information that identifies a desired lot is entered by the user. In FIG. 4, the character string "Lot No." superimposed on the input field F11 is a character string that indicates to the user that the information entered in the input field F11 is lot identification information. In the example shown in FIG. 4, nothing is entered in the input field F11. Note that the lot identification information may be entered in the input field F11 by selecting the lot identification information from a pull-down menu, or by direct entry using an input device such as a keyboard.

[0042] The input field F12 is a field where process information indicating the work process currently being performed on the product of the desired lot by the user, among the various processes included in the production process. Therefore, in the example shown in FIG. 4, the process information is included in the lot-related information described above, and the lot can be searched for using the process information as a search key. The character string "Process" superimposed on the input field F12 in FIG. 4 indicates to the user that the information entered in the input field F12 is process information. In this example, nothing is entered in the input field F12. Note that the process information can be entered into the input field F12 by selecting the process information from a pull-down menu, or by direct input using an input device such as a keyboard.

[0043] The input field F13 is a field for inputting injection molding machine identification information that identifies the injection molding machine that molded the product lot desired by the user or the injection molding machine that will mold the product lot desired by the user. Therefore, in the example shown in FIG. 4, the lot-related information includes the injection molding machine identification information, and the lot can be searched for using the injection molding machine identification information as a search key. The character string "machine" superimposed on the input field F13 in FIG. 4 indicates to the user that the information entered in the input field F13 is injection molding machine identification information. In this example, nothing is entered in the input field F13. The injection molding machine identification information can be entered into the input field F13 by selecting the injection molding machine identification information from a pull-down menu or by directly entering it using an input device such as a keyboard.

[0044] The input field F14 is a field where the user inputs product type information indicating the type of product of the desired lot. Therefore, in the example shown in FIG. 4, the lot-related information includes product type information, and the lot can be searched for using the product type information as a search key. The character string "Item" superimposed on the input field F14 in FIG. 4 indicates to the user that the information input into the input field F14 is product type information. In this example, nothing is input into the input field F14. Note that the product type information can be input into the input field F14 by selecting the product type information from a pull-down menu, or by direct input using an input device such as a keyboard.

[0045] The input field F15 is a field where information identifying the higher-level group to which the desired lot belongs is entered. The following description will be given, as an example, of a case where the group is a production lot. For ease of explanation, the information will be referred to as production lot identification information. Therefore, in the example shown in FIG. 4, the lot-related information includes production lot identification information, and a lot can be searched for using the production lot identification information as a search key. The group may also be another group, such as the work shift of a manager who manages the production of the products of the lot. The character string "Job No." superimposed on the input field F15 in FIG. 4 indicates to the user that the information entered in the input field F15 is production lot identification information. In this example, nothing is entered in the input field F15. The production lot identification information may be entered in the input field F15 by selecting the production lot identification information from a pull-down menu or by directly entering it using an input device such as a keyboard.

[0046] The input field F16 is a field where lot status information indicating the desired lot status is entered by the user. Therefore, in the example shown in FIG. 4 , the lot-related information includes the lot status information, and a lot can be searched for using the lot status information as a search key. The character string "Lot Status" superimposed on the input field F16 in FIG. 4 indicates to the user that the information entered in the input field F16 is lot status information. In this example, nothing is entered in the input field F16. The lot status information indicates one of the following states: a lot is stopped, a lot is being prepared, a lot is waiting, or a lot is completed. Hereinafter, for convenience of explanation, a state in which a lot is stopped will be simply referred to as "lot stopped." Also, for convenience of explanation, a state in which a lot is being prepared will be simply referred to as "lot being prepared." Also, for convenience of explanation, a state in which a lot is waiting will be simply referred to as "lot waiting." For ease of explanation, the state in which a lot has been completed will be referred to simply as “lot completion.” Note that the input of lot status information into the input field F16 may be performed by selecting lot status information from a pull-down menu, or by direct input using an input device such as a keyboard.

[0047] Input fields F17 and F18 are fields where the user inputs period information indicating the period including the date when production of the desired lot of products began. Therefore, in the example shown in FIG. 4, the lot-related information includes information indicating the date, and the lot can be searched for using this information as a search key. The character string "Start Date of First Process from" superimposed on input field F17 in FIG. 4 indicates to the user that the information entered in input field F17 is start date and time information indicating the start date and time of the period. The character string "Start Date of First Process to" superimposed on input field F18 in FIG. 4 indicates to the user that the information entered in input field F18 is end date and time information indicating the end date and time of the period. In this example, nothing is entered in input fields F17 and F18. The start date and time information can be entered in input field F17 by selecting a date using a calendar or the like and a time using a clock or the like, or by direct input using an input device such as a keyboard. The end date and time information may be entered into the input field F18 by selecting the date using a calendar or the like, selecting the time using a clock or the like, or by direct input using an input device such as a keyboard. The start date and time information may be information indicating only the date and time. The end date and time information may be information indicating only the date and time.

[0048] The button B31 is a button that accepts an operation to delete the information entered in some or all of the input fields F11 to F18. In other words, the button B31 is a button that accepts an operation to clear the information entered in some or all of the input fields F11 to F18. When the button B31 is selected, the server 30 deletes the information entered in some or all of the input fields F11 to F18.

[0049] Button B32 is a button that accepts an operation to execute a search for a lot based on the information entered in some or all of input fields F11 to F18. When button B32 is selected, server 30 extracts one or more pieces of lot information that include the information entered in some or all of input fields F11 to F18 from one or more pieces of lot information stored in advance. After extracting one or more pieces of lot information, server 30 displays a list of the one or more pieces of extracted lot information in search result display area RG2. For ease of explanation, this list will be referred to below simply as a lot information list.

[0050] The search result display area RG2 is an area where a list of lot information is displayed as a result of a selection operation on the button B32. If no selection operation is performed on the button B32, the search result display area RG2 may display a list of all lot information stored in the server 30, or may display nothing. In the example shown in FIG. 4, the list is displayed in the search result display area RG2. The number of lot information items to be displayed in the search result display area RG2 may be determined in advance. In this case, the search result display area RG2 includes a button for displaying lot information that could not be displayed in the search result display area RG2.

[0051] In the example shown in FIG. 4, the lot information displayed in the search result display area RG2 includes lot identification information as well as some of the lot-related information. Specifically, the lot information includes lot identification information, production quantity information, production type information, process information, lot status information, and start date and time information. Note that the lot information may include all of the lot-related information along with the lot identification information. For example, the lot information displayed at the top of the search result display area RG2 shown in FIG. 4 includes lot identification information "1234567890," production quantity information "10," production type information "Part 1," process information "Shipping Inspection SB1," lot status information indicating that the lot is being prepared, and start date and time information "2022-06-08 08:00." Here, "10" represents the production quantity information indicating 10 units. "2022-06-08 08:00" represents the start date and time information indicating 8:00 AM on June 8, 2022.

[0052] A detailed display button (not shown) is displayed in association with each piece of lot information displayed in the search result display area RG2. The detailed display button displayed in association with certain lot information is a button that accepts an operation to display a detailed information display image in which detailed information about the lot indicated by the lot information is displayed. The detailed information displayed in the detailed information display image includes at least a portion of the information contained in the lot information that is displayed in the search result display area RG2, and at least a portion of the information contained in the lot information that is not displayed in the search result display area RG2.

[0053] As described above, one or more pieces of information included in the lot-related information of a certain lot information are associated with the lot identification information included in the lot information. Therefore, the server 30 can extract the lot information from the storage area of ​​the server 30 using the lot identification information. This is useful because it not only simplifies the data structure of the lot information but also reduces the load on the server 30 in searching for lots.

[0054] Furthermore, when one or more pieces of lot information are displayed in the search result display area RG2, check boxes are displayed for accepting an operation to select each of the one or more pieces of lot information. For example, the check box C1 shown in FIG. 4 is a check box for accepting an operation to select the lot information displayed in the top row of the search result display area RG2. Note that the search result display area RG2 may also be configured to display check boxes for accepting an operation to select all of the lot information displayed in the search result display area RG2. This allows the server 30 to reduce the effort required for the user to select lot information. For convenience of explanation, the operation of selecting lot information via such check boxes will be referred to as a lot information selection operation below. Note that the selection of certain lot information may also be referred to as the selection of the lot indicated by that lot information.

[0055] The processing button group area RG3 is an area where a GUI is displayed that accepts a processing execution operation that causes the server 30 to start executing a predetermined process on each of the lots indicated by one or more pieces of lot information selected in response to a received lot information selection operation from among the one or more pieces of lot information displayed in the search result display area RG2. In the example shown in FIG. 4, 11 buttons are displayed as such a GUI in the processing button group area RG3. In this example, these 11 buttons include a button B41. In this embodiment, a description of the 11 buttons other than the button B41 will be omitted.

[0056] The button B41 is a button that accepts an operation to display a history information display image that displays history information included in the lot-related information of the target lot information, with the lot information selected by the user in the search result display area RG2 as the target lot information. If a predetermined first gray-out condition is met, the server 30 grays out the button B41 and does not accept any selection operation on the button B41. On the other hand, if the first gray-out condition is not met, the server 30 cancels the gray-out of the button B41 and accepts any selection operation on the button B41. By graying out the button in this manner, the server 30 can prevent erroneous operations by the user. The first gray-out condition is, for example, a condition that includes the following two conditions, Condition 1A and Condition 1B.

[0057] Condition 1A: Multiple lot information items are selected by the user in the search result display area RG2. Condition 1B: No lot information has been selected by the user in the search result display area RG2

[0058] The server 30 determines that the first gray-out condition is met when either condition 1A or condition 1B is met. On the other hand, the server 30 determines that the first gray-out condition is not met when both condition 1A and condition 1B are not met.

[0059] 4, the user has selected the topmost lot information among the multiple lot information displayed in the search result display area RG2, and no other lot information has been selected, so in this example, button B41 is not grayed out.

[0060] When a selection operation is performed on button B41, the server 30 identifies the lot information selected by the user in the search result display area RG2 as the target lot information, and displays a history information display image P4 that displays the history information included in the lot-related information of the target lot information.

[0061] FIG. 5 is an example of a history information display image P4. The history information display image P4 is an area that displays various pieces of information included as history information in the lot-related information of the target lot information. In this example, the history information includes only lot information change history information. Therefore, the history information display image P4 displays a list of lot information change history information included as history information in the lot-related information of the target lot information. As described above, the lot information change history information is information that indicates the history of changes made to the target lot information. In other words, the lot information change history information is information that indicates the history of changes made by a user to at least one piece of information included in the target lot information. For example, if a user makes a change to information X included in the target lot information, the lot information change history information indicates the history of changes made to information X by the user. Information X may be any information included in the target lot information.

[0062] The server 30 may be configured to display the history information display image P4 as one of the images included in the lot search image P3, or may be configured to display the history information display image P4 in a separate window, or may be configured to display the history information display image P4 superimposed on the lot search image P3, or may be configured to display the history information display image P4 in a pop-up, or may be configured to display the history information display image P4 by some other method.

[0063] 5, the lot information change history information displayed in the history information display image P4 includes lot information change date and time information, process information change history information, history type information, lot information changer information, equipment information, production number change history information, production number history information, lot information change reason information, and lot information change comment information. In other words, in this example, the target lot information history information includes lot information change date and time information, process information change history information, history type information, lot information changer information, equipment information, production number change history information, production number history information, lot information change reason information, and lot information change comment information as lot information change history information. Note that the lot information change history information displayed in the history information display image P4 may include other information indicating the history of changes to the target lot information instead of some or all of the above information, or in addition to all of the above information. Here, the lot information change date and time information included in certain lot information change history information is information indicating the date and time when the lot information including the lot information change history information was changed. The process information change history information included in the lot information change history information is information indicating the history of changes to the process information at the date and time indicated by the lot information change date and time information. Note that the process information change history information may be, for example, the process information included in the lot information at the date and time, or other information indicating the history of changes to the process information at the date and time. The history type information included in the lot information change history information is information indicating the type of change to the lot information made by the user. The lot information changer information included in the lot information change history information is information indicating the user who changed the lot information at the date and time. The equipment information included in the lot information change history information is information indicating the equipment that was performing work on the products of the lot indicated by the target lot information at the date and time. Note that the equipment information may be null information if there was no equipment performing work on the products of the lot at the date and time, or may be other information indicating that there was no equipment performing work on the products of the lot at the date and time.The production quantity change number history information included in the lot information change history information indicates the difference between the number indicated by the production quantity information before and after a change in the production quantity information of the lot information at a given date and time. The production quantity change number history information may be expressed as a positive or negative integer, or may be the production quantity information at that date and time. However, if the production quantity change number history information is the production quantity information, the number indicated by the production quantity change number history information matches the number indicated by the production quantity history information. The production quantity history information included in the lot information change history information indicates the history of changes to the production quantity information of the lot information at that date and time. The production quantity history information may be, for example, the production quantity information included in the lot information at that date and time, or other information indicating the history of changes to the production quantity information at that date and time. The lot information change reason information included in the lot information change history information indicates the reason the lot information was changed at that date and time. The lot information change comment information included in the lot information change history information indicates a comment regarding the change to the lot information at that date and time.

[0064] Furthermore, in the history information display image P4 shown in FIG. 5, lot information change date and time information is indicated by "results registration date and time." Furthermore, in the history information display image P4 shown in FIG. 5, process information change history information is indicated by "process." Furthermore, in the history information display image P4 shown in FIG. 5, history type information is indicated by "history type." Furthermore, in the history information display image P4 shown in FIG. 5, lot information change person information is indicated by "results registration worker." Furthermore, in the history information display image P4 shown in FIG. 5, equipment information is indicated by "equipment." Furthermore, in the history information display image P4 shown in FIG. 5, production quantity change number history information is indicated by "increase / decrease number." Furthermore, in the history information display image P4 shown in FIG. 5, production quantity history information is indicated by "current number." Furthermore, in the history information display image P4 shown in FIG. 5, lot information change reason information is indicated by "reason." Furthermore, in the history information display image P4 shown in FIG. 5, lot information change comment information is indicated by "comment."

[0065] The history information display image P4 may be configured to include information about work processes that have not yet been performed. In this case, the history information display image P4 also displays information indicating the start date and time, completion date and time, etc. of each work process. In this case, the information indicating the start date and time and the completion date and time associated with the information about the work processes that have not yet been performed is, for example, null information.

[0066] For example, the lot information change history information displayed in the top row of the history information display image P4 shown in Figure 5 includes "2023-08-24 08:00" as lot information change date and time information, "injection molding" as process information change history information, "lot creation" as history type information, "first user" as lot information change person information, null information as equipment information, "0" as production item quantity change number history information, "0" as production item quantity change history information, "reason 1" as lot information change reason information, and "comment 1" as lot information change comment information. Here, "2023-08-24 08:00" indicates 8:00 on August 24, 2023. Additionally, the "injection molding" is also process information included in the target lot information at 8:00 AM on August 24, 2023, indicating that the work process being performed on the products of the lot indicated by the target lot information at 8:00 AM on August 24, 2023 is the injection molding process. The "lot creation" indicates that the target lot information was created as one of the changes to the target lot information. The "first user" indicates that the user who made the change to the target lot information was the first user. The null information as equipment information in the lot information change history information indicates that there was no equipment performing work on the products of the lot indicated by the target lot information at 8:00 AM on August 24, 2023. The "0" as the production item quantity change history information in the lot information change history information indicates that there was no change to the production item quantity information included in the target lot information when the target lot information was changed at 8:00 AM on August 24, 2023. The "0" as the production item quantity change history information in the lot information change history information also indicates that there was no change in the production item quantity information included in the target lot information when the target lot information was changed at 08:00 on August 24, 2023. The "Reason 1" indicates the reason why the target lot information was changed at 08:00 on August 24, 2023. The "Comment 1" indicates a comment by the first user regarding the change to the target lot information at 08:00 on August 24, 2023.

[0067] 5 includes "2023-08-29 14:50" as lot information change date and time information, "visual inspection / packaging" as process information change history information, "process completed" as history type information, "third user" as lot information change person information, "inspection machine 1" as equipment information, "0" as production quantity change number history information, "10" as production quantity change history information, "reason 5" as lot information change reason information, and "comment 5" as lot information change comment information. Here, "2023-08-29 14:50" indicates 14:50 on August 29, 2023. Additionally, the "visual inspection and packaging" is also process information included in the target lot information as of 2:50 PM on August 29, 2023, indicating that the visual inspection and packaging process was the work process being performed on the products of the lot indicated by the target lot information at 2:50 PM on August 29, 2023. The "process completed" indicates that the visual inspection and packaging process has been completed as one of the changes to the target lot information, i.e., a change to the lot status information in the target lot information. The "third user" indicates that the user who made the change to the target lot information was the third user. The "inspection machine 1" indicates that inspection machine 1 was the machine performing the work on the products of the lot indicated by the target lot information as of 2:50 PM on August 29, 2023. The "0" as the production item quantity change history information in the lot information change history information indicates that there was no change to the production item quantity information included in the target lot information when the target lot information was changed at 2:50 PM on August 29, 2023. The "10" as the production item quantity change history information in the lot information change history information also indicates that there was no change to the production item quantity information included in the target lot information when the target lot information was changed at 14:50 on August 29, 2023. The "Reason 5" indicates the reason for the change to the target lot information at 14:50 on August 29, 2023. The "Comment 5" indicates a comment by a third user regarding the change to the target lot information at 14:50 on August 29, 2023.

[0068] 5 includes "2023-08-29 14:51" as lot information change date and time information, "visual inspection / packaging" as process information change history information, "cancellation of completion" as history type information, "third user" as lot information change person information, null information as equipment information, "0" as production quantity change number history information, "10" as production quantity change history information, "reason 6" as lot information change reason information, and "comment 6" as lot information change comment information. Here, "2023-08-29 14:51" indicates 14:51 on August 29, 2023. The "Cancellation of Completion" indicates that, as one of the changes to the target lot information, the completion of the visual inspection and packaging process scheduled for 14:50 on August 29, 2023 was canceled at 14:51 on August 29, 2023, i.e., a change to the lot status information of the target lot information. Furthermore, the "visual inspection and packaging" is also process information included in the target lot information as of 14:51 on August 29, 2023, indicating that the work process whose completion was canceled at 14:51 on August 29, 2023 was the visual inspection and packaging process. The "Third User" indicates that the user who made the change to the target lot information was a third user. The "Inspection Machine 1" indicates that Inspection Machine 1 was the device that performed the visual inspection and packaging process, the work process whose completion was canceled at 14:51 on August 29, 2023, on the products of the lot indicated by the target lot information. The "0" as the production item quantity change history information in the lot information change history information indicates that there was no change in the production item quantity information included in the target lot information when the target lot information was changed at 14:51 on August 29, 2023. The "10" as the production item quantity change history information in the lot information change history information also indicates that there was no change in the production item quantity information included in the target lot information when the target lot information was changed at 14:51 on August 29, 2023. The "Reason 6" indicates the reason why the completion of the visual inspection and packaging process was canceled at 14:51 on August 29, 2023. The "Comment 6" indicates a comment by a third user regarding the cancellation of the completion of the visual inspection and packaging process at 14:51 on August 29, 2023.

[0069] In this way, the history information display image P4 displays a list of lot information change history information included in the target lot information. For example, by comparing the lot information change history information displayed in the top row of the history information display image P4 shown in FIG. 5 with the lot information change history information displayed in the second row from the top of the history information display image P4 shown in FIG. 5, it can be seen that at 10:02 AM on August 24, 2023, the injection molding process for the product of the lot indicated by the target lot information changed from not started to started. This can be seen from the fact that the history type information is different when comparing these two pieces of lot information change history information. For example, by comparing the lot information change history information displayed in the second row from the top of the history information display image P4 shown in FIG. 5 with the lot information change history information displayed in the third row from the top of the history information display image P4 shown in FIG. 5, it can be seen that at 10:04 AM on August 24, 2023, the injection molding process for the product of the lot changed from started to completed. For this reason, in the lot information change history information displayed in the third row from the top of the history information display image P4 shown in Fig. 5, the production quantity change history information is "10" indicating +10 units, and the production quantity change history information is "10" indicating 10 units. That is, in the example shown in Fig. 5, it can be seen by looking at the history information display image P4 that 10 units of the production lot were molded in the injection molding process during the two minutes from 10:02 on Aug. 24, 2023 to 10:04 on Aug. 24, 2023. Furthermore, for example, when comparing the lot information change history information displayed in the third row from the top of the history information display image P4 shown in Fig. 5 with the lot information change history information displayed in the fourth row from the top of the history information display image P4 shown in Fig. 5, it can be seen that at 12:27 on August 29, 2023, the work process for the products of the lot in question changed from an injection molding process to a visual inspection and packaging process, and that the visual inspection and packaging process changed from a not yet started state to a started state. Therefore, in the lot information change history information displayed in the fourth row from the top of the history information display image P4 shown in Fig. 5, the equipment information is "Inspection Machine 1," which indicates an inspection device.In the example shown in Figure 5, it can be seen by looking at the history information display image P4 that the number of products in the lot has not changed between 10:04 on August 24, 2023 and 12:27 on August 29, 2023. As described above, by displaying the lot information change history information, the server 30 can allow the user to easily identify the date and time, work process, reason, comment, etc., when the number of products in the lot was changed. In other words, by displaying the lot information change history information, the server 30 can improve the traceability of the products.

[0070] The history information display image P4 may be configured to allow the user to edit lot information change reason information, lot information change comment information, etc. In this case, for example, input of lot information change reason information into the history information display image P4 may be performed by selecting lot information change reason information from a pull-down menu, or may be performed by direct input using an input device such as a keyboard. Also, in this case, input of lot information change comment information into the history information display image P4 may be performed by selecting lot information change comment information from a pull-down menu, or may be performed by direct input using an input device such as a keyboard.

[0071] Furthermore, when the history information includes quality inspection history information along with lot information change history information, the history information display image P4 may be configured to display a button associated with each lot information change reason information, which accepts an operation to display a quality inspection history information display image. Here, the quality inspection history information display image refers to an image that displays the quality inspection history information. For example, a button displayed associated with certain lot information change history information is a button that accepts an operation to display a quality inspection history information display image that displays the quality inspection history information included in the history information including the lot information change history information. Also, for example, the quality inspection history information display image is an image that displays, as quality inspection history information, the quality information of the target lot information at the date and time indicated by the lot information change date and time information included in the lot information change history information. Note that the quality information of the target lot information refers to the quality information included in the target lot information. In this case, the target lot information includes one or more pieces of quality information including a timestamp indicating the date and time of generation. When the server 30 receives a selection operation for a certain button that receives an operation for displaying a quality inspection history information display image, the server 30 generates a quality inspection history information display image that displays the quality inspection history information included in the history information including the lot information change reason information associated with the button, and displays the generated quality inspection history information display image. Note that the quality inspection history information display image may also be an image that displays other information indicating the history of quality inspection of the products of the lot indicated by the target lot information as quality inspection history information.

[0072] Comparing the lot information change history information displayed in the second row from the bottom of the history information display image P4 shown in FIG. 5 with the lot information change history information displayed in the bottom row of the history information display image P4 shown in FIG. 5, it can be seen that the completion of the visual inspection and packaging process performed on the products of the lot indicated by the target lot information during the one-minute period from 14:50 on August 29, 2023 to 14:51 on August 29, 2023 was canceled. This suggests that the visual inspection and packaging process may have been completed by mistake at 14:50 on August 29, 2023. Therefore, the following describes, as an example, a case in which the visual inspection and packaging process was completed by mistake at 14:50 on August 29, 2023. In this case, the user can cancel the completion of the visual inspection and packaging process by selecting button B51 included in the history information display image P4 shown in FIG. 5.

[0073] Button B51 accepts an operation to delete the most recent lot information change history information from the list of lot information change history information displayed in the history information display image P4 as lot information change history information to be deleted. In other words, in this example, the lot information change history information to be deleted is the lot information change history information most recently stored in the server 30 among the lot information change history information stored in the server 30 before the deletion of the lot information change history information to be deleted. When button B51 is selected, the server 30 deletes the lot information change history information to be deleted. In this case, the server 30 changes the target lot information to the target lot information before the change indicated by the lot information change history information to be deleted. In this case, the server 30 stores deletion history information indicating the history of the deletion of the lot information change history information to be deleted in association with the lot identification information included in the target lot information. This allows the server 30 to easily identify the time, user, etc., when the target lot information change history information was deleted based on the deletion history information. As a result, the server 30 can prevent the unauthorized deletion of lot information change history information. Furthermore, even if the user makes a mistake in changing the target lot information, the server 30 can allow the user to redo the change in the target lot information. As described above, the button B51 or the history information display image P4 is an example of a lot information change history information deletion image.

[0074] The history information display image P4 may be configured to allow a GUI such as a checkbox to select each piece of lot information change history information included in the list of lot information change history information displayed on the history information display image P4 as lot information change history information to be deleted. In this case, the server 30 identifies each piece of lot information change history information selected by the GUI as lot information change history information to be deleted. Then, upon receiving a selection operation on button B51, the server 30 deletes each piece of lot information change history information identified as lot information change history information to be deleted. In this case, the server 30 changes the target lot information to the target lot information immediately after the history change indicated by each piece of lot information change history information remaining in the list. This prevents inconsistencies from occurring between the target lot information before and after the deletion of lot information change history information desired by the user from the lot information change history information included in the list. In this case, the server 30 stores deletion history information indicating the history of the deletion of each piece of lot information change history information selected as lot information change history information to be deleted, in association with the lot identification information included in the target lot information.

[0075] Here, if a predetermined second gray-out condition is met, the server 30 grays out the button B51 and does not accept any selection operation on the button B51. On the other hand, if the second gray-out condition is not met, the server 30 cancels the graying out of the button B51 and accepts any selection operation on the button B51. By graying out the button in this manner, the server 30 can prevent erroneous operations by the user. The second gray-out condition is, for example, a condition that includes the following condition 2A.

[0076] Condition 2A: Lot information change history information is not displayed on the history information display image P4

[0077] If condition 2A is satisfied, the server 30 determines that the second gray-out condition is satisfied. On the other hand, if condition 2A is not satisfied, the server 30 determines that the second gray-out condition is not satisfied. Note that the second gray-out condition may include multiple conditions. In this case, the server 30 determines that the second gray-out condition is satisfied if at least one of the multiple conditions is satisfied. On the other hand, in this case, the server 30 determines that the second gray-out condition is not satisfied if all of the multiple conditions are not satisfied.

[0078] In the example shown in FIG. 5, the lot information change history information is displayed in the history information display image P4, and therefore the button B51 is not grayed out in this example.

[0079] Such a button B51 may be a button that accepts an operation to display a comment acceptance image P5. The comment acceptance image P5 is an image that accepts history deletion comment information that indicates a comment regarding the deletion of lot information change history information that is set as the lot information change history information to be deleted in the history information display image P4. In this case, when a selection operation is performed on the button B51 shown in FIG. 5, the server 30 generates the comment acceptance image P5 and displays the generated comment acceptance image P5. Note that the server 30 may be configured to display the comment acceptance image P5 in a pop-up, may be configured to display the comment acceptance image P5 within the lot history image P4, may be configured to display the comment acceptance image P5 in a separate window, or may be configured to display the comment acceptance image P5 by some other method.

[0080] FIG. 6 is a diagram showing an example of a comment acceptance image P5 displayed on the lot history image P4 by selecting the button B51 shown in FIG.

[0081] The comment reception image P5 includes, for example, input fields F21 to F23, a button B61, an area RG4, and an area RG5.

[0082] The input field F21 is a field for inputting user identification information that identifies the user who will delete the lot information change history information that is designated as the lot information change history information to be deleted in the lot history image P4. In FIG. 6, the character string "Worker ID" superimposed on the input field F21 indicates to the user that the information entered in the input field F21 is user identification information. By default, the input field F21 is input with user identification information for the user currently logged in to the server 30. The method by which the server 30 identifies the user identification information may be a known method or a method to be developed. In the example shown in FIG. 6, "1234567" is input as the default user identification information in the input field F21. Note that input of user identification information other than the default user identification information into the input field F21 may be performed by selecting the user identification information from a pull-down menu or by direct input using an input device such as a keyboard.

[0083] The input field F22 is a field for inputting user name information indicating the name of the user who will delete the lot information change history information that is designated as the lot information change history information to be deleted in the lot history image P4. In FIG. 6, the character string "Worker Name" superimposed on the input field F22 indicates to the user that the information entered in the input field F22 is user name information. By default, the input field F22 is input with the user name information of, for example, the user currently logged in to the server 30. The method by which the server 30 identifies the user name information may be a known method or a method to be developed in the future. In the example shown in FIG. 6, "Third User" is input as the user name information entered by default in the input field F22. Note that input of user name information into the input field F22 other than the default user name information may be performed by selecting the user name information from a pull-down menu or by direct input using an input device such as a keyboard.

[0084] The input field F23 is a field for inputting history deletion comment information indicating a comment regarding the deletion of lot information change history information that is designated as the lot information change history information to be deleted in the history information display image P4. The character string "Comment" superimposed on the input field F23 in FIG. 6 indicates to the user that the information input into the input field F23 is history deletion comment information. Note that the history deletion comment information may be input into the input field F23 by selecting history deletion comment information from a pull-down menu, or by direct input using an input device such as a keyboard. In the example shown in FIG. 6, the third user has directly input history deletion comment information indicating the comment "Comment 7" into the input field F23.

[0085] The button B61 is a button that accepts an operation to confirm the deletion of lot information change history information that is set as lot information change history information to be deleted in the history information display image P4. The lot information change history information that is set as lot information change history information to be deleted in the history information display image P4 refers to the most recent lot information change history information among the lot information change history information displayed in the history information display image P4, or one or more individual lot information change history information selected by the user in the history information display image P4. When the button B61 is selected, the server 30 deletes the lot information change history information that is set as lot information change history information to be deleted in the history information display image P4. In this case, the server 30 changes the target lot information to the target lot information immediately after the history change indicated by each of the lot information change history information that remains undeleted in the list of lot information change history information displayed in the history information display image P4. In this case, the server 30 generates deletion history information that indicates the history of the deletion of the lot information change history information that is set as lot information change history information to be deleted in the history information display image P4. At this time, the server 30 generates the deletion history information so that the information entered in each of the input fields F21 to F23 is included in the deletion history information.The server 30 then stores the generated deletion history information in association with the lot identification information included in the target lot information.In other words, the server 30 includes the generated deletion history information in the target lot information.

[0086] 6, when the button B61 is selected, the server 30 confirms the deletion of the lot information change history information that is set as the lot information change history information to be deleted in the history information display image P4. This also enables the server 30 to prevent the lot information change history information from being improperly deleted, and allows the user to redo the change to the target lot information even if the user has mistakenly changed the target lot information. In this example, the comment acceptance image P5 or button B61 is an example of a lot information change history information deletion image. Furthermore, the input field F23 is an example of an input field for inputting a comment regarding the deletion of the lot information change history information to be deleted.

[0087] Here, when the deletion of the lot information change history information that is set as the lot information change history information to be deleted in the history information display image P4 is confirmed by selecting button B61, the server 30 may be configured to delete the display of the comment reception image P5 and display a message MS on the lot history image P4, as shown in Figure 7.

[0088] FIG. 7 is a diagram showing an example of the lot history image P4 immediately after the button B61 is selected. As shown in FIG. 7, a message MS is displayed on the lot history image P4. The message MS may be any message indicating that the deletion of the lot information change history information that was set as the lot information change history information to be deleted in the history information display image P4 has been completed. In the example shown in FIG. 7, the message MS is a string of characters that reads, "Lot history cancellation completed." The method for displaying the message MS may be a known method such as a pop-up, or may be a method to be developed in the future.

[0089] Furthermore, after the server 30 confirms the deletion of the lot information change history information that is the lot information change history information to be deleted in the history information display image P4 by selecting button B61, it may delete the display of the comment reception image P5, or the display of both the lot history image P4 and the comment reception image P5, and display another image such as terminal image P2, or it may be configured to perform other processing.

[0090] The server 30 may be configured to gray out the button B61 and not accept any selection operation on the button B61 when a predetermined third gray-out condition is met. In this case, when the third gray-out condition is not met, the server 30 cancels the graying out of the button B61 and accepts any selection operation on the button B61. By graying out the button in this manner, the server 30 can prevent erroneous operations by the user. The third gray-out condition is, for example, a condition that includes the following condition 3A.

[0091] Condition 3A: No history deletion comment information has been entered in input field F23

[0092] If condition 3A is satisfied, the server 30 determines that the third gray-out condition is satisfied. On the other hand, if condition 3A is not satisfied, the server 30 determines that the third gray-out condition is not satisfied. Note that the third gray-out condition may include multiple conditions. In this case, the server 30 determines that the third gray-out condition is satisfied if at least one of the multiple conditions is satisfied. On the other hand, in this case, the server 30 determines that the third gray-out condition is not satisfied if all of the multiple conditions are not satisfied.

[0093] 6, history deletion comment information has been entered in the input field F23. Therefore, in this example, the button B61 is not grayed out. This prevents the server 30 from confirming the deletion of lot information change history information that is set as lot information change history information to be deleted in the history information display image P4 without comment information being entered in the input field F23. This is useful because it helps prevent a decrease in traceability regarding the deletion of lot information change history information.

[0094] Furthermore, when the user selects button B61 to confirm the deletion of lot information change history information that is designated as the deletion target lot information change history information in the history information display image P4, the server 30 may be configured to send a notification to a predetermined information processing device requesting permission for the deletion of the lot information change history information to be deleted before deleting the deletion target lot information change history information, and to delete the lot information change history information to be deleted if the server 30 receives information indicating permission for the deletion of the deletion target lot information change history information as a response to the notification. This corresponds to, for example, an approval flow in which approval is requested from a manager who manages the production of the products for the lot indicated by the target lot information before deleting the deletion target lot information change history information. By double-checking using this approval flow, the server 30 can more reliably prevent the unauthorized deletion of lot information change history information.

[0095] Returning to Figure 6, area RG4 included in the comment reception image P5 is an area where the lot information change history information that is set as the lot information change history information to be deleted in the history information display image P4 is displayed. In the example shown in Figure 6, the lot information change history information that is set as the lot information change history information to be deleted is only the lot information change history information that was displayed in the bottom row of the history information display image P4 shown in Figure 5. Therefore, in this example, only this lot information change history information is displayed in area RG4.

[0096] Area RG5 displays at least a portion of the quality information included in the target lot information at the date and time indicated by the lot information change date and time information in the lot information change history information that is the lot information change history information to be deleted in the history information display image P4. In the example shown in FIG. 6, area RG5 displays the defective product occurrence history information included in the quality information. The defective product occurrence history information includes defective product identification information indicating the defective products that occurred at the date and time, defective product name information indicating the type of defective products that occurred at the date and time, and defective product number information indicating the number of defective products that occurred at the date and time. In FIG. 6, the defective product identification information is represented by "xxx." In FIG. 6, the defective product name information is represented by "yyy." In FIG. 6, the defective product number information is represented by "0." Note that when deleting the lot information change history information, the server 30 also deletes the lot information change history information and the quality information included in the target lot information at the date and time. This is a natural process, considering that the target lot information is changed to the target lot information before the change was made to the target lot information indicated by the deleted lot information change history information.

[0097] In this manner, the server 30 can delete the lot information change history information that is designated as the deletion target lot information change history information in the history information display image P4. The server 30 can also display a list of deletion history information stored to be included in the target lot information, i.e., deletion history information stored in association with the lot identification information of the target lot information, in response to a predetermined operation. The list may be displayed in any manner. For example, the server 30 may display the list by displaying an image containing the list. In this case, the server 30 may be configured to display the deletion history information with the most recent deletion date in a different manner from the display manner of other deletion history information. In this case, the server 30 can make it easier for the user to identify the deletion history information that was most recently deleted. The different display modes may include different fonts such as colors and sizes, different brightness, or other display modes.

[0098] Here, after the deletion of the deletion-target lot information change history information is confirmed, if the server 30 changes the target lot information to the target lot information before the change in the history indicated by the deletion-target lot information change history information, and if the change in the history indicated by the deletion-target lot information change history information includes a change in the lot status information included in the target lot information, the server 30 changes the lot status information included in the target lot information to the lot status information before the change in the history indicated by the deletion-target lot information change history information. Therefore, for example, if the server 30 selects button B61 and confirms the deletion of the lot information change history information that is the deletion-target lot information change history information in the history information display image P4, and then displays the lot search image P3, the lot status information of the lot information selected as the target lot information in the search result display area RG2 shown in FIG. 4 may change as shown in FIG. 8. FIG. 8 is a diagram illustrating an example of the lot search image P3 displaying lot information after the deletion of the deletion-target lot information change history information. In the example shown in FIG. 8, a list of all lot information stored in the server 30 is displayed in the search result display area RG2. The search result display area RG2 of the lot search image P3 shown in FIG. 8 displays the lot information selected as the target lot information in the search result display area RG2 shown in FIG. 4. The lot information in question is lot information with lot identification information "1234567890." Comparing FIG. 4 with FIG. 8, it can be seen that the lot status information of the lot information in question has changed from "Lot Completed" to "Lot Preparation in Progress." This indicates that the lot status information included in the target lot information was changed by the server 30 when the lot information change history information of the target lot information was deleted by selecting button B51 shown in FIG. 5 or button B61 shown in FIG. 6. This is because, in the example shown in FIG. 5, the lot information change history information deleted as the lot information change history information to be deleted was lot information change history information that included "Cancel Completion" as history type information.

[0099] Returning to FIG. 3, the button B22 is a button that accepts an operation to display a history information display operation acceptance image P6. Here, the history information display operation acceptance image P6 is an image that accepts an operation to display the history information display image P4 using the lot identification information of the target lot information. When the server 30 accepts a selection operation on the button B22, it generates the history information display operation acceptance image P6 and displays the generated history information display operation acceptance image P6.

[0100] Fig. 9 is a diagram showing an example of a history information display operation acceptance image P6. In the example shown in Fig. 9, the history information display operation acceptance image P6 includes, for example, an input field F31 and a button B71. Note that the history information display operation acceptance image P6 may be configured to include another GUI instead of one or both of these, or in addition to both of these.

[0101] The input field F31 is a field where the lot identification information of the lot information designated by the user as the target lot information is entered. In FIG. 9, the character string "Lot No." superimposed on the input field F31 is a character string that indicates to the user that the information entered in the input field F31 is the lot identification information. In the example shown in FIG. 9, nothing is entered in the input field F31. Note that the lot identification information may be entered in the input field F31 by selecting the lot identification information from a pull-down menu, or by direct entry using an input device such as a keyboard.

[0102] The button B71 is a button that accepts an operation to confirm the lot identification information entered in the input field F31 as the lot identification information of the target lot information and to display the history information display image P4. When a selection operation is performed on the button B71, the server 30 confirms the lot identification information entered in the input field F31 as the lot identification information of the target lot information. The server 30 then deletes the display of the history information display operation acceptance image P6 and displays the history information display image P4. Here, if a predetermined fourth gray-out condition is satisfied, the server 30 grays out the button B71 and does not accept a selection operation on the button B71. On the other hand, if the fourth gray-out condition is not satisfied, the server 30 cancels the gray-out of the button B71 and accepts a selection operation on the button B71. By graying out the button in this manner, the server 30 can prevent erroneous operations by the user. The fourth gray-out condition is, for example, a condition that includes the following condition 4A.

[0103] Condition 4A: Lot identification information is not entered in input field F31

[0104] If condition 4A is satisfied, the server 30 determines that the fourth gray-out condition is satisfied. On the other hand, if condition 4A is not satisfied, the server 30 determines that the fourth gray-out condition is not satisfied.

[0105] 9, as described above, no lot identification information has been entered in the input field F31, and therefore the button B71 is grayed out in this example.

[0106] The server 30 capable of displaying images such as the history information display image P4 on the terminal device 40 as described above is, for example, a workstation, a desktop PC (Personal Computer), a notebook PC, etc., but is not limited to these. The server 30 may be configured integrally with the information processing device 20.

[0107] The server 30 is communicably connected to the information processing device 20 via wired or wireless communication. The communication network connecting the server 30 and the information processing device 20 may be, for example, a LAN within a facility where multiple managed devices 10 are installed, the Internet, a mobile communication network, or another communication network. In the following, as an example, a case will be described in which the communication network connecting the server 30 and the information processing device 20 is the Internet. In this case, the server 30 is a cloud server.

[0108] Furthermore, the server 30 is communicably connected to the terminal device 40 via wired or wireless communication. In the example shown in FIG. 1, the server 30 is communicably connected to the terminal device 40 via wireless communication. The communication network connecting the server 30 and the terminal device 40 may be, for example, a LAN within the facility where the server 30 is installed, the Internet, a mobile communication network, or another communication network. In the following, as an example, a case will be described in which the communication network connecting the server 30 and the terminal device 40 is the Internet.

[0109] <Server hardware configuration> The hardware configuration of the server 30 will be described below with reference to Fig. 10. Fig. 10 is a diagram showing an example of the hardware configuration of the server 30.

[0110] The server 30 includes, for example, a processor 31, a storage unit 32, and a communication unit 33. These components are connected to each other via a bus so that they can communicate with each other. The server 30 also communicates with the information processing device 20 and the terminal device 40 via the communication unit 33.

[0111] The processor 31 is, for example, a CPU (Central Processing Unit). Note that instead of a CPU, the processor 31 may be another processor such as an FPGA (Field Programmable Gate Array). The processor 31 executes various programs stored in the storage unit 32.

[0112] The storage unit 32 is a storage device including, for example, a hard disk drive (HDD), a solid state drive (SSD), an electrically erasable programmable read-only memory (EEPROM), a read-only memory (ROM), and a random access memory (RAM). Note that instead of being built into the server 30, the storage unit 32 may be an external storage device connected via a digital input / output port such as a universal serial bus (USB). The storage unit 32 stores various types of information, images, and programs processed by the server 30. In other words, the various types of information stored by the server 30 are stored in the storage unit 32.

[0113] The communication unit 33 is a communication device that includes, for example, a digital input / output port such as a USB, an Ethernet (registered trademark) port, an antenna for wireless communication, and the like.

[0114] <Server functional configuration> The functional configuration of the server 30 will be described below with reference to Fig. 11. Fig. 11 is a diagram showing an example of the functional configuration of the server 30.

[0115] The server 30 includes a storage unit 32, a communication unit 33, and a control unit .

[0116] The control unit 34 controls the entire server 30. The control unit 34 includes a reception unit 341, an acquisition unit 342, and a display control unit 343. These functional units included in the control unit 34 are realized, for example, by the processor 31 executing various programs stored in the storage unit 32. Some or all of these functional units may be hardware functional units such as LSI (Large Scale Integration) or ASIC (Application Specific Integrated Circuit).

[0117] The reception unit 341 receives various information and various operations from devices connected to the server 30 so as to be able to communicate with the server 30 .

[0118] The acquiring unit 342 acquires, for each of the multiple managed devices 10, status information about the managed device 10 from the managed device 10 via the information processing device 20. The acquiring unit 342 may be configured to acquire the status information directly from the managed device 10 without going through the information processing device 20.

[0119] The display control unit 343 generates various images in response to operations received via the receiving unit 341. The display control unit 343 transmits the generated images to the terminal device 40 and causes the terminal device 40 to display the images.

[0120] <Process by which the server deletes lot information change history information> The process of the server 30 deleting the lot information change history information will be described with reference to FIG. 12. For ease of explanation, the lot search image P3 or the history information display operation acceptance image P6 will be referred to as the target image below. FIG. 12 is a diagram showing an example of the flow of the process of the server 30 deleting the lot information change history information. The following describes, as an example, a case where the target image is displayed on the terminal device 40 at a timing before the processing of step S110 shown in FIG. 12 is performed. The following also describes, as an example, a case where the lot information has already been stored in the server 30 at that timing.

[0121] The control unit 34 waits until it receives an operation to display the history information display image P4 via the terminal device 40, that is, until it receives a selection of the target lot information and a selection operation on the button B41, or until it receives an input of the lot identification information in the input field F31 and a selection operation on the button B71 (step S110). In Fig. 12, the processing of step S110 is indicated by "Display history information display image?"

[0122] When the control unit 34 determines that an operation to display the history information display image P4 has been received via the terminal device 40 (step S110—YES), the control unit 34 generates the history information display image P4 (step S120). The method for generating the history information display image P4 in step S120 may be a known method or a method to be developed in the future.

[0123] Next, the control unit 34 transmits the history information display image P4 generated in step S120 to the terminal device 40, and causes the terminal device 40 to display the history information display image P4 (step S130).

[0124] Next, the control unit 34 waits until an operation is accepted via the history information display image P4 displayed on the terminal device 40 (step S140). In Fig. 12, the process of step S140 is indicated by "operation accepted?".

[0125] When the control unit 34 determines that an operation has been received via the history information display image P4 displayed on the terminal device 40 (step S140-YES), the control unit 34 determines whether the received operation is an operation that ends the processing of the flowchart shown in Fig. 12 (step S150). The determination processing of step S150 by the control unit 34 may be performed by a known method or a method to be developed in the future. In Fig. 12, the processing of step S150 is indicated by "End?"

[0126] If the control unit 34 determines that the operation received in step S140 is an operation that ends the processing of the flowchart shown in FIG. 12 (step S150-YES), it, for example, deletes the display of the history information display image P4 from the terminal device 40 and ends the processing of the flowchart shown in FIG. 12.

[0127] On the other hand, if the control unit 34 determines that the operation received in step S140 is not an operation that ends the processing of the flowchart shown in FIG. 12 (NO in step S150), it performs processing according to the received operation (step S160). This processing includes a process for deleting the lot information change history information. Here, the processing performed by the control unit 34 in step S160 has already been described in connection with FIGS. 5 to 8, and therefore a detailed description thereof will be omitted. Furthermore, the details of the history information display image P4 displayed by the processing of step S130 have already been described in connection with FIGS. 5 and 6, and therefore a detailed description thereof will be omitted.

[0128] After the process of step S160 is performed, the control unit 34 transitions to step S140 and waits again until an operation is received via the history information display image P4 displayed on the terminal device 40.

[0129] Through the above-described processing, the server 30 displays a history information display image P4 that accepts an operation to delete, as deletion-target lot information change history information, at least a portion of the lot information change history information, which indicates the history of changes to the target lot information selected from one or more pieces of lot information stored in the storage unit 32. Furthermore, when the server 30 accepts the operation via the history information display image P4, the server 30 deletes the deletion-target lot information change history information in accordance with the accepted operation, changes the target lot information to the target lot information before the change in the history indicated by the deletion-target lot information change history information, and stores the deletion history information, which indicates the history of the deletion of the deletion-target lot information change history information, in association with the lot identification information included in the target lot information, in the storage unit 32. This enables the server 30 to prevent the unauthorized deletion of lot information change history information.

[0130] The above-described process for deleting the change history information of the lot information to be deleted may also be applied to the process for deleting other information selected by the user from among the information included in the lot information, such as, but not limited to, material history information, work process change history information, lot management history information, quality inspection history information, and quality information.

[0131] Furthermore, the method of displaying the history information display image P4 via the history information display operation acceptance image P6 described above is a method used in cases where, for example, an identification tag on which the lot identification information of the target lot information is written and a lot label on which a barcode or the like indicating the lot identification information is printed are available, etc. On the other hand, the method of displaying the history information display image P4 via the lot search image P3 described above is a method used in cases where, for example, an office production engineer is operating the terminal device 40 but the lot label is not available.

[0132] The molding management system 1 described above may also include a terminal device 40.

[0133] Furthermore, the search for a lot described above may be performed using a time period during which the lot was not operating normally as a search key. In this case, the lot-related information includes information indicating that time period.

[0134] Furthermore, the search for a lot described above may be performed using one or more pieces of information included in the injection molding apparatus-related information as a search key. In this case, the lot-related information includes injection molding apparatus-related information. The injection molding apparatus-related information included in the lot-related information for a certain lot is information about the injection molding apparatus that molds the products of that lot, and as described above, this information includes, for example, operating status information indicating the operating status of the injection molding apparatus, detection information about the injection molding apparatus, etc. This allows server 30 to more reliably improve the traceability of the products.

[0135] Furthermore, the above-described lot search may be performed using an arbitrary character string as a search key. In this case, when the server 30 receives an arbitrary character string, it identifies information containing the received character string from one or more pieces of information included in the lot-related information, and displays a list of lot information indicating the lots identified by each piece of lot identification information associated with the identified information. This allows the server 30 to more easily search for lots by the user.

[0136] Furthermore, the above-described contents may be combined in any manner.

[0137] <Additional Notes> [1] A molding management system includes a server communicably connected to a terminal device, and manages production of a product in a production process including an injection molding process of the product by an injection molding device, wherein the server includes a storage unit that stores one or more pieces of lot information in which lot identification information that identifies the lot of the product is associated with lot-related information that includes one or more pieces of information related to the lot of the product, and accepts a lot information change history information deletion operation that deletes at least a portion of lot information change history information that indicates a history of changes to target lot information selected from the one or more pieces of lot information stored in the storage unit as deletion target lot information change history information. a control unit that displays a lot information change history information deletion image on the terminal device, wherein when the control unit receives a lot information change history information deletion operation via the lot information change history information deletion image, the control unit deletes the lot information change history information to be deleted in accordance with the received lot information change history information deletion operation, changes the target lot information to the target lot information before the change in history indicated by the lot information change history information to be deleted, and stores deletion history information indicating a history related to the deletion of the lot information change history information to be deleted in the storage unit in association with the lot identification information included in the target lot information. [2] The molding management system described in [1], wherein the lot information change history information to be deleted is the lot information change history information that was most recently stored in the storage unit among the lot information change history information that was stored in the storage unit before the lot information change history information to be deleted was deleted. [3] The molding management system according to [1] or [2], wherein the lot-related information includes lot status information indicating the status of the lot, and when the control unit changes the target lot information to the target lot information before the change in history indicated by the deletion target lot information change history information was made and when the change in history indicated by the deletion target lot information change history information includes a change in the lot status information included in the target lot information, the control unit changes the lot status information included in the target lot information to the lot status information before the change in history indicated by the deletion target lot information change history information was made. [4] A molding management system described in any one of [1] to [3], wherein the lot information change history information deletion image includes an input field for inputting comments regarding the deletion of the lot information change history information to be deleted, and the deletion history information includes comment information indicating the comment input in the input field. [5] The molding management system according to any one of [1] to [4], wherein when the control unit receives a lot information change history information deletion operation via the lot information change history information deletion image, the control unit sends a notification to a predetermined information processing device requesting permission for deletion of the lot information change history information to be deleted before deleting the lot information change history information to be deleted, and when the control unit receives information indicating that deletion of the lot information change history information to be deleted is permitted as a response to the notification, the control unit deletes the lot information change history information to be deleted. [6] A molding management system described in any one of [1] to [5], wherein the lot information change history information deletion image includes quality information about the product of the lot indicated by the target lot information. [7] A molding management system described in any one of [1] to [6], wherein the lot-related information includes, as the one or more pieces of information, injection molding apparatus-related information regarding an injection molding apparatus that molds the product of the lot identified by the lot identification information associated with the lot-related information, and the injection molding apparatus-related information includes at least one of operating status information indicating the operating status of the injection molding apparatus and detection information detected by each of one or more sensors attached to the injection molding apparatus. [8] A molding management system described in any one of [1] to [7], wherein the lot-related information includes quality information about the product of the lot identified by the lot identification information associated with the lot-related information. [9] A molding management system described in any one of [1] to [8], wherein the lot-related information includes process information indicating the work process currently being performed on the product of the lot identified by the lot identification information associated with the lot-related information.

[10] A molding management system according to any one of [1] to [9], including the terminal device.

[11] The molding management system according to any one of [1] to

[10] , including the injection molding device.

[0138] The embodiments of this disclosure have been described in detail above with reference to the drawings, but the specific configuration is not limited to this embodiment, and may be changed, substituted, deleted, etc. as long as it does not deviate from the gist of this disclosure.

[0139] A program for implementing the functions of any of the components of the above-described apparatus may be recorded on a computer-readable recording medium and loaded into a computer system for execution. Here, the apparatus may be, for example, the injection molding apparatus 11, the information processing apparatus 20, the server 30, or the terminal device 40. The term "computer system" herein includes hardware such as an operating system (OS) and peripheral devices. The term "computer-readable recording medium" also refers to portable media such as flexible disks, magneto-optical disks, ROMs, and compact disks (CDs)-ROMs, as well as storage devices such as hard disks built into computer systems. The term "computer-readable recording medium" also includes devices that retain a program for a certain period of time, such as volatile memory within a computer system that acts as a server or client when the program is transmitted via a network such as the Internet or a communication line such as a telephone line.

[0140] The above program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by transmission waves in the transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has the function of transmitting information, such as a network such as the Internet or a communication line such as a telephone line. The program may also be a program for realizing some of the functions described above, or may be a so-called differential file or differential program that can realize the functions described above in combination with a program already recorded in the computer system. [Explanation of symbols]

[0141] 1... molding management system, 10... managed device, 11... injection molding device, 20... information processing device, 30... server, 31... processor, 32... memory unit, 33... communication unit, 34... control unit, 40... terminal device, 341... reception unit, 342... acquisition unit, 343... display control unit

Claims

1. A molding management system that includes a server communicably connected to a terminal device and manages production of a product in a production process that includes an injection molding process of the product by an injection molding device, The server a storage unit that stores one or more pieces of lot information in which lot identification information that identifies the lot of the product is associated with lot-related information that includes one or more pieces of information related to the lot of the product; a control unit that displays, on the terminal device, a lot information change history information deletion image that accepts a lot information change history information deletion operation for deleting, as deletion target lot information change history information, at least a portion of lot information change history information that indicates a history of changes to target lot information selected from the one or more pieces of lot information stored in the storage unit; Equipped with When the control unit receives the lot information change history information deletion operation via the lot information change history information deletion image, deleting the lot information change history information to be deleted in response to the received operation to delete the lot information change history information; changing the target lot information to the target lot information before the change in history indicated by the deletion target lot information change history information; storing deletion history information indicating a history of deletion of the deletion target lot information change history information in the storage unit in association with the lot identification information included in the target lot information; Molding management system.

2. the deletion target lot information change history information is the lot information change history information most recently stored in the storage unit among the lot information change history information stored in the storage unit before the deletion target lot information change history information is deleted; The molding management system according to claim 1 .

3. the lot-related information includes lot status information indicating a status of the lot; when changing the target lot information to the target lot information before the change in history indicated by the deletion target lot information change history information was made, and when the change in history indicated by the deletion target lot information change history information includes a change in the lot status information included in the target lot information, changing the lot status information included in the target lot information to the lot status information before the change in history indicated by the deletion target lot information change history information was made; The molding management system according to claim 1 .

4. the lot information change history information deletion image includes an input field for inputting a comment regarding the deletion of the lot information change history information to be deleted, The deletion history information includes comment information indicating the comment entered in the input field. The molding management system according to claim 1 .

5. When the control unit receives a lot information change history information deletion operation via the lot information change history information deletion image, it transmits a notification to a predetermined information processing device before deleting the lot information change history information to be deleted, and when it receives information indicating that the deletion of the lot information change history information to be deleted is permitted as a response to the notification, it deletes the lot information change history information to be deleted. The molding management system according to claim 1 .

6. The lot information change history information deletion image includes quality information about the product of the lot indicated by the target lot information. The molding management system according to claim 1 .

7. the lot-related information includes, as the one or more pieces of information, injection molding device-related information relating to an injection molding device that molds the product of the lot identified by the lot identification information associated with the lot-related information; The injection molding device-related information includes at least one of operating status information indicating an operating status of the injection molding device and detection information detected by each of one or more sensors attached to the injection molding device. The molding management system according to claim 1 .

8. the lot-related information includes quality information about the product of the lot identified by the lot identification information associated with the lot-related information; The molding management system according to claim 1 .

9. the lot-related information includes process information indicating a work process currently being performed on the product of the lot identified by the lot identification information associated with the lot-related information; The molding management system according to claim 1 .

10. Including the terminal device, The molding management system according to claim 1 .

11. the injection molding apparatus, The molding management system according to claim 1 .

Images